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
