2163268 - Creating local indexes simultaneously on a partitioned table will put shared lock on the table instead of an exclusive lock resulting in deadlock. - ASE

Creating local indexes simultaneously on a semantically partitioned table results in deadlock.

Deadlock Id 3: Process (Familyid 0, Spid 18) was waiting for a 'shared row' lock on row 10 page 890881 of the 'sysstatistics' table in database 'stats_data' but process (Familyid 0, Spid 21) already held a 'exclusive row' lock on it.
Deadlock Id 3: Process (Familyid 0, Spid 21) was waiting for a 'shared row' lock on row 18 page 762113 of the 'sysstatistics' table in database 'stats_data' but process (Familyid 0, Spid 18) already held a 'exclusive row' lock on it.
Deadlock Id 3: Process (Familyid 0, Spid 21) was chosen as the victim.  Victim process host = `sunspot', user = `migration' program name = `isql' host processes = `4998'

• SAP Adaptive Server Enterprise (ASE) 15.7
• SAP Adaptive Server Enterprise (ASE) 16.0

statistics values , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , BC-SYB-ASE-CE , ASE Cluster Edition (Standalone) , Problem