DDIC_ACTIVATION and TP_STEP_FAILURE error in SAINT Update (urgent)

[Former Member]

Hi All,

In Solution Manager SR 2 we have to update from SP 10 to SP 15. When we loaded in the OCS, it was asking for ST-SER 700_2008_1 Add-on, eventhough that Add-on is included the queue.

So We started doing only the Add-on import from ST-SER 700_2007_1 to ST-SER 700_2008_1 in SAINT.

In the middle it thorwed an error as follows

Error in phase: DDIC_ACTIVATION

Reason for error: TP_STEP_FAILURE

Return code: 0008

Error Messsage : OCS Package SAPKA70012 , tp step A return code 0008.

-

---

Hardware details of the server

SAP directory : 250 GB

RAM capacity : 2GB

Processor : intel Xenon 2 quad core processor

OS : Windows 2003

-

---

R3trans -d

This is R3trans version 6.14 (release 700 - 10.09.07 - 09:57:00).

unicode enabled version

R3trans finished (0000).

tp -v

This is tp version 372.04.04 (release 700, unicode enabled)

-

---

tp information

-

---

kernel release 700

kernel make variant 700_REL

DBMS client library OCI_10201_SHARE ()

DBSL shared library version 700.08

compiled on NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10

compilation mode UNICODE

compile time Oct 22 2007 20:43:34

update level 0

patch number 120

source id 0.133

disp+work

-

---

disp+work information

-

---

kernel release 700

kernel make variant 700_REL

compiled on NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10

compilation mode UNICODE

compile time Oct 23 2007 01:07:18

update level 0

patch number 133

source id 0.133

-

---

This TR SAPKB70012 failed in Ativation with below error.

Table SI_WD_ALLOWED_OBJECT_STR does not exist

BGRFC_UNIT_DELTIME-FINISHED_AT is used in aggregate E_BGRFC_UNIT_DEL. Delete not allowed

Tab. DB6PMCD is of type INTTAB (Technical settings are not meaningful)

Tab. DB6PMCD2 is of type INTTAB (Technical settings are not meaningful)

Tab. DB6PMCF is of type INTTAB (Technical settings are not meaningful)

Tab. DB6PMCG is of type INTTAB (Technical settings are not meaningful)

Tab. DB6PMCK is of type INTTAB (Technical settings are not meaningful)

Tab. DB6PMCM1 is of type INTTAB (Technical settings are not meaningful)

Tab. DB6PMCM2 is of type INTTAB (Technical settings are not meaningful)

Tab. DB6PMCN is of type INTTAB (Technical settings are not meaningful)

Tab. DB6PMCP is of type INTTAB (Technical settings are not meaningful)

Tab. DB6PMCR is of type INTTAB (Technical settings are not meaningful)

Tab. DB6PMSA is of type INTTAB (Technical settings are not meaningful)

Tab. DB6PMSA_AG is of type INTTAB (Technical settings are not meaningful)

Tab. DB6PMSA_LW is of type INTTAB (Technical settings are not meaningful)

Tab. DB6PMSA_SS is of type INTTAB (Technical settings are not meaningful)

Tab. DB6PMSA_ST is of type INTTAB (Technical settings are not meaningful)

Tab. DB6PMSB is of type INTTAB (Technical settings are not meaningful)

Tab. DB6PMSD is of type INTTAB (Technical settings are not meaningful)

Tab. DB6PMSL_AP is of type INTTAB (Technical settings are not meaningful)

Tab. DB6PMSL_DB is of type INTTAB (Technical settings are not meaningful)

Tab. DB6PMSL_LK is of type INTTAB (Technical settings are not meaningful)

Tab. DB6PMSL_LW is of type INTTAB (Technical settings are not meaningful)

Tab. DB6PMSM is of type INTTAB (Technical settings are not meaningful)

Tab. DB6PMSM_FC is of type INTTAB (Technical settings are not meaningful)

Tab. DB6PMSM_FN is of type INTTAB (Technical settings are not meaningful)

Tab. DB6PMSP is of type INTTAB (Technical settings are not meaningful)

Tab. DB6PMSP_HD is of type INTTAB (Technical settings are not meaningful)

Tab. DB6PMSQ is of type INTTAB (Technical settings are not meaningful)

Tab. DB6PMST is of type INTTAB (Technical settings are not meaningful)

Tab. DB6PMST_HD is of type INTTAB (Technical settings are not meaningful)

Tab. DB6PM_LST is of type INTTAB (Technical settings are not meaningful)

We hanged here, Kindly advice us.

regards,

Prat

[markus_doehr2]

> R3trans -d

> This is R3trans version 6.14 (release 700 - 10.09.07 - 09:57:00).

> unicode enabled version

> R3trans finished (0000).

>

> tp -v

