Com.ibm.db2.jcc.am.sqlexception Db2 Sql Error Sqlcode=-954
Contents |
Controller database caused by DB2 server not actioning LOG changes Technote (troubleshooting) Problem(Abstract) Customer's DB2 DBA creates a brand new DB2 database. The DBA "db2 sql error: sqlcode=-964, sqlstate=57011" then runs the relevant scripts to configure the database. Immediately afterwards, user
Sqlstate 57011 Sqlcode 904
launches "Controller Configuration" and selects a database connection. User starts the standard (Java-based) "Database Conversion Utility", and chooses sqlcode sqlstate 57011 "Controller DB". User clicks "Connect" and chooses "Create DB". After a while, an error appears. Symptom Running script: script/db2/procedure_usp_xbrt_upd_ins.sql Running script: script/db2/procedure_usp_xbr_del.sql Running script: script/db2/procedure_usp_xbr_upd_ins.sql ** ERROR: com.ibm.db2.jcc.am.SqlException: DB2 SQL sqlcode 968 sqlstate 57011 Error: SQLCODE=-964, SQLSTATE=57011, SQLERRMC=null, DRIVER=3.59.81 ** ERROR: Invalid datbase, XFRANGO is empty Cause There are several possible causes for this error. TIP: For more examples, see separate IBM Technote #1503319. This Technote specifically relates to the scenario where the customer has run the correct script (to create the new DB2 database with sufficient LOG space) but the DB2 server has not
Db2 Sql Error: Sqlcode=-954, Sqlstate=57011
'actioned' these changes yet. More Information: DB2 does not action all requested database changes immediately - instead, for some requests it must wait for all users to disconnect from the database before actioning them. For example, imagine a scenario where: The DBA launches DB2 "Command Editor" and runs the database creation scripts described inside separate IBM Technote #1570572. The following message is returned (by the DB2 command editor): UPDATE DB CFG USING logprimary 100 logsecond 20 logfilsiz 1024 DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully. SQL1363W One or more of the parameters submitted for immediate modification were not changed dynamically. For these configuration parameters, all applications must disconnect from this database before the changes become effective. update db cfg using auto_reval DEFERRED_FORCE DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully. update db cfg using decflt_rounding ROUND_HALF_UP DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully. SQL1418W Changing the databa se configuration parameter DECFLT_ROUNDING may have unintended consequences. The value was not changed dynamically. All applications must disconnect from this database before the changes become effective. SQLSTATE=0168M The DBA does *not
Pools Bugs c3p0:JDBC DataSources/Resource Pools beta Brought to you by: swaldman Summary Files Reviews Support Wiki Mailing Lists Tickets ▾ 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 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 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 do