An Sql Error 911 Occurred During Processing Db2
Contents |
You can track all active APARs for this component. APAR status Closed as program error. Error
Db2 Sql Error Sqlcode 911
description Cust has installed MERVA USE & Branch for NT v4.1. All db2 sql error code 911 initial MERVA users like mervaadm, merva1 and merva are created. The installation is verified. The setting and sql3015n an sql error occurred during processing status of MERVA instance is checked correctly. She then migrates all except BIC (correspondents, type 256) from MERVA/2 v3.3 to the v4.1. The import command used is: -
Sql3015n An Sql Error
rexx enmcxmig -f e:\enmmigra\migra -c 767 (where 767=1023 - 256) - During the import process, error occurs (when accessing user rights): - SQL3015N An SQL error "-911" occurred during processing. SQL0911N The current transaction has been rolled back because of a deadlock or timeout. Reason code "68". SQLSTATE=40001 Local fix The problem: The access violation occurs
Sqlcode=-911 Sqlstate=40001 Sqlerrmc=2
if a user has NO rights!!! - To import your users, open the MIGRA.USR file and delete (or comment with a leading ';') the following lines User = ( UserID = "install" Assigned_LT = "BKCHHKH0A" ) Problem summary Import users fails, if a user has NO rights. Problem conclusion MERVA module enmcximp changed to fix the problem. Temporary fix Comments APAR Information APAR numberPQ45583 Reported component nameMERVA NT USE Reported component ID5648B3001 Reported release410 StatusCLOSED PER PENoPE HIPERNoHIPER Special AttentionNoSpecatt Submitted date2001-01-31 Closed date2001-02-07 Last modified date2001-06-01 APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros ENMCXIMP Fix information Fixed component nameMERVA NT USE Fixed component ID5648B3001 Applicable component levels R410 PSY UQ52508UP01/06/01 I 1000 Document information More support for: MERVA Software version: 410 Reference #: PQ45583 Modified date: 2001-06-01 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
68 If this is your first visit, be sure to check out the FAQ by clicking the sql3015n an sql error "-572" occurred during processing link above. You may have to register before you can
How To Resolve Sqlcode 911
post: click the register link above to proceed. To start viewing messages, select the forum that sql3015n an sql error "-1224" occurred during processing. you want to visit from the selection below. Results 1 to 15 of 15 Thread: SQL Error: -911, SQLState: 40001 ]ROLLBACK DUE TO DEADLOCK/TIMEOUT; REASON http://www.ibm.com/support/docview.wss?uid=swg1PQ45583 68 Tweet Thread Tools Show Printable Version Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 11-11-08,09:42 #1 rodex2mail View Profile View Forum Posts Registered User Join Date Nov 2008 Posts 7 Unanswered: SQL Error: -911, SQLState: 40001 ]ROLLBACK DUE TO http://www.dbforums.com/showthread.php?1635479-SQL-Error-911-SQLState-40001-ROLLBACK-DUE-TO-DEADLOCK-TIMEOUT-REASON-68 DEADLOCK/TIMEOUT; REASON 68 We are using Database server = DB2/SUN64 8.2.4 fixpack 11. Our J2EE Application will do batch inserts in DB2. recently we are getting Exceptions while we doing batch inserts on table. net.sf.hibernate.util.JDBCExceptionReporter.logExc eptions(JDBCExceptionReporter.java:58)] ERROR - [BEA][DB2 JDBC Driver][DB2]Abnormal end unit of work condition occurred. net.sf.hibernate.util.JDBCExceptionReporter.logExc eptions(JDBCExceptionReporter.java:57)] WARN - SQL Error: -911, SQLState: 40001 [net.sf.hibernate.util.JDBCExceptionReporter.logExc eptions(JDBCExceptionReporter.java:58)] ERROR - [BEA][DB2 JDBC Driver][DB2]ROLLBACK DUE TO DEADLOCK/TIMEOUT; REASON 68 We tried a lot to replicate the error in Our Dev environments . but we could not able to do... It seems issue is with Database configurations. And what we observed is ....when we query the data from table , at sametime bacth inserts are happeing on that table, we are getting exceptions. This table has 900K rows have one column with CLOB(50080) Is there anything todo with Tablespace and Bufferpool configurations? Can someone pls advise me if u have idea? Thanks. Reply With Quote 11-11-08
touching the DB at this time.About every 2 days I get http://comp.databases.ibm-db2.narkive.com/M4XyR8Qj/an-sql-error-911-occurred-during-processing the error below on the same tablesmost of the time.What could be causing this??????SQL3104N The Export utility is beginning to export data to file"/db2/data/crprod/exports/TBL_PREMINDERS_CA.ixf".SQL3015N An SQL error "-911" occurred during processing.SQL0911N The current transaction has been rolled back because of a deadlockor timeout. sql error Reason code "2". SQLSTATE=40001SQL3105N The Export utility has finished exporting "9202778" rows.Thanks Shashi Mannepalli 2006-10-05 17:39:49 UTC PermalinkRaw Message Reason Code 02 is a DEAD LOCK.Reason Code 68 is a LOCK TIME OUT.So clearly there is a contention for your EXPORT with another processon an sql error that table.Schedule a DB2 EVENT MONITOR to find the SQL(applications) which areinvolved in this DEAD LOCK.Cheers...Shashi MannepalliPost by Willard FarwarkDB2 7.2. I do an export each night of important tables.Nothing else should be touching the DB at this time.About every 2 days I get the error below on the same tablesmost of the time.What could be causing this??????SQL3104N The Export utility is beginning to export data to file"/db2/data/crprod/exports/TBL_PREMINDERS_CA.ixf".SQL3015N An SQL error "-911" occurred during processing.SQL0911N The current transaction has been rolled back because of a deadlockor timeout. Reason code "2". SQLSTATE=40001SQL3105N The Export utility has finished exporting "9202778" rows.Thanks 1 Reply 30 Views Switch to linear view Disable enhanced parsing Permalink to this page Thread Navigation Willard Farwark 2006-10-05 17:05:25 UTC Shashi Mannepalli 2006-10-05 17:39:49 UTC about - legalese Loading...