> This is tp version 372.04.04 (release 700, unicode enabled)

I suggest to update R3trans and tp to the latest versions (yours are almost a year old) - and retry that phase.

Markus

[Former Member]

Hi Marcus,

Thanks a lot.

I have copied latest R3trans, TP version and restarted the Support pack update."MAIN IMPORT" is finished for 4 support packs and failed for this "SAPKITL422"

By throwing below error:

1 duplicate key error during insert into table AGSTWB_RSTAT_VAL occured

1 duplicate key error during insert into table AGSTWB_RSTAT_VAL occured

1 duplicate key error during insert into table AGSTWB_RSTAT_VAL occured

1 duplicate key error during insert into table AGSTWB_RSTAT_VAL occured

1 duplicate key error during insert into table AGSTWB_RSTAT_VAL occured

1 duplicate key error during insert into table AGSTWB_RSTAT_VAL occured

1 duplicate key error during insert into table AGSTWB_RSTAT_VAL occured

-

---

SAINT executed screen came out with below RUN TIME ERROR.

Runtime Errors LOAD_PROGRAM_CLASS_MISMATCH

Date and Time 18.07.2008 13:40:11

What happened?

Error in the ABAP Application Program

The current ABAP program "SAPLSPO6" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

The system attempted to correct the error

automatically, so you should try to restart

the program.

Error analysis

The section "PUBLIC" of the interface of the class "CL_MESSAGE_HELPER" was

changed during

program flow, which caused inconsistencies at runtime.

The program "SAPLSHL2" uses the interface version 20080718123253.

The program "SAPLSAINT_UI" uses the interface version 20041216204104.

The internal session was started at 20080718115135.

How to correct the error

Try to restart the program.

_________________________________________________

Kindly advide us.

Best Regards,

Praty

[Former Member]

Hi

We tried resart the "MAIN IMPORT" and it throwed below error.

Error in phase: IMPORT_PROPER

Reason for error: TP_STEP_FAILURE.

Reture Code : 0008

Error Message : OCS Package SAPKITL422, tp step "I", return code 0008.

Kindly advise us

Regards,

Pratyu

[markus_doehr2]

> I have copied latest R3trans, TP version and restarted the Support pack update."MAIN IMPORT" is finished for 4 support packs and failed for this "SAPKITL422"

>

> By throwing below error:

> 1 duplicate key error during insert into table AGSTWB_RSTAT_VAL occured

> 1 duplicate key error during insert into table AGSTWB_RSTAT_VAL occured

> 1 duplicate key error during insert into table AGSTWB_RSTAT_VAL occured

> 1 duplicate key error during insert into table AGSTWB_RSTAT_VAL occured

> 1 duplicate key error during insert into table AGSTWB_RSTAT_VAL occured

> 1 duplicate key error during insert into table AGSTWB_RSTAT_VAL occured

> 1 duplicate key error during insert into table AGSTWB_RSTAT_VAL occured

That error is documented in note 1074030 - R3trans: "Duplicate key" composite SAP note (as of Rel 6.10) - open the note and search for the table name.

> SAINT executed screen came out with below RUN TIME ERROR.

>

> Runtime Errors LOAD_PROGRAM_CLASS_MISMATCH

This is "normal" since a support package also patches the transaction SAINT itself. Just restart SAINT.

Markus

[Former Member]

Hi Marcus,

Thanks for the info.

In Se14, index button showing only one Primary key, there are no secondary keys and in the check also it is showing Consistent ( Both database object & Runtime object are Consistent)

We tried using Note:1074030, after going to SE11 --> AGSTWB_RSTAT_VAL --> by clicking Display or change button, its going to Runtime error

Runtime Errors LOAD_CLASS_NOT_FOUND

Date and Time 18.07.2008 15:10:39

Short text

Class "CL_BADI_FLT_DATA_TRANS_AND_DB" not found.

What happened?

The class "CL_BADI_FLT_DATA_TRANS_AND_DB" was adressed in the ABAP program

"CL_EXITHANDLER================CP". However, no class

definition was found.

Error in the SAP kernel.

The current ABAP "CL_EXITHANDLER================CP" program had to be

terminated because the

ABAP processor detected an internal system error.

Kindly advise us.

Thanks and regards,

Pratyu

[markus_doehr2]

If you have a version of R3trans newer than the one mentioned for that table I think the only thing left is an OSS call (BC-UPG-OCS)...

Markus

[Former Member]

Hi Marcus,

Can we restart the Server and try for "MAIN IMAPORT"

[markus_doehr2]

Yes you can - but what do you expect to happen? This is a problem of the import software (R3trans) - this won´t be fixed after a reboot.

And even if: Rebooting hides problems, it does not solve them. If it works after reboot, what was the error then? And what will prevent the error from reoccurring next time you install patches?

Markus