cancel
Showing results for 
Search instead for 
Did you mean: 

error in Basis patch 6 for PI 7.10

Former Member
0 Kudos

Hello Experts,

We are implementing Basis 6 patch in PI 7.1 System. It has terminated with return code 12. Now we are not able to start it again as are getting SYNTAX_ERROR dump. Nothing can be done!

Following is the log at the point of termination:

4 ETW000 [dbrepo ,00000] ***LOG BY4=>sql error 60 performing UPD on table REPOSRC

4 ETW000 41 1088.769817

4 ETW000 [dbrepo ,00000] ***LOG BY0=>ORA-00060: deadlock detected while waiting for resource

4 ETW000 28 1088.769845

2EETW000 sap_dext called with msgnr "1":

2EETW000 -


db call info -


2EETW000 function: db_report_interface

2EETW000 fcode: OPEN_LINE_UPDATE

2EETW000 tabname: SOURCE

2EETW000 len (char): 40

2EETW000 key: RSALEXTI

2EETW000 retcode: 1

2EETW125 SQL error "60" during "" access: "ORA-00060: deadlock detected while waiting for resource"

1 ETP154 MAIN IMPORT

1 ETP110 end date and time : "20081120221717"

1 ETP111 exit code : "12"

1 ETP199 ######################################

Thanks,

Antarpreet

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

Try reset the queue by using the following steps.

Execute SE37 and use the function module OCS_RESET_QUEUE -> Single Test

with the parameters IV_TOOL=SPAM, IV_FORCE=X

Deleted all the files from \usr\sap\trans\tmp.

Kill all the tp processes running

Scheduled the program RDDIMPDP using Report RDDNEWPP in SE38

PS: Try this at your own risk

Former Member
0 Kudos

Hello Antarpreet,

I have the same problem.

Please let me know if you have get an answer from SAP to solve it.

Thanks a lot.

Kind Regards,

Mischa

Former Member
0 Kudos

Hi All,

One update: the struckup phase is IMPORT_PROPER!

Thank You,

Antarpreet

Former Member
0 Kudos

Got the same error and after than SPAM would give dump. Had to execute the patch from OS using tp.

Before doing that :-

1. Kill all running tp and R3trans processes (if any).

2. Empty table TRBAT and TRJOB using SM31 (if not possible then from SQL level) if there be any entries in them.

3) Make sure you have a full backup.

After the import finsihed successfully I had to import again from SPAM because SPAM didn't

recognize those patches already imported. It looked like synchronizing any tables not updated by manual import.

Hope this helps.

Thanks,

Naveed

Former Member
0 Kudos

Hello Naveed,

All this have been done butof no use!

We are facing syntax errors in starting SPAM......

How to rectify this?

Thanks Again!

Antarpreet

Former Member
0 Kudos

"All this has been done" mean you have tried to import from OS usig tp command and once the import has finsihed, SPAM is still giving dump ?

This is the command that I used :

tp r3i SAPKB71005 <SID> pf=<Path to the transport profile> tag=spam -Dclientcascade=yes -Drepeatonerror=8

Hope this helps.

Thanks,

Naveed

Edited by: Naveed Qureshi on Nov 21, 2008 9:51 AM

Former Member
0 Kudos

Do not use "tp r3i" command without SAP recommendation!! SAP will not support the system anymore if you use it without their recommendation.

Please refer to the following posts:

I would suggest you open a message with SAP.

Cheers,

Jazz