The prepare-offboard-fetcher script is used to complete the final installation steps for Section 220.127.116.11, “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
|--help, -?||Show the help text|
|--host, -h||Hostname of the Offboard host|
The method to use for retrieving config from the offboard host
Values: scp, rsync, none
See below for further explanation of the use of none
The location of the config on the offboard host
|--service, -s||The service name defined during installation on the offboard host|
The full path the local TNS_ADMIN directory
Is the host a RAC Node
Values: true, false
|--sid, -d||SID of the ASM Instance for RAC, only required if rac=true|
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
To copy the files manually, you need to locate the
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
/opt/continuent/plog/alpha from offboard
/opt/continuent/plog on DBHost
Execute prepare script as follows specifying --method none and --path /opt/continuent/plog
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
tar zxvf orarr-2.9.06-aix.o12.tar.gzshell>
path-to-local-tns--service alpha --bin /tmp/orarr
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.
path-to-local-tns--service alpha --rac true --sid "+ASM1"
path-to-local-tns--service alpha --rac true --sid "+ASM2"