7
Installing and Configuring GoldenGate Veridata Agent The GoldenGate Veridata Agents execute the database related requests to compare source and target database rows on behalf of the Veridata Server. At a minimum we need to install two agents – one to retrieve source rows and one to retrieve target rows from the database. There are two types of agents – one is the Java based agent and the other is the C-Agent. The Java Agent connects to the database using JDBC and permits data comparisons in heterogeneous environments. A Java environment JRE/JSDK is required to support this agent and a minimum java version is 1.5 We have copied the V19618-01.zip file from the Metalink E-Deilvery site and unzipped it as shown below. dba1:/u01/ofsad2> mkdir veriagent dba1:/u01/ofsad2> mv V19618-01.zip ./veriagentdba1:/u01/ofsad2> cd veriagent dba1:/u01/ofsad2/veriagent> ls V19618-01.zip dba1:/u01/ofsad2/veriagent> unzip * Archive: V19618-01.zip creating: agent/ creating: agent/classes/ creating: agent/drivers/ creating: agent/lib/ creating: agent/licenses/

Veridata Config

Embed Size (px)

DESCRIPTION

Veridata Config guide

Citation preview

Page 1: Veridata Config

Installing and Configuring GoldenGate Veridata Agent

The GoldenGate Veridata Agents execute the database related requests to compare source and target database rows on behalf of the Veridata Server.

At a minimum we need to install two agents – one to retrieve source rows and one to retrieve target rows from the database.

There are two types of agents – one is the Java based agent and the other is the C-Agent.

The Java Agent connects to the database using JDBC and permits data comparisons in heterogeneous environments. A Java environment JRE/JSDK is required to support this agent and a minimum java version is 1.5

We have copied the V19618-01.zip file from the Metalink E-Deilvery site and unzipped it as shown below.

dba1:/u01/ofsad2> mkdir veriagentdba1:/u01/ofsad2> mv V19618-01.zip ./veriagentdba1:/u01/ofsad2> cd veriagentdba1:/u01/ofsad2/veriagent> lsV19618-01.zipdba1:/u01/ofsad2/veriagent> unzip *Archive: V19618-01.zipcreating: agent/creating: agent/classes/creating: agent/drivers/creating: agent/lib/creating: agent/licenses/inflating: agent/JavaAgent.jarinflating: agent/agent.batinflating: agent/agent.properties.sampleinflating: agent/classes/log4j.propertiesinflating: agent/drivers/gvdb2.jarinflating: agent/drivers/ojdbc5.jarinflating: agent/drivers/sqljdbc.jarinflating: agent/lib/commons-dbcp-1.2.2.jar

Page 2: Veridata Config

inflating: agent/lib/commons-pool-1.3.jarinflating: agent/lib/log4j-1.2.12.jarinflating: agent/licenses/Apache-LICENSE-2.0.txtinflating: agent/licenses/notices.txtinflating: agent/agent.sh

We then need to copy the agents.properties.sample file and create a file called agents.properties as shown below. Here we are providing the port where the agent will run as well as database connection information like the listener port and SID of the database.

dba1:/u01/ofsad2/veriagent/agent> cp agent.properties.sample agent.properties

# The server.port property is the port where the Veridata agent listens# for connection requests.server.port=4000# Oracle sample database connection URL^Mdatabase.url=jdbc:oracle:thin:@redhat346:1522:gavinserver.driversLocation = driversserver.jdbcDriver=ojdbc5.jardatabase.transaction.isolation=READ_COMMITTED

[oracle@redhat346 agent]$ export JRE_HOME=/u01/oracle/jre1.6.0_18[oracle@redhat346 agent]$ ./agent.sh start

Installing the C Agent

We first download the file V18202-01.zip from the E-Delivery web site and unpack as shown below. We then will launch the GoldenGate Command Interpretor (GGSCI) from the Veridata Agent directory location. We create the sub directories for the agent and configure a manager process for the Veridata Agent – not to be confused with the Manager process that we configured at the very beginning of the GoldenGate installation.

dba1:/u01/ofsad2/veriagent> unzip V18202-01.zipArchive: V18202-01.zipinflating: ggs_veridataAgent_aix53_ppc_ora102_64bit_v3.0.0.2_001.tar

