Stuck in the SAP_APPL component

[Former Member]

Hi Team,

We are applying the SAP_APPL patches SAPKH60511 & SAPKH60512.

We are stuck in the phase IMPORT_PROPER phase.

The RDDGENOL job was running for 17 hours.  In  SLOG , ALOG & Temp directory there are no errors. The log was not updating in proper time. It was updated 8 hours back. RDDIMPDP job was not running , even though we executed the report RDDNEWPP the job was not triggering.

Then we have trigger the report SAP_TRIGGER_RDDIMPDP in SM62. The job was successful but log was displaying as below

Header N: Acc. to TRBAT, job 02152900 is still running. Checking job status

Header N: Job 02152900 is still running

Now we have aborted that session and rename the temp files and ran the SAP_APPL component again. It was started from import2 phase.

Now the OCS_QUEUE_IMPORT & RDDGENOL jobs were running again for long time.

Experts please helpful for us to resolve the issue.

Regards

Raghu

[Reagan]

I would first perform a "Check Status" for the job RDDGENOL from Tx SM37.

If the R3trans and tp processes were running at the OS level then for sure there is some activity under progress. Did you perform the patching with parallelism ?

Also check the database trace logs for any errors.

Regards

RB

[Former Member]

Hi,

Just to add check the below note.

The reason why you might not get the dump as you are at higher release.

But try checking these two steps.

The error can have the following causes:
- Termination of the job RDDGEN0L when the system generates lock objects with time out if the accesses to the table D010INC or D010TAB are not optimized (Note 1232776).
- Termination of the conversion of tables with time out because the table is simply too large for the permitted dialog time (disp/max_wprun_time ).

794802 - Runtime error RAISE_EXCEPTION job RDDGEN0L

And

if you see any DB related issue. Dont forget to check the job status in SM37 -->select the job and then check status.

Thanks

Rishi Abrol

[Former Member]

1. One job was checked and 0 jobs corrected

2. No we didnt start perform with patching parallelism.

3. No logs were getting updated .

Still the jobs were running for long time.

[Former Member]

Hi,

Can you please check that how much memory tp and the R3trans running for the current patch are taking.

How long was the last log update.

If no log has been updated quite long than it can be that the process is hanging but not doing any thing.

Do you see any issue in the DB log . Do you see any update happening in SM50. Try to set trace in st05 and see if any activity is happening. Just use the filter with the id that you are running the patch import.

If nothing comes in the trace i would suggest you to stop all the process and restart with update R3trans patch 514 but it you think you want to wait for the error you can.

Thanks

Rishi Abrol

[Former Member]

This looks very strange. Since the job RDDGEN0L is running for 20 hours and was not updating any kind of logs. I aborted and import the phase again. In the next attempt it was completed for 15 hours.

Now im completed with SAP_APPL patches SAPKH60510 & SAPKH60511.

But i look further to investigate why this job ran for so long time with out updating any logs.

subsequently im going to do the patching in PRD. I've to minimize the downtime.

Experts if you face the same issue can any one help why this was happening.

Regards

Raghu

[ashish_vikas]

Do you see process tp / R3trans running on OS level ? If not, you can update latest TP and R3trans for your kernel and try again.

Check if this solution is helpful ? Also make sure you do not have archive stuck of something.

http://scn.sap.com/thread/434751

best regards

av

[Former Member]

Hi Ashish,

Thanks for the quick response. I've go through that forum.

In SLOG i didn't find any error. Initially it was running so long at START tp_getprots phase. After i aborted that phase then i got RC=12. Ignore that error. Then i've re imported the component again. Still it is running so long at same phase.

Currently OCS_QUEUE_IMPORT & RDDGENOL jobs are running. SLOG & in tmp folder i didn't find any update in logs.

INFO: event SAP_IMPORT_START triggered successfully

START DISTRIBUTION OF DD-O TST S      20131116021414              RKUMAR       SSGMELTSTCI1 20131116021401600  

