Bip2321e Database Error Odbc
error 1 reply Latest Post - 2014-01-16T15:55:25Z by Gregory(Greg)Bowman Display:ConversationsBy Date 1-2 of 2 Previous Next w_w_h 270005JE1J 1 Post Pinned topic Database bip2321e database error odbc return code error 2013-12-27T14:07:07Z | Tags: Answered question This question has been answered. bip8040e unable to connect to the database Unanswered question This question has not been answered yet. Hi, We have 2 clustered nodes bip2393e: database error: odbc return code '-1' from data source on IBM AIX. Lately, we saw the following error in the cluster log: [6940]BIP2321E: Database error:ODBC return code '-1': AAA.BBB.BK.FLOW.dc6f4fbc-2601-0000-0080-d999162ad314:/build/S600_P/src/DataFlowEngine/ImbOdbc.cpp: 231:ImbOdbcHandle::checkRcInner:: [6940]BIP2321E: Database error:SQL State '08S01'; bip2322e database error Native Error Code '3114' ; Error Text '[DataDirect][ODBC Oracle driver][Oracle]ORA-03114:not connected to ORACLE'.: AAA.BBB.BK.FLOW.dc6f4fbc-2601-0000-0080-d999162ad314:/build/S600_P/src/DataFlowEngine/ImbOdbc.cpp: 369:ImbOdbcHandle::checkRcInner:: As a result, the data was not updated in our application. May I know does anyone encountered this error before? Besides cluster log, where can we find out more related this error so that we could determine the cause of the lost connection to ORACLE? Thank you! Log in to reply. Gregory(Greg)Bowman 1000007M77 1 Post Re: Database error 2014-01-16T15:55:25Z This is the accepted answer. This is the accepted answer. Hi, Just searching around within the IBM support information, I did not find anything specifically related to IIB or WMB for the ORA-03114 error code but there were lots of references to network connectivity problems associated with that code in other non-IBM sites. In general there is a really good Webcast replay: Debugging top ten WebSphere Message Broker V7.x/8.x problems with databases on Windows/UNIXes http://www.ibm.com/support/docview.wss?uid=swg27036313 It has several sections talking about configuration and setting up connections. Maybe something there could help. Regards, Greg Bowman, IBM Knowledge Engineer, opinions are my own and not those of my employer. Log in to reply. Show: 10 25 50 100 items per page Previous Next Feed for this topic
PROCEDURES IN SQL SERVER 2008 A fix is available WebSphere Message Broker V7.0 - Fix Pack 7.0.0.3 Subscribe You can track all active APARs for this component. 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 https://www.ibm.com/developerworks/community/forums/html/topic?id=cbbf4153-ab07-44c1-8f85-a7fe8d09f08b 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 http://www.ibm.com/support/docview.wss?uid=swg1IC76897 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 for delivery in the following PTFs: V7.0 - Maintenance Level 7.0.0.3 The latest available maintenance can be obtained from 'WebSphere Message Broker Recommended Fixes' http://www.ibm.com/support/docview.wss
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.Che