GoldenGate Monitor基础知识

1.GoldenGate Monitor介绍

Oracle GoldenGate Monitor使用基于web浏览器去监控远程的Oracle GoldenGate
instances。借助 GoldenGate Monitor 可以提高生产效率，实时监控 Oracle GoldenGate 的运行状态，减少系统持续可用性、灾难恢复、实时数据集成方案的上线时间。

2.GoldenGate Monitor 的技术架构如下：

3.Oracle GoldenGate

每个 GoldenGate instances 就是一个 GoldenGate 管理进程，配置的时候需要指定主机名和访问端口，对于一个企业级的应用环境，这个主机名最好能通过 DNS 解析，并要配置完整的域名。一个Oracle GoldenGate Monitor Server与一个或多个Oracle GoldenGate instances通信，他们使用 Java Management Extensions(JMX)技术实现的。每个 GoldenGate instance 的Manager 进程与 Monitor Agent 相关联。

4.GoldenGate Monitor Server

Oracle GoldenGate Monitor Server
协调多个 Oracle GoldenGate instances 的监控，它是一个 Java 应用程序：1) 处理来自 Oracle Goldengate Monitor Agent 的信息和 web 浏览器的显示2) 管理用户、历史数据、信息显示和事件通知(如：mail)

5.GoldenGate Monitor Repository

这个是用来存放 Director 的一些信息，如 monitor 用户和组、进程状态、事件和其他信息，需要提前准备好，并创建好相应的访问用户。

6.GoldenGate Monitor Agent

Oracle Goldengate Monitor Agent 安装在每个 Oracle GoldenGate instance，它主要是收集 GoldenGate instance 信息并发送到 Oracle GoldenGate Monitor Serve

GOLDENGATE MONITOR安装

安装前准备

软件要求

• JDK版本
  Java SE, JDK 8u40 and greater
• Oracle WebLogic Server 12.2.1.2 with JRF
  Note:The Oracle WebLogic Server version is not forward compatible, which means that it doesn’t work with Oracle GoldenGate Veridata 12.2.1.3 and future versions.
  One of the following supported databases:
• 支持数据库版本
  a.Oracle 11gR2, 12c, 18c, or 19c
  b.Microsoft SQL Server 2008, 2012, 2016, or 2019

java版本检查

软件安装到oracle用户下，所以切换到oracle用户查看
java -version

1.下载java1.8版本

https://www.oracle.com/java/technologies/downloads/#java17

2. 配置java的环境变量

cd /usr/local
chmod -R 775 jdk1.8
将下载的jdk*.tar.gz 压缩包解压后放到jdk1.8的文件夹下，移动完参考以下截图

把jdk1.8 添加到oracle的安静变量中

cat .bash_profile
export JAVA_HOME=/usr/local/jdk1.8
export $PATH=$JAVA_HOME/bin:$PATH

3. 检查java 版本，确认生效

java -version
java version “1.8.0_361”
Java™ SE Runtime Environment (build 1.8.0_361-b09)
Java HotSpot™ 64-Bit Server VM (build 25.361-b09, mixed mode)

Monitor Server端安装

Monitor Server 安装

Monitor server 的安装路径：

检查前提要求->OUI 安装 monitor server->RCU（Repository Configuration Utility）创建数据
结构->使用向导为 oracle 数据库创建 weblogic domain（如果非 oracle 数据库如：mysql
或 sqlserver，参考手册中的 1.5 和 4.2）-> 手工配置完成 domain 的创建 -> 启动 monitor
server -> welogic 中用户的配置 -> 更新server端配置，生成与agent端通信的密码文件 -> 使用新建用户启动weblogic托管服务。

Oracle Fusion Middleware 12c Infrastructure（Weblogic12c）安装

• 1.下载安装包，两个软件包
  a.Fusion Middleware Infrastructure Installer (1.5 GB)
  fmw_12.2.1.2.0_infrastructure_Disk1_1of1.zip (fmw_12.2.1.2.0_infrastructure.jar)
  http://www.oracle.com/technetwork/middleware/weblogic/downloads/wls-main-097127.html
  b.Oracle GoldenGate Monitor 12.2.1 (410 MB)
  fmw_12.2.1.2.0_ogg_Disk1_1of1.zip (fmw_12.2.1.2.0_ogg.jar)
  http://www.oracle.com/technetwork/middleware/goldengate/downloads/index.html

• 2.安装前准备
  mkdir -p /u01/ogg_monitor/Oracle_Home
  unzip fmw_12.2.1.2.0_infrastructure_Disk1_1of1.zip

• 3.安装weblogic软件
  java -jar fmw_12.2.1.2.0_infrastructure.jar

java -jar fmw_12.2.1.2.0_infrastructure.jar
Launcher log file is /tmp/OraInstall2023-05-05_04-49-26PM/launcher2023-05-05_04-49-26PM.log.
Extracting the installer . . . . . . . . Done
Checking if CPU speed is above 300 MHz. Actual 2097.571 MHz Passed
Checking monitor: must be configured to display at least 256 colors. Actual unknown. Failed <<<<
Checking swap space: must be greater than 512 MB. Actual 8191 MB Passed
Checking if this platform requires a 64-bit JVM. Actual 64 Passed (64-bit not required)
Checking temp space: must be greater than 300 MB. Actual 20712 MB Passed

Some system prerequisite checks failed.
You must fulfill these requirements before continuing.

Continue? (yes [y] / no [n]) [n]
y
You have confirmed that the product can be installed on this platform.
Continuing with the installation.

Preparing to launch the Oracle Universal Installer from /tmp/OraInstall2023-05-05_04-49-26PM
Log: /tmp/OraInstall2023-05-05_04-49-26PM/install2023-05-05_04-49-26PM.log

记住这个安装目录，后面安装时候还要用=> /u01/ogg_monitor/Oracle_Home

创建资料库

• 检查数据库的字符集
  select VALUE from nls_database_parameters where parameter=‘NLS_CHARACTERSET’;

AL32UTF8

• 执行monitor安装的Oracle_Home下的rcu进行创建
  cd /u01/ogg_monitor/Oracle_Home/oracle_common/bin/
  ./rcu
  
  
  
  
  
  
  
  
  

创建DOMAIN

• 1.执行monitor安装的Oracle_Home下的config.sh进行创建
  cd /u01/ogg_monitor/Oracle_Home/oracle_common/common/bin
  ./config.sh
  
  目录：/u01/ogg_monitor/Oracle_Home/monitor_domain
  
  这里选择从模板里面安装：/u01/ogg_monitor/Oracle_Home/oggmon/common/templates/wls/monitor_server_template.jar
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  

修改配置并启动Weblogic

• .修改weblogic的配置
  vi /u01/ogg_monitor/Oracle_Home/monitor_domain/config/monitorserver/cfg/monitor.properties
  修改为以下内容：
  monitor.jmx.server.host=localhost
  monitor.jmx.server.user=oggadmin
