Does MaxDataVolumes auto-adjust?
In two databases, have noticed MaxDataVolumes changing without an administrator changing it. Is this normal or perhaps an un-documented feature?
In a production database, MaxDataVolumes was originally 12 and now after some months it is 15.
The auto_extend feature is activated and it has been active during this time since the number of data volumes has grown from the original two or three to eleven.
From the kernel messages history:
2016-11-13 13:18:23 RunTime 15: ( ) MaxDataVolumes=12
2016-12-04 13:48:35 RunTime 15: ( ) MaxDataVolumes=12
2017-01-29 09:26:04 0x1 15 RunTime ( ) MaxDataVolumes=15
The second database is for recovery testing and previously had recovered into it an older, smaller backup of the production database.
Recently a current, larger backup was to be recovered into it and the starting point was that there were two data volumes and MaxDataVolumes was 12. The initial recovery attempt failed because the data area was too small. After 9 more data volumes were added to get to 11, a “db_activate recover” was successful and then noticed that MaxDataVolumes was 21.
In neither database is MaxDataVolumes included in the output of “param_extgetall USERDEFINED=YES” and the kernel messages above confirm this in that have the empty parenthesis “( )” rather than “(U)”.
“param_getfull MaxDataVolumes” does not say that this is dynamic:
MaxDB 7.9.08.35 (for SAP Content Server)