Oracle® GoldenGate

Upgrading to Oracle GoldenGate Monitor 12.1.3

12c (12.1.3)

E50583-02

May 2014

This document contains the procedures for upgrading Oracle GoldenGate Monitor 11g to Oracle GoldenGate MonitorServer 12.1.3.0 (12c).

Oracle GoldenGate Upgrading to Oracle GoldenGate Monitor 12.1.3, 12c (12.1.3)

E50583-02

Copyright © 2011, 2014, Oracle and/or its affiliates. All rights reserved.

Primary Author:  Edwin Spear

Contributing Author:

Contributor:

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate failsafe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Preparing to Upgrade Oracle GoldenGate Monitor Server

- 1.1 Overview

- 1.2 Upgrade Roadmap

- 1.3 Upgrade Prerequisites

- 1.4 Upgrade Tools

2 Upgrading Oracle GoldenGate Monitor Server

- 2.1 Upgrading from Version 11g on Tomcat

- 2.2 Schema Upgrade Instructions for Oracle Database Users

- 2.2.1 Create Required 12.1.3 Schema by Using RCU

- 2.2.2 Upgrade the Schema by Running UA

- 2.3 Schema Upgrade Instructions for MySQL Database Users

- 2.3.1 Upgrade the MySQL Schema by Running RCU

- 2.3.2 Upgrade the Schema by Running UA

- 2.3.2.1 Prerequisites

- 2.3.2.2 Run UA

- 2.4 Schema Upgrade Instructions for SQL Server Database Users

- 2.4.1 Update the SQL Server Database by Running RCU

- 2.4.2 Upgrade the Database by Running UA

- 2.5 Next Step: Perform Post-Upgrade Tasks

3 Performing Post-Upgrade Tasks

- 3.1 Create WebLogic Domain for Monitor Server

- 3.2 Run the Post-Upgrade Configuration Scripts

- 3.3 Create the Oracle GoldenGate agent Instance (12c)

- 3.4 Start Oracle GoldenGate Monitor Server

- 3.4.1 Starting the Server for a Compact Domain

- 3.4.2 Starting the Server for an Expanded Domain:

Preface

This document describes how to upgrade Oracle GoldenGate Monitor 11g to Oracle GoldenGate Monitor Server 12c (12.1.3.0.0). This information includes the upgrade process, details regarding the components involved in that process, pre-requisites for upgrading, and post-upgrade instructions.

Audience

This document is intended for administrators who are familiar with Oracle Fusion Middleware installation, upgrade, and administration tasks.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

For more information, see the following documents in the Oracle GoldenGate Monitor documentation set:

- Administering Oracle GoldenGate Monitor

- Oracle GoldenGate Monitor Console Online Help

- Installing and Configuring Oracle GoldenGate Monitor Server

- Installing and Configuring Oracle GoldenGate Monitor Agent

- Release Notes for Oracle GoldenGate Monitor

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 Preparing to Upgrade Oracle GoldenGate Monitor Server

This chapter summarizes the main points you should understand before upgrading Oracle Oracle GoldenGate Monitor Server from the version 11.2.1 to 12.1.3.0.0 (12c).

This chapter contains the following topics:

- Section 1.1, "Overview"

- Section 1.2, "Upgrade Roadmap"

- Section 1.3, "Upgrade Prerequisites"

- Section 1.4, "Upgrade Tools"

1.1 Overview

The upgrade process described in this document applies only for an upgrade from Oracle GoldenGate Monitor release 11.2.1 to Oracle GoldenGate Monitor Server release 12.1.3.If you are using versions prior to 11.2.1 of Oracle GoldenGate Monitor, you must first upgrade Oracle GoldenGate Monitor to release 11.2.1 before upgrading to release 12.1.3. For more information, see "Upgrading Oracle GoldenGate Monitor" in the 11.2.1 Administrator's Guide at:

http://docs.oracle.com/cd/E22355_01/doc.11111/e17815.pdf

1.2 Upgrade Roadmap

Upgrading the Oracle GoldenGate Monitor 12c (12.1.3) schema requires the following steps:

Note:

This roadmap assumes that you have stopped 11g Oracle GoldenGate Monitor Server and backed up the database and ORACLE_HOME directory.

