Active DataGuard 11.2

Converting Physical Standby database to an Active Dataguard

This is a continuation of my previous articles on Oracle Dataguard 11.2. If you have inquiries, please let me know and I will be happy to answer them as soon as I can.

Thanks.

Let's share and make others love Oracle, too.

========================================================================


Introduction:

Active Dataguard provides the capability to have read-only access to a physical standby database. The standby database can be used for queries, sorting, and reporting. For RMAN, it allows fast incremental backups when offloading backups to a standby database. Converting a physical standby database to an active Dataguard incurs additional licensing fees.


Steps in converting Physical Standby database to Active Dataguard


1.    Follow the steps presented in the section: Check the redo transport and redo apply
2.    Convert the physical standby database to active dataguard

If coming from a functional physical standby:

SQL> alter database recover managed standby database cancel;
SQL> alter database open;
SQL> alter database recover managed standby database
     disconnect;

If coming from shutdown:

SQL> startup nomount;
SQL> alter database mount;
SQL> alter database recover managed standby database
     disconnect;
SQL> alter database recover managed standby database cancel;
SQL> alter database open;
SQL> alter database recover managed standby database
     disconnect;


3.    To perform a switch-over or fail-over, follow the steps shown in the section: Validate the Dataguard Functionality (which is written on my previous article: Oracle DataGuard 11g R2 Administration)

Comments

Post a Comment

Popular posts from this blog

RMAN Restoration to New Server with Different Directory and New Database Name

In this case, I have an existing production database with RMAN Level 0 backup: CONFIGURE CONTROLFILE AUTOBACKUP ON; CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'C:\flash_recovery_area\galaxy\backupsets\autobackup\SAMSUNG-ctl_%F'; CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS; CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'C:\flash_recovery_area\galaxy\backupsets\level0\level0-%d-%T-%U' MAXPIECESIZE 4G; DELETE NOPROMPT ARCHIVELOG ALL COMPLETED BEFORE 'SYSDATE - 7'; SHOW ALL; REPORT SCHEMA; LIST BACKUP OF DATABASE; REPORT NEED BACKUP; REPORT UNRECOVERABLE; LIST EXPIRED BACKUP BY FILE; LIST ARCHIVELOG ALL; REPORT OBSOLETE; CROSSCHECK BACKUP DEVICE TYPE DISK; CROSSCHECK COPY OF ARCHIVELOG ALL; DELETE NOPROMPT EXPIRED BACKUP DEVICE TYPE DISK; DELETE NOPROMPT OBSOLETE DEVICE TYPE DISK; RUN { sql 'alter system archive log current'; BACKUP INCREMENTAL LEVEL 0 DATABASE PLUS ARCHIVELOG DELETE INPUT; } LIST BACKUP ...
Read more

Copy and Delete Dumpfiles from ASM to Local Filesystem Automatically

Hello Everyone, So someone ask you to create a script to take a logical backup of your database and store it in ASM. You decided to create an Export DataPump script that will: 1. Take a full export of the database to +FRA 2. Take a full metadata export of the database and store it in +FRA 3. Copy the dumpfiles in +FRA to your local disk (in case the ASM instace fails) 4. Delete old dumpfiles in +FRA and in the local disk if they are past the retention period. The script provided below will: 1. Perform export datapump and store the dumpfiles in ASM 2. The dumpfiles stored in ASM will be copied to the local disk. The script will read the logfile generated by the export job. If you will take a look at the end of the export logfile, you will see there the list of dumpfiles generated, we just need to extract these string and process it using Unix scripts. Then we can form an ASMCMD command from here. When running ASMCMD command, just make sure you switch to the GRID environmen...
Read more

Oracle Export-Import with QUERY parameter on LINUX box

There's this one time when I like to purge a certain table but it is very large. It creates a lot of archive logs when I am performing delete statements using a where clause as a delimiter for the rows I'd like to delete. It is very time consuming and it eats space on the disk. And one more thing is that, there are more rows that I need to delete that the rows I need to keep. So I just tried to purge this very large table using Oracle' EXP and IMP utility. My plan is to export the rows that I want to keep and truncate the table I am purging. Afterwards, I will IMP the dumpfile into that same table. Here's what I did: Environment: OS: RHELinux 5.4 32bit DB: Oracle 10.2.0.4 SQL Query: SQL> select * from sh.sales      where time_id = to_date('28-DEC-01:00:00:00',      'DD-MON-RR:HH24:MI:SS'); The output of this query are the rows that I want to keep. My gameplan is: 1. Perform EXP using QUERY parameter. 2. T...
Read more