Step 1: Create a Physical Standby Database
Following the steps in the prior section of this chapter, create a physical standby database. After
you create and start up the physical standby, stop Redo Apply on the physical standby to avoid
applying changes past the redo that contains the supplemental log information:
alter database recover managed standby database cancel;
?–
?–
?–
?–
?–
?–
?–
?–
?–
Chapter 13: Oracle Data Guard 485
Step 2: Enable Supplemental Logging
Supplemental logging on the primary database generates additional information in the redo log.
That information is then used during the redo application process in the standby database to make
sure the correct rows are affected by the generated SQL. To add primary key and unique index
information to the redo data, issue the following command in the primary database:
execute dbms_logstdby.build;
This procedure waits for all existing transactions to complete; if there are long-running
transactions on the primary database, this process will not finish until those transactions
commit or roll back.
Step 3: Transition the Physical Standby to a Logical Standby
The redo log files have the information necessary to convert your physical database to a logical
database; run this command to continue redo log data application to the physical standby database
until the moment you??™re ready to convert to a logical standby:
alter database recover to logical standby new_db_name;
Oracle automatically stores the name of your new logical standby database, new_db_name, in
the SPFILE.
Pages:
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736