2 Upgrading Oracle GoldenGate Monitor Server

This chapter describes the tasks you perform to upgrade Oracle GoldenGate Monitor.

This chapter includes the following sections:

Section 2.1, "Upgrading from Version 11g on Tomcat"
Section 2.2, "Schema Upgrade Instructions for Oracle Database Users"
Section 2.3, "Schema Upgrade Instructions for MySQL Database Users"
Section 2.4, "Schema Upgrade Instructions for SQL Server Database Users"

2.1 Upgrading from Version 11g on Tomcat

If you are upgrading from Oracle GoldenGate Monitor 11g on Tomcat, before commencing with the process, make sure that you have stopped all Oracle GoldenGate Monitor components, including the Oracle GoldenGate Monitor Server, Oracle GoldenGate Manager, and JAgent.

2.2 Schema Upgrade Instructions for Oracle Database Users

Upgrading Oracle GoldenGate Monitor Server for Oracle databases is a two-stage process:

Create Required 12.1.3 Schema by Using RCU
Upgrade the Schema by Running UA

Note:

Enure that the existing Monitor 11g server is stopped before you proceeding with the following steps.

2.2.1 Create Required 12.1.3 Schema by Using RCU

Note:

This upgrade supports only latest version of Oracle 11g R1, Oracle 11g R3 and Oracle 12c R1 database software releases. For current database support information for Oracle GoldenGate Monitor 12c (12.1.3), see "Platform Support" in Installing and Configuring Oracle GoldenGate Monitor Server.

Important:

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 Oracle12c, so RCU supports only plug-able database, not container database.

To update the database:

To update the database, run the Repository Creation Utility, which is part of the product installation. To launch RCU, navigate to ORACLE_HOME/oracle_common/bin and enter:

$./rcu

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 de-select it.

Screen	Upgrade Action
Welcome	Click Next.
Create Repository	Select System Load and Product Load. Click Next.
Database Connection Details	Enter the Oracle GoldenGate Monitor database details. Click Next.
Select Components	Under the AS Common Services node, select the following schemata: Audit Services Audit Services Append Audit Services Viewer Oracle Platform Security Services Note: Do not select the Monitor Server schema in this step. Click Next. A progress window appears, checking off each schema as its prerequisites ar e met. Click OK.
Schema Passwords	Enter the necessary password, if it's not already there, and confirm it. Click Next.
Map Tablespaces	Click Next. Schema creation for the selected services will commence.
Summary	Review the schema information and click Create.
Creation Summary	Click Close.

2.2.2 Upgrade the Schema by Running UA

Warning:

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 the Upgrade Assistant to upgrade the database to version 12c (12.1.3). Like RCU, UA is included in the product installation. Navigate to ORACLE_HOME/oracle_common/upgrade/bin and enter:

$./ua

The UA Welcome screen appears.

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	Select Oracle GoldenGate Monitor. Click Next.
Prerequisites	Select all three prerequisites. Click Next.
OGGMON Schema	Enter the Oracle GoldenGate Monitor schema name and password. Click Next.
OGGMON Schema Prefix	Enter the same schema prefix you used when creating the STB schema in RCU (see To update the database:). Click Next.
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. The /ua_timestamp.log ,ua_timestamp.out files are generated at $oracle_common/upgrade/logs under the 12g ORACLE_HOME.

2.3 Schema Upgrade Instructions for MySQL Database Users

Note:

Oracle GoldenGate Monitor Server 12c (12.1.3) supports only MySQL 5.5 and later. If you are trying to upgrade an earlier version of MySQL, you first must upgrade it to MySQL 5.5 or later. For more information, see "Upgrading or Downgrading MySQL" at:

http://dev.mysql.com/doc/refman/5.5/en/upgrading-downgrading.html

Upgrading Oracle GoldenGate Monitor Server for MySQL databases is a two-stage process:

Upgrade the MySQL Schema by Running RCU
Upgrade the Schema by Running UA

2.3.1 Upgrade the MySQL Schema by Running RCU

Important:

Before you can upgrade Oracle GoldenGate Monitor for a MySQL database, the following values need to be set in the database:

