DDIC_TYPE_INCONSISTENCY during Support Package import

Hi,
we are in the process of importing SPS 11+12 into our R/3 system. Phase 'move nametabs' has been hanging for a few hours. When trying to create another session or log in we get an ABAP runtime error DDIC_TYPE_INCONSISTENCY even before the log in screen comes up.
In the dev_w* tracefile we see the same error and RABAX messages.
We have stopped SAP, no problem, deleted the SQL packages, the system is back up, means all WP's are running, but we still get the same errors.
I have created a ticket with SAP, but as this is not a Production system, I am afraid they are not coming back soon enough for us.
If anybody has a good idea what else we can try.
Thanks,
Ingrid

Hi,
I wanted to give a quick update.
We had done SPS11 and 12 together in our sandbox without any issues, but with a different kernel. Not sure this was the issue, but during phase 'move nametabs' something went wrong which caused the inconsistency between the database and the dictionary. We still don't know what it was, but we had to restore the system and do a reclstg.
Regards,
Ingrid

Similar Messages

System shutdown during support package import

We were importing a BASIS support package in our system. Then for other reasons the system shutdown in the IMPOR_PROPER phase so...the system now is corrupted.
We try to launch the import of support package again from SAP GUI but we can not, a dump is generated everytime.
Are there a posibility of launch the import from operating system to finalice the aplication of package?what are the commands to do that?
We try to avoid the recovery from backup
Regards

Hi,
I don't think it is possible other than backup restore.
But already you are at worst case..i will suggest you to check the data in PAT01 and PAT03 tables at database level.
And delete all the contents from those tables then retry to login.
*Open a support message
Regards,
Nick Loy

Problem with support package import SAPKNA7018

Hi Experts,
I have installed CRM 7.0 support release 1. After that,I have successfully imported the following components SAPKA70107 (level 7), SAPKB70107 (level 7), SAPK-70107INPIBASIS (level 7), SAPKW70107 (level 7) and SAPK-70108INSAPBSFND (level 8). Also, SAP_AP: SAPKNA7016 & SAPKNA7017 have been imported successfully.
I facing the below issue while trying to import SAPKNA7018. (As it is CRM I am importing with CRM Support Package Manager wizard.)
Prerequiste     Log. AND      Prerequisite      Prereq typ       Package Description
SAPKW701??      1           SAPKNA7018       P                     Could not find an equivalent
But already SAP_BW patch is successfully upgraded to level 7 (SAPKW70107).
While checking PAT07 table it is showing dependancy as:
PATCH                CONJUNCT SEQUENCE REQ_TYPE REQUMENT                                 CONFLICT_R TRUTH FLAG DESCRIPT
SAPKNA7018           01       001      A        SAP_AP,700                                          T
SAPKNA7018           01       002      P        SAPKNA7017                                          T          SAP_AP,700,0017
SAPKNA7018           01       003      A        SAP_BW,700                                          T
SAPKNA7018           01       004      P        SAPKW70022                                          T          SAP_BW,700,0022
No idea, why dependency is on SAPKW70022 while it is already in SAPKW70107 level. For other landscapes we never faced this error while did the same patching. Could anyone give some clue on this?
Thanks & Regards,
Sujit.

Hi Experts,
Please share your thoughts. The issue is still persisting.
Any help is appreciated.
Thanks & Regards,
Sujit.

Short dump in every transaction during support pack import - Solution Mgr

I am in the middle of applying support packs SP13 and SP14 for Solution Manager. In SPAM, during the import, I received short dumps. I get short dump for all transactions. The error message is 'Syntax error in program "SAPLWB_CUSTOMIZING", Field "G_DC_TABSTR" is unknown in INCLUDE LWB_CUSTOMIZINGDEV'.
Please help. Thanks !

Hi
My first question, would be, why are you performing other activities while importing patches?
This is not recommended.
Rahul

Support Package Import Error in ECC 6.0 SR2

Hi,
We tried to upgrade EA-GLTRADE in our ECC 6.0 SR 2 system with
SAPKGPGD07 patch during which, we encounter with some error at
DDIC_ACTIVATION. (Attached: Entire Log)
Note:
We have already updated the Kernal with latest patch and SPAM with
latest version 7.00/0023.
We also applied dependency patches for SAPKGPGD07.
Please give us the steps to resolve it or to reset the Queue so that
atleast we can continue with other patches
Thanks,
Vignesh P,
Log from Log File:
ides\sapmnt\trans\log\SAPAGPGD07.I01
Log File:
ides\sapmnt\trans\log\SAPAGPGD07.I01
        ABAP Dictionary: Activation
        Transport request   : SAPKGPGD07
             System              : I01
        tp path             : tp
        Version and release: 370.01.01 700
     3T             Program start============================================================
        Mass Activation
        =========================================================================
             Process..................: ides_9
        User.....................: DDIC
        Date, time...............: 20.04.2007, 17:14:35
        Platform.................: CUSTOMER-I01(700)/MSSQL/WindowsNT/ides
        Tool.....................: BATCH/RADMASG0
        Log......................: F,
ides\sapmnt\trans\tmp\SAPAGPGD07.I01
        Program parameters:
        Input Medium...............: Transp. Request SAPKGPGD07
        Activation Method..........: Inactv.
        Chk Mode...................: T
        Version to be activated....: M
        Versions to be deleted.....: Delete Only Active Versions
        Lock Against Paral. Exec...: Shared
        Independent Statistics Log.: being written
        Parallel Mode..............: Switched on
        ..Resources................: 50% of Dialog Processes, Maximum 4 Processes
        .Costs for Each Task.......: Minimum: 3.000, Maximum: 150.000
        =========================================================================
        Number of objects to be analyzed: 121
        Number of relevant dependencies: 108
        Level 1:42 objects assigned, 52 less dependencies
        Level 2:34 objects assigned, 35 less dependencies
        Level 3:27 objects assigned, 10 less dependencies
        Level 4:7 objects assigned, 7 less dependencies
        Level 5:7 objects assigned, 4 less dependencies
        Level 6:4 objects assigned, 0 less dependencies
        Graph_Analysis: 121 objects on 6 topological levels
        Start phase 001 **********************************************************
              Object Activation
     3T             *** Activate objects at level 1
