【翻译自mos文章】OGG Director 不会purge log table

OGG Director 不会purge log table。

来源于：OGG Director does not Purge Log Table (文档 ID 1637931.1)

适用于：
Management Pack for Oracle GoldenGate - Version 12.1.2.0.1 and later
Information in this document applies to any platform.

症状：
Purge rule 被设置为1 小时的默认值，但是purge table 并没有发生。

SQL>select to_char(min(sourcetimestamp),'yyyy-mm-dd hh24:mi:ss') from gguser.logentryb;

TO_CHAR(MIN(SOURCET
-------------------
2012-05-29 19:33:43   ------------------>>>>>此时间是ogg的部署时间（不是ogg director的部署时间）

SQL>select to_char(min(inserttimestamp),'yyyy-mm-dd hh24:mi:ss') from gguser.logentryb;

TO_CHAR(MIN(SOURCET
-------------------
2014-02-26 23:04:09   ------------------>>>>>此时间是ogg director的部署时间（不是ogg的部署时间）

SQL>select to_char(sysdate,'yyyy-mm-dd hh24:mi:ss') from dual;

TO_CHAR(SYSDATE,'YY
-------------------
2014-03-14 13:48:06   ------------------>>>>>此时间是ogg director所在的os的时间。

原因：

在Admin tool 中，"Log Purge Hours" 被设置为72小时，我们怀疑有些 repository  tables 有corrupted row，或者他们太多的行。

解决方案：

1. Logon to the Director Admin Tool, click on the Monitor Agent tab. Make sure value of Go Back Hours is 0, the default.
2. Logon to the Director Admin Tool, click on the Monitor Agent tab. The default for "Log Purge Hours" is 72 hours. Please
reduce it to your interested retention period
3. Stop the Director server
4. On the OGG instances being monitored

os> cd 
os> cp ggserr.log ggserr.log.bak
os> cat /dev/null > ggserr.log

5. truncate the logentryb, statentryb tables directly from the DB. If needed you could take a export dump before truncating
6. Restart Director server