Reconditioning of the original Production Site and servers must commence as soon as the site
and resources become available and are secure. Proper WAN connectivity is also required to
adequately accomplish this task.
If the Original Production Site was lost due to a LAN/WAN link failure:
Test connectivity to the Standby Site thoroughly using terminal services or using the
Oracle OEM Data Guard Switchover functionality.
Insure that any modifications applied to the Operating System, services and servers
during the interim operation, are replicated to the Original Production servers
Same as above applies for the DMS application, programs and files
If any of the servers at the Original Production site were lost due to hardware failure(s):
Rebuild the failed hardware, according to the documented configuration
Install and configure the Operating System, patches, servers, and services, as well as the
DMS applications, programs, files, etc. as detailed in the documentation
Test proper connectivity to the Standby Site
Synchronize the DMS data, from the Standby to the Original Production Site:
A full hot or cold database (control files, database files, init.ora) backup of the Production
Database (located at the Standby Site) needs to be shipped to the Original Production
Site
The Database server, located at the Original Production Site needs to be configured in
Standby Database mode, as documented previously
Backed up DMS data from the Standby Site needs to be loaded at the Production Site
Activate the changes and run the Production Site’s Database server in Standby-mode,
allowing the Standby Site to send updates
Plan for a DMS service outage (during a weekend or after-hours, if possible)
Perform a Controlled Switchover, turning the Production Site’s database as the current
Production Database, effectively switching the Standby Site’s database to Standby mode
Redirect the users/clients to the recently re-enabled Production Site, using either the
manual or DNS-supported schema
To Controlled Switchover:
Standby Site: The Production Database must be properly SHUTDOWN
Production Site: The Standby Database is updated with all the archived logs and
SHUTDOWN NORMAL
Standby Site: Online Redo Logs are sent to the Standby Site
Production Site: A new controlfile is created; the Database is restarted, running now as
the Production database
Standby Site: A new controlfile is created, enabling the database in Standby mode
operation. Then the database is mounted, effectively running in Standby mode, accepting
updates and logs from the Production Site’s Database.
Upon completion of the above procedures, the Production Site hosts again the Production
Database, while the Standby database resides at the Standby Site, and the DMS application is
back to its normal mode of operation and performance.
New DMS Database and Application Server Configuration in case of a Disaster:
In case, a new database server needs to be configured; then the following steps need to be
followed to setup the DMS Application:
Install the Oracle Database on the new Database Server.
Generate the DMS Application from the Oracle Designer Repository or last backup.
o