Parallel execution with maximal 3 concurrent tasks *
        Total of 42 objects with 28.630 costs in 8 tasks
     3T             Activate data element WB2_DEFAULT_TEW
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
     3T             Activate data element WB2_FIELD
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
     3T             Activate data element WB2_KBETR_BAPI
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
     3T             Activate data element WB2_KBETR_SCALE_BAPI
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
     3T             Activate data element WB2_KOMXWRT_BAPI
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
     3T             Activate data element WB2_KSTBW_SCALE_BAPI
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
     3T             Activate data element WB2_ORDER_KEY
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
        Activate table BAPITCCOND
        Table BAPITCCOND was activated successfully
        Activate table BAPITCCONDCX
        Table BAPITCCONDCX was activated successfully
        Activate table BAPITCCONDD
        Table BAPITCCONDD was activated successfully
        Activate table BAPITCCONDDCX
        Table BAPITCCONDDCX was activated successfully
        Activate table E1BPTCCOND
        Table E1BPTCCOND was activated successfully
        Activate table E1BPTCCONDCX
        Table E1BPTCCONDCX was activated successfully
        Activate table E1BPTCCONDD
        Table E1BPTCCONDD was activated successfully
        Activate table E1BPTCCONDDCX
        Table E1BPTCCONDDCX was activated successfully
        Activate table KOMEXPENSE
        Table KOMEXPENSE was activated successfully
        Activate table KOMTCKO
        Table KOMTCKO was activated successfully
        Activate table KOMTCKOCX
        Table KOMTCKOCX was activated successfully
        Activate table KOMTCKOE
        Table KOMTCKOE was activated successfully
        Activate table KOMWBHIE_NEW
        Table KOMWBHIE_NEW was activated successfully
        Activate table KOMWBHKEX_NEW
        Table KOMWBHKEX_NEW was activated successfully
        Activate table KOMWBHKE_NEW
        Table KOMWBHKE_NEW was activated successfully
        Activate table WB2_CHANGED_FIELDS
        Table WB2_CHANGED_FIELDS was activated successfully
        Activate table WB2_COND_MAP
        Table WB2_COND_MAP was activated successfully
        Activate table WB2_KONV_SELECT
        Table WB2_KONV_SELECT was activated successfully
        Activate table WB2_SCALE_EXTERNAL
        Table WB2_SCALE_EXTERNAL was activated successfully
        Activate table WBHID_NEW
        WBHID_NEW-LGOBE: Table KOMWBHI in search help attachment differs from table of search field
        Table WBHID_NEW was activated successfully
        Activate table WCOCOH
        WCOCOH-RATE: Table KOMWCOCOH in search help attachment differs from table of search field
        Table WCOCOH was activated successfully
     3T             Activation of table type T681E_TAB
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
     3T             Activation of table type T6B2F_TAB
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
     3T             Activation of table type TB2BN_TAB
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
     3T             Activation of table type TB2BO_TAB
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
     3T             Activation of table type TB2BP_TAB
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
     3T             Activation of table type TWBACCTYPE_TAB
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
     3T             Activation of table type TWBEXCLASSGROUP_TAB
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
     3T             Activation of table type WB2_BAPIRET2_TAB
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
     3T             Activation of table type WB2_CONDSCALE_STAB
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
     3T             Activation of table type WB2_CONDSCALE_TAB
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
     3T             Activation of table type WB2_KONH_STAB
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
     3T             Activation of table type WB2_KONP_STAB
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
     3T             Activation of table type WB2_KONP_TAB
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
     3T             Activation of table type WB2_VAKE_TAB
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
        Server Usage ************************************************************
          Server..............     Workp     Tasks     Error     .Timesum     Objcount     ms/Obj     ..KCosts     ms/KCs
          ides_I01_00.........     ....3     ....8     .....     .....106     ......42     .2.524     ......29     .3.655
             Parallel execution: 38 sec., Phase out time: 8 sec., Load: 9,2982456140350877E+01 percent
     3T             *** Activate objects at level 2
Parallel execution with maximal 3 concurrent tasks *
        Total of 34 objects with 28.040 costs in 8 tasks
        Activate table APPEND_KOMWBHKEX
          8R      Enhancement category for table missing
     8R      Enhancement category for include or subtype missing
        Table APPEND_KOMWBHKEX was activated with warnings
        Activate table BAPITCCONDITIONITEM
        Table BAPITCCONDITIONITEM was activated successfully
        Activate table BAPITCCONDITIONITEMO
        Table BAPITCCONDITIONITEMO was activated successfully
        Activate table BAPITCCONDITIONITEMX
        Table BAPITCCONDITIONITEMX was activated successfully
        Activate table BAPITCCONDITIONKEY
        Table BAPITCCONDITIONKEY was activated successfully
        Activate table BAPITCCONDITIONKEYO
        Table BAPITCCONDITIONKEYO was activated successfully
        Activate table BAPITCCONDITIONKEYX
        Table BAPITCCONDITIONKEYX was activated successfully
        Activate dependent table KOMWBHIE_APPEND
        Activation of dependent table KOMWBHIE_APPEND successful
        Activate dependent table KOMWBHKE_APPEND
        Activation of dependent table KOMWBHKE_APPEND successful
        Activate dependent table KOMWCOCOH
        Activation of dependent table KOMWCOCOH successful
        Activate dependent table KOMWCOCOH_LI
        KOMWCOCOH_LI-RATE: Table KOMWCOCOH in search help attachment differs from table of search field
        Activation of dependent table KOMWCOCOH_LI successful
        Activate table TWGTA
        Table TWGTA was activated successfully
        Activate table WB2_KOMG
          8O      WB2_KOMG-ZZANZ_KG (combination reference table/field WB2_KOMG-ZZME_KG does not exist)
          8O      WB2_KOMG-ZZAUFMENG_KG (combination reference table/field WB2_KOMG-ZZME_KG does not exist)
     8R      Flag: 'Incorrect enhancement category' could not be updated
        Table WB2_KOMG was not activated
        Activate dependent table WBHID_APPEND
        Activation of dependent table WBHID_APPEND successful
     3T             Activation of table type KOMEXPENSE_TAB
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
        Activate dependent table type TABKOMTCKO
        Activate dependent table type TABKOMTCKOCX
     3T             Activation of table type WB2B_FIELD_TAB
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
     3T             Activation of table type WB2_CHANGED_FIELDS_STAB
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
     3T             Activation of table type WB2_COND_MAP_STAB
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
     3T             Activation of table type WB2_SCALE_EXTERNAL_STAB
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
        Activate dependent table type WCB_WCOCOH_STAB
        Activate dependent table type WCB_WCOCOH_TAB
        Activate dependent view DB_WCOCOA
             View must be deleted from the database and created again
        Activate dependent view DB_WCOCOA_JEST
             View must be deleted from the database and created again
        Activate dependent view DB_WCOCOH_I_ST
             View must be deleted from the database and created again
        Activate dependent view V_WCOCOA_CUS_LST
        Check dependent search help WCB_SH_CC_NUM_CUS_LST_HEADER
        Search help WCB_SH_CC_NUM_CUS_LST_HEADER is consistent
             View must be deleted from the database and created again
        Activate dependent view V_WCOCOA_VEN_LST
        Check dependent search help WCB_SH_CC_NUM_VEN_LST_HEADER
        Search help WCB_SH_CC_NUM_VEN_LST_HEADER is consistent
             View must be deleted from the database and created again
        Activate dependent view V_WCOCOH_CUS_LST
        Check dependent search help WCB_SH_CC_NUM_CUS_LST_A
        Search help WCB_SH_CC_NUM_CUS_LST_A is consistent
             View must be deleted from the database and created again
        Activate dependent view V_WCOCOH_VEN_LST
        Check dependent search help WCB_SH_CC_NUM_VEN_LST_A
        Search help WCB_SH_CC_NUM_VEN_LST_A is consistent
             View must be deleted from the database and created again
        Server Usage ************************************************************
          Server..............     Workp     Tasks     Error     .Timesum     Objcount     ms/Obj     ..KCosts     ms/KCs
          ides_I01_00.........     ....3     ....8     .....     .....171     ......34     .5.029     ......28     .6.107
             Parallel execution: 82 sec., Phase out time: 44 sec., Load: 6,9512195121951223E+01 percent
     3T             *** Activate objects at level 3
