Ray
2006-09-18 10:00:13 UTC
The transaction log on one of the ASE 12.5 databases was full. It was
followed by an unexpected Instance crash.
When I tried to restart the ASE Server, the user databases could not
online with the following messages :
server Error: 1105, Severity: 17, State:3
server Can't allocate space for object 'syslogs' in database 'dbuser'
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 or sp_extendsegment to increase size of the segment.
server Error: 3475, Severity: 21, State:7
server There is no space available in SYSLOGS for process 1 to log a
record for which space has been reserved. This process will retry at
intervals of one minute. The internal error number is -4.
Anyone who can kindly help on this ?
followed by an unexpected Instance crash.
When I tried to restart the ASE Server, the user databases could not
online with the following messages :
server Error: 1105, Severity: 17, State:3
server Can't allocate space for object 'syslogs' in database 'dbuser'
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 or sp_extendsegment to increase size of the segment.
server Error: 3475, Severity: 21, State:7
server There is no space available in SYSLOGS for process 1 to log a
record for which space has been reserved. This process will retry at
intervals of one minute. The internal error number is -4.
Anyone who can kindly help on this ?