4 Installing Oracle GoldenGate Veridata C-Agent

4.3.1 Installing the Oracle GoldenGate Veridata Agent Files

1. Create a directory for the agent.

2. Follow the steps in Appendix A, "Downloading Oracle GoldenGate Veridata" to obtain the software.

3. Using WinZip or an equivalent compression product, extract the files from the mediapack.zip file to the directory that you created, and make certain to preserve folder names. The extraction creates the installation directory and a subdirectory named agent that contains the software files.

4. From the agent subdirectory, run GGSCI.

5. In GGSCI, issue the following command to create the working directories for the agent.

   CREATE SUBDIRS
   

6. If you will be installing the Manager as a Windows service and there are other local Manager services, continue with the following steps to specify a custom Manager name. Otherwise, skip that section and follow the instructions for installing Manager as a service on Section 4.3.3, "Installing Manager as a Windows service".

4.3.2 Specifying a Custom Manager Name

You must specify a custom name for the Manager process if either of the following is true:

• you want to use a name for Manager other than the default of GGSMGR.

• there will be multiple Manager processes running as Windows services on this system, such as one for the Oracle GoldenGate replication software and one for Oracle GoldenGate Veridata. Each Manager on a system must have a unique name. Before proceeding further, verify the names of any local Manager services.

To specify a custom Manager name

1. From the directory that contains the Manager program, run GGSCI.

2. Issue the following command.

   EDIT PARAMS ./GLOBALS
   

3. In the file, add the following line, where name is a one-word name for the Manager service.

   MGRSERVNAME name
   

4. Save the file. The file is saved automatically with the name GLOBALS, without a file extension. Do not move this file. It is referenced during installation of the Windows service and during data processing.

4.3.3 Installing Manager as a Windows service

By default, Manager is not installed as a service and can be run by a local or domain account. However, when run this way, Manager will stop when the user logs out. When you install Manager as a service, you can operate it independently of user connections, and you can configure it to start manually or at system start-up.

To install Manager as a Windows service

1. (Recommended) Log on as the system administrator.

2. Click Start, then Run, and type cmd in the Run dialog box.

3. From the directory that contains the Manager program that you are installing as a service, run the INSTALL program with the following syntax:

   install option [...]
   

   Where:

   option is one of the following:

   Table 4-1 INSTALL options

   Option	Description
   ADDEVENTS	Adds Oracle GoldenGate events to the Windows Event Manager. By default, Oracle GoldenGate errors are generic. To produce more specific error content, copy the following files from the Oracle GoldenGate installation directory to the SYSTEM32 directory. category.dll ggsmsg.dll
   ADDSERVICE	Adds Manager as a service by the name specified in the GLOBALS file, if one exists, or by the default of GGSMGR. ADDSERVICE configures the service to run as the Local System account, the standard for most Windows applications because the service can be run independently of user logins and password changes. To run Manager as a specific account, use the USER and PASSWORD options.Foot 1  The service is installed to start at system boot time (see AUTOSTART). To start it after installation, either reboot the system, or start the service manually from the Services applet of the Control Panel.
   AUTOSTART	Specifies that the service created with ADDSERVICE is to be started at system boot time. This is the default unless MANUALSTART is used.
   MANUALSTART	Specifies that the service created with ADDSERVICE is to be started manually through GGSCI, a script, or the Services applet of the Control Panel. The default is AUTOSTART.
   USER name	Specifies a domain user account for executing Manager. For name, include the domain name, a backward slash, and the user name, for example HEADQT\GGSMGR. By default, the Manager service is installed to use the Local System account.
   PASSWORD password	Specifies the password for the user specified with USER.

   
   

   ^Footnote 1  A user account can be changed by selecting the Properties action from the Services applet of the Windows Control Panel.

4. (Windows Server 2008) If Windows User Account Control (UAC) is enabled, you are prompted to allow or deny the program access to the computer. Click Allow to enable the INSTALL program to run. This installs the Manager service with a local system account running with administrator privileges. No further UAC prompts will be encountered when running Manager if installed as a service.

   Note:

   If Manager is not installed as a service, Oracle GoldenGate users will receive a UAC prompt to confirm the elevation of privileges for Manager when it is started from the GGSCI command prompt. Running other Oracle GoldenGate programs also will trigger a prompt

4.3.4 Configuring Manager

1. In GGSCI, issue the following command to create and edit a Manager parameter file.

   EDIT PARAMS MGR
   

2. On the first line of the file, add the following parameter to specify a port number for the Manager process. This port number must be a unique number that is not being used by any other process, including any Manager processes for other Oracle GoldenGate software.

   PORT number
   

3. (Optional) On the next line, add the following parameter to specify a range of up to 256 ports that the Manager process can allocate dynamically. This parameter can be used to specify ports for concurrent processing threads if you will be running batch comparisons.

   DYNAMICPORTLIST {port | port-port} [ , ...]
   

   Where:

   • To specify multiple ports, use a comma-delimited list, for example 7830, 7833.

   • To specify a range of ports, use a dash (-) to separate the first and last port in the range, for example 7830-7835.

   • To specify a range of ports plus an individual port, place a comma between the range and the individual port number, for example 7830-7835, 7839.

4. Save and close the parameter file. This file is stored in the dirprm subdirectory of the agent directory. Do not move it.

5. In GGSCI, start the Manager process. You can defer this step until you are ready to run comparisons. To perform comparisons, Manager must be running.

   START MANAGER
   

