This appendix describes how to manage Oracle Inventory on the production and standby sites for an Oracle Fusion Middleware Disaster Recovery topology.
It includes the following sections:
When you update Oracle Inventory (for example, by installing new Oracle software, or by applying an Oracle patch set or patch to existing Oracle software) on a production site host, you must ensure that the same software updates are made on the standby site peer host.To do this, you must update Oracle inventory on the standby site peer host by executing the following script:
ORACLE_HOME/oui/bin/attachHome.sh
In addition, you must update the beahomelist file to edit the location of the Middleware home. Edit the following file to update the Middleware home information:
user_home/bea/beahomelist
(Windows) C:\bea\beahomelist
When you update Oracle inventory (for example, by installing new Oracle software or by applying an Oracle patch set or a patch to existing Oracle software) on a production site Windows host, you must ensure that the same software updates are made on the standby site peer host by exporting the following Windows Registry key on the production site host and importing it on the standby site peer host:
HKEY_LOCAL_MACHINE\Software\oracle
In addition, when you modify system components, such as Oracle Web Cache, you must export the following Windows Registry key on the production site host and import it on the standby site peer host:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services
To import a key that you have previously exported, use the following command:
regedit /I FileName
For example:
regedit /I C:\oracleregistry.reg
You can also use the Registry Editor to import the key. See the Registry Editor Help for more information.