Symptom
- SAP ASE database is not starting on Microsoft Windows VM.
- recovery seems to hang after 'roll forward message':
- server Roll forward transaction '$systsflush'.
- server Roll forward transaction '$systsflush'.
- After ASE reboot recovery is stuck and not moving during REDO phase
- Following error messages are reported in the Windows Event log:
- {Delayed Write Failed} Windows was unable to save all the data for the file E:\sybase\SID\sapdata_2\SID_data_002.dat; the data has been lost. This error may be caused if the device has been removed or the media is write-protected.
- Database load from backup fails with:
- ...
- Backup Server: 4.188.1.1: Database EP1: 234475088 kilobytes (86%) LOADED.
- Backup Server: 4.145.2.22: [105] Error for database/archive device while working on stripe device 'F:\BACKUP\SID\SID.DB.20170914.193751.000'.
- The i/o WriteFile call failed for device E:\sybase\SID\sapddata_... at offset 77800407040 for size 65536 bytes. Operating system error message:
- The requested operation could not be completed due to a file system limitation
- Msg 8009, Level 16, State 1:
- Server 'SID', Line 1:
- Error encountered by Backup Server. Please refer to Backup Server messages for details.
Read more...
Environment
- SAP Adaptive Server Enterprise (ASE) 15.7 for Business Suite (BS) and Business Warehouse (BW)
- SAP Adaptive Server Enterprise (ASE) 16.0 for Business Suite (BS) and Business Warehouse (BW)
- SAP NetWeaver (NW) - All versions
- Microsoft Windows
Product
SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 16.0 ; SAP NetWeaver all versions
Keywords
- Windows Event, performance, slow, ASE hang, sybase hung, database recovery, compression, compress, disk space, database load
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.