SAPKB70012 patch struck in IMPORT_PROPER

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

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

Similar Messages

Apply SAPKB70012 and SAPKB70012. i stick in IMPORT_Proper

Hi all ,
I am facing a major issue
when i apply Sp SAPKB70012 and SAPKB70012. i stick in IMPORT_Proper.
TO run report RDDNEWPP
when excet the sm37 or se38 its going to short Dump.
Have anybody faced this kind of issue ?
SLOG:
INFO: event SAP_IMPORT_START triggered successfully
INFO TBATG CONVERSION OF ACC N      not needed                  BASIS        oiam
WARNING: System ACC. Warning.        20090429203640 :
ERROR:       Background job RDDIMPDP is not scheduled. Please run report RDDNEWPP.
ERROR:       I'm waiting 100 sec (Count: 0).
WARNING:       (This warning is harmless if no further warnings follow.)
WARNING: System ACC. Warning.        20090429203821 :
ERROR:       Background job RDDIMPDP is not scheduled. Please run report RDDNEWPP.
ERROR:       I'm waiting 100 sec (Count: 1).
WARNING:       (This warning is harmless if no further warnings follow.)
WARNING: System ACC. Warning.        20090429204001 :
ERROR:       Background job RDDIMPDP is not scheduled. Please run report RDDNEWPP.
ERROR:       I'm waiting 100 sec (Count: 2).
WARNING:       (This warning is harmless if no further warnings follow.)
WARNING: System ACC. Warning.        20090429204141 :
ERROR:       Background job RDDIMPDP is not scheduled. Please run report RDDNEWPP.
ERROR:       I'm waiting 100 sec (Count: 3).
WARNING:       (This warning is harmless if no further warnings follow.)
WARNING: System ACC. Warning.        20090429204321 :
ERROR:       Background job RDDIMPDP is not scheduled. Please run report RDDNEWPP.
ERROR:       I'm waiting 100 sec (Count: 4).
WARNING:       (This warning is harmless if no further warnings follow.)
WARNING: System ACC. Warning.        20090429204502 :
ERROR:       Background job RDDIMPDP is not scheduled. Please run report RDDNEWPP.
ERROR:       I'm waiting 100 sec (Count: 5).
WARNING:       (This warning is harmless if no further warnings follow.)
WARNING: System ACC. Warning.        20090429204642 :
ERROR:       Background job RDDIMPDP is not scheduled. Please run report RDDNEWPP.
ERROR:       I'm waiting 100 sec (Count: 6).
WARNING:       (This warning is harmless if no further warnings follow.)
thanks for your help and support
keshava
Edited by: Juan Reyes on Apr 29, 2009 8:23 PM

Hello Keshava,
you will not be able to run the report I suppose,
but what you can do is run the support pack at OS level using tp command
. logon with root, then switch to sidadm:
su - sidadm
2. go to DIR_TRANS/bin (/usr/sap/trans/bin), run command:
tp R3I SAPKB70012 SID pf=TP_DOMAIN_SID.PFL -Dclientcascade=yes
-Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems= tag=SPAM
3. open another command window, monigor files under DIR_TRANS/tmp
file SAPKKB70012.SID & SAPIB70012.SID will be generated, and size of
SAPIB70012.SID will increase.
When tp command finished successfully, those two log files will disappear from DIR_TRANS/tmp
Goto DIR_TRANS/log to check SAPIB70012.SID, if return code is 0.
As long as it is 0, the manual import is successful, you will be able
to logon system via SAPGUI and call SPAM to continue the import.
otherwise it will be better to log a call with SAP
Rohit

SPAM version 36 is struck in import_proper phase of Prologue for crm rel700

Hi Gurus,
While updating the spam version to 36 in crm 700, its throughing the below message. I checked tp tool, consistency check, everything seems fine.
any idea what may casue this problem, as my spam is struck in import_proper phase of Prologue
The installation was stopped, since an error occurred during the phase
IMPORT_PROPER, which the Add-On Installation Tool is unable to resolve
without your input.
After you have corrected the cause of the error, continue with the
import by choosing Continue in the queue display.
The following details help you to analyze the problem:
      -   Error in phase: IMPORT_PROPER
      -   Reason for error: TP_STEP_FAILURE
     -   Return code: 0008
   -   Error message: OCS Package ALL, tp step "6", return code 0008
