SAP Knowledge Base Article - Preview

2156268 - Error 3475 process in syslogshold cannot be killed - SAP ASE

Symptom

  • Process in syslogshold can not be killed 
  • 3475 error reported in the ASE error log

WARNING - Fatal Error 3475 occurred at Mar 27 20XX  3:32PM.  Please note the error and time, and contact a user with System Administrator (SA) authorization.
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 'dbname' (id 10). This process will retry at  intervals of one minute.

  • 1105 error reported in the ASE error log

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

  • 12893 error reported in the ASE error log

Error: 12893, Severity: 10, State: 1
Processed 28400 allocation unit(s) out of 4000 units (allocation page 7270144). 710% completed.
Processed 28800 allocation unit(s) out of 4000 units (allocation page 7372544). 720% completed.
Processed 29200 allocation unit(s) out of 4000 units (allocation page 7474944). 730% completed.
Processed 29600 allocation unit(s) out of 4000 units (allocation page 7577344). 740% completed.
Processed 30000 allocation unit(s) out of 4000 units (allocation page 7679744). 750% completed.
Processed 30400 allocation unit(s) out of 4000 units (allocation page 7782144). 760% completed.
Processed 30800 allocation unit(s) out of 4000 units (allocation page 7884544). 770% completed.
Processed 31200 allocation unit(s) out of 4000 units (allocation page 7986944). 780% completed.
Processed 31600 allocation unit(s) out of 4000 units (allocation page 8089344). 790% completed.
Processed 32000 allocation unit(s) out of 4000 units (allocation page 8191744). 800% completed.
Processed 168001 allocation unit(s) out of 4000 units (allocation page 43008000). 2097% completed.
Processed 216001 allocation unit(s) out of 24000 units (allocation page 55296000). 349% completed.
Processed 336001 allocation unit(s) out of 16000 units (allocation page 86016000). 524% completed.
Processed 432001 allocation unit(s) out of 66000 units (allocation page 110592000). 127% completed.
Processed 728401 allocation unit(s) out of 90800 units (allocation page 186470400). 92% completed.
Rebuilt syslogs gam for dbid 10

  • Other errors are reported in the ASE error log

ERROR: Can't get a new log page in db 10. num_left=4 num_in_plc=4.

  • There are databases that have been set to use 'minimal dml logging' and it's in 'sp_helpdb' output.
  • Some process in the system is running minimally logged DMLs on tables having TEXT|IMAGE columns
  • There exists table having text | image column in 'minimal dml logging' database
  • Database becomes unresponsive
  • Syslogs can not be expanded
  • A reboot of ASE is required


Read more...

Environment

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

Product

SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 16.0

Keywords

zombie, freeze, kill, hang, Error3475, MLDML, LOB, 782102, CR782102, CR#782102, minimally logged DMLs, TEXT/IMAGE columns, dml_logging, dbcc tablealloc, checktable , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Bug Filed

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.