Skip to Main Content

This is an IBM Automation portal for Integration products. 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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

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.

Status Future consideration
Workspace App Connect
Created by Guest
Created on Nov 9, 2012

Update Broker System Trace to include value of ODBCINI and the real error behind issues reading odbc.ini

In troubleshooting a problem connecting to MS SQL Server we performed a system trace. The trace provided the following error information:

DatabaseException BIP2347E: Database error: SQL State ''IM002''; Native Error Code ''0''; Error Text 'System information file not found. Please check the ODBCINI and the ODBCSYSINI environment variables are correctly set.'

The issue was not what the Error indicated. The file did exist and the ODBCINI variable was set correctly. The issue was that the file had incorrect permissions which prevented broker from being able to read it.

It would be very helpful in troubleshooting if the following were added to the error being dumped:

1) The value of ODBCINI.
2) The real reason for the failure, 'file not found', 'file read error', 'access error', etc.

Idea priority Medium
RFE ID 28351
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Feb 3, 2021

    RFE Review. Although this enhancement idea has not received widespread support, despite being open for several years, we still feel this requirement could bring improved usability for the product in the scenario outlined. Ultimately, the odbcini file is interpreted and used by the UnixODBC Driver Manager embedded within the product, so there are limits to the validation logic which we can easily apply, however it would absolutely make sense to include it in service trace output to help make it easier to discover user errors and issues like the one described. Given this backdrop, whilst we don't have imminent delivery plans in this area we do wish to keep the enhancement open and will continue to monitor. Status is maintained as Uncommitted Candidate.

  • Guest
    Oct 7, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Connectivity and Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

  • Guest
    Feb 6, 2014

    Thanks for raising this requirement - a useful enhancement for diagnosing database problems.