Need help evaluating the stability/correctness of standby E-Business Suite

Question

Hello Experts,
In September 2011, we moved 52 datafiles from one disk /u01 to another disk /u03 for performance reasons in our primary EBS environment using http://docs.oracle.com/cd/E11882_01/server.112/e25608/manage_ps.htm#i1034172. We only realized last week that we never replicated this on the standby, so we proceeded to move the 52 datafiles from /u01 to /u03 on the standby EBS environment. We are now concerned about whether or not the standby environment is stable and matches the primary exactly.
We checked the standby alert log and did not find any ORA-00283, ORA-01157 or ORA-01110 errors, and v$archived_log shows that the standby database is in sync with the primary.
Is it possible that the standby operated correctly during the past six months when filesystem path names to datafiles as well as datafile names in v$datafiles were different from the primary, and can we now continue as is after making the corresponding changes six months after updating the primary?
I appreciate any help.
EBS Version: R12.1.3
DB Version: 11.2.0.1
OS Version: RHEL 5.7
Configuration: 2-node dataguard --> db/concurrent processing on one server; web/forms on separate server; two other servers host the standby application and database tiers
Thanks,
Ss

Answer 1

I'm watching Your thread.
Simple Logic,
You perform any operations on primary those will be update as is in standby.
In Many environments, Primary & Standby data files are in Different locations.
Lets suppose, You have primary as /u01/prim/oradata/datafiles
you have standby as /u04/stby/oradata/datafiles
If you add any data file on primary, The new datafile added on standby only when you set standby_file_management to AUTO , based on db_file_name_convert parameters too.
Of course you can change the data file locations in primary But those changes are not going to perform on standby. Even in my environment Data file locations are completely differnet, Believe it Primary is on ASM and standby is on non-ASM its normal file system.
Again if you query v$datafile it points to each data file location. Even you can see trace file of controlfile.
We checked the standby alert log and did not find any ORA-00283, ORA-01157 or ORA-01110 errors, and v$archived_log shows that the standby database is in sync with the primary.These errors you can find in case what above i mentioned link,
here if you see your standby is working fine, Archive are in sync.
But here is procedure to achieve that task.
1) Stop MRP
SQL> alter database recover managed standby database cancel;
2) Rename/Move data files from */u01* to */u03*
Check all the datafiles are online.
3) Change value of DB_FILE_NAME_CONVERT in standby
Its a static value, You have to bounce standby instance Change it to new location where datafiles exist.
Ex:
DB_FILE_NAME_CONVERT='/u03/prod/datafiles/...','Standby location';
4) Then put in mount status and start MRP again
SQL> alter database recover managed standby database disconnect from session;
Hope this clears.
Sorry
I read your question Again And Again..
dont worry of your standby datafile locations. its nothing to do.
Even if you change in primary there is no rule that should changed on standby
So Please ignore, Your standby is functioning well.
Also i seen that your standby time is ahead. can you please confirm?
Edited by: CKPT on Mar 23, 2012 5:45 PM