3 Performing the Oracle GoldenGate Studio Upgrade
The Oracle GoldenGate Studio upgrade from a previous 12c release to 12c (12.2.1.4.0) is performed in-place; that is, the upgrade operations are performed on the existing 12c domain.
High-level upgrade steps:
- About the Oracle GoldenGate Studio Upgrade Process
Review the flowchart and roadmap for an overview of the upgrade process for Oracle GoldenGate Studio . - Installing Oracle GoldenGate Studio
Before you begin your upgrade, download the Oracle GoldenGate Studio 12c (12.2.1.4.0) distribution on the target system and install it by using Oracle Universal Installer. - Upgrading Product Schemas
After stopping servers and processes, use the Upgrade Assistant to upgrade supported product schemas to the current release of Oracle Fusion Middleware.
About the Oracle GoldenGate Studio Upgrade Process
Review the flowchart and roadmap for an overview of the upgrade process for Oracle GoldenGate Studio .
The steps you take to upgrade your existing domain varies depending on how your domain is configured and which components are being upgraded. Follow only those steps that are applicable to your deployment.
Figure 3-1 Upgrade Process Flowchart for Oracle GoldenGate Studio

Description of "Figure 3-1 Upgrade Process Flowchart for Oracle GoldenGate Studio"
Table 3-1 Tasks for Upgrading Oracle GoldenGate Studio
Task | Description |
---|---|
Required If you have not done so already, review the introductory topics in this guide and complete the required pre-upgrade tasks. |
The pre-upgrade tasks include cloning your production environment, verifying system requirements and certifications, purging unused data, and creating a non-SYSDBA user. For a complete list of pre-upgrade tasks, see Preparing to Upgrade Oracle GoldenGate Studio. |
Required Shut down the connection to the existing 12c repository. |
Before you start the upgrade process, shut down the connection to the 12c (12.2.1.4.0) repository. |
Required Download and install the Oracle GoldenGate Studio 12c (12.2.1.4.0) distribution in the new Oracle home. |
To install the product distribution, see Installing Oracle GoldenGate Studio. |
Required Upgrade the existing schemas with the Upgrade Assistant. |
The schemas that you created during the 12c (12.2.1.x) installation are supported in 12c (12.2.1.4.0). Therefore, you do not need to create the schemas again. You must upgrade all the repository schemas by using the Upgrade Assistant. See Using the Oracle Fusion Middleware Upgrade Assistant to Upgrade Product Schemas. |
Required Connect to the 12c (12.2.1.4.0) repository and verify your upgrade. |
The upgrade process is complete. You can now verify the 12c (12.2.1.4.0) instance to compare the previous 12c environment with the 12c (12.2.1.4.0) and verify that the data and configuration settings are consistent in the newly upgraded environment. |
Parent topic: Performing the Oracle GoldenGate Studio Upgrade
Installing Oracle GoldenGate Studio
Before you begin your upgrade, download the Oracle GoldenGate Studio 12c (12.2.1.4.0) distribution on the target system and install it by using Oracle Universal Installer.
Parent topic: Performing the Oracle GoldenGate Studio Upgrade
Upgrading Product Schemas
After stopping servers and processes, use the Upgrade Assistant to upgrade supported product schemas to the current release of Oracle Fusion Middleware.
The Upgrade Assistant allows you to upgrade individually selected schemas or all schemas associated with a domain. The option you select determines which Upgrade Assistant screens you will use.
- Starting the Upgrade Assistant
Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to 12c (12.2.1.4.0). Oracle recommends that you run the Upgrade Assistant as a non-SYSDBA user, completing the upgrade for one domain at a time. - Upgrading the Schemas with the Upgrade Assistant
Navigate through the screens in the Upgrade Assistant to upgrade the product schemas. - Verifying the Schema Upgrade
After completing all the upgrade steps, verify that the upgrade was successful by checking that the schema version inschema_version_registry
has been properly updated.
Parent topic: Performing the Oracle GoldenGate Studio Upgrade
Starting the Upgrade Assistant
Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to 12c (12.2.1.4.0). Oracle recommends that you run the Upgrade Assistant as a non-SYSDBA user, completing the upgrade for one domain at a time.
Note:
Before you start the Upgrade Assistant, make sure that the JVM character encoding is set to UTF-8 for the platform on which the Upgrade Assistant is running. If the character encoding is not set to UTF-8, then you will not be able to download files containing Unicode characters in their names. This can cause the upgrade to fail.
- Go to the
oracle_common/upgrade/bin
directory:- (UNIX)
NEW_ORACLE_HOME/oracle_common/upgrade/bin
- (Windows)
NEW_ORACLE_HOME\oracle_common\upgrade\bin
- (UNIX)
- Start the Upgrade Assistant:
- (UNIX) ./ua
- (Windows) ua.bat
For information about other parameters that you can specify on the command line, such as logging parameters, see:
Parent topic: Upgrading Product Schemas
Upgrade Assistant Parameters
When you start the Upgrade Assistant from the command line, you can specify additional parameters.
Table 3-2 Upgrade Assistant Command-Line Parameters
Parameter | Required or Optional | Description |
---|---|---|
|
Required for readiness checks
Note: Readiness checks cannot be performed on standalone installations (those not managed by the WebLogic Server). |
Performs the upgrade readiness check without performing an actual upgrade. Schemas and configurations are checked. Do not use this parameter if you have specified the |
|
Optional |
Identifies the number of threads available for concurrent schema upgrades or readiness checks of the schemas. The value must be a positive integer in the range 1 to 8. The default is 4. |
|
Required for silent upgrades or silent readiness checks |
Runs the Upgrade Assistant using inputs saved to a response file generated from the data that is entered when the Upgrade Assistant is run in GUI mode. Using this parameter runs the Upgrade Assistant in silent mode (without displaying Upgrade Assistant screens). |
|
Optional |
Performs the examine phase but does not perform an actual upgrade. Do not specify this parameter if you have specified the |
|
Optional |
Sets the logging level, specifying one of the following attributes:
The default logging level is Consider setting the |
|
Optional |
Sets the default location of upgrade log files and temporary files. You must specify an existing, writable directory where the Upgrade Assistant creates log files and temporary files. The default locations are: (UNIX)
(Windows)
|
|
Optional |
Displays all of the command-line options. |
Parent topic: Starting the Upgrade Assistant
Upgrading the Schemas with the Upgrade Assistant
Navigate through the screens in the Upgrade Assistant to upgrade the product schemas.
Note:
Make sure that the administration and managed servers are stopped before you launch the Upgrade Assistant.Parent topic: Upgrading Product Schemas
Verifying the Schema Upgrade
After completing all the upgrade steps, verify that the upgrade was successful by checking that the schema version in schema_version_registry
has been properly updated.
If you are using an Oracle database, connect to the database as a user having Oracle DBA privileges, and run the following from SQL*Plus to get the current version numbers:
SET LINE 120 COLUMN MRC_NAME FORMAT A14 COLUMN COMP_ID FORMAT A20 COLUMN VERSION FORMAT A12 COLUMN STATUS FORMAT A9 COLUMN UPGRADED FORMAT A8 SELECT MRC_NAME, COMP_ID, OWNER, VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY ORDER BY MRC_NAME, COMP_ID ;
In the query result:
-
Check that the number in the
VERSION
column matches the latest version number for that schema. For example, verify that the schema version number is 12.2.1.4.0.Note:
However, that not all schema versions will be updated. Some schemas do not require an upgrade to this release and will retain their pre-upgrade version number.
-
The
STATUS
field will be eitherUPGRADING
orUPGRADED
during the schema patching operation, and will becomeVALID
when the operation is completed. -
If the status appears as
INVALID
, the schema update failed. You should examine the logs files to determine the reason for the failure. -
Synonym objects owned by
IAU_APPEND
andIAU_VIEWER
will appear asINVALID
, but that does not indicate a failure.They become invalid because the target object changes after the creation of the synonym. The synonyms objects will become valid when they are accessed. You can safely ignore these
INVALID
objects.
Parent topic: Upgrading Product Schemas