6. To confirm that Manager is running, issue the following command in GGSCI.

   INFO MGR
   

4.4.1 Installing the Oracle GoldenGate Veridata Agent Files

1. Follow the steps in Section A, "Downloading Oracle GoldenGate Veridata" to download the Oracle GoldenGate Veridata Agent build file to a Windows workstation.

2. Using WinZip or an equivalent compression product, unzip the files to a temporary directory on your workstation.

3. Transfer the files in binary mode to the volume and subvolume on the NonStop Server where you want to install and run the agent. The agent software must be installed in a dedicated subvolume, including one that is separate from other Oracle GoldenGate software.

4. Alter the VERUNPAK to be an edit file by issuing the following TACL command.

   FUP ALTER VERUNPAK, CODE 101
   

5. Run the VERUNPAK macro by issuing the following TACL command.

   RUN VERUNPAK
   

6. At the prompt, verify the installation location. Type Y to confirm the location shown or N to select another location.

   Installing GoldenGate at $DATA.GoldenGate Veridata
   Is this correct? (Y/N) y
   UNPAK - File decompression program - T1255G06 - (2002-05-06)
   Archive version: 1
   File Mode RESTORE Program - T9074G07 (15JAN2002)
   Copyright Tandem Computers Incorporated 1981-2002
   Summary Information
   Files restored = 7  Files not restored = 0
   GoldenGate Veridata for Nonstop Installation
   Installs the GoldenGate Veridata Product
   Enter X at any prompt to quit.
   

7. You are prompted for a SQL catalog for the agent to use. Type the catalog name or type X for no catalog.

   SQL Catalog for Compilation (X for no catalog)? $data.cpscat
   SQL compiling VERIAGT
   GoldenGate Veridata Installation Complete.
   

8. Continue with Section 4.4.2, "Copying VSNSERV to Remote Nodes" and Section 4.4.3, "Creating a GLOBALS File" as necessary for your environment.

4.4.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 VSNSERV object to each of the remote nodes. To use this option, take the following steps.

To copy VSNSERV to remote nodes 

1. Copy the appropriate VSNSERV program to each of the remote nodes.

2. Log onto each remote node as a super user.

3. Issue the following commands on each remote node:

   FUP GIVE vsnserv, SUPER.SUPER
   FUP secure vsnserv, "NNNN", PROGID
   

   • The first command sets the VSNSERV owner as SUPER.SUPER.

   • The second command sets security and PROGID to run as SUPER.SUPER.

4. Specify the location of VSNSERV on each remote node by adding a HOST parameter for the node in the GLOBALS file that resides in the Oracle GoldenGate Veridata Agent installation directory. See Section 4.4.3, "Creating a GLOBALS File."

4.4.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 GGSPREFIX parameter, including the one that will be used by the Oracle GoldenGate Veridata agent.

• Partitions for tables that will be compared with Oracle GoldenGate Veridata are stored on remote nodes. The name of each node must be specified with the HOST parameter in the GLOBALS file.

To create a GLOBALS file

1. At the TACL prompt, issue the following command.

   EDIT GLOBALS
   

2. If prompted to create the file, enter Yes.

3. In the GLOBALS file, add one or both of the following parameters, depending on your environment:

   GGSPREFIX $aa
   HOST system_name [, GGSSUBVOL subvol] [, NODENUM node_number]
   [HOST system_name [, GGSSUBVOL subvol] [, NODENUM node_number]]
   

   • GGSPREFIX specifies a unique, two-character prefix that will be attached to the Manager process name, for example GGSPREFIX $GV.

   • HOST specifies the location of remote nodes where there is a VSNSERV component.

     Note:

     If you do not know the expand node number of a system, run SYSINFO on that node.

     SYSINFO - T9268H01 - (01 OCT 2004) SYSTEM \TEST Date 10 Jul 2008, 10:44:54
     Copyright 2003 Hewlett-Packard Development Company, L.P.
     
              System name    \TEST
       EXPAND node number    110
            Current SYSnn    SYS10
            System number    012345
      Software release ID    H06.13.00
     

4. Save the file without a file extension. The file is stored in the subvolume where the agent resides. Do not move it.

4.4.4 Configuring Manager

1. From TACL, run the GGSCI program that is installed with the agent.

   RUN GGSCI
   

2. In GGSCI, issue the following command to create and edit a Manager parameter file.

   EDIT PARAMS MGRPARM
   

3. On the first line of the file, add the following parameter, where number is a unique port number that is not being used by any other process, including any Manager processes for other Oracle GoldenGate software.

   PORT number
   

4. (Optional) On the next line, add the following parameter to specify a range of up to 256 ports that the Manager process can allocate dynamically. You can specify ports for concurrent processing threads if you will be running batch comparisons.

   DYNAMICPORTLIST {port | port-port} [ , ...]
   

   Where:

   • To specify multiple ports, use a comma-delimited list, for example 7830, 7833.

   • To specify a range of ports, use a dash (-) to separate the first and last port in the range, for example 7830-7835.

   • To specify a range of ports plus an individual port, place a comma between the range and the individual port number, for example 7830-7835, 7839.

5. Save and close the file.

6. In GGSCI, issue the following command to start the Manager process. You can defer this step until you are ready to run comparisons. To perform comparisons, Manager must be running.

   START MANAGER
   

7. To confirm that Manager is running, issue the following command in GGSCI.

   INFO MGR