Scalable operation
In scalable operation with Oracle RAC, Oracle instances are operated on all nodes. The clients can access to the database regardless of which node they are connected to.
Standby operation
In standby operation, a cluster system consists of operating nodes and standby nodes. On the operating node, the resources such as Oracle applications, a logical IP address and shared disks are active. On the standby node, these resources are inactive. In the event of a failure, userApplication is switched to the standby node, and the resources on this standby node become activated. Then, the client can connect itself to the operating node using the logical IP address without changing any settings.
Note
In order to use Oracle ASM of Oracle Database 11g R2 or later, it is necessary to install Oracle Grid Infrastructure. When installing Oracle Grid Infrastructure, the composition which separates the installation user of Oracle database and the installation user of Oracle Grid Infrastructure is supported. The composition which creating one user is not supported.
A different directory must be assigned respectively for an ORACLE_BASE of the installation user of Oracle Database and an ORACLE_BASE of the installation user of Oracle Grid Infrastructure.
When using PRIMECLUSTER Wizard for Oracle with an Oracle Solaris Zones environment, refer to "Appendix E Using PRIMECLUSTER Wizard for Oracle in Oracle Solaris Zones Environment".
Standby database cluster operation using Oracle Data Guard/Oracle Active Data Guard
Scalable operation
In the scalable operation with Oracle RAC using Oracle Data Guard, Oracle Database operates in all nodes on the primary site. In the standby site, Oracle Database operates in all nodes or in one node of them. You must set and operate apply services to start in one of the nodes.
Standby operation
In the standby operation using Oracle Data Guard, the operating node and the standby node exist on the primary site and the standby site. Oracle Database operates in the operating node of each site. In the event of a failure, userApplication is switched to the standby node, and the resources in this standby node become activated.
Single-Node Cluster operation
In Single-Node Cluster operation, a cluster system consists of one node.
The status of Oracle database is monitored. Oracle database operation can be continued by restarting Oracle database automatically if Oracle database failures are detected.
Note
In order to use Oracle ASM of Oracle Database 11g R2 or later, it is necessary to install Oracle Grid Infrastructure. When installing Oracle Grid Infrastructure, the composition which separates the installation user of Oracle database and the installation user of Oracle Grid Infrastructure is supported. The composition which creating one user is not supported.
A different directory must be assigned respectively for an ORACLE_BASE of the installation user of Oracle database and an ORACLE_BASE of the installation user of Oracle Grid Infrastructure.
When using PRIMECLUSTER Wizard for Oracle with an Oracle Solaris Zones environment, refer to "Appendix E Using PRIMECLUSTER Wizard for Oracle in Oracle Solaris Zones Environment".
Information
For further details about the operation modes of Scalable operation, Standby operation and Single-Node Cluster operation, refer to "PRIMECLUSTER Installation and Administration Guide".
Multitenant configuration
The multitenant configuration is supported by the standby operation or the single-Node Cluster operation. The starting, the stopping and the monitoring of CDB are the same as Oracle instance. After CDB is started, PDBs are started. When fault of PDBs is detected, the message is output to syslog. The restart and the failover due to fault of PDBs is not executed.
1-252 PDBs(upper bound of Oracle Database) can be managed.
The single tenant configuration with only one PDB in CDB is supported.
