Cloning processing example
An example of a cloning configuration file, showing the production database named
P01, and the clone database named C01.
./fcmcli -f preproc_clone -u oraclec01 -C C01 -X /oracle/C01/acs/preprocessing.ini
./fcmcli -f postproc_clone -u oraclec01 -C C01 -Y /oracle/C01/acs/postprocessing.ini
If a processing script needs extra command-line options, add these options to each line of the
configuration file. In this example, the additional command-line argument LC01
is added to the script entry in the configuration
file:/oracle/C01/acs/scripts/PostProcessing_startListener.sh LC01The
IBM® Storage Protect
Snapshot command-line interface issues a
call to the processing script with the six default arguments. After these arguments are provided,
extra command-line options are sent. In this example, the additional command-line argument
LC01 is passed to the PostProcessing_startListener.sh script as
the seventh argument:
#!/bin/ksh
# FOLLOWING ACTIONS ARE PERFORMED ---------------------------------------------
# start the Oracle Listener
DBNAME_PROD=$1
DBNAME_CLONE=$2
DBHOST_PROD=$3
DBHOST_CLONE=$4
CLONE_TIMESTAMP=$5
# ${SCHEMA} is schema owner (for SAP Kernel > 6.10, for userid other than SAPR3)
SCHEMA=$6
SCHEMA=$(echo ${SCHEMA} | tr [a-z] [A-Z])
# ${LISTENER} is the name of the listener to be started (taken from listener.ora)
LISTENER=$7
lsnrctl start ${LISTENER}