This note describes the process of deploying the Enterprise Manager Cloud Control 13c Release 2 plug-in (13.2.1.0.0) for Oracle GoldenGate.

At a high level, these are the main steps involved:

Download the latest GoldenGate plug-in version 13.2.1.0.0. This can be done manually by downloading it from the Oracle Software Cloud (edelivery.oracle.com) website or via the Online/Offline Patching feature available in OEM Cloud Control.

Deploy the plug-in first on the Management Server and then the agent running on all the hosts where we want monitoring enabled for running Oracle GoldenGate instances.

Install the GoldenGate Monitor Agent Configure the GoldenGate Monitor Agent (JAgent) Discover and configure Oracle GoldenGate targets in Cloud Control 13c Release 2

Download the latest GoldenGate plug-in version 13.2.1.0.0

In this instance, the OEM 13c environment has been configured for Online Patching which will automatically download patches and self-updates.

From the Setup – Extensibility – Self Update menu we open the Plug-in Updates page and we can see that the Oracle GoldenGate 13.2.1.0.0 version plug-in is having the status ‘Available’.

We will now download the latest update and schedule it to start immediately.

We can also monitor the status of the download job which was submitted.

Note now that the status has changed from ‘Available’ to ‘Downloaded’.

From the Setup – Extensibility – Plug-ins menu we launch the Plug-ins page and we can see that the latest version of the GoldenGate plug-in has been downloaded.

Deploying the Oracle GoldenGate Plug-in

The downloaded Plug-ins now need to be deployed on both the OMS as well as on management agents located on hosts where we have an instance of Oracle GoldenGate running which we need to monitor via OEM.

We first have to deploy the plug-in on the Management Server host.

Note – deploying the plug-in on the OMS host will incur a bit of downtime while the plug-in deployment is in progress.

Note – this is a test instance and that is why the Repository Database is running in NOARCHIVELOG mode. Do not do this in production!

We can now log out from the 13c OEM console as the instance will automatically be shut down and we will anyway see an error on the page if we do not exit.

Monitor the status of the plug-in deployment via the emctl status oms -details command.

[oracle@emcc bin]$ ./emctl status oms -detailsOracle Enterprise Manager Cloud Control 13c Release 2 Copyright (c) 1996, 2016 Oracle Corporation. All rights reserved.Enter Enterprise Manager Root (SYSMAN) Password : Console Server Host : emcc.example.comHTTP Console Port : 7788HTTPS Console Port : 7799

HTTP Upload Port : 4889HTTPS Upload Port : 4900EM Instance Home : /u02/app/gc_inst/em/EMGC_OMS1OMS Log Directory Location : /u02/app/gc_inst/em/EMGC_OMS1/sysman/logOMS is not configured with SLB or virtual hostnameAgent Upload is locked.OMS Console is locked.Active CA ID: 1Console URL: https://emcc.example.com:7799/emUpload URL: https://emcc.example.com:4900/empbs/upload

WLS Domain InformationDomain Name : GCDomainAdmin Server Host : emcc.example.comAdmin Server HTTPS Port: 7101

Oracle Management Server InformationManaged Server Instance Name: EMGC_OMS1Oracle Management Server Instance Host: emcc.example.comWebTier is Down

Oracle Management Server status is down possibly because plug-ins are being deployed or undeployed from it. Use -details option to get more details about the plug-in deployment status.Plug-in Deployment/Undeployment Status

Destination : Management Server - emcc.example.com:4889_Management_ServicePlug-in Name : Oracle GoldenGate Version : 13.2.1.0.0 ID : oracle.fmw.gg Content : Plug-in Action : Deployment Status : Deploying Steps Info:---------------------------------------- ------------------------- ------------------------- ---------- Step Start Time End Time Status ---------------------------------------- ------------------------- ------------------------- ---------- Submit job for deployment 12/2/16 2:42:46 PM AWST 12/2/16 2:42:46 PM AWST Success

Initialize 12/2/16 2:42:48 PM AWST 12/2/16 2:42:57 PM AWST Success

Install software 12/2/16 2:42:57 PM AWST 12/2/16 2:43:01 PM AWST Success

Validate plug-in home 12/2/16 2:43:06 PM AWST 12/2/16 2:43:06 PM AWST Success

Perform custom preconfiguration 12/2/16 2:43:07 PM AWST 12/2/16 2:43:07 PM AWST Success

Check mandatory patches 12/2/16 2:43:07 PM AWST 12/2/16 2:43:07 PM AWST Success

Generate metadata SQL 12/2/16 2:43:07 PM AWST 12/2/16 2:43:07 PM AWST Success