Parallel execution with maximal 3 concurrent tasks *
        Total of 28 objects with 20.340 costs in 6 tasks
        Activate dependent search help WCB_SH_CC_NUM_CUS_LST_A
        Activate dependent search help WCB_SH_CC_NUM_CUS_LST_HEADER
        Activate dependent search help WCB_SH_CC_NUM_VEN_LST_A
        Activate dependent search help WCB_SH_CC_NUM_VEN_LST_HEADER
        Activate table BAPITCSCALE
        Table BAPITCSCALE was activated successfully
        Activate table BAPITCSCALEO
        Table BAPITCSCALEO was activated successfully
        Activate dependent table KOMWBHIE
        Activation of dependent table KOMWBHIE successful
        Activate dependent table KOMWBHKE
        Activation of dependent table KOMWBHKE successful
        Activate dependent table KOMWBHKEX
             Append structure APPEND_KOMWBHKEX appended to table KOMWBHKEX
     8R      Enhancement category 2 possible, but include or subty. not yet classified
        Activation of dependent table KOMWBHKEX successful
        Activate table WB2_COND_CHANGE
        Table WB2_COND_CHANGE was activated successfully
        Activate table WB2_KEY_CHANGE
          8O      INCLUDE table WB2_KOMG is not active
          8O      Routine EXPAND (Table WB2_KEY_CHANGE could not be expanded)
        Table WB2_KEY_CHANGE was not activated
        Activate table WB2_KOMG_EXT
        Table WB2_KOMG_EXT was activated successfully
        Activate dependent table WBHID
        Activation of dependent table WBHID successful
        Activate dependent table type KOMWCOCOH_LI_TAB
        Activate dependent table type KOMWCOCOH_STAB
     3T             Activation of table type WB2_BAPITCCONDITIONITEMO_TAB
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
     3T             Activation of table type WB2_BAPITCCONDITIONITEMX_TAB
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
     3T             Activation of table type WB2_BAPITCCONDITIONITEM_TAB
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
     3T             Activation of table type WB2_BAPITCCONDITIONKEYO_TAB
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
     3T             Activation of table type WB2_BAPITCCONDITIONKEYX_TAB
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
     3T             Activation of table type WB2_BAPITCCONDITIONKEY_TAB
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
        Activation of table type WB2_KOMG_STAB
          8O      Row type WB2_KOMG is not active or does not exist
        Table type WB2_KOMG_STAB was not activated
        Activate dependent table type WCB_DB_WCOCOA_JEST_STAB
        Activate dependent table type WCB_DB_WCOCOA_STAB
        Activate dependent table type WCB_DB_WCOCOH_I_ST_STAB
        Activate view V_TWGTA
        Activate dependent view V_TWGTA_CFM
        Server Usage ************************************************************
          Server..............     Workp     Tasks     Error     .Timesum     Objcount     ms/Obj     ..KCosts     ms/KCs
          ides_I01_00.........     ....3     ....6     .....     ......45     ......28     .1.607     ......20     .2.250
             Parallel execution: 17 sec., Phase out time: 3 sec., Load: 8,8235294117647058E+01 percent
     3T             *** Activate objects at level 4
        Too low cost (3.270) for parallel processing. Minimum: 6.000
Synchronous execution, no parallel processing *
     3T             Activate dependent table KOMWBHI
        KOMWBHI-HKPSTP: Table KOMWBHK in search help attachment differs from table of search field
        Activation of dependent table KOMWBHI successful
        Activate dependent table type TABKOMWBHIE
     3T             Activation of table type WB2_BAPITCSCALEO_TAB
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
     3T             Activation of table type WB2_BAPITCSCALE_TAB
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
     3T             Activation of table type WB2_COND_CHANGE_STAB
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
        Activation of table type WB2_KEY_CHANGE_STAB
          8O      Row type WB2_KEY_CHANGE is not active or does not exist
        Table type WB2_KEY_CHANGE_STAB was not activated
     3T             Activation of table type WB2_KOMG_EXT_STAB
             Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
        Synchronous processing: 19 sec., 7 objects, 3.270 costs
     3T             *** Activate objects at level 5
        Too low cost (4.630) for parallel processing. Minimum: 6.000
Synchronous execution, no parallel processing *
     3T             Activate dependent table KOMWBHIH
        KOMWBHIH-HKPSTP: Table KOMWBHK in search help attachment differs from table of search field
        Activation of dependent table KOMWBHIH successful
     3T             Activate dependent table MCWBHI
        MCWBHI-HKPSTP: Table KOMWBHK in search help attachment differs from table of search field
        Activation of dependent table MCWBHI successful
        Activate dependent table WB2_NASTLIEF
        Activation of dependent table WB2_NASTLIEF successful
        Activate dependent table type KOMWBHI_TAB
        Activate dependent table type TABKOMWBHI
        Activate dependent table type TRCON_KOMWBHI_TAB
        Activate dependent table type WB2_KOMWBHI_STAB
        Synchronous processing: 27 sec., 7 objects, 4.630 costs
     3T             *** Activate objects at level 6
        Too low cost (2.160) for parallel processing. Minimum: 6.000
Synchronous execution, no parallel processing *
        Activate dependent table TRCON_OUTP_DBDATA
        Activation of dependent table TRCON_OUTP_DBDATA successful
        Activate dependent table type GT_MCWBHI
        Activate dependent table type KOMWBHIH_TAB
        Activate dependent table type WB2_NASTLIEF_TAB
        Synchronous processing: 2 sec., 4 objects, 2.160 costs
              Object Activation
        End phase 001 ***********************************************************
        Start phase 002 **********************************************************
              Final log
        Following objects not activated/deleted or activated/deleted w. warning:
     3T          8O      Table WB2_KEY_CHANGE could not be activated
     8O      Table WB2_KOMG could not be activated
     8O      Table Type WB2_KEY_CHANGE_STAB could not be activated
        (E- Row type WB2_KEY_CHANGE is not active or does not exist )
     8O      Table Type WB2_KOMG_STAB could not be activated
     8R      Table Type WB2_CHANGED_FIELDS_STAB was activated (error in the dependencies)
     8R      Table Type WB2_VAKE_TAB was activated (error in the dependencies)
     8R      Table APPEND_KOMWBHKEX was activated (warning for the dependent tables)
     8R      Table KOMWBHKEX_NEW was activated (warning for the dependent tables)
              Final log
        End phase 002 ***********************************************************
        Start phase 003 **********************************************************
              Statistics on Activated and Deleted Objects
        Number of objects to be activated............: 118
        Objects not activated........................: 4
        Activated objects with errors in dependencies: 2
        Objects activated with warning...............: 2
        Successfully activated objects...............: 110
        Number of objects to be deleted..............: 0
        Objects not successfully deleted.............: 0
        Successfully deleted objects.................: 0
        Tables/views with DROP/CREATE................: 0
        No. of them marked for DROP/CREATE: 0
        Not marked for DROP/CREATE: 0
        Number of nametabs to be deleted.............: 0
        Successfully deleted nametabs................: 0
        Nametabs that were not successfully deleted..: 0
              Statistics on Activated and Deleted Objects
        End phase 003 ***********************************************************
        =========================================================================
        Mass Activation
        =========================================================================
             Process..................: ides_9
        Return code..............: 8
        Phase 001..................: 00:03:05 (Object Activation)
        Phase 002..................: < 1 sec. (Final log)
        Phase 003..................: < 1 sec. (Statistics on Activated and ...)
        Program runtime..........: 00:03:20
        Date, time...............: 20.04.2007, 17:17:55
        Program end==============================================================
        ABAP Dictionary: Activation
        End date and time : 20070420171755
          8O      Ended with return code: ===> 8 <===
