SAP Knowledge Base Article - Preview

3247394 - Error 3475 after loading a database dump - SAP ASE 16.0


  • Error 1105 on the default segment of the saptools database during SPA during recovery:

    ERROR: Can't get a new log page in dbid 4 (num_left=258, num_in_plc=259, num_in_plc_at_start=259, num_newlogpgs_allocated=0).
    ERROR: Can't get a new log page in dbid 4 (num_left=258, num_in_plc=258, num_in_plc_at_start=258, num_newlogpgs_allocated=0).
    Error: 1105, Severity: 17, State: 12
    Can't allocate space for object 'syslogs' in database 'DDD' 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.
    Rebuilt syslogs gam for dbid 4

  • The database did come online:

    Database 'DDD' is now online.

  • It was shortly followed by Error 3475:

    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 'DDD' (id 4). This process will retry at intervals of one minute.



  • SAP Adaptive Server Enterprise (ASE) 16.0 SP03 PL10 for Business Suite
  • SAP NetWeaver (NW) - All versions
  • SAP Solution Manager (SOLMAN) 7.x ABAP


SAP Adaptive Server Enterprise 16.0 ; SAP Solution Manager 7.2


CR827003, CR#827003, 827003 , KBA , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Known Error

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.