1. Upgrade the Oracle GoldenGate Monitor schema to 12.1.3.0.0 by following the instructions for your specific database:

- For Oracle, see Section 2.2, "Schema Upgrade Instructions for Oracle Database Users".

- For MySQL, see Section 2.3, "Schema Upgrade Instructions for MySQL Database Users".

- For SQL Server, see Section 2.4, "Schema Upgrade Instructions for SQL Server Database Users".

2. Create a WebLogic domain for Oracle GoldenGate Monitor Server. For instructions, see "Configuring Oracle GoldenGate Monitor Server for Oracle Databases" in Installing and Configuring Oracle GoldenGate Monitor Server.

3. Run the post upgrade configuration scripts. For instructions, see Chapter 3, "Performing Post-Upgrade Tasks".

4. Create an Oracle GoldenGate 12.1.3 (12c) agent instance. For instructions, see "Creating and Configuring an Oracle GoldenGate Monitor Agent Instance" in Installing and Configuring Oracle GoldenGate Monitor Agent.

5. Start the Oracle GoldenGate Monitor Server 12.1.3.0.0 (12c). For instructions, see "Starting Oracle GoldenGate Monitor Server" in Installing and Configuring Oracle GoldenGate Monitor Server.

1.3 Upgrade Prerequisites

Before you can upgrade an existing 11.2.1 Oracle GoldenGate Monitor implementation to Oracle GoldenGate Monitor Server 12.1.3.0.0 (12c), ensure that the following prerequisites are met:

- JDK 1.7 installed on the target machine.

- WebLogic Server with JRF installed on the target machine.

- Oracle GoldenGate Monitor 12c (12.1.3) is installed. For installation instructions see Installing and Configuring Oracle GoldenGate Monitor Server.

- Monitor 11g server is stopped and Supported databases are installed. For current platform support information for Oracle GoldenGate Monitor 12c (12.1.3), log in to Oracle Support and click the Certifications tab. For more detailed instructions, see "Platform Support" in Installing and Configuring Oracle GoldenGate Monitor Server.

- The Oracle GoldenGate Monitor manager and the JAgent are stopped.

1.4 Upgrade Tools

You will use the following tools to upgrade Oracle GoldenGate Monitor Server.

- Repository Creation Utility (RCU); Use this tool to create the other relevant schemas for Oracle GoldenGate Monitor.
For more information on creating a repository with RCU, see Oracle Fusion Middleware Creating Schemas with the Repository Creation Utility.

- Upgrade Assistant (UA); Use this tool to upgrade Oracle GoldenGate Monitor Server schema/repository to 12.1.3.0.0 (12c).
For more information on using UA, see Upgrading with the Upgrade Assistant.

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:

1. Create Required 12.1.3 Schema by Using RCU

2. 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

1. Select System Load and Product Load.

2. Click Next.

Database Connection Details

1. Enter the Oracle GoldenGate Monitor database details.

2. Click Next.

Select Components

1. 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.

2. Click Next.
A progress window appears, checking off each schema as its prerequisites ar e met.

3. Click OK.

Schema Passwords

1. Enter the necessary password, if it's not already there, and confirm it.

2. 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

1. Select Oracle GoldenGate Monitor.

2. Click Next.

Prerequisites

1. Select all three prerequisites.

2. Click Next.

OGGMON Schema

1. Enter the Oracle GoldenGate Monitor schema name and password.

2. Click Next.

OGGMON Schema Prefix

1. Enter the same schema prefix you used when creating the STB schema in RCU (see To update the database:).

2. 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:

1. Upgrade the MySQL Schema by Running RCU

2. 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

1. Select System Load and Product Load.

2. Click Next.

Database Connection Details

1. Enter the Oracle GoldenGate Monitor database details.

2. Click Next.

Select Components

1. Service Table should be selected, by default; if not, do so. If other values are selected, deselect them.

2. Click Next.
A progress window appears, checking off the schema when its prerequisites ar e met.

3. Click OK.

Schema Passwords

1. Enter the necessary password, if it's not already there, and confirm it.

2. 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:

1. 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.

2. 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

1. Select Oracle GoldenGate Monitor.

2. Click Next.

Prerequisites

1. Select all three prerequisites.

