Run the Upgrade Assistant to upgrade all the schemas in the 12.2.1.0.0 domain to 12.2.1.1.0.
- Run the Upgrade Assistant from the 12.2.1.1 Oracle home by entering the following command:
On UNIX operating system:
$Oracle_Home/oracle_common/upgrade/bin/ua
On Windows operating system:
%Oracle_Home%\oracle_common\upgrade\bin\ua.bat
- The Welcome screen provides an overview of the Upgrade Assistant and some information about important pre-upgrade tasks. Click Next.
For more information about using the Upgrade Assistant, click Help on the Upgrade Assistant screen.
- On the Selected Schemas screen, select Individually Selected Schemas. This option allows you to select only those schemas that you want to include in the upgrade. Click Next.
- On the Available Components screen, select Oracle GoldenGate Studio and click Next.
- On the Prerequisites screen, acknowledge that the prerequisites have been met by checking all the check boxes. Click Next.
Note:
The Upgrade Assistant does not verify whether the prerequisites have been met.
- On the OGGSTUDIO Schema screen, specify the connection credentials in which you will be creating or dropping schemas.
Specify the service name and the database administrator account: DBA username and password for the database containing the OGGSTUDIO schema and click
Connect.
Note:
Do not use SYSDBA as the database user name.
- Specify the schema user name and the password for the selected schema.
When you see the message “Connection to database successfully completed”, click Next.
- On the Studio Options screen, select Upgrade topology and security metadata and Use AES-128 encryption algorithm. Click Next.
Note:
If you do not select Use AES-128 encryption algorithm, AES-256 will be used as the encryption algorithm will be used for the upgrade.
- On the OGG Studio Supervisor screen, specify the supervisor credentials for the OGG repository you want to upgrade and click Next.
- The Examine screen displays the status of the Upgrade Assistant as it examines each component, verifying that the component is ready for upgrade. If the status is “ready for upgrade.”, click Upgrade.
If the repository version is same as that of the current repository, the status will be ‘upgrade not required’.
- On the Upgrade Summary screen, review the summary of the options you have selected by expanding the tree.
Review the Source Version and the Target Version to make sure that both the versions are correct before proceeding with the upgrade.
The response file collects and stores all the information that you have entered through the Upgrade Assistant's graphical user interface , and enables you to perform a silent upgrade at a later time. The silent upgrade performs exactly the same function that the Upgrade Assistant wizard performs, but you do not have to manually enter the data again. If you want to save these options to a response file, click Save and provide the location and name of the response file.
Click Upgrade to start the upgrade process.
- The Upgrade Progress screen shows the status of the upgrade process and the projected Target Version of the component after a successful upgrade. Click Next.
Caution:
Allow the Upgrade Assistant enough time to perform the upgrade. Do not cancel the upgrade operation unless absolutely necessary. Doing so may result in an unstable environment.
If any components are not upgraded successfully, refer to the Upgrade Assistant log files for more information.
- If the upgrade is successful, you see the Upgrade Success screen. Click Close to complete the upgrade and close the wizard.
The Post-Upgrade Actions window describes the manual tasks you must perform to make the component functional in the new installation. This is an optional window that only appears if a component has post-upgrade steps.
- If the upgrade has failed, you see the Upgrade Failure screen. This indicates that the upgrade of one or more components has failed. The components cannot be upgraded this time.
Click View Log to view and troubleshoot the errors.
Fix the issues in the pre-upgrade environment before starting the Upgrade Assistant again. Restore your pre-upgrade environment from backup (making sure to keep the original backup files in a separate location), fix the issues, and restart the Upgrade Assistant.