ALOG
ALL                  I01.ALL t 0000 20070419142033              DDIC         ides
SAPKD70022           I01.ALL m 0000 20070419142040 SAPUSER      DDIC         ides
SAPKD70022           I01.ALL L 0004 20070419142051 SAPUSER      DDIC         ides 20070419142042
SAPKD70022           I01.ALL P 0004 20070419142056 SAPUSER      DDIC         ides 20070419142053
SAPKD70022           I01.ALL H 0004 20070419142615 SAPUSER      DDIC         ides 20070419142100
SAPKD70022           I01.ALL A 0004 20070419142914 SAPUSER      DDIC         ides 20070419142100
ALL                  I01.ALL S 0000 20070419142929              DDIC         ides 20070419142100
ALL                  I01.ALL 6 0004 20070419142947              DDIC         ides 20070419142100
SAPKD70022           I01.ALL I 0004 20070419143215 SAPUSER      DDIC         ides 20070419142100
ALL                  I01.ALL n 0000 20070419143340              DDIC         ides 20070419142100
SAPKD70022           I01.ALL R 0000 20070419143413 SAPUSER      DDIC         ides 20070419142100
ALL                  I01.ALL t 0000 20070419145325              DDIC         ides
SAPKD70023           I01.ALL m 0000 20070419145327 SAPUSER      DDIC         ides
SAPKD70023           I01.ALL L 0004 20070419145330 SAPUSER      DDIC         ides 20070419145328
SAPKD70023           I01.ALL P 0004 20070419145332 SAPUSER      DDIC         ides 20070419145331
SAPKD70023           I01.ALL H 0004 20070419145350 SAPUSER      DDIC         ides 20070419145332
SAPKD70023           I01.ALL A 0004 20070419145432 SAPUSER      DDIC         ides 20070419145332
ALL                  I01.ALL S 0000 20070419145439              DDIC         ides 20070419145332
ALL                  I01.ALL 6 0000 20070419145443              DDIC         ides 20070419145332
SAPKD70023           I01.ALL I 0004 20070419145527 SAPUSER      DDIC         ides 20070419145332
ALL                  I01.ALL n 0000 20070419145529              DDIC         ides 20070419145332
SAPKD70023           I01.ALL R 0000 20070419145535 SAPUSER      DDIC         ides 20070419145332
ALL                  I01.ALL t 0000 20070419150805              DDIC         ides
SAPKB70010           I01.ALL m 0000 20070419150826 SAPUSER      DDIC         ides
SAPKB70010           I01.ALL L 0004 20070419151011 SAPUSER      DDIC         ides 20070419150915
SAPKB70010           I01.ALL P 0004 20070419151101 SAPUSER      DDIC         ides 20070419151032
SAPKB70010           I01.ALL H 0004 20070419152544 SAPUSER      DDIC         ides 20070419152217
SAPKB70010           I01.ALL A 0004 20070419154149 SAPUSER      DDIC         ides
ALL                  I01.ALL S 0000 20070419154232              DDIC         ides 20070419154155
ALL                  I01.ALL N 0000 20070419154335              DDIC         ides 20070419154155
ALL                  I01.ALL 6 0004 20070419154820              DDIC         ides 20070419154155
SAPKB70010           I01.ALL I 0004 20070419163829 SAPUSER      DDIC         ides 20070419154155
ALL                  I01.ALL n 0000 20070419164133              DDIC         ides 20070419154155
SAPKB70010           I01.ALL R 0000 20070419171913 SAPUSER      DDIC         ides
ALL                  I01.ALL t 0000 20070419172644              DDIC         ides
ALL                  I01.ALL t 0000 20070420101414              DDIC         ides
ALL                  I01.ALL t 0000 20070420102627              DDIC         ides
SAPKA70010           I01.ALL m 0000 20070420102638 SAPUSER      DDIC         ides
SAPKIPYJ7A           I01.ALL m 0000 20070420102647 PIBASISUSER DDIC         ides
SAPKW70010           I01.ALL m 0000 20070420102659 SAPUSER      DDIC         ides
SAPKNA7007           I01.ALL m 0000 20070420102705 SAPAPUSER    DDIC         ides
SAPKH60007           I01.ALL m 0000 20070420102728 SAPUSER      DDIC         ides
SAPK-60007INFICA     I01.ALL m 0000 20070420102754 SAPUSER      DDIC         ides
SAPK-60007INFICAX    I01.ALL m 0000 20070420102757 SAPUSER      DDIC         ides
SAPKA70010           I01.ALL L 0004 20070420102832 SAPUSER      DDIC         ides 20070420102800
SAPKIPYJ7A           I01.ALL L 0004 20070420102838 PIBASISUSER DDIC         ides 20070420102800
SAPKW70010           I01.ALL L 0004 20070420102906 SAPUSER      DDIC         ides 20070420102800
SAPKNA7007           I01.ALL L 0004 20070420102910 SAPAPUSER    DDIC         ides 20070420102800
SAPKH60007           I01.ALL L 0004 20070420102949 SAPUSER      DDIC         ides 20070420102800
SAPK-60007INFICA     I01.ALL L 0004 20070420103005 SAPUSER      DDIC         ides 20070420102800
SAPK-60007INFICAX    I01.ALL L 0004 20070420103007 SAPUSER      DDIC         ides 20070420102800
SAPKA70010           I01.ALL P 0004 20070420103039 SAPUSER      DDIC         ides 20070420103026
SAPKIPYJ7A           I01.ALL P 0004 20070420103042 PIBASISUSER DDIC         ides 20070420103026
SAPKW70010           I01.ALL P 0004 20070420103053 SAPUSER      DDIC         ides 20070420103026
SAPKNA7007           I01.ALL P 0004 20070420103055 SAPAPUSER    DDIC         ides 20070420103026
SAPKH60007           I01.ALL P 0004 20070420103121 SAPUSER      DDIC         ides 20070420103026
SAPK-60007INFICA     I01.ALL P 0004 20070420103126 SAPUSER      DDIC         ides 20070420103026
SAPK-60007INFICAX    I01.ALL P 0004 20070420103128 SAPUSER      DDIC         ides 20070420103026
SAPKA70010           I01.ALL H 0004 20070420104455 SAPUSER      DDIC         ides 20070420104317
SAPKIPYJ7A           I01.ALL H 0004 20070420104510 PIBASISUSER DDIC         ides 20070420104317
SAPKW70010           I01.ALL H 0004 20070420104614 SAPUSER      DDIC         ides 20070420104317
SAPKNA7007           I01.ALL H 0004 20070420104619 SAPAPUSER    DDIC         ides 20070420104317
SAPKH60007           I01.ALL H 0004 20070420105120 SAPUSER      DDIC         ides 20070420104317
SAPK-60007INFICA     I01.ALL H 0004 20070420105217 SAPUSER      DDIC         ides 20070420104317
SAPK-60007INFICAX    I01.ALL H 0004 20070420105228 SAPUSER      DDIC         ides 20070420104317
ALL                  I01.ALL t 0000 20070420110210              DDIC         ides
SAPK-60007INFICA     I01.ALL A 0004 20070420115140 SAPUSER      DDIC         ides
SAPK-60007INFICAX    I01.ALL A 0004 20070420115140 SAPUSER      DDIC         ides
SAPKA70010           I01.ALL A 0004 20070420115140 SAPUSER      DDIC         ides
SAPKH60007           I01.ALL A 0004 20070420115140 SAPUSER      DDIC         ides
SAPKIPYJ7A           I01.ALL A 0004 20070420115140 PIBASISUSER DDIC         ides
SAPKNA7007           I01.ALL A 0004 20070420115140 SAPAPUSER    DDIC         ides
SAPKW70010           I01.ALL A 0004 20070420115140 SAPUSER      DDIC         ides
ALL                  I01.ALL S 0000 20070420115355              DDIC         ides 20070420115217
ALL                  I01.ALL N 0000 20070420115401              DDIC         ides 20070420115217
ALL                  I01.ALL 6 0004 20070420120305              DDIC         ides 20070420115217
SAPKA70010           I01.ALL I 0004 20070420121421 SAPUSER      DDIC         ides 20070420115217
SAPKIPYJ7A           I01.ALL I 0004 20070420121612 PIBASISUSER DDIC         ides 20070420115217
SAPKW70010           I01.ALL I 0004 20070420123219 SAPUSER      DDIC         ides 20070420115217
SAPKNA7007           I01.ALL I 0004 20070420123349 SAPAPUSER    DDIC         ides 20070420115217
SAPKH60007           I01.ALL I 0004 20070420130625 SAPUSER      DDIC         ides 20070420115217
SAPK-60007INFICA     I01.ALL I 0004 20070420131144 SAPUSER      DDIC         ides 20070420115217
SAPK-60007INFICAX    I01.ALL I 0004 20070420131253 SAPUSER      DDIC         ides 20070420115217
ALL                  I01.ALL n 0000 20070420131356              DDIC         ides 20070420115217
SAPKA70010           I01.ALL R 0000 20070420132346 SAPUSER      DDIC         ides
SAPKIPYJ7A           I01.ALL R 0000 20070420132353 PIBASISUSER DDIC         ides
SAPKW70010           I01.ALL R 0000 20070420134358 SAPUSER      DDIC         ides
SAPKNA7007           I01.ALL R 0000 20070420134934 SAPAPUSER    DDIC         ides
SAPKH60007           I01.ALL R 0006 20070420140042 SAPUSER      DDIC         ides
SAPK-60007INFICA     I01.ALL R 0000 20070420140703 SAPUSER      DDIC         ides
SAPK-60007INFICAX    I01.ALL R 0000 20070420140713 SAPUSER      DDIC         ides
ALL                  I01.ALL t 0000 20070420141932              DDIC         ides
ALL                  I01.ALL t 0000 20070420141939              DDIC         ides
ALL                  I01.ALL t 0000 20070420142045              DDIC         ides
ALL                  I01.ALL t 0000 20070420142823              DDIC         ides
SAPKGPID07           I01.ALL m 0000 20070420142825 SAPUSER      DDIC         ides
SAPKGPID07           I01.ALL L 0004 20070420142836 SAPUSER      DDIC         ides 20070420142828
SAPKGPID07           I01.ALL P 0004 20070420142839 SAPUSER      DDIC         ides 20070420142837
ALL                  I01.ALL 6 0000 20070420143317              DDIC         ides 20070420143303
SAPKGPID07           I01.ALL I 0004 20070420143348 SAPUSER      DDIC         ides 20070420143303
ALL                  I01.ALL t 0000 20070420143614              DDIC         ides
SAPKW70011           I01.ALL m 0000 20070420143625 SAPUSER      DDIC         ides
SAPKW70011           I01.ALL L 0004 20070420143742 SAPUSER      DDIC         ides 20070420143632
SAPKW70011           I01.ALL P 0004 20070420143811 SAPUSER      DDIC         ides 20070420143749
SAPKW70011           I01.ALL H 0004 20070420144247 SAPUSER      DDIC         ides 20070420144134
SAPKW70011           I01.ALL A 0004 20070420144612 SAPUSER      DDIC         ides
ALL                  I01.ALL S 0000 20070420144641              DDIC         ides 20070420144617
ALL                  I01.ALL 6 0004 20070420144903              DDIC         ides 20070420144617
SAPKW70011           I01.ALL I 0004 20070420150622 SAPUSER      DDIC         ides 20070420144617
ALL                  I01.ALL n 0000 20070420150652              DDIC         ides 20070420144617
SAPKW70011           I01.ALL R 0000 20070420151931 SAPUSER      DDIC         ides
ALL                  I01.ALL t 0000 20070420153322              DDIC         ides
SAPKGPDD07           I01.ALL m 0000 20070420153324 SAPUSER      DDIC         ides
SAPKGPDD07           I01.ALL L 0004 20070420153338 SAPUSER      DDIC         ides 20070420153326
SAPKGPDD07           I01.ALL P 0004 20070420153345 SAPUSER      DDIC         ides 20070420153340
SAPKGPDD07           I01.ALL H 0004 20070420153632 SAPUSER      DDIC         ides 20070420153610
SAPKGPDD07           I01.ALL A 0004 20070420153818 SAPUSER      DDIC         ides
ALL                  I01.ALL S 0000 20070420153831              DDIC         ides 20070420153823
ALL                  I01.ALL 6 0000 20070420153905              DDIC         ides 20070420153823
SAPKGPDD07           I01.ALL I 0004 20070420154205 SAPUSER      DDIC         ides 20070420153823
SAPKGPDD07           I01.ALL R 0000 20070420154226 SAPUSER      DDIC         ides
ALL                  I01.ALL t 0000 20070420154751              DDIC         ides
SAPKGPAD07           I01.ALL m 0000 20070420154807 SAPUSER      DDIC         ides
SAPKGPAD07           I01.ALL L 0004 20070420154851 SAPUSER      DDIC         ides 20070420154814
SAPKGPAD07           I01.ALL P 0004 20070420154911 SAPUSER      DDIC         ides 20070420154856
SAPKGPAD07           I01.ALL H 0004 20070420155533 SAPUSER      DDIC         ides 20070420155317
ALL                  I01.ALL t 0000 20070420155918              DDIC         ides
SAPKGPAD07           I01.ALL A 0004 20070420160620 SAPUSER      DDIC         ides
ALL                  I01.ALL S 0000 20070420160638              DDIC         ides 20070420160625
ALL                  I01.ALL 6 0004 20070420160743              DDIC         ides 20070420160625
SAPKGPAD07           I01.ALL I 0004 20070420162359 SAPUSER      DDIC         ides 20070420160625
ALL                  I01.ALL n 0000 20070420162445              DDIC         ides 20070420160625
SAPKGPAD07           I01.ALL R 0004 20070420163533 SAPUSER      DDIC         ides
ALL                  I01.ALL t 0000 20070420163915              DDIC         ides
ALL                  I01.ALL t 0000 20070420164004              DDIC         ides
ALL                  I01.ALL t 0000 20070420164112              DDIC         ides
SAPKGPFD07           I01.ALL m 0000 20070420164119 SAPUSER      DDIC         ides
SAPKGPFD07           I01.ALL L 0004 20070420164205 SAPUSER      DDIC         ides 20070420164129
SAPKGPFD07           I01.ALL P 0004 20070420164217 SAPUSER      DDIC         ides 20070420164209
SAPKGPFD07           I01.ALL H 0004 20070420164645 SAPUSER      DDIC         ides 20070420164524
SAPKGPFD07           I01.ALL A 0004 20070420165233 SAPUSER      DDIC         ides
ALL                  I01.ALL S 0000 20070420165248              DDIC         ides 20070420165238
ALL                  I01.ALL 6 0000 20070420165322              DDIC         ides 20070420165238
SAPKGPFD07           I01.ALL I 0004 20070420170133 SAPUSER      DDIC         ides 20070420165238
ALL                  I01.ALL n 0000 20070420170156              DDIC         ides 20070420165238
SAPKGPFD07           I01.ALL R 0000 20070420170418 SAPUSER      DDIC         ides
ALL                  I01.ALL t 0000 20070420170650              DDIC         ides
ALL                  I01.ALL t 0000 20070420171054              DDIC         ides
SAPKGPGD07           I01.ALL m 0000 20070420171056 SAPUSER      DDIC         ides
SAPKGPGD07           I01.ALL L 0004 20070420171108 SAPUSER      DDIC         ides 20070420171059
SAPKGPGD07           I01.ALL P 0004 20070420171112 SAPUSER      DDIC         ides 20070420171109
SAPKGPGD07           I01.ALL H 0004 20070420171431 SAPUSER      DDIC         ides 20070420171339
SAPKGPGD07           I01.ALL A 0008 20070420171755 SAPUSER      DDIC         ides
ALL                  I01.ALL t 0000 20070420171911              DDIC         ides
SAPKGPGD07           I01.ALL A 0008 20070420171918 SAPUSER      DDIC         ides
ALL                  I01.ALL t 0000 20070420172106              DDIC         ides
SAPKGPGD07           I01.ALL A 0008 20070420172117 SAPUSER      DDIC         ides
ALL                  I01.ALL t 0000 20070420173251              DDIC         ides
SAPKGPGD07           I01.ALL A 0008 20070420173255 SAPUSER      DDIC         ides
ALL                  I01.ALL t 0000 20070420173753              DDIC         ides
SAPKGPGD07           I01.ALL A 0008 20070420173756 SAPUSER      DDIC         ides
ALL                  I01.ALL t 0000 20070420173914              DDIC         ides
SAPKGPGD07           I01.ALL A 0008 20070420173917 SAPUSER      DDIC         ides
ALL                  I01.ALL t 0000 20070420174114              DDIC         ides
ALL                  I01.ALL t 0000 20070420174541              DDIC         ides
SAPKGPGD07           I01.ALL A 0008 20070420174543 SAPUSER      DDIC         ides
ALL                  I01.ALL t 0000 20070420181327              DDIC         ides
SAPKGPGD07           I01.ALL A 0008 20070420181355 SAPUSER      DDIC         ides
ALL                  I01.ALL t 0000 20070420183111              DDIC         ides
SAPKGPGD07           I01.ALL A 0008 20070420183123 SAPUSER      DDIC         ides
ALL                  I01.ALL t 0000 20070420183655              DDIC         ides
SAPKGPGD07           I01.ALL A 0008 20070420183700 SAPUSER      DDIC         ides
ALL                  I01.ALL t 0000 20070420185422              DDIC         ides
SAPKGPGD07           I01.ALL A 0008 20070420185424 SAPUSER      DDIC         ides
ALL                  I01.ALL t 0000 20070420185611              TMSADM       ides
ALL                  I01.ALL S 0000 20070420190348              DDIC         ides 20070420190338
ALL                  I01.ALL t 0000 20070420190358              DDIC         ides
SAPKGPGD07           I01.ALL A 0008 20070420190403 SAPUSER      DDIC         ides
ALL                  I01.ALL 6 0000 20070420190407              DDIC         ides 20070420190338
ALL                  I01.ALL a 0000 20070420190537              DDIC         ides
ALL                  I01.ALL t 0000 20070420190559              DDIC         ides
SAPKGPGD07           I01.ALL A 0008 20070420190606 SAPUSER      DDIC         ides
ALL                  I01.ALL d 0000 20070420190622              DDIC         ides
SAPKGPGD07           I01:000 I 0004 20070420190713 SAPUSER      DDIC         ides 20070420190338
ALL                  I01.ALL t 0000 20070420190713              DDIC         ides
ALL                  I01.ALL Q 0000 20070420190717              DDIC         ides 20070420190338
SAPKGPGD07           I01.ALL A 0008 20070420190925 SAPUSER      DDIC         ides
ALL                  I01.ALL t 0000 20070420191154              DDIC         ides
SAPKGPGD07           I01.ALL A 0008 20070420191156 SAPUSER      DDIC         ides
ALL                  I01.ALL t 0000 20070420202424              DDIC         ides
SAPKGPGD07           I01.ALL A 0008 20070420202534 SAPUSER      DDIC         ides
ALL                  I01.ALL t 0000 20070420204507              DDIC         ides
SAPKGPGD07           I01.ALL A 0008 20070420204509 SAPUSER      DDIC         ides
ALL                  I01.ALL t 0000 20070420211533              DDIC         ides
SAPKGPGD07           I01.ALL A 0008 20070420211555 SAPUSER      DDIC         ides
ALL                  I01.ALL t 0000 20070420220457              DDIC         ides
SAPKGPGD07           I01.ALL A 0008 20070420220500 SAPUSER      DDIC         ides
SLOG
START CMDIMPORT            I01 L      20070419142043              DDIC         ides 20070419142042
STOP CMDIMPORT            I01 L      20070419142052              DDIC         ides 20070419142042
START imp all              I01        20070419142100              DDIC         ides 20070419142100
INFO: event SAP_IMPORT_START triggered successfully
START DD IMPORT            I01 H      20070419142101              DDIC         ides 20070419142100
STOP DD IMPORT            I01 H      20070419142617              DDIC         ides 20070419142100
START DD ACTIVATION        I01 A      20070419142618              DDIC         ides 20070419142100
START tp_getprots          I01 J      20070419142620              DDIC         ides 20070419142100
STOP tp_getprots          I01 J      20070419142918              DDIC         ides 20070419142100
STOP DD ACTIVATION        I01 A      20070419142918              DDIC         ides 20070419142100
START DISTRIBUTION OF DD-O I01 S      20070419142918              DDIC         ides 20070419142100
START tp_getprots          I01 S      20070419142918              DDIC         ides 20070419142100
STOP tp_getprots          I01 S      20070419142933              DDIC         ides 20070419142100
STOP DISTRIBUTION OF DD-O I01 S      20070419142933              DDIC         ides 20070419142100
INFO TBATG CONVERSION OF I01 N      not needed                  DDIC         ides 20070419142100
START MOVE NAMETABS        I01 6      20070419142934              DDIC         ides 20070419142100
START tp_getprots          I01 P      20070419142934              DDIC         ides 20070419142100
STOP tp_getprots          I01 P      20070419142949              DDIC         ides 20070419142100
STOP MOVE NAMETABS        I01 6      20070419142949              DDIC         ides 20070419142100
START MAIN IMPORT          I01 I      20070419142949              DDIC         ides 20070419142100
STOP MAIN IMPORT          I01 I      20070419143215              DDIC         ides 20070419142100
START TBATG CREATION OF EN I01 n      20070419143216              DDIC         ides 20070419142100
START tp_getprots          I01 Y      20070419143216              DDIC         ides 20070419142100
STOP tp_getprots          I01 Y      200

