This chapter includes the following sections:
Note:
This upgrade supports only the latest version of Oracle 11g R3 and Oracle 12c R1 database software releases. For current database support information for Oracle GoldenGate Monitor 12c (12.2.1), see "Platform Support" in Installing and Configuring Oracle GoldenGate Monitor.
This section is only applicable to 11g upgrades. It is not applicable to 12c upgrades because the required schema already exists.
Note:
Before running RCU for Oracle 12c databases, ensure the following:
The character set is AL32UTF8. You must do this because the default character set is not supported by RCU.
You are using a plug-able database. By default, a container database will enable in Oracle 12c, so RCU supports only plug-able database, not container database.
To create the 12.2.1 database schema, run the Repository Creation Utility, which is part of the product installation. To launch RCU, navigate to ORACLE_HOME/oracle_common/bin
and enter:
For Linux or UNIX:
$ ./rcu
For Windows:
C:\ rcu.bat
RCU will open, displaying the Welcome screen.
Navigate the RCU screens as instructed in the following table to update the database.
Note:
Some of the RCU items that this procedure instructs you to select might already be selected by default. If an item on a screen is already selected and the instructions below tell you to select it, be careful not to deselect it.
Screen | Upgrade Action |
---|---|
Welcome |
Click Next. |
Create Repository |
|
Database Connection Details |
|
Select Components |
|
Schema Passwords |
|
Map Tablespaces |
Click Next. Schema creation for the selected services will commence. |
Summary |
Review the schema information and click Create. |
Creation Summary |
Click Close. |
Before beginning an upgrade, you must use the UA to perform an upgrade readiness check. The UA runs a read-only check on various database contents including the schema version, required tables, and columns. If the schema version is already at the upgraded or latest version of Oracle GoldenGate Monitor or there are unexpected or missing tables or columns found, the readiness test will fail. If a failure occurs, the UA provides the test details and any exceptions in the UA logs, and the readiness test results are provided in the ORACLE_HOME
/oracle_common/upgrade/logs/postreadiness.txt
file. Like RCU, UA is included in the product installation.
Use one of the following sections to perform your readiness check:
On your existing 11g Oracle GoldenGate Monitor server, navigate to ORACLE_HOME
/oracle_common/upgrade/bin
and enter:
For Linux or UNIX:
$ ./ua -readiness
For Windows:
C:\ ua.bat -readiness
Navigate the UA screens as instructed in the following table to upgrade your server.
Screen | Upgrade Action |
---|---|
Welcome |
Click Next. |
Schemas |
Ensure Schemas is selects and click Next. |
Available Components |
|
OGGMON Schema |
|
Readiness Summary |
Click Next. |
Readiness Check |
Click Continue. You can use the View Readiness Report button to view your results. |
Readiness Success |
Click Close. |
On your existing Oracle GoldenGate Monitor server, navigate to ORACLE_HOME
/oracle_common/upgrade/bin
and enter:
For Linux or UNIX:
$ ./ua -readiness
For Windows:
C:\ ua.bat -readiness
Navigate the UA screens as instructed in the following table to upgrade your server.
Screen | Upgrade Action |
---|---|
Welcome |
Click Next. |
WebLogic Components |
Ensure WebLogic Component Configurations - offline checks only is selected and click Next. |
Component List |
Click Next. |
Readiness Summary |
Click Next. |
Readiness Check |
Click Continue. You can use the View Readiness Report button to view your results. |
Readiness Success |
Click Close. |
On your existing Oracle GoldenGate Monitor server, navigate to WEBLOGIC_HOME
/oracle_common/upgrade/bin
and enter:
Note:
Ensure that you go to your Oracle WebLogic home directory not your Oracle home directory.
For Linux or UNIX:
$ ./ua -readiness
For Windows:
C:\ ua.bat -readiness
Navigate the UA screens as instructed in the following table to upgrade your server.
Screen | Upgrade Action |
---|---|
Welcome |
Click Next. |
WebLogic Components |
Ensure WebLogic Component Configurations - offline checks only is selected and click Next. |
Component List |
Click Next. |
Readiness Summary |
Click Next. |
Readiness Check |
Click Continue. You can use the View Readiness Report button to view your results. |
Readiness Success |
Click Close. |
Upgrading Oracle GoldenGate Monitor Server for Oracle databases is a two-stage process:
Note:
Ensure that the existing Monitor server is stopped before you proceeding with the following steps.
Note:
Ensure that the existing Oracle GoldenGate Monitor Server 11g pointed to the schema you are going to upgrade is stopped before commencing with this procedure.
With the repository created, you next run UA to upgrade the database to version 12c (12.2.1). Navigate to ORACLE_HOME
/oracle_common/upgrade/bin
and enter:
For Linux or UNIX:
$ ./ua
For Windows:
C:\ ua.bat
The UA Welcome screen appears.
Use one of the following sections to perform your schema upgrade:
Upgrading the Server
Navigate the UA screens as instructed in the following table to upgrade your server.
Screen | Upgrade Action |
---|---|
Welcome |
Click Next. |
Schemas |
Ensure Schemas is selects and click Next. |
Available Components |
|
Prerequisites |
|
OGGMON Schema |
|
OGGMON Schema Prefix |
|
Examine |
Click Next. |
Upgrade Summary |
Click Upgrade. |
Upgrade Progress |
Click Next. |
Upgrade Success |
Click Close. |
The /ua_timestamp.log,ua_timestamp.out
files are generated at $oracle_common/upgrade/
logs
under the 12g ORACLE_HOME
.
Upgrading the Oracle GoldenGate Monitor Server Configuration
The UA updates the Monitor Server configuration files to the latest 12.2.1 configuration by maintaining your existing set property values. It creates a oggmon.properties
file in the domain_name
/config/monitorserver/cfg/
directory, with an encrypted password entry that is used in JMX communication between Monitor Server and Agent.
Navigate to ORACLE_HOME
/oracle_common/upgrade/bin
and enter:
For Linux or UNIX:
$ ./ua
For Windows:
C:\ ua.bat
Navigate the UA screens as instructed in the following table to upgrade your server.
The UA Welcome screen appears.
Screen | Upgrade Action |
---|---|
Welcome |
Click Next. |
Schemas |
Ensure Schemas is selects and click Next. |
WebLogic Components |
|
Component List |
Click Next. |
Prerequisites |
|
OGGMON Schema |
|
OGG Monitor Installed Version |
|
Examine |
Click Next. |
Upgrade Summary |
Click Upgrade. |
Upgrade Progress |
Click Next. |
Upgrade Success |
Click Close. |
This completes the Oracle GoldenGate Monitor Server for Oracle database upgrade process.
Use this section to upgrade your 12.1.3 schema, WebLogic domain, and Oracle GoldenGate Monitor Server.
Upgrading the Server
Navigate the UA screens as instructed in the following table to upgrade your server.
Screen | Upgrade Action |
---|---|
Welcome |
Click Next. |
Schemas |
Ensure Schemas is selects and click Next. |
Available Components |
|
Domain Directory |
Enter the directory for the domain you are upgrading or browse for it, then click Next. |
Prerequisites |
|
IAU Schema |
|
OPSS Schema |
|
OGGMON Schema |
|
Examine |
Click Next. |
Upgrade Summary |
Click Upgrade. |
Upgrade Progress |
Click Next. |
Upgrade Success |
Click Close. |
The /ua_timestamp.log,ua_timestamp.out
files are generated at $oracle_common/upgrade/
logs
under the 12g ORACLE_HOME
.
Upgrading the WebLogic Domain
Next, you must update the existing 12.1.3 WebLogic domain configuration to a 12.2.1 domain. Navigate to ORACLE_HOME
/wlserver/common/bin
and enter:
For Linux or UNIX:
$ ./reconfig.sh
For Windows:
C:\ reconfig.bat
The Fusion Middleware Reconfiguration Wizard opens, displaying the Select Domain screen.
Navigate the wizard screens as instructed in the following table to upgrade your domain.
Screen | Upgrade Action |
---|---|
Select Domain |
Enter the directory for the domain you are upgrading or browse for it, then click Next. |
Setup Progress |
Click Next. |
Domain Mode and JDK |
Enter your JDK directory or browse for it, then click Next. |
Database Configuration Type |
|
Component Datasources |
Click Next. |
JDBC Test |
|
Advanced Configuration |
Do not select anything. Click Next. |
Configuration Summary |
Click Reconfig. |
Reconfiguration Progress |
Click Next. |
Reconfiguration Success |
Click Finish. |
Upgrading the Oracle GoldenGate Monitor Server Configuration
The UA updates the Monitor Server configuration files to the latest 12.2.1 configuration by maintaining your existing set property values. It creates a oggmon.properties
file in the domain_name
/config/monitorserver/cfg/
directory, with an encrypted password entry that is used in JMX communication between Monitor Server and Agent.
Navigate to ORACLE_HOME
/oracle_common/upgrade/bin
and enter:
For Linux or UNIX:
$ ./ua
For Windows:
C:\ ua.bat
Navigate the UA screens as instructed in the following table to upgrade your server.
The UA Welcome screen appears.
Screen | Upgrade Action |
---|---|
Welcome |
Click Next. |
Schemas |
Ensure Schemas is selects and click Next. |
WebLogic Components |
|
Component List |
Click Next. |
Prerequisites |
|
OGG Monitor Installed Version |
|
OGGMON Schema |
|
Examine |
Click Next. |
Upgrade Summary |
Click Upgrade. |
Upgrade Progress |
Click Next. |
Upgrade Success |
Click Close. |
This completes the Oracle GoldenGate Monitor Server for Oracle database and domain upgrade process.
With the upgrade process complete for your database type, you next need to perform certain post-upgrade tasks, which are described in Performing Post-Upgrade Tasks.
After applying the Oracle GoldenGate Monitor patch 12.2.1.2.171115 (PS2 BP3), optionally, you can execute a table re-partition script to optimize the history purging feature. After the script execution is completed, it reduces the time needed to purge historical data by using the Oracle GoldenGate Monitor server user interface. However, significant amount of time may be needed for script execution depending of amount of existing data.
SYSDBA
user and enter the Oracle GoldenGate Monitor Repository User Name when asked for parameter 1 – <ORACLE_HOME>/oggmon/plugins/upgrade/scripts/grant_permission_oracle.sql
.<ORACLE_HOME>/oggmon/plugins/upgrade/scripts/oracle_partitions.sql
.