Why am I unable to add a new volume when using the "dbmgr -addvol" command?
When running the command "dbmgr -addvol", the command prompt is returned and there is no indication of successfully adding a volume. Further evidence to confirm that this did not complete as expected can determined by looking for the presence of a new systemX file in the ...\CaliberRMServer\Versant\DB\SQMDBdirectory with an initial size of 368KB, or by running the"dbmgr -free" command to confirm that there is not an additional 2047M of free space in the DB.
For the particular issue outlined in this article, the symptom is seen when trying to add the 10th volume, or any volume after the tenth volume.
Once confirmed that the problem matches the above description,we may add a volume directly at the DB level without using thedbmgr utility.
From the command prompt:
- Stop CaliberRM Server by running "dbmgr-stop"
- Stop the database using "stopdb SQMDB"(adjust accordingly if not using the default DB name)
- To confirm which system volume you are adding, check the...\CaliberRMServer\Versant\DB\SQMDB directory for the name of the last system file and increment the suffix number by 1.
- Type "addvol" and enter to show the usage instructions
- The command should look something like "addvol -nsystem9 -p system9 -s 2047M SQMDB"
- There should be a confirmation message of "insertingsystem volume" before returning to the command prompt.
- Confirm the presence of a new system file in the...\CaliberRMServer\Versant\DB\SQMDB directory with an initial sizeof 368KB
- Once confirmed that the volume was added, the CaliberRM Server can be started again using "dbmgr -start"
For step by step screen shots of both the problem symptoms and the solution, please refer to the following document.