ogg mgr不清理trail文件？

生产环境中，出现过一次，由于mgr不清理trail文件。导致文件系统爆掉。由于是在晚上，相关的文件系统告警未通知，造成后面一些小的影响。
猜测可能是遇到了这个bug。版本号也符合。暂作记录
Goldengate Manager Not Purging Trail Files (文档 ID 1460097.1)

In this Document

APPLIES TO:

Oracle GoldenGate - Version 10.4.0.0 to 11.2.1.0.3 [Release 10.4.0 to 11.2]
Information in this document applies to any platform.

SYMPTOMS

Example 

Trail files not being purged by the manager. The event parameter is correctly set as

PURGEOLDEXTRACTS ./dirdat/local/migration/jm/jm*, USECHECKPOINTS, MINKEEPDAYS 3

CAUSE

 The cause is due to local and remote trails have same full path filenames. the remote trail number is much smaller than local one, and the remote one was used to check if the local one may be purged.

Best practice is to use unique names for each trail set in the combined configuration.

 You may check the below command to summarize the trail prefixes used by different processes under this manager

GGCSI > info exttrail *

GGCSI > info rmttrail *

SOLUTION

 Solution is to make sure that all trails (Local and Remote) uses different trail prefixes all the time.

In example below, we could observe that Master extract (writing to exttrail) and Pump extract(writing to rmttrail) uses same trail file prefix

GGSCI (lgpwd514) 1> info exttrail *

Extract Trail: ./dirdat/migration/jm/jm
Extract: E_MERC
Seqno: 1194
RBA: 90081793
File Size: 100M

Extract Trail: ./dirdat/migration/jm/jm

Extract: P_MERC
Seqno: 1123
RBA: 31631582
File Size: 100M

Manager checks all checkpoint files and does not differentiate between exttrail/rmttrail so if the names are the same, the trail files are purged based on the sequence numbers of the rmttrails

 

**Note This works in both bidirectional aswell as unidirectional setup's

REFERENCES

BUG:10240388 - AUTOMATIC PURGING OF TRAIL FILES ON GOLDENGATE FAILS TO PURGE SOME TRAIL FILES