Instead of letting replication do the loads, why dont you load the tables
before you start replication. It might require some
coordination, but you wont need a huge supply of logs






"Andy Liggins " <db2udbdba-ezmlmshield-x80679264.[Email address protected]
03/20/2008 10:30 AM

To
"LazyDBA Discussion" <[Email address protected]
cc

Subject
replication and transaction logs







How do I get around the problem of transaction logs being filled up as I
start replication. DB2 is using up over 100GB of log space trying to get
through the initial startup of replication.

I am running capture in warmsi mode and using LOADXIT = Y on apply.

any help would be greatly appreciated.


---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To post a dba job: http://jobs.lazydba.com
To Subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html



DB2 & UDB email list listserv db2-l LazyDBA home page