Hot DR site preparation

[Former Member]

Dear all,

We have to prepare a hot DR site of our production server using Oracle Data Guard. We are on ECC 6.0 / Win / Oracle 10g

Can anyone advice me on the steps involved in this activity?

We have to use Oracle data guard to ship the logs.

Please advice

[Former Member]

Thanks

[mohammed_anish]

Following is an outline of the steps to be followed...

1. Prepare the target host:

i. Start installing SAP using backup/restore (Homogenous system copy).

ii. When SAPINST instructs to install database software, perform the software installation using the oracle installer provided by SAP.

Rest of the things can be done only after setting up the physical standby on the target host and then switching over to the new standby and make it as primary. This is because, rest of the installation need the database to be restored and then "OPEN"ed.

1. Physical Standby Database Creation. Follow the steps in http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm

2. Activate Physical Standby database (activate "managed recovery using current logfile" and synchronize the standby with primary)

3. After the synchronization switch over to the standby database, continue SAPINST to complete database instance installation and then CI and so on.

4. Once the installation os SAP instances are done you can switch back to the old primary which is the current standby. Before doing this you may also apply a permanent license on this system so that, the step may be avoided in future failover/switchover.

Regards,

Anish

[Former Member]

hi,

you can try to find some PDF documents from oracle.com regarding this ODG stuff.

it's the best place to start.

ardhian

http://sapbasis.wordpress.com

[Former Member]

Oracle Data Guard is a good solution for DR sites,

Step by Step process - I cannot provide you, But you can search the Data Guard implementaion on web.

The process of Data Guard set-up works as below:

You have to configure/enable some of the parameters (fal_client, val_server, secondary archive destination on primary),

Then Datagurad will ship the archivelogs from the secondary destination of primary server to your DR site,

And applies the archivelogs on DR,

After that you can delete the shipped and applied archivelogs on secondary destination on primary and DR site by creating scritps and scheduling them.

And Data Guard can be monitored with Agent/Broker or Manually.

Regards,

Nick Loy