In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-01-17 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >
Share
Shulou(Shulou.com)06/01 Report--
The JAVA version is greater than 1.6.
[root@cwogg ~] # rpm-ivh jre-8u65-linux-x64.rpm
Preparing... # [100%]
1:jre1.8.0_65 # # [100%]
Unpacking JAR files...
Plugin.jar...
Javaws.jar...
Deploy.jar...
Rt.jar...
Jsse.jar...
Charsets.jar...
Localedata.jar...
Jfxrt.jar...
Add java environment variable to oracle user: (because I used ogg installed by oracle user)
Export PATH
Export ORACLE_BASE=/u01/app/oracle
Export ORACLE_HOME=/u01/app/oracle/product/11.2.0/db_1
Export ORACLE_SID=PHUB
Export PATH=$ORACLE_HOME/bin:$PATH
Export LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib
Export CLASSPATH=$ORACLE_HOME/JRE:$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib
Export DISPLAY=:0.0
Umask=022
Alias sqlplus='rlwrap sqlplus'
Alias rman='rlwrap rman'
Alias ggsci='rlwrap ggsci'
Export PATH=/u01/ogg:$PATH
Export LD_LIBRARY_PATH=/u01/ogg:$LD_LIBRARY_PATH
Export GGATE=/u01/ogg
Export JAVA_HOME=/usr/java/jre1.8.0_65
PATH=$PATH:$HOME/bin:$JAVA_HOME/jre/bin
Source side:
GGSCI (cwogg) 6 > view params. / GLOBALS
GGSCHEMA ogg
ENABLEMONITORAGENT
Target end
GGSCI (ogg1) 3 > view params. / GLOBALS
GGSCHEMA ogg
CHECKPOINTTABLE ogg.CKPT_TABLE
ENABLEMONITORAGENT
# cd / u01/ogg
Edit Config.properties and modify the following items:
Source database:
Vim / u01/ogg/cfg/Config.properties
Jagent.host=172.16.30.227
Monitor.host=172.16.30.228
Monitor.jmx.username=jmxuser
Target Library:
Vim / u01/ogg/cfg/Config.properties
Jagent.host=172.16.30.226
Monitor.host=172.16.30.228
Monitor.jmx.username=jmxuser
Configure ogg wallet
Source-side configuration
[oracle@cwogg ogg] $. / 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. Password 123123, where the password is the same as the JMX password set during installation.
Destination side configuration:
[oracle@ogg1 ogg] $. / 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.
Start the destination JAGETN:
GGSCI (ogg1) 2 > start JAGENT
GGCMD JAGENT started
GGSCI (ogg1) 3 > info all
Program Status Group Lag at Chkpt Time Since Chkpt
MANAGER RUNNING
JAGENT RUNNING
REPLICAT RUNNING REP1 00:00:00 00:00:02
GGSCI (ogg1) 4 > view report JAGENT
*
Oracle GoldenGate Command Tool for Oracle
Version 11.2.1.0.1 OGGCORE_11.2.1.0.1_PLATFORMS_120423.0230
Linux, x64, 64bit (optimized) on Apr 23 2012 04:41:46
Copyright (C) 1995, 2012, Oracle and/or its affiliates. All rights reserved.
Starting at 2015-10-28 10:15:23
*
Operating System Version:
Linux
Version # 1 SMP Wed Feb 22 17:37:40 EST 2012, Release 2.6.32-300.10.1.el5uek
Node: ogg1
Machine: x86_64
Soft limit hard limit
Address Space Size: unlimited unlimited
Heap Size: unlimited unlimited
File Size: unlimited unlimited
CPU Time: unlimited unlimited
Process id: 13462
Parameters...
COMMAND java-jar-Xms64m-Xmx512m dirjar/jagent.jar
Program is' java', arguments are'- jar-Xms64m-Xmx512m dirjar/jagent.jar'
*
* * Run Time Messages * *
*
2015-10-28 10:15:23 INFO OGG-00978 GGCMD JAGENT is running.
2015-10-28 10:15:23 INFO OGG-01927 Child process started, process ID 13466, command line 'java-jar-Xms64m-Xmx512m dirjar/jage
Nt.jar'
Start JAGENT on the source side:
GGSCI (cwogg) 2 > start JAGENT
GGCMD JAGENT started
GGSCI (cwogg) 3 > info all
Program Status Group Lag at Chkpt Time Since Chkpt
MANAGER RUNNING
JAGENT RUNNING
EXTRACT RUNNING EXT1 00:00:00 00:00:05
GGSCI (cwogg) 4 > view report JAGENT
*
Oracle GoldenGate Command Tool for Oracle
Version 11.2.1.0.1 OGGCORE_11.2.1.0.1_PLATFORMS_120423.0230
Linux, x64, 64bit (optimized) on Apr 23 2012 04:41:46
Copyright (C) 1995, 2012, Oracle and/or its affiliates. All rights reserved.
Starting at 2015-10-28 10:16:58
*
Operating System Version:
Linux
Version # 1 SMP Wed Feb 22 17:37:40 EST 2012, Release 2.6.32-300.10.1.el5uek
Node: cwogg
Machine: x86_64
Soft limit hard limit
Address Space Size: unlimited unlimited
Heap Size: unlimited unlimited
File Size: unlimited unlimited
CPU Time: unlimited unlimited
Process id: 26094
Parameters...
COMMAND java-jar-Xms64m-Xmx512m dirjar/jagent.jar
Program is' java', arguments are'- jar-Xms64m-Xmx512m dirjar/jagent.jar'
*
* * Run Time Messages * *
*
2015-10-28 10:16:58 INFO OGG-00978 GGCMD JAGENT is running.
2015-10-28 10:16:58 INFO OGG-01927 Child process started, process ID 26114, command line 'java-jar-Xms64m-Xmx512m
Dirjar/jagent.jar'.
After completion, it is found that it does not appear on the interface:
The jagent.log error is as follows:
2015-10-28 11:21:22 [main] INFO JAgentWSMain-About to call initialize on the WebService
2015-10-28 11:21:22 [main] INFO AgentInfoImpl-Using IP address 172.16.30.226 to connect to the Manager Web Service
2015-10-28 11:21:22 [main] INFO AgentInfoImpl-Reading Manager port 7500 from mgr.prm file.
2015-10-28 11:21:23 [main] INFO ManagerFacadeImpl-Metadata initialized
2015-10-28 11:21:23 [main] INFO JAgentDigestMD5JmxFactory-Starting JMX connector server on port 5555
2015-10-28 11:21:23 [main] INFO JAgentWSMain-JAgent finished initialization.
2015-10-28 11:21:23 [ManagerConnectionKeeper] INFO ManagerWSApi-Created WSAPI
2015-10-28 11:21:28 [getInstanceList] ERROR ManagerWSAdapter-com.goldengate.monitor.model.AgentCommunicationException: Failed to get Registry.
2015-10-28 11:21:28 [getInstanceList] ERROR ManagerFacadeImpl-InstanceList returned from JNI call is null
2015-10-28 11:21:28 [getInstanceList] ERROR MBeansContainerImpl-Unexpected behavior, no agent object found! JAgent will exit!
2015-10-28 11:21:28 [getInstanceList] INFO MBeansContainerImpl-Jagent Mode: Monitor-Integrated
2015-10-28 11:21:28 [main] WARN JAgentWSMain-No Agent Mbean found, exit with error code 1
2015-10-28 11:21:28 [main] INFO JAgentWSMain-JAgentWSMain is about to terminate its operation
2015-10-28 11:21:28 [agentRegistration] WARN MBeansContainerImpl-AgentMBean is null
For version 11.2.1 of Jagent, you need to create a local datastore under OGG on the server where the monitoring agent is deployed. Otherwise, even if you prompt jagent to start successfully in ggsci and the status is running after starting Jagent, the HOST is not added to the monitoring in the server-side WEB interface, and an error similar to the above will be reported in the jagent.log under the ogg installation directory:
The reason for this problem is that the agent side does not establish a local datastore, but creates a datastore on the agent side.
GGSCI (ogg1) 2 > create datastore
Datastore created
GGSCI (ogg1) 3 > stop jagent
JAgent process is required by other GGS processes.
Are you sure you want to stop it (YBO)? Y
Sending STOP request to GGCMD JAGENT...
Request processed.
JAgent stopped.
GGSCI (ogg1) 7 > start JAGENT
GGCMD JAGENT started
GGSCI (ogg1) 8 > info all
Program Status Group Lag at Chkpt Time Since Chkpt
MANAGER RUNNING
JAGENT RUNNING
REPLICAT RUNNING REP1 00:00:00 00:00:10
The web monitoring page will show:
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.