SPAM is strucked while updating patches, no T-Code is working showing SYNTAX_ERROR

[Former Member]

Hi Techies,

Here I am facing the problem while upgrading the support packages from SAPKA70106 to 11 and SAPKB70106 to 11. I imported both at a time to run patches. got many issues while patches in progress. still Main Import phase is ok. its strucked now, no T-Code is working showing syntax_error. and unable to solve it....please help in this thank you.

No logs are created after this phase.....

I am pasting SLOG n ULOG below.

START imp all              BI7        20130709034050              BASIS1       IDCSAPBIW 20130709034049747  

INFO: event SAP_IMPORT_START triggered successfully

START DISTRIBUTION OF DD-O BI7 S      20130709034050              BASIS1       IDCSAPBIW 20130709034049747  

START tp_getprots          BI7 S      20130709034050              BASIS1       IDCSAPBIW 20130709034049747  

STOP  tp_getprots          BI7 S      20130709034206              BASIS1       IDCSAPBIW 20130709034049747  

STOP  DISTRIBUTION OF DD-O BI7 S      20130709034206              BASIS1       IDCSAPBIW 20130709034049747  

START TBATG CONVERSION OF  BI7 N      20130709034206              BASIS1       IDCSAPBIW 20130709034049747  

START tp_getprots          BI7 N      20130709034206              BASIS1       IDCSAPBIW 20130709034049747  

STOP  tp_getprots          BI7 N      20130709034227              BASIS1       IDCSAPBIW 20130709034049747  

STOP  TBATG CONVERSION OF  BI7 N      20130709034227              BASIS1       IDCSAPBIW 20130709034049747  

START MOVE NAMETABS        BI7 6      20130709034227              BASIS1       IDCSAPBIW 20130709034049747  

START tp_getprots          BI7 P      20130709034227              BASIS1       IDCSAPBIW 20130709034049747  

STOP  tp_getprots          BI7 P      20130709034813              BASIS1       IDCSAPBIW 20130709034049747  

STOP  MOVE NAMETABS        BI7 6      20130709034813              BASIS1       IDCSAPBIW 20130709034049747  

START MAIN IMPORT          BI7 I      20130709034813              BASIS1       IDCSAPBIW 20130709034049747  

A LOG

SAPKB70106           BI7.ALL A 0008 20130709032248 SAPUSER      BASIS1       IDCSAPBIW                    

SAPKB70107           BI7.ALL A 0008 20130709032248 SAPUSER      BASIS1       IDCSAPBIW                    

SAPKB70108           BI7.ALL A 0008 20130709032248 SAPUSER      BASIS1       IDCSAPBIW                    

SAPKB70109           BI7.ALL A 0008 20130709032248 SAPUSER      BASIS1       IDCSAPBIW                    

SAPKB70110           BI7.ALL A 0008 20130709032248 SAPUSER      BASIS1       IDCSAPBIW                    

SAPKB70111           BI7.ALL A 0008 20130709032248 SAPUSER      BASIS1       IDCSAPBIW                    

SAPKB70112           BI7.ALL A 0008 20130709032248 SAPUSER      BASIS1       IDCSAPBIW                    

SAPKA70106           BI7.ALL A 0004 20130709034046 SAPUSER      BASIS1       IDCSAPBIW                    

SAPKA70107           BI7.ALL A 0004 20130709034046 SAPUSER      BASIS1       IDCSAPBIW                    

SAPKA70108           BI7.ALL A 0004 20130709034046 SAPUSER      BASIS1       IDCSAPBIW                    

SAPKA70109           BI7.ALL A 0004 20130709034046 SAPUSER      BASIS1       IDCSAPBIW                    

SAPKA70110           BI7.ALL A 0004 20130709034046 SAPUSER      BASIS1       IDCSAPBIW                    

SAPKA70111           BI7.ALL A 0004 20130709034046 SAPUSER      BASIS1       IDCSAPBIW                    

SAPKA70112           BI7.ALL A 0004 20130709034046 SAPUSER      BASIS1       IDCSAPBIW                    

