Srinivasan R Mottupalli

1. What is Latency in Change Data Capture? Latency information is normally for Mirroring subscription. As InfoSphere CDC measures latency as the amount of time that passes between when data changes on a source table and when it changes on the target table. For example, if an application inserts a row into the source table at 10:00 and CDC applies that row to the target able at 10:15, then the latency for the subscription is 15 minutes. 2. What is in-scope and out-of-scope tables in InfoSphere CDC terminology? The tables are inscope tables if they are replicated to the target by InfoSphere CDC. The tables are out-of-scope when those tables are not part of any replication. 3. How to ignore error that occurs during refresh/mirrorring? Prior 6.3 D_MIRROR_REFRESH_ERROR_STOP=OFF - refresh continues after an error has occurred. D_MIRROR_MIRROR_ERROR_STOP=OFF - mirroring continues after an error has occurred. Post 6.3 Set the following 2 system parameters via Management Console. mirror_end...

For any read-only DB connections (to Oracle) InfoSphere CDC does additional checking to see if the supplemental logging for the all the tables that are relevant to the subscriptions. This is an initial ONE TIME sanity check for any read-only connections when we change from REFRESH mode to MIRROR mode. InfoSphere CDC has the system parameter called " read_only_check_supplemental_logging " to enable or disable this ONE TIME sanity check because some customers can enable the supplemental logging ONLY for few selected columns. For such customers, this system parameter helps to by-pass this sanity check. After the instance goes to MIRROR mode, CDC does not look back this system parameter. So, it is harmless to keep this system parameter around OR one can choose to unset this parameter after CDC goes to the MIRROR mode. When this sanity check is disabled, it is assumed by InfoSphere CDC that the source database is providing the supplemental logging for all the columns in the tabl...