Com.ibm.db2.jcc.b.sqlexception Db2 Sql Error
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. db2 sql error sqlcode 964 sqlstate 57011 User starts the standard (Java-based) "Database Conversion Utility", and chooses "Controller DB". User
Db2 Sqlcode: -968, Sqlstate: 57011
clicks "Connect" and chooses "Create DB". 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 sqlstate 57011 sqlcode 904 Running script: script/db2/trigger_trg_saxipstand_insert.sql ** ERROR: com.ibm.db2.jcc.am.SqlException: DB2 SQL 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
Sqlstate 57011 Sqlcode 968
for "LOGPRIMARY" is too small (for example it was set 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 sqlerrmc db2 settings Scenario #2 - DBA has configured the database to have the correct settings, but these 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
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 then http://www.ibm.com/support/docview.wss?uid=swg21614478 runs the relevant scripts to configure the database. Immediately afterwards, user launches "Controller Configuration" and selects a database connection. User starts the standard (Java-based) "Database Conversion Utility", and chooses "Controller https://community.oracle.com/thread/1107456 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 Error: SQLCODE=-964, db2 sql 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 'actioned' these changes sqlstate 57011 sqlcode 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* disconnect from the database (instead, stay
CommunityOracle User Group CommunityTopliners CommunityOTN Speaker BureauJava CommunityError: You don't have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it enabled. Please turn JavaScript back on and reload this page. Please enter a title. You can not post a blank message. Please type your message and try again. More discussions in WebLogic Server - JDBC All PlacesFusion MiddlewareWebLogicWebLogic Server - JDBC This discussion is archived 5 Replies Latest reply on Jul 27, 2010 3:43 PM by Joe Weinstein-Oracle com.ibm.db2.jcc.b.SqlException: DB2 SQL Error: SQLCODE=-973, SQLSTATE=00000 Tarun Boyella-Oracle Jul 26, 2010 10:00 PM Hi, We are running WebLogic 10.3.0 on RHEL 5.3 with JRockit JDK 1.6 and DB2 Version 8 on mainframe running z/OS 1.9. We are getting below exception in webLogic logs from connection pool connecting to DB2 database. > ####