cancel
Showing results for 
Search instead for 
Did you mean: 

SAPKB70012 patch struck in IMPORT_PROPER

Former Member
0 Kudos

Hi All,

I have a SAP SCM 5.0 system with BI.

I applied one single SAP Basis Support Package (SAPKB70012) overnight. In the morning saw that its struck in IMPORT_PROPER. The current action showing is QUEUE IMPORT. I started the SP again from that point and its continuing with "imp_all" for the last two days.

I am sure, the installation is not happening but the SPAM status shows "imp_all". I stopped and started again..But again its in that phase "imp all" still going on.

The Transport log show return code 12.

Please see the Transport Log below

REP System REP

Generate Transport Information File 15.12.2008 20:43:02 (0) Successfully Comple

Import Request Piece List 15.12.2008 20:44:48 (4) Ended with Warning

Test Import 15.12.2008 20:46:42 (4) Ended with Warning

Import ABAP Dictionary Objects 15.12.2008 21:07:17 (4) Ended with Warning

ABAP Dictionary Activation 15.12.2008 21:28:02 (4) Ended with Warning

Import 15.12.2008 22:29:10 (12) Canceled

Import steps not specific to transport request

Please see the Error Log also

Main import

Tansport request : SAPKB70012

System : REP

tp path : tp

Version and release: 370.00.01 700

sap_dext called with msgnr 1:

-


db call info -


function: db_setget

fcode: RT_GET

tabname: ALMONISETS

len (char): 28

key: MSSAP CCMS Monitor Templates

ok fetches: 0

last entry:

retcode: 1

SQL error 3106 accessing : ORA-03106: fatal two-task communication protocol e

Main import

End date and time : 20081215222910

Ended with return code: ===> 12 <===

Please advice what to do?

Regards,

Jitender

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Are you on a MS SQL system? We had this happen on a MS SQL system when we brought SP12 in as the last SP in the stack. We fixed it by following some of the instructions in this [Note 1042435 - SAPSQL_SUBQUERY_ILL_TABLE_TYPE in SDB1FMSS, Form exists_data|https://service.sap.com/sap/support/notes/1042435].

Hope that helps.

J. Haynes

Former Member
0 Kudos

Hi All,

Sorry for late reply.

SAP have suggested to upgarde the database from 10.2.0.1 to 10.2.0.2. After that I have to apply a patch which solves the ORA 3601 problem.

Will update you all once I complete

Regards,

Jitender

Former Member
0 Kudos

Hi Jitender,

There is a seperate note for this error (Note No. 1011262).

But as per my personal experience this patch will not import, the only way is to restore the system from your backup.

Thanks,

Venumanohar

Former Member
0 Kudos

Hi Jitender,

Please check this note.

Note 822379 - Known problems with Support Packages in SAP NW 7.0x AS ABAP

Thanks,

Mano

Former Member
0 Kudos

Hi Venu,

Please check the note (1011262) once more. I don't see any relevance to this problem.

I might be wrong. Can you please clarify.

Regards,

Jitender

Former Member
0 Kudos

Venu,

I have checked the note (822379 - Known problems with Support Packages in SAP NW 7.0x AS ABAP) also. Nothing there.

The problem which I can see in the SLOG

WARNING: Background job RDDIMPDP could not be started or terminated abnormally.

Please check that the R/3 system is running.

Please check the system. Use transactions SM21, SM37, SM50.

WARNING: (This warning is harmless if no further warnings follow.)

sapretail:repadm>

Can I schedule RDDIMPDP at OS level. Reason, it gives dump when i try to open se37.

Moreover SAP Suggested me to upgrade the database to 10.2.0.2 and apply the interim patch which solves the ORA 3601 problem. But after this also. I am not able to apply the patch

Regards,

Jitender

Edited by: Jitender Dugar on Jan 2, 2009 5:37 PM

Former Member
0 Kudos

1. Pls make sure that you have NOT made any change to import

buffer. try to use the command to verify

tp showbuffer <SID> tag=spam pf=<full path to transport profile>

2. Check at OS level to see if there is any tp or R3trans still

running; if yes, pls terminate it.

3. Pls issue the following tp command to manully import the package:

tp r3i SAPKB64016 <SID> pf=<full path of the transport profile>

tag=spam -Dclientcascade=yes -Drepeatonerror=8

The return code for this tp call must be 0 or 4.

4. After this you should be able to logon to the system as normal

and you MUST continue and finish the remaining steps after the

import from SPAM. Check queue and confirm after SPAM finishes.

The above 4 stpes resolved my problem.

Answers (3)

Answers (3)

Former Member
0 Kudos

Can be tried with recommendation from SAP

Former Member
0 Kudos

Hi,

As error is of Rc-12, so need to check from your system end, what is the exact problem.

Also in your logs it is mentioned "Import steps not specific to transport request", just check, whether are you using correct version of SP.

If possible, download again and use that .

JPReyes
Active Contributor
0 Kudos

check the status of the SP on the import monitor in STMS if necesary cancel and try to import the SP again, also read the SP Note for known issues

Regards

Juan