Shared Server (MTS) Diagnostics

Architecture, of the Shared Server Database Configuration

The best position to be in will always be based on understanding. The components of the Shared Server database configuration consist of the Dispatchers and the Shared Servers. These components run as separate processes in the operating system (or threads in some operating systems). They interact with each other through the use of a Common Queue (CQ - also known as the Virtual Queue) and individual Dispatcher Queues. Both queues reside in the Shared Global Area (SGA) and are sized automatically by the database itself. Another component of Shared Server is not a process but an abstraction of the user session(more of an owned pointer), called a Virtual Circuit (VC). The communication between the Dispatchers and Shared Servers is primarily done by passing ownership of a Virtual Circuit from one to another.

Creating a Highly Available Environment for APEX Application in an Oracle Real Application Clusters

In Oracle 11g Oracle Application Express (APEX) is now a standard component in the Oracle 11g RDBMS.
The APEX component is intergration with the Oracle Database and ensures that the application builts with Oracle APEX
benefit from the reliability, security, scalability and availability offered by the Oracle database.
Oracle Real Application Cluster (RAC) is recommended for applications that require High Availability (HA), scalability,
and workload management. How can we intergrate the High Availability (HA), scalability,
and workload management functionality to the APEX module in a RAC environment
In this blog I descibe, how to use and configure APEX module in a RAC database environment.
In a normal High Availability for database enviroment is the Oracle HTTP server an unprotected feature by the Oracle Clusterware.