This post is the answer to one of the FAQs found in License Tips for IBM Data Replication.
You may have seen a recent announcement on ibm.com
that says IBM would no longer be marketing it's older data replication products in 2013. That includes InfoSphere CDC. Why?
And what happens to the CDC technology?
Over the years, IBM provided its data replication technologies
through a lot of different products. For example, IBM used to offer two major
data replication products at the same time -
InfoSphere CDC and InfoSphere Replication Server. That was a little
even to some IBM people. To simplify the situation, IBM consolidated all it's replication technologies into a single product called IBM InfoSphere Data Replication
(IIDR). Once IIDR was available, the older products no longer needed to be sold to new customers. That's why the end of marketing was announced. However, the replication technologies - CDC, Q Replication, and SQL Replication - are still alive and well. You can
continue to use them as you always
have. Of course, you may have two related questions:
- Are the older products still being supported?
- How do you move from your old InfoSphere CDC product to IIDR?
If you have any questions, feel free to post them in the comments section of this blog.
Modified on by MikeJory
IIDR 18.104.22.168 has been released with new functionality in addition to resolving some APARs.
IIDR 22.214.171.124-4 can be found on Fix Central.
* No IIDR downtime support for Microsoft SQL Server non-structural online index rebuild operations
Index and table reorganizations done to improve query performance no longer impact replication. Replication will continue with no outage and with no user actions required.
* Log based change capture for Oracle is now supported on Microsoft Windows
* No IIDR downtime support for Oracle Automatic Storage Management rebalancing activities
Previously in some situations rebalancing of ASM could could require replication be restarted
* An unplanned failure of Oracle to a DataGuard standby database no longer requires a resynchronization
Previously if an Oracle database being used as a source of changes failed over to an Oracle DataGuard standby, you would have been required to refresh the target data before restarting replication
* IIDR can now capture changes directly from ASM on Exadata
Previously replication required the ASM logs to be multiplexed to a non-ASM destination which typically could only be accomodated off the Exadata appliance
* IIDR can now target Cloudant
* IIDR can now use webHDFS to deliver change data to HDFS
This allows IIDR to be installed remotely from the cluster and enables targeting HDFS deployments that are secured via Kerberos
JR53019 POTENTIAL FOR DUPLICATE TRANSACTION REPLAY ON THE TARGET DUE TO INCORRECT BOOKMARKING ON IMMEDIATELY PREVIOUS SHUTDOWN.
JR53294 CDC TRIES TO READ AN UNCOMPLETED ORACLE LOG AND GETS ERROR IN LOG SHIPPING USING DATAGUARD SCENARIO.
JR53370 CDC DATA LOSS / CONSISTENCY UPOEN CDC RESTART AFTER ABORT
JR52825 CDC FOR DATASTAGE IN DIRECTCONNECT MODE NOT HONOURING THE DELAY PARAMETER FROM BATCH THRESHOLD SUBS PROPERTY
JR52973 DMSHUTDOWN COMMAND WITH -A OPTION DOESN'T TERMINATE SUBSCRIPTIONS
JR52797 ADDRESSING AN IDENTIFIED BUFFER OVERRUN CONDITION IN THE ORACLE SOLARIS JVM
JR53411 SETTING BLOB/CLOB TRUNCATION IN DATASTAGE PROPERTIES FOR A SUBSCRIPTION, REVERSES THE LIMITS
JR52923 TIMESTAMP IS NOT PROPERLY REPLICATING
JR53413 HAVING ROW SIZES GREATER THAN 341333 BYTES THROWS JAVA.NIO.BUFFEROVERFLOWEXCEPTION
JR52946 INSTANCE USING UPPER CASE ORACLE SID FOR STANDBY DATABASE CANNOT BE CREATED
JR53340 IIDR FOR ORACLE 12C FAILS TO START REPLICATION WHEN AN INSCOPE TABLE WAS ALTERED
The IBM Redbook titled "Smarter Business: Dynamic Information with IBM InfoSphere Data Replication CDC" is now available and can be found: http://www.redbooks.ibm.com/Redbooks.nsf/RedbookAbstracts/sg247941.html?Open
This Redbook covers a wide range of topics from InfoSphere CDC use cases, solution topologies, features and functionality, performance, environmental considerations and automation. This is a great source of information if you are wondering how best to set up InfoSphere CDC, how do you fit it into a resilient environment, etc.
With the announcement of InfoSphere Data Replication 10.1.2
, IBM added a product called InfoSphere Data Replication for Database Migration. This new product is a tool to help you with hardware and database upgrades. It is intended for short-term use. For example, if you're upgrading to a totally new hardware platform, the new Data Replication product keeps two copies of your database in sync - one copy on your old hardware and the other on your new hardware. This gives you the time you need - a few weeks or several months - to migrate and test applications before you turn off the old hardware. A similar scenario is possible if you're just upgrading databases or if you're upgrading hardware and databases simultaneously.
The first release of the new product is available for three different combinations of source and target databases (three different from and to combinations):
- Oracle to Oracle
- Oracle to DB2 for Linux, UNIX, and Windows (LUW)
- DB2 LUW to DB2 LUW
It provides only the data replication function needed for database migration. Specifically:
- Unidirectional (one-way) replication
- If you need multi-way replication, you need to buy the full Data Replication product.
- One source and target database pair.
- In other words, a single copy of the product can only be replicating between two databases at any given time.
- However, after you finish migrating a given database, you can move the product to another system and migrate another database.
- Data transformations when the source is an Oracle database and the target is DB2 LUW.
- If you need transformations for other source and target combinations, you need to buy the full Data Replication product.
- Replication of add and remove table partitions when both source and target are Oracle databases.
- If you need other DDL replication, you need to buy the full Data Replication product.
Of course, like the full Data Replication product, the new product contains all IBM Data Replication technologies - CDC, Q Replication, and SQL Replication. However, for those of you familiar with the older products- InfoSphere CDC and InfoSphere Replication Server - there is no database migration edition of those two products.
Note that there are two licensing differences for this Data Replication product when compared to many other products. First, this one is licensed by target server install instead of a PVU (processor value unit) count. That means for each target install you license, you can install at a single source for no additional charge. Second, IBM does not offer a non-production version. Therefore, you buy the same product for both production and non-production uses. This isn't bad since this database migration product is significantly cheaper than the full Data Replication product. To verify these licensing points and others, always see the the license file on ibm.com
as the official word in how licensing works.
The IBM Developer Works Data Replication communities are being merged into this community. As such, the "The CDC (Change Data Capture) Forum" is being renamed to better represent the expanded content that will now reside in this community.
"The CDC (Change Data Capture) Forum" is being renamed to "IBM Data Replication Community".
This community will include content from what was formerly:
- The CDC (Change Data Capture) Forum
- The Q+SQL Replication Forum
For those who have been using the CDC Developer Works Community, you will notice a change to the look & feel of the entry page. This new menu driven mechanism will provide extra flexibility as significant new content gets added to this community. I have tested it out on various browsers, so if you experience an issue, please send me an email at email@example.com and I will investigate.
Note I will also be cleaning up some old blog entries where questions were asked. Questions should continue to be asked on the forum versus the blog.
Hope you continue to get benefit from this community.
The new IIDR 11.3.3 Release is available today!
Here is a link to a page that describes the new functionality available: https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/W8d78486eafb9_4a06_a482_7e7962f5ac59/page/IIDR%20CDC%20New%20Features%20By%20Release?section=IIDR%2011.3.3
There are a large number of usability enhancements, new platform/DB support such as SQL Server 2014, along with technology previews/beta available for many new key technologies such as a Cloudant apply, WebHDFS support for Hadoop, and many others.
The following rules apply with respect to what Versions of Management Console (MC), Access Server, and CDC agents (engines) will inter-operate.
These rules apply to any CDC 6.x or higher release.
1) The MC and AS must be at the exact same release level
2) The CDC source and target agents (engines) can be at different release levels
3) The MC version must be >= the most recent CDC source or target agent (engine)
I have updated the look and feel of the wiki to make it easier to navigate and find what you need.
Samples are now organized in their own table and can be found by clicking the "Samples" icon on the home page.
All "how-to" documents can now be found by clicking on the "Documents" icon on the home page.
A new section has been added to the wiki which describes the features that have been added to all the recent IIDR CDC releases. In the near future I will be adding presentations with details on the features in this section.... so please check back.
In response to: Best Practice - Target Considerations
Regarding Oracle triggers on the target tables, would these fire
during a standard refresh? We want them to fire off during normal
continuous replication from DB2 to Oracle..
Most are triggers on insert so I am concerned during the refresh
which we do whenever we change the table structure to match the
I've added three new videos to my channel. They walk through configuring, operating and monitoring data replication using the CDC Management Console. This is basically the same thing you'd get if you came by the InfoSphere demo room at Information On Demand (now Insight) and agreed to let me show you a quick demo of CDC.
Here's the link to my channel "James talks about Data Replication":
I'm recording some videos where I provide technical background about data replication. I've created a YouTube channel to collect them all together. The channel is "James Talks about Data Replication". Here's a link:
I've uploaded two so far. The first one discusses the special considerations you should be aware of when using data replication with tables that have duplicate rows. The second discusses the role of data replication when moving to a real time operational analytics system from a traditional batch oriented data warehouse.
There are multiple deployment models available for InfoSphere CDC. The deployment model chosen for the source system will significantly affect the complexity of implementation.
Here are the CDC source deployment options from the least complex to the most complex:
1. InfoSphere CDC scraper runs on the source database server
2. InfoSphere CDC scraper runs on a remote tier reading logs from a shared disk (SAN)
This configuration is available for Oracle and Sybase. DB2 LUW has a similar capability, but utilizes a remote client instead of reading from a SAN.
3. InfoSphere CDC scraper runs on a remote tier using log shipping
This configuration is only available for Oracle.
Rule of Thumb
You should always use the least complex deployment option that will meet the business needs. The vast majority of CDC users install InfoSphere CDC on the source database server.