GoldenGate

Hi all,

I have installed OGG (Oracle GoldenGate) on SQL Server 2008 R2 hosted on Windows 2008 R2. I found that log file grows quickly and cannot be released after transaction log backup.
The spaces issues almost crash the database, I just execute the sp_repldone command to clean truncation point; then the log file is enabled to be shrink after the transaction log backup.
As I know, OGG should automatically issue sp_repldone to move truncation point for releasing log file spaces by marking data distributed if we start extract with MANAGESECONDARYTRUNCATIONPOINT.
But my oracle consult told me not to use the option but using NOMANAGESECONDARYTRUNCATIONPOINT instead; because once we start the extract with MANAGESECONDARYTRUNCATIONPOINT,
OGG will give a OGG-00091 warning below in the ggserr.log, so we CANNOT use MANAGESECONDARYTRUNCATIONPOINT option:


2011-10-03 10:31:23 WARNING OGG-00091 Oracle GoldenGate Capture for ODBC, E_MYDBEX.prm: VAM Client Report <MSSqlVam: (0) MANAGESECONDARYTRUNCATIONPOINT will provide the highest capture performance on SQL Server 2008 but it is incompatible Microsoft Change Data Capture for this database.>.


We have built a mirror site of database, but there is no other third-party replication or SQL server transaction replication; I have checked the installation guide(SQL Server Installation and Setup Guide, 11g
Release 1 Patch Set 1 (11.1.1.1), E21507-01) and wonder that whether I can use MANAGESECONDARYTRUNCATIONPOINT option or not?

Any idea is highly appreciated.


Best Regards,
David

Edited by: wyswyg1 on 2011/11/14 上午 1:37

Edited by: wyswyg1 on 2011/11/14 上午 1:38