How can a ROLLBACK occur on SELECT

Forgive my ignorance, but when reading from a table, i assume it puts up shared locks on the records that are selected. I am familiar with the concept of lock escalation but i thought it applied mainly to updates/inserts. Do lock escalation (from row level to table level) happen even when reads are being performed?

With badly written queries over large tables, the optimizer sometimes creates "temporary" tables and indexes that it uses to execute the query.

If you kill the query, it has to rollback those obects, too.

HTH,
DaveSlash

"Rollback" is the name of the state a db job goes into when an SQL step running under commitment control ends in error. Depending on how you terminated the db2 connect job, it is possible that the server is hung in a state where it is waitng for a response from the client.

Jobs running under commitment control go through a more complex recovery process, and it is possible that there can be more than one SQL statement within a transaction that s being rolled back.

Eventually it will probably time out. Sometimes the job log of the hung job will provide clues.

If the rollback job is not consuming resources, then it may just be hung. If so, you can also try to force the job to shutdown by ending it directly using wrkactjob option 4 or endjob. Assuming this is a qzdasoinit/qzdassinit job?


If this happens frequently, you need to make sure you are current on database ptfs.

Hi
you may need to include the

FOR READY ONLY

the the sql select statement otherwise dependant on the environment it may try to obtain some locks.

ie

select  * from my file FOR READY ONLY

Dave