SQLCODE=-911 and it is Time out abend

sriram.mukundan · New User Joined: 20 Nov 2007 Posts: 28 Location: chennai

HI all,

I have a table which has only 2 rows.
i want to delete the Rows in the table. We identified this is due to Timeout because as the Reason code is 00C9008E.

So kindly let me know how to over come this problem.

Sinkaravelan S · Posted: Thu Jun 26, 2008 11:19 am

00C9008E
Explanation:
A lock request for the resource identified by NAME could not be granted, and the request waited for a period longer than the maximum specified by the installation.

Troubleshooting

Error SQL0913N Received: Unsuccessful execution caused by deadlock or timeout
There is a known problem that most often occurs when running one of the DYK ETL processes against a IBM Tivoli Service Level Advisor database that is located on a DB2 for z/OS operating system. The ETL step fails with a message that indicates a deadlock or timeout condition has occurred. The message is similar to the following example:

CDWEX8087E A general SQL error occurred: SQL_ERROR: 'ExecDirect' 2004.06.04

10:52:30.718 sqlState = 57033, nativeErr = -913, errorMsg = [IBM][CLI Driver][DB2]

SQL0913N Unsuccessful execution caused by deadlock or timeout. Reason code

"00C9008E". SQLSTATE=57033

This error usually follows a drop table or a create table command. The error is typically caused by multiple outside connections to the same location, for example, connections opened through the DB2 Control Center or by DB2 command prompts. To recover from this error, close all extraneous connections other than those opened by IBM Tivoli Service Level Advisor components, and try the failed ETL step again.

Thanks,

sriram.mukundan · New User Joined: 20 Nov 2007 Posts: 28 Location: chennai

There is no Extraneous connections. we are doing in SPUFI not in control center or in DB2 command prompts.

FYI i have pasted the SQLCODE AND SQLSTATE below.

DSNT408I SQLCODE = -911, ERROR: THE CURRENT UNIT OF WORK HAS BEEN ROLLED BACK DUE TO DEADLOCK OR TIMEOUT.
DSNT418I SQLSTATE = 40001 SQLSTATE RETURN CODE

enrico-sorichetti · Posted: Thu Jun 26, 2008 1:05 pm

the message is clear, it' s a lock timeout...

the locks are being held until changes are committed.

are You running another spufi session on the same table ?

check the commit options of spufi

sriram.mukundan · New User Joined: 20 Nov 2007 Posts: 28 Location: chennai

Hi Enrico,

Thanks for the suggestion. Our settings in the spufi is same as you mentioned.
we didnt open the same table in another spufi session also.

am_ne · New User Joined: 24 Mar 2007 Posts: 25 Location: Bangalore

Hi Sriram,

Did you check for any unsuccessfull utility-ids ? May be some util-id is hanging there with exclusive locks and not allowing any other connections.

If you are having DROP authority on the database then you must be having the DISPLAYDB authority.

Issue following commands to see if anything holding the tablespace.

-DIS DATABASE(databse name) SPACE(tablespace name) LOCKS

AND

-DIS DATABASE(databse name) SPACE(tablespace name) CLAIMERS

These commands will give you the current locks and the claimers information.

Thanks,
Amit