on 06-15-2016 12:38 PM
Hi,
We have a few systems where MAXDATAVOLUME is too high:
MAXDATAVOLUME x file size is bigger than hard drive size.
We don't want to increase size of hard drive - because those databases are not growing fast and it would be waste of hundreds of gigabytes.
It is easy to increase MAXDATAVOLUME parameter - MaxDB Studio - change parameter - restart database - voila - works.
But is it possible to DECREASE?
When I have changed MAXDATAVOLUME to lower level (but still bigger than current number of active data files) and restart database - it comes back to previous (higher) value automatically.
Database version is: 7.8.02.41
MaxDB database studio version is: 7.9.09
--
Daniel
Hi Daniel,
maxdb adapt MAXDATAVOLUME automatically? This is curious.
Please attach diagpack.tgz after executing following command:
dbmcli -d <dbsid> -u <username>,<password> diag_pack
Best regards,
James
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Simon,
I'm surprised now
Yes you are right - I have checked many databases and MAXDATAVOLUME is equal to current volume number + 10
So - as it works automatically - how to protect system to against disk drive overflow?
And how it compares to setup of: Automatic Data Area Adjustment (ON/OFF)?
For me both does the same.
--
Daniel
Hi Daniel,
MaxDataVolumes only shows the number of data volumes you can have without restarting the MaxDB instance. No data volume is added automatically.
AFAIK the "Automatic Data Area Adjustment" does the same as you can do manually, it adds data volumes. I guess it can usually add up to 10 data volumes without restarting the instance.
So both options are different but have related meanings.
Regards,
Simon
User | Count |
---|---|
74 | |
10 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.