DB2 Query failing due to ASUTIME Limit.

chandraBE · New User Joined: 02 Feb 2010 Posts: 44 Location: Bangalore

Hi,

The below Query was running fine in production from long time but today after DB2 Version 10 upgrade this giving SQLCODE = -905 for the RESOURCE NAME = ASUTIME.

Query:

DELETE FROM AAAA.TABLENAME POS
WHERE POS.IDNUMBER IN
(SELECT ALT.IDNUMBER FROM AAAA.TABLES2 ALT
WHERE ALT.CD_SYS = 'ABC')

Error LOG:

SQLERROR ON DELETE COMMAND, EXECUTE FUNCTION
RESULT OF SQL STATEMENT:
DSNT408I SQLCODE = -905, ERROR: UNSUCCESSFUL EXECUTION DUE TO RESOURCE LIMIT BEING EXCEEDED, RESOURCE NAME = ASUTIME LIMIT
= 000000000098 CPU SECONDS (000005000000 SERVICE UNITS) DERIVED FROM SYSIBM.DSNRLST01
DSNT418I SQLSTATE = 57014 SQLSTATE RETURN CODE
DSNT415I SQLERRP = DSNXRRC SQL PROCEDURE DETECTING ERROR
DSNT416I SQLERRD = 106 13172746 0 13820889 -1041948638 12714050 SQL DIAGNOSTIC INFORMATION
DSNT416I SQLERRD = X'0000006A' X'00C9000A' X'00000000' X'00D2E3D9' X'C1E52022' X'00C20042' SQL DIAGNOSTIC
INFORMATION

Can you anyone help me to resolve this issue on ASUTIME?.

Regards,
Chandra

sushanth bobby · Posted: Tue Aug 16, 2011 2:59 pm

Chandra,

chandraBE · New User Joined: 02 Feb 2010 Posts: 44 Location: Bangalore

Hi Sushanth,

Thanks for the Quick reply.

Its direct upgrade from DB2 version 8 to version 10.

I had ran an explain but dont see any difference. Can you help to understand how do we find the how much the ASUTIME required for the query?.

Thanks and Regards,
Chandra

sushanth bobby · Posted: Tue Aug 16, 2011 3:32 pm

chandra,

After running an EXPLAIN you should check the DSN_STATEMNT_TABLE for the service units.

Bring this issue to your DBA's attention, he/she might have changed the limits during the migration.

Thanks,
Sushanth