SAP Knowledge Base Article - Preview

2085398 - How to find and remove stranded or "orphan" temporary tables ? - SAP ASE


  • ASE errorlog may or may not report errors like 3702, 622, or others
  • Space used by system tables such as syscolumns and syspartitions in one or more temporary databases may seem excessive
  • There has been some kind of an error, such as if a query causes the transaction log fillup and get aborted by the ASE server according to the database option setting, the #-temporary tables do not get dropped from temp databases



SAP Adaptive Server Enterprise (ASE) all versions


SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 16.0 ; Sybase Adaptive Server Enterprise 12.5 ; Sybase Adaptive Server Enterprise 15.0 ; Sybase Adaptive Server Enterprise 15.5


#tables, objects, orphantables, temp, locks, tempdb, temporary database, orphan tables, orphaned #temporary tables, exclusive locks , 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 ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.