IMPORT_PROPER TP_STEP_FAILURE 0012 OCS Package ALL, tp step "N"

[joo_migueldimas]

Hello,

SAP System: ECC 6.0

DataBase: SQL Server 2005

Operation System: Windows Server 2003 x64

I´m faccing with an error during an importing of Support Packages SP06 to SP16 through SPAM

The updating process stopped with the following message error:

The following details help you to analyze the problem:

- Error in phase: IMPORT_PROPER

- Reason for error: TP_STEP_FAILURE

- Return code: 0012

- Error message: OCS Package ALL, tp step "N", return code 0012

When I checked SPAM Action Log it show the next error:

Import phase 'IMPORT_PROPER' (04.07.2010, 22:00:28)

Error during executing the tp command 'tp IMPORT all PRD ...'

tp return code: '0012' , tp message: 'A tool used by tp aborted' , tp output:

This is tp version 372.04.71 (release 700)

ERROR: stopping on error 12 during TBATG CONVERSION OF DD-OBJECTS

stopping on error 12 during TBATG CONVERSION OF DD-OBJECTS

tp returncode summary:

TOOLS: Highest return code of single steps was: 12

WARNS: Highest tp internal warning was: 0118

standard output from tp and from tools called by tp:

Details of the error situation can also be found in the import logs

Interrupt the import due to an error situation (04.07.2010, 22:24:37)

Display detailed informations concerning the error in phase 'IMPORT_PROPER'

Abort the import due to an error situation (05.07.2010, 00:10:23)

Other log file that I checked was TP System Log:

STOP TBATG CONVERSION OF PRD N

ERROR: stopping on error 12 during TBATG CONVERSION OF DD-OBJECTS

START INFORM SAP-SYSTEM OF PRD Q

START tp_getprots PRD Q

STOP tp_getprots PRD Q

STOP INFORM SAP-SYSTEM OF PRD Q

STOP imp all PRD 0012

START imp all PRD

INFO: event SAP_IMPORT_START triggered successfully

START TBATG CONVERSION OF PRD N

START tp_getprots PRD N

ERROR ALL PRD N 0012

STOP tp_getprots PRD N

STOP TBATG CONVERSION OF PRD N

ERROR: stopping on error 12 during TBATG CONVERSION OF DD-OBJECTS

START INFORM SAP-SYSTEM OF PRD Q

START tp_getprots PRD Q

STOP tp_getprots PRD Q

STOP INFORM SAP-SYSTEM OF PRD Q

STOP imp all PRD 0012

Can you help me please to solve this problem?

João Dimas - Portugal

[joo_migueldimas]

The solution for this problem is described in my last message (previous to this one)!

[Former Member]

Hi,

Several indexes should be created, deleted, or changed during the support pack update. Two indexes may have the same defination. This should be the problem.

Delete the objects in table TBATG, and all subsequent packages and retry the import.

Regards,

JP.

[paul_power]

Hi,

What are the error entries in the latest ALOg, ULOG and SLOG?

Check the background job that would have been running for this phase: RDDGEN0L

Check its joblog, the SM21 system log from the time it failed and any shortdump in ST22 from this time.

Please also ensure your tp and R3trans patch level are the most recent available on the SAP service marketplace.

These should show further details of why the phase failed. If doubts remain please post the what you find from the above.

Regards,

Paul

[joo_migueldimas]

Hello Paul Power,

First at all... before this importing process I did a kernel upgrade to the last release (236) and I did the same to the SPAM component!

I checked the job RDDGEN0L (with status Canceled - DDIC user) and it show the following job log:

05.07.2010 11:23:46 Job started

05.07.2010 11:23:46 Step 001 started (program RDDGENBB, variant CONV, user ID DDIC)

05.07.2010 11:23:46 Start of conversion: 11:23:46

05.07.2010 11:23:46 File log: :D:T:S:tmp:F:N100705.PRD

05.07.2010 12:23:50 ABAP/4 processor: RAISE_EXCEPTION

05.07.2010 12:23:50 Job cancelled

As you know during the process the job OCS_QUEUE_IMPORT is Active and the status of it is Finished with the next job log:

05.07.2010 11:23:43 Job started

05.07.2010 11:23:43 Step 001 started (program RSSPAM30, variant , user ID SAP_BASIS)

05.07.2010 11:23:43 Start of RSSPAM30

05.07.2010 11:23:43 Start of queue import

05.07.2010 12:24:04 Stop of RSSPAM30

05.07.2010 12:24:04 Job finished

The system log in SM21 have this entries:

12:23:49 DIA 000 000 DDIC AB 0 Run-time error "TIME_OUT" occurred

12:23:50 DIA 000 000 DDIC AB 1 > Short dump "100705 122349 ptresapp rd_PRD_00 " generated

12:23:50 DIA 000 000 DDIC D0 1 Transaction Canceled SY 002 ( Time limit exceeded. )

12:23:50 BTC 017 000 DDIC AB 0 Run-time error "RAISE_EXCEPTION" occurred

12:23:50 BTC 017 000 DDIC AB 1 > Short dump "100705 122350 ptresapp rd_PRD_00 " generated

12:23:50 BTC 017 000 DDIC D0 1 Transaction Canceled 00 671 ( RAISE_EXCEPTION 20100705122350ptresapprd_PRD_00 DDIC 000 )

In ST22 I see there two shortdumps: TIME_OUT and RAISE_EXCEPTION

Maybe I have to set the parameter rdisp/max_wprun (instance profile) with other value like such 8000, what do you think??

BR

João Dimas - Portugal

[joo_migueldimas]

Hello everyone,

I already solve this issue!

The solution was, in fact, the value of parameter rdisp/max_wprun_time. I had set this parameter with 3600 but nevertheless the jobs RDDGEN0L and OCS_QUEUE_IMPORT finished with errors (with canceled status) and I noticed that both jobs ended with duration time 3660 seconds... thus I concluded that was related with the value of that parameter, so what I did it was increase the value of that parameter because this have a lot of files, this queue is very big (sap_basis SP09 to SP21) almost 900 files, and because of that the process of each commits on database has a extended periods of time!! So the solution was increase the value of that parameter I set with 10.000 seconds and the error never appeared! In my case the job RDDGEN0L finished with sucess after 5 hours!!

For this case, please be aware of this next two notes (related with shortdumps):

1094421 - TIME_OUT Job termination DDIC conversion as mass proc.

794802 - Runtime error RAISE_EXCEPTION job RDDGEN0L

Both notes suggest to increase that parameter!!

Kind regards,

João Dimas - Portugal