SAP Basis 731 patching

[Former Member]

Hello All,

We have installed a SAP SCM 7 and after that we are trying to patch it.

During which we are facing a problem in SAP BASIS 731 01 to 07.

Whenever we try to logon to the system to check the status, then we are unable to do so and we can't execute any t-codes.

Category               ABAP Programming Error

Runtime Errors         SYNTAX_ERROR

ABAP Program           SAPLSTRD

Application Component  BC-CTS-ORG

Date and Time          30.05.2013 14:38:14

Short text

     Syntax error in program "SAPLSTRD ".

What happened?

     Error in the ABAP Application Program

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

     come across a statement that unfortunately cannot be executed.

     The following syntax error occurred in program "SAPLSTRD " in include "LSTRDU50

      " in

     line 5036:

     "The data object "IS_API_CALL" does not have a component called "NO_DBC"

     "OMMIT"."

     " "

     " "

     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 "SAPLSCTS_TRDIR" had to be terminated because it has

     come across a statement that unfortunately cannot be executed.

Please let us know, if you have ever come across this problem. And were you able to over come it ? If yes, Please let us know.

Thanks & Regards,

Ananda Swaroop G K

[Former Member · Accepted solution]

Hi Ananda,

Please try the steps here:

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

Thanks.

Best Regards,

Anita

[Former Member]

Hello All,

We were able to resolve the issue, after following the below workaround.

Our Scenario is

OS - Windows 2008 R2 Std

DB - Oracle 11.2.0.3

In this situation, if you ever try to patch your new installation system (SAP NW 7.31). Then you will end up with above issue (See my original post).

01. Please change the Oracle parameter " _use_zero_copy_io=false " . As per " SAP Note 1635605 CLIENT HANGS ON INSERT INTO TABLE WITH SECUREFILE LOB "

02. If your tp and R3trans are not reconnecting then, kill them.

03. Empty /usr/sap/trans/tmp folder.

04. Restart command (tp r3i .....) at OS level.

This was true to our scenario, please be careful or check with SAP before using this workaround in your landscape.

Thanks & Regards,

Ananda Swaroop G K

[Former Member]

Hi Swaroop,

I am at same level now  but i am not able to restart spam through tp from os level .

OS command i tried   

tp r3i SAPKD73101 EN1 pf=\\drcismx1\sapmnt\trans\bin\TP_DOMAIN_EN1.PFL

am getting message No valid entry found for SAPKD73101

i am checking buffer showing message SAPKD73101 will not be imported because it is already in system

still not able to login to sap system . other than this have you done any thing.

It will be greate help if you share your experience

thanks

Shashikiran

[former_member144433]

Hi Shashi,

I think u have issued wrong tp R3i command in the system. SAPKD731* is the SPAM\SAINT update package. If you are importing basis support packages then it should be SAPKB73101. Please do not issue wrong tp R3i commands in the system as it will damage the system.

Please always check the consistency of the buffer using the command specified below.

tp SHOWBUFFER SID tp= < transport profile > tag=SPAM

The above command should show the correct status of the queue as per the logs and should end with the return code 0000.

With out consistent buffer, it is never possible to continue the import either from SPAM or OS level.

Please DO NOT issue tp R3i command in the system with out proper checking as it will damage the system and it will not be possible to fix the inconsistency and system restore would be required.

Thank You.

Regards,

Deepika

[Former Member]

Hello Shashikiran,

Sorry for the delay response.

You need to move all the contents of /usr/sap/trans/log and tmp folder to other location.

In your log folder, you will find file similare to this " ULOG13_2 ". You will be able to find the correct command.

Thanks & Regards,

Ananda Swaroop G K

[Former Member]

Dear Ananda,

Good that your issue is resolved, i found the convinient way to resolve this...

Start the SPAM in front end it will ask you to apply a prerequisite note :-  0001680583 Field names for tables and views with more than 16 char....

once the note is applied repeate the SPAM it will work...

If your not able to login to system itself... restore the last back up and repeat the SPMA again....

Hope this will help some one to get the issue resolved

Regards

Amar Ghuge

[Former Member]

Hi,

Have you sorted out the issue?

Did the recommended command help you ?

Based on above logs, please check http://scn.sap.com/thread/831105 thread for "IS_API_CALL" does not have a component called "NO_DBCOMMIT" error:-

Nilutpal.

[Former Member]

Hello,

i have got once basis patching crashed. Following article helped me to finish it from commandline:

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

[Former Member]

Hello George,

