Bip2321e Database Error
Contents |
PROCEDURES IN SQL SERVER 2008 A fix is available WebSphere Message Broker V7.0 - Fix Pack
Bip2393e: Database Error: Odbc Return Code '-1' From Data Source
7.0.0.3 Subscribe You can track all active APARs for this component. bip2322e database error APAR status Closed as program error. Error description BIP2921E or BIP2321E and BIP2322E errors may be encountered when using ESQL to call stored procedures in SQL Server 2008. Local fix Problem summary **************************************************************** USERS AFFECTED: All users of WebSphere Message Broker V7.0 using ODBC to access a SQL Server 2008 database. Platforms affected: AIX,HP-UX (Itanium),HP-UX (PA-RISC),Linux (Power),Linux (s390x), Linux (x86),Linux (x86-64),Linux (zSeries),Solaris (SPARC), Solaris (x86-64),Windows **************************************************************** PROBLEM SUMMARY: One problem appears as a BIP2921E error when calling a stored procedure on SQL Server 2008: The procedure 'stored_procedure_name' with 'n' parameters could not be matched with a corresponding Database stored procedure. Stored Procedures must match the ESQL CREATE PROCEDURE definition in the following ways: 1: The ESQL parameters must all be of SCALAR type. 2: The directions of each ESQL and Database parameter (IN / OUT / INOUT) must match. 3: The number of parameters in both the ESQL and database definitions must match. Ensure these conditions are met and redeploy the message flow. However, a stored procedure is known to exist and match the ESQL CREATE PROCEDURE definition and so should be found. Another problem appears as a BIP2321E/BIP2322E error when calling a stored procedure on SQL Server 2008: BIP2321E: Database error: ODBC return code '-1' using ODBC driver manager 'libbipodbc.a(odbc.so)'. : BROKER.EGUUID: /build/S700_P/src/DataFlowEngine/ImbOdbc.cpp: 347: ImbOdbcHandle::checkRcInner: : BIP2322E: Database error: SQL State 'HY104'; Native Error Code '0'; Error Text '[IBM][ODBC SQL Server Driver]Invalid precision value'. : BROKER.EGUUID: /build/S700_P/src/DataFlowEngine/ImbOdbc.cpp: 486: ImbOdbcHandle::checkRcInner: : Problem conclusion The problems were resolved in version 06.00.0146 of the DataDirect ODBC driver for SQL Server. --------------------------------------------------------------- The fix is targeted
Subscribe You can track all active APARs for this component. APAR status Closed as program error. Error description When the ODBC API SQLError() is called to retrieve the error status of a database call that has returned SQL_NO_DATA on Unix, an unexpected return code is returned from the unixODBC Driver Manager resulting in the error not being handled as expected. The user is likely to see just the following error after the BIP2488E message: BIP2321E: Database error: ODBC return code '100' using ODBC driver manager The expected behavior would be to see both the following: BIP2321E: Database error: ODBC return code '100' http://www.ibm.com/support/docview.wss?uid=swg1IC76897 using ODBC driver manager BIP2322E: Database error: SQL State '02000'; Native Error Code '100'; Error Text '[IBM][CLI Driver][DB2/AIX64] SQL0100W No row was found for FETCH, UPDATE or DELETE This can cause issues especially when users are trying to catch the SQL_NO_DATA return code in their code. Local fix Problem summary **************************************************************** USERS AFFECTED: All users of WebSphere Message Broker V8.0 or IBM Integration Bus V9.0 who use ODBC to connect to https://www-304.ibm.com/support/docview.wss?uid=swg1IT04084 databases on Unix platforms. Platforms affected: AIX, HP-UX Itanium platform, Linux on Power platform, Linux on x86 platform, Linux on x86-64 platform, Linux on zSeries platform, Solaris x86-64 platform, Solaris SPARC platform **************************************************************** PROBLEM DESCRIPTION: When the ODBC API SQLError() is called to retrieve the error status of a database call that has returned SQL_NO_DATA on Unix, an unexpected return code is returned from the unixODBC Driver Manager resulting in the error not being handled as expected. The user is likely to see just the following error after the BIP2488E message: BIP2321E: Database error: ODBC return code '100' using ODBC driver manager The expected behavior would be to see both the following: BIP2321E: Database error: ODBC return code '100' using ODBC driver manager BIP2322E: Database error: SQL State '02000'; Native Error Code '100'; Error Text '[IBM][CLI Driver][DB2/AIX64] SQL0100W No row was found for FETCH, UPDATE or DELETE This can cause issues especially when users are trying to catch the SQL_NO_DATA return code in their code. 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 uses SQLGetDIagRec() when gathering error information which means the expected response is returned from the UnixODBC DriverManager. ----------------------------------
problem to DB2 with Message Broker Pages 1 You must login or register to post a reply Topic RSS feed Posts [ 5 ] 1 Topic by dzoff http://www.progtown.com/topic677811-connection-problem-to-db2-with-message-broker.html 2012-06-14 08:15:19 dzoff Member Offline Registered: 2012-06-15 Posts: 14 Topic: Connection problem to DB2 with Message Broker That is given:WebSphere Message brokerIBM DB2HP-UXOn one server there is a broker and basis DB2. The basis is created, is normal to it I am connected.At attempt to create the broker of messages is produced the message mqsicreatebroker BROKER-i user1-a userpass-q BROKER-n DBBROKER-u db2user-p passuserAMQ8110: WebSphere database error MQ queue manager already exists.WebSphere MQ queue manager running.The setmqaut command completed successfully.The setmqaut command completed successfully.The setmqaut command completed successfully.The setmqaut command completed successfully.The setmqaut command completed successfully.The setmqaut command completed successfully.The setmqaut command completed successfully.The setmqaut command completed successfully.The setmqaut command completed successfully.The setmqaut command completed successfully.The setmqaut command completed successfully.The setmqaut command completed successfully.The setmqaut command completed successfully.The setmqaut command completed bip2321e database error successfully.The setmqaut command completed successfully.BIP2321E: Database error: ODBC return code '-1 '.The message broker encountered an error whilst executing a database operation. The ODBC return code was '-1 '. See the following messages for information obtained from the database pertaining to this error.Use the following messages to determine the cause of the error. This is likely to be such things as incorrect datasource or table names. Then correct either the database or message broker configuration.BIP2322E: Database error: SQL State "HY010"; Native Error Code ' 0 '; Error Text "[DataDirect] [ODBC lib] The driver is incapable of supporting the current environment attributes.".The error has the following diagnostic information: SQL State "HY010" SQL Native Error Code ' 0 ' SQL Error Text "[DataDirect] [ODBC lib] The driver is incapable of supporting the current environment attributes."This message may be accompanied by other messages describing the effect on the message broker itself. Use the reason identified in this message with the accompanying messages to determine the cause of the error.BIP8040E: Unable to connect to the database.The database cannot be accessed with the userid and password that were specified when the broker was created.C