Database Software

All,

I have 3 node RAC primary database and 3 node RAC standby database.
Oracle version is 10.2.0.4.0 running on Sun Solaris.
We are using standby log shipping through LGWR, auto mode and database is in maximum performance mode.

We are planning to run critical batch process which is heavily resource consumption oriented like CPU and Memory consumption. It will run for 10 hours with set of Stored procedures.

In order to provide resource to this batch process, front end applications will be shutdown (completely down time to users).

Question 1_

There is a recommendation to stop log shipping to standby database during the batch process. Once the batch process is over, enable it to standby.

I am new to this standby environment. I have gone through documentation and I have identified the below steps to achieve the above task.

1) Before batch process, run the following command in primary - alter system set log_archive_dest_state_2=defer scope=both sid="*"; This command will temporarily stop log shipping to standby database.
2) Run the batch job for 10 hours. Based on the available FRA size are log generation rate, we have enough space to withstand logs for 3 days.
3)Once batch is successfully completed, i will execute the below command in primary - alter system set log_archive_dest_state_2=enable scope=both sid="*";

After the step 3, I assume all the backlogs of logs pending at primary will be transferred automatically to standby database and applied.

Is my above assumption correct and did i missed any important steps.

Question 2_

Before batch process, we are going to take full hot backup using RMAN.
If anything goes wrong with batch process, we are planning to restore and reset logs. here no recovery is required. Is this approach fine. any other best solution.

My questions may be very basic, since I don't have data guard set up in standby, I am not able to test it. i need your help in reviewing above steps and suggestions / corrections.