SAPKB70106           BI7.ALL A 0004 20130709034046 SAPUSER      BASIS1       IDCSAPBIW                    

SAPKB70107           BI7.ALL A 0004 20130709034046 SAPUSER      BASIS1       IDCSAPBIW                    

SAPKB70108           BI7.ALL A 0004 20130709034046 SAPUSER      BASIS1       IDCSAPBIW                    

SAPKB70109           BI7.ALL A 0004 20130709034046 SAPUSER      BASIS1       IDCSAPBIW                    

SAPKB70110           BI7.ALL A 0004 20130709034046 SAPUSER      BASIS1       IDCSAPBIW                    

SAPKB70111           BI7.ALL A 0004 20130709034046 SAPUSER      BASIS1       IDCSAPBIW                    

SAPKB70112           BI7.ALL A 0004 20130709034046 SAPUSER      BASIS1       IDCSAPBIW                    

ALL                  BI7.ALL S 0000 20130709034158              BASIS1       IDCSAPBIW 20130709034049747  

ALL                  BI7.ALL N 0004 20130709034226              BASIS1       IDCSAPBIW 20130709034049747  

ALL                  BI7.ALL 6 0004 20130709034805              BASIS1       IDCSAPBIW 20130709034049747

A LOG

APServiceBI7 20130709034049 RFC: tp IMPORT all BI7 pf=\\IDCSAPBIW\sapmnt\trans\bin\TP_DOMAIN_BI7.PFL -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems= -Dbuffreset=yes -Dmainimp_proc=1 -Dwatchparallelprocesses=yes -Dparallel=0 -Dstopimmediately=1 -Dactivatemerged=yes -Dcheckmasterlang=no tag=spam -Dtransdir=\\IDCSAPBIW\sapmnt\trans  (pid=5648)

[Former Member]

Hi Raz,

           You will get short dumps when you doing upgrade of Basis and ABAP patches and in between try to execute some tcodes , if the phase is still running let it run , after completion of patch everything will come back to normal.

Thanks and Regards,

Kunal Gahlot

[Manas_Vincit]

Hi Raz,

Check in database , if there was same error . In DB2 database soemtime Patch upgrade cause Log space full condition . As it import has taken too much time , check how many tp process running , cancel those and import Basis pacakge again . incase you are not able to do from SAP , run it from OS level . till Basis import will not complete you will get those ABAP Dumps ?

Also go thorugh SAP notes thorougly for any known issues and facts .

Thanks

Manas Behra

[Former Member]

Hi Raz,

