Skip to Main Content
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 Data & AI Roadmaps (http://ibm.biz/Data-and-AI-Roadmaps) - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at https://hybridcloudunit-internal.ideas.aha.io/


Status Not under consideration
Workspace Informix
Components Informix Server
Created by Guest
Created on Aug 3, 2015

Only update rows in referenced tables only once per template repair (with p > 0), thus avoid deadlock & LongTX

Product in Use IBM Informix 11.70UC8X6
Customer Information Duane Guthrie
Email: dguthrie@cisco.com Phone: 972-813-5115
Sizing info TBD
Product Enhancement Request Abstract Request to only update rows in referenced tables (t1 and t2 here) only once per template repair (with p > 0), thus avoid the deadlock situation that leads to a long transaction.

1 Problem Description/Usage Scenario


As part of Cisco's migration strategy, they take a backup of a node and restore it on a new node. During this time updates can occur, so this new node needs to be checked (w/ cdr check –repair) to see if it's in sync with the rest of the cluster when brought online.

In this scenario table1(t1), table2(t2), table3(t3), and table4(t4) are all part of a replicate template. Both t3 and t4 have references to both t1 and t2. When running cdr check repair with p>0, and both t3 and t4 needing repairs, it is possible to see deadlocks that ultimately lead to long transactions.
1.1 Describe your current usage scenarios of Informix and problem associated with it
See above.
1.2 Describe what would you like the new product to do for your business
This would allow the setup process for new nodes to avoid deadlocks/long tx's which cause the setup process to fail.
2 List any special considerations around expected solution
2.1 Expected Capability
That Informix would only updating rows in referenced tables (t1 and t2 here) only once per template repair, thus avoid the deadlock situation that leads to a long transaction.
2.2 Standards Compliance
N/A
2.3 Platform-Specific Considerations
Cisco runs Linux RH6 32-bit.
2.4 List any restrictions which would need to be placed on the enhancement's implementation
N/A

2.5 List any performance expectations

3 Deadlines/Known Revenue Impacts/Impact of not meeting requirements

3.1 Timeframe
As soon as possible

3.2 Product Release
Ideally in the next interim release of 11.70/12.10

3.3 What is the business benefit of having this enhancement?
By only updating rows in referenced tables (t1 and t2 here) only once per template repair, thus avoid the deadlock situation that leads to a long transaction.