SAP Knowledge Base Article - Preview

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

Symptom

  • Auto-expansion of a database fails due to OS file system being full.

  • Database device corruption errors like Error 692 and 823 occur thereafter

  • Error 1105 followed by Error 692 is reported after the disk space  error:


    background task message: Threshold action procedure 'sp_dbxt_extend_db' fired in db 'PER' on segment 'logsegment'. Space left: 65536 logical pages ('1024M').
    background task message: ALTER DATABASE PER log on PER_log_001 = '947.0M' -- Segment: logsegmentbackground task message: ALTER DATABASE PER log on SID_log_001 = '947.0M' -- Segment: logsegment
    background task message: DISK RESIZE name = 'SID_log_001', size = '1024.0M' -- Db: PER Segment: logsegment
    kernel  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)
    kernel  dcreate: insufficient space on device 'H:\sybase\SID\saplog_1\SID_log_001.dat'.
    kernel  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\PER\saplog_1\PER_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\PER\saplog_1\PER_log_001.dat' and virtual device number 7 failed. Please refer to ASE errorlog for more information.
    Failed to execute the threshold procedure for database 4, segment 2, free space 65536.
    Space available in segment 'logsegment' has fallen critically low in database 'PER'. All future modifications to this database will be aborted until the transaction log is successfully dumped and space becomes available.
    Error: 1105, Severity: 17, State: 4
    Can't allocate space for object 'syslogs' in database 'PER' 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.
    Error: 2812, Severity: 16, State: 5
    Stored procedure 'sp_thresholdaction' not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output).
    Error: 1105, Severity: 17, State: 4
    Can't allocate space for object 'syslogs' in database 'PER' 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.
    ...
    ...
    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:

    background task message: Threshold action procedure 'sp_dbxt_extend_db' fired in db 'SID' on segment 'default'. Space left: 655360 logical pages ('10240M').
    background task message: 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.
    background task message: sp_dbxt_do_resize_dev: Device SID_data_001 of size 94208M resized by -0.0078125M to a total size of 94207.9922M.
    background task message: 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

      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


Read more...

Environment

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

Product

SAP Adaptive Server Enterprise 16.0

Keywords

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 , 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.