Symptom
You have scheduled the table reorg job with default options in DBA Planning Calendar.
You find it is in lock-wait status as per application snapshot.
Application status = Lock-wait
Status change time = 02/28/2017 01:40:41.346237
Application code page = 1208
Application country/region code = 1
DUOW correlation token = *LOCAL.DB2.170228155452
Application name = db2reorg
Application ID = *LOCAL.DB2.170228155452
Snapshot timestamp = 02/28/2017 02:08:41.227771
ID of agent holding lock = 12345
Application ID holding lock = *LOCAL.db2abc.170228160038
Lock name = 0x000A000000000000000000006F
Lock attributes = 0x00000000
Release flags = 0x00000000
Lock object type = Internal Online Backup Lock
Lock mode = Exclusive Lock (X)
Lock mode requested = Share Lock (S)
Name of tablespace holding lock = ABC#BTABD
Data Partition Id of table holding lock = 0
Lock wait start timestamp = 02/28/2017 01:40:41.346238
Read more...
Environment
SAP on IBM DB2 for Linux, UNIX, and Windows
Keywords
Lock-wait, Reorg, Backup, Online, Offline , KBA , lock , reorg , BC-DB-DB6-DBA , Database Administration , BC-DB-DB6 , DB2 Universal Database for Unix / NT , BC-DB-DB6-CCM , CCMS/Database Monitors , How To
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.