PI22639: AN ATTEMPT TO CONNECT TO DB INACCURATELY REPORTS BIP2338E OR BIP2466E

APAR status

• Closed as program error.

Error description

• The first time WMB tries to connect to a database, it will issue
  multiple SQLGetTypeInfo calls in order to ensure that the
  database supports all of the types that broker needs. If the
  SQLGetTypeInfo does not return a successful return code, we
  assume it is because the datatype is unsupported and throw a
  recoverable exception stating as much. The failure of the
  SQLGetTypeInfo may not be related to an invalid SQL data type
  and the broker should report the actual database error.
  
  If the message flow is trying to connect to a second database in
  a flow and one of the databases returns certain types as
  supported and other types as not then a BIP2466E is thrown
  indicating that the database types are incompatible:
  
   BIP2466E: The target database 'DB1' does not have the same
  characteristics as the reference database 'DB3'.
  
  If the SQLGetType calls are failing because of a database setup
  issue and not because the SQLType is really unsupported then the
  BIP2466E is thrown in error and the real setup exception thrown
  from the database should be thrown. For example on z/OS this may
  be covering up a setup issue with the DB2 plan which is in use.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of WebSphere Message Broker V7.0 & V8.0 and IBM
  Integration Bus V9.0 who access ODBC datasources.
  
  
  Platforms affected:
  MultiPlatform, z/OS
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The first time the product tries to connect to a database, it
  will issue multiple SQLGetTypeInfo calls in order to ensure that
  the database supports all of the types that broker needs. If the
  SQLGetTypeInfo does not return a successful return code, we
  assume it is because the datatype is unsupported and throw a
  recoverable exception stating as much. The failure of the
  SQLGetTypeInfo may not be related to an invalid SQL data type
  and the broker should report the actual database error.
  
  
  There are a number of resource name changes between WebSphere
  Message Broker and IBM Integration Bus Version 9.0. For details
  visit
  http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e
  tools.mft.doc/bb23814_.htm
  

Problem conclusion

• The product now checks the return code from SQLGetTypeInfo calls
  to ensure they are appropriate for an unsupported datatype and
  if not throws an exception.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v7.0       7.0.0.8
  v8.0       8.0.0.7
  v9.0       9.0.0.4
  
  The latest available maintenance can be obtained from:
  http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
  
  If the maintenance level is not yet available,information on
  its planned availability can be found on:
  http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
  ---------------------------------------------------------------
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEB MB Z/OS

• Fixed component ID

  5655V6000

Applicable component levels

• R700 PSY

     UP