SAP Knowledge Base Article - Preview

1852243 - Error 1105 on replicated database - SAP ASE

Symptom

  • A replicated database runs out of log space with error 1105 messages in ASE errorlog:

Error: 1105, Severity: 17, State: 7 Can't allocate space for object 'syslogs' in database '<DBSID>' 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

  • "dump transaction <DBSID> with truncate_only" completes but does not clear any log space
  •  select * from master..syslogshold reports a long running process with name $replication_truncation_point:

dbid   reserved  spid   page  xactid  masterxactid          starttime                           name                                             
------  ------------- ------  ------  ---------  -----------------  -----------------------------  ------------------------------------------
   10               0      0    1234 0x000             0x000  May  7 2018 11:33AM $replication_truncation_point             


Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE)
  • SAP Replication Server (SRS)

Product

SAP Adaptive Server Enterprise all versions ; SAP Replication Server all versions

Keywords

dbcc settrunc, out of space, truncation point, transaction log, truncate , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-SYB-REP , Sybase Replication Server (standalone) , Problem

About this page

This 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.