• 配置后台启动Weblogic的启动文件
  $ mkdir -p $DOMAIN_HOME/servers/AdminServer/security
  $ echo “username=weblogic” > $DOMAIN_HOME/servers/AdminServer/security/boot.properties
  $ echo “password=Password1” >> $DOMAIN_HOME/servers/AdminServer/security/boot.properties
• 切换到$DOMAIN_HOME目录，直接启动
  cd /u01/ogg_monitor/Oracle_Home/monitor_domain/bin
  ./startWebLogic.sh &
  输入用户密码 = > weblogic/password
  启动日志如下：

.
JAVA Memory arguments: -Xms256m -Xmx1024m
.
CLASSPATH=/u01/ogg_monitor/Oracle_Home/oracle_common/modules/features/com.oracle.db.jdbc7-dms.jar:/u01/ogg_monitor/Oracle_Home/monitor_domain/config/monitorserver/cert:/u01/ogg_monitor/Oracle_Home/monitor_domain/config/monitorserver/cfg:/usr/local/jdk1.8/lib/tools.jar:/u01/ogg_monitor/Oracle_Home/wlserver/server/lib/weblogic.jar:/u01/ogg_monitor/Oracle_Home/wlserver/…/oracle_common/modules/net.sf.antcontrib_1.1.0.0_1-0b3/lib/ant-contrib.jar:/u01/ogg_monitor/Oracle_Home/wlserver/modules/features/oracle.wls.common.nodemanager.jar:/u01/ogg_monitor/Oracle_Home/oracle_common/modules/internal/features/jrf_wlsFmw_oracle.jrf.wls.classpath.jar::/u01/ogg_monitor/Oracle_Home/wlserver/common/derby/lib/derbynet.jar:/u01/ogg_monitor/Oracle_Home/wlserver/common/derby/lib/derbyclient.jar:/u01/ogg_monitor/Oracle_Home/wlserver/common/derby/lib/derby.jar
.
PATH=/u01/ogg_monitor/Oracle_Home/monitor_domain/bin:/u01/ogg_monitor/Oracle_Home/wlserver/server/bin:/u01/ogg_monitor/Oracle_Home/wlserver/…/oracle_common/modules/org.apache.ant_1.9.2/bin:/usr/local/jdk1.8/jre/bin:/usr/local/jdk1.8/bin:/u01/app/oracle/product/19.3.0/dbhome_1/bin:/usr/local/jdk1.8/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/oracle/.local/bin:/home/oracle/bin
.

---

• To start WebLogic Server, use a username and *
• password assigned to an admin-level user. For *
• server administration, use the WebLogic Server *
• console at http://hostname:port/console *

---

Starting WLS with line:
/usr/local/jdk1.8/bin/java -server -Xms256m -Xmx1024m -Dweblogic.Name=AdminServer -Djava.security.policy=/u01/ogg_monitor/Oracle_Home/wlserver/server/lib/weblogic.policy -Dweblogic.ProductionModeEnabled=true -Doracle.monitorserver.home=/u01/ogg_monitor/Oracle_Home/oggmon -Doracle.monitorserver.domain.home=/u01/ogg_monitor/Oracle_Home/monitor_domain -Djava.util.logging.config.class=oracle.core.ojdl.logging.LoggingConfiguration -Doracle.core.ojdl.logging.config.file=/u01/ogg_monitor/Oracle_Home/monitor_domain/config/monitorserver/cfg/logging-config.xml -Doracle.core.ojdl.logging.componentId=MONITOR -Doracle.monitor.version=12.2.1.2.0 -Djava.system.class.loader=com.oracle.classloader.weblogic.LaunchClassLoader -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dopss.version=12.2.1.2 -Digf.arisidbeans.carmlloc=/u01/ogg_monitor/Oracle_Home/monitor_domain/config/fmwconfig/carml -Digf.arisidstack.home=/u01/ogg_monitor/Oracle_Home/monitor_domain/config/fmwconfig/arisidprovider -Doracle.security.jps.config=/u01/ogg_monitor/Oracle_Home/monitor_domain/config/fmwconfig/jps-config.xml -Doracle.deployed.app.dir=/u01/ogg_monitor/Oracle_Home/monitor_domain/servers/AdminServer/tmp/_WL_user -Doracle.deployed.app.ext=/- -Dweblogic.alternateTypesDirectory=/u01/ogg_monitor/Oracle_Home/oracle_common/modules/oracle.ossoiap,/u01/ogg_monitor/Oracle_Home/oracle_common/modules/oracle.oamprovider,/u01/ogg_monitor/Oracle_Home/oracle_common/modules/oracle.jps -Doracle.mds.filestore.preferred= -Dadf.version=12.2.1.1.0 -Dweblogic.jdbc.remoteEnabled=true -Dcommon.components.home=/u01/ogg_monitor/Oracle_Home/oracle_common -Djrf.version=12.2.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=/u01/ogg_monitor/Oracle_Home/monitor_domain -Doracle.server.config.dir=/u01/ogg_monitor/Oracle_Home/monitor_domain/config/fmwconfig/servers/AdminServer -Doracle.domain.config.dir=/u01/ogg_monitor/Oracle_Home/monitor_domain/config/fmwconfig -Djava.awt.headless=true -javaagent:/u01/ogg_monitor/Oracle_Home/wlserver/server/lib/debugpatch-agent.jar -da -Dwls.home=/u01/ogg_monitor/Oracle_Home/wlserver/server -Dweblogic.home=/u01/ogg_monitor/Oracle_Home/wlserver/server -Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder -Djava.util.logging.manager=oracle.core.ojdl.logging.ODLLogManager weblogic.Server
<May 15, 2023 6:20:55 PM CST> <Disabling the CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true.>
<May 15, 2023 6:20:56 PM CST> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG128 to HMACDRBG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true.>
<May 15, 2023 6:20:56 PM CST> <Starting WebLogic Server with Java HotSpot™ 64-Bit Server VM Version 25.371-b11 from Oracle Corporation.>
<May 15, 2023 6:20:56 PM CST> <“ResourceManagement” is not enabled in this JVM. Enable “ResourceManagement” to use the WebLogic Server “Resource Consumption Management” feature. To enable “ResourceManagement”, you must specify the following JVM options in the WebLogic Server instance in which the JVM runs: -XX:+UnlockCommercialFeatures -XX:+ResourceManagement.>
<May 15, 2023 6:20:56 PM CST> <Version: WebLogic Server 12.2.1.2.0 Mon Oct 3 04:35:36 PDT 2016 1827450>
<May 15, 2023 6:20:58 PM CST>

