IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


Add a new idea Subscribe
Status Under review
Workspace Replication: Change Data Capture
Created by Guest
Created on Jun 16, 2023

RELATED IDEAS

Avoid locking table at the start of a refresh

Currently  DB2 z/OS Remote agent will try to lock a table, apparently to obtain the head of logs position, just before starting a table refresh. Although the lock is immediately released, in some customer environments it very hard to obtain this lock. Customers end up with the error:
com.datamirror.ts.util.TsThread.run(TsThread.java:130)|Caused by: com.datamirror.ts.util.EnvironmentUserException A SQL exception has occurred. The SQL error code is '-913'. The SQL state is: 57033. The error message is: |[CDC][DB2 JDBC Driver][DB2]FAILED EXECUTION DUE TO DEADLOCK/TIMEOUT. REASON 00C9008E TYPE 00000D01|    at
com.datamirror.ts.customertable.db2z.dao.Db2zTablePropertiesDAO.lockTable(Db2zTablePropertiesDAO.java:89)|    at
com.datamirror.ts.scrapers.db2zscraper.Db2zLogConfig.getBookmark(Db2zLogConfig.java:104)|    at
com.datamirror.ts.scrapers.LogConfig.getStartBookMark(LogConfig.java:134)|    at
com.datamirror.ts.source.logcleanup.EarliestBookmarkTracker.setTableBookmarkToCurrent(EarliestBookmarkTracker.java:387)|    at
com.datamirror.ts.scrapers.history.ScrapedTableContextStorage.getAndProtectHeadOfLogForTable(ScrapedTableContextStorage.java:1687)|    at
com.datamirror.ts.scrapers.history.ScrapedTableContextStorage.captureVersionedTableStructure(ScrapedTableContextStorage.java:1544)|    at
com.datamirror.ts.scrapers.history.Db2zScrapedTableContextStorage.captureTableStructure(Db2zScrapedTableContextStorage.java:109)|    at
com.datamirror.ts.scrapers.history.ScrapedTableContextStorage.captureAndReturnTableStructure(ScrapedTableContextStorage.java:356)|    at
com.datamirror.ts.source.tablereader.TableReader.getCurrentBookMark(TableReader.java:458)|    at
com.datamirror.ts.source.tablereader.TableReader.beginTableRead(TableReader.java:166)|    at
com.datamirror.ts.source.tablereader.TableReader.beginTableRead(TableReader.java:121)|    at
com.datamirror.ts.source.replication.TableRefresher.refreshTable(TableRefresher.java:330)|    at
com.datamirror.ts.source.replication.MirrorComponent.doRefresh(MirrorComponent.java:374)|    at
com.datamirror.ts.source.replication.MirrorComponent.refreshTableSetForMirrorRefresh(MirrorComponent.java:3750)|    at
com.datamirror.ts.source.replication.MirrorComponent.evaluateRulesAndRefresh(MirrorComponent.java:2351)|    at
com.datamirror.ts.source.replication.MirrorComponent.startReplication(MirrorComponent.java:3397)|    at
com.datamirror.ts.source.replication.MirrorComponent.moderateForTheSource(MirrorComponent.java:456)|    at
com.datamirror.ts.source.replication.ModeratorBase$SourceDataChannelJob.execute(ModeratorBase.java:495)|    at
com.datamirror.ts.engine.component.PipelineThread.runThread(PipelineThread.java:217)|    at


This makes the refresh fail, and on this customer where they still have many occurrences of the DB2 LOAD utility makes the subscription abort many times and then they need to relaunch the refresh at times where the concurrent processes are not running. From what we gathered the concurrent processes use "persistent threads" which prevent this type of locks.

This is causing frequent issues in their replication environment.
 From discussions with development team, the Java agents have never used the lock to obtain consistency, and this lock to obtain the bookark should not be needed. The z/OS native agent apparently also removed the need for any lock for table refresh consistency (PTF PH38050), so this enhancement would put both agents at the same functionality level (althouth the cause for the lock seems to differ).
This would benefit all customers using the DB2 z/OS remote agent. Again, accordingly to internal discussions there are ways to obtain the same result without the lock
 

Needed By Quarter

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.