How was this problem fixed? We are running into the same problem. Any help will be much appreciated.
Thanks so much.
Mario

Short dump in every transaction during support pack import In PRD server

HI
While trying to applying support pack stack, get short abap dump, but after this in every tx same dump is there.
Following is the Support stack that we are applying
SAPKA70020
SAPKB70020
SAPKIPYM10
SAPKW70022
SAPKNA7017
SAPKH60012
SAPK-60008INFINBASIS
SAPKGS6008
following is dump
Syntax error in program "SAPLPA_PACKAGE_SERVICES
Error in the ABAP Application Program
The current ABAP program "SAPLSFW_COMMON" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLPA_PACKAGE_SERVICES " in
include "CL_PACKAGE_HELPER=============CU " in
line 179:
"Type "SLS_PACKAGE_INFO" is unknown"
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program
The current ABAP program "SAPLSFW_COMMON" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Thanks
YogRaj

Hi
I have applied support Pack successfully. But after this my one of SD user getting short dump in Tx VL01N, VA01.
Syntax error in program "SAPLDG95 "
What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_IM_EHS_DG_002_IMPL=========CP" had to be
     terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "SAPLDG95 " in include "LDG95U01
     " in
    line 29:
    ""X_DGMSD_TAB" and "E_DGMSD_TAB" are not mutually convertible. In Unico"
    "de programs, "X_DGMSD_TAB" must have the same structure layout as "E_D"
    "GMSD_TAB", independent of the length of a Unicode character."
    The include has been created and last changed by:
    Created by: "SAP "
    Last changed by: "SAP "
    Error in the ABAP Application Program
    The current ABAP program "CL_IM_EHS_DG_002_IMPL=========CP" had to be
     terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    The following syntax error was found in the program SAPLDG95 :
    ""X_DGMSD_TAB" and "E_DGMSD_TAB" are not mutually convertible. In Unico"
    "de programs, "X_DGMSD_TAB" must have the same structure layout as "E_D"
    "GMSD_TAB", independent of the length of a Unicode character."
