SAP Knowledge Base Article - Preview

2614731 - If database is blocked then unwanted database auto expansion may run through sp_thresholdaction - SAP ASE

Symptom

  • You have configured threshold action for automatic database expansion for the data and logsegments for the database. In general, when the data or logsegment for this database has reached to its threshold level, it will execute sp_thresholdaction to increase the database and device size.
  • But if the database alteration is not allowed immediately because of other reasons like its blocked by full dump databases then the threshold action may keep on checking and executing multiple times to increase the database segment size.
  • You may see multiple threshold action executed in the errorlog and also once the dump is completed you can see the database size got extended many time.

00:0017:00000:00645:2018/02/25 05:32:16.85 server background task message: Threshold action procedure 'sp_dbxt_extend_db' fired in db 'XXX' on segment 'default'. Space left: 1048576 logical pages ('16384M').
00:0013:00000:00270:2018/02/25 12:24:27.53 server background task message: Threshold action procedure 'sp_dbxt_extend_db' fired in db 'XXX' on segment 'default'. Space left: 1048576 logical pages ('16384M').
00:0013:00000:00177:2018/02/25 12:44:54.86 server background task message: Threshold action procedure 'sp_dbxt_extend_db' fired in db 'XXX' on segment 'default'. Space left: 1048576 logical pages ('16384M').
00:0021:00000:00332:2018/02/25 13:54:11.90 server background task message: Threshold action procedure 'sp_dbxt_extend_db' fired in db 'XXX' on segment 'default'. Space left: 1048576 logical pages ('16384M').
00:0010:00000:00800:2018/02/25 14:57:42.67 server background task message: Threshold action procedure 'sp_dbxt_extend_db' fired in db 'XXX
' on segment 'default'. Space left: 1048576 logical pages ('16384M').
00:0021:00000:00568:2018/02/25 20:06:00.23 server background task message: Threshold action procedure 'sp_dbxt_extend_db' fired in db 'XXX' on segment 'default'. Space left: 1048576 logical pages ('16384M').
00:0015:00000:00778:2018/02/25 20:22:49.58 server background task message: Threshold action procedure 'sp_dbxt_extend_db' fired in db 'XXX' on segment 'default'. Space left: 1048576 logical pages ('16384M').

  • Now once the lock is released for this database the space has been extended many times as below


00:0020:00000:00645:2018/02/25 20:56:38.27 server Extending database by 524288 pages (8192.0 megabytes) on disk XXX_data_005
00:0019:00000:00270:2018/02/25 21:01:27.83 server background task message: DISK RESIZE name = 'XXX_data_005', size = '8192.0M' -- Db: XXX Segment: default
00:0019:00000:00270:2018/02/25 21:01:27.83 server background task message: sp_dbxt_synchronize_expansion: Received control for token 4. (spid: 270). DISK RESIZE DB: 'XXX' Segment: 'default' Device: 'XXX_data_005'
00:0003:00000:00000:2018/02/25 21:01:27.86 kernel Performing space allocation for device '/sybase/XXX/sapdata_1/XXX_data_005.dat' (8.00 Gb). This may take some time.
00:0025:00000:00270:2018/02/25 21:02:12.38 server background task message: sp_dbxt_do_resize_dev: Device XXX_data_005 of size 155648M resized by 8192M to a total size of 163840M.
00:0025:00000:00270:2018/02/25 21:02:12.38 server background task message: ALTER DATABASE XXX on XXX_data_005 = '8192.0M' -- Segment: default
00:0025:00000:00270:2018/02/25 21:02:12.38 server Extending database by 524288 pages (8192.0 megabytes) on disk XXX_data_005
00:0008:00000:00177:2018/02/25 21:06:30.23 server background task message: DISK RESIZE name = 'XXX_data_005', size = '8192.0M' -- Db: XXX Segment: default


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

CR#813847, 813847, CR813847, auto database expansion, segment, threshold , KBA , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Problem

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.