SAP Knowledge Base Article - Preview

3525192 - Deadlock happened during drop partition -SAP ASE

Symptom

  • When trying to drop a partition with alter table with online option, it failed due to deadlock issue.

    Deadlock Id 3 detected
    Deadlock Id 3 detected. 1 deadlock chain(s) involved.
    Deadlock Id 3: Process (Familyid 0, Spid 1468, Suid 199) was executing a SELECT command in the procedure 'objid 0' at line 1 at nested level 2.

    EXEC IMMEDIATE:SQL Text:
    SQL Text: select top 16 * from <tablename> (omit) desc  at isolation read committed

    Deadlock Id 3: Process (Familyid 0, Spid 1742, Suid 191) was executing a ALTER TABLE command at line 7.
    Deadlock Id 3: Process 1742 was involved in transaction '$ALTER TABLE Journal DROP PARTITION ID=1136004047'.
    SQL Text: alter table <tablename> drop partition P071402 with online

    Deadlock Id 3: Process (Familyid 0, Spid 1742) was waiting for a 'exclusive guid' 'Schema Lock' lock on the '<tablename>' table in database '<DBNAME>' but process (Familyid 0, Spid 1468) already held a 'shared guid' lock on it.
  • The following signal 11 might be logged in the DB log.
    lock__print_deadlockchain -> traceprint -> vsnprintf -> _ndoprnt -> strlen


Read more...

Environment

SAP Adaptive Server Enterprise (ASE) 16.0

Product

SAP Adaptive Server Enterprise 16.0

Keywords

Shared GUID, exclusive guid, Schema Lock , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Problem

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.