This section provides two active/standby configuration examples, shown in Figure 1and Figure 2. In these configurations, Server 1 is considered active because it has exclusive access to the database. Server 2 does other processing. If Server 1 fails, Server 2 gains access to the database and LifeKeeper re-establishes the database operations.
Figure 1. Active/Standby Configuration, Example 1
Configuration Notes:
Each server has its own $ORACLE_HOME directory on a non-shared disk. Each server has the same version of the Oracle application.
The $ORACLE_HOME path is the same on both servers.
The database, databaseA, is on a shared disk.
Creating a resource hierarchy on Server 1:
| Server: |
Server1 |
| ORACLE_SID for Database: |
databaseA |
| Username for Database: |
system |
| Password for Username: |
********** |
| ORACLE_SID for Database: |
/home1/oracle |
| Database Tag: |
databaseA-on-server1 |
Extending the resource hierarchy to Server 2:
| Template Server: |
Server1 |
| Tag to Extend: |
databaseA-on-server1 |
| Target Server: |
Server2 |
| Target Priority: |
10 |
| Database Tag: |
databaseA-on-server1 |
Figure 2. Active/Standby Configuration, Example 2
Configuration Notes:
- Both servers use the $ORACLE_HOME directory on a shared disk.
- The $ORACLE_HOME path is the same on both servers.
- The database, databaseA, is on a shared disk.
- Server 2 can not access files and directories on the shared disk while Server 1 is active.
- $ORACLE HOME can be on the same shared disk as the database or on separate disks.
Creating a resource hierarchy on Server 1:
| Server: |
Server1 |
| ORACLE_SID for Database: |
databaseA |
| Username for Database: |
system |
| Password for Username: |
********** |
| ORACLE_HOME for Database: |
/shr1/oracle |
| Database Tag: |
databaseA-on-server1 |
Extending the resource hierarchy to Server 2:
| Template Server: |
Server1 |
| Tag to Extend: |
databaseA-on-server1 |
| Target Server: |
Server2 |
| Target Priority: |
10 |
| Database Tag: |
databaseA-on-server1 |
このトピックへフィードバック