An 1105 message "Can't allocate space for object 'syslogs' in database 'tempdb' because 'logsegment' segment is full" may incorrectly be printed for tempdb.
Example of the message returned to the client:
Space available in the log segment has fallen critically low in database 'tempdb'.
All future modifications to this database will be aborted until the log is successfully
dumped and space becomes available.
Msg 1105, Level 17, State 4:
Server '<server>', Procedure 'sp_helpthreshold', Line 91:
Can't allocate space for object 'syslogs' in database 'tempdb' because 'logsegment'
segment is full/has no free extents. If you ran out of space in syslogs, dump the
transaction log. Otherwise, use ALTER DATABASE to increase the size of the segment.
(return status = -7)
Depending on if the 'abort tran on log full' tempdb database is set or not, the command will either be suspended or aborted.
- SAP Adaptive Server Enterprise (ASE) 15.7
- SAP Adaptive Server Enterprise (ASE) 16.0
syslogs, logsegment, transaction log , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Bug Filed
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.