cancel
Showing results for 
Search instead for 
Did you mean: 

OCS_QUEUE_IMPORT is running long time during ST\A-PI patch upgrade

farkathulla_cikkanther
Active Participant
0 Kudos

Hello Friends,

   We applying support package ST\A-PI(SAPKITAB7L), It has running long time on IMPORT_PROPER phase.

Also the BTC workprocess status shows as stop and the reason as RFC.

And the below BG jobs are in active from long back(same job has running 2 times).

When i try the job SAP_SLD_DATA_COLLECT in other system, It has finished with in 100 sec.

When the OCS_QUEUE_IMPORT will start .

Can i kill the SAP_SLD_DATA_COLLECT Job ?

Please Guide in this.

Regards,

Farkath C

Accepted Solutions (1)

Accepted Solutions (1)

former_member264034
Active Contributor
0 Kudos

Hi,


You should check dev_w12 work process trace to see if there is an error here
which might explain the long runtime.

Kind Regards,
Aidan

farkathulla_cikkanther
Active Participant
0 Kudos

Hello Aidan,

   I can see the below lon in SLOG file at os level.

START imp all              TST        20150428022823              DDIC         sap2tstsrv 20150428022823725  

INFO: event SAP_IMPORT_START triggered successfully

INFO  TBATG CONVERSION OF  TST N      not needed                  DDIC         sap2tstsrv 20150428022823725  

START MOVE NAMETABS        TST 6      20150428022824              DDIC         sap2tstsrv 20150428022823725  

START tp_getprots          TST 6      20150428022824              DDIC         sap2tstsrv 20150428022823725  

WARNING: System TST. Warning.        20150428023229 :

WARNING:       Background job RDDIMPDP could not be started or terminated abnormally.

      Please check that the R/3 system is running.

      Please check the system. Use transactions SM21, SM37, SM50.

WARNING:       (This warning is harmless if no further warnings follow.)

WARNING: System TST. Warning.        20150428023729 :

WARNING:       Background job RDDIMPDP could not be started or terminated abnormally.

      Please check that the R/3 system is running.

      Please check the system. Use transactions SM21, SM37, SM50.

WARNING:       (This warning is harmless if no further warnings follow.)

WARNING: System TST. Warning.        20150428024229 :

WARNING:       Background job RDDIMPDP could not be started or terminated abnormally.

      Please check that the R/3 system is running.

      Please check the system. Use transactions SM21, SM37, SM50.

What could be the reason.

Guide me.

Regards,

Farkath C

former_member264034
Active Contributor
0 Kudos

Hi Farkath,

In SM37 check for any cancelled or active RDD* jobs.


Please check the following note carefully:

  449270 - Job RDDIMPDP is not triggered by sapevt

Regards,
Aidan

former_member185954
Active Contributor
0 Kudos

Hello Farkathulla,

Are all batch processes occupied ?

If they are ? you can terminate the SAP_SLD_DATA_COLLECT job to allow for the RDDIMPDP job run.

Do not stop/start the system as your system may start in inconsistent state.

Regards,

siddhesh

farkathulla_cikkanther
Active Participant
0 Kudos

Hello Siddhesh,

  When i ran the Data collector as dialog mode in rz70, It throws a time_out dump.

I have already Increased BG-Wp in rz04 but in WP table only 3 BTC processors are available.

What are the possible ways to resolve this issue with out restarting instance.

Thanks,

Regards,

Farkath C

farkathulla_cikkanther
Active Participant
0 Kudos

Hello,

  There is no any cancelled or active jobs available for RDDIMPDP.

Regards,

Farkath C

former_member185954
Active Contributor
0 Kudos

Hello Farkathulla,

After you increased the btc processes, are you seeing any changes in Transport logs, does the log show that that RDDIMPDP is now running ?

Please check in SM37 for recent runs of RDDIMPDP

Regards,

Siddhesh

Former Member
0 Kudos

Hello Farkath,

You said "increased BTC with RZ04", did you perform the OP Mode switch with RZ03 ?

You have two different problems for which the various posters have offered possible solutions.

1. RZ70 ... follow up in the suggestions from the different people here. In the interim, you can cancel the running batch jobs. There's no harm or danger in doing so.

2. Hanging import. As has been suggested, please increase the number of BTC and make sure you perform a OP Mode switch after you have adapted RZ04.

