This document covers the following topics:
If replicate files are not being updated with master file changes, the cause could be the failure of ETP to log the master file changes in the log file.
If you look at the log file entries (use the Display Transactions function of the ETP maintenance utility) and find that there are no entries in the log file, the cause could be either one of the following:
Master file not correctly defined;
ETP NATPARM
parameters or Natural start up parameters
not correctly specified.
First, check the master file definition (with the maintenance utility's Display Master File Definition function) to ensure that the file has been correctly defined.
If it has, then specific installation parameters should be checked.
The figure below shows the sequence for correcting the logging problem:
NTDB ADAV7,<dbid>,ETP in
NATPARM module or DB=(ADAV7,<dbid>,ETP)
dynamically specified?
|
If no transactions have been replicated but the log file is not empty, check the replicate file definitions.