Hello Thanks for the post.
Please find below the details -
For Log - It should be - $NE_BASE/inst/<CONTEXT_NAME>/logs/appl/conc/out - Its centralized location no need to sync.
- FS_NE - Again centralized.
- ORACLE_HOME, FMW_HOME - It will be sync after fs_clone, including .env files.
I hope this answer your queries.
I would rsync everything under BASE_TOP. After the first synch, it will only synch changed files and will be very fast.
Thanks for the reply. But if we sync up from the base then Inst_top and FMW_top also will get synced up which is instance specific , moreover we will have different ports for oacore from the primary and it may end up in corrupting the DR Applications?. Please provide your inputs.
There are two ways to consider sync of filesystem from primary to standby node.
1) Enabled full filesystem sync from Primary to Standby Application Tier
2) Whenever you perform a DR switch, rename standby Application Servers hostname to primary application hosts.
3) Also, perform changes in DNS as well
1) Enabled sync of Run Filesystem and FS_NE
2) Whenever you perform a DR switch run adcfgclone.pll on AppsTier to reconfigure Apps.
3) Perform any post configuration steps like WF Configuration, Update paths,etc.,
Method 2 is little complex as this need thorough testing specifically for post steps. Method 1 doesn't is much simpler and faster to bring up Apps incase of any disaster.
For more details on how to setup standby appication, follow the below MOS ID
Business Continuity for Oracle E-Business Suite Release 12.2 Using Oracle 12c (18.104.22.168) Physical Standby Database (Doc ID 1963472.1)