Relevant log files for replication - Precisely Data Integrity Suite

1. Retrieve diagnostic bundles.
2. Gather these logs and artifacts at the project/model level.
   • Listener logs(kernel/<HostName>*.log): One set per listener/host. Rolls over at 10 MB by default, up to 10 files. Listener status. Summary of alerts across all models running on the listener. Needed to resolve host-wide/cross-project issues, resolve design-time issues, understand general environment, troubleshoot kernel startup.
   • Kernel logs(kernel/<ModelName>*.log): One set per model/project per listener/host. Rolls over at 10 MB by default, up to 10 files. Detailed logs for kernel (one model running on one host). Needed for full resolution of replication problems - runtime database connection issues, deployment/model update issues, data correctness issues, understanding of data volumes and performance.
   • Change Selector/Log Reader logs: One set per Change Selector/Log Reader. Detailed logs for the capture mechanism. Needed for full resolution of transaction log capture issues, other system issues on the database source host, e.g. IBM i journaling, permissions accessing the transaction logs, etc. For non-DB2 sources, these are part of the kernel log, or are outside of the product (e.g. SQL Server agent).
3. Contact Support if necessary.