Thursday, 16 May 2013

Dataguard Configuration Steps (Disaster Recovery)

DATAGUARD STEPS TESTING
Configuring the Primary Database
Enable archiving and define a local archiving destination
1. PRIMARY DATABASE SHOULD BE IN ARCHIVE MODE.
IF NOT
THEN
sql>ALTER SYSTEM ARCHIVE LOG START.

Enable forced logging

2. PRIMARY DATABASE SHOULD BE IN FORCE LOGGING MODE.
IF NOT
THEN
sql>ALTER DATABASE FORCE LOGGING

Configuring the Oracle networking files

3. ENTER THE TNS ENTRIES IN TNS FILES.FOR PRIMARY AND STANDBY DATABASE.

Set initialization parameters on the primary database

4. SET PARAMETERS FILE PARAMETERS CAREFULLY
FAL_CLIENT (IF YOU ARE ON PRIMARY THEN
PRIMARY DATABASE NAME HERE OTHERWISE STANDBY)
FAL_SERVER SAME AS PREVIOUS
LOG_ARCHIVE_DEST_2 THIS PARAMETER SHOULD BE SET ENABLE ON
PRIMARY AND DEFER ON STANDBY
LOG_ARCHIVE_DEST_STATE_2 ‘service=STANDBY DATABASE NAME
optional reopen=15
Take cold backup of the primary database

5.TAKE COLD BACKUP AND TRANSFER THESE FILES TO STANDBY DATABASE.
Create a controlfile for the standby database

6.OPEN PRIMARY AFTER COLD BACKUP AND CREATE STANDBY DATABASE
CONTROL FILE AND PARAMETER FILE.

alter database create standby controlfile as ‘/u01/app/oracle/control01.ctl’;
create pfile=’/u01/app/oracle/initTESTDB.ora’ from spfile;
Copy all files from the primary host to the standby host

7. COPY STANDBY CONTROL FILE AND PARAMETER FILE ALSO AT STANDBY

Configuring the Standby Database
Configuring the Oracle networking files

1.ENTER THE TNS ENTRIES IN TNS FILES.FOR PRIMARY AND STANDBY DATABASE.
Create a server parameter file for the standby database
IN PARAMETER FILE AT STANDBY
FAL_CLIENT ((IF YOU ARE ON PRIMARY THEN PRIMARY
DATABASE NAME HERE OTHERWISE STANDBY))
FAL_SERVER(SAME)
LOG_ARCHIVE_DEST_
LOG_ARCHIVE_DEST_STATE_2

Copy the standby controlfile to the appropriate location

2. COPY CONTROL FILES COME FROM PRIMARY DATABASE
ACCORDING TO PARAMETER FILE LOCATION.

Create Oracle Password File

3. CREATE PASSWORD FILE.
ORAPWD FILE=PATH PASSWORD=PASSWORD
Start The Physical Standby Database

4. START STANDBY ON NOMOUNT

Mount The Standby Database

5. AND MOUNT IT WITH
ALTER DATABASE MOUNT STANDBY DATABASE

Initiate log apply services

6. INITIATE REDO APPLY BY
alter database recover managed standby database disconnect from
session;
Start Remote Archiving

1. ON PRIMARY issue

alter system archive log current

Verifying the Physical Standby Database

1. use v$archived_log table (archived,applied,sequence# columns).

2. SQL> SELECT MESSAGE FROM V$DATAGUARD_STATUS;

No comments:

Post a Comment