Notes on phase IMPORT_PROPER
   to be continued

In this phase the system imports the Repository objects and the table
   entries. The following are reasons why this phase may fail:
   o   TP_INTERFACE_FAILURE: The tp interface could not be called.
   o   TP_FAILURE: The tp program could not be executed. For more
       information on this, see the SLOG or ALOG log file.
   o   TP_STEP_FAILURE: A tp step could not be executed. To find the cause
       of the error, see the appropriate log, such as the import log.
       If a tp step 6, N, or S is specified in the termination message, it
       is a step that is independent of the transport request. You can vie
       these logs in the log overview by choosing Import Steps Not Specifi
       to Transport Request.
   Alternatively, see the logs in the following files in the log
   subdirectory of your transport directory (usually /usr/sap/trans/log):
        -   tp step 6: P<YY><MM><DD>.<SID>
        -   tp step N: N<YY><MM><DD>.<SID>
        -   tp step S: DS<YY><MM><DD>.<SID>
    To display these files, use the report RSPUTPRT or transaction AL11.
The Add-On Installation Tool requires that the Change and Transport
    System (CTS) be configured correctly. For more detailed information,
    read the online documentation available from Help -> SAP Library ->
    mySAP Technology Components -> SAP Web Application Server -> BC Change
    and Transport System .
    A list of the most important SAP Notes for Online Correction Support
    (OCS) is available in SAP Note 97620, which is updated regularly.
Regards - Munish

Error in SAPKB70012 patch

Hi,
when am applying the SAPKB70012 patch it will taking the long time in "tp user check ok" this phase. This phase is running last 6 hours and still running. plzzz send me solution and experts.
Thanks,
Sumanbabu.B

Hi,
I have encountered situations where SAPKB70012 Patch runs for about 24 Hrs. If you are not getting any errors I would suggest to wait for it to it get completed.
Is your processor AMD ?
Regards
Christo

Patch in phase IMPORT_PROPER is hanging

Hi!
I am facing with the following errors after the system copy of SAP ERP 2005 on Windows migrated from MS SQL to SAP DB.
The SAP_BASIS-Patch (SAPKB70014) in the phase u201CIMPORT_PROPERu201D (Step: DD Activation)
is hanging.
I have checked the RFC-connections like TMSADM(at)VHT.DOMAIN_VHT
and have detected (via u201Cconnection testu201D) that
the responsible time of data transport is very long.
Could it be the reason for the problem above?
If Yes, how can this be solved?
Thank you very much
regards
Thom

HI there,
Regarding support pack, please check import logs for any errors and return codes >4. Also, check the action log to see if all phases have completed successfully so far.
And regarding RFC, the connection test is successfull, right?
regards, Sean.

SPAM update struck in IMPORT_PROPER phase

Hello gurus,
we are importing SAPKB70030, SAPKB70030 and SAPKA70030 into our LEH. LEH is a HCM developer system running on zLinux with database DB2 on zOS.
The update is stuck at the "move nametab" on the table TTONFTVZZBEPP. This table is a lock, which can currently not be resolved.
Because it is an empty table, we would like to skip this action. There is a possibility?
Thank you for your efforts.
Regards
Hartmut Wagner

Matt,
After we unlock the tables, we were able to continue the SPAM. Thank you for the tip.
Regards,
Hartmut

Error Patch IMPORT_PROPER phase

Dear support,
We were applying patches on Netweaver 2004s Oracle 10.2.0.2 Windows platform server. Basis patch 12 and it was successfull in Test mode , but during standard mode suddenly machine got restarted because of power problem.
Now database and SAP is up and running , but i am unable to proceed with any of transactions ( like SPAM ) as i get <b>syntax_error</b>. Patch is in IMPORT_PROPER phase so i cannot reset until i do some database work.
What i am just aware i need to check entries in PAT01 , PAT02 , PAT03 and TRBAT tables and delete entries from PAT01 there to reset the queue and run patch again.
I can login to database with user SAPSR3 and there are entries for Basis patch 12 in table PAT01.Can anyone tell me further actions and querry which need to be executed to delete entry in detail , as i am having one week old backup which is not usefull for me.Please let me know safest way out of this issue.
Please help me at earliest.
Best Regards,
AjitR

