cdawes
VIP Member
The inability of OneWorld to consistently kill the Runbatch.exe process
occassionally causes OneWorld to be down following a cold backup.
Currently we do cold Oracle backup's that stop the JDE Queue services, waits
2 minutes for all the kill queue's, stops JDE Network services and then
stops Oracle so the database export can start. After the export the backup
script restarts Oracle, waits 2 minutes for Oracle to come up, starts JDE
Network services waits 2 minutes and then starts JDE Queue services. All
this works great most of the time. However, if a UBE is running at the time
the JDE services are stopped then Runbatch.exe will still be running and
will not be killed when the JDE services are stopped. If runbatch.exe is not
killed then the JDE services do not start the correct number of processes
(the services do start) and OneWorld is effectively unavailable in the
morning..
Has anyone else experienced this? Does anyone have an easy solution for this
(ie. an easy utility to automatically kill an NT process at a predetermined
time). We're looking at using the MKS toolkit to try and deal with this but
hopefully a OneWorld solution can be found (I do have killimmediate=1 in the
server ini but this doesn't solve the problem). I have found two SAR's that
relate to this issue (3508897 and 4089313) but they obly state that the
problem has been corrected in B9.........not too much use to me right now.
Thanks
Colin
Colin Dawes, MSc
City of Guelph
B7332 SP15.1_009, Oracle 8.1.6.3.4, NT 4.0, Fat, WTS, Citrix
P.S. Happy Canada Day!!!
Colin Dawes, MSc
City of Guelph
B7332 SP13.1, Oracle 8.1.6, NT 4.0, Fat & WTS
occassionally causes OneWorld to be down following a cold backup.
Currently we do cold Oracle backup's that stop the JDE Queue services, waits
2 minutes for all the kill queue's, stops JDE Network services and then
stops Oracle so the database export can start. After the export the backup
script restarts Oracle, waits 2 minutes for Oracle to come up, starts JDE
Network services waits 2 minutes and then starts JDE Queue services. All
this works great most of the time. However, if a UBE is running at the time
the JDE services are stopped then Runbatch.exe will still be running and
will not be killed when the JDE services are stopped. If runbatch.exe is not
killed then the JDE services do not start the correct number of processes
(the services do start) and OneWorld is effectively unavailable in the
morning..
Has anyone else experienced this? Does anyone have an easy solution for this
(ie. an easy utility to automatically kill an NT process at a predetermined
time). We're looking at using the MKS toolkit to try and deal with this but
hopefully a OneWorld solution can be found (I do have killimmediate=1 in the
server ini but this doesn't solve the problem). I have found two SAR's that
relate to this issue (3508897 and 4089313) but they obly state that the
problem has been corrected in B9.........not too much use to me right now.
Thanks
Colin
Colin Dawes, MSc
City of Guelph
B7332 SP15.1_009, Oracle 8.1.6.3.4, NT 4.0, Fat, WTS, Citrix
P.S. Happy Canada Day!!!
Colin Dawes, MSc
City of Guelph
B7332 SP13.1, Oracle 8.1.6, NT 4.0, Fat & WTS