Thanks
YogRaj

How to deal with delta queue when importing Support Package/Kernel Patch

Hi,
From my experience, when importing a Support Package for an installation, the system will issue an error message and get stuck if this Support Package is about to alter the structures used in delta loads.
But I would like to double with you if there is possible that the support packet which is going to alter structure, but no error message. If so, the delta data will be lost.
Do we need to clear down the delta queue every time we import support package?
Anyway, is there anyone have any suggestions or steps regarding this question?
Many Thanks
Jonathan

Hi,
Delta queues during support package upgrade
Its always better to drain the delta queues before an upgrade.
As a standard practice we drain the delta queues by running the IP/ chain multiple times.
As a prerequiste we cancel/reschedule the V3 jobs to a future date during this activity.
The V3 extraction delta queues must be emptied prior to the upgrade to avoid any possible data loss.
V3 collector jobs should be suspended for the duration of the upgrade.
They can be rescheduled after re-activation of the source systems upon completion of the upgrade.
See SAP Notes 506694 and 658992 for more details.
Page 17
Load and Empty all Data mart Delta Queues in SAP BW. (e.g. for all export DataSources)
The SAP BW Service SAPI, which is used for internal and BW to BW data mart extraction, is
upgraded during the SAP BW upgrade. Therefore, the delta queues must be emptied prior to the
upgrade to avoid any possibility of data loss.
upgrade preparation and postupgrade checklist
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/472443f2-0c01-0010-20ab-fbd380d45881
/message/3221895#3221895
OSS notes 328181 and 762951 as a prerequisites.
Failure to follow the instructions in those notes may probably result in data loss.
https://websmp207.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700002662832005E
/thread/804820
Effect on BW of R/3 Upgrade
How To Tackle Upgrades to SAP ERP 6.0
/people/community.user/blog/2008/03/20/how-to-tackle-upgrades-to-sap-erp-60
Start with the Why Not the How When You Upgrade to SAP ERP 6.0
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/008dddd1-8775-2a10-ce97-f90b2ded0280
Rapid SAP NetWeaver 7.0 BI Technical Upgrade
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0c9c8be-346f-2a10-2081-cd99177c1fb9
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c2b3a272-0b01-0010-b484-8fc7c068975e
Hope this helps.
Thanks,
JituK

