SAPKB70107 Error in step IMPORT_PROPER while applying SP Stack 26

[Former Member]

Hello All,

I'm applying the SP Stack 26 on our solman system(SAP EHP 1 for SAP Solution Manager 7.0; SP Stack originally 24; kernel 701, patch 97)

Step IMPORT_PROPER fails with the following message:

Error in phase: IMPORT_PROPER

Reason for error: TP_STEP_FAILURE

Return code: 0012

Error message: OCS Package SAPKB70107, tp step "I", return code

0012

If i check the log of SAPKB70107:

...

2EETW000 sap_dext called with msgnr "1":

2EETW000 -

---

db call info -

---

2EETW000 function: db_report_interface

2EETW000 fcode: CLOSE_LINE_MODE

2EETW000 tabname: SOURCE

2EETW000 len (char): 40

2EETW000 key: IF_HTTP_SERVER================IU

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 : "20110331115119"

1 ETP111 exit code : "12"

....

I have restarted SPAM a few times, but get the same syntax errors (also tried to start SPAM beeing on another hardware - from a dialog instance): Syntax error in programm "SAPLSUSM ".

Any ideas how to fix the error? Is it something wellknown?

Thanks,

Polina

[Former Member]

You can try reimporting the SP once again.

You can have a look at 822379 once.

Regards

Vivek

[Former Member]

Also you check in NOTES in case there are any known issues with this particular SP..

Regards,

[Former Member]

Hope below note helps you:

Note 84348 - Oracle deadlocks, ORA-00060

[Former Member]

Hi Rajneesh,

thanks for your reply.

I had a look at this note, but to tel lthe truth i don't have an idea, what should i change in my case:

(a cutout from the trace file)

• 2011-03-31 11:51:18.360

DEADLOCK DETECTED ( ORA-00060 )

[Transaction Deadlock]

The following deadlock is not an ORACLE error. It is a

deadlock due to user error in the design of an application

or from issuing incorrect ad-hoc SQL. The following

information may aid in determining the deadlock:

Deadlock graph:

-

---

Blocker(s)--

---

-

---

Waiter(s)--

---

Resource Name process session holds waits process session holds waits

TX-0008000f-00024b57 47 161 X 50 27 X

TX-00070007-0001d66a 50 27 X 47 161 X

session 161: DID 0001-002F-000002AC session 27: DID 0001-0032-00000002

session 27: DID 0001-0032-00000002 session 161: DID 0001-002F-000002AC

Rows waited on:

Session 161: obj - rowid = 00002632 - AAAMZ/AAFAAAe3zAAH

(dictionary objn - 9778, file - 5, block - 126451, slot - 7)

Session 27: obj - rowid = 00002632 - AAAMZ/AAFAAAe5NAAB

(dictionary objn - 9778, file - 5, block - 126541, slot - 1)

regards,

Polina

[Former Member]

Hi Vivek,

thanks for reply.

I have checked the note 822379, everything seems to be fine in my system. No notes have to be taken out before applying of the SP Stack. I have also tried to re-import the SPS again, but as i already mentioned, got syntax errors.

regards,

Polina

[Former Member]

Hello Polina

We had this issue of deadlock then we restarted the import which landed in sytanx error and we fixed it using the below mentioned note. We also encounted the activation issue too.

If you are getting the Syntax error then kindly have a look at 1281321.

Let me know if it fixes the issue.

When I had the DDIC_ACTIVATION issue I just changed the type using the note 1256384.

Regards

Vivek

[Former Member]

Hello, Was this ever resolved? I am getting the same exact error.

Thanks...

[sivakumar_kilari3]

Hi

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

This is a problem related to deadlock .you can check for DB lock objects in DB01 .

Refer to

Problem in DDIC ACTIVATION - note 71353

Thanks

Siva

[Former Member]

Hi,

This error ( TP_STEP_FAILURE: tp step CREATE_VERS_BEFORE could not be performed successfully. To find the exact cause of the error, choose Goto ® Log ® Queue, and look at the version log.

SPDD_SPAU_CHECK

In this phase, the system checks if a modification adjustment is necessary (transactions SPDD/SPAU).)

Hope this helps you..

Thanks,

George

[Former Member]

Hi george,

Thanks for your comments!

that doesn't sound really optimistic Unfortunately i can't really change to Goto ® Log ® Queue, when i do that i get my syntax error. Is this information seable somewhere in the logs on a OS level? (there are some of them in in /usr/sap/trans/log)

Actually i have already had the phase with SPDD and set all the modifications back to original, so no modifications were left in

an unchecked condition.

Thanks in advance,

Polina

[Former Member]

Hi ,

Check this thread on SDN

http://forums.sdn.sap.com/thread.jspa?threadID=969246

which tells problem might be with the tp and R3Trans?

Have you upgraded your kernel?

Thanks,

George

Edited by: george rayi on Mar 31, 2011 8:38 PM

[Former Member]

Hi George,

no, i haven't upgraded my kernel. But it's patch level is actually higher than those which will be delevered in the SP Stack, so i thought it might be ok. Now i do hope that a SAP consultant will have a look on a situation in the next 1.2 hrs. If not then i'll update the kernel to a newest one.

May be the problem also depends somehow on the fact that we have upgraded Oracle

on 11g not a long time ago?

Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit

Thanks & regards,

Polina