SAP Knowledge Base Article - Preview

2207667 - Multiple Errors Can't get a new log page in dbid xx 3475, and 1105 in the tempdb database - SAP ASE

Symptom

  • Getting multiple Errors "Can't get a new log page in dbid xx",
  • Errors 3475 followed by stack traces.
  • Errors 1105 in the tempdb database (however, this could happen on ANY database)

For example:

Error: 1105, Severity: 17, State: 5
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.
ERROR: Can't get a new log page in dbid 2 (num_left=1, num_in_plc=1, num_in_plc_at_start=1, num_newlogpgs_allocated=0).

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 'tempdb' (id 2). This process will retry at intervals of one minute.
ERROR: Can't get a new log page in dbid 2 (num_left=2, num_in_plc=2, num_in_plc_at_start=2, num_newlogpgs_allocated=0).

Error: 1105, Severity: 17, State: 7

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.


Read more...

Environment

SAP Adaptive Server Enterprise (ASE)

Product

SAP Adaptive Server Enterprise 15.7

Keywords

Transaction Log full timestamp recycle reboot sysusages "dbid = 2" , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , 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.