2. Click Next.

OGGMON Schema

1. Ensure that the proper information is supplied.

2. Click Next.

OGGMON Schema Prefix

1. Enter the same schema prefix you used when creating the STB schema in RCU.

2. 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:

1. Update the SQL Server Database by Running RCU

2. 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

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 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

1. Select System Load and Product Load.

2. Click Next.

Database Connection Details

1. Enter the Oracle GoldenGate Monitor database details.

2. Click Next.

Select Components

1. Service Table should be selected, by default; if not, do so. If other values are selected, deselect them.

2. Click Next.
A progress window appears, checking off the schema when its prerequisites ar e met.

3. Click OK.

Schema Passwords

1. Enter the necessary password, if it's not already there, and confirm it.

2. 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

1. Select Oracle GoldenGate Monitor.

2. Click Next.

Prerequisites

1. Select all three prerequisites.

2. Click Next.

OGGMON Schema

1. Ensure that the proper information is supplied.

2. Click Next.

OGGMON Schema Prefix

1. Enter the same schema prefix you used when creating the STB schema in RCU.

2. 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".

3 Performing Post-Upgrade Tasks

This chapter describes the tasks required once you have updated your version of Oracle GoldenGate Monitor to the current version.

This chapter contains the following sections:

- Section 3.1, "Create WebLogic Domain for Monitor Server"

- Section 3.2, "Run the Post-Upgrade Configuration Scripts"

- Section 3.3, "Create the Oracle GoldenGate agent Instance (12c)"

- Section 3.4, "Start Oracle GoldenGate Monitor Server"

Note:

After upgrading to Oracle GoldenGate Monitor 12c (12.1.3), Oracle GoldenGate Monitor 11g users cannot immediately log in to it. You must create users and assign privileges by using the Oracle WebLogic Administration Console. For more information, see "Managing Users from the WebLogic Administration Console" in Installing and Configuring Oracle GoldenGate Monitor Server.

3.1 Create WebLogic Domain for Monitor Server

With the existing Oracle GoldenGate Monitor Server database successfully upgraded from 11.x to 12c (12.1.3), you need to create a Weblogic domain for the server implementation that runs with the upgraded schema. You must use the upgraded Monitor schema during this process. For Oracle databases, you need to create an expanded domain; however, you can only create compact domains for non-Oracle databases because they do not support the Oracle Platform Security Service (OPSS). Follow the procedure for the specific database, described in Installing and Configuring Oracle GoldenGate Monitor Server:

- To create an expanded domain for Oracle databases, see "Configuring the Server for Oracle Databases"

- To create a compact domain for non-Oracle databases (that is, MySQL and Microsoft SQL Server), see "Configuring the Server for Non-Oracle Databases".

3.2 Run the Post-Upgrade Configuration Scripts

Note:

The procedure in this section is required only if an existing customer is upgrading the Oracle GoldenGate Monitor from 11g version to 12.1.3 software.

Once the Oracle GoldenGate Monitor Server domains are created successfully, set your JAVA_HOME and then run the upgrade configuration scripts (monitor_server_cfg_update.sh and monitor_server_cfg_update.bat) to upgrade the server configuration and properties that are installed during domain creation.

The monitor_server_cfg_update.sh (Linux) and monitor_server_cfg_update.bat (Windows) scripts update the configuration properties files—which are under the newly-created domain's DOMAIN_NAME/config/monitorserver/cfg/ folder—with the Monitor server configuration and properties details from old Monitor 11g installation cfg/ directory.

To run the scripts, do the following:

1. Navigate to the DOMAIN_HOME/oggmon/plugins/upgrade/script folder and enter:

- On Linux:

$ ./monitor_server_cfg_update.sh

- On Windows:

monitor_server_cfg_update.bat

The system responds:

Enter absolute path to cfg directory of Monitor 11g installation

2. Enter (for example):

- On Linux:

/apps/monitor/cfg : /scratch/username/Monitor-11.2.1.7/oggmon_ms/cfg

- On Windows:

C\apps\monitor\cfg : C:\username\Monitor-11.2.1.7\oggmon_ms/cfg

The system responds:

Enter absolute path to cfg directory of current Monitor installation

3. Enter (for example):