praveen ,
I havent deleted any entry from tables , please find below
SQL> select PATCH,STEPCOND,RET_CODE,MESSAGE from PAT01;
PATCH                                                        STE RET_CODE
MESSAGE
SAPKB70012                                                   ?
SQL> SELECT * FROM PAT02;
no rows selected
SQL> SELECT COUNT(*) FROM PAT03;
COUNT(*)
        33
SQL> SELECT COUNT(*) FROM PAT10;
COUNT(*)
         1
SQL> SELECT PATCH,STATUS,IMPL_MANDT from PAT10;
PATCH                                                        STA IMPL_MAND
SAPKB70012                                                   R   000
SQL> SELECT RETCODE,CLIENT,ARGUMENT FROM TRBAT;
RETCODE      CLIENT    ARGUMENT
F
logs are as below
Transport request ; SAPKB70012
SQL error 1089 accessing : ORA-01089 immediate shutdown in progress - no ope
Main import
Ended with Return code 12
could you throw some light on the same.

Struck in SPDD phase while patch importing

Hi,
While importing basis patches, struck at RUN_SPDD phase.
I cant understand what is this? will anybody explain that
Regards,
J Wang

Hi,
If you have modified SAP objects, you must adjust these objects when you import them. Transaction SPDD adjusts Dictionary objects
If the patch upgrade is on a live system where users have customized and developers have created/modified programs, then you should do the modification adjustment. If its a fresh installation without any work done, you can ignore the modification adjustment.
Read more info in
http://help.sap.com/saphelp_sm32/helpdata/en/c6/068d380be34e6ce10000009b38f842/frameset.htm
Regards,
Mano

Error while Applying patch KW70014

Hi ,
I am facing the given error below while importing the patch KW70014.This is a BW patch .
     The import was stopped, since an error occurred during the phase
     IMPORT_PROPER, which the Support Package Manager is unable to resolve
     without your input.
     After you have corrected the cause of the error, continue with the
     import by choosing     Support Package -> Import queue      from the initial
     screen of the Support Package Manager.
     The following details help you to analyze the problem:
         -   Error in phase: IMPORT_PROPER
         -   Reason for error: TP_STEP_FAILURE
         -   Return code: 0016
I am not able to remove this from queue also since the patch is in IMPORT_PROPER Phase.Please give me some solution on priority either to remove it from queue or reimport this patch .Kernal level is 146 and we are using SQL DB.
Please help me on priority.
Regards,
Prasad
         -   Error message: OCS Package SAPKW70014, tp step "I", return code
             0016

Hi,
Please reply the support package without doing any action.
Hopefully it will resolve the issue.
Shivam

Error in basis patch SAPKB64012

Hello
I got the duplicate key error while applying basis patch SAPKB64012 in import_proper phase
Can anyone tell me the solution for this
Thanks

Hi Aashu,
Please refer to Note 88656, section 29, and use the attached allow file to ignore the error.
Basis Support Package SAPKB64013 deletes the corrupt entries in RSMPTEXTS.
Note 88656, section 29 says,
There is "data scrap" in the target table.
The error can also occur in the target table of the existing data scrap.
In many cases, R3trans essentially reads the existing table entries in
sorted sequence to merge them with the newly transported entries. Data
scrap may result in the entries not being returned correctly in sorted
sequence.
These scrap characters, in many cases, were distributed by transports
into several systems.
In the majority of cases, these types of errors can only be solved by
cleaning up the export system and repeating the transport. If the error
also occurs in when you are importing the cleaned-up transport, the data
scrap must also be cleaned up in the import system.
As of Release 6.20, data scrap is no longer exported. See section 5c in
Note 1074030, and Note 718511.
How to do:-
Please copy the attached file(from note) in AB64012.zip to /usr/sap/trans/cofiles
or /usr/sap/put/cofiles and repeat the import.
You can do the same for SP SAPKB64013.
Please use the latest versions of the tool 'tp' along with 'r3trans'
as well.
Please let me know if it resolves or not.
Thanks
kishore

Sort Dumps All Over in DEV and QAS While Applying Patches - Help Pls

