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 > Impact of CDC on OLTP throughput

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 04-20-11, 13:39
getback0 getback0 is offline
Registered User
 
Join Date: Oct 2010
Posts: 73
Impact of CDC on OLTP throughput

We are moving off the Mainframe for a couple of our OLTPs to AIX - the backend is still on DB2.

The problem: Our EDW loads extracted only changed data through IBM's Log Analyzer tool on the Mainframe. Now that this is going to AIX, we will need a CDC mechanism of some kind in the distributed world -

Options I am aware of are -

1. SQL Rep (Free with Db2 LUW, right?) - not very fast? and Only DB2 replication possible
2. Qrep - Licensing purchase - fast and DB2 and Oracle replication

All this is good, however, the OLTP stakeholders are pushing back saying they have a performance concern around the CDC reading the transaction log. I am not given numbers to substantiate this. My understanding is that CDC is an industry best-practice and there would have to be a strong argument against not performing CDC - performance is a genuine concern for OLTPs but would need to established.

Obvious question:
In you guys' experience, have you ever seen significant performance problems from conventional CDC ? If so, what was done to remediate?

As always, THANKS FOR YOUR HELP!

- G

Last edited by getback0; 04-20-11 at 13:42.
Reply With Quote
  #2 (permalink)  
Old 04-20-11, 14:34
n_i n_i is offline
:-)
 
Join Date: Jun 2003
Location: Toronto, Canada
Posts: 4,449
There is a separate product - IBM InfoSphere Change Data Capture, formerly known as DataMirror, - so don't confuse the three.

It's not clear from your description whether your OLTP systems are the source or the target of replication; I'm assuming the former.

Since SQL replication Capture reads transaction data from the logs that have already been written, I don't see how that can affect OLTP workload (unless, of course, your system is running at close to 100% of CPU and/or I/O capacity, in which case you have bigger problems to solve). You can schedule Capture so as to minimize interference with other workloads.
Reply With Quote
  #3 (permalink)  
Old 04-20-11, 14:38
getback0 getback0 is offline
Registered User
 
Join Date: Oct 2010
Posts: 73
Thanks for the confirmation n_i! The OLTP is the source for replication.
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