Support Package Problem

Hi Experts,
While applying the support package of BASIS (KB70012) and ABAP (KA70012) in SAP ECC 6.0.we get the following error.
<i>The import was stopped, since an error occurred during the phase
DDIC_ACTIVATION, 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: DDIC_ACTIVATION
    -   Reason for error: TP_CANNOT_CONNECT_SYSTEM
    -   Return code: 0230
   -   Error message: Cant create any process
When I go through the command mode and type tp connect <sid> & tp connect <sid> pf=g:\usr\sap\trans\bin\ TP_DOMAIN_S10.PFL
Its give the following error.
G:\usr\sap\trans>tp connect S10
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 372.04.04 (release 700)
E-TPSETTINGS could not be opened.
EXIT
ERROR: System : Parameter SAPEVTPATH not set. Batch jobs cannot be started.
Error in TPSETTINGS: 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,...)
G:\usr\sap\trans>tp connect S10 pf=G:\usr\sap\trans\bin\TP_DOMAIN_S10.PFL
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 372.04.04 (release 700)
Connection to Database of S10 was successful.
punesrv02\usr\sap\trans\tmp\C071023.S10 for transport: ALL: No such file or di
rectory
punesrv02\usr\sap\trans\tmp\SLOG0743.S10.LOC: No such file or directory
PANIC --> exiting
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0212
tp finished with return code: 212
meaning:
could not access file as supposed (see dev_tp or SLOG0743.S10 for more details
Please help me.

Hi Sateesh,
It seems like your transport management system is not configured properly, Just check your CTS. is it configured properly.
Check your transport directory too.
when you imort a support patch it creates a file in this location. this message are co,img that means you transport directory is not configured properly.
\punesrv02\usr\sap\trans\tmp\C071023.S10 for transport: ALL: No such file or di
rectory
punesrv02\usr\sap\trans\tmp\SLOG0743.S10.LOC: No such file or directory
Regards
Subhash

SOLUTION MANGER SUPPORT PACKAGES CRTs ERROR

Hi all..
System status: solution manager 4.0/MS SQL/Windows 2003/kernel-159/sapm 027/700/tp version:372.04.29
When i am applying basis and abap patches(11) then i am getting CRTs error.
the error message is-
The import was stopped, since an error occurred during the phase
ADDON_CONFLICTS_?, 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: ADDON_CONFLICTS_?
    -   Reason for error: TP_CANNOT_CONNECT_SYSTEM
    -   Return code:
    -   Error message: TP_INTERFACE_FAILURE
how can I remove this error? please help me urgently.
thanks
NANI

Hi,
You have to add extra addon (CRT) support pack with SAP Basis support pack. It is necessary for solution manager.
Please can you tell me which support pack you are installing and what is your system version. (e.g SAP ECC 6.0 or SAP R/3 4.7 etc)

SPAM support packages error

Hi,
I've tried to upgrade CRM 5.0 SR 1 to SR 2, during the operation I had error during the phase TP_IMPORT, the error was an buffer inconsistency. It was impossible to reset the queue during this phase. So I deleted entries in the database table PAT01-PAT02-PAT03, now queue is empty but I've internal error of spam check when I try to reload this package.
In the background, I've the job still running RDDGENOL (triggered RAISE_EXECPTION, and timeout) created by ddic during the SP, who lock tables for SP, I can't stop it.
Furthermore, a dialogue process running with a BDG process waiting for RFC, which is also impossible to cancel.
Any help will be thankful.

hi people,
we have checked for the status of support package in Transaction SPAM traffic signal is still red and in the Phase RUN_SPAU_? it is stuck and even after restarting import it shows clean-up phase is left and it ends with same error mention above
the support package name is SAPKB70014 size is 116266 MB now after restarting the Import the following error message comes
The import was stopped, since an error occurred during the phase
RUN_SPAU_?, 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: RUN_SPAU_?
     -   Reason for error: TP_CANNOT_CONNECT_SYSTEM
     -   Return code: 0255
     -   Error message: Could not connect to semaphore server
we run all the phase in background, and even after entering the support package number in transaction SPAU there it is showing
"No objects within selected filter parameteres"
Q.1 Any idea what went wrong and how to fix that?
Q.2 Is there any problem if we run the all four phases of support package in background or it should be run in dialog ?
latest tp & R3trans updated

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

Support Package Manger for EBP/CRM cannot confirm SP ???, 'Package unknown'

I am installing CRM 5.0 SR1 (Windows 32bit/Oracle/NW04s).
I have imported SAP_BASIS SP07 and SP08:
'Queue SAPKB70007 - SAPKB70008 imported successfully according to Standard scen.: Confirm this',
but I cannot confirm (Support Package - Confirm is grayed out). If I start Support Package Manager for EBP/CRM SPAM, I get a window: 'Package is unknown'; after continuing I get an exception 'PATCH_NOT_SPECIFIED'. The status window in SPAM shows:
Software Component: ???
SPAM Status: yellow triangle
Next Action: Confirm
Please help.

I ran into this issue. Upgraded spam from 38 to 42. When I go to env-EBp/CRM, the SPAM Package is unknown error came up
Resolution: go to support package -> import spam/saint update again. It tokk care of the issue. Contuniuing with upgrade.

CIN packages - Import taking lot of time

Hi,
We are on SAP 46C, CIN 40A. While i am trying to import CIN suport package 10 in my server, the system is taking lot of time. I have updated my SPAM to the latest version. As of now, the import has taken more than 4 hours. What will be the usual time for the CIN support package import. Is there any way to speed up the process. Please advise at the earliest.
Thanx,
subbu

Check
Note 532596 - FAQ: Country Version India (CIN)- Installation and SPs
. How long does a CIN installation take ?
The time depends on the hardware that is available. If 4 processors and 2 GB RAM is allocated to that instance then it takes about 40 minutes. The maximum time is about 1.5 hrs .
Be also aware of the fact, that 40A is no more supporter after December 2006.
Markus

Importing Support Packages - Error during XPRA_EXECUTION

Hello,
Database: Oracle 10.2.0.4
Operation System: Windows Server 2008 X64
I´m facing with an error during an importing of support packages in our Solution Manager Ehp1 system (SPS 20 to SPS 25).
I checked the import logs of the queue and I see in there the following error:
Program terminated (job: RDDEXECL, no.: 02083200)
   See job log
Execution of programs after import (XPRA)
End date and time : 20110126020847
Ended with return code: ===> 12 <===
When I checked the job log I see in there this:
Job started
Step 001 started (program RDDEXECL, variant , user ID DDIC)
All DB buffers of application server SAPSM were synchronized
Internal session terminated with a runtime error (see ST22)
Job cancelled
I went to ST22 and I see in there that specific short dump which show:
Short text
    XSLT: No valid XML source
What happened?
    The transformation is not possible since the XML source document cannot
    be parsed.
What can you do?
    Note which actions and input led to the error.
    For further help in handling the problem, contact your SAP administrator.
    You can use the ABAP dump analysis transaction ST22 to view and manage
    termination messages, in particular for long term reference.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_XSLT_RUNTIME_ERROR', was not
     caught in
    procedure "TRANSFORM_FROM_XML" "(METHOD)", 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:
    Either the source document contains invalid XML or it is handled
    incorrectly in the ABAP program that called the transformation.
How to correct the error
    The most common cause of this error is a conflict between the encoding
    specified in the declaration <?xml version="1.0" encoding="..."?> in the
     document and the actual encoding of the data.
    If the document is held in an ABAP string, the actual encoding is the
    system code page. If this does not match the declaration, a parsing
    error may occur.
    These conflicts are a particular issue when XML documents are produced
    in one system and then imported into a system with a different code page
     (as strings).
    For this reason, XML documents should be held as binary data (X strings)
    , if they are extracted from the system or accessed from outside.
    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:
    "XSLT_BAD_SOURCE_CONTEXT" "CX_XSLT_RUNTIME_ERROR"
    "CL_SM_BFR_CONTENT_TRANSPORT===CP" or "CL_SM_BFR_CONTENT_TRANSPORT===CM00E"
    "TRANSFORM_FROM_XML"
    The exception must either be prevented, caught within proedure
    "TRANSFORM_FROM_XML" "(METHOD)", or its possible occurrence must be declared in
     the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
Can you help how to correct this situation for I can continue the update of support packages!
Best regards,
João Dimas - Portugal

Hello William,
Which import logs do you refer?
I pasted in my first message the log of import... that is the unique error that it appeared.
I checked the SLOG:
STOP MOVE NAMETABS        SSM 6      20110125215838              SAP_BASIS    SAPSM 20110125214839404
START MAIN IMPORT          SSM I      20110125215838              SAP_BASIS    SAPSM 20110125214839404
STOP MAIN IMPORT          SSM I      20110125235752              SAP_BASIS    SAPSM 20110125214839404
START TBATG CREATION OF EN SSM n      20110125235752              SAP_BASIS    SAPSM 20110125214839404
START tp_getprots          SSM Y      20110125235753              SAP_BASIS    SAPSM 20110125214839404
WARNING: '\SAPSMsapmnt     rans     mpN110126.SSM' : cant open
(tpfsnam.c:504)
WARNING: '' : cant open
(tpfsnam.c:584)
WARNING: '\SAPSMsapmnt     rans     mpN110126.SSM' : cant open
(tpfsnam.c:504)
WARNING: '' : cant open
(tpfsnam.c:584)
STOP tp_getprots          SSM Y      20110126000148              SAP_BASIS    SAPSM 20110125214839404
STOP TBATG CREATION OF EN SSM n      20110126000148              SAP_BASIS    SAPSM 20110125214839404
INFO EXECUTION OF STANDAR SSM 9      not needed                  SAP_BASIS    SAPSM 20110125214839404
INFO: event SAP_IMPORT_STOP triggered successfully
STOP imp all              SSM   0004 20110126000149              SAP_BASIS    SAPSM 20110125214839404
I also checked the ULOG which has the following records:
APServiceSSM 20110126013719 RFC: tp XPA ALL SSM pf=\SAPSMsapmnt     rans inTP_DOMAIN_SSM.PFL -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems= -Dbuffreset=yes -Dbatch_proc=1 tag=spam -Dtransdir=\SAPSMsapmnt     rans (pid=5276)
APServiceSSM 20110126020829 RFC: tp SHOWPARAMS SSM pf=\SAPSMsapmnt     rans inTP_DOMAIN_SSM.PFL -Dtransdir=\SAPSMsapmnt     rans (pid=5196)
APServiceSSM 20110126020830 RFC: tp CONNECT SSM pf=\SAPSMsapmnt     rans inTP_DOMAIN_SSM.PFL -Dtransdir=\SAPSMsapmnt     rans (pid=5196)
APServiceSSM 20110126020831 RFC: tp XPA ALL SSM pf=\SAPSMsapmnt     rans inTP_DOMAIN_SSM.PFL -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems= -Dbuffreset=yes -Dbatch_proc=1 tag=spam -
Any idea what´s happen?!
Kind regards,
João Dimas - Portugal

Error in "Test IMPORT" during applying BASIS Support Package

Hi All,
I'm applying basis support package from SAPKB70014 to SAPKB70018,
now it hangs in Import phase: TEST_IMPORT, there maybe something wrong with the import object.
For detail screenshots, please kindly have a look at URL: http://nickfiles.150m.com/Question_1.html
And for the detail import log, please have a look at http://nickfiles.150m.com/SAPPB70015.html.
I think the root cause is located in:
2EETW165 Function "TMW_TAOAGENT (TMW_TAOINTERFACE|01)" does not fit into the existing function group "(TMW_CLIENT_INTERFACES|06)".
2 ETW167 Please transport the whole function group.
But I do not know how to solve it. Could anyone help me?
Thank you very much.
Best regards,
Nick

Hi Nick,
This is the solution to your Issue..
Note 1156706 - Function TMW_TAOAGENT (TMW_TAOINTERFACE 01) does not fit...
Other SAPnote you can read .. for your help..
Note 42379 - SPAM aborts at step TEST_IMPORT
Note 1092979 - TMW_TAOAGENT: Repairing function group after SAPKB70013
Hope it will solve your issue ....
All teh best !!

DDIC_TYPE_INCONSISTENCY during Support Package import

Similar Messages

Maybe you are looking for