cancel
Showing results for 
Search instead for 
Did you mean: 

Error in Phase DDIC_ACTIVATION - TP_STEP_FAILURE returncode 0008

Former Member
0 Kudos

Hello,

I am updating my Solman 7.0 system to EHP1. I am getting an error in the DDIC_ACTIVATION phase:

The detailed error says:

The installation was stopped, since an error occurred during the phase

DDIC_ACTIVATION, 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: DDIC_ACTIVATION

- Reason for error: TP_STEP_FAILURE

- Return code: 0008

- Error message: OCS Package SAPK-1507EINSTPL, tp step A, return

code 0008

Notes on phase DDIC_ACTIVATION

In this phase the system activates the imported Data Dictionary objects.

This phase may terminate for several reasons:

- TP_INTERFACE_FAILURE: The system was unable to call the tp

interface.

- TP_FAILURE: The system was unable to execute the tp program. For

more information, see the SLOG or ALOG log file.

- TP_STEP_FAILURE: The system was unable to perform the tp step DDIC

activation successfully. To see the cause of the problem in the

activation log, choose Logs.

If you import two or more OCS packages in one installation queue,

and activate the Data Dictionary objects in the incorrect sequence,

this can cause errors. In this case, the activation errors disappear

if you repeat the activation run. To do this, choose Continue.

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.

I am not able to get rid of this error even after applying the corrections mentioned in SAP note: 822380. I also tried running the phase again, but still getting this error. How do I get past this error. Your help in this regard is highly appreciated.

Thanks,

Ajay

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Solved with comment above

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

Check SAP Note 447839 - ZDATE_ILLEGAL_LOCTIME

Thanks

Sunny

Former Member
0 Kudos

Hi Sunny,

I have checked that. That did not help me.

Thanks,

Ajay

Former Member
0 Kudos

Also the Import log of SAPK-1507EINSTPL says:

ABAP Dictionary: Activation

Transport request : SAPK-1507EINSTPL

System : YSM

tp path : tp

Version and release: 372.04.65 701

See log for request /usr/sap/transSM/tmp/SAPAIBIIP6.YSM

Program terminated (job: RDDMASGL, no.: 14480600)

See job log

ABAP Dictionary: Activation

End date and time : 20100131152902

Ended with return code: ===> 12 <===

Job Log says:

Date Time Message

31.01.2010 14:48:06 Job started

31.01.2010 14:48:07 Step 001 started (program RDDMASGL, variant IMPACTMRG, user ID DDIC)

31.01.2010 14:48:07 Start of mass activation 14:48:07

31.01.2010 15:28:59 ABAP/4 processor: ZDATE_ILLEGAL_LOCTIME

31.01.2010 15:28:59 Job cancelled

Please let me know how to proceed.

Thanks,

Ajay

RajeevP
Advisor
Advisor
0 Kudos

Hi Ajay,

As the job failed with the message ZDATE_ILLEGAL_LOCTIME, this should be an issue with the day light saving time. You must have received an ABAP dump for the same.

Have u gone through all the notes related with this error? Note 398374 , Note 102088 ,Note 840770 ...

Rajeev.

Former Member
0 Kudos

Hi,

I no longer see the ILLEGAL_LOCTIME error in the logs. But it is still failing in the DDIC_ACTIVATION error with TP_STEP_FAILURE and return code 8.

Any idea how I can proceed from here?

Thanks,

Ajay

RajeevP
Advisor
Advisor
0 Kudos

Hi Ajay,

Could you please paste the import log entries for RC 8?

Rajeev

Former Member
0 Kudos

Hi All,

I solved this error by applying both the corrections 679591 and 1059518 mentioned in the SAP note 1256384. Had opened a message with SAP for this, but they were of no help.

Thanks all

Ajay