Shared Server Process

Question

I have one query regarding Shared Server Process.
1)Why SHUTDOWN needs dedicated server process and not shared server process?
Thanks in advance

Answer 1

>
1)Why SHUTDOWN needs dedicated server process and not shared server process?
>
Because Oracle maintains the connection for the user performing the shutdown until the shutdown is complete and their is still more work to be performed after the shared server processes are shutdown.
If you look at the shutdown part of the alert log when a shutdown is performed you will see that the dispatchers and shareds servers are shutdown before the database is closed and dismounted. There would be no more connection if a shared server were being used.
Consider the example shutdown log from this article
http://oracleappstechnology.blogspot.com/2007/08/oracle-11g-db-startup-and-shutdown.html
Find the portion that shows these steps
>
All dispatchers and shared servers shutdown
ALTER DATABASE CLOSE NORMAL
Wed Aug 15 18:24:35 2007
SMON: disabling tx recovery
SMON: disabling cache recovery
Wed Aug 15 18:24:35 2007
Shutting down archive processes
>
See how the CLOSE is issued AFTER the dispatchers and shared servers are shutdown?
See how the SMON service is still running?
If you then look at the very end you will see this
>
Stopping background process VKTM:
>
That last background process is described in chapter 9 (Process Architecture) in the Database Concepts doc
http://docs.oracle.com/cd/B28359_01/server.111/b28318/process.htm
>
•VKTM (virtual keeper of time) is responsible for providing a wall-clock time (updated every second) and reference-time counter (updated every 20 ms and available only when running at elevated priority).
>
Grandfather time is the last process to be stopped.
When your time comes to an end - you too will be 'shutdown' (chances of a successful recovery are not good even with extensive logs).
Here's hoping that your personal shutdown is 'normal' and not 'immediate' or 'abort'!