cancel
Showing results for 
Search instead for 
Did you mean: 

Problem installing EHP1 on Solution Manager

Former Member
0 Kudos

Hello out there,

we had a problem when installing EHP 1 on Solution Manager, which forced us to do a restore. When installin EHP1 on Solution Manager with Transacation SAINT, Transaction was aborted.

When we called SAINT again, we always got a dump.

On Operating system we got following messages:

SLOG

INFO: event SAP_IMPORT_START triggered successfully

START DD IMPORT SM2 H 20090521200505 CLAULENG SDBDN510 20090521200504888

STOP DD IMPORT SM2 H 20090521200505 CLAULENG SDBDN510 20090521200504888

START DISTRIBUTION OF DD-O SM2 S 20090521200505 CLAULENG SDBDN510 20090521200504888

START tp_getprots SM2 S 20090521200505 CLAULENG SDBDN510 20090521200504888

STOP tp_getprots SM2 S 20090521200851 CLAULENG SDBDN510 20090521200504888

STOP DISTRIBUTION OF DD-O SM2 S 20090521200851 CLAULENG SDBDN510 20090521200504888

START TBATG CONVERSION OF SM2 N 20090521200851 CLAULENG SDBDN510 20090521200504888

START tp_getprots SM2 N 20090521200851 CLAULENG SDBDN510 20090521200504888

STOP tp_getprots SM2 N 20090521200906 CLAULENG SDBDN510 20090521200504888

STOP TBATG CONVERSION OF SM2 N 20090521200906 CLAULENG SDBDN510 20090521200504888

START MOVE NAMETABS SM2 6 20090521200906 CLAULENG SDBDN510 20090521200504888

START tp_getprots SM2 P 20090521200906 CLAULENG SDBDN510 20090521200504888

STOP tp_getprots SM2 P 20090521204640 CLAULENG SDBDN510 20090521200504888

STOP MOVE NAMETABS SM2 6 20090521204640 CLAULENG SDBDN510 20090521200504888

START MAIN IMPORT SM2 I 20090521204640 CLAULENG SDBDN510 20090521200504888

ERROR SAPK-701DRINSAPBASIS SM2 I 0012 20090521212038 SAPBASISUSER CLAULENG SDBDN510 20090521200504888

STOP MAIN IMPORT SM2 I 20090521220613 CLAULENG SDBDN510 20090521200504888

ERROR: stopping on error 12 during MAIN IMPORT

START INFORM SAP-SYSTEM OF SM2 Q 20090521220613 CLAULENG SDBDN510 20090521200504888

START tp_getprots SM2 Q 20090521220614 CLAULENG SDBDN510 20090521200504888

STOP tp_getprots SM2 Q 20090521220629 CLAULENG SDBDN510 20090521200504888

STOP INFORM SAP-SYSTEM OF SM2 Q 20090521220629 CLAULENG SDBDN510 20090521200504888

STOP imp all SM2 0012 20090521220629 CLAULENG SDBDN510 20090521200504888

HALT 20090522035249

SLOG

SAPK-701DMINSAPBASIS SM2.ALL I 0000 20090521211758 SAPBASISUSER CLAULENG SDBDN510 20090521200504888

SAPK-701DXINSAPBASIS SM2.ALL I 0000 20090521211759 SAPBASISUSER CLAULENG SDBDN510 20090521200504888

SAPK-701DKINSAPBASIS SM2.ALL I 0000 20090521211809 SAPBASISUSER CLAULENG SDBDN510 20090521200504888

SAPK-701DTINSAPBASIS SM2.ALL I 0004 20090521211954 SAPBASISUSER CLAULENG SDBDN510 20090521200504888

SAPK-701DRINSAPBASIS SM2.ALL I 0012 20090521212038 SAPBASISUSER CLAULENG SDBDN510 20090521200504888

SAPK-701DDINSAPBASIS SM2.ALL I 0000 20090521212121 SAPBASISUSER CLAULENG SDBDN510 20090521200504888

SAPK-701DZINSAPBASIS SM2.ALL I 0004 20090521212145 SAPBASISUSER CLAULENG SDBDN510 20090521200504888

SAPK-701DWINSAPBASIS SM2.ALL I 0004 20090521212614 SAPBASISUSER CLAULENG SDBDN510 20090521200504888

SAPK-701DOINSAPBASIS SM2.ALL I 0004 20090521212653 SAPBASISUSER CLAULENG SDBDN510 20090521200504888

SAPK-701DFINSAPBASIS SM2.ALL I 0004 20090521220506 SAPBASISUSER CLAULENG SDBDN510 20090521200504888

ALL SM2.ALL Q 0000 20090521220624 CLAULENG SDBDN510 20090521200504888

Prococol of SAPK-701DRINSAPBASIS

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: CL_ABSTRACT_ENH_TOOL==========CI

2EETW000 retcode: 1

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

1 ETP154 MAIN IMPORT

1 ETP110 end date and time : "20090521212038"

1 ETP111 exit code : "12"

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

Can somebody help to avoid this problem next time?

Best Regards

Gerd Bühler

Accepted Solutions (0)

Answers (1)

Answers (1)

stephane_lamarche
Active Participant
0 Kudos

Did you find a solution to this?

Former Member
0 Kudos

Hello Stephane,

finally we succeeded in installing EHP1 on 2nd attempt. We still have no explanation for the problem we had the first time. After first unsuccessful attempt we tried to install EHP1 on a sandbox and it worked. On 2nd attempt on produktive system we hat no problems. What we did was locking all users. But whether this ist the reason for the first failure, we dont know.

Best Regards

Gerd