I tried to follow the link and used the below tp command

tp r3i SAPKB73101 <SID> pf=D:\usr\sap\trans\bin\TP_DOMAIN_<SID>.PFL tag=spam -Dclientcascade=yes -Drepeatonerror=8

But still it is hanging and when I check the developer trace file of dialog work process, then, I see the below log

ABAP Program SAPLSCTS_TRDIR                          .

A  Source LSCTS_TRDIRU01                           Line 24.

A  Error Code SYNTAX_ERROR.

A  Module  $Id: //bas/721_REL/src/krn/runt/abgen.c#4 $ SAP.

A  Function ab_genprog Line 1850.

A  ** RABAX: level LEV_RX_STDERR completed.

A  ** RABAX: level LEV_RX_RFC_ERROR entered.

A  ** RABAX: level LEV_RX_RFC_ERROR completed.

A  ** RABAX: level LEV_RX_RFC_CLOSE entered.

A  ** RABAX: level LEV_RX_RFC_CLOSE completed.

A  ** RABAX: level LEV_RX_IMC_ERROR entered.

A  ** RABAX: level LEV_RX_IMC_ERROR completed.

A  ** RABAX: level LEV_RX_DATASET_CLOSE entered.

A  ** RABAX: level LEV_RX_DATASET_CLOSE completed.

A  ** RABAX: level LEV_RX_ERROR_SAVE entered.

A  ** RABAX: level LEV_RX_ERROR_SAVE completed.

A  ** RABAX: level LEV_RX_ERROR_TPDA entered.

A  ** RABAX: level LEV_RX_ERROR_TPDA completed.

A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.

A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.

A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.

A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.

A  ** RABAX: level LEV_RX_END entered.

A  ** RABAX: level LEV_RX_END completed.

A  ** RABAX: end no http/smtp

A  ** RABAX: end RX_BTCHLOG|RX_VBLOG

A  Syntax error in program SAPLSTRD                                ..

A 

M  *** WARNING => PfStatWrite: missing STAT_END for opcode STAT_GENERATE [pfxxstat.c   5033]

M  {root-id=0015C58765DE1EE2B2B6C3679BD5AAAF}_{conn-id=00000000000000000000000000000000}_0

A 

A Fri May 31 11:22:16 2013

A  *GENER* request remote generation: SAPMSSY2.

A 

A Fri May 31 11:22:20 2013

A  *GENER* starting inline generation: SAPMSSY2 (reason: no process available for remote generation).

A 

A Fri May 31 11:22:21 2013

A  *GENER* starting inline generation: SAPLSTRD (reason: already local generations within LUW).

A 

A Fri May 31 11:22:22 2013

A  *** ERROR => Syntax error in program SAPLSTRD                                 [abgen.c      1816]

A  {root-id=0015C58765DE1EE2B2B6C7E04509AAAF}_{conn-id=00000000000000000000000000000000}_0

A  *** ERROR => > Include LSTRDU50                                 line 5036 [abgen.c      1818]

A  {root-id=0015C58765DE1EE2B2B6C7E04509AAAF}_{conn-id=00000000000000000000000000000000}_0

A  *** ERROR => > The data object "IS_API_CALL" does not have a component called "NO_DBCOMMIT". [abgen.c      1820]

A  {root-id=0015C58765DE1EE2B2B6C7E04509AAAF}_{conn-id=00000000000000000000000000000000}_0

A  TH VERBOSE LEVEL FULL

A  ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.

A  ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.

A  ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.

A  ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.

A  ** RABAX: level LEV_RX_HOTSPOT_TRACE entered.

A  ** RABAX: level LEV_RX_HOTSPOT_TRACE completed.

A  ** RABAX: level LEV_RX_SAVE_SHMLOCKS entered.

A  ** RABAX: level LEV_RX_SAVE_SHMLOCKS completed.

A  ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.

A  ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.

A  ** RABAX: level LEV_RX_ROLLBACK entered.

A  ** RABAX: level LEV_RX_ROLLBACK completed.

A  ** RABAX: level LEV_RX_DB_ALIVE entered.

A  ** RABAX: level LEV_RX_DB_ALIVE completed.

A  ** RABAX: level LEV_RX_HOOKS entered.

A  ** RABAX: level LEV_RX_HOOKS completed.

A  ** RABAX: level LEV_RX_STANDARD entered.

A  ** RABAX: level LEV_RX_STANDARD completed.

A  ** RABAX: level LEV_RX_STOR_VALUES entered.

A  ** RABAX: level LEV_RX_STOR_VALUES completed.

