APAR status
Closed as program error.
Error description
Using a JDBC provider configurable service definition for Teradata, a message flow is able to successfully connect to the database from a JavaCompute node using the getJDBCType4Connection() API, but a DatabaseRetrieve node fails to connect with the following errors: BIP6233E: An error occurred in node: Broker 'brokerName'; Execution Group 'EGName'; Message Flow 'MsgFlowName'; Node 'nodeName'; Node Type 'DatabaseRetrieve' There was a problem establishing a connection to the given database URL:jdbc:teradata://xxx.zzz.com/DATABASE=dev,DBS_PORT=1025,TMODE =ANS I Exception details: error message [Teradata JDBC Driver] [TeraJDBC 15.10.00.05] [Error 1032] [SQLState HY000] Single Sign-On NOT supported for Mechanism TD2., SQLState value: HY000, vendor's error code: 1032, stack trace: [com.teradata.jdbc.jdbc_4.util.ErrorFactory.makeDriverJDBCExcept ion com.teradata.jdbc.jdbc_4.util.ErrorFactory.makeDriverJDBCExcepti on com.teradata.jdbc.jdbc.GenericTeraEncrypt.initEncrypt com.teradata.jdbc.jdbc.GenericTeraEncrypt.<init> com.teradata.jdbc.jdbc.GenericLogo Additional Symptom(s) Search Keyword(s): DatabaseRetrieve,, Teradata DB, JDBC , BIP6233E
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM Integration Bus V10.0 using the DatabaseRetrieve node. Platforms affected: z/OS, MultiPlatform **************************************************************** PROBLEM DESCRIPTION: Using a JDBC provider configurable service definition for Teradata, a message flow is able to successfully connect to the database from a JavaCompute node using the getJDBCType4Connection() API, but a DatabaseRetrieve node fails to connect with the exception: [Teradata JDBC Driver] [TeraJDBC 15.10.00.05] [Error 1032] [SQLState HY000] Single Sign-On NOT supported for Mechanism TD2., SQLState value: HY000, vendor's error code: 1032 The reason is that the user and password logon credentials from the JDBCProvider's securityIdentity property are not being used on the connection attempt if user and password are not included on the connectionUrlFormat. 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 DatabaseRetrieve node now uses the JDBCProvider securityIdentity credentials to make a JDBC connection even if the user and password properties are not set in the connectionUrlFormat string. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v10.0 10.0.0.7 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 number
IT14583
Reported component name
INTEGRATION BUS
Reported component ID
5724J0540
Reported release
A00
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-04-01
Closed date
2016-11-23
Last modified date
2016-11-23
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
INTEGRATION BUS
Fixed component ID
5724J0540
Applicable component levels
RA00 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
23 March 2020