SAP Knowledge Base Article - Preview

2356907 - How to recover a user database after error 1105 followed by error 3475 - SAP ASE


  • How to recover a user database when error 1105 followed by error 3475 was reported in the ASE errorlog?
  • From ASE errorlog you can see some messages like:

Space available in the log segment has fallen critically low in database 'database_name'. All future modifications to this database will be suspended until the log is successfully dumped and space becomes available.
Error: 1105, Severity: 17, State: 4
Can't allocate space for object 'syslogs' in database 'database_name' 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.
Error: 3475, Severity: 21, State: 7
There is no space available in SYSLOGS to log a record for which space has been reserved in database 'database_name' (id x). This process will retry at intervals of one minute.



  • SAP Adaptive Server Enterprise (ASE) 15.7
  • SAP Adaptive Server Enterprise (ASE) 16.0


SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 16.0


replicate, replication, RepAgent, usedextents, -32768, sysdatabases, status, bypass, by-pass, recovery, secondary, truncation, point, truncate, truncate_only, sp_stop_rep_agent, sp_start_rep_agent, settrunc, ltm, ignore, valid, log, space, syslogs, GA1105, "Guided Answers" , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

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