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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Data & AI Roadmaps ( - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at

Status Not under consideration
Workspace Informix
Components Informix Server
Created by Guest
Created on Jan 7, 2014

Feature Request: Allowing dirty read capability beyond ETX 1.31.xC2

IDS 11.70.FC7W2
OS AIX 6.1
ETX version
expression) DataBlade version:
Excalibur Text DataBlade Release 1.31.FC1X3

Due to the fix of IC73561 may have introduced the new behaviors on 1.31.xC2 that impact customer's current operation.

Customer use ETX in OLTP environment. If a particular query runs too long say 5 minutes, all the rest of the queries and updates will have to wait for that long to continue processing.
On average each query will run anywhere from 10 to 60 seconds.

On 1.31.xC1 can assert fail when ETX dirty reads occur because the server was not designed to support dirty reads on ETX Large Objects. The defect IC73561 here was determined that we should not have allowed dirty reads.
On 1.31.xC2, with IC73561, development decided to fix this defect by having readers wait and retry while a writer is doing ETX Large Object manipulation. There is no other fix that will circumvent these dirty read
relevant assertion failures.

New behavior introduced in 1.31.xC2 as below:
- when a reader encounters a writer who has a lock doing LO navigating and change,
- the reader will stay on and keep trying certain times
- the reader will proceed when the writer finishes the LO navigating within the trying period
- the reader will return the lock error after try certain times and allow user to check the status and re-try the read
- currently not allow user to change that certain times (currently it try 20 times) in order to avoid complicated deadlock

Customer said workaround of Running on secondary is not being considered at the moment as secondary is used for DSS queries.

Hence, customer wishes to having dirty read capability beyond 1.31.xC2; or other alternative which allows them to overcome the changes put in 1.31.xC2 or avoid the AF crash ( due to idsdb00186209) that happens in current ETX 1.31.XC1.
  • Admin
    Karen Qualley
    Jun 12, 2019

    Thank you for the input! However, Excalibur blade is out of support so will not implement at this time.