Preconfigure Management Repository 12/2/16 2:43:07 PM AWST 12/2/16 2:43:07 PM AWST Success

Preregister DLF 12/2/16 2:43:07 PM AWST 12/2/16 2:43:07 PM AWST Success

Stop management server 12/2/16 2:43:07 PM AWST 12/2/16 2:45:27 PM AWST Success

Configure Management Repository 12/2/16 2:45:27 PM AWST N/A Running

Register DLF 12/2/16 2:45:27 PM AWST N/A Running

Configure middle tier 12/2/16 2:45:27 PM AWST N/A Running

After some time, we run the same command again and we can see that the plug-in deployment has been successfully completed and that the OMS is now being restarted.

Submit job for deployment 12/2/16 2:42:46 PM AWST 12/2/16 2:42:46 PM AWST Success

Initialize 12/2/16 2:42:48 PM AWST 12/2/16 2:42:57 PM AWST Success

Install software 12/2/16 2:42:57 PM AWST 12/2/16 2:43:01 PM AWST Success

Validate plug-in home 12/2/16 2:43:06 PM AWST 12/2/16 2:43:06 PM AWST Success

Perform custom preconfiguration 12/2/16 2:43:07 PM AWST 12/2/16 2:43:07 PM AWST Success

Check mandatory patches 12/2/16 2:43:07 PM AWST 12/2/16 2:43:07 PM AWST Success

Generate metadata SQL 12/2/16 2:43:07 PM AWST 12/2/16 2:43:07 PM AWST Success

Preconfigure Management Repository 12/2/16 2:43:07 PM AWST 12/2/16 2:43:07 PM AWST Success

Preregister DLF 12/2/16 2:43:07 PM AWST 12/2/16 2:43:07 PM AWST Success

Stop management server 12/2/16 2:43:07 PM AWST 12/2/16 2:45:27 PM AWST Success

Configure Management Repository 12/2/16 2:45:27 PM AWST 12/2/16 2:48:15 PM AWST Success

Register DLF 12/2/16 2:45:27 PM AWST 12/2/16 2:47:20 PM AWST Success

Configure middle tier 12/2/16 2:45:27 PM AWST 12/2/16 2:49:12 PM AWST Success

OPSS jazn policy migration 12/2/16 2:49:13 PM AWST 12/2/16 2:49:38 PM AWST Success

Register metadata 12/2/16 2:49:38 PM AWST 12/2/16 2:49:43 PM AWST Success

Perform custom postconfiguration 12/2/16 2:49:43 PM AWST 12/2/16 2:49:43 PM AWST Success

Update inventory 12/2/16 2:49:43 PM AWST 12/2/16 2:49:45 PM AWST Success

Start management server 12/2/16 2:49:45 PM AWST N/A Running

After the OMS is restarted we can log back in to OEM 13c and check the status of the deployment job from the console as well.

We now can see that the plug-in has been deployed on the Management Server and we next have to deploy the plug-in on each Management Agent as we so require.

From the Deploy On menu select Management Agent.

Select the agent running on the host where we would like to deploy the GoldenGate plug-in.

Note – deploying the plug-in on the management agent will not require any downtime.

Execute the command emcli get_plugin_deployment_status to monitor the progress of the plug-in deployment on the Management Agent.

[oracle@emcc bin]$ ./emcli login -username=sysman -password=welcome1

Login successful

[oracle@emcc bin]$ ./emcli get_plugin_deployment_status

Displaying status for the latest deployment activity(deployment ID 15)

Plug-in Deployment/Undeployment Status

Destination : Management Agent - host01.localdomain:3872

Plug-in Name : Oracle GoldenGate

Version : 13.2.1.0.0

ID : oracle.fmw.gg

Content : Plug-in

Action : Deployment

Status : Deploying

Steps Info:

---------------------------------------- ------------------------- ------------------------- ----------

Step Start Time End Time Status

---------------------------------------- ------------------------- ------------------------- ----------

Submit job for deployment 12/2/16 12:35:09 AM PST 12/2/16 12:35:09 AM PST Success

Initialize 12/2/16 12:36:49 AM PST 12/2/16 12:37:31 AM PST Success

Validate Environment 12/2/16 12:37:33 AM PST 12/2/16 12:37:33 AM PST Success

Install software 12/2/16 12:37:34 AM PST 12/2/16 12:37:36 AM PST Success

Attach Oracle Home to Inventory 12/2/16 12:37:38 AM PST 12/2/16 12:38:18 AM PST Success

Configure plug-in on Management Agent 12/2/16 12:38:19 AM PST N/A Running

If we execute the same command again we can see that the plug-in deployment on the agent has completed successfully.

