goldengate monitor 界面没有任何显示
测试环境3台机器为redhat5.4 内核2.6.18-164.el5 64位
生产主机test1 192.168.56.21 goldengate版本 Version 11.2.1.0.7 16934304
容灾机 test2 192.168.56.22 goldenagate版本 Version 11.2.1.0.7 16934304
monitor机器 192.168.56.31 monitor版本 Oracle_GoldenGate_Monitor_unix_x64_11_1_1_1_0
在test1，test2之间实现了TEST用户的同步，而且已经开启ddl支持。
在monitor上安装goldengate monitor软件。
按照如下步骤配置生产端test1
1.Add the following line if Oracle GoldenGate release is above 11.2.1
EDIT PARAMS ./GLOBALS
ENABLEMONITORING
2.Edit the /cfg/Config.properties file located in the GoldenGate software directory
agent.type.enabled=OGGMON
Ensure that the jagent.host property points to the fully qualified host name of the server of the Oracle GoldenGate instance.
jagent.host=192.168.56.21
Ensure that the property monitor.host points to the fully qualified host name of the server on which Oracle GoldenGate Monitor is installed.
The monitor.host in Config.properties value MUST MATCH with the value of monitor.jmx.server.host which is found in the monitor.properties file located in the /cfg directory where we have installed the GoldenGate Monitor software.
monitor.host =192.168.56.31
Change the monitor.jmx.username property to the user specified on the JMX Configuration screen during the Oracle GoldenGate Monitor installation.
monitor.jmx.username=jmxuser
3.Create the Wallet
Go to the GoldenGate software location (not GoldenGate Monitor software)
$ ./pw_agent_util.sh -create
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:
Wallet is created successfully.
4.Start GoldenGate
If GoldenGate version is 11.2.1 and higher then agent is Standalone Agent.
If GoldenGate version is below 11.2.1, then agent is Embedded Agent.
For Embedded Agent.
Stop and Start the Manager from ggsci via STOP MANAGER and START MANAGER comand
For Standalone Agent via GGSCI
Run ….
CREATE DATASTORE
STOP MANAGER
START MANAGER
START JAGENT
生产机上查看进程信息全部正常
GGSCI (test1) 1> info all
Program Status Group Lag at Chkpt Time Since Chkpt
MANAGER RUNNING
JAGENT RUNNING
EXTRACT RUNNING DEPA 00:00:00 00:00:07
EXTRACT RUNNING EXTA 00:00:00 00:00:10
此时在ie界面上没有任何反应，没有出现主机信息。
查看jagent进程 view report jagent 如下
COMMAND java -jar -Xms64m -Xmx512m dirjar/jagent.jar
Program is 'java', arguments are '-jar -Xms64m -Xmx512m dirjar/jagent.
jar'
**********************************************************************
*
** Run Time Messages **
***********************************************************************
2013-08-27 10:25:33 INFO OGG-00978 GGCMD JAGENT is running.
2013-08-27 10:25:33 INFO OGG-01927 Child process started, process ID 7803, command line 'java -jar -Xms64m -Xmx512m dirjar/jagent.jar'.
查看jagentlog日志，报错如下
2013-08-27 10:42:39 ERROR MBeansContainerImpl - Exception in registration process :java.lang.SecurityException: javax.security.sasl.SaslException: DIGEST-MD5: digest response format violation. Mismatched response.
2013-08-27 10:42:39 WARN MBeansContainerImpl - javax.security.sasl.SaslException: DIGEST-MD5: digest response format violation. Mismatched response.
2013-08-27 10:42:49 ERROR MBeansContainerImpl - Exception in registration process :java.lang.SecurityException: javax.security.sasl.SaslException: DIGEST-MD5: digest response format violation. Mismatched response.
2013-08-27 10:42:49 WARN MBeansContainerImpl - javax.security.sasl.SaslException: DIGEST-MD5: digest response format violation. Mismatched response.
2013-08-27 10:42:59 ERROR MBeansContainerImpl - Exception in registration process :java.lang.SecurityException: javax.security.sasl.SaslException: DIGEST-MD5: digest response format violation. Mismatched response.
2013-08-27 10:42:59 WARN MBeansContainerImpl - javax.security.sasl.SaslException: DIGEST-MD5: digest response format violation. Mismatched response.
2013-08-27 10:43:09 ERROR MBeansContainerImpl - Exception in registration process :java.lang.SecurityException: javax.security.sasl.SaslException: DIGEST-MD5: digest response format violation. Mismatched response.
2013-08-27 10:43:09 WARN MBeansContainerImpl - javax.security.sasl.SaslException: DIGEST-MD5: digest response format violation. Mismatched response.
2013-08-27 10:43:19 ERROR MBeansContainerImpl - Exception in registration process :java.lang.SecurityException: javax.security.sasl.SaslException: DIGEST-MD5: digest response format violation. Mismatched response.
2013-08-27 10:43:19 WARN MBeansContainerImpl - javax.security.sasl.SaslException: DIGEST-MD5: digest response format violation. Mismatched response.
此报错是什么意思呢，如何解决。 主备机器已经安装java1.6
配置oracle环境变量
export JAVA_HOME=/u01/jdk1.6.0_45
export PATH=$PATH:$JAVA_HOME/bin:$JAVA_HOME/jre/bin 在monitor上安装goldengate monitor软件。真没用过,根据错误信息,检查用户和密码 ODM FINDING:
Beta: Oracle GoldenGate Monitoring Agent Quick Start GuideEnabling Monitor AgentAfter the OGG Monitor Server is running,the following steps will enable the OGG monitoring agent for each OGGinstallation:
1. Install JDK 1.6 and enable environment settings
2. Create Oracle wallet
3. Edit settings in cfg/Config.properties file
4. Add ENABLEMONITORAGENT parameter to file GLOBAL
5. Restart the manager process
6. View manger report file for validation
Ensuring you have the Java Development Kit• Make sure you have some releaseof 1.6 JDK installed on the system where Oracle GoldenGate is installed.
• Set your appropriate Java andpath environmental variables to point to the JDK. (See the MonitorAdministrator's Guide for details on what is needed for various platforms.)
Creating the Oracle Wallet• Run with the –create argument:
Windows> pw_agent_util.bat –create
UNIX> pw_agent_util.sh –create
• Enter the agent's password tocommunicate with the Monitor Server and confirm it.
• Enter the JMX server passwordthat you created for the Monitor Server. (This is entered during the Monitor installation.)
PropertiesSetting properties
The agent settings in the OGGHOME/cfg/Config.properties must have some values match the Monitor Serversettings:
Parameter
(OGG_HOME/cfg/Config.properties)
Description
Monitor Server Equivalent (cfg/monitor.properties)
jagent.host
Full hostname of OGG installation
N/A
monitor.host
Full hostname of OGG Monitor server
monitor.jmx.server.host
monitor.jmx.port
Listening port on server for JMX communication monitor.jmx.server.port
monitor.jmx.username
Name of user to instantiate communication
monitor.jmx.server.user
jagent.username
Used internally. No wrong value
N/A
Where’s the password formonitor.jmx.username / monitor.jmx.server.user? It’s in the wallet. There is acwallet.sso file that lives on Monitor Server and on each agent installation indirwlt. The server wallet is created during Monitor Server installation. Theagent wallet is created (and both can be modified) locally via thepw_agent_util.sh utility.Things to watch for
• Make sure that the name youentered for the Monitor Server host during the installation is a fullyqualified name or IP address that can be used to connect to the system.
(Check the monitor.jmx.server.host inthe <Monitorinstall location>/cfg/monitor.properties file
(You should be able to ping it)
• Ensure that the name you willenter for monitor.host in the Config.properties file is the same name that you have for the monitor.jmx.server.host in the monitor properties file. If you use an IP address for one,use an IP address for the other.
• When you use a remote trail,match the RMTHOST parameter with what is entered for the jagent.host parameter in theConfig.properties file.
monitor配置文件：
# cat monitor.properties
#Copyright (c) 2009, 2011, Oracle and/or its affiliates. All rights reserved.
#Oracle GoldenGate Monitor
#Wed Feb 12 18:09:30 CST 2014
#JMX server is enabled by default (otherwise Agents cannot register), so property is optional
monitor.jmx.server.enabled=true
#JMX server's host name
monitor.jmx.server.host=192.168.56.31
#Port that is bound by the JMX server
monitor.jmx.server.port=5502
#JMX server's user
monitor.jmx.server.user=jmxuser
#Whether internal components are exposed as MBeans - useful for troubleshooting
#monitor.jmx.internal.mbeans.enabled=false
#Sender's name/email Mr. Postman <foo@goldengate.com>
monitor.smtp.from=Oracle GoldenGate Monitor <>
#SMTP server's hostname/ip
monitor.smtp.host=
#SMTP server's port
monitor.smtp.port=25
#SMTP secure mode flag
monitor.smtp.secure=false
#SMTP username for auth
monitor.smtp.user=
#Whether email alerts are generated or not
monitor.smtp.alerts.enabled=false
#Number of attempts to connect before giving up (0 or negative numbers means unlimited attempts)
#monitor.default_agent_connection.max_attempts=0
#Interval (in seconds) between each attempt
monitor.default_agent_connection.interval=30
#interval (in seconds) before each attempt to reconnect (after an existing connection was broken)
#monitor.default_agent_connection.reconnect_interval=5
#The version of meta-data currently supported by CM when the agents attempt to register
#monitor.supported.agent.metadata.version=1.0
#JPA User
monitor.jpa.connection.user=system
#JPA driver class
monitor.jpa.connection.driver_class=oracle.jdbc.driver.OracleDriver
#JPA Connection URL
monitor.jpa.connection.url=jdbc:oracle:thin:@192.168.56.22:1521:orcl
#Whether SNMP alerts are enabled or not
monitor.snmp.alerts.enabled=false
#Number of threads for the event dispatcher
monitor.events.dispatcher.threads_size=30
#Flavor of the EclipseLink dialect
eclipselink.target-database=org.eclipse.persistence.platform.database.OraclePlatform
#EclipseLink weaving mode
eclipselink.weaving=static
#Enable this property to create database objects on server re-start if the administrator wants to re-point the server install to a new database
#eclipselink.ddl-generation=create-tables
#Interval for Interval Renderer in seconds. To disable interval renderer set to 0
#monitor.web.rendering_interval=15
#Whether CLI (Command Line Interface) alerts are enabled or not
monitor.cli.alerts.enabled=false
#Time out in milli seconds for Solution Discovery to pick up events
monitor.cm.event.timeout=2000
#Maximum events before Solution Discovery to pick up
monitor.cm.event.max.size=1000 生产端配置文件：
$ cat cfg/Config.properties
####################################################################
## jagent.host: Host name of the machine where jAgent is running ###
## Note: This host name has to be reachable from Monitor Server ###
####################################################################
jagent.host=192.168.56.21
####################################################################
## jagent.jmx.port: jAgent's JMX port number ###
####################################################################
jagent.jmx.port=5588
####################################################################
## interval.regular, interval.quick: ###
## jAgent's regular and quick polling interval for new ###
## Monitoring Point values. ###
## Default values are 60 and 30 seconds ###
####################################################################
interval.regular=60
interval.quick=30
####################################################################
## monitor.host: Monitor Server host name. ###
## Note: This property has to be the same with the property: ###
## monitor.jmx.server.host in monitor.properties file ###
## on Monitor Server side ###
####################################################################
monitor.host=192.168.56.31
####################################################################
## monitor.jmx.port: Monitor Server JMX port number ###
####################################################################
monitor.jmx.port=5502
####################################################################
## monitor.jmx.username: Monitor Server JMX username ###
## This is the JMX username defined during Monitor Installation ###
####################################################################
monitor.jmx.username=jmxuser
####################################################################
## jagent.username: jAgent username ###
## It can be any name. This jAgent username will be passed to ###
## Monitor Server during jAgent registration. ###
####################################################################
jagent.username=master
####################################################################
## reg.retry.interval: jAgent incremental registration ###
## retry interval in seconds; when connection exception ###
## occurs while jAgent is connecting to Monitor Server for the ###
## first time ###
## Default value is 60 seconds ###
####################################################################
reg.retry.interval=10
####################################################################
## instance.query.initial.interval: ###
## If only manager process is running, jAgent will wait for ###
## 15 seconds by default before starting to register ###
## to Monitor Server. After this waiting period of time, ###
## if there are still no other running processes such as ###
## extract and replicat beside the manager process, JAgent will ###
## go ahead and register to Monitor Server. ###
####################################################################
instance.query.initial.interval=5
####################################################################
## incremental.registration.quiet.interval: ###
## jAgent will incrementally register to Monitor Server after ###
## a new process is configured. However, jAgent will wait for ###
## a period of 5 seconds by default before each ###
## incremental registration started. ###
####################################################################
incremental.registration.quiet.interval=5
###################################################################
## maximum.message.retrieval: ###
## Maximum number of message to retrieve from cagent/core when ###
## jagent starts ###
####################################################################
maximum.message.retrieval=500
####################################################################
## mgr.host: Host name of the machine where Manager is running ###
## Note: This host name has to be reachable from JAgent ###
## There is no need to define this property if JAgent is ###
## running on the same machine with OGG Deployment ###
####################################################################
mgr.host=192.168.56.21
####################################################################
## mgr.port: Manager port number ###
## There is no need to define this property if JAgent is ###
## running on the same machine with OGG Deployment ###
####################################################################
#mgr.port=7089
####################################################################
## jagent.rmi.port ###
## RMI Port which EM Agent will use to connect to JAgent ###
## RMI Port will only be used if agent.type.enabled=OEM ###
####################################################################
jagent.rmi.port=5559
####################################################################
## agent.type.enabled : Choose either OEM or OGGMON ###
## Choosing OGGMON will allow JAgent to register to ###
## Monitor Server and JMX RMI connector will not be enabled. ###
## Choosing OEM will enable JMX RMI connector which will be used ###
## by EM Agent to connect to JAgent and JAgent will not register ###
## to Monitor Server. ###
####################################################################
agent.type.enabled=OGGMON
####################################################################
## status.polling.interval: polling interval for status changes ###
## in second. Newly added process will be detected based on this ###
## polling interval.Default is 5 seconds. ###
####################################################################
status.polling.interval=5
####################################################################
## message.polling.interval: polling interval for message ###
## changes in second. Default is 5 seconds. ###
####################################################################
message.polling.interval=5
## This property is not being used at the moment
reg.retry.times=-1 还是没找到问题所在，依然在报错：
2013-08-27 14:43:06 ERROR MBeansContainerImpl - Exception in registration process :java.lang.SecurityException: javax.security.sasl.SaslException: DIGEST-MD5: digest response format violation. Mismatched response.
2013-08-27 14:43:06 WARN MBeansContainerImpl - javax.security.sasl.SaslException: DIGEST-MD5: digest response format violation. Mismatched response.
2013-08-27 14:43:16 ERROR MBeansContainerImpl - Exception in registration process :java.lang.SecurityException: javax.security.sasl.SaslException: DIGEST-MD5: digest response format violation. Mismatched response.
2013-08-27 14:43:16 WARN MBeansContainerImpl - javax.security.sasl.SaslException: DIGEST-MD5: digest response format violation. Mismatched response. if (!Arrays.equals(responseFromClient, expectedResponse)) {
throw new SaslException("DIGEST-MD5: digest response format " +
"violation. Mismatched response.");
}这是DigestMD5Server.java中的一段代码，密码不匹配。
agent上删除 ./dirwlt/cwallet.sso 然后重新执行 pw_agent_util.sh -create 重置密码，确保Monitor Server JMX password要和安装时设定的JMX Server密码一致。
页:
[1]