<May 15, 2023, 6:21:43,858 PM CST>
<May 15, 2023, 6:21:44,532 PM CST>
<May 15, 2023, 6:21:45,397 PM CST>
<May 15, 2023, 6:21:45,677 PM CST> <JMX Connector Server started at service:jmx:iiop://10.163.84.203:7001/jndi/weblogic.management.mbeanservers.runtime.>
2023-05-15 18:21:46.040/52.627 Oracle Coherence 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Loaded operational configuration from “jar:file:/u01/ogg_monitor/Oracle_Home/coherence/lib/coherence.jar!/tangosol-coherence.xml”
2023-05-15 18:21:46.077/52.663 Oracle Coherence 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Loaded operational overrides from “jar:file:/u01/ogg_monitor/Oracle_Home/coherence/lib/coherence.jar!/tangosol-coherence-override-prod.xml”
2023-05-15 18:21:46.078/52.665 Oracle Coherence 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Optional configuration override “/tangosol-coherence-override.xml” is not specified
2023-05-15 18:21:46.080/52.667 Oracle Coherence 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Optional configuration override “cache-factory-config.xml” is not specified
2023-05-15 18:21:46.081/52.668 Oracle Coherence 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Optional configuration override “cache-factory-builder-config.xml” is not specified
2023-05-15 18:21:46.081/52.668 Oracle Coherence 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Optional configuration override “/custom-mbeans.xml” is not specified

Oracle Coherence Version 12.2.1.2.0 Build 65221
Grid Edition: Production mode
Copyright © 2000, 2016, Oracle and/or its affiliates. All rights reserved.

