Why does the goldengate replicat process display running without applying any records?

Sometimes, we will find that the status of the replicat process is running, but the report shows that no record is updated. There are four main reasons for this phenomenon:
1. The replicat process is reading the wrong trail record.
2. The replicat process is reading the wrong trail file.
3. The specified table name format is incorrect.
4. replicat or extract hang

In the preceding four cases, the Process status is displayed as running, but no records are copied when you view the report.
In the first case:
Execute info extract, detail, or view the rmttrail parameters in the extract parameter file.
Execute info replicat, detail, or view replicat report
The name, host, and path of the trail file being read by the replicat process must be the same as that specified in the extract process parameter.

In the second case:
Execute info replicat, detail, or view the replicat report.
Run ls-L to check the target trail file and check whether the trail file is being read. The replicat process is
The end of the trail file to be read is not linked to the next available file.

Solution: Execute alter replicat rep_name, extseqno nnnnnn, And the extrba 0 division replicat switches to the next slap file, and then restart the replicat process.
This phenomenon is usually caused by the source side performing the etrolover operation. We usually need to modify the extseqno and
Extrba can solve the problem.

If the format of the specified table name is incorrect:
Run logdump on the trail file to check whether the table name in the trail file is consistent with schema. table_name specified in the replicat process parameter.

Starting from hang:
Generally, hang may occur in extract, replicat, and Mgr processes.
Run the PS-Ef | grep proecess_name process to check whether multiple processes are running, or run the stop operation in ggsci to check whether the process is running.
It can be stopped normally. If not, we can kill process_name (which can be found in ggsci or OS) to restart the process.
Problem.

For reprint, please indicate the author's source and original article link:

Http://blog.csdn.net/xiangsir/article/details/8728747