A  ** RABAX: level LEV_RX_C_STACK entered.

A  ** RABAX: level LEV_RX_C_STACK completed.

A  ** RABAX: level LEV_RX_MEMO_CHECK entered.

A  ** RABAX: level LEV_RX_MEMO_CHECK completed.

A  ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.

A  ** RABAX: level LEV_RX_AFTER_MEMO_CHECK completed.

A  ** RABAX: level LEV_RX_INTERFACES entered.

A  ** RABAX: level LEV_RX_INTERFACES completed.

A  ** RABAX: level LEV_RX_GET_MESS entered.

A  ** RABAX: level LEV_RX_GET_MESS completed.

A  ** RABAX: level LEV_RX_INIT_SNAP entered.

A  ** RABAX: level LEV_RX_INIT_SNAP completed.

A  ** RABAX: level LEV_RX_WRITE_SYSLOG entered.

A  ** RABAX: level LEV_RX_WRITE_SYSLOG completed.

A  ** RABAX: level LEV_RX_WRITE_SNAP_BEG entered.

A  ** RABAX: level LEV_RX_WRITE_SNAP_BEG completed.

A  ** RABAX: level LEV_RX_WRITE_SNAP entered.

A 

A Fri May 31 11:22:23 2013

A  *GENER* request remote generation: IF_SCV_GEN_METADATA===========IP.

Thanks & Regards,

Ananda Swaroop G K

[Former Member]

Hello Ananda,

Sorry to hear that, it does not look good. Probably time to restore from backup.

Regards

George

[Former Member]

Hi Ananda,

Kindly check the following things to sort out the issue:-

1. Have you found any issue in SICK after completion of installation ?

2. For SAP_BASIS 731 Level *, you should use EXT version of kernel (720).

3. Is SPAM level up to dated ?

Please check the action logs in OS level.

Regards,

Nilutpal

[Former Member]

Hello Nilutpal,

Yes, we installed latest kernel 721_EXT and we also updated the SPAM to the latest level.

Thanks & Regards,

Ananda Swaroop G K

[Former Member]

Hi Ananda,

Thanks for your update.

If you can't login into your system itself due the above mentioned issue, please try out following command for TP profile in bin directory :-

tp r3i SAPKDxxxx <SID> pf=/usr/sap/trans/bin/<transportprofile>

where SAPKDxxxx is the SPAM import number (e. g. BASIS patch 07 for 731 would be KD73107) as user sidadm.

It may ended with return code 04, still you can proceed to log into the system.

Please let me once you perform the same.

In case you are doing it in PRD server, then I would recommend to raise an OSS message in parallel.

Regards,

Nilutpal.

[Former Member]

Hello Ananda,

During the process you cannot log in, when BASIS component is being patched.

for NW 7.31 you need to apply following notes

before applying the Support packages.

1614802 "Mass activation hangs during INSERT in the table DDFTX" 

1680583 "Field names for tables and views with more than 16 char." 

1678047 "COMPUTE_INT_PLUS_OVERFLOW during activation" 

1672480 "Runtime error COMPUTE_INT_PLUS_OVERFLOW in RADIXCHK"

Did you have them applied? How long your patching runs?

[Former Member]

Hello George,

Before starting the patching, we have followed " 1597765 - Known problems with Support Packages in SAP NW 7.31 AS ABAP " and implemented all mentioned notes.

Patching was running fine for about more than 02 hours until it reached " Import_Proper " phase.

Until, then, we were monitoring it and we were able to see the changes in file size under        

" /usr/sap/trans/tmp and log folders "

We waited for about more than 06 hours before raising it as a question here.

Thanks & Regards,

Ananda Swaroop G K

[magexposito]

Hello Ananda,

Sometimes when you are doing a Basis SP upgrade the SYNTAX_ERROR dump appears when you try to log-in the system or execute any transaction. In these cases the only solution is to wait until the import queue has finished and then log-in in the system to check if the dumps still appears.

Anyway you can check the current situation of every SP import and the queue status in the following directories:

/usr/sap/trans/tmp

/usr/sap/trans/log

Check over there the files that have been modify recently.

Best regards.

[Former Member]

Hello Miguel,

Nothing is getting updated in /usr/sap/trans/tmp and log folder. We have waited almost 06 hours.

Nothing is happening and since, we were running it as background the status of which is "Stopped"

We tried to search for notes in SAP Market Place, but we couldn't find any relevant SAP Note.

Thanks & Regards,

Ananda Swaroop G K