5.1.8. Using the prepare-offboard-fetcher script

The prepare-offboard-fetcher script is used to complete the final installation steps for Section 5.2.3.1, “Deploying Offboard with FETCHER” and Section 5.2.4, “Deploying on Oracle RAC”. The script will copy across the configuration for the FETCHER from the offboard host. This will have been prepared during the installation via the tpm command on the offboard host, therefore that step must be completed first.

Options for the prepare-offboard-fetcher script are as follows

Option Description
--help, -? Show the help text
--host, -h Hostname of the Offboard host
--method, -m

The method to use for retrieving config from the offboard host

Values: scp, rsync, none

Default: rsync

See below for further explanation of the use of none

--path, -p

The location of the config on the offboard host

Default: /opt/continuent/plog

--service, -s The service name defined during installation on the offboard host
--tns, -t

The full path the local TNS_ADMIN directory

Default: $ORACLE_HOME/network/admin

--rac, -r

Is the host a RAC Node

Values: true, false

Default: false

--sid, -d SID of the ASM Instance for RAC, only required if rac=true
--bin, -b

The Path to the extracted Redo-Reader binaries

This should be used when the target OS for the FETCHER is not the default Linux (RHEL, CentOS, Oracle linux) OS

Supported OS types: Solaris, AIX, HP-UX, RHEL, CentOS, Oracle Linux, Suse10

The script will use scp or rsync to retrieve files from the offboard host, therefore ssh access will need to be available between hosts. If your environment does not allow this, you will need to copy these files manually, and then execute the prepare script using option --method none and ensuring --path points to the local location that you copied the files to.

To copy the files manually, you need to locate the ./plog/servicename directory on the offboard host and copy it and its contents to the DBHost. The plog directory, by default will be in /opt/continuent, or whichever location you specified via the --install-directory tpm parameter.

For example, if the servicename was alpha, and install-directory was /opt/continuent:

  • Copy /opt/continuent/plog/alpha from offboard host to /opt/continuent/plog on DBHost

  • Execute prepare script as follows specifying --method none and --path /opt/continuent/plog

5.1.8.1. Running on a non-Linux host

If your FETCHER is on an OS other than a Linux variant, for example AIX, Solaris or HP-UX then you will also need to obtain the Oracle Redo Reader binaries appropriate for this OS.

This package will be supplied to you by a Continuent Engineer during deployment. By default the replicator packages are bundled with Oracle Redo Reader binaries for Linux (RHEL, CentOS, Oracle Linux) therefore this step can be skipped if your DBHost is also running the same OS.

Copy the provided package into a temporary location on the OffBoard host, uncompress and extract it, you then need supply the full path to these files as the --bin parameter

The worked example below shows the AIX package being used

shell> cd tmp
shell> tar zxvf orarr-2.9.06-aix.o12.tar.gz
shell> cd <prepare-script-location>
shell> ./prepare-offboard-fetcher --host offboardhost \
  --tns path-to-local-tns --service alpha --bin /tmp/orarr

5.1.8.2. Running on a RAC host

When setting up a RAC Node, you need to ensure you supply additional parameters to the prepare script. You also need to run the prepare script on ALL nodes in the RAC cluster.

An example below shows the script being executed on two different RAC Nodes.

racnode1-shell> ./prepare-offboard-fetcher --host offboardhost \
  --tns path-to-local-tns --service alpha --rac true --sid "+ASM1"
racnode2-shell> ./prepare-offboard-fetcher --host offboardhost \
  --tns path-to-local-tns --service alpha --rac true --sid "+ASM2"