Symptom
- Following error was reported in the ASE error log
kernel Listener with protocol tcp, <HOST>, port 4100 started.
server ERROR: Can't get a new log page in dbid 76 (num_left=18, num_in_plc=36, num_in_plc_at_start=36, num_newlogpgs_allocated=0).
server ERROR: Can't get a new log page in dbid 76 (num_left=18, num_in_plc=18, num_in_plc_at_start=18, num_newlogpgs_allocated=0).
server Rebuilt syslogs gam for dbid 76
server ERROR: Can't get a new log page in dbid 76 (num_left=18, num_in_plc=18, num_in_plc_at_start=18, num_newlogpgs_allocated=0).
server Error: 1105, Severity: 17, State: 12
server Can't allocate space for object 'syslogs' in database 'indexdb' 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.
server Error: 3475, Severity: 21, State: 7
server There is no space available in SYSLOGS to log a record for which space has been reserved in database 'indexdb' (id 76). This process will retry at intervals of one minute.
- Attempted to add log space but it was blocked by the CHKPOINT WRKR process
- After rebooting server not all log space was reclaimed
- Executed dbcc dbrepair(<database>, fixlogfreespace) in single-user mode, but the log space was still not freed.
- negative space count was reported on the log segment
Read more...
Environment
- SAP Adaptive Server Enterprise (ASE) 16.0 SP02
- SAP Adaptive Server Enterprise (ASE) 16.0 SP04
Product
Keywords
3475, CR 831018 , 831018, 1105 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Product Enhancement
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.
SAP Knowledge Base Article - Preview