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

Similar Messages

  • 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

  • SPAM update in IMPORT_PROPER phase

    Dear All,
    I have installed SAP Web Neweaver 04s as ABAP on MSSQL database windows
    OS and upgraded kernel 640 patch 175.
    But now when i go to import SPAM /SAINT from level 17 to 23 ie.
    SAPKD64023 then its running in IMPORT_PROPER Phase since last 5-6 hrs.
    PLEASE SUGGEST how to speed up my process??
    Log is as below:
    Log Overview for SAPKD64023
    SAPKD64023 SPAM/SAINT Update - Version 640/0023
    BPW System BPW
    Generate Transport Information File 02.01.2008 13:41:45 (0)
    Successfully Completed
    Test Import 02.01.2008 13:41:46 (0) Successfully Completed
    Import Request Piece List 02.01.2008 13:41:47 (4) Ended with Warning
    Import ABAP Dictionary Objects 02.01.2008 13:41:52 (4) Ended with
    Warning
    02.01.2008 10:54:46 (4) Ended with Warning
    02.01.2008 13:41:52 (4) Ended with Warning
    ABAP Dictionary Activation 02.01.2008 14:13:28 (4) Ended with Warning
    Import steps not specific to transport request
    ABAP Dictionary Distribution 02.01.2008 14:23:31 (4) Ended with Warning
    pls help me ASAP.
    Regards & Thanks,
    Ankita.

    Hi Ankita,
    I advice you to leave it for the moment and wait until it finishe that particular stage and check for the workporcess overview which report its executing at the back.Dont stop the process forcefully as it might cause inconsistency.
    Regards,
    Iqbal

  • SPAM IMPORT_PROPER Phase delay

    Hi all,
    I have SOLMAN 7 EHP1 SP 24. in a windows host, with Oracle database.
    I just update my spam to latest version 7.01/0041
    then i need to updatethe component "ST-ICO 150_700"  my actual SP is 24, i need get updated to  patch 0025.
    I add to the queue only this ST-ICO component. 
    In sm37 I see the job running without errors.
    Job                              Spool Job Doc Job CreatedB Status          Start date Start time Duration(sec.) Delay (sec.)
    OCS_QUEUE_IMPORT                               71360900     Active          19.01.2011 16:21:02          55.578            0
    In spam in action log see that all previous phases was successfully finished, for example the latest phase was  Import phase 'DDIC_ACTIVATION' .
    but in  IMPORT_PROPER Phase is taking more than 16 hours right now.
    If is just a ST-iCO component why this take so long? Is normal this behaviour?
    Where can i see detailed log of actions, or how can i ensure me that all is running ok?
    Thanks a lot
    update: in tp system log i see so many lines with this:
    WARNING: \\solman\sapmnt\trans\tmp\SAPKK-1507PINSTPL.SSM is already in use (17060), I'm waiting 2 sec (20110120064823). My nam
    WARNING: \\solman\sapmnt\trans\tmp\SAPKK-1507PINSTPL.SSM is already in use (17070), I'm waiting 2 sec (20110120064853). My nam
    WARNING: \\solman\sapmnt\trans\tmp\SAPKK-1507PINSTPL.SSM is already in use (17080), I'm waiting 4 sec (20110120064921). My nam
    WARNING: \\solman\sapmnt\trans\tmp\SAPKK-1507PINSTPL.SSM is already in use (17090), I'm waiting 2 sec (20110120064952). My nam
    WARNING: \\solman\sapmnt\trans\tmp\SAPKK-1507PINSTPL.SSM is already in use (17100), I'm waiting 1 sec (20110120065010). My nam
    WARNING: \\solman\sapmnt\trans\tmp\SAPKK-1507PINSTPL.SSM is already in use (17110), I'm waiting 3 sec (20110120065038). My nam
    WARNING: \\solman\sapmnt\trans\tmp\SAPKK-1507PINSTPL.SSM is already in use (17120), I'm waiting 5 sec (20110120065117). My nam
    WARNING: \\solman\sapmnt\trans\tmp\SAPKK-1507PINSTPL.SSM is already in use (17130), I'm waiting 1 sec (20110120065153). My nam
    WARNING: \\solman\sapmnt\trans\tmp\SAPKK-1507PINSTPL.SSM is already in use (17140), I'm waiting 4 sec (20110120065222). My nam
    WARNING: \\solman\sapmnt\trans\tmp\SAPKK-1507PINSTPL.SSM is already in use (17150), I'm waiting 1 sec (20110120065259). My nam
    WARNING: \\solman\sapmnt\trans\tmp\SAPKK-1507PINSTPL.SSM is already in use (17160), I'm waiting 2 sec (20110120065332). My nam
    WARNING: \\solman\sapmnt\trans\tmp\SAPKK-1507PINSTPL.SSM is already in use (17170), I'm waiting 3 sec (20110120065404). My nam
    I wiil try restart the import .
    Edited by: Manfred Kaufmann on Jan 20, 2011 1:55 PM

    Thanks for the tip. This seemed to resolve my issue.

  • 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

  • Error in IMPORT_PROPER phase

    Hi guys,
    I am trying to apply SP on my system 09-15
    and I get and import_proper phase error below:
    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_BUFFER_INCONSISTENCY
         -   Return code: 0008
         -   Error message: Pkgs. in queue don"t exist in the tp buffer (e.g.
             SAPKB64010)
    Tried the following:
    Generated a new TP Parameter through STMS
    Clear the log files
    Tried to clear the buffer manually with S37 OCS_RESET_QUEUE getting an object locked message.
    Updated the Kernel and SPAM/SAINT
    Please Help
    Thanks,
    Damien

    Hi All!
    I have a similar problem on my Netweaver'04 BW Productive Instance, STMS is on Stuck and no more transport are possible!!!
    VERY BAD!!!
    I have the SAME error and i checked all the possible but finding nothing interesting
    Following a print screen from varous commands such as "TP SHOWPARAMS" "TP ADDTOBUFFER" etc..
    Could you check again for me?
    Thanks in advance...
    G.R.
    *0000
    *0000
    I
    BSVK900675          |                    | |0000 |      |      |0000 |      |
    *0000
    *0000
    I
    BSVK900677          |                    | |0000 |      |      |0000 |      |
    *0000
    *0000
    I
    BSVK900678          |                    | |0000 |      |      |0000 |      |
    *0000
    *0004
    I
    BSVK900657          |                    | |0000 |      |      |0000 |      |
    *0000
    *0000
    I
    BSVK900659          |                    | |0000 |      |      |0000 |      |
    *0000
    *0000
    I
    BSVK900655          |                    | |0000 |      |      |0000 |      |
    *0000
    *0000
    I
    BSVK900661          |                    | |0000 |      |      |0000 |      |
    *0000
    *0004
    I
    BSVK900663          |                    | |0000 |      |      |0000 |      |
    *0000
    *0004
    I
    BSVK900665          |                    | |0000 |      |      |0000 |      |
    *0000
    *0000
    I
    BSVK900680          |                    | |0000 |      |      |0000 |      |
    *0000
    *0000
    I
    BSVK900681          |                    | |0000 |      |      |0000 |      |
    *0000
    *0000
    I
    BSVK900685          |                    | |0000 |      |      |0000 |      |
    *0000
    *0000
    I
    BSVK900687          |                    | |0000 |      |      |0000 |      |
    *0000
    *0000
    I
    BSVK900688          |                    | |0000 |      |      |0000 |      |
    *0000
    *0000
    I
    BSVK900690          |                    | |0000 |      |      |0000 |      |
    *0000
    *0000
    I
    BSVK900691          |                    | |0000 |      |      |0000 |      |
    *0000
    *0000
    I
    BSVK900692          |                    | |0000 |      |      |0000 |      |
    *0000
    *0000
    I
    BSVK900695          |                    | |0000 |      |      |0000 |      |
    *0000
    *0000
    I
    that makes 174 transports to be imported.
    tp finished with return code: 0
    meaning:
      Everything OK
    C:\Documents and Settings\bpradm>tp addtobuffer bsvk901395 bpr pf=d:\usr\sap\tra
    ns\bin\tp_domain_bsv.pfl -Dtransdir=d:\usr\sap\trans
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    This is tp version 340.16.09 (release 640)
    Warning: Parameter DBHOST is no longer used.
    Warning: Parameter DBNAME is no longer used.
    Addtobuffer failed for BSVK901395.
      Neither datafile nor cofile exist (cofile may also be corrupted).
    tp returncode summary:
    TOOLS: Highest return code of single steps was: 0
    ERRORS: Highest tp internal error was: 0247
    tp finished with return code: 247
    meaning:
      addtobuffer has problems with data- and/or cofile
    C:\Documents and Settings\bpradm>tp addtobuffer bsvk901395 bpr pf=d:\usr\sap\tra
    ns\bin\tp_domain_bsv.pfl -Dtransdir=d:\usr\sap\trans
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    This is tp version 340.16.09 (release 640)
    Warning: Parameter DBHOST is no longer used.
    Warning: Parameter DBNAME is no longer used.
    Addtobuffer failed for BSVK901395.
      Neither datafile nor cofile exist (cofile may also be corrupted).
    tp returncode summary:
    TOOLS: Highest return code of single steps was: 0
    ERRORS: Highest tp internal error was: 0247
    tp finished with return code: 247
    meaning:
      addtobuffer has problems with data- and/or cofile
    C:\Documents and Settings\bpradm>tp addtobuffer bsvk901396 bpr pf=d:\usr\sap\tra
    ns\bin\tp_domain_bsv.pfl -Dtransdir=d:\usr\sap\trans
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    This is tp version 340.16.09 (release 640)
    Warning: Parameter DBHOST is no longer used.
    Warning: Parameter DBNAME is no longer used.
    Addtobuffer failed for BSVK901396.
      Neither datafile nor cofile exist (cofile may also be corrupted).
    tp returncode summary:
    TOOLS: Highest return code of single steps was: 0
    ERRORS: Highest tp internal error was: 0247
    tp finished with return code: 247
    meaning:
      addtobuffer has problems with data- and/or cofile
    C:\Documents and Settings\bpradm>tp help
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    This is tp version 340.16.09 (release 640)
    usage:   tp <command> [argument(s)] [option(s)], where <command> may be one of:
    Exporting                   I Buffer Actions              I Disk Space
    EXPORT       I EXPWBO       I ADDTOBUFFER  I DELFROMBUFFERI CLEAROLD
    R3E          I VERSE        I SETSYNCMARK  I DELSYNCMARK  I CHECK
    SDE          I              I SETSTOPMARK  I DELSTOPMARK  I TESTOLD
    TST          I              I MARK         I UNMARK       I
                  I              I CLEANBUFFER  I              I
    Importing                   I Special Functions           I Information
    PUT          I              I LOCKSYS      I UNLOCKSYS    I SHOWBUFFER
    IMPORT       I CHNTABS      I LOCK_EU      I UNLOCK_EU    I COUNT
    CMD          I R3I          I WRITELOG     I GETPROTS     I SHOWPARAMS
    LIM          I MEA          I SAPSTART     I SAPSTOP      I GO
    R3H          I MVREPOS      I GETTBATGENT  I GETTRBATENT  I CONNECT
    ACT          I MVKERNEL     I GETDDXTTENT  I GETDDXTFENT  I CHECKIMPDP
    TACOB        I SDI          I GETOPENCORR  I CREATECOFILE I SHOWINFO
    GENTB        I GENT1        I PREPAREBUFFERI CREATEINFO   I GETOBJLIST
    GENT2        I GEN          I CONTP        I EXPCHK       I EXTRDOCU
    DIST         I XPA          I SHOWSEMAPHOREI SHOWSEMACLIENI GETCONVENT
    MVNTABS      I VERSI        I SETSEMAPHORE I DELSEMACLIENTI EXPLAINRC
    IMPSYNC      I DELIVER      I DELSEMAPHORE I GETTPSTATENT I
    For more details call tp with the desired command (and no other parameters)
    C:\Documents and Settings\bpradm>tp showparams  bsvk901396 bpr pf=d:\usr\sap\tra
    ns\bin\tp_domain_bsv.pfl -Dtransdir=d:\usr\sap\trans
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    This is tp version 340.16.09 (release 640)
    ERROR: : parameter -Dtransdir=d:\usr\sap\trans has wrong length
    Usage of command SHOWPARAMS:
      tp SHOWPARAMS <SAPSID> [options ...]
      Reads the parameter file and displays the current setting.
      Options:
         parname=<name>        display the value of the parameter <name> only
         pf=<TPPARAM>          specify a transport parameter file
         silent                redirect stdout to dev_tp in current directory
         -D"<entry>"           specify a parameter for tp
         -t<k>                 specify a trace level for tp
         tf=<filename>         specify the name of a trace file for tp
         shdwtadir=<tabname>   specify the name of a shadow TADIR
      Description of arguments:
         <TPPARAM>   (complete) path of a transport parameter file
         <entry>     a parameter description as in a tp parameter file
         <SAPSID>    R/3 system's name, (target or source whatever is appropriate)
    tp returncode summary:
    TOOLS: Highest return code of single steps was: 0
    ERRORS: Highest tp internal error was: 0206
    tp finished with return code: 206
    meaning:
      parameter %s has wrong length
    C:\Documents and Settings\bpradm>tp showparams bpr pf=d:\usr\sap\trans\bin\tp_do
    main_bsv.pfl -Dtransdir=d:\usr\sap\trans
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    This is tp version 340.16.09 (release 640)
    Warning: Parameter DBHOST is no longer used.
    Warning: Parameter DBNAME is no longer used.
    Parameters having their default value are displayed with a '>' as separator.
    Global settings:
    TRANSDIR : d:\usr\sap\trans\
    ALLLOG : ALOG0605.BPR              STOPONERROR >        9 SYSLOG : SLOG0605.BPR            REPEATONERROR>         9
    ABAPNTFMODE > t
    TP_VERSION :        266
    STOPIMMEDIATELY > 1 =TRUE
    NEW_SAPNAMES >    1 =TRUE    SQL_TRACE >          0 =FALSE
    DUMMY >          0 =FALSE
    CTC >          0 =FALSE       NBUFFORM :          1 =TRUE
    BUFFERFORMAT >
    SSFKEYS >
    SSFSIGNER >
    SSFLIB >
    SSFPAB >
    ALLOW_RC4 >    1 =TRUE   SID_LOG_FILES >          0 =FALSE
    IMPMON_MODE > NORMAL      IMPSMON_MODE > OFF
    TRACE2SERVER >          0 =FALSE
    DB-connection:
            CONNECT_MODE > USE_ENV
                 MOD_ENV >
                  DBTYPE : ora
    MSSQL_USEINTEGRATEDS >
            MSSQL_SCHEMA >
          DROPSTATISTICS >          1 =TRUE
        DBS_DB2_PLANNAME >
       RSDB_DB2PSLIBRARY >
    Distribution of transports:
           SYSTEM'S NAME : BPR                       VERS_AT_IMP > NEVER
       SEPARATE_DELIVERY >          0 =FALSE
             TESTSYSTEMS :
         DELIVERYSYSTEMS :
           SOURCESYSTEMS :
           TARGETSYSTEMS :
        SAPNAMES_LOGGING : ALL
             VERS_AT_EXP >          1 =TRUE
          CREATE_REPLIST >          0 =FALSE
    R3trans:
             R3TRANSPATH > R3trans.exe
             R3TRANSSTAT >
            LOCALR3TRANS >          0 =FALSE
           CLIENTCASCADE >          0 =FALSE
               RECCLIENT >
                LANGUAGE >
                     LSM > NONE
                     SLI >         -1
         CHECKMASTERLANG >          0 =FALSE
            RESTRICTLANG >
            IMPORTSHADOW >          0 =FALSE
          R3TRANSOPTIONS >
               FILESPLIT >          0
              ACC_IMPORT >          0 =FALSE
                DDACTIVE >          0 =FALSE
                   SMODI >          1 =TRUE
         PRESERVEMODINFO >          0 =FALSE
          CHEATCLIENT000 >          0 =FALSE
           LANGDELETIONS >          1 =TRUE
    Transport daemon:
               BATCHHOST >
               SYSTEM_NR >
               SYSTEM_PF >
              SAPEVTPATH > sapevt.exe
    Import in general:
                                                    MAINIMP_PROC >          1
                         >          0 =FALSE       LOGICALIMPORT >    0 =FALSE
    SETUNICODEFLAG >   0 =FALSE   DDINACTIVE >          0 =FALSE
    MAB >          1 =TRUE
    R3UP >          0 =FALSELOCK_CHECK_WAIT_TIME >          0
    EXP_CHECK_WAIT_TIME >          0                   W_IMPORT >          1 =TRUE
                 W_NEVER >          0 =FALSE
                K_IMPORT >          1 =TRUE              K_NEVER >          0 =FALSE
                T_IMPORT >          1 =TRUE              T_NEVER >          0 =FALSE
                C_IMPORT >          1 =TRUE              C_NEVER >          0 =FALSE
          BUFFERSNAPSHOT >          0 =FALSE
    PUT:
                PUTSTEPS > *=<Lw(H3A)dG
                STARTSAP >
                 STOPSAP >
               BUFFRESET >          1 =TRUE           BUFREFTIME >        180
                 LOCK_EU >          1 =TRUE          MC_ENQ_STEP >          1 =TRUE
              GENERATION >          1 =TRUE     RESET_TIMESTAMPS >          0 =FALSE
          TATAF_TOLERANT >          0 =FALSE         RESET_DBPOS >          0 =FALSE
           NTACT_TIMECMP >          0 =FALSE
      MVNTAB_LIST_FAILED >          1 =TRUE
    Kernelmove:
              KERNELMOVE >          0 =FALSE            CLEANIPC >          0 =FALSE
                 EXELIST >
                 FROMDIR >
                   TODIR >
          KERNELMOVEPATH >
            CLEANIPCPATH >
    Clearold:
            DATALIFETIME >        200            OLDDATALIFETIME >        365
          COFILELIFETIME >        365                LOGLIFETIME >        200
    Properties:
         SemaServer.Host : NULL
         SemaServer.Port : NULL
           tp.Semaphores : FILE
       tp.ConnectTimeout : 10000
    tp finished with return code: 0
    meaning:
      Everything OK

  • SAP_APPL(SAPKH60012)-eroor during Import_Proper phase

    Hello All,
    I has an ECC 6.0 sytem and was applying SAPKH60012-SAPKH60013 together.
    During the TEST-IMPORT i got the following error for both the support package
    "R3TRMSAGME was repaired in this system".
    I had ignored the error during TEST_IMPORT.
    But now i am stuck with this in my IMPORT_PROPER phase.
    Please suggest, I did not find any SAP Notes for this error.
    Also the main error
    Error in phase :IMPORT_PROPER
    Reason of the ERROR:TP_STEP_FAILUER
    Return Code: 0008
    Error Message :OCS Package SAPKH60012 , tp step "I",return Code 0008
    Also i found in the log this error
    Start import LIMUDOCUNAME818
    R3TRMSAGME was repaired in this system
    LIMUDOCUNAME818
    Regards
    Anthony
    Edited by: Anthony D'souza on Mar 6, 2009 11:11 PM

    Hi,
    For this error "R3TRMSAGME was repaired in this system". You need to reset the repair fag by using tcode se03.
    Also this error "TP_STEP_FAILUER" says that  tp failed. If you have upgraded kernel level before sp upgrade then check current tp's version. If you have not upgraed tp.exe  then download latest tp.exe & put it in your kernel path & restart the sp upgrade.
    Please check ksap note for known problem in Support packs for your SAP release
    Also check below threads. It will help you
    Re: spam error in IMPORT_PORPER
    tp
    Thanks,
    Sushil

  • Support Pack General Question:- IMPORT_PROPER phase

    Hi All,
    Is there any command at OS level to complete IMPORT_PROPER phase of SPAM transaction (support pack import)?

    Hi ,
    Is there any command at OS level to complete IMPORT_PROPER phase of SPAM transaction (support pack import) in My QAS system............. ?
    I tried the following command in my DEV & QAS System.but not solved.
    C:\>tp cleanbuffer qas pf=myprofile.pfl
    This is tp version 320.56.89 (release 620)
    E-myprofile.pfl could not be opened.
    EXIT
    Error in myprofile.pfl: transdir not set.
    tp returncode summary:
    TOOLS: Highest return code of single steps was: 0
    ERRORS: Highest tp internal error was: 0208
    tp finished with return code: 208
    meaning:
      error in transportprofil (param missing, unknown,...)

  • Support Packages Installation Stops at IMPORT_PROPER Phase

    Hi Sap stars,
                                I have started Installation of support packages for PI 7.1 Cluster Server , It got stuck at phase Import_Proper
                                and do not do anything , Then I executed the TP R3I .....COMMAND Which executed successfully
                                Then I executed the Command
                                tp showbuffer SID tag=spam pf=G:\usr\sap\trans
    \bin\TP_DOMAIN_SID.PFL
    This is tp version 375.33.68 (release 710, unicode enabled)
    SID buffer:
    SAPKB71007          |                    | |has already been imported completely
    that makes 0 transports to be imported.
    tp finished with return code: 0
    meaning:
    Everything OK
    But still in SPAM it is showing the IMPORT_PROPER status in RED
    Could anyone tell me how can this status get changed and Import other Support Packages
    Thanks In Advance
    Anil Kumar

    Hi Raghu,
    I have used the tp r3i command when I got stuck in Import_proper Phase It ended with TP retun code 008
    2EETW109 TABLE "SQL_TOOL_GROUPT" does not exist in Nametab
    When I try to run any Transaction Code it is throwing an Dump
    OS-Windows, Database_Sqlserver 2005 Application-PI 7.1
    Can u pls suggest me what can I do to sort this issue
    Thanks In Advance
    Anil

  • Error while importing SPAM version 7.0/33 Tp ended with error code 12.

    Hi all,
    Os: Windows 2003 advanced server
    DB: MaxDB 7.6
    SAP: NetWeaver 2004S - (ABAP+JAVA) EP
    When i was trying to import latest SAPM on the system. V 7.0/33 it got stopped in the middle at
    IMPORT_PROPER phase.
    Please find the error as follows:
    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: 0012
         -   Error message: OCS Package SAPKD70033, tp step "R", return code
             0012
    Notes on phase IMPORT_PROPER
    In this phase repository objects and table entries are imported. This
    phase can terminate due to the following reasons:
    o   TP_INTERFACE_FAILURE: The tp interface could not be called.
    o   TP_FAILURE: The program tp 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 the cancelation message contains a tp step 6, N or S, the step in
         question is independent of the transport request. You can find these
         logs under the node Import steps not specific to transport request
         in the log overview.
         Alternatively, you can find these logs in the following files in the
    log directory 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>
    You can display these files using the report RSPUTPRT or by calling the
    transaction AL11.
    A prerequisite of the Support Package Manager is that the Change and
    Transport System (CTS) is configured correctly. For more detailed
    information, read the online documentation available from Help -> SAP
    Library -> mySAP Technology Components -> SAP Web Application Server ->
    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.
    In the import log file the errors was :
    Program terminated (job: RDDEXECL, no.: 14444101)
    Job log for this job is ;
    Job started
    Step 001 started (program RDDEXECL, variant , user ID DDIC)
    All DB buffers of application server nanadual were synchronized
    ABAP/4 processor: SYSTEM_RUDI_INVALID
    Job cancelled
    Please let me know if you need more details...
    Best Regards,
    Nanda

    Hi Nanda,
    Please check your trans log for further details .
    It cud be caused due to unavailability of RDDIMPDP batch job which is mandatory for any SPAM / SP updates to work.
    If this is the case you wud require to trigger the batch job RDDIMPDP using report RDDNEWPP(From SE38). This needs to be triggered in 000 as well as other existing clients too.
    once this is done please resume your SPAM Update. it shud go ahead.
    Next possibility that you cud check is updating your tp / R3trans with latest available from Service market place.
    Hope this helps you.
    Regards,
    Prem

  • Too low SPAM version - EHP installation

    Dear All,
    during Configuration step in EHP installer I've got such error:
    Checks after phase PREP_CONFIGURATION/SPAM_CHK_INI were negative!
    Last error code set: SPAM version 26 is too low, at least version 40 is required. Apply latest SPAM patch
    Installer already extracted files from download directory and there was also SPAM/SAINT 701/0042 - it was added to download basket by solution manager.
    I was thinking about updating SPAM/SAINT by downloading newest version and perform the update in SPAM transaction, but option 'Import SPAM/SAINT update' for some reason is disabled. Why? What can I do to go ahead with update?
    Thanks in advance.

    Indeed using client 000 it is enabled. Firstly I had some errors with tpparam, but already fixed it. Now I'm facing:
    A newer version of data type "PAT10B" was found than one required
    Program: SAPLOCS_ALM
    Include: LOCS_ALMU03
    Row: 197
    Module type: (FUNCTION)
    Module Name: OCS_ALM_REPORT_QUEUE_STATUS
    anyone could help?

  • 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.

  • SPAM Version Check Issue

    Hi all, I am in process to update my production with EHP5 and I have a weird issue. Right now on my ECC 6 system 700 I am at the version 44 witch is the latest one. During the phase SPAM Check version, I have the following thing :
    SPAM version 44 in your source system is sufficient for this installation.
    Nevertheless, we recommend that you import the latest SPAM update.
    The program has not found a SPAM Update for release 700 in the EPS inbox.
    SPAM update message: SPAM/SAINT update SAPKD70044 has already been imported successfully
    Well I have the option to choose Search for newer version in /usr/sap/trans/EPS/in and Skip SPAM update ...
    If I choose Skip SPAM update and click continue, I loop on the SPAM version Check and I not able to go to the next phase. I do this procedure in DEV and QAS and I never had this issue before ?
    Help will be appreciate
    regards

    Dear Marc,
    This phase should be skipped without problems.
    Something is wrong in the ehpi gui...
    My suggestion is to reset the phase "Configuration".
    This can be done by clicking on the "back" button. This will reset only the phase "Configuration" and not the entire EHP Installation.
    Incase, the back button is deactivated, may I request to exit the Installer by clicking on the "Cancel" button, and trigger the sapehpi installer again which should then display the "back" button.
    Please then repeat the phase "Configuration".
    Regards,
    Abhishek

  • Support Package still running in Import_proper phase ( KB70017)

    Dear all,
    When i appling  Basis Support Package ( KB70017) , still its running the import_proper phase and its running around 12 hours .
    kindly suggest me to resolve the issue
    Regards

    Dear all ,
    i applied Basis Patch it took long time and still its not complete so i restart the server .
    now i cant able to login SAP its giving Syntax error kindly advise me
    i found these are the logs in this directory usr\sap\trans\tmp logs
    1 , UMODPROT.SID log
    ETN080X*************************************************************************
    1 E0U531 "Report RSUMODSP (modified objects)"
    1 ETN252     Start date: "15.01.2010"
    1 ETN253     Start time: "11:40:03"
    1 ETN080 *************************************************************************
    3 E0U531 "Analysis for OCS Package Queue:"
    3 E0U531 "SAPKB70017"
    3 E0U531X"Special handling of SORTTABS tables..."
    3 E0U532X"Check objects of request" "SAPKB70017"
    3 E0U531X"Update modification information..."
    3 E0U531X"Summary:"
    3 E0U531 "No modified SAP objects found"
    1 ETN080X*************************************************************************
    1 E0U531 "Report RSUMODSP (modified objects)"
    1 ETN252     Start date: "15.01.2010"
    1 ETN253     Start time: "11:53:07"
    1 ETN080 *************************************************************************
    3 E0U531 "Analysis for OCS Package Queue:"
    3 E0U531 "SAPKB70017"
    3 E0U531X"Special handling of SORTTABS tables..."
    3 E0U532X"Check objects of request" "SAPKB70017"
    3 E0U531X"Update modification information..."
    3 E0U531X"Summary:"
    3 E0U531 "No modified SAP objects found"
    AMODPROT.SID log
    1 E0U532 "Report RSUMOD10_SP" "(Classification of Modified Objects)"
    1 ETN252     Start date: "15.01.2010"
    1 ETN253     Start time: "11:54:57"
    1 ETN080 *************************************************************************
    3 E0U533X"Fetch objects to be adjusted" "(SPDD)" "from UMODOBJ..."
    4 E0U533 "Fetch objects from request" "SAPKB70017" "..."
    3 E0U532 "0" "objects to be adjusted were fetched"
    CMODACT.SID log
    ETN085X"OCS Package Queue Import:" "15.01.2010" "10:23:11" " "
    1 ETN085 "(De)activate customer exits:" " " " " " "
    1 ETN085X"OCS Package Queue Import:" "15.01.2010" "11:23:22" " "
    1 ETN085 "(De)activate customer exits:" " " " " " "
    IMODPROT.SID log
    1 E0U532 "Report RSUMOD20_SP" "(Special Handling of IS Tables)"
    1 ETN252     Start date: "15.01.2010"
    1 ETN253     Start time: "09:45:14"
    1 ETN080 *************************************************************************
    Regards
    1 ETN080X*************************************************************************
    1 E0U532 "Report RSUMOD20_SP" "(Special Handling of IS Tables)"
    1 ETN252     Start date: "15.01.2010"
    1 ETN253     Start time: "11:08:39"
    1 ETN080 *************************************************************************
    1 ETN080X*************************************************************************
    1 E0U532 "Report RSUMOD20_SP" "(Special Handling of IS Tables)"
    1 ETN252     Start date: "15.01.2010"
    1 ETN253     Start time: "11:54:58"
    1 ETN080 *************************************************************************

  • Missing spam version on service marketplace

    Hi *,
    i have spam-version 700/0024 installed on SAP Netweaver 7.
    I tried to get updates for spam but I only get the last 3 update available.
    Version 26, 27 and 28.
    If I understand everything correct I need also the version 25 (sapkd70025) to make a update to version 28.
    Is this correct. If so where can I get version 25 ?
    thanks in advance
    Dirk

    Hello Dirk,
    Please directly install the last SPAM 28.
    It should work without any problem.
    http://help.sap.com/saphelp_nw04/helpdata/en/d7/56e89a884b11d2b422006094b9ea64/content.htm
    Best regards,
    Olivier
    Edited by: Olivier Vanderperre on Jul 2, 2008 4:10 PM

Maybe you are looking for