2938960 - dbcc orphantables falsely identifies an orphan and can cause 8201 error when dropped - SAP ASE

• If a table was incorrectly identified by dbcc orphantables("drop") as orphaned and is in use, an 8201 might be reported in the ASE errorlog along with a stack trace:

1> dbcc orphantables("drop")
2> go
Running DBCC ORPHANTABLES in DROP mode.
Dropped orphan temporary table #tab00000xxxxxxxxxxxx.
DBCC execution completed. If DBCC printed error messages, contact a user with
System Administrator (SA) role.

• Example of error 8201 with a stack trace:

Error: 8201, Severity: 26, State: 6

ucbacktrace+0x54()
terminate_process+0xb1e()
hdl_default+0x3b()
s_handle+0x454()
exc__raise+0x4a0()
exc_raise+0x10c()
des__unkeep+0x155()
des_unkeep_or_drop+0x265()
closetable+0x7eb()
close_range+0x166()
exectrig+0x80e()
s_execute+0xaede()

SAP Adaptive Server Enterprise 16.0 SP03 PL08 and later, and SP02 PL09

8201, Found orphan table, orphantables, des__unkeep, des_unkeep_or_drop, drop , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Bug Filed