Db2 Sql Error Sqlcode=-954 Sqlstate=57011
Contents |
DRIVER=3.59.81 ** ERROR: Invalid datbase, XFRANGO is empty" creating new Controller database Technote (troubleshooting) Problem(Abstract) User launches "Controller Configuration" and selects a database connection. User starts the standard (Java-based) "Database "db2 sql error: sqlcode=-964, sqlstate=57011" Conversion Utility", and chooses "Controller DB". User clicks "Connect" and chooses "Create DB".
Sqlcode Sqlstate 57011
After a while, an error appears. Symptom Running script: script/db2/trigger_trg_saxipmain_insert.sql Running script: script/db2/trigger_trg_saxipstand_delete.sql Running script: script/db2/trigger_trg_saxipstand_insert.sql ** ERROR: com.ibm.db2.jcc.am.SqlException: DB2 SQL sqlstate 57011 sqlcode 904 Error: SQLCODE=-964, SQLSTATE=57011, SQLERRMC=null, DRIVER=3.59.81 ** ERROR: Invalid datbase, XFRANGO is empty Cause Controller database's transaction log settings are too restrictive. Specifically, the value for "LOGPRIMARY" is too small (for example it was set http://www.ibm.com/support/knowledgecenter/SSEPGG_9.7.0/com.ibm.db2.luw.messages.sql.doc/doc/msql00954c.html to 20). For more details on this topic, see separate IBM article "Tivoli Identity Manager Express Version 4.6 - Database update fails with an SQL error". There are several different possible causes for the log settings being incorrect: Scenario #1 - DBA has configured the database to have the wrong (too restrictive) log settings Scenario #2 - DBA has configured the database to have the correct settings, but these http://www.ibm.com/support/docview.wss?uid=swg21503319 settings have not yet been activated by the database server. See separate IBM Technote 1614478. More Information: Transaction logs keep track of each and every transaction - if anything goes wrong with database/instance it gives the database a chance to roll forward/back these transactions. There are many different potential ways to configure transaction logs, such as: In DB2 there are two different ways of taking care of transactions: Circular Archive Transaction log file sizes Number of log files The optimal transaction log configuration varies between database usage (for example 'datawarehouses', 'OLTP') and how intense the usage is (for example the number of concurrent active users). => Therefore it is impossible to give precise/exact recommendations for transaction log settings. Extra Tip: One tip can be useful is to use the "logsecond" parameter - if 'logprimary' is full a second logfile ('logsecond') is created. This is created "on the fly when needed", and they are freed (over time) when the database manager determines that they are no longer needed. There is a downside to this - there can be some overhead to create a new logfile during a transaction. For more information on 'logsecond' see link at the end of this Technote. Environment Controller 10.1 databa
Pools Bugs c3p0:JDBC DataSources/Resource Pools beta Brought to you by: swaldman Summary Files Reviews Support Wiki Mailing Lists Tickets ▾ https://sourceforge.net/p/c3p0/bugs/118/ Bugs Support Requests Patches Feature Requests News Create Ticket View Stats Group v1.0 (example) Searches Changes Closed Tickets Open Tickets Help Formatting Help #118 DB2 954 error occuring under c3p0 Milestone: v1.0 (example) Status: closed-fixed Owner: nobody Labels: None Priority: 5 Updated: 2015-02-16 Created: 2013-07-04 Creator: Kristan McDonald Private: No Hi, We've db2 sql migrated a legacy app from using hardcoded DB2 drivers to c3p0, however we're getting intermittent failures as below : com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-954, SQLSTATE=57011, SQLERRMC=null, DRIVER=4.14.113 at com.ibm.db2.jcc.am.ed.a(ed.java:682) at com.ibm.db2.jcc.am.ed.a(ed.java:60) at com.ibm.db2.jcc.am.ed.a(ed.java:127) at com.ibm.db2.jcc.am.ResultSet.completeSqlca(ResultSet.java:4101) at com.ibm.db2.jcc.am.ResultSet.earlyCloseComplete(ResultSet.java:4083) at com.ibm.db2.jcc.t4.ab.a(ab.java:835) at com.ibm.db2.jcc.t4.ab.n(ab.java:801) at com.ibm.db2.jcc.t4.ab.j(ab.java:253) at com.ibm.db2.jcc.t4.ab.d(ab.java:55) at com.ibm.db2.jcc.t4.p.c(p.java:44) at com.ibm.db2.jcc.t4.qb.j(qb.java:147) at com.ibm.db2.jcc.am.oo.kb(oo.java:2158) at db2 sql error com.ibm.db2.jcc.am.po.b(po.java:4482) at com.ibm.db2.jcc.am.po.hc(po.java:756) at com.ibm.db2.jcc.am.po.executeQuery(po.java:725) at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeQuery(NewProxyPreparedStatement.java:76) at com.myapp.shared.db.DBDynamicConnection.executeQuery(DBDynamicConnection.java:177) The description of the error is here : http://www-01.ibm.com/support/docview.wss?uid=swg21597038 It's for IBM Tivoli, but it's a DB2 error. The description there indicates it's a problem with large querys, but when it occurs it causes the connection to not process any query (simple select, update etc.) and applying fix specified to increase the application heap doesn't seem to have helped. Now don't quote me but I think it's just a single connection, not all in the pool. It's a bit hard to tell as there's multiple threads making calls to multiple databases, but the symptom is some bits work, others fail. The only way to fix it seems to be a stop and start of tomcat - even forcing a close of all the connections and c3p0 then starting it up again doesn't fix it. I'm also not sure this is a c3p0 issue specifically, but this