2023-05-15 18:21:46.179/52.766 Oracle Coherence GE 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Loaded Reporter configuration from “file:/u01/ogg_monitor/Oracle_Home/em/metadata/reports/coherence/report-group.xml”
2023-05-15 18:21:46.185/52.771 Oracle Coherence GE 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Loaded Reporter configuration from “file:/u01/ogg_monitor/Oracle_Home/em/metadata/reports/coherence/report-cluster-config.xml”
2023-05-15 18:21:46.192/52.779 Oracle Coherence GE 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Loaded Reporter configuration from “file:/u01/ogg_monitor/Oracle_Home/em/metadata/reports/coherence/report-node-cache-config.xml”
2023-05-15 18:21:46.198/52.785 Oracle Coherence GE 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Loaded Reporter configuration from “file:/u01/ogg_monitor/Oracle_Home/em/metadata/reports/coherence/report-node-cache-size.xml”
2023-05-15 18:21:46.204/52.791 Oracle Coherence GE 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Loaded Reporter configuration from “file:/u01/ogg_monitor/Oracle_Home/em/metadata/reports/coherence/report-node-cache-usage.xml”
2023-05-15 18:21:46.211/52.798 Oracle Coherence GE 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Loaded Reporter configuration from “file:/u01/ogg_monitor/Oracle_Home/em/metadata/reports/coherence/report-node-config.xml”
2023-05-15 18:21:46.219/52.806 Oracle Coherence GE 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Loaded Reporter configuration from “file:/u01/ogg_monitor/Oracle_Home/em/metadata/reports/coherence/report-node-connection.xml”
2023-05-15 18:21:46.225/52.812 Oracle Coherence GE 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Loaded Reporter configuration from “file:/u01/ogg_monitor/Oracle_Home/em/metadata/reports/coherence/report-node-conn-mgr.xml”
2023-05-15 18:21:46.232/52.819 Oracle Coherence GE 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Loaded Reporter configuration from “file:/u01/ogg_monitor/Oracle_Home/em/metadata/reports/coherence/report-node-flash-journal.xml”
2023-05-15 18:21:46.238/52.825 Oracle Coherence GE 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Loaded Reporter configuration from “file:/u01/ogg_monitor/Oracle_Home/em/metadata/reports/coherence/report-node-garbage-collector-hotspot.xml”
2023-05-15 18:21:46.244/52.831 Oracle Coherence GE 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Loaded Reporter configuration from “file:/u01/ogg_monitor/Oracle_Home/em/metadata/reports/coherence/report-node-http-session.xml”
2023-05-15 18:21:46.250/52.837 Oracle Coherence GE 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Loaded Reporter configuration from “file:/u01/ogg_monitor/Oracle_Home/em/metadata/reports/coherence/report-node-memory-pool.xml”
2023-05-15 18:21:46.256/52.842 Oracle Coherence GE 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Loaded Reporter configuration from “file:/u01/ogg_monitor/Oracle_Home/em/metadata/reports/coherence/report-node-memory.xml”
2023-05-15 18:21:46.260/52.846 Oracle Coherence GE 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Loaded Reporter configuration from “file:/u01/ogg_monitor/Oracle_Home/em/metadata/reports/coherence/report-node-messaging.xml”
2023-05-15 18:21:46.264/52.851 Oracle Coherence GE 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Loaded Reporter configuration from “file:/u01/ogg_monitor/Oracle_Home/em/metadata/reports/coherence/report-node-network-health.xml”
2023-05-15 18:21:46.269/52.856 Oracle Coherence GE 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Loaded Reporter configuration from “file:/u01/ogg_monitor/Oracle_Home/em/metadata/reports/coherence/report-node-operating-system.xml”
2023-05-15 18:21:46.274/52.861 Oracle Coherence GE 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Loaded Reporter configuration from “file:/u01/ogg_monitor/Oracle_Home/em/metadata/reports/coherence/report-node-perf-details.xml”
2023-05-15 18:21:46.279/52.866 Oracle Coherence GE 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Loaded Reporter configuration from “file:/u01/ogg_monitor/Oracle_Home/em/metadata/reports/coherence/report-node-publisher.xml”
2023-05-15 18:21:46.284/52.870 Oracle Coherence GE 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Loaded Reporter configuration from “file:/u01/ogg_monitor/Oracle_Home/em/metadata/reports/coherence/report-node-query-optimization.xml”
2023-05-15 18:21:46.287/52.874 Oracle Coherence GE 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Loaded Reporter configuration from “file:/u01/ogg_monitor/Oracle_Home/em/metadata/reports/coherence/report-node-ram-journal.xml”
2023-05-15 18:21:46.291/52.878 Oracle Coherence GE 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Loaded Reporter configuration from “file:/u01/ogg_monitor/Oracle_Home/em/metadata/reports/coherence/report-node-runtime.config.xml”
2023-05-15 18:21:46.297/52.883 Oracle Coherence GE 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Loaded Reporter configuration from “file:/u01/ogg_monitor/Oracle_Home/em/metadata/reports/coherence/report-node-service.xml”
2023-05-15 18:21:46.302/52.888 Oracle Coherence GE 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Loaded Reporter configuration from “file:/u01/ogg_monitor/Oracle_Home/em/metadata/reports/coherence/report-node-storage-manager.xml”
2023-05-15 18:21:46.306/52.893 Oracle Coherence GE 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Loaded Reporter configuration from “file:/u01/ogg_monitor/Oracle_Home/em/metadata/reports/coherence/report-node-txn-mgr.xml”
2023-05-15 18:21:46.377/52.964 Oracle Coherence GE 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Loaded Reporter configuration from “file:/u01/ogg_monitor/Oracle_Home/em/metadata/reports/coherence/report-node-wls-http-session.xml”
2023-05-15 18:21:46.383/52.970 Oracle Coherence GE 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Loaded Reporter configuration from “file:/u01/ogg_monitor/Oracle_Home/em/metadata/reports/coherence/report-node-heap-memory.xml”
2023-05-15 18:21:46.388/52.975 Oracle Coherence GE 12.2.1.2.0 (thread=[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Loaded Reporter configuration from “file:/u01/ogg_monitor/Oracle_Home/em/metadata/reports/coherence/report-node-garbage-collector.xml”
<May 15, 2023, 6:22:19,896 PM CST> <JMX Connector Server started at service:jmx:iiop://10.163.84.203:7001/jndi/weblogic.management.mbeanservers.domainruntime.>
<May 15, 2023, 6:22:20,76 PM CST> <JMX Connector Server started at service:jmx:iiop://10.163.84.203:7001/jndi/weblogic.management.mbeanservers.edit.>
<May 15, 2023, 6:22:25,170 PM CST>

• 4.关闭weblogic服务
  ./stopWebLogic.sh

查看weblogic是否启动成功

• 1．查看weblogic启动进程，$DOMAIN_HOME
  /u01/ogg_monitor/Oracle_Home/oggmon_domain/servers/AdminServer/tmp/AdminServer.lok
• 2．查看端口是否启动
  netstat -anp |grep 7001

创建GOLDENGATE托管服务用户

• 1.登录weblogic console页面
  http://xx.xx.xx.xx:7001/console/
• 管理员用户名/密码 => weblogic/password
  主页=>安全领域=>myrealm=>用户和组=>新建
• 创建新的登录用户
  username/password=> oggadmin/password
  
  
  

更新Monitor配置，并生产密码文件

• 1.Server端启动后，生成与Agent端通信的密码文件
  更新monitor配置，Configure the JMX Server Properties
  [oracle@d2-apptest203 ~]$ cd /u01/ogg_monitor/Oracle_Home/oggmon/monitor_server/bin/
  [oracle@d2-apptest203 bin]$ ./updateOGGMonitorConfig.sh
  This script utility is used to update configuration information for monitor server. All feilds are mandatory. Press Ctrl+C to exit.
  Enter absolute path for oggmon domain:
  /u01/ogg_monitor/Oracle_Home/monitor_domain
  You have entered the domain path as : /u01/ogg_monitor/Oracle_Home/monitor_domain
  Enter JMX HOST NAME/IP:10.163.84.203
  Enter JMX Server Port:5502
  Enter JMX Server Username:oggadmin
  Enter the database type for Monitor Installation.
  For Oracle Database, Press 1. For SQL Server, Press 2:1
  May 15, 2023 6:23:50 PM oracle.security.jps.JpsStartup start
  INFO: Jps initializing.
  May 15, 2023 6:23:51 PM org.hibernate.validator.internal.util.Version
  INFO: HV000001: Hibernate Validator 5.1.3.Final
  May 15, 2023 6:23:56 PM oracle.security.jps.JpsStartup start
  INFO: Jps started.
  May 15, 2023 6:23:57 PM oracle.security.audit.Auditor init
  WARNING: IAU:IAU-6012: Unable to determine the audit log directory. No log directory specified.
  May 15, 2023 6:23:57 PM oracle.security.jps.util.JpsUtil disableAudit
  INFO: JpsUtil: isAuditDisabled set to true
  May 15, 2023 6:23:57 PM oracle.security.jps.internal.audit.AuditServiceImpl validateLogPossible
  WARNING: No audit log directory is set. Cannot perform audit operations for component JPS.

Created Secure Key properties file.
Added Secure Key into Monitor Server Oracle Wallet.

• 2.将步骤1生产的配置文件拷贝到agent实例中
  步骤1生成oggmon.properties文件.
  把文件oggmon.properties复制到agent 实例.
  在GoldenGate Monitor Server,目录是$DOMAI{N}_{H}OME/config/monitorserver/cfg;在MonitorAgent上,目录是$AGENT_HOME/cfg.
  1.cd /u01/ogg_monitor/Oracle_Home/monitor_domain/config/monitorserver/cfg
  2.scp oggmon.properties oracle@10.163.47.200:/datatmp/u01/ogg_monitor/oggagent47200/cfg/oggmon.properties

启动weblogic托管服务

• 1.配置文件设置用户名密码
  cd $DOMAIN_HOME/bin
  /u01/ogg_monitor/Oracle_Home/monitor_domain/bin/startManagedWebLogic.sh
  修改为以下内容：
  WLS_USER=“oggadmin”
  WLS_PW=“password”

• 2.启动之前调整内存（可选项）
  $ vi setStartupEnv.sh
  找到

• Startup parameters for STARTUP_GROUP MONITORSERVER-MANAGED-SERVERS
  然后修改斜体加粗部分 如图所示
  64 bit JVM memory settings
  SERVER_MEM_ARGS_64=“-Xms256m -Xmx1024m”
  export SERVER_MEM_ARGS_64
  SERVER_MEM_ARGS_64HotSpot="-Xms256m -Xmx4096m"
  export SERVER_MEM_ARGS_64HotSpot
  SERVER_MEM_ARGS_64JRockit=“-Xms256m -Xmx1024m”
  export SERVER_MEM_ARGS_64JRockit

• 3.启动weblogic托管服务
  cd /u01/ogg_monitor/Oracle_Home/monitor_domain/bin
  ./startManagedWebLogic.sh MONITORSERVER_server1 http://xx.xx.xx.xx:7001 -Djava.awt.headless=true &

• 4.关闭weblogic托管服务
  ./stopManagedWebLogic.sh MONITORSERVER_server1 http://xx.xx.xx.xx:7001

• 5.使用新建用户oggadmin登录托管网页
  进入gg monitor web页面: http://xx.xx.xx.xx:7003/monitor
  使用用户名/密码 => oggadmin/password 登录
  
  

Monitor Agent 端安装：

Monitor Agent 安装

Monitor Agent安装路径

安装 monitor agent -> 创建和配置 agent 实例 -> 拷贝Server端产生的oggmon.properties文件到Agent端 -> 生成Agent端密码文件 -> 启动Jagent

java版本检查

软件安装到oracle用户下，所以切换到oracle用户查看
java -version

1.下载java1.8版本

https://www.oracle.com/java/technologies/downloads/#java17

2. 配置java的环境变量

cd /usr/local
chmod -R 775 jdk1.8
将下载的jdk*.tar.gz 压缩包解压后放到jdk1.8的文件夹下，移动完参考以下截图

把jdk1.8 添加到oracle的安静变量中

cat .bash_profile
export JAVA_HOME=/usr/local/jdk1.8
export $PATH=$JAVA_HOME/bin:$PATH

3. 检查java 版本，确认生效

java -version
java version “1.8.0_361”
Java™ SE Runtime Environment (build 1.8.0_361-b09)
Java HotSpot™ 64-Bit Server VM (build 25.361-b09, mixed mode)

Agent图形化安装

java -jar fmw_12.2.1.2.0_ogg.jar

Monitor Agent 补丁安装

• 1.说明：
  注意是给 agent 打 patch。所以建议不要把 monitor server 和 agent 放一台机器，agent 应该
  和 ogg 实例同一台机器。
  按照文档要求，需要打 26982776 的 patch（agent 的 patch）

• 2.检查middleware opatch version(OPatch version 13.2.0.0.0 or higher)
  /u01/ogg_monitor/Oracle_Home/OPatch/opatch version
  [oracle@d2-apptest203 OPatch]$ /u01/ogg_monitor/Oracle_Home/OPatch/opatch version
  OPatch Version: 13.2.0.0.0
  OPatch succeeded.

• 3.打补丁26982776
  unzip p26982776_122120_Generic.zip
  ----切换oracle home的目录为middleware的安装目录：
  export ORACLE_HOME=/u01/ogg_monitor/Oracle_Home

/u01/ogg_monitor/Oracle_Home/OPatch/opatch apply
Oracle Interim Patch Installer version 13.9.1.0.0
Copyright © 2023, Oracle Corporation. All rights reserved.

Oracle Home : /u01/ogg_monitor/Oracle_Home
Central Inventory : /u01/app/oraInventory
from : /u01/ogg_monitor/Oracle_Home/oraInst.loc
OPatch version : 13.9.1.0.0
OUI version : 13.9.1.0.0
Log file location : /u01/ogg_monitor/Oracle_Home/cfgtoollogs/opatch/opatch2023-05-11_09-25-18AM_1.log

OPatch detects the Middleware Home as “/u01/ogg_monitor/Oracle_Home”

Verifying environment and performing prerequisite checks…
OPatch continues with these patches: 26982776

Do you want to proceed? [y|n]
Y
User Responded with: Y
All checks passed.

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = ‘/u01/ogg_monitor/Oracle_Home’)

Is the local system ready for patching? [y|n]
Y
User Responded with: Y
Backing up files…
Applying interim patch ‘26982776’ to OH ‘/u01/ogg_monitor/Oracle_Home’
ApplySession: Optional component(s) [ oracle.rcu.oggmon, 12.2.1.2.0 ] , [ oracle.rcu.oggmon, 12.2.1.2.0 ] , [ oracle.ogg.monitor.server, 12.2.1.2.0 ] , [ oracle.fmw.upgrade.oggmon, 12.2.1.2.0 ] , [ oracle.fmw.upgrade.oggmon, 12.2.1.2.0 ] not present in the Oracle Home or a higher version is found.

Patching component oracle.ogg.monitor.agent, 12.2.1.2.0…

Patching component oracle.ogg.monitor.agent, 12.2.1.2.0…
Patch 26982776 successfully applied.
Log file location: /u01/ogg_monitor/Oracle_Home/cfgtoollogs/opatch/opatch2023-05-11_09-25-18AM_1.log

OPatch succeeded.

• 4.查看补丁是否成功
  /u01/ogg_monitor/Oracle_Home/OPatch/opatch lsinventory
  Oracle Interim Patch Installer version 13.9.1.0.0
  Copyright © 2023, Oracle Corporation. All rights reserved.

Oracle Home : /u01/ogg_monitor/Oracle_Home
Central Inventory : /u01/app/oraInventory
from : /u01/ogg_monitor/Oracle_Home/oraInst.loc
OPatch version : 13.9.1.0.0
OUI version : 13.9.1.0.0
Log file location : /u01/ogg_monitor/Oracle_Home/cfgtoollogs/opatch/opatch2023-05-11_09-28-23AM_1.log

OPatch detects the Middleware Home as “/u01/ogg_monitor/Oracle_Home”

Lsinventory Output file location : /u01/ogg_monitor/Oracle_Home/cfgtoollogs/opatch/lsinv/lsinventory2023-05-11_09-28-23AM.txt

---

Local Machine Information::
Hostname: d2-giiqsdb-pre206
ARU platform id: 226
ARU platform description:: Linux x86-64

Interim patches (9) :

Patch 26982776 : applied on Thu May 11 09:25:37 CST 2023
Unique Patch ID: 21992599
Patch description: “One-off”
Created on 31 Oct 2017, 15:25:44 hrs PST8PDT
Bugs fixed:
20714185, 21909349, 21943985, 22004103, 22179784, 22752926, 23564507
23756494, 24324655, 24477119, 24525589, 25101869, 25289835, 25497895
26569656, 26569895, 26589791, 26630294, 26673458, 26847646

Patch 22754279 : applied on Wed May 10 17:40:48 CST 2023
Unique Patch ID: 20383951
Patch description: “One-off”
Created on 9 Jul 2016, 00:36:58 hrs UTC
Bugs fixed:
22754279

Patch 21663638 : applied on Wed May 10 17:40:15 CST 2023
Unique Patch ID: 20477024
Patch description: “One-off”
Created on 31 Aug 2016, 21:01:13 hrs UTC
Bugs fixed:
21663638

Patch 19795066 : applied on Wed May 10 17:39:41 CST 2023
Unique Patch ID: 19149348
Patch description: “One-off”
Created on 16 Jul 2015, 15:51:43 hrs UTC
Bugs fixed:
19795066

Patch 19632480 : applied on Wed May 10 17:39:08 CST 2023
Unique Patch ID: 19278519
Patch description: “One-off”
Created on 25 Aug 2015, 07:19:43 hrs UTC
Bugs fixed:
19632480

Patch 19154304 : applied on Wed May 10 17:38:35 CST 2023
Unique Patch ID: 19278518
Patch description: “One-off”
Created on 25 Aug 2015, 07:10:13 hrs UTC
Bugs fixed:
19154304

Patch 19030178 : applied on Wed May 10 17:38:00 CST 2023
Unique Patch ID: 19234068
Patch description: “One-off”
Created on 4 Aug 2015, 05:40:22 hrs UTC
Bugs fixed:
19030178

Patch 19002423 : applied on Wed May 10 17:37:28 CST 2023
Unique Patch ID: 18804275
Patch description: “One-off”
Created on 9 Apr 2015, 23:09:16 hrs UTC
Bugs fixed:
19002423

Patch 18905788 : applied on Wed May 10 17:36:54 CST 2023
Unique Patch ID: 18668039
Patch description: “One-off”
Created on 7 Mar 2015, 00:43:09 hrs UTC
Bugs fixed:
18905788

---

OPatch succeeded.

创建和配置 agent 实例

• 1.切换到agent的安装目录，对每个实例都要指定不同的目录，同时与agent_home不同（OGG Agent instance directory should be outside AGENT_HOME.）：
  cd /u01/ogg_monitor/Oracle_Home/oggmon/ogg_agent/
  ./create_ogg_agent_instance.sh
  Please enter absolute path of Oracle GoldenGate home directory : /u01/app/goldengate/
  Please enter absolute path of OGG Agent instance : /u01/ogg_monitor/oggagent206
  Please enter unique name to replace timestamp in startMonitorAgent script (startMonitorAgentInstance_20230510180035.sh) : 01
  Successfully created OGG Agent instance.

• 2.配置新建的 agent 实例属性：
  vi /u01/ogg_monitor/oggagent206/cfg/Config.properties
  对应的设置要和 monitor server 的设置匹配，配置被监控的 ogg 实例信息（mgr.port 等，以及用户名的一致）：
  agent 参数文件样例：
  jagent.host=xx.xx.xx.xx —agent host ip
  monitor.host=xx.xx.xx.xx —monitor host ip
  jagent.username=oggadmin
  monitor.jmx.username=oggadmin
  agent.type.enabled=OGGMON
  #mgr.host=localhost —该值可以不用去掉注释，因为在 agent 和 ogg 在同一台主机上
  #mgr.port=7089 —该值可以不用去掉注释，因为在 agent 和 ogg 在同一台主机上

配置说明：
项目 说明

项目	说明
jagent.host=xx.xx.xx.xx	运行 Agent 的主机名称，DNS 名称或 IP 地址
jagent.jmx.port=5555	Agent JMX 端口
monitor.host=xx.xx.xx.xx	monitor 的主机名称，DNS 名称或 IP 地址。名字与monitor server 主机的 cfg/monitor.properties 中 的monitor.jmx.server.host 必须一样
monitor.jmx.port=5502	Monitor Server JMX 端口，必须与 monitor server 主机的cfg/monitor.properties中monitor.jmx.server.port 相同
monitor.jmx.username=oggadmin	Monitor Server JMX 用户，在 monitor 安装的时候定义的。必须与 monitor server 主机的 cfg/monitor.properties中的 monitor.jmx.server.user 相同。否则会报：javax.security.sasl.SaslException: DIGEST-MD5: cannot acquire password for jmxUser in realm:
jagent.username=oggadmin	Agent 用户名称，它可以是任意名字。此 username 将传给 Monitor Server 在 Agent registration
注意：	a) monitor.host与monitor server的monitor.jmx.server.host必须相互 ping 通 ，b)如果Extract有RMTTRAIL 参数，则必须与 remote 的OGG中cfg/Config.properties中得jagent.host匹配

