Reply from kiran34777 on Nov 24 at 5:53 AM Hi,
Please check whether you have configured the log on load balance. If it is
SMLGd, the jobs would get distributed to other servers if they won't get
the free available work processes on the applications.
Also schedule RDDIMPDP in regular intervals.
| | | ---------------Original Message---------------
From: LiamC
Sent: Thursday, November 20, 2014 7:03 AM
Subject: Background Jobs Getting Stuck In Ready Status
Hi,
We are currently experiencing an issue with certain background jobs being scheduled/triggered but then getting stuck in ready status and not processing when it gets to their start time.
When they get stuck in ready status we can see in sm37 that the executing server is always the application server.
Our central server is a unix system and our application server(s) are windows both running on the oracle db hosted on the central server.
The jobs that are getting stuck are both technical (RDDIMPDP, SAP_COLLECTOR_PERFMON etc) and user triggered jobs.
I've noticed that sometimes we receive messages stating 'unable to connect to oracle' which im assuming is related as these seem to have picked up with the increase in stuck jobs.
and in work process logs these messages keep appearing:
dblink[db_reconnect]: { new_reconnect_message=1
dbcon[db_con_reconnect]: { reco_trials=3, reco_sleep_time=5
00: name=R/3, con_id=000000000, state=INACTIVE , tx=NO , bc=NO , hc=NO , perm=YES, reco=NO , info=NO ,
timeout=000, con_max=255, con_opt=255, occ=NO , prog=
dbcon[db_con_reconnect]: } rc=0
***LOG BV4=> reconnect state is set for the work process [dblink 1999]
***LOG BYY=> work process left reconnect status [dblink 2000]
dblink[db_reconnect]: } rc=0
ThHdlReconnect: reconnect o.k.
Does anyone have an idea of where to look to resolve this?
We have looked at sap note 1902517 and tried various values for parameters SQLNET.SEND_TIMEOUT & SQLNET.RECV_TIMEOUT but they have not resolved this. Since upgrading our kernel and support packs on the system it seems to have worsened in our dev environment too (where these parameters were changed).
The only way to get round this is to go in sm37 and start the job off manually but it is too much time to do this for every stuck job.
Let me know if you want more information and thanks in advance
Liam |
| Reply to this email to post your response. __.____._ |   _.____.__ |