START tp_getprots          TST S      20131116021414              RKUMAR       SSGMELTSTCI1 20131116021401600  

STOP  tp_getprots          TST S      20131116021542              RKUMAR       SSGMELTSTCI1 20131116021401600  

STOP  DISTRIBUTION OF DD-O TST S      20131116021542              RKUMAR       SSGMELTSTCI1 20131116021401600  

START TBATG CONVERSION OF  TST N      20131116021542              RKUMAR       SSGMELTSTCI1 20131116021401600  

START tp_getprots          TST N      20131116021542              RKUMAR       SSGMELTSTCI1 20131116021401600  

ERROR ALL                  TST N 0012 20131116215827              RKUMAR       SSGMELTSTCI1 20131116021401600  

STOP  tp_getprots          TST N      20131116215849              RKUMAR       SSGMELTSTCI1 20131116021401600  

STOP  TBATG CONVERSION OF  TST N      20131116215849              RKUMAR       SSGMELTSTCI1 20131116021401600  

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

START INFORM SAP-SYSTEM OF TST Q      20131116215849              RKUMAR       SSGMELTSTCI1 20131116021401600  

START tp_getprots          TST Q      20131116215849              RKUMAR       SSGMELTSTCI1 20131116021401600  

STOP  tp_getprots          TST Q      20131116215852              RKUMAR       SSGMELTSTCI1 20131116021401600  

STOP  INFORM SAP-SYSTEM OF TST Q      20131116215852              RKUMAR       SSGMELTSTCI1 20131116021401600  

STOP  imp all              TST   0012 20131116215852              RKUMAR       SSGMELTSTCI1 20131116021401600  

START imp all              TST        20131116220319              RKUMAR       SSGMELTSTCI1 20131116220305684  

INFO: event SAP_IMPORT_START triggered successfully

START TBATG CONVERSION OF  TST N      20131116220322              RKUMAR       SSGMELTSTCI1 20131116220305684  

START tp_getprots          TST N      20131116220322              RKUMAR       SSGMELTSTCI1 20131116220305684  

Regards

Raghu

[Former Member]

R3 Trans and Tp was running well at the moment. We have update the latest SPAM 50 , and kernel 720 and patch 500.

[ashish_vikas]

What this job  RDDGENOL is doing? Check workprocess trace, SM50 and database activity. (also i hope you have checked ST22 & SM21)

Check if increasing  rdisp/max_wprun_time to a large value helps.

best regards

ashish

[Former Member]

I'm wondering why RDDGENOL job was running for longtime. Check the below log for this job.

Job started

Step 001 started (program RDDGENBB, variant CONV, user ID DDIC)

Start of conversion: 22:03:16

File log: :D:T:S:tmp:F:N131116.TST

Check the below trace for the job RDDGENOL

Sat Nov 16 22:03:31 2013

  ***SUBPOOL*** generating subroutine pool %_T00004 for user DDIC (000f0003).

                MainProg=SAPLSDB2, Incl=LSDB2U13, Line=26

  dbmyclu : info : my major identification is 168806923, minor one 1411.

  dbmyclu : info : Time Reference is 1.12.2001 00:00:00h GMT.

  dbmyclu : info : my initial uuid is E34EAEB9524FEBF182EC005056B15AEF.

  dbmyclu : info : current optimistic cluster level: 3

  dbmyclu : info : pessimistic reads set to 2.

Sat Nov 16 23:36:22 2013

  ***SUBPOOL*** generating subroutine pool %_T00005 for user DDIC (000f0004).

                MainProg=SAPLSDB2, Incl=LSDB2U13, Line=26

I check the trace for OCS_QUEUE_IMPORT in SM50. The status is in ON HOLD , reason RFC. This trace is not updating.

I didn't find any dumps and any logs in SM21.

We have removed the rdisp/max_wprun_time parameter in instance profile.

Regards

Raghu