• 3.将步骤 ”3.6.4” 生产的配置文件(oggmon.properties)拷贝到agent实例中
  GoldenGate Monitor Server,目录是$DOMAIN_HOME/config/monitorserver/cfg;
  在 Monitor Agent上, 目录是$AGENT_HOME/cfg.
  1.cd /u01/ogg_monitor/Oracle_Home/monitor_domain/config/monitorserver/cfg
  2.scp oggmon.properties oracle@xx.xx.xx.xx:/datatmp/u01/ogg_monitor/oggagent47200/cfg/oggmon.properties

• 4.创建 wallet 身份验证：
  cd /u01/ogg_monitor/oggagent206/bin
  ./pw_agent_util.sh -create
  输入的 4 个密码均为 password
  Please create a password for Java Agent:
  Please confirm password for Java Agent:
  Please enter Monitor Server JMX password:
  Please confirm Monitor Server JMX password:
  May 09, 2023 10:52:05 AM oracle.security.jps.JpsStartup start
  INFO: Jps initializing.
  May 09, 2023 10:52:07 AM oracle.security.jps.JpsStartup start
  INFO: Jps started.
  Wallet is created successfully.

• 5.更新wallet密码：
  cd /u01/ogg_monitor/oggagent206/bin/
  [oracle@d2-giiqsdb-pre206 bin]$ ./pw_agent_util.sh -updateAgentJMX
  Please enter new password for Java Agent:
  Please confirm password for Java Agent:
  May 10, 2023 6:12:10 PM oracle.security.jps.JpsStartup start
  INFO: Jps initializing.
  May 10, 2023 6:12:11 PM oracle.security.jps.JpsStartup start
  INFO: Jps started.
  Password for Java Agent is updated successfully.

