Follow these steps to define and manage a new replication pipeline.
Note: The replication pipeline uses the DB2 z/OS to Oracle sample scenario with <ENGINE_NAME>=DB2ZTOORACLE but you must replace that with your own unique name.
- Select a unique apply <engine_name> that should also be used as the jobname in the job script file and the subdirectory path in the instance as shown in the following steps for DB2ZTOORACLE.
- Create the apply engine directories in $SQDATA_VAR_DIR/apply/<ENGINE_NAME>. For example,
connect> mkdir -p $SQDATA_VAR_DIR/apply/DB2ZTOORACLE/ddl connect> mkdir -p $SQDATA_VAR_DIR/apply/DB2ZTOORACLE/scripts
- Upload, create or edit the job script <engine_name>.sqd. For example,
connect> vi $SQDATA_VAR_DIR/apply/DB2ZTOORACLE/scripts/db2ztooracle.sqd
Note:- Sample job scripts are provided in $SQDATA_VAR_DIR/templates/*.sqd.
- Sample schemas are provided in $SQDATA_VAR_DIR/templates/*.ddl
- Add <ENGINE_NAME> stanza to sqdagents.cfg. For example,
> vi $SQDATA_DAEMON_DIR/cfg/sqdagents.cfg
Note: See sample stanzas in $SQDATA_VAR_DIR/templates/sqdagents.cfg. - Once the above is added to sqdagents.cfg section, reload sqdmon for changes to take effect.
> sqdmon reload
The above should be done whenever a new replication task (apply engine script) is being added or modified.
- Consider setting auto_start=1 to have the engine automatically started in case of a system restart.