There are different ways that orphan temporary tables can be stranded, for example:
- ASE errorlog may report errors like 3702 or 622.
- Space used by system tables such as syscolumns and syspartitions in one or more temporary databases may seem excessive
- A query causes the transaction log fill-up and be aborted by the ASE server.
- #temptables are not dropped from a temporary database
How are orphan temporary tables dropped from a temporary database, other than a reboot of the ASE server?
SAP Adaptive Server Enterprise (ASE) all versions
#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) , How To
About this pageThis 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.