Applying about 80 patches on DEV and QAS over the weekend with the "Minimize Downtime" option. I got failure at the "TEST_IMPORT" phase and tried to backout and ignore the error but now I keep getting short dumps for any tcode that I use. I can't get past short dumps.
Here is a sample of short dump that I got when I try to execute SPAM and reapply just one patch. I does not load the patch, it just generates a short dump. I opened an OSS note with SAP and they refused to consider that as high priority. Since my DEV and QAS systems are down, the developers will not have any system to work on today and there will be a lot pressure on me today. Please help.
Short Dump text below
The following syntax error occurred in the program SAPLKKBL :
"The field "GFLG_NESTED_PRINT_ON" is unknown, but there is a field with"
Error in ABAP application program.
The current ABAP program "CL_GUI_ALV_GRID===============CP" had to be
terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Please eliminate the error by performing a syntax check
(or an extended program check) on the program "SAPLKKBL ".
You can also perform the syntax check from the ABAP/4 Editor.
If the problem persists, proceed as follows:
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion

Hi
Please check the following link, it may help you:
Re: Can not lanche workflow with event
Can you give me some more details like whether the patch application is complete or its hung in between? Did u tried to restart the patch application? Can you tell me what error you got while patch application in import_proper phase?
Regards
Sumit

While installing BI system tried to add-on bi704 cont but patch shows error

hi Experts ,
here i installed one BI system and after i try to add BI 704 cont to that system
in saint i added that BI cont, after some time it shows error in the phase of IMPORT_PROPER AND the error message is in below
please reply what is the solution for below error
WARNING: /usr/sap/trans/tmp/SAPKK-704IFINBICONT.LSD is already in use (71580), I'm waiting 4 sec (20100927115806). My name: p
id 708834 on server name
WARNING: /usr/sap/trans/tmp/SAPKK-704IFINBICONT.LSD is already in use (71590), I'm waiting 3 sec (20100927115836). My name: p
id 708834 on name server
WARNING: /usr/sap/trans/tmp/SAPKK-704IFINBICONT.LSD is already in use (71600), I'm waiting 4 sec (20100927115908). My name: p
id 708834 on name server
WARNING: /usr/sap/trans/tmp/SAPKK-704IFINBICONT.LSD is already in use (71610), I'm waiting 1 sec (20100927115940). My name: p
id 708834 on name server
WARNING: /usr/sap/trans/tmp/SAPKK-704IFINBICONT.LSD is already in use (71620), I'm waiting 5 sec (20100927120013). My name: p
id 708834 on name server
WARNING: /usr/sap/trans/tmp/SAPKK-704IFINBICONT.LSD is already in use (71630), I'm waiting 4 sec (20100927120050). My name: p
id 708834 on name server
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR SAPK-704IFINBICONT   LSD I 0012 20100927120107 BICONTUSER   SAP_BASIS    labidev 20100924201404
STOP MAIN IMPORT          LSD I      20100927120107              SAP_BASIS    labidev 20100924201404
ERROR: stopping on error 12 during MAIN IMPORT
STOP imp all              LSD   0012 20100927120107              SAP_BASIS    labidev 20100924201404
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR SAPK-704IFINBICONT   LSD I 0012 20100927120109 BICONTUSER   SAP_BASIS    labidev 20100924225043
STOP MAIN IMPORT          LSD I      20100927120109              SAP_BASIS    labidev 20100924225043
ERROR: stopping on error 12 during MAIN IMPORT
STOP imp all              LSD   0012 20100927120109              SAP_BASIS    labidev 20100924225043
Regards

Dear sarath,
thanks for your cool responce
now i strucked at import_proper
and the error message is
Main import
Transport request   : SAPK-704IFINBICONT
System              : LSD
tp path             : tp
Version and release: 372.04.08 700
sap_dext called with msgnr 1:
     db call info
function:   db_report_interface
fcode:      CLOSE_LINE_MODE
tabname:    SOURCE
len (char): 40
key:        /MAP/LFG_SSM01F04
retcode:    1
SQL error 1089 accessing : ORA-01089: immediate shutdown in progress - no ope
Main import
End date and time : 20100930095406
Ended with return code: ===> 12 <===
and so please let me can i reset queue for applying new version or can i do as per your previous mail
Regards

Error in import_phase while applying addon ST-PI 2008_710

