Monday , September 25 2017
Home / Oracle DBA / SHARED SERVER ARCHITECTURE

SHARED SERVER ARCHITECTURE

 

SHARED SERVER ARCHITECTURE

SHARED SERVER ARCHITECHTURE

  1. Multiple user requests will be received by dispatcher which will be placed in request queue.
  1. Shared server processes will take information from request queue and will be processed inside the database.
  1. The results will be placed in response queue from where dispatcher will send them to corresponding users.
  1. Instead of PGA, statements will get executed in UGA (user global area) in shared server architecture.
  1. Shared server architecture can be enabled by specifying following parameters.
    1. DISPATCHERS
    2. MAX_DISPATCHERS
    3. SHARED_SERVER_PROCESSES
    4. MAX_SHARED_SERVER_PROCESSES
    5. CIRCUITS and MAX_CIRCUITS (optional)
  1. This architecture should be enabled only if ora-04030 or ora-04031 errors are observed frequently in alert log file.
  1. To make shared server architecture effective, SERVER=SHARED should be mentioned in client TNSNAMES.ORA file.
  1. A single dispatcher can handle 20 user requests where as a single shared server process can handle 16 requests concurrently.
Note: SMONn can have 16 slave processes and DBWRn can have 20 slave processes working concurrently
Note: startup and shutdown is not possible if sysdba connects through shared server connection
Read More:
ASMM (AUTOMATIC SHARED MEMORY MANAGEMENT)
PARAMETER FILE
Background Processors

Comments

comments

Check Also

How to switch on primary database to physical standby database

After configuration data guard then data is switching  into primary database  to standby database : …

Leave a Reply

Your email address will not be published. Required fields are marked *