|The ScopeSET Support and Community Portal|
Sybase does not store data correctly, cannot add users, etc., the following type of errors appear in the:
Error: 1105, Severity: 17, State: 4 Can't allocate space for object 'syslogs' in database 'master' 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.
This is primarily caused by a lack of (manual) maintenance on the Sybase Server. As Ameos Models grow, log segments of individual databases need to be increased. Also, for Sybase Servers which do not reboot regularly, running the Ameos desktop's Admin -> Perform Manager Maintenance command is essential. See also "5 Repository Manager Maintenance" in the Online PDF documentation or
The following steps will usually help to solve the problem:
First, dump the transaction log: ()
isql -Usa Password:<SA_PASSWORD> 1> use master 2> go 1> dump transaction master with no_log 2> go
Now, the errorlog should show something like:
server WARNING: *************************** server Attempt by user 1 to dump xact on db master with NO_LOG server Attempt by user 1 to dump xact on db master with NO_LOG was successful server WARNING: ***************************
It might also be a good idea to extend the log segment of the master database by some MBs. Check how much space there is left on the master device by using the sp_helpdevice command, then:
1> alter database master 2> log on master = 8 3> with override 4> go
This extends the master log segment by 8MB (the threshold warbing can be ignored). If there's not enough space left on the master device, you canbefore running the alter database command.
If you have done this, restart the Sybase server and test it.
If Sybase is still not working, you have to increase the size of the segment 'logsegment' as mentioned in the errorlog with:
1> sp_extendsegment logsegment, master, master 2> go
The answer should be:
DBCC execution completed. If DBCC printed error messages, contact a user with System Administrator (SA) role. Segment extended. (return status = 0)
In many cases this will help. (Further details can be found in the above mentioned manual in the chapter "Troubleshooting a Sybase Server")
As last resort, see this Sybase article