启动 monitor agent

• 1.先把 monitor server 上的 weblogic admin server 和 manage server 启动好；
  首先配置 ogg 主目录：
  /u01/app/goldengate/ggsci
  在mgr进程参数中加入:
  autostart jagent

• ggsci>edit param ./GLOBALS
  ENABLEMONITORING
  创建 datastore（Berkeley DB，在 ogg 的 dirbdb 目录中存储）：
  ggsci>create datastore
  退出 ggsci，然后再次登陆 ggsci
  start mgr
  start jagent
  start PMSRVR

• 查看Agent进程状态
  GGSCI (d2-giiqsdb-pre206) 4> info all
  Program Status Group Lag at Chkpt Time Since Chkpt
  MANAGER RUNNING
  JAGENT RUNNING
  PMSRVR RUNNING

查看AGENT启动日志

• 1.查看AGENT启动日志
  cd /u01/ogg_monitor/oggagent206/logs/
  tail -300f /u01/ogg_monitor/oggagent206/logs/ogg_agent.log

[2023-05-12T10:14:18.872+08:00] [JAGENT] [ERROR] [] [com.goldengate.monitor.jagent.JAgentWSMain] [tid: main] [ecid: 0000OWDjDGfAPP5LNQXBie1^NQ3u000001,0] *******************************************
[2023-05-12T10:14:18.937+08:00] [JAGENT] [ERROR] [] [com.goldengate.monitor.jagent.JAgentWSMain] [tid: main] [ecid: 0000OWDjDGfAPP5LNQXBie1^NQ3u000001,0] (NON-ERROR NOTIFICATION) Monitor Agent Release Version: 12.2.1.2.171115
[2023-05-12T10:14:18.937+08:00] [JAGENT] [ERROR] [] [com.goldengate.monitor.jagent.JAgentWSMain] [tid: main] [ecid: 0000OWDjDGfAPP5LNQXBie1^NQ3u000001,0] (NON-ERROR NOTIFICATION) Build Label: OGGMON_12.2.1.2.0_PLATFORMS_RELEASE
[2023-05-12T10:14:18.937+08:00] [JAGENT] [ERROR] [] [com.goldengate.monitor.jagent.JAgentWSMain] [tid: main] [ecid: 0000OWDjDGfAPP5LNQXBie1^NQ3u000001,0] *******************************************
[2023-05-12T10:14:29.795+08:00] [JAGENT] [NOTIFICATION] [OGGMON-20286] [com.goldengate.monitor.jagent.jmx.MBeansContainerImpl] [tid: getInstanceList] [ecid: 0000OWDjFu^APP5LNQXBie1NQ3u000002,0] Registering MBean Agent[localId=:type=agent,name=MGR] as :type=agent,name=MGR
[2023-05-12T10:14:29.803+08:00] [JAGENT] [NOTIFICATION] [OGGMON-20285] [com.goldengate.monitor.jagent.jmx.MBeansContainerImpl] [tid: getInstanceList] [ecid: 0000OWDjFu^APP5LNQXBie1NQ3u000002,0] No running process other than agent found, wait for next cycle 5 seconds for the running process!
[2023-05-12T10:14:29.805+08:00] [JAGENT] [NOTIFICATION] [OGGMON-20591] [com.goldengate.monitor.jagent.jmx.MBeansContainerImpl] [tid: getInstanceList] [ecid: 0000OWDjFu^APP5LNQXBie1NQ3u000002,0] JAgent connection info: [[
jagent.host=localhost
jagent.jmx.port=5555
monitor.host=10.163.84.203
monitor.jmx.port=5502
monitor.jmx.username=oggmsjmxusr
jagent.username=oggmajmxusr
jagent.rmi.port=OGGMON
jagent.type.enabled=false
jagent.ssl={8}

]]
[2023-05-12T10:14:29.806+08:00] [JAGENT] [NOTIFICATION] [OGGMON-20288] [com.goldengate.monitor.jagent.jmx.MBeansContainerImpl] [tid: getInstanceList] [ecid: 0000OWDjFu^APP5LNQXBie1NQ3u000002,0] Jagent Mode: Monitor-Integrated
[2023-05-12T10:14:29.889+08:00] [JAGENT] [ERROR] [OGGMON-20284] [com.goldengate.monitor.jagent.jmx.MBeansContainerImpl] [tid: agentRegistration] [ecid: 0000OWDjFw1APP5LNQXBie1^NQ3u000003,0] Exception thrown is: Authentication failed. Invalid username/password.
[2023-05-12T10:14:49.900+08:00] [JAGENT] [ERROR] [OGGMON-20284] [com.goldengate.monitor.jagent.jmx.MBeansContainerImpl] [tid: agentRegistration] [ecid: 0000OWDjFw1APP5LNQXBie1^NQ3u000003,0] Exception thrown is: Authentication failed. Invalid username/password.
[2023-05-12T10:18:49.042+08:00] [JAGENT] [ERROR] [] [com.goldengate.monitor.jagent.JAgentWSMain] [tid: main] [ecid: 0000OWDkFE5APP5LNQXBie1^NQ89000001,0] *******************************************
[2023-05-12T10:18:49.106+08:00] [JAGENT] [ERROR] [] [com.goldengate.monitor.jagent.JAgentWSMain] [tid: main] [ecid: 0000OWDkFE5APP5LNQXBie1^NQ89000001,0] (NON-ERROR NOTIFICATION) Monitor Agent Release Version: 12.2.1.2.171115
[2023-05-12T10:18:49.107+08:00] [JAGENT] [ERROR] [] [com.goldengate.monitor.jagent.JAgentWSMain] [tid: main] [ecid: 0000OWDkFE5APP5LNQXBie1^NQ89000001,0] (NON-ERROR NOTIFICATION) Build Label: OGGMON_12.2.1.2.0_PLATFORMS_RELEASE
[2023-05-12T10:18:49.107+08:00] [JAGENT] [ERROR] [] [com.goldengate.monitor.jagent.JAgentWSMain] [tid: main] [ecid: 0000OWDkFE5APP5LNQXBie1^NQ89000001,0] *******************************************
[2023-05-12T10:18:57.355+08:00] [JAGENT] [NOTIFICATION] [OGGMON-20286] [com.goldengate.monitor.jagent.jmx.MBeansContainerImpl] [tid: getInstanceList] [ecid: 0000OWDkHFBAPP5LNQXBie1^NQ89000002,0] Registering MBean Agent[localId=:type=agent,name=MGR] as :type=agent,name=MGR
[2023-05-12T10:18:57.362+08:00] [JAGENT] [NOTIFICATION] [OGGMON-20285] [com.goldengate.monitor.jagent.jmx.MBeansContainerImpl] [tid: getInstanceList] [ecid: 0000OWDkHFBAPP5LNQXBie1^NQ89000002,0] No running process other than agent found, wait for next cycle 5 seconds for the running process!
[2023-05-12T10:18:57.364+08:00] [JAGENT] [NOTIFICATION] [OGGMON-20591] [com.goldengate.monitor.jagent.jmx.MBeansContainerImpl] [tid: getInstanceList] [ecid: 0000OWDkHFBAPP5LNQXBie1^NQ89000002,0] JAgent connection info: [[
jagent.host=localhost
jagent.jmx.port=5555
monitor.host=10.163.84.203
monitor.jmx.port=5502
monitor.jmx.username=oggadmin
jagent.username=oggadmin
jagent.rmi.port=OGGMON
jagent.type.enabled=false
jagent.ssl={8}

]]
[2023-05-12T10:18:57.366+08:00] [JAGENT] [NOTIFICATION] [OGGMON-20288] [com.goldengate.monitor.jagent.jmx.MBeansContainerImpl] [tid: getInstanceList] [ecid: 0000OWDkHFBAPP5LNQXBie1^NQ89000002,0] Jagent Mode: Monitor-Integrated