Page 3: Veridata Config

dba1:/u01/ofsad2/veriagent> tar -xvf ggs_veridataAgent_aix53_ppc_ora102_64bit_v3.0.0.2_001.tarx veridatax veridata/agentx veridata/agent/mgr, 1848763 bytes, 3611 tape blocksx veridata/agent/ggsci, 2283442 bytes, 4460 tape blocksx veridata/agent/ggMessage.dat, 393280 bytes, 769 tape blocksx veridata/agent/help.txt, 117942 bytes, 231 tape blocksx veridata/agent/bcrypt.txt, 1725 bytes, 4 tape blocksx veridata/agent/libxml2.txt, 1668 bytes, 4 tape blocksx veridata/agent/zlib.txt, 1476 bytes, 3 tape blocksx veridata/agent/freeBSD.txt, 1968 bytes, 4 tape blocksx veridata/agent/notices.txt, 176571 bytes, 345 tape blocksx veridata/agent/libicui18n38.a, 9302329 bytes, 18169 tape blocksx veridata/agent/libicuuc38.a, 6302602 bytes, 12310 tape blocksx veridata/agent/libicudata38.a, 11360230 bytes, 22188 tape blocksx veridata/agent/veriagt, 4438543 bytes, 8670 tape blocks

dba1:/u01/ofsad2/veriagent> cd veridatadba1:/u01/ofsad2/veriagent/veridata> lsagentdba1:/u01/ofsad2/veriagent/veridata> cd agentdba1:/u01/ofsad2/veriagent/veridata/agent> lsbcrypt.txt ggMessage.dat help.txt libicui18n38.a libxml2.txt notices.txt zlib.txtfreeBSD.txt ggsci libicudata38.a libicuuc38.a mgr veriagt

dba1:/u01/ofsad2/veriagent/veridata/agent> ./ggsci

Oracle GoldenGate Command Interpreter for OracleVersion 10.4.0.19 Build 003AIX 5L, ppc, 64bit (optimized), Oracle 10 on Sep 21 2009 00:19:47

Copyright (C) 1995, 2009, Oracle and/or its affiliates. All rights reserved.

GGSCI (devu026) 1>

GGSCI (devu026) 1> create subdirs

Page 4: Veridata Config

Creating subdirectories under current directory /u01/ofsad2/veriagent/veridata/agent

Parameter files /u01/ofsad2/veriagent/veridata/agent/dirprm: createdReport files /u01/ofsad2/veriagent/veridata/agent/dirrpt: createdCheckpoint files /u01/ofsad2/veriagent/veridata/agent/dirchk: createdProcess status files /u01/ofsad2/veriagent/veridata/agent/dirpcs: createdSQL script files /u01/ofsad2/veriagent/veridata/agent/dirsql: createdDatabase definitions files /u01/ofsad2/veriagent/veridata/agent/dirdef: createdExtract data files /u01/ofsad2/veriagent/veridata/agent/dirdat: createdTemporary files /u01/ofsad2/veriagent/veridata/agent/dirtmp: createdVeridata files /u01/ofsad2/veriagent/veridata/agent/dirver: createdVeridata Lock files /u01/ofsad2/veriagent/veridata/agent/dirver/lock: createdVeridata Out-Of-Sync files /u01/ofsad2/veriagent/veridata/agent/dirver/oos: createdVeridata Out-Of-Sync XML files /u01/ofsad2/veriagent/veridata/agent/dirver/oosxml: createdVeridata Parameter files /u01/ofsad2/veriagent/veridata/agent/dirver/params: createdVeridata Report files /u01/ofsad2/veriagent/veridata/agent/dirver/report: createdVeridata Status files /u01/ofsad2/veriagent/veridata/agent/dirver/status: createdVeridata Trace files /u01/ofsad2/veriagent/veridata/agent/dirver/trace: createdStdout files /u01/ofsad2/veriagent/veridata/agent/dirout: created

GGSCI (devu026) 2> edit params mgr

“/u01/ofsad2/veriagent/veridata/agent/dirprm/mgr.prm” [New file]PORT 7807~

GGSCI (devu026) 3> start manager

Manager started.

GGSCI (devu026) 4> info manager

Page 5: Veridata Config

Manager is running (IP port devu026.7807).