Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

EnableDataVolumeBalancing not working?


we have MaxDB database: (upgraded from 7.8.01 BUILD 014-121-233-288

on May 2014)

running on Linux 2.6.32-431.17.1.el6.x86-64

Three days ago our database has stopped because of Data Area full.

We have Dynamic Data Area Adjustment: ON  (should add a new file at 90%)
A new file wasn't added automatically
There was enough filespace on the disk.

I have added two new files to database manually (files DATA0019, DATA0020).

Now (after 3 days), I see that data is not balanced between old and new files.
Old files are 99->100% full, new files are <>5% full.

EnableDataVolumeBalancing parameter is ON

We had some errors on 22nd of August:
Thread     0x27DB Task      -  2014-08-22 14:12:33 ERR RTEIO        126:  Medium write error on /sapdb/D86/sapdata/DISKD0014 after 3 retries, 'No space left on device' (28),_FILE=RTEIO_StreamMedium+noPIC.cpp,_LINE=3182

Thread     0x27DB Task      -  2014-08-22 13:25:00 ERR RTEIO        126:  Medium write error on /sapdb/D86/sapdata/DISKD0013 after 3 retries, 'No space left on device' (28),_FILE=RTEIO_StreamMedium+noPIC.cpp,_LINE=3182

Database was restarted 2 day ago.

What could be causing of not working Data Volume Balancing?

Former Member

Hi Daniel,

in regards to Volume Balancing, you probably have experienced a MaxDB bug fixed in version (not yet released) and version
The corresponding problem tracking# are 1242644 and 1242646 which you can look up at

Here is the 'feature'-description:
"Volume balancing now starts even when a new volume is added to a large number of existing volumes. Previously, this would not have changed the avearge filling threshold enough to trigger volume balancing".


and, yes, a new file should have been added automatically - any error in the database log file or any attempt to add a volume visible?

0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question