3.7 Installing Oracle GoldenGate Veridata C-Agent
This chapter includes the following sections:
3.7.1 Installation Overview
These instructions are for installing a new, clean copy of the C-based Oracle GoldenGate Veridata Agent software.
The Oracle GoldenGate Veridata C-agent is installed on the same system that hosts the database that contains compare data. You will install one Oracle GoldenGate Veridata C-Agent for each database instance where there is data that is to be compared.
Parent topic: Installing Oracle GoldenGate Veridata C-Agent
3.7.2 Installing the C-Agent on a NonStop System
To install the agent on a NonStop SQL/MP system, the following steps are required:
-
Install the Oracle GoldenGate Veridata Agent files.
-
Copy
VSNSERVto remote nodes if they contain table partitions. -
Create a
GLOBALSparameter file that contains specifications for:-
Locations of remote nodes where there is a
VSNSERVprocess. -
A unique Manager name (if other Manager processes exist on the system)
-
-
Configure the Manager process.
-
(Optional) Add the following parameter that will rollover report files after the specified increment
VERIDATAREPORTAGE <nnn> [time units]Time units are, one of:
DAY(s), HOUR(S), MINUTE(s), or SECOND(s)
For example:
VERIDATAREPORTAGE 1 DAY
- Installing the Oracle GoldenGate Veridata Agent Files
- Copying VSNSERV to Remote Nodes
- Creating a GLOBALS File
- Configuring Manager
Parent topic: Installing Oracle GoldenGate Veridata C-Agent
3.7.2.1 Installing the Oracle GoldenGate Veridata Agent Files
Parent topic: Installing the C-Agent on a NonStop System
3.7.2.2 Copying VSNSERV to Remote Nodes
If your tables have partitions on remote nodes, you will need to place a copy of the VSNSERV module on each of those nodes.
If all of the remote nodes are the same hardware type, you can use a copy of the VSNSERV that is in the Oracle GoldenGate Veridata agent subvolume. Otherwise, you might need to download the correct agent build for that hardware type. It will include the correct VSNSERV.
To place the VSNSERV on each node, you can do either of the following:
-
Install the entire Oracle GoldenGate Veridata Agent package on each of the remote nodes, even though the agent itself will not be running on them.
-
Copy the
VSNSERVobject to each of the remote nodes. To use this option, take the following steps.
To copy VSNSERV to remote nodes:
- Copy the appropriate
VSNSERVprogram to each of the remote nodes. - Log onto each remote node as a super user.
- Issue the following commands on each remote
node:
FUP GIVE vsnserv, SUPER.SUPER FUP secure vsnserv, "NNNN", PROGID FUP license <volume>.<subvolume>.VSNSERV
-
The first command sets the
VSNSERVowner asSUPER.SUPER. -
The second command sets security and
PROGIDto run asSUPER.SUPER.
-
- Specify the location of
VSNSERVon each remote node by adding aHOSTparameter for the node in theGLOBALSfile that resides in the Oracle GoldenGate Veridata Agent installation directory. See Creating a GLOBALS File.
Parent topic: Installing the C-Agent on a NonStop System
3.7.2.3 Creating a GLOBALS File
You need to create a GLOBALS file in the Oracle GoldenGate Veridata Agent directory if:
-
Other Manager processes exist on this system, such as the one used by Oracle GoldenGate data synchronization software. A unique name for each Manager process must be specified in this file with the
GGSPREFIXparameter, including the one that will be used by the Veridata agent. -
Partitions for tables that will be compared with Veridata are stored on remote nodes. The name of each node must be specified with the
HOSTparameter in theGLOBALSfile.
To create a GLOBALS file:
Parent topic: Installing the C-Agent on a NonStop System