- On Linux:

/weblogic/user_projects/domains/YOUR_DOMAIN_NAME/config/monitorserver/cfg) : /scratch/username/Oracle/DOMAIN_HOME/user_projects/domains/one_domain/config/monitorserver/cfg

- On Windows:

C:\weblogic\user_projects\domains\YOUR_DOMAIN_NAME\config/monitorserver\cfg) : C:\username\Oracle/DOMAIN_HOME\user_projects\domains\one_domain\config/monitorserver\cfg

3.3 Create the Oracle GoldenGate agent Instance (12c)

After running the upgrade configuration scripts described in Section 3.2, "Run the Post-Upgrade Configuration Scripts", use the following procedure to create an Oracle GoldenGate agent instance:

1. Stop the Oracle GoldenGate agent instance that is pointing to the Oracle GoldenGate Monitor 11g server.

2. Create an Oracle GoldenGate agent instance by following the instance set up instructions in Installing and Configuring Oracle GoldenGate Monitor Agent.

3. Once you have the Oracle GoldenGate agent (12c) instance, update the jagent.jmx.port property in OGG_AGENT_INST_HOME/cfg/Config.properties in the 12c instance by adding the port number value from the Oracle GoldenGate Agent 11g OGG_HOME/cfg/Config.properties. Also, ensure that all Oracle GoldenGate agent configuration property values are set correctly.

Note:

Ensure that all Oracle GoldenGate agent configuration property (MonitorServer JMX properties) values are set correctly with the newly created 12c Monitor server setup.

4. Remove existing Oracle GoldenGate JAgent (JAGENT) software that was bundled with Oracle GoldenGate Software by doing the following:

1. Delete OGG_HOME/cfg folder

2. Delete OGG_HOME/dirjar folder

3. Delete OGG_HOME/pw_agent_util.* files

4. Delete OGG_HOME/jagent.* files

5. Start the Oracle GoldenGate agent from Oracle GoldenGate Core GGSCI console by entering start jagent.

3.4 Start Oracle GoldenGate Monitor Server

Finally, start the Oracle GoldenGate Monitor Server by running the scripts described below from your domain directory:

- Starting the Server for a Compact Domain

- Starting the Server for an Expanded Domain:

3.4.1 Starting the Server for a Compact Domain

Compact domains are used for MySQL and SQL Server databases. To start an Oracle GoldenGate Monitor Server that is running a MySQL database, navigate to MONITORSERVER_MYSQL_DOMAIN and the following command:

On Linux:

$ ./startWebLogic.sh

On Windows:

C:\MONITORSERVER_MYSQL_DOMAIN> startWebLogic.cmd

To start the Monitor server that is running a SQLServer database, navigate to MONITORSERVER_SQLSERVER_DOMAIN and the following command:

On Linux:

$ ./startWebLogic.sh

On Windows:

C:\MONITORSERVER_SQLSERVER_DOMAIN> startWebLogic.cmd

3.4.2 Starting the Server for an Expanded Domain:

Expanded domains are used for Oracle databases. To start Oracle GoldenGate Monitor Server running with this type of database, do the following:

1. Navigate to MONITORSERVER_GOLDENGATE_DOMAIN and run the following scripts to start the Weblogic Administration Server as described in "Start the WebLogic Administration Server" in Installing and Configuring Oracle GoldenGate Monitor Server.

2. Navigate to MONITORSERVER_GOLDENGATE_DOMAIN/bin, and start the Weblogic 12c (12.1.3) Managed Server, as described in "Start the WebLogic Managed Server" in Installing and Configuring Oracle GoldenGate Monitor Server.

3. Run this script with the arguments noted:

$ ./startManagedWebLogic.sh MONITOR_server1 http://<hostname>:7001

4. Open the WebLogic Administration Console and, following the instructions in "Managing Monitor Server Users from the WebLogic Administration Console" in Installing and Configuring Oracle GoldenGate Monitor Server, create a Oracle GoldenGate Monitor user.

5. Once you have completed the preceding steps, log in to Oracle GoldenGate Monitor with the username and password created in the Weblogic Server and verify system functionality.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2016, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Private Alpha and Beta Draft Documentation Notice

If this document is in private preproduction status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your beta trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.