Goldengate 托管平台：

登录GOLDENGATE托管页面

1.登录托管平台页面
http://xx.xx.xx.xx:7003/monitor/faces/secured/activeDataAlertsPage.jspx
Username/password=>oggadmin/password

GOLDENGATE托管页面信息

• 页面汇总信息
  
• 2.进程详细信息
  
• 3.ogg相关日志
  
  
• 相关配置的信息
  

Goldengate管理平台日常运维

问题处理

1. Agent启动报用户名密码错

问题：[2017-03-10T13:07:53.552-07:00] [JAGENT] [ERROR] [OGGMON-20284] [com.goldengate.monitor.jagent.jmx.MBeansContainerImpl] [tid: agentRegistration] [ecid: 0000LetpR11B5EI5yrG7yW1OkkUP000001,0] Exception thrown is: Authentication failed. Invalid username/password.

[2017-03-10T13:08:03.706-07:00] [JAGENT] [ERROR] [OGGMON-20284] [com.goldengate.monitor.jagent.jmx.MBeansContainerImpl] [tid: agentRegistration] [ecid: 0000LetpR11B5EI5yrG7yW1OkkUP000001,0] Exception thrown is: Authentication failed. Invalid username/password.

解决方案：

OGG Monitor Agent Receives -> OGGMON-20284 Nvalid Username/password Error (Doc ID 2243843.1)
The error message does not indicate if the problem is with the username, the password, or both.

To check that the username is valid make sure that $OGGMON_AGENT_INST_HOME/cfg/Config.properties
parameter -> monitor.jmx.username=

Matches the value of
$OGG_MONITOR_SERVER/config/monitorserver/cfg/monitor.properties
parameter -> monitor.jmx.server.user=jmxuser

If there is a difference in values for these parameters then modify
$OGGMON_AGENT_INST_HOME/cfg/Config.properties
parameter -> monitor.jmx.username=jmxuser
to match and save Config.properties file changes.

Then re-create $OGGMON_AGENT_INST_HOME/dirwlt (wallet)
using $OGGMON_AGENT_INST_HOME/bin/pw_agent_util.sh -create

Finally, start “jagent” from ggsci prompt and monitor -> “ogg_agent.log”
as the “Invalid username/password” should be resolved.

If problem persist, then it could be related to wrong/invalid password.
Check Doc ID 2007276.1

2. Agent Could not decrypt password

问题：