SET GLOBAL INNODB_FILE_PER_TABLE="ON";
SET GLOBAL INNODB_FILE_FORMAT="Barracuda";
SET GLOBAL INNODB_LARGE_PREFIX="ON";
SET GLOBAL LOG_BIN_TRUST_FUNCTION_CREATORS="ON";

If you do not set these values, RCU will throw an error at the end of the session. You cannot cancel the RCU process and it is difficult to reboot the database to set/reflect the RCU during its run.

Since Oracle GoldenGate Monitor Server is released with Weblogic Server 12c (12.1.3) 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 MySQL database.

To add these dependent schemas, use the 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	Select System Load and Product Load. Click Next.
Database Connection Details	Enter the Oracle GoldenGate Monitor database details. Click Next.
Select Components	Service Table should be selected, by default; if not, do so. If other values are selected, deselect them. Click Next. A progress window appears, checking off the schema when its prerequisites ar e met. Click OK.
Schema Passwords	Enter the necessary password, if it's not already there, and confirm it. Click Next.
Summary	Review the schema information and click Create.
Creation Summary	Click Close.

2.3.2 Upgrade the Schema by Running UA

Note:

Ensure that the existing Oracle GoldenGate Monitor Server 11g that is pointed to the schema that you are going to upgrade is stopped before starting this procedure.

This section describes how to use UA to upgrade the MySQL database.

2.3.2.1 Prerequisites

UA expects to see schema names in capital letters, therefore, before running UA, you need to do the following:

If Monitor 11g schema was created in lowercase letters, you need to create new schema using capital letters and then move the existing repository to that newly created Schema.
Ensure the schema name and the username match.

2.3.2.2 Run UA

To run UA, navigate to ORACLE_HOME/oracle_common/upgrade/bin and enter:

$./ua

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	Select Oracle GoldenGate Monitor. Click Next.
Prerequisites	Select all three prerequisites. Click Next.
OGGMON Schema	Ensure that the proper information is supplied. Click Next.
OGGMON Schema Prefix	Enter the same schema prefix you used when creating the STB schema in RCU. Click Next.
Examine	Click Next.
Upgrade Summary	Click Upgrade.
Upgrade Progress	Click Next.
Upgrade Success	Click Close.

This completes the Oracle GoldenGate Monitor Server for MySQL databases upgrade process.

2.4 Schema Upgrade Instructions for SQL Server Database Users

Upgrading Oracle GoldenGate Monitor Server for SQL Server databases is a two-stage process:

Update the SQL Server Database by Running RCU
Upgrade the Database by Running UA

Oracle GoldenGate Monitor 12c (12.1.3) supports SQL Server versions 2008 and 2012. See "Install the Database Software" in Installing and Configuring Oracle GoldenGate Monitor Server.

2.4.1 Update the SQL Server Database by Running RCU

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	Select System Load and Product Load. Click Next.
Database Connection Details	Enter the Oracle GoldenGate Monitor database details. Click Next.
Select Components	Service Table should be selected, by default; if not, do so. If other values are selected, deselect them. Click Next. A progress window appears, checking off the schema when its prerequisites ar e met. Click OK.
Schema Passwords	Enter the necessary password, if it's not already there, and confirm it. Click Next.
Summary	Review the schema information and click Create.
Creation Summary	Click Close.

2.4.2 Upgrade the Database by Running UA

With the repository created, next run the Upgrade Assistant to upgrade the database to version 12c (12.1.3). Like RCU, UA is included in the product installation. Navigate to ORACLE_HOME/oracle_common/upgrade/bin and enter:

$./ua

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	Select Oracle GoldenGate Monitor. Click Next.
Prerequisites	Select all three prerequisites. Click Next.
OGGMON Schema	Ensure that the proper information is supplied. Click Next.
OGGMON Schema Prefix	Enter the same schema prefix you used when creating the STB schema in RCU. Click Next.
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.

2.5 Next Step: Perform Post-Upgrade Tasks

With the upgrade process complete for your database type, you next need to perform certain post-upgrade tasks, which are described in Chapter 3, "Performing Post-Upgrade Tasks".