when i am applying addon for ST-PI 2008_710 db2 databse , its strucking in import_proper phase and giving below error in sm21
Grp N Text
BY 2 Database error -104 at EXE
BY 0 > SQL0104N An unexpected token "LENGTH 4096" was found
BY 0 > following "_L" CLOB(99K) INLINE". Expected tokens may
BY 0 > include: "<references_spec>". SQLSTATE=42601
the below are the logs on OS level,
2WETP000 12:43:02: Retcode 1: error in DDL statement for "/ASU/STEPST " - repeat
2EETP345 12:43:14: Retcode 1: SQL-error "-104-SQL0104N An unexpected token "LENGTH 4096" was found
2EETP345 following "_L" CLOB(99K) INLINE". Expected tokens may include: "<references_spec>". SQ
2EETP345 LSTATE=42601" in DDL statement for "/ASU/STEPST "
2 ETP399 -
DB-ROLLBACK() -
2EETP334 12:43:14: error in DDL, nametab for "/ASU/STEPST" not activated
3 ETP379X12:43:14: activating Nametab "/ASU/STEPST_V":
3 ETP355Xstatements:
3 ETP399 CREATE TABLE "/ASU/STEPST_V"
3 ETP399 ("SCENARIO" SAPDB6CHAR(000020)
3 ETP399 DEFAULT ' ' NOT NULL,
3 ETP399 "VERSION" SAPDB6CHAR(000014)
3 ETP399 DEFAULT ' ' NOT NULL,
3 ETP399 "INDX" SAPDB6CHAR(000006)
3 ETP399 DEFAULT '000000' NOT NULL,
3 ETP399 "LANGU" SAPDB6CHAR(000001)
3 ETP399 DEFAULT ' ' NOT NULL,
3 ETP399 "DESCRIPTION" SAPDB6CHAR(000060)
3 ETP399 DEFAULT ' ' NOT NULL,
3 ETP399 "DESCR_FILENAME" SAPDB6CHAR(000255)
3 ETP399 DEFAULT ' ' NOT NULL,
3 ETP399 "DESCR_MIMETYPE" SAPDB6CHAR(000128)
3 ETP399 DEFAULT ' ' NOT NULL,
3 ETP399 "BDS_DOC_ID" SAPDB6CHAR(000042)
3 ETP399 DEFAULT ' ' NOT NULL,
3 ETP399 "LEN_DESCR_L" SMALLINT
3 ETP399 DEFAULT 0 NOT NULL,
3 ETP399 "DESCRIPTION_L" SAPDB6VARCHAR(008000))
3 ETP399 IN "PID#POOLD"
3 ETP399 INDEX IN "PID#POOLI"
3 ETP399 LONG IN "PID#POOLD"
3 ETP399
2WETP000 12:43:14: Retcode 1: error in DDL statement for "/ASU/STEPST_V " - repeat
2EETP345 12:43:26: Retcode 1: SQL-error "-104-SQL0104N An unexpected token "LENGTH 4096" was found
2EETP345 following "_L" CLOB(99K) INLINE". Expected tokens may include: "<references_spec>". SQ
2EETP345 LSTATE=42601" in DDL statement for "/ASU/STEPST_V "
2 ETP399 -
DB-ROLLBACK() -
2EETP334 12:43:26: error in DDL, nametab for "/ASU/STEPST_V" not activated
This table doesn't exist in database db2, but its showing active in sap.
Thanks - MJ

Hi,
The system is struck in import_proper phase while applying addon and its patch in STPI, I am getting the below eror :-
Kindly hlep urgently. Getting the same error event i added the requests to buffer again.
     The installation was stopped, since an error occurred during the phase
     IMPORT_PROPER, which the Add-On Installation Tool is unable to resolve
     without your input.
     After you have corrected the cause of the error, continue with the
     import by choosing Continue in the queue display.
     The following details help you to analyze the problem:
         -   Error in phase: IMPORT_PROPER
         -   Reason for error: TP_BUFFER_INCONSISTENCY
         -   Return code: 0008
        -   Error message: Pkgs. in queue don"t exist in the tp buffer (e.g.
             SAPKITLREB)
   Notes on phase IMPORT_PROPER
   In this phase the system imports the Repository objects and the table
   entries. The following are reasons why this phase may fail:
   o   TP_INTERFACE_FAILURE: The tp interface could not be called.
   o   TP_FAILURE: The tp program could not be executed. For more
       information on this, see the SLOG or ALOG log file.
   o   TP_STEP_FAILURE: A tp step could not be executed. To find the cause
       of the error, see the appropriate log, such as the import log.
       If a tp step 6, N, or S is specified in the termination message, it
       is a step that is independent of the transport request. You can view
       these logs in the log overview by choosing Import Steps Not Specific
       to Transport Request.
   Alternatively, see the logs in the following files in the log
   subdirectory of your transport directory (usually /usr/sap/trans/log):
         -   tp step 6: P<YY><MM><DD>.<SID>
         -   tp step N: N<YY><MM><DD>.<SID>
         -   tp step S: DS<YY><MM><DD>.<SID>
     To display these files, use the report RSPUTPRT or transaction AL11.
     The Add-On Installation Tool requires that the Change and Transport
     System (CTS) be configured correctly. For more detailed information,
     read the online documentation available from Help -> SAP Library ->
     mySAP Technology Components -> SAP Web Application Server -> BC Change
     and Transport System .
     A list of the most important SAP Notes for Online Correction Support
     (OCS) is available in SAP Note 97620, which is updated regularly.

