Deadlocks or timeouts

Db2® might encounter a deadlock or timeout condition (SQLCODE -911) if it attempts to implement changes made in a File Manager/Db2 Edit session. If this occurs there is a delay, followed by the display of the SQL error pop-up panel with the explanation for the -911 SQLCODE.

If you encounter this error, be aware that:

• Changes made to any row marked with -911 have not been completed.
• Db2® has rolled back the current unit of work. This means that all uncommitted changes made in the current Edit session have been lost.
• After the rollback of the current unit of work, the data shown in the FM/Db2 Edit session might not reflect the current state of the data in the Db2® table.

The recommended course of action is to cancel the current Edit session and restart with a new copy of the data. If the problem persists contact your Db2® systems administrator for assistance in determining which other Db2® task is preventing access to the Db2® object.

Related tasks

• Ending a File Manager/Db2 editor session