There may be more to it on Windows, but this problem has also occurred on
Unix (HP). It is in some sense a concurrent manager problem. Sometimes they
don't want to quit. I believe the standard stop command lets them execute
until they can shut down cleanly.
I have heard it recommended that the concurrent managers should be shut down
a couple of hours before the time of the backup so that they are down when
the backup needs to run. We have not resorted to that, but we do run a
pre-exec script on the cold backup that uses remshell to execute an "apps
stop" on the appstier, and waits for a signal that the apps have indeed
stopped. Then it continue with a db shutdown, and backup. Of course there is
a timeout so that if it takes too long to shutdown apps, the db shutdown and
backup go ahead anyway.
| Henry A.L. Wollman Rejoice and be glad!
|_____________________________________________________
| Moody Bible Institute, Database Administrator, [Email address protected]
| 820 N. LaSalle Blvd, Chicago, IL 60610 312-329-2291
|_____________________________________________________
-----Original Message-----
From: Paul Murgatroyd
[mailto:oracledba-ezmlmshield-x58706951.[Email address protected]
Sent: Tuesday, April 05, 2005 8:15 AM
To: LazyDBA Discussion
Subject: Re: Shutting down the Concurrent Manager on 11.5.9 (Windows 2000)
Windows and the Concurrent Manager has always been problematic. The real
issue is that Windows gets impatient. If you are just doing a "normal"
Concurrent Manager shutdown, if you have long running jobs on the Concurrent
Manager, the FNDLIBR will remain active for as long as the job runs. Only
when all running jobs are complete will the Internal Manager (and FNDSM)
shut down as well.
To get around the "problem", I bypassed the "Net stop <OracleConcMgr<SID>"
crap, and simply wrote a quick batch file that issues a CONCSUB FND ABORT
(or STOP). That will do exactly the same thing, and the service will also
stop when it is completed.
That is the best I could do on Windows!
Paul
*********** ORIGINAL MESSAGE ***********
On 5/04/2005 at 8:25 AM Cohn Grant wrote:
Hi All
We have a fairly new Oracle Financials 11i installation running on a
two-tier Windows platform.
One server is running the database and the concurrent manager and the
other server runs the forms server and Apache.
I am having huge problems trying to automate the shutdown (and
subsequent cold backup) or the database: The Concurrent Manager Service
will not stop! - so then the database will not stop.
I have tried the Oracle supplied scripts and have tried the 'NET STOP
<Service Name>' : Both result in the error "Could not stop the
OracleConcMgr<SID> service on local Computer. Error 1053 The service did
not respond to the request in a timely fashion"
The only way I can achieve this is by killing all the FNDLIBR.exe
processes left after the Attempt to stop the service fails.
Agreed....... A terrible way to do things.
Has anyone successfully managed to get scripts (ON WINDOWS 2000) to
gracefully shut the database and all other Oracle services down??
I end up having to do this manually from home late at night.
Many thanks
Grant Cohn
Sapref
DURBAN
--------
website: http://www.LazyDBA.com
Please don't reply to RTFM questions
Oracle documentation is here: http://tahiti.oracle.com
To unsubscribe: see http://www.lazydba.com/unsubscribe.html
To subscribe: see http://www.lazydba.com
By using this list you agree to these
terms:http://www.lazydba.com/legal.html
--------
website: http://www.LazyDBA.com
Please don't reply to RTFM questions
Oracle documentation is here: http://tahiti.oracle.com
To unsubscribe: see http://www.lazydba.com/unsubscribe.html
To subscribe: see http://www.lazydba.com
By using this list you agree to these
terms:http://www.lazydba.com/legal.html
Oracle LazyDBA home page