Refreshing a virtual EBS instance
This topic describes the process of refreshing a virtual Oracle E-Business Suite (EBS) instance.
Changes applied to EBS and picked up only in some dSource snapshots may make certain combinations of snapshots across the appsTier and dbTier incompatible. When provisioning, refreshing, or rewinding a virtual EBS instance, be sure the points in time you choose for each dataset are compatible with each other.
Be careful! Services running on the appsTier depend on the availability of services on the dbTier. The steps below are explicitly ordered with these dependencies in mind. Executing steps out of order may lead to errors in accessing the virtual EBS instance.
Procedure
Login to the Delphix Management application.
Click Manage.
Select Datasets
Select the appsTier vFiles for your EBS instance.
Click the Stop icon to shut down the appsTier services.
Select the VDB utilized by your EBS instance.
Click the Stop icon to shut down the database.
Select the dbTechStack vFiles hosting your virtual EBS database.
Click the Stop icon to shut down the database listener.
Warning: If you did NOT specify the Cleanup Before Provision option for either your virtual dbTechStack or appsTier, you must manually clean up your target environments prior to refreshing. If you have specified this option for both datasets, no manual work is required.
To manually clean up a target environment prior to refresh, remove instance-specific directories and or inventory entries that will conflict with files and entries recreated during the refresh. Without this clean-up, post-clone configuration performed during a refresh will fail with an error claiming that a conflicting EBS instance is already installed.
Refresh the dbTechStack vFiles.
On the vFiles, click the Refresh.
Select a snapshot from which to refresh.
Refresh the EBS VDB.
On the VDB, click the Refresh.
Select a snapshot from which to refresh.
Refresh the appsTier vFiles.
On the vFiles, click the Refresh.
Select a snapshot from which to refresh.
Once you have refreshed all three EBS virtual datasets successfully, your virtual EBS instance should be running and accessible.