Recently I have come across an sql error while trying to execute a sql in DB2 version 7 from web application. The application is developed in Enterprise Generation Language (EGL). The query retrieves huge result set of around 14000 rows. The sql error reads as "UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE RESOURCE. REASON 00C90096, TYPE OF RESOURCE 00000302, AND RESOURCE NAME ....[sqlstate:57011][sqlcode:-904]". However the same sql is executed successfully from DB2 SQL client.
After lot of R&D, we tried to set isolation level in the SQL. By default db2 is set to Repeatable Read (RR) level. We have changed this level to Uncommitted Read (UR). Great it works.
Example
Select * from Emp order by empName WITH UR;
After lot of R&D, we tried to set isolation level in the SQL. By default db2 is set to Repeatable Read (RR) level. We have changed this level to Uncommitted Read (UR). Great it works.
Example
Select * from Emp order by empName WITH UR;
Regards
Monu
2 comments:
Well written article.
Using UR really helped me to solve
"UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE RESOURCE. REASON 00C90096, TYPE OF RESOURCE 00000302, AND RESOURCE NAME DPGRS6 .SPGRS63 .X'037BC0'"
Big lesson learnt that for any select sql queries, we need to add WITH UR. Big thanks !!!
Post a Comment