[2023-05-11T10:26:59.737+08:00] [JAGENT] [ERROR] [OGGMON-20270] [com.goldengate.monitor.jagent.jmx.MBeansContainerImpl] [tid: agentRegistration] [ecid: 0000OW8_OqOAPP5LNQXBie1^N4wo000002,0] Please perform the following steps to fix the problem if it still occurs: [[

1. Restart JAgent (Stop and Start JAgent again).
2. If problem still persists after step 1, please restart Monitor Server.
   ]]
   [2023-05-11T10:27:19.750+08:00] [JAGENT] [ERROR] [OGGMON-20604] [com.goldengate.monitor.jagent.config.impl.CmDelegateImpl] [tid: agentRegistration] [ecid: 0000OW8_OqOAPP5LNQXBie1^N4wo000002,0] Error encrypting Agent JMX Password. Exception: null
   [2023-05-11T10:27:19.752+08:00] [JAGENT] [ERROR] [OGGMON-20269] [com.goldengate.monitor.jagent.jmx.MBeansContainerImpl] [tid: agentRegistration] [ecid: 0000OW8_OqOAPP5LNQXBie1^N4wo000002,0] com.goldengate.monitor.MonitorException[[
   at com.goldengate.monitor.jagent.config.impl.CmDelegateImpl.encryptAgentJmxPassword(CmDelegateImpl.java:192)
   at com.goldengate.monitor.jagent.config.impl.CmDelegateImpl.initJmxObjects(CmDelegateImpl.java:158)
   at com.goldengate.monitor.jagent.config.impl.CmDelegateImpl.register(CmDelegateImpl.java:80)
   at com.goldengate.monitor.jagent.jmx.MBeansContainerImpl$2.run(MBeansContainerImpl.java:1630)
   at java.lang.Thread.run(Thread.java:750).

解决方案：

参考文档： MON Agent Fails with [OGGMON-20269] Could not decrypt password (Doc ID 2319218.1)
NOTE:
If there is an existing “instance” of GoldenGate already registered with the same “hostname” and manager port in GoldenGate Monitor Server
please delete that first after the steps below but BEFORE re-starting jagent. It is possible that old/stale GoldenGate Monitor Server meta data
information cause issues similar to this upon re-registration attempt with Monitor Server UI.

1. Delete existing oggmon.properties from JAgent.
2. Delete wallet (remove dirwlt) => rm -rf /u01/ogg_monitor/Oracle_Home/oggagent206/dirwlt
3. Copy oggmon.properties using (cp/scp/ftp) from the Monitor Server after running unix2dos on 12.2.1.1 version oggmon.properties
4. Re-create Wallet.
5. Restart JAgent.

3. Jagent Fails With Unexpected Behavior No Agent Object Found JAgent Will Exit

问题：Jagent Fails With Unexpected Behavior No Agent Object Found JAgent Will Exit

解决方案：参考文档：Jagent Fails With Unexpected Behavior No Agent Object Found JAgent Will Exit (Doc ID 2320529.1)

OGG Monitor Agent 12.2.1.2.0 is not compatible with PMSRVR.
GoldenGate 12.3.x monitoring is now available either Oracle Enterprise Manager or OGG Monitor Server 12.2.x. We need to have Patch 26982776 applied in-order to monitor 12.3 OGG processes.
How to Install and Configure GoldenGate Monitor Server 12.2.1 and Monitor Agent 12.2.1? [VIDEO] (Doc ID 2186831.1)

4. [JAGENT] [ERROR] [OGGMON-20348] [com.goldengate.monitor.jagent.jmx.ManagerConnectionKeeperThread] [tid: ManagerConnectionKeeper] [ecid: 0000OWTDWHT3Z75LNQK6ye1^OPS6000002,0] Failed to establish a connection to the OGG Core Manager Process-Host:10.163.89.115 Port:7,809. Stop all polling tasks. Wait for 17 second(s) and retry again. Due to OGGMON-20625

问题：[JAGENT] [ERROR] [OGGMON-20348] [com.goldengate.monitor.jagent.jmx.ManagerConnectionKeeperThread] [tid: ManagerConnectionKeeper] [ecid: 0000OWTDWHT3Z75LNQK6ye1^OPS6000002,0] Failed to establish a connection to the OGG Core Manager Process-Host:10.163.89.115 Port:7,809. Stop all polling tasks. Wait for 17 second(s) and retry again. Due to OGGMON-20625

解决方案：

参考文档：False OEM or OGGMON SRV Emails for GoldenGate targets - OGGMON-20348 Failed To Establish A Connection To The OGG Core Web Services-Host (Doc ID 2701817.1)

1. Make sure GoldenGate “core” has a bundle patch that contains fix for bug 29382134
   To confirm this, run “opatch lsinventory” for $OGG_HOME and search command output for ‘29382134’
   If in doubt, open a new SR and upload $OGG_HOME/dirrpt/MGR.rpt and “opatch lsinventory” output.
   In the new SR, request bundle patch with fix of bug 29382134.

2. Make sure GoldenGate Monitor Agent (jagent) is patched to the latest bundle patch.
   At time of publication of this doc. id. the latest OGG Monitor Agent patch is
   Patch 30241740: Oracle GoldenGate Monitor 12.2.1.2.200131 (PS2 BP6)

3. If both items #1 and #2 above are completed and OEM false/fake emails are still received and

[JAGENT] [ERROR] [OGGMON-20348] [com.goldengate.monitor.jagent.jmx.ManagerConnectionKeeperThread] [tid: ManagerConnectionKeeper] [ecid: 0000NEJ^e4d2zGIqyo6iMG1V7oNM000003,0] Failed to establish a connection to the OGG Core Web Services-Host:xxx.xx.xxx.xx Port:9,004. Stop all polling tasks. Wait for 1 second(s) and retry again. Due to OGGMON-20614
type errors still occur in -> $OGGMON_AGENT_INSTANCE_HOME/logs/oggagent.lgo

Then

1. Increase -> interval.quick=120
   in $OGGMON_AGENT_INSTANCE_HOME/cfg/Config.properties
   save the changes.
2. Login to ggsci prompt and run
   stop jagent
   start jagent
   for changes to take effect.
3. Monitor environment behavior to confirm the issue is resolved.

5. RCU-6016:The specified prefix already exists

问题：安装RCU时候，报错：RCU-6016:The specified prefix already exists

解决方案：

1. Connect to the repository database an ADMIN user and execute the following SQL statement:
   select comp_name,OWNER,VERSION,STATUS,COMP_ID,MRC_NAME from SCHEMA_VERSION_REGISTRY TT where owner like ‘OGGMON%’;
   
2. If any row is returned, delete it with one or all the folling SQL statements:
   delete from SCHEMA_VERSION_REGISTRY where owner like ‘OGGMON%’;
   commit;

相关文档参考

1.Oracle WebLogic Server 12c: Installing WebLogic Server and Creating a Domain

https://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/wls/12c/12_1_3/01/installwls.html

2.How to Install and Configure GoldenGate Monitor Server 12.2.1 and Monitor Agent 12.2.1? [VIDEO] (Doc ID 2186831.1)

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=419190440550094&id=2186831.1&_adf.ctrl-state=6rsktxax0_77