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.

Similar Messages

  • 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

  • Support Pack upgrade error in Import Phase

    Hello,
    Currently I am upgrading SCM system with Support pack level 12 to 20 . When i am applying Basis 12 to 20. I got an error in Import_Proper phase.
    Could you please help me on this? I tried and still searching solution for this..But no luck...
    Os is : AIX and
    Log File:                /usr/sap/trans/log/SAPIB70013.xxx
    Main import
    Transport request   : SAPKB70013
    System              : xxxx
    tp path             : tp
    Version and release: 372.04.71 700
    child process 934006 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_report_interface
    fcode:      CLOSE_LINE_MODE
    tabname:    SOURCE
    len (char): 40
    key:        CL_OBJECT_COLLECTION==========CT
    retcode:    1
    SQL error -913 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
    child process 1212554 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_report_interface
    fcode:      CLOSE_LINE_MODE
    tabname:    SOURCE
    len (char): 40
    key:        CL_WDR_APPLICATION_WINDOW=====CT
    retcode:    1
    SQL error -913 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
    child process 1171520 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_report_interface
    fcode:      CLOSE_LINE_MODE
    tabname:    SOURCE
    len (char): 40
    key:        CL_WDY_MD_EVENT_SOURCE========CI
    retcode:    1
    SQL error -913 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
    child process 1331412 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_xrtab
    fcode:      RT_MI_LOAD
    tabname:    ECSCR_DATA
    len (char): 106
    key:        EC_TEST_DATA                  00000000P10                           IECATTDEFAULT
    retcode:    1
    SQL error -904 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
    insert / update sequence failed due to an error in DBI.
    maybe there's a concurrent process which inserted this table entry at the same time.
    insert / update sequence failed due to an error in DBI.                       
    maybe there's a concurrent process which inserted this table entry at the same time.
    child process 1310922 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_xrtab
    fcode:      RT_MI_END
    tabname:    WDY_APP_PROPERTY
    len (char): 64
    key:        DEMO_UIEL_DROPDOWN_BY_IDX     DEMO_VIEW
    retcode:    1
    SQL error -904 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
    import portion 018446 - 999999 not imported because the child processes died for unknown reason
    child process 1310924 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_report_interface
    fcode:      CLOSE_LINE_MODE
    tabname:    SOURCE
    len (char): 40
    key:        CL_WDY_MD_OUTGOING_EVENT======CT
    retcode:    1
    SQL error -913 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
    child process 1286192 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_xrtab
    fcode:      RT_MI_LOAD
    tabname:    ECSCR_DATA
    len (char): 106
    key:        EC_TEST_DATA                  00000000P10                           IECATTDEFAULT
    retcode:    1
    SQL error -904 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
    import portion 009158 - 018411 not imported because the child processes died for unknown reason
    import portion 018412 - 018527 not imported because the child processes died for unknown reason
    import portion 018528 - 999999 not imported because the child processes died for unknown reason
    sap_dext called with msgnr 1:
    db call info -
    function:   db_xrtab
    fcode:      RT_MI_LOAD
    tabname:    ECSCR_DATA
    len (char): 106
    key:        EC_TEST_DATA                  00000000P10                           IECATTDEFAULT
    retcode:    1
    SQL error -904 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
    Main import
    End date and time : 20100909034914
    Ended with return code:  ===> 12 <===
         |   ######################################                     
    Thanks and Regards,
    Sankar
    SAP BASIS Consultant

    Hi,
    Thanks for you reply. I restarted import but no luck still. I activated some object also not working. when i call SPAM it is not going to the SPAM pager. Showing dump...
    Runtime Errors         CALL_FUNCTION_NOT_FOUND
    Except.                CX_SY_DYN_CALL_ILLEGAL_FUNC
    Date and Time          10.09.2010 09:41:37
    Short text
         Function module "POSS_UIREQ_OPT_SUBMIT" not found.
    What happened?
         The function module "POSS_UIREQ_OPT_SUBMIT" is called,
         but cannot be found in the library.
         Error in the ABAP Application Program
         The current ABAP program "SAPLSTXC" had to be terminated because it has
         come across a statement that unfortunately cannot be executed.
    Error analysis
         An exception occurred that is explained in detail below.
         The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_FUNC', was
          not caught in
         procedure "OPEN_FORM" "(FUNCTION)", nor was it propagated by a RAISING clause.
         Since the caller of the procedure could not have anticipated that the
         exception would occur, the current program is terminated.
         The reason for the exception is:
         The program "SAPLSTXC" contains the CALL FUNCTION statement.
         The name of the function module to be called is "POSS_UIREQ_OPT_SUBMIT".
         No function module exists with the name "POSS_UIREQ_OPT_SUBMIT".
         All function modules are listed in the Function Library (SE37).
    Possible reasons:
    a) Wrong name specified. Pay particular attenti
        upper/lower case and underscores ("_").
        or
    b) Transport error
    c) In the case of an enqueue/dequeue module,
        the lock object may not have been activated
        (ABAP/4 Dictionary).
    When i tried to check function module it is not there..
    Could you please help on this?
    Regards,
    Sankar Basis Consultant

  • Error in the phase IMPORT_PROPER while applying support packages

    Dear All,
    I am on ECC 6.0(ABAP+JAVA) SR2, SUSE Linux 10 SP1, DB2.
    I have successfully applied the kernel patch and started applying the support packages,  i have successfully completed applying the ABAP, Basis, BW, HR and other related patches, but i am not sure why i am stuck at the import_proper phase when applying the SAP_APPL patches (SAPKH60008 and SAPKH60009 both in the same queue) and my tp log is as follows
    ========================================================================================================
    START imp all              SCD        20081229080538              DDIC         sealcpro 20081229080537
    INFO: event SAP_IMPORT_START triggered successfully
    INFO  TBATG CONVERSION OF  SCD N      not needed                  DDIC         sealcpro 20081229080537
    START tp_getprots          SCD P      20081229080539              DDIC         sealcpro 20081229080537
    2EETP000 sap_dext called with msgnr "1":
    2EETP000      db call info
    2EETP000 function:   db_setget
    2EETP000 fcode:      RT_SETB (65535)
    2EETP000 tabname:    TRBAT
    2EETP000 len (char): 0
    2EETP000 key:
    2EETP000 retcode:    1
    1AETP000 exit in function texitnow
    ERROR: EXIT(16) -> process ID is: 5319
    STOP  imp all              SCD   0016 20081229080602              DDIC         sealcpro 20081229080537
    =========================================================================================================
    And also when i look at the Support package import logs they show that
    TEST IMPORT
    Import ABAP Dictionary Objects and
    ABAP Dictionary Activation phases ended with return code 4
    But i dont think this can give any problem.
    I have tried to import from the phase where it stopped, but all of a sudden i get disconnected from SAP and get an error message saying that NO CONNECTION TO THE DATABASE, then when i check for the processes for dw and db2 there are process already running.
    I had to start SAP and only then i was able to connect to the SERVER again.
    Can you please help me on this..
    For any more information plz let me know
    Thanks and regards
    Hunky

    Dear Balaji,
    Thank you very much for the reply...
    I deleted the import request in the STMS and wi ran the RDDIMPDP and RDDMNTAB reports and restart the SPAM, but this time the SPAM immediately stopped, but i am still connected to the system and the error which i got earlier (database connection error ) is now not occuring.
    But otherwise also i noticed that i get the following ABAP Dump while this error is triggering
    ===================================================================
    DBIF_REPO_INTERNAL_ERROR
    Internal error when accessing program "CX_SY_OPEN_SQL_DB=============CP ".
    An unspecified internal error occurred in the SAP-internal
    database interface.
    For further analysis the SAP system log should be examined
    (transaction SM21).
    Check the entries in the developer trace of the relevant work process
    (transaction ST11).
    Attempted to access component "LOAD" of program
    "CX_SY_OPEN_SQL_DB=============CP ".
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "DBIF_REPO_INTERNAL_ERROR" " "
    "SAPLSTPA" or " "
    ==========================================================================
    Based on this error i searched few notes and got the below results 309583 and 132383 but these are not for my release.
    So i request you to kindly help me on this as i am running out of time in delivering my server.
    Waiting for all the valuble replies
    Thank you in advance
    Regards
    Hunky

  • Basis patch IMPORT_PROPER error

    Hi All,
    Iam applying  basis patch 12 .
    I have done this on other system with no problem, but on the
    current one, it seems to hang on the "imp all" step (displayed
    next to the spinning clock.
    I opened another session I canceled spam transaction.
    it is giving error.
    Import_proper.
    How to overcome this problem.
    Regards
    Siva

    Hi Markus & sunil,
    I applied patch, But problem is same.
    APQUA:oraeqa> /oracle/EQA/102_64/OPatch/opatch apply
    Invoking OPatch 10.2.0.2.0
    Oracle interim Patch Installer version 10.2.0.2.0
    Copyright (c) 2005, Oracle Corporation.  All rights reserved..
    Oracle Home       : /oracle/EQA/102_64
    Central Inventory : /oracle/oraInventory
       from           : /oracle/EQA/102_64/oraInst.loc
    OPatch version    : 10.2.0.2.0
    OUI version       : 10.2.0.2.0
    OUI location      : /oracle/EQA/102_64/oui
    Log file location : /oracle/EQA/102_64/cfgtoollogs/opatch/opatch-2008_Nov_06_13-
    42-32-CST_Thu.log
    ApplySession applying interim patch '5099990' to OH '/oracle/EQA/102_64'
    Invoking fuser to check for active processes.
    Invoking fuser on "/oracle/EQA/102_64/bin/oracle"
    OPatch detected non-cluster Oracle Home from the inventory and will patch the lo
    cal system only.
    Please shutdown Oracle instances running out of this ORACLE_HOME on the local sy
    stem.
    (Oracle Home = '/oracle/EQA/102_64')
    Is the local system ready for patching?
    Do you want to proceed? [y|n]
    y
    User Responded with: Y
    Backing up files and inventory (not for auto-rollback) for the Oracle Home
    Backing up files affected by the patch '5099990' for restore. This might take a
    while...
    Backing up files affected by the patch '5099990' for rollback. This might take a
    while...
    Patching component oracle.rdbms, 10.2.0.2.0...
    Updating archive file "/oracle/EQA/102_64/lib/libserver10.a"  with "lib/libserve
    r10.a/opiexe.o"
    Updating archive file "/oracle/EQA/102_64/lib/libserver10.a"  with "lib/libserve
    r10.a/opitsk.o"
    Updating archive file "/oracle/EQA/102_64/lib/libcommon10.a"  with "lib/libcommo
    n10.a/ttcclr.o"
    Running make for target ioracle
    ApplySession adding interim patch '5099990' to inventory
    Verifying the update...
    Inventory check OK: Patch ID 5099990 is registered in Oracle Home inventory with
    proper meta-data.
    Files check OK: Files from Patch ID 5099990 are present in Oracle Home.
    The local system has been patched and can be restarted.
    OPatch succeeded.
    SAPQUA:oraeqa>
    Regards
    Siva

  • Error in XPRA_EXECUTION phase while upgrading patch in solman 7.0.

    Hi all,
    I was upgrading solman system( 7.0 ) from patch level 10 to patch level 13 , while upgrading it throwed error in XPRA_EXECUTION phase. Error is in SAPK-40003INCPRXRPM and SAPK-40004INCPRXRPM.
    Error log is as given below :
    Post-import method SWO_OBJTYPE_AFTER_IMPORT started for SOBJ L, date and time: 20090415070141
    Object type 'BUS2178' generated successfully
    Object type 'BUS2177' generated successfully
    Object type 'BUS2176' generated successfully
    Object type 'BUS2175' could not be generated
    The type 'DPR_SCHEDULING' is unknown.
    Object type 'BUS2174' could not be generated
    The type 'DPR_SCHEDULING' is unknown.
    Object type 'BUS2173' could not be generated
    The type 'DPR_SCHEDULING' is unknown.
    Object type 'BUS2172' could not be generated
    Please help me out as i am stuck.

    HI,
    Did u check is there any dependencies of Solman support packages with other support pakckages.
    Object type 'BUS2174' could not be generated it seems there is a issues with dependencies only.
    Please check the stack guide once then u will come to know all the dependencies.
    -Srini

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

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

  • Problem with Support Package SAP_BASIS (Error Stop) IMPORT_PROPER

    Hi Everyone,
    i want to apply Support Pack for SAP_BASIS. Now Its Level is 0009 (ECC 6.0).
    i did import the SPs SAPKB70010 and SAPKB70011. We only want until Stack 11.
    The test scenario was without an error. But during the Standard scenario there occurred a problem:
    SPAM Status: Error Stop
    Import Phase: IMPORT_PROPER
    I guess there are different reasons:
    1) We didn´t make a SPAM update before! it´s still version 7.00/0021.
    2) I have no idea if the guy before me made a kernel update.
    And now i wanted to update SPAM to version 27. but first i should "repair" this problem because the SAP_BASIS is still in the queue.
    Is there a possibility to delete the queue, update SPAM and the Kernel and then try it again with this support package?
    We cannot go further than Stack 11!
    please help me!

    Hi,
    This is not because of SPAM version nor the upgrade of kernal.If that was a SPAM problem then it will
    not allow you to define the queue.
    There are some know problems with this basis patches please read the note .Just run the import again this error would not occur.
    If this error occurs  then post the import logs for further analysis.
    Regards,
    Vamshi.

  • Error in XPRA_EXECUTION phase in instalation BI_CONT 3.53

    Hello,
    After installing SAP Netweaver 04 as ABAP i am Installing Add-on
    BI_CONT Rel.353 : Import of the queue -
    via SAINT Tcode.
    Now it is in error in XPRA_EXECUTION Phase of pkg
    SAPKIBIFQ4 BI_CONT 353: patch 0014.
    Error is in Method Execution step:
    InfoObject 0GRC_CSEOWR, version D being deleted, (basic char. not
    found)
    Start of the after-import method for object type R3TR DTMP ( )
    Errors occurred during post-handling RS_AFTER_IMPORT_D for DUPD L
    RS_AFTER_IMPORT_D belongs to package RS
    The errors affect the following components:
    BW-WHM (Warehouse Management)
    Post-import method RS_AFTER_IMPORT_D completed for DUPD L, date and
    time: 20080103122305
    Pls help me ASAP to resolve this error.
    Regards,
    Ankita

    Hi,
    I solved this problem after implementing
    Note 1083886 - Method IF_FDT_EXPRESSION~IS_GENERATING is not implemented.
    is thsi dosent work try restarting the queue again.
    Kind regards,
    Vamsi

  • 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

  • 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

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

  • 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

  • Error in TP_ACTION_CP2STRIG phase ERP 6 EHP4

    Hi all,
    I have a error in TP_ACTION_CP2STRIG phase, please check the error..
    SAPEBBQ701.GE3
    3 ETW685Xstart copying of "R3TRTABUKSML" ...
    4 ETW000 Mon Jul 26 09:36:14
    2010 104301412 359.495280
    4 ETW000 OCIStmtExecute() failed with
    -1=OCI_ERROR 26 359.495306
    4 ETW000 SQL error
    942: 17 359.495323
    ***4 ETW000 **LOG BZA=>table KSML~ does not**
    *exist on database *
    4
    ETW000
    69 359.495392
    2EETW000 sap_dext called with msgnr "2":
    2EETW000 -
    db call info -
    2EETW000 function: db_xrtab
    2EETW000 fcode: RT_INSERT
    2EETW000 tabname: KSML~
    2EETW000 len (char): 182
    2EETW000 key: 00099999900000010000
    99999493990000000000100 00000000 000
    2EETW000 retcode: 2
    2EETP200 Export with errors, request will not be imported
    1 ETP150 MAIN EXPORT
    1 ETP110 end date and time : "20100726093614"
    1 ETP111 exit code : "12"
    1 ETP199 ######################################
    4 EPU202XEND OF SECTION BEING ANALYZED
    Thank you
    Rogério

    Hi,
    I used the latest version of R3trans but the problem not solved.
    I used the SAPEHP Inst with the patch 32 but the problem not solved.
    In outhers ERP system with EHP 4 the table KSML~ not exist.
    The OSS with SAP opened.
    Thank you.
    Rogério

Maybe you are looking for