1.What is the difference between stopping the services of a database and shutting it down through svrmgrl.
2.What if some one shutdown the database server without stopping the services or shutting down the database through svrmgrl.
I presume that you are running oracle in Windows NT. Im not really sure with this, but you need the services to automate the startup and shutdown of your database. During startup, Windows NT runs these services, with this you dont need to startup of database manually in server manager the same goes when you shutdown the server, it stops the services thus shutting down your database.
have few desires. LAO TZU
when you shutdown or startup the service the process invokes the file oracle.exe along with the corresponding database to start the database or shutdown the database just like what you do with the startup and shutdown command thru svrmgrl.
No problem somebody can surely shutdown the database server the service will automatically shutdown the database
Someone correct me if I'm wrong.... But, I've always been of the understanding that you want to shutdown the DB through svrmgrl before shutting down the services. By shutting down the services only, the DB does not shutdown cleanly. Only by shutting down through svrmgrl with a valid shutdown command (shutdown immediate, etc) will the DB shutdown cleanly.
With net stop OracleServiceSid (shutdown the service) you are doing a database shutdown clean too.
If it is true that I shutdown cleanly by only shutting down services, then why do I receive msgs such as
"Beginning crash recovery of 1 threads"
"Thread recovery: finish rolling forward thread 1
Thread recovery: 0 blocks read, 0 blocks written
Crash recovery completed successfully"
only when I have not shutdown in svrmgrl and only shutdown my Oracle NT services?
Just trying to understand.......
Yes true if any users are connected the Oracle Service does a
If none of the users are connected it does a normal shutdown
It is allways better to shutdown the database thru svrmgrl in windows.In fact I have seen in windows NT the oracle service does a
You need to look at your Oracle alert log file to find out how is the database being bought down
The service is just NT's mechanism for allocating the memory space in the OS for the Oracle.exe to run in. NT runs all threads in the same service (UNIX runs each process in a separate OS process)
You can shut down the instance with a 'shutdown' in svrmgrl, which leaves the service running. I personally prefer to do this if I want to get a clean shutdown, UNLESS you have the services set up right. There is a way to create another service that runs a script and starts/stops the instance and the service. (so you'd have two services per instance, one to start/stop and another to run Oracle) If it's 8.1.5 or better, it should handle this for you, and I *believe* 2000 only needs the one service. (not sure on this)
If you're getting crash recovery messages in your alert log, then your service is NOT handling the clean shutdown of the instance--the OS is pulling the rug out from under the Oracle process. So it's doing an instance recovery every time it comes back up. It only matters if it is not for personal use and you're taking cold backups or care about those log messages.
At one point using the NT Service Panel to stop the Oracle service was the equivalent of a SHUTDOWN ABORT (this goes back to early 8.0.x). THis is why you are seeing instance recovery on restart.
We ran into this because we had some long running transactions (loads, etc.) that were aborted. Recovery took almost as long as the load had been running.
Joseph R.P. Maloney, CSP,CDP,CCP
'The answer is 42'
Click Here to Expand Forum to Full Width