You must initialize the Datareplicators when you start data linkage for the first time after you have set the Datareplicator configuration.

The following figure shows the general procedure.

Figure 6-3 Initialization procedure at the environment configuration stage

Note:

You must start the target database to perform the steps beginning with step 6 below.

The initialization procedure at the environment configuration stage shown in the figure is explained below. The numbers correspond to the numbers in the figure.

1. Create the following Datareplicator definition files:
   
   • Extraction system definition file
   • Transmission environment definition file
   • Extraction environment definition file
   • Extraction definition file
   • Duplexing definition file (for the source Datareplicator) (optional)
   • Import system definition file
   • Import environment definition file
   • Import definition file
   • Duplexing definition file (for the target Datareplicator) (optional)
2. Terminate the source HiRDB.
   

   No.	Task	Execution command	Check item
   1	Terminate the source HiRDB normally.	pdstop	Check that the KFPS01850-I message has been output to the syslog file (to the event log in Windows).

   Note:

   If the HiRDB is not terminated normally, changes to HiRDB definition files will not take effect.

3. Modify the source HiRDB's definition files listed below.
   For details, see 5.6 Source HiRDB definition.
   
   • pd_rpl_init_start in the system common definition
     (We recommend that you specify Y in the pd_rpl_init_start operand.)
     
   • pd_log_rpl_no_standby_file_opr in the system common definition
   • pd_rpl_hdepath in the unit control information definition
4. Initialize the source system.
   

   No.	Task	Execution command	Check item
   1	Initialize the source Datareplicator.	hdestart -i (Enter Y in the response message)	Check that the KFRB00504-I message has been output to msterrfile1 or msterrfile2. If the KFRB00504-I message has not been output or msterrfile1 and msterrfile2 have not been created, a definition analysis error might have occurred or file creation might have failed. Determine the nature of the error by referencing the syslog file (event log in Windows), take appropriate action, and then re-initialize the source Datareplicator.

5. Start the source HiRDB.
   Once you have started the source HiRDB, do not perform any updating application on the source database until you have completed step 8.
   

   No.	Task	Execution command	Check item
   1	Start the source HiRDB.	pdstart	Check that the KFPS05210-I message has been output to the syslog file (event log in Windows).
   2	Start HiRDB Datareplicator linkage. Perform this task if nothing or N is specified in the pd_rpl_init_start operand in HiRDB's system common definition.	pdrplstart	Check that the KFPS05140-I message has been output to the standard output.
   3	Verify that HiRDB is ready for data linkage with Datareplicator.	pdls -d rpl -j	Check the displayed results.#

   #

   As shown in the example below, verify that (1) and (2) are both Y in the displayed results. Also verify that Gen No and Block No indicated as (3) and (4), respectively, are not 0.

   

6. Synchronize data in the source and target databases.
   You synchronize the data in the source and target databases by using a program such as HiRDB Datareplicator to copy data from a source table to a target table in the batch mode (initial data creation).
   
7. Create the extraction definition preprocessing file.
   

   No.	Task	Execution command	Check item
   1	Create the extraction definition preprocessing file.	hdeprep -f extraction-definition-file	Check that the KFRB04500-I message has been output to the standard output.

   Note:

   Specify options in the hdeprep command as necessary.

8. Initialize the target Datareplicator.
   

   No.	Task	Execution command	Check item
   1	Initialize the target Datareplicator.	hdsstart -i -f -q	Check that the KFRB04216-I message has been output to the standard output (Event Viewer in Windows). If the KFRB04216-I message has not been output, a definition analysis error might have occurred or file creation might have failed. Determine the nature of the error by referencing the standard output (Event Viewer in Windows), take appropriate action, and then re-initialize the target Datareplicator.

   Note:

   When you initialize the target Datareplicator for the first time, we recommend that you execute the hdsstart command with the -f option specified. You can also specify other options as necessary.

9. Start the source and target Datareplicators.
   

   No.	Task	Execution command	Check item
   1	Start the target Datareplicator.	hdsstart	Check that the KFRB00100-I message has been output to errfile1 or errfile2.
   2	Start the source Datareplicator.	hdestart#	Check that the KFRB00502-I message has been output to msterrfile1 or msterrfile2.

   #

   Specify options in the hdestart command as necessary.

When using the import transaction synchronization facility

If you will be using the import transaction synchronization facility, after you have finished steps 1 through 9, execute a synchronous event to activate all processes in the target Datareplicator's synchronous import group.

No.	Task	Execution command	Check item
1	Execute a synchronous event.	hdeevent# -n synchronous-event-code	Check that no messages have been output to the standard error output. Check that the KFRB03009-I message has been output to the target system's error information file and that reason is SYNC EVENT.

#

Specify options in the hdeevent command as necessary.