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;
Labels:

Comments

Post a Comment

Popular posts from this blog

ORA-39014: One or more workers have prematurely exited.ORA-00018: maximum number of sessions exceeded

ERROR: I was Performing a full database import and during the import I faced the below error. ORA-39014: One or more workers have prematurely exited. ORA-39029: worker 6 with process name "DW07" prematurely terminated ORA-31672: Worker process DW07 died unexpectedly. Job "SYSTEM"."SYS_IMPORT_FULL_04" stopped due to fatal error at 00:59:40 ORA-39014: One or more workers have prematurely exited. SOLUTION:  Run the import with fewer parallel processes, like PARALLEL=2 instead of 8. I was able to run the import successfully. NOTE 1: This errors occurs when there are less session allocation in the database. check the session,process parameters and increase them accordingly. To avoid such errors again. NOTE 2 : Note: Increasing processes parameter increases the amount of shared memory that needs to be reserved & the OS must be configured to support the larger amount of shared memory. So here we first need to increase the Memory & SG...
Post a Comment
Read more

ORA-01143: cannot disable media recovery - file 1 needs media recovery

I got a request from the client - To flashback the database to the existing restore point & disable flashback and archive log mode for database UATB. Here I came a cross error - ORA-01143. I followed the below steps. 1. SQL> select name from v$database; NAME ------------ UATB 2. SQL> SELECT NAME FROM V$RESTORE_POINT WHERE GUARANTEE_FLASHBACK_DATABASE='YES' ORDER BY TIME; NAME --------- UATB_COPY Here I'm going to restore the database to the above restore point. NOTE: The flashback database restore has to be done in MOUNT stage of the database. SQL> select name from v$database; NAME --------- UATB SQL> shut immediate; Database closed. Database dismounted. ORACLE instance shut down. SQL> startup mount ORACLE instance started. Total System Global Area  612368384 bytes Fixed Size                  1250428 bytes Variable Size             167775108 bytes ...
2 comments
Read more