In any case, by terminating the blocked SLD jobs, you'll release 2 BTC which will allow the RDDIMPDP to run.

Kindest Regards,

Amerjit

Former Member
0 Kudos

Just in case it is unclear. I am only talking about cancelling the running SLD jobs.

farkathulla_cikkanther
Active Participant
0 Kudos

Hello Siddhesh,

  Once i terminate the job SAP_SLD_DATA_COLLECT, It has finished successfully.

ST\A-PI patch has upgraded successfully.

Thanks for your input.

Regards,

Farkath C

former_member185954
Active Contributor
0 Kudos

Great, as they say 'Patience always pays'

Answers (3)

Answers (3)

former_member182657
Active Contributor
0 Kudos

Hi,


Background job RDDIMPDP could not be started or terminated abnormally.

Try to locate the above mentioned job under SM37 & share job logs,If possible try to restart complete system & re-perform the complete activity.

Hope this will help you.

Good luck !!

farkathulla_cikkanther
Active Participant
0 Kudos

Hello Guavrav,

   There is no any cancelled jobs available for RDDIMPDP job.

Regards,

Farkath C

former_member189797
Active Contributor
0 Kudos

Hello Farkath,

Could you check if below note is applicable to your scenario :
2109609 - import hangs due to unknown entries in table TRBAT (FUNCTION = C)

### Use this note only if all condition matches.

Regards,
Gaurav

former_member182657
Active Contributor
0 Kudos

Hi,

Could you check with SAP Note  1739999 - Number of SAP_SLD_DATA_COLLECT* jobs increases (2)

In addition could you share job logs for SAP_SLD_DATA_COLLECT along with system logs from SM21.

Regards,

farkathulla_cikkanther
Active Participant
0 Kudos

Hello Gaurav,

Please find the SM21 log and Job log for SAP_SLD_DATA_COLLECT.

Help me if you have find any thing,

Thanks.

Regards,

Farkath C

former_member182657
Active Contributor
0 Kudos

Hi Farkath,

Your system is filled with dumps,could you share the latest one from ST22.

Regards,

farkathulla_cikkanther
Active Participant
0 Kudos

Hi Gaurav,

All the dumps were occurred during Basis patch upgrade. Basis patches were upgraded successfully.

Only the Time out dump has occurred during this ST-A\PI patch.

Regards,

Farkath C

former_member182657
Active Contributor
0 Kudos

Hi Farkath,

Could you share dump for time out issue at your end.

Thanks,

farkathulla_cikkanther
Active Participant
0 Kudos

Hello  Guavrav,

  Please find the Time_Out dump.

Regards,

Farkath C

former_member182657
Active Contributor
0 Kudos

Unfortunately issue with low value of parameter rdisp/max_wprun_time i.e 600 secs in your case.

Reagan
Product and Topic Expert
Product and Topic Expert
0 Kudos

Have a look at this SAP note 2073816 - RZ70 hangs in endless loop

It appears to me that you are hitting the bug mentioned in the above SAP note.

Regarding the OCS job, perform a "Check Status" of the job from Tx SM37 and see if it changes.

farkathulla_cikkanther
Active Participant
0 Kudos

Hello Reagan,,

  Yes, I can see the program_SLD_ASSOC, SAPLSLDAG is running again and again.

Can i implement the note now or will it require to kill the running job?

Already i terminate one data collector job in 2 running data collector jobs.

Regards,

Farkath C

Reagan
Product and Topic Expert
Product and Topic Expert
0 Kudos

First check whether the note is valid for your system. If yes then terminate the job and implement the note.

farkathulla_cikkanther
Active Participant
0 Kudos

Hello Reagan,

  Thanks for your input,

this note has resolved Data collector issue in RZ70.

Thanks again.

Regards,

Farkath C

former_member185954
Active Contributor
0 Kudos

Hello,

The import jobs are event driven, they will run when they need to, if you check /usr/sap/trans/tmp directory, you may find some log being updated frequently, which means R3trans is running at OS level.

Not sure what your OS is, but try to check if R3trans and tp processes running at OS level, if they are, don't terminate any jobs, let them run.

If you figure out during your investigation that its waiting for batch process to be free, you can dynamically increase Batch processes, by using Operation modes (RZ04).

Regards,

Siddhesh