Synchronize and Create Backups

Now that you've completed the configuration and have a fully running PeopleSoft application, you can create backups.

Convert the Standby Database Back to a Physical Standby

Convert the snapshot standby back to a physical standby and allow it to be synchronized with production and apply all outstanding redo.

1. On each compute instance of the PIA and Application tier, shut down the PeopleSoft application using the scripts in Basic Tasks.
2. As the user oracle, in the home directory, source the standby database environment.

   $ . ./CDBHCM.env

3. Start Data Guard Broker and enter the SYS password.

   $ dgmgrl

4. As the oracle user on any of the Oracle Exadata Database Service on Dedicated Infrastructure domUs, use Data Guard Broker to convert the snapshot standby database back to a physical standby.

   DGMGRL> convert database CDBHCM_iad1dx to physical standby
   Converting database "CDBHCM_iad1dx" to a Physical Standby database, please wait...
   Database "CDBHCM_iad1dx" converted successfully

5. Wait a few minutes to allow the managed recover process (MRP) to start applying redo. Then while still logged into Data Guard Broker, show the configuration

   DGMGRL> show configuration lag
   
   Configuration - ZDM_ CDBHCM_iad1dx
   
     Protection Mode: MaxPerformance
     Members:
      CDBHCM_sca6dp - Primary database
      CDBHCM_iad1dx  - Physical standby database 
                        Transport Lag:      0 seconds (computed 2 seconds ago)
                        Apply Lag:          10 minutes 14 seconds (computed 2 seconds ago)
         CDBHCM_phx5s - Physical standby database (receiving current redo)
                        Transport Lag:      1 second (computed 1 second ago)
                        Apply Lag:          2 seconds (computed 1 second ago)
   
   Fast-Start Failover:  Disabled
   
   Configuration Status:
   SUCCESS   (status updated 60 seconds ago)

   You may see warnings indicating that the transport lag has exceeded thresholds. This warning will go away after several minutes.

6. Continue to show the configuration until both Transport Lag and Apply Lag reach 0 minutes and as close to 0 seconds.
   At that point, the physical standby is within the lag thresholds and is caught up with the primary database.