Skip to main content

HIGH LEVEL STEPS TO SETUP A STANDBY DATABASE IN ORACLE


1) The database has to be archive log mode

2) Force Logging should be enabled.

3) The DBNAME will be the same in Primary and standby but DB unique name will be different.

4) Need to alter => ALTER SYSTEM SET LOG_ARCHIVE_CONFIG='DG_CONFIG=(DB11G,DB11G_STBY)';

5) Need to alter log_archive_dest_2 and enable it

6) REMOTE_LOGIN_PASSWORDFILE = { shared | exclusive | none } should exclusive

7) ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT=AUTO;

8) add entries in tnsnames.ora file in primary and standby side.

9) backup primary database.

10) create a standby control file => ALTER DATABASE CREATE STANDBY CONTROLFILE AS '/tmp/db11g_stby.ctl';

11) CREATE PFILE='/tmp/initDB11G_stby.ora' FROM SPFILE;

12) Amend the PFILE making the entries relevant for the standby database

*.db_unique_name='DB11G_STBY'

*.fal_server='DB11G'

*.log_archive_dest_2='SERVICE=db11g ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=DB11G'

13) Create the necessary directories on the standby server.

14) Copy the files from the primary to the standby server.

15) Remote login password file.

16) CREATE SPFILE FROM PFILE='/tmp/initDB11G_stby.ora'

17) startup mount => restore database

18) create redo logs => we can start MRP process

 
NOTE: FOLLOW BELOW STEPS CREATE STANDBY FROM ACTIVE DATABASE:

19) Standby Server Setup (DUPLICATE)

20) Create Standby Redo Logs on Primary Server

21) Create Standby Using DUPLICATE => STARTUP NOMOUNT PFILE='/tmp/initDB11G_stby.ora';

22) rman TARGET sys/password@DB11G AUXILIARY sys/password@DB11G_STBY

23) DUPLICATE TARGET DATABASE

  FOR STANDBY

  FROM ACTIVE DATABASE

  DORECOVER

  SPFILE

    SET db_unique_name='DB11G_STBY' COMMENT 'Is standby'

    SET LOG_ARCHIVE_DEST_2='SERVICE=db11g ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=DB11G'

    SET FAL_SERVER='DB11G' COMMENT 'Is primary'

  NOFILENAMECHECK;

24) Nornal => ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;

25) RTA => ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE;

26) SELECT protection_mode FROM v$database;

Comments

Popular posts from this blog

ORA-28007: THE PASSWORD CANNOT NE REUSED

             - Here will see how to deal with  => ORA-28007: the password cannot be reused -  I got a request from client user, stating his account has been locked. When I check the status of the account I found the below. connect to SYS user & execute the below query of that database. SQL> select password,username,account_status,profile from dba_users where username='TEST'; PASSWORD               USERNAME   ACCOUNT_STATUS                 PROFILE ------------------             ----------------  -------------------------------           -------------------- AB2Aa8AC9971521e3     TEST       EXPIRED(GRACE)&LOCKED    NONAPP_USERS So, then I have unlocked the account and checked the same again & I found the below results. ...

CHANGING DBID FOR ORACLE DATABASE 11G

C:\Users\computer>sqlplus SQL*Plus: Release 11.1.0.7.0 - Production on Thu Sep 10 21:03:33 2013 Copyright (c) 1982, 2008, Oracle.  All rights reserved. Enter user-name: sys as sysdba Enter password: Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL> select dbid from v$database;       DBID ---------- 2188161033 SQL> exit Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production With the Partitioning, OLAP, Data Mining and Real Application Testing options C:\Users\computer>nid DBNEWID: Release 11.1.0.7.0 - Production on Thu Sep 10 21:04:44 2013 Copyright (c) 1982, 2007, Oracle.  All rights reserved. Keyword     Description                    (Default) ---------------------------------------------------- TARGET ...