SPAM is hangs XPRA_EXECUTION Phase

Hi Gurus,
I have stucked in XPRA_EXECUTION phase. The TP
ended with return code 0008 while implementing the sapkb70012 patch for SAP_BASIS in ECC system.
SPAM is hangs XPRA_EXECUTION Phase.I see in status of Support Package :The import was stopped, since an error occurred.
Error in phase - XPRA_EXECUTION
Reason for error - TP_STEP_FAILURE
Return code - 0008
Error message - OCS package SAPKB70012, tp step R, return code 0008.
Could please Advise the Solution for the issue.
Appretiate you help.
Thanks
Anils

Hi
See below is the log for error code 0008 in SAPRB70012.
3 EPU182 Post-processing for &2"ACGR" &3"SAP_XI_BPE_ADMINISTRATOR_ABAP" was already performed successfully earlier&1"R3TR"
3 EPU182 Post-processing for &2"ACGR" &3"SAP_XI_BPE_CONFIGURATOR_ABAP" was already performed successfully earlier&1"R3TR"
3 EPU182 Post-processing for &2"ACGR" &3"SAP_XI_BPE_MONITOR_ABAP" was already performed successfully earlier&1"R3TR"
3 EPU182 Post-processing for &2"ACGR" &3"SAP_XI_BPE_SERV_USER" was already performed successfully earlier&1"R3TR"
3 EPU182 Post-processing for &2"ACGR" &3"SAP_XI_BPE_SERV_USER_MAIN" was already performed successfully earlier&1"R3TR"
3 EPU123 Post-import method "PRGN_AFTER_IMP_ACTGROUP_ACGR" completed for "ACGR" "L", date and time: "20080206084243"
2 EPU122XPost-import method "RH_ACTIVATE_PDOBJECT_AFTER_IMP" started for "PDST_BASE" "T", date and time: "20080206084243"
3 EPU182 Post-processing for &2"TDAT" &3"PDST_BASE" was already performed successfully earlier&1"R3TR"
3 EPU123 Post-import method "RH_ACTIVATE_PDOBJECT_AFTER_IMP" completed for "PDST_BASE" "T", date and time: "20080206084243"
2 EPU122XPost-import method "SRT_REG_AFTER_IMPORT" started for "SRTD" "L", date and time: "20080206084243"
3 EPU182 Post-processing for &2"SRTD" &3"8A0A000A416FA34EBD449DF66C50649B" was already performed successfully earlier&1"R3TR"
3 EPU123 Post-import method "SRT_REG_AFTER_IMPORT" completed for "SRTD" "L", date and time: "20080206084243"
2 EPU122XPost-import method "SUSR_AFTER_IMP_PROFILE" started for "SUSPR" "T", date and time: "20080206084244"
3 EPU182 Post-processing for &2"TDAT" &3"SUSPR" was already performed successfully earlier&1"R3TR"
3 EPU123 Post-import method "SUSR_AFTER_IMP_PROFILE" completed for "SUSPR" "T", date and time: "20080206084244"
2 EPU127 Post-import methods of change/transport request "SAPKB70012" completed
2 EPU128      Start of subsequent processing ... "20080206084214"
2 EPU129      End of subsequent processing... "20080206084244"
2 EPU110XExecute reports for change/transport request: "SAPKB70012"
4 EPU111    on the application server: "DRIECCDEV"
3 ETP000
3 ETP000 **************************************************
3 ETP000
2 EPU117 Reports for change/transport request "SAPKB70012" have been executed
2 EPU118      Start of................ "20080206084244"
2 EPU119      End of.................. "20080206084244"
1 ETP162 EXECUTION OF REPORTS AFTER PUT
1 ETP110 end date and time   : "20080206084244"
1 ETP111 exit code           : "8"
1 ETP199 ######################################
Regards
Anilsai

