This chapter includes the following sections:
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, create a database user in the database with same default schema as dbo using the following:
use <monitor_11g_database_name> CREATE LOGIN dbo WITH PASSWORD = <password_of_your_choice>'; create USER <username_of_your_choice> FOR LOGIN dbo WITH DEFAULT_ SCHEMA = dbo; grant select to <username_of_your_choice>
This user is used only in the readiness check wizard and not in the upgrade schema wizard. In the Monitor 11g upgrade schema wizard, use the DBA user only.
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. |
Schemas |
Ensure Schemas is selects and click Next. |
Available Components |
|
OGGMON Schema (SQLSERVER) |
|
OGGMON Schema Prefix |
|
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 SQL Server databases is a two-stage process:
Oracle GoldenGate Monitor 12c (12.2.1.3.0) supports SQL Server versions 2008 and 2012. See "Install the Database Software" in Installing and Configuring Oracle GoldenGate Monitor.
Since Oracle GoldenGate Monitor Server is released with WebLogic Server 12c (12.2.1) with JRF and to comply with Fusion Middleware standards and requirements, you must upgrade the existing Oracle GoldenGate Monitor by adding STB schemas to the SQL Server database.
Before you begin, do the following:
set:
ISOLATION LEVEL, ALTER DATABASE $(DATABASE_NAME) SET READ_COMMITTED_SNAPSHOT ON
Ensure the database is case-sensitive:
DECLARE @collate sysname select @collate = convert(sysname, serverproperty('Collation')) IF ( charindex(N'_CI', @collate) > 0 ) BEGIN select @collate = replace(@collate, N'_CI', N'_CS') exec ('ALTER database $(DATABASE_NAME) COLLATE ' + @collate) END
To add these dependent schemas, use RCU, which is included in the product installation. To launch RCU, navigate to ORACLE_HOME
/oracle_common/bin
and enter:
$ ./rcu
RCU opens, displaying the Welcome screen.
Navigate the RCU screens as instructed in the following table to update the database. If you want further information on any screen, click its name in the left-hand column.
Screen | Upgrade Action |
---|---|
Welcome |
Click Next. |
Create Repository |
|
Database Connection Details |
|
Select Components |
|
Schema Passwords |
|
Summary |
Review the schema information and click Create. |
Creation Summary |
Click Close. |
With the repository created, next run the Upgrade Assistant to upgrade the database to version 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.
Navigate the UA screens as instructed in the following table to upgrade your server. If you want further information on any screen, click its name in the left-hand column.
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. |
This completes the Oracle GoldenGate Monitor Server for SQL Server databases upgrade process.
Next, you must create a new domain with an 11g upgrade and with a 12c upgrade you 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:
$ ./config.sh
For Windows:
C:\ config.bat
The Configuration Wizard starts and the Configuration Type screen appears.
To create the domain, navigate the Configuration Wizard screens providing the necessary information as described on the following table and providing the details from your previous domain (Tomcat for 11g and WebLogic domain for 12c):
Screen | Configuration Action |
---|---|
Create Domain |
Ensure Create a new domain is selected then:
|
Templates |
|
Administrative Account |
|
Domain Mode and JDK |
|
Database Configuration Type |
|
JDBC Component Schema |
Verify the schema information and click Next. |
JDBC Component Schema Test |
Verify the schema information and click Next. |
Credentials |
|
Advanced Configuration |
|
Administration Server |
By default, the server name is AdminServer and the port is 7001, although you can always change default values. For example, you can change the server name AdminServer to OGGMONAdminServer. If port 7001 is already in use, replace it with an unused port number. Make selections as necessary and click Next. |
Managed Servers |
The managed server name is already populated with the default, MONITORSERVER_server1, and the port number with 7003. You can change these values, if desired. Also, if port 7003 is already in use, replace it with an unused port number. Either accept the defaults of update the data and click Next. |
Clusters |
Click Next. |
Coherence Cluster |
Click Next. |
Machines |
Click Next. |
Configuration Summary |
Review the configuration details and click Create. |
Configuration Progress |
When configuration creation is complete, click Next. |
Configuration Success |
|
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.