If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > Replication Issue with CLOB columns

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 02-27-08, 06:10
arehmanb arehmanb is offline
Registered User
 
Join Date: Feb 2008
Posts: 1
Replication Issue with CLOB columns

I am working on DB2 Version 8.1 Fixpack 10. My O/S is AIX.

I have a SQL replication setup in my database(production).I have a table with CLOB colums. All the column data is replicating good from the source to target except CLOB columns till this date.

With the same dprop settings on test and development databases working good including CLOB colums.

So, here my question is,why this CLOB column data is not replicting in the production databases.Is there any updates needed in the ASN tables.

Please help me in this:

Thanks in Advance
Reply With Quote
  #2 (permalink)  
Old 02-27-08, 17:15
sundaram sundaram is offline
Registered User
 
Join Date: Mar 2006
Posts: 104
Hi,
This is my guess. Replication use the journal entries. DDL for creating a CLOB column has option to say wether it is logged or not. Probably in your case the CLOB is not marked logged and that could be the reason why it is not replicated.

Regards

Harikumar
Reply With Quote
  #3 (permalink)  
Old 02-28-08, 02:57
stolze stolze is offline
Registered User
 
Join Date: Jan 2007
Location: Jena, Germany
Posts: 2,662
Another restriction on LOB columns is that the CD tables only contain an "update indicator", i.e. a flag saying whether the LOB was changed ('U') or not (NULL). The Apply process will, upon discovering the 'U', issue a query against the actual source table to grab the real LOB value and send it to the target database. The obvious issue with that is that CD table entries are not synchronized with the source table, i.e. Apply may read a newer LOB value. Depending on your scenario, this may result in seeing no visible change - for example, if you change LOB value A to B and then back again. The advantage of this approach is that the LOB values will not be copied to CD tables, doubling the amount of space required.
__________________
Knut Stolze
IBM DB2 Analytics Accelerator
IBM Germany Research & Development
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On