There are lots of sensible suggestions here.  Check the DB space first and make sure that you have a good backup before you try the next stage (I'm guessing you had a good one before you started the SPAM application).

We've all had this at some time or other and you are going to need to be courageous and probably do what Deepak Kori says above.  When all the tps are killed, do see if you can update tp and R3trans to the latest version first though as Regan says as that always helps.

all the best!

Graham

[Former Member]

Hi,

Did you check SM21 logs . Can you check that database has free table space.

Thanks

Rishi Abrol

[Former Member]

Hi Raz,

I'm not sure if you saw this thread below, but the symptoms look very similar to your situation. It looks as though you may need to log a call with SAP:

http://scn.sap.com/thread/723326

Their issue appear to be caused by a DB shutdown during the import.

Kind regards.

Rich

[Former Member]

Hi Richard,

Thanks for thread,it is very helpful message for me... Im currently checking on that....thanks

[Former Member]

Hi Rcihard ,

Thanks again, I havent seen the thread you provided me. after seeing the thread i got to know the same situation happened over there, so i used those steps. It worked for sometime n again strucked at below phase....

[Former Member]

Hi Raz,

What is the error in the log file now? Check the /Upgrade/log directory and the /Upgrade/tmp as well..

Thanks and kind regards.

Rich

[former_member185239]

Hi Raz,

Few points to check at os level

Goto the directory /usr/sap/trans/tmp

1. In this directory , check files are getting updated or not.

2. At os level pleasw check any process are running for tp or not.

      If running then let them run , it will become fine after few 2 hours(approx).

Please let me know.

With Regards

Ashutosh Chaturvedi

[Former Member]

Hi Ashutosh Chaturvedi,

Thanks for your reply, no files are updating at os level. usr/sap/trans/tmp also not getting update.

and Tpis running fine, and still its completed morethan 24 hrs, i never faced this issue before.

these are found in stms...

Regards

Raz

[former_member188883]

Hi Raz,

As I understand no logs being updated, request you to take SAP restart. Ensure all the tp processes are stopped.

Start SAP and then restart patch application.

Hope this helps.

Regards,

Deepak Kori

[Former Member]

Hi Raz,

Dumps are common while importing SP's.

In which mode your are trying to Run import.

Give a try to start import again in both Dialog and BG mode once, If issue still persists then paste the logs or screens.

Regards,

Ravi

[Former Member]

Hi screens shared as above, still the problem persists.

Logs

SLOG

START MAIN IMPORT          BI7 I      20130716045052              bi7adm       IDCSAPBIW 201307160450510001c0

STOP  MAIN IMPORT          BI7 I      20130716051746              bi7adm       IDCSAPBIW 201307160450510001c0

START MAIN IMPORT          BI7 I      20130716054405              bi7adm        01307160544040016a4

STOP  MAIN IMPORT          BI7 I      20130716054704              bi7adm     

201307160544040016a4

START MAIN IMPORT          BI7 I      20130716054752              bi7adm     

201307160547510002b4

STOP  MAIN IMPORT             20130716061153                  201307160547510002b4

START MAIN IMPORT              20130716062033                  2013071606203300118c

STOP  MAIN IMPORT          20130716064402               2013071606203300118c

START MAIN IMPORT              20130716065112                 20130716065112001300

STOP  MAIN IMPORT             20130716065429                20130716065112001300

[Former Member]

Hi Please find below screenshots n logs regarding the same issue....thanks

ULOG:

SIDadm       20130716054404    : tp r3i SAPKA70111 SID pf=/usr/sap/trans/bin/TP_DOMAIN_BI7.PFL tag=spam -Dclientcascade=yes -Drepeatonerror=8  (pid=5796)

SIDadm       20130716054751    : tp r3i SAPKB70111 SID pf=/usr/sap/trans/bin/TP_DOMAIN_BI7.PFL tag=spam -Dclientcascade=yes -Drepeatonerror=8  (pid=692)

SIDadm       20130716062033    : tp r3i SAPKB70112 SID pf=/usr/sap/trans/bin/TP_DOMAIN_BI7.PFL tag=spam -Dclientcascade=yes -Drepeatonerror=8  (pid=4492)

SIDadm       20130716065112    : tp r3i SAPKA70112 SID pf=/usr/sap/trans/bin/TP_DOMAIN_BI7.PFL tag=spam -Dclientcascade=yes -Drepeatonerror=8  (pid=4864)

[Reagan]

Hello

There are no errors in the screen shots and logs you have provided.

Transport ending with 0004 is not an error . It is just a warning.

Regards

RB

[Former Member]

Hi Raz,

As Reagan mentioned, the return code 4 is just a warning. I cannot see the first two screenshots you pasted above.

There should be a log file which contains a specific error..

Kind regards.

Rich

[Former Member]

Hi Pls find above screenshots that are not visible bfore.... the spam has been strucked at IMPORT_PROPER PHASE and showing in screen error stop in spam status.....

Thanks everyone for your kind information.....its very helped me to get solve some issues through, as i followed Richard Mackrill thread...thank you

Regards

Raz

[former_member227600]

Hi,

Have you got any abap dump if yes than please check if this is happening in any FM our program and also please provide logs of TMP/logs as siad in above posts.

Regards

Ram

[Reagan]

Hello

Have you tried with a newer version of TP and R3trans ?

Regards

RB

[Former Member]

Hi Raz,

Can you take a look at the transport log for the imports to see if you can identify the error more accurately?

Regards,

Graham

[Former Member]

Hi Graham,

Thanks for your quick reply.

Yes i got error before in the phase of DDIC_IMPORT and i corrected that error. now again spam strucked at IMPORT_PROPER (--> MAIN_IMPORT). no logs are writing at os level. what ever T-code im entering getting the abap below dump. 

Runtime Errors         SYNTAX_ERROR

Date and Time          10.07.2013 21:31:34

Short text

     Syntax error in program "CL_GUI_ALV_GRID===============CP ".

What happened?

     Error in the ABAP Application Program

     The current ABAP program "RSSHOWRABAX" had to be terminated because it has

     come across a statement that unfortunately cannot be executed.

     The following syntax error occurred in program

      "CL_GUI_ALV_GRID===============CP " in include

      "CL_SALV_EX_MODEL_TABLE========CU " in

     line 126:

     "Method "IF_SALV_BS_MODEL_FIELD~GET_DECIMALS" is not declared or inheri"

     "ted in class "CL_SALV_EX_MODEL_TABLE". -"

     " "

     " "

     The include has been created and last changed by:

     Created by: "SAP "

     Last changed by: "SAP "

     Error in the ABAP Application Program

     The current ABAP program "RSSHOWRABAX" had to be terminated because it has

     come across a statement that unfortunately cannot be executed.

Error analysis

     The following syntax error was found in the program

Error analysis

    The following syntax error was found in the program

     CL_GUI_ALV_GRID===============CP :

    "Method "IF_SALV_BS_MODEL_FIELD~GET_DECIMALS" is not declared or inheri"

    "ted in class "CL_SALV_EX_MODEL_TABLE". -"

    " "

    " "

Trigger Location of Runtime Error

    Program                                 RSSHOWRABAX

    Include                                 RSSHOWRABAX_100

    Row                                     20

    Module type                             (MODULE PBO)

    Module Name                             BUILD_ALV

Source Code Extract

Line  SourceCde

    1 *----------------------------------------------------------------------*

    2 ***INCLUDE RSSHOWRABAX_100 .

    3 *----------------------------------------------------------------------*

    4 *&---------------------------------------------------------------------*

    5 *&      Module  STATUS_0100  OUTPUT

    6 *&---------------------------------------------------------------------*

    7 *       text

    8 *----------------------------------------------------------------------*

    9 module status_0100 output.

   10   set pf-status 'ALV100'.

   11   set titlebar 'ALV100'.

12

13 endmodule.                             " STATUS_0100  OUTPUT

14

15 *&---------------------------------------------------------------------*

16 *&      Module  build_alv  OUTPUT

17 *&---------------------------------------------------------------------*

18 *       text

19 *----------------------------------------------------------------------*

>> module build_alv output.

21

22   g_repid = sy-repid.

23

24

25 *** three "constants":

26

27 *** get_alv_from_buffer = select SNAP_BEG and fill gt_snap with new

28 ***                       values. Necesary after REFRESH and BACK to

29 ***                       Selection screen

30

31 *** custom_container1 = Create the objekts for container and alv.

32 ***                     Only necessary 1 time during the program

33 ***                     running

34

35 *** get_alv_content_from_buffer = refresh the ALV grid

36

37

38 ***************************************************

39 ******* SELECT DUMPS FROM SNAP_BEG AND FILL GT_SNAP

Regards

Raz

[Former Member]

Hello Raz,

Can you specifically point it out in phase it is stuck. I guess IMPORT PROPER.

If your upgrade is in import proper it common to get dumps specifically while upgrading base Netweaver components ie. SAP_BASIS.

Please monitor the import from OS level

>> tp is running or not

>>check tp sys logs

>> tmp/log are updating properly or not

As per my experience its running properly.

Regards,

Surojit

[Former Member]

Hi Surojit Guha,

Thanks for your quick reply ,

Yes it is Import Proper Phase in that phase MAIN IMPORT step was strucked itself.

Yes, its running properly. but no logs are writing at os lvl. ..... still not problem not solved.

Kernel Version is 721 and Patch level is 100 in my present System.

Regards

Raz