[oracle@emcc bin]$ ./emcli get_plugin_deployment_status

Displaying status for the latest deployment activity(deployment ID 15)

Plug-in Deployment/Undeployment Status

Destination : Management Agent - host01.localdomain:3872

Plug-in Name : Oracle GoldenGate

Version : 13.2.1.0.0

ID : oracle.fmw.gg

Content : Plug-in

Action : Deployment

Status : Success

Steps Info:

---------------------------------------- ------------------------- ------------------------- ----------

Step Start Time End Time Status

---------------------------------------- ------------------------- ------------------------- ----------

Submit job for deployment 12/2/16 12:35:09 AM PST 12/2/16 12:35:09 AM PST Success

Initialize 12/2/16 12:36:49 AM PST 12/2/16 12:37:31 AM PST Success

Validate Environment 12/2/16 12:37:33 AM PST 12/2/16 12:37:33 AM PST Success

Install software 12/2/16 12:37:34 AM PST 12/2/16 12:37:36 AM PST Success

Attach Oracle Home to Inventory 12/2/16 12:37:38 AM PST 12/2/16 12:38:18 AM PST Success

Configure plug-in on Management Agent 12/2/16 12:38:19 AM PST 12/2/16 12:39:23 AM PST Success

Update inventory 12/2/16 12:39:08 AM PST 12/2/16 12:39:23 AM PST Success

We can also check the status of the deployment job via the OEM 13c console

We can now see that the GoldenGate 13.2.1.0.0 plug-in has been deployed on both the Management server as well as the Management Agent.

Install GoldenGate Monitor Agent

From the Oracle Software Delivery Cloud website (edelivery.oracle.com) download the file V789398-01.zip which is the Oracle Fusion Middleware 12c (12.2.1.2.0) GoldenGate Monitor and Veridata product.

Unzip the V789398-01.zip file

[oracle@host01 V789398-01]$ ls -l

total 435577

-rwxrwx---. 1 root vboxsf 446021430 Oct 11 18:46 fmw_12.2.1.2.0_ogg.jar

-rwxrwx---. 1 root vboxsf 8986 Dec 2 17:19 fmw_12212_readme.htm

Install JDK 1.8

[root@host01 sf_software]# rpm -ivh jdk-8u111-linux-x64.rpm

Preparing... ########################################### [100%]

1:jdk1.8.0_111 ########################################### [100%]

Unpacking JAR files...

tools.jar...

plugin.jar...

javaws.jar...

deploy.jar...

rt.jar...

jsse.jar...

charsets.jar...

localedata.jar...

[root@host01 sf_software]# java -version

java version "1.8.0_111"

Java(TM) SE Runtime Environment (build 1.8.0_111-b14)

Java HotSpot(TM) 64-Bit Server VM (build 25.111-b14, mixed mode)

Set the JAVA_HOME environment variable

[oracle@host01 V789398-01]$ export JAVA_HOME=/usr/java/jdk1.8.0_111

[oracle@host01 V789398-01]$ $JAVA_HOME/bin/java -version

java version "1.8.0_111"

Java(TM) SE Runtime Environment (build 1.8.0_111-b14)

Java HotSpot(TM) 64-Bit Server VM (build 25.111-b14, mixed mode)

Launch the Fusion Middleware 12c GG Monitor_Veridata installer

[oracle@host01 V789398-01]$ $JAVA_HOME/bin/java -jar fmw_12.2.1.2.0_ogg.jar

Launcher log file is /tmp/OraInstall2016-12-02_05-38-45PM/launcher2016-12-02_05-38-45PM.log.

Extracting the installer . . . . . . . . . Done

Enter the location to install the Goldengate Monitor Agent

Configure the GoldenGate Monitor Agent (JAGENT)

We need to provide the path to the existing Oracle 12c GoldenGate home directory and also the location of the OGG agent instance. The OGG agent instance location will be under the directory where we had just installed the GoldenGate monitor agent.

[oracle@host01 ogg_agent]$ pwd

/u01/app/ogg_agent/oggmon/ogg_agent

[oracle@host01 ogg_agent]$ echo $OGG_11G

/u01/app/oracle/ogg_11g

[oracle@host01 ogg_agent]$ ./createMonitorAgentInstance.sh

Please enter absolute path of Oracle GoldenGate home directory : /u01/app/oracle/ogg_11g

Please enter absolute path of OGG Agent instance : /u01/app/ogg_agent/agent_inst

Please enter unique name to replace timestamp in startMonitorAgent script (startMonitorAgentInstance_20161203104343.sh) :

Successfully created OGG Agent instance.

