We have a production job 'A' which is failing due to 'Resource Unavailable' Issue. This Job establishes the quiesce point for tablespaces. The error message is as follows:
DSNT500I 178 04:13:42.01 DSNUGBAC - RESOURCE UNAVAILABLE
NAME DSNDB06 .SYSCOPY
This issue is forTablespace 'SYSCOPY' which is using database 'DSNDB06'. On checking the DB2 master log, we found that another production Job 'B' was holding the resource. This Job 'B' is used for recovery of tablespace and indexes for a particular db2 table. These Jobs "A' and 'B' have not changed in last many years.
When i looked at the SYSIBM.SYSTABLES and see SYSCOPY as a name. Is this table running out of space. The PCTPAGES is 98 – does that mean 98% full?
I can adjust the timing of these jobs so that these will not come in contention but for RCA, need to dig more. It's really odd that the entire tablespace SYSCOPY was locked when there is no lock escalation messages in the Db2 MSTR log. SYSCOPY is defined with LOCKRULE=’ANY’ which nearly always means page-locking but could truly mean “any” level DB2 decides and I don’t know if there is a way to tell exactly which mode DB2 chooses.
Any suggestion. Thanks a lot!