SPAM-Patch (SAPKB70014) is hanging in phase Import_Proper

Hi experts!
I have problems to patch the SAP-Basis component (SAPKB70014) for SAP ERP 2005.
The problem is that the patch is hanging in the phase Import_Proper.
I read suitable SAP Note 822379 and changed the kernel to Patch 133 or 146, but it does not help.
The system is installed via heterogeneous system copy.
I have also other problems, e.g. Dump u201CITAB_DUPLICATE_KEYu201D by accessing into the tcodes DB13, DBACOCKPIT.
Enclosed the last lines of the log file ULOG08_2
Any helpful information is very appreciated and will be awarded with points.
APServiceVHT 20080526133153 RFC: tp IMPORT all VHT pf=
vzhl9000\sapmnt\trans\bin\TP_DOMAIN_VHT.PFL -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems= -Dbuffreset=yes -Dmainimp_proc=1 -Ddictimp_proc=1 -Dbatch_proc=1 -Dstopimmediately=1 -Dactivatemerged=yes -Dcheckmasterlang=no tag=spam -Dtransdir=
vzhl9000\sapmnt\trans
APServiceVHT 20080526133221 RFC: tp COUNT AUS pf=
vzhl9000\sapmnt\trans\bin\TP_DOMAIN_VHT.PFL -Dtransdir=
vzhl9000\sapmnt\trans
APServiceVHT 20080526133221 RFC: tp COUNT VHT pf=
vzhl9000\sapmnt\trans\bin\TP_DOMAIN_VHT.PFL -Dtransdir=
vzhl9000\sapmnt\trans
APServiceVHT 20080526133224 RFC: tp COUNT AUS pf=
vzhl9000\sapmnt\trans\bin\TP_DOMAIN_VHT.PFL -Dtransdir=
vzhl9000\sapmnt\trans
APServiceVHT 20080526133224 RFC: tp COUNT VHT pf=
vzhl9000\sapmnt\trans\bin\TP_DOMAIN_VHT.PFL -Dtransdir=
vzhl9000\sapmnt\trans
APServiceVHT 20080526133246 RFC: tp COUNT AUS pf=
vzhl9000\sapmnt\trans\bin\TP_DOMAIN_VHT.PFL -Dtransdir=
vzhl9000\sapmnt\trans
APServiceVHT 20080526133246 RFC: tp COUNT VHT pf=
vzhl9000\sapmnt\trans\bin\TP_DOMAIN_VHT.PFL -Dtransdir=
vzhl9000\sapmnt\trans
APServiceVHT 20080526133248 RFC: tp COUNT AUS pf=
vzhl9000\sapmnt\trans\bin\TP_DOMAIN_VHT.PFL -Dtransdir=
vzhl9000\sapmnt\trans
APServiceVHT 20080526133248 RFC: tp COUNT VHT pf=
vzhl9000\sapmnt\trans\bin\TP_DOMAIN_VHT.PFL -Dtransdir=
vzhl9000\sapmnt\trans
APServiceVHT 20080526151612 RFC: tp SHOWPARAMS VHT pf=
vzhl9000\sapmnt\trans\bin\TP_DOMAIN_VHT.PFL -Dtransdir=
vzhl9000\sapmnt\trans
APServiceVHT 20080526151612 RFC: tp CONNECT VHT pf=
vzhl9000\sapmnt\trans\bin\TP_DOMAIN_VHT.PFL -Dtransdir=
vzhl9000\sapmnt\trans
APServiceVHT 20080526151614 RFC: tp IMPORT all VHT pf=
vzhl9000\sapmnt\trans\bin\TP_DOMAIN_VHT.PFL -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems= -Dbuffreset=yes -Dmainimp_proc=1 -Ddictimp_proc=1 -Dbatch_proc=1 -Dstopimmediately=1 -Dactivatemerged=yes -Dcheckmasterlang=no tag=spam -Dtransdir=
vzhl9000\sapmnt\trans
APServiceVHT 20080526151807 RFC: tp COUNT AUS pf=
vzhl9000\sapmnt\trans\bin\TP_DOMAIN_VHT.PFL -Dtransdir=
vzhl9000\sapmnt\trans
APServiceVHT 20080526151807 RFC: tp COUNT VHT pf=
vzhl9000\sapmnt\trans\bin\TP_DOMAIN_VHT.PFL -Dtransdir=
vzhl9000\sapmnt\trans
APServiceVHT 20080526161807 RFC: tp SHOWPARAMS VHT pf=
vzhl9000\sapmnt\trans\bin\TP_DOMAIN_VHT.PFL -Dtransdir=
vzhl9000\sapmnt\trans
APServiceVHT 20080526161807 RFC: tp CONNECT VHT pf=
vzhl9000\sapmnt\trans\bin\TP_DOMAIN_VHT.PFL -Dtransdir=
vzhl9000\sapmnt\trans
APServiceVHT 20080526161810 RFC: tp IMPORT all VHT pf=
vzhl9000\sapmnt\trans\bin\TP_DOMAIN_VHT.PFL -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems= -Dbuffreset=yes -Dmainimp_proc=1 -Ddictimp_proc=1 -Dbatch_proc=1 -Dstopimmediately=1 -Dactivatemerged=yes -Dcheckmasterlang=no tag=spam -Dtransdir=
vzhl9000\sapmnt\trans
APServiceVHT 20080526165518 RFC: tp SHOWPARAMS VHT pf=
vzhl9000\sapmnt\trans\bin\TP_DOMAIN_VHT.PFL -Dtransdir=
vzhl9000\sapmnt\trans
APServiceVHT 20080526165518 RFC: tp CONNECT VHT pf=
vzhl9000\sapmnt\trans\bin\TP_DOMAIN_VHT.PFL -Dtransdir=
vzhl9000\sapmnt\trans
APServiceVHT 20080526165520 RFC: tp IMPORT all VHT pf=
vzhl9000\sapmnt\trans\bin\TP_DOMAIN_VHT.PFL -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems= -Dbuffreset=yes -Dmainimp_proc=1 -Ddictimp_proc=1 -Dbatch_proc=1 -Dstopimmediately=1 -Dactivatemerged=yes -Dcheckmasterlang=no tag=spam -Dtransdir=
vzhl9000\sapmnt\trans
APServiceVHT 20080526165743 RFC: tp SHOWPARAMS VHT pf=
vzhl9000\sapmnt\trans\bin\TP_DOMAIN_VHT.PFL -Dtransdir=
vzhl9000\sapmnt\trans
APServiceVHT 20080526165743 RFC: tp CONNECT VHT pf=
vzhl9000\sapmnt\trans\bin\TP_DOMAIN_VHT.PFL -Dtransdir=
vzhl9000\sapmnt\trans
APServiceVHT 20080526165744 RFC: tp SHOWPARAMS VHT pf=
vzhl9000\sapmnt\trans\bin\TP_DOMAIN_VHT.PFL -Dtransdir=
vzhl9000\sapmnt\trans
APServiceVHT 20080526165744 RFC: tp CONNECT VHT pf=
vzhl9000\sapmnt\trans\bin\TP_DOMAIN_VHT.PFL -Dtransdir=
vzhl9000\sapmnt\trans
APServiceVHT 20080526165744 RFC: tp IMPORT all VHT pf=
vzhl9000\sapmnt\trans\bin\TP_DOMAIN_VHT.PFL -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems= -Dbuffreset=yes -Dmainimp_proc=1 -Ddictimp_proc=1 -Dbatch_proc=1 -Dstopimmediately=1 -Dactivatemerged=yes -Dcheckmasterlang=no tag=spam -Dtransdir=
vzhl9000\sapmnt\trans
Regards
Thom

Hi,
I have similiar problem with patching SPS from 9 to 14 level on NetWeaver2004s.
One background process is working second day, but it has status - STOP.
When I'm logging into system a have "Status 0020 of the user interface SAPMSYST missing" message.
Thom did you resolve your problem?
Regards
Michal Sarna

SAPKB70012 patch struck in IMPORT_PROPER

Similar Messages

Maybe you are looking for