9.7.7.2 Task 2: Configure the Sparse Test Master and Sparse Files on the Standby Site

In this task you convert the standby into a test master and create sparse files to receive and apply redo from the primary database.

Note:

During this process you will not be creating a full snapshot database, you will be using portions of the existing standby database and adding sparse data files to the standby. The standby database controlfile will be modified to use the sparse files that are added. Going forward, the same standby instance is used, but redo apply will use the sparse files to store changes, leaving the original standby data files to serve as a sparse test master files for snapshots.

The existing data files are used to support full database snapshots with data as of the point in time the process was run.

1. Shutdown all instances of the TM_STANDBY database.

   $ srvctl stop db –d tm_standby –o abort

2. Using SQL*Plus, start one of the TM_STANDBY instances in mount mode.

   SQL> startup mount

3. Change the DB_CREATE_FILE_DEST setting in the standby instance to point to the SPARSE disk group.
   This ensures all new data files that are created will reside in the SPARSE disk group. To perform this step you must disable standby file management.

   SQL> alter system set standby_file_management='MANUAL';
   SQL> alter system set db_create_file_dest='+SPARSE';

4. Run the rename_files.sql script created in Task 1 against the standby database.
   Running the script renames the data files in the TM_STANDBY controlfile and creates the sparse files for the snapshot.

   SQL> @rename_files

5. Re-enable standby file management.
   Completing this step ensures that all new data files added to the primary will automatically be created by the standby when it receives the redo to create the data file.

   SQL> alter system set standby_file_management='AUTO';

6. Enable redo apply on TM_STANDBY.
   Completing this step applies redo to the snapshot, keeping it current and preparing for the next round of snapshot creation.

   DGMGRL> edit database tm_standby set state='APPLY-ON';

7. Restart the remaining instances in mount mode.

   $ srvctl start db –d tm_standby –o mount

   Note:

   If you plan to clone a local pluggable database (PDB) at the primary database, then enable Active Data Guard mode at the standby. This requires an Active Data Guard license.

Figure 9-15 Configuration with Test Master Files and Sparse Files for Redo Apply

Description of "Figure 9-15 Configuration with Test Master Files and Sparse Files for Redo Apply"