[翻譯自MOS文章]怎麼在OGG 12c版本中把replicat程序重新定位到之前的trail檔案位置上?

翻譯本文時,是中國農曆新年的大年初一(2017.01.28),已經放了好幾天假了,也好幾天不上MOS了,感覺心裡不踏實,猶如電影"核艇風暴"中阿拉巴馬号艇長Ramsey在潛艇下潛之前,在潛艇艦橋(潛艇圍殼)上抽着雪茄對副艇長Hunter說:"沒有雪茄的空氣是不真實的",我覺得每天不登入MOS也是不真實的.

适用于:

Oracle GoldenGate - Version 12.1.2.1.9 and later

Information in this document applies to any platform.

症狀:

在OGG v12.x版本中,replicat程序不重新處理(譯者注:此處的重新處理了解成重新應用比較合适)trail檔案中已經應用過的record.

改變:

(譯者注:無)

原因:

如果replicat程序重新定位到已經處理完畢的trail file,replicat程序不會重新應用這些資料--這是預期的行為,因為 COMMIT SCN 小于被replicat程序處理過的last record.

解決方案:

start <replicat-name> NOFILTERDUPTRANSACTIONS      

當replicat程序從0,0開始處理時,replicat程序正常使用CSN Filtering功能.當你改變replicat到之前應用過的record,并且使用start with nofilterduptransactions 來啟動replicat時, replicat程序能按照預期(譯者注:預期是指重新應用已經應用過的record)來處理record

譯者注:

關于nofilterduptransactions

1.這是一個ggsci中start replicat指令中的一個參數,不是replicat程序的參數檔案中的參數

2.該參數的含義見

3.該參數有如下的解釋:

Causes Replicat to ignore transactions that it has already processed. 
Use when Extract was repositioned to a new start point (see the ATCSN or AFTERCSN option of “START EXTRACT”) 
and you are confident that there are duplicate transactions in the trail that could cause Replicat to abend. 
This option requires the use of a checkpoint table.If the database is Oracle, 
this option is valid only for Replicat in nonintegrated mode.
In case of Integrated mode and automatic target trail file regeneration, 
the Integrated mode handles the duplicate transactions transparently. 
The default is FILTERDUPTRANSACTIONS      

4.MOS中的相關參考文章: