Version Control Migration getting SQLCODE = -911, ERROR REASON 00C9008E

Document ID : KB000008703
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

Migration getting SQLCODE = -911, ERROR REASON 00C9008E

-911                                                                       
                                                                           
 THE CURRENT UNIT OF WORK HAS BEEN ROLLED BACK DUE TO DEADLOCK OR TIMEOUT. 
 REASON reason-code, TYPE OF RESOURCE resource-type, AND RESOURCE NAME     
 resource-name                                                             

 

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.                                                              

 

Environment:
z/OS
Cause:

When selecting 10 or more objects for migration, get resource unavailable.

 

 

Full Error Message:

DSNT408I SQLCODE = -911, ERROR: THE CURRENT UNIT OF WORK HAS BEEN ROLLED BACK

DUE TO DEADLOCK OR TIMEOUT. REASON 00C9008E, TYPE OF RESOURCE

00000D01, AND RESOURCE NAME 00000476.00000041

DSNT418I SQLSTATE = 40001 SQLSTATE RETURN CODE

DSNT415I SQLERRP = DSNXRRC SQL PROCEDURE DETECTING ERROR

DSNT416I SQLERRD = -190 13172746 13172878 13226962 -975040511

536870912 SQL DIAGNOSTIC INFORMATION

DSNT416I SQLERRD = X'FFFFFF42' X'00C9000A' X'00C9008E' X'00C9D3D2'

X'C5E21001' X'20000000' SQL DIAGNOSTIC INFORMATION

ONLOC = UPDATE_ASC_LIST

ONCODE = 9

 

 

Resolution:

If using CE-Access, get a fix from this vendor so that it will not lock the tables.   Other possible resolutions below.

 

Additional Information:

1.  Reorg

2. Use SPUFI and run SQL SELECT * FROM DMAX and save output. At any command line after logging onto the Host Encyclopedia, reset DMAX by typing TSO %TIEMAX.  Leave all options blank to update all schemas or enter the schema to reset (ex: 9.2.A6 for Gen 8.x releases).  The SQL is included to see what changed.

3. Check the setting for LOCKMAX. Ask your System/CICS Admin for the setting. If set to 0, it disables lock escalations. This may have been changed since original install if any of the data tablespaces were altered.

4.  Schedule to run off-hours, during lunch, or with smaller sets of aggregate objects.

5.  Resubmitting the job for a few tries may eventually work.