on 04-28-2015 2:28 PM
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
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
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
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
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 !!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.