DR Server Move Question

Question

We built a Production server and a DR server, testing everything works fine, Now it is time to move the DR server to another State.
Looks like we will have two choices:
1. IN PROD: Change  LOG_ARCHIVE_DEST_STATE_2=ENABLE  to DEFER
Shutdown DR and wait 5 days to ship to new location and turn on DR
Change PROD: LOG_ARCHIVE_DEST_STATE_2=ENABLE  
this will force all archive logs get picked up.
2. IN PROD: Change  LOG_ARCHIVE_DEST_STATE_2=ENABLE  to DEFER
ShutDown PROD, start up mount
  SQL> alter database noarchivelog;
This will stop create any new archive log files
After DR shipped to new location, we will need to re-build DR first.
More process/procedures need to run.
===========================================================
The Advantage/Disadvantage of Choice #1:
1. Doesn't require any PROD down time, Process is simple and strighforward
2. But the performance when turn on DR maybe unpredictable, if archive log files accumulated too much.
  WE have been monitoring: it is about 2GB, 200 archive log files  every day
   Estimate: 10 GB, 1000 files for about 5 days.
===========================================================
Can anyone experience DR move in your project, any suggestion ?

Answer 1

Step 1. Start up DR
alter database recover managed standby database disconnect from session;
Step 2. Go to Prod Database
alter system set log_archive_dest_state_2=ENABLE scope=spfile;
This will start all log shipping, and pick up from the date when DR get shutdown. Right?
YES...
You can check the status MRP apply on Standby as below;
select process, client_process, thread#, sequence#, status from v$managed_standby;
You can run same statement on Primary to see on how archive log shipping is happening.
>>About "Roll forward using RMAN", Do I still need that?
>> What do you still need ?
If you are enabling Data Guard then you don't need this. It is required only when you dont' want to move archvielogs.
HTH
Pradeep