3195468 - Auto-expansion of database device fails due to OS disk full, resulting in database corruption - SAP ASE

• Auto-expansion of a database fails due to OS file system being full
• The errors and issue caused may vary
• Typical example show errors including 5166 and 5113 in the ASE errorlog.
• As a result, the database device gets corrupted and raise errors like 692 or 823
• An error log sequence example shows: 
  
  Threshold action procedure 'sp_dbxt_extend_db' fired in db 'SID' on segment 'logsegment'. Space left: 65536 logical pages ('1024M').
  DISK RESIZE name = 'SID_log_001', size = '1024.0M' 
  basis_dsizecheck: attempt to write page (Offset low:92260055040, Offset High:290341504) on device 'Windows NT system error 112: Not enough space on disk.' failed, system error is: (null)
  dcreate: insufficient space on device 'H:\sybase\SID\saplog_1\SID_log_001.dat'.
  dresize: Cannot resize H:\sybase\SID\saplog_1\SID_log_001.dat. Windows NT system error 0: Unforseen error..
  Error: 5166, Severity: 16, State: 1
  DISK RESIZE encountered an error while attempting to open/resize the physical file 'H:\sybase\SID\saplog_1\SID_log_001.dat'. Please consult the ASE error log (in the ASE boot directory) for more details.
  Error: 5113, Severity: 17, State: 1
  Disk update for logical device = 'SID_log_001' with physical path 'H:\sybase\SID\saplog_1\SID_log_001.dat' and virtual device number 7 failed. Please refer to ASE errorlog for more information.
  ...
  Error: 692, Severity: 20, State: 1
  Uninitialized logical page '44737093' was read while accessing database 'SID' (4), object 'syslogs' (8), index 'syslogs' (0), partition 'syslogs_8' (8). Please contact SAP Technical Support.
  server  A transaction in database 'SID' (spid=83) has hit a fatal error during rollback. ASE will try to reboot and recover the database. The XREC_BEGINXACT of this failing transaction is (44725303, 101).
  
  
• In some cases, the following messages are reported when the auto extend fails, indicating negative free space on the device:
  
  Threshold action procedure 'sp_dbxt_extend_db' fired in db 'SID' on segment 'default'. Space left: 655360 logical pages ('10240M').
  DISK RESIZE name = 'SID_data_001', size = '10240.0M' -- Db: SID Segment: default
  dcreate: insufficient space on device 'F:\sybase\SID\sapdata_1\SID_data_001.dat'.
  Initializing 5242880 pages only; insufficient disk space.
  disk resize: Initialized 5242880 pages only; insufficient disk space.
  Successfully resized the device 'SID_data_001' to 96468984 kilobytes.
  sp_dbxt_do_resize_dev: Device SID_data_001 of size 94208M resized by -0.0078125M to a total size of 94207.9922M.
  Database 'SID' was altered by total size '0M' for segment 'default'.
  
  
  
• As result of this issue database backups fail
• With ASE Error 8006 and a stack trace that includes 'dbmap' functions
  
  Error: 8006, Severity: 20, State: 1
  ASE error detected by Backup Server. Refer to the preceding Backup Server message.
  SQL causing error : dump database SID using config = '<config>'
  
  as_send_db_map
  dmpld_send_dbmap
  dpdb_main
  
  
• And the Backup Server log includes additional errors, for example:
  
  Backup Server Internal Error: 4.76.3.3: Device F:\sybase\SID\sapdata_1\<SID>_data_001.dat: 12582912 is not a legal virtual
  
  
• Running sp_helpdevice, output shows negative free space on the device:
  
  SID_data_001         F:\sybase\SID\sapdata_1\SID_data_001.dat .....  32767.98 MB, Free: -0.02 MB

• SAP Adaptive Server Enterprise (ASE) 16.0
• Windows OS

auto-expansion, auto-extend, 1105, syslogs, 692,  823, "disk resize", 5113, basis_dsizecheck, CR827435, CR#827435, 827435 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , How To