Note the password we provide for the Java Agent. We will need to provide this password when we configure GoldenGate in the 13c OEM Cloud Control console.

[oracle@host01 bin]$ pwd

/u01/app/ogg_agent/agent_inst/bin

[oracle@host01 bin]$ ./pw_agent_util.sh -jagentonly

Please create a password for Java Agent:

Please confirm password for Java Agent:

Dec 03, 2016 10:47:54 AM oracle.security.jps.JpsStartup start

INFO: Jps initializing.

Dec 03, 2016 10:47:55 AM oracle.security.jps.JpsStartup start

INFO: Jps started.

Wallet is created successfully.

Edit the Config.properties file and change the following lines from the default values.

We can provide any name for the jagent.username parameter. Again, make a note of what value we provide for the jagent username as we will need to provide this value when we configure GoldenGate later on via the OEM 13c console.

[oracle@host01 bin]$ cd /u01/app/ogg_agent/agent_inst/cfg

[oracle@host01 cfg]$ vi Config.properties

jagent.host=host01.localdomain

jagent.username=oggmon

agent.type.enabled=OEM

Edit the GLOBALS file in the GoldenGate instance and include the parameter ENABLEMONITORING

GGSCI (host01.localdomain) 1> edit params ./GLOBALS

ENABLEMONITORING

Stop and start the manager process.

GGSCI (host01.localdomain) 1> stop manager

Manager process is required by other GGS processes.

Are you sure you want to stop it (y/n)?y

Sending STOP request to MANAGER ...

Request processed.

Manager stopped.

GGSCI (host01.localdomain) 2> start manager

Manager started.

GGSCI (host01.localdomain) 3> info all

Program Status Group Lag at Chkpt Time Since Chkpt

MANAGER RUNNING

JAGENT STOPPED

Start the JAgent

GGSCI (host01.localdomain) 4> start jagent

Sending START request to MANAGER ...

GGCMD JAGENT starting

GGSCI (host01.localdomain) 5> info all

Program Status Group Lag at Chkpt Time Since Chkpt

MANAGER RUNNING

JAGENT RUNNING

Port 5559 is the RMI Port which EM Agent will use to connect to JAgent (by default). Use netstat command to see if the Jagent is listening on that port

[oracle@host01 ogg_11g]$ netstat -an |grep 5559

tcp 0 0 :::5559 :::* LISTEN

Discover and Configure GoldenGate targets in Oracle Enterprise Manager Cloud Control

From the Setup – Add Target – Configure Auto Discovery menu, open the Setup Discovery page

Click on GoldenGate Discovery

Click Add

Select the required host

Highlight the host and click on the Edit Parameters icon

Enter the values for the JAgent user name and password – note we had entered the JAgent username in the Config.properties file and the JAgent password when we created the OGG Agent instance earlier.

Highlight the host and click on Discover Now

We can now see that the Auto Discovery which ran earlier has discovered the GoldenGate manager process and the running Oracle GoldenGate instance

Highlight the Oracle GoldenGate instance and click on Promote

The Manager process is automatically selected to be promoted as well.

We can now see in the Targets menu, an entry appearing for GoldenGate as well which was not present earlier.

Selecting GoldenGate from the Targets menu will now take us to the OGG Instance home page in OEM

We can see the GoldenGate instance and Manager process indicating a status of running

But if we click on MGR link, it shows that we have not set the Preferred credentials as yet. These credentials are basically those of the operating system user account under which the Oracle GoldenGate software was installed on the host server.

Highlight Oracle GoldenGate Manager and click on Manage Preferred Credentials icon

Click on Set

We can use one of the existing Named Credentials we had created earlier

Click on Test and Save

We next should set the preferred credentials for the Oracle GoldenGate instance as a whole itself. Here we have to include the username and password of the GoldenGate Monitoring Agent which is called the OGG Admin.

Click on Set

Click on Test and Save

We can also customize how the name of the Oracle GoldenGate instance should appear in the OEM console OGG Home Page. Click on the Customize link and change the default naming via the Alias column.

Let us check if the status of the GoldenGate instance is being reported correctly in OEM.

Via GGSCI we stop the manager process

GGSCI (host01.localdomain) 1> stop manager

Manager process is required by other GGS processes.

Are you sure you want to stop it (y/n)?y

Sending STOP request to MANAGER ...

Request processed.

Manager stopped.

After about 10-15 seconds, we can see that the status of GoldenGate targets is showing down in OEM

Via GGSCI we now start the Manager and after a few seconds have elapsed we can see that the status of the GoldenGate targets in OEM are now showing as Running.

GGSCI (host01.localdomain) 4> start manager

Manager started.