goldengate for SQL Server log explosion resolution

When the GG for SQL Server 2008 R2 is turned on, the SQL Server log will skyrocket, as follows:

1. Confirm that the database setup problem is causing

Such as:

1 Check the Ggerror, whether there is an error!

2 then confirm that log backup uses log backups and does not use compression.

3) Database Recovery model

2. After the GG added the table's extended log, confirm that the agent in the corresponding CDC capture disabled

Add Trandata dbo.tbl01

After opening the extended log, you need to disable the corresponding CDC capture in the agent.

3. Confirm parameter extract parameter file use Managesecondarytruncationpoint

Tranlogoptions Managesecondarytruncationpoint

4. If all of the above methods are configured correctly, the SQL Server log still soars! Need to reconfigure the following GG:

Please make sure that GG has read the current log before doing the following.

--4.1 Delete Extension Log

Delete Trandata dbo.tbl01

---4.2 Delete extraction and transfer

Delete Extract Extrate

Delete Exttrail S:\gg\dirdat\rt

Delete EXTRACT pumprate

Delete Rmttrail S:\gg\dirdat\rt

DBCC Opentran

Go

EXECUTE Sp_repltrans

Go

--4.3 Note: Resetting the unassigned logs to 0 using sp_repldone may cause reconfiguration and can not resolve log surges

EXEC sp_repldone @xactid = null, @xact_segno = null, @numtrans = 0, @time = 0, @reset = 1

Go

--4.4 Disable the database CDC

Use test

Go

EXEC sys.sp_cdc_disable_db

Go

--4.5 reconfiguration

You can then add the extended log, extract, and transfer again.

See more highlights of this column: http://www.bianceng.cnhttp://www.bianceng.cn/database/SQLServer/