Configuring HP Serviceguard Toolkit for Oracle Data Guard

following SQL statement:

SQL> ALTER DATABASE FORCE LOGGING;

2. Create a password file:

Create a password file if one does not already exist. Every database in a Data Guard

configuration must use a password file, and the password for the SYS user must be identical on

every system for redo data transmission to succeed.

3. Setting the primary database initialization parameters:

On the primary database, define initialization parameters that control log transport services while

the database is in the primary role.

4. Enable archiving:

If archiving is not enabled, issue the following statements to put the primary database in

ARCHIVELOG mode and enable automatic archiving:

SQL> SHUTDOWN IMMEDIATE;

SQL> STARTUP MOUNT;

SQL> ALTER DATABASE ARCHIVELOG;

SQL> ALTER DATABASE OPEN;

5. It is recommended that the online redo log files are created on the shared disk so that when a

local failover of the primary database instance occurs, the online redo logs are also accessible to

the new instance on the adoptive node. Here’s a sample SQL statement that adds a new group of

redo logs to the database:

SQL> ALTER DATABASE ADD LOGFILE (“<oracle_redo_file_1>.rdo,”

“<oracle_redo_file_2>.rdo”) SIZE 500K;

Creating a physical standby database

1. Create a backup copy of the primary database data files:

You can use any backup copy of the primary database to create the physical standby database as

long as you have the necessary archived redo log files to completely recover the database. Oracle

recommends that you use the Recovery Manager utility (RMAN).

2. Create a control file for the standby database:

If the backup procedure required you to shut down the primary database, issue the following

SQL*Plus statement to start the primary database:

SQL> STARTUP MOUNT;

Then create the control file for the standby database, and open the primary database to user

access, as shown in the following example:

SQL> ALTER DATABASE CREATE STANDBY CONTROLFILE AS “/tmp/standby.ctl”;

SQL> ALTER DATABASE OPEN;

3. Prepare an initialization parameter file for the standby database.

4. Copy files from the primary system to the standby system:

Use an operating system copy utility to copy the following files from the primary system to the

standby system:

Backup data files

Standby control file

Initialization parameter file

5. Set up the environment to support the standby database:

a. Create a password file.

Create a password file, and set the password for the SYS user to the same password used by

the SYS user on the primary database. The password for the SYS user on every database in

a Data Guard configuration must be identical for redo transmission to succeed.