You define additional data volumes to extend the data area for the database instance.
When doing so, you can define either the size of the new volume or a target fill level for the data area. If this target fill level is less than the current fill level, the Database Manager executes the command and adds as many volumes as required to reach the target fill level. If the current fill level is less than the target level, the command is not executed.
You can enter the name of the new volume directly in the DBM command or define it using Database Manager parameters (see: Configuration of the Database Manager).
You have the server authorization ParamFull or AccessUtility.
db_addvolume DATA [-fd <filling_level>] [<vol_name>] [<vol_type>] [<size>]
Options
Option |
Description |
<filling_level> |
Target fill level of the data area in percent |
<vol_name> |
Name of the device/file; can be defined with the Database Manager parameter AutoExtDir If you do not enter a name and the AutoExtDir parameter is not defined, the Database Manager creates the new data volume(s) in the run directory of the database instance. It generates the name based on the name of the last volume of this type that was created and assigns a sequence number or adds 1 to a number in the name. |
<vol_type> |
Type
of device/file to be added |
<size> |
Size of the volume to be added; can be defined with the Database Manager parameter AutoExtSize You can enter an absolute value or a percentage. The percentage is based on the entire data area. The default value is the size of the last data volume created. |
OK
<number>
<number> |
Only after use of the option -fd <filling_level>: Number of added volumes required to reach the target fill level |
In the event of errors, see Reply Format.
You define additional log volumes to extend the log area for the database instance.
You can enter the properties of the new volumes directly in the DBM command or define it using Database Manager parameters (see: Configuration of the Database Manager).
You can also use this DBM command to create log volumes using mirror volumes, if your database instance is already mirrored. If the database instance is not yet mirrored, use the DBM command for changing volume parameters to create the first mirror volume.
You have the server authorization ParamFull or AccessUtility.
db_addvolume LOG [<vol_name>] [<vol_type>] [<size>] [<mvol_definition>]
<mvol_definition>::= [<mvol_name>] [<mvol_type>]
Options
Option |
Description |
<vol_name> |
Name of the device/file; can be defined with the Database Manager parameter AutoExtDirLog If you do not enter a name and the AutoExtDirLog parameter is not defined, the Database Manager creates the new log volume in the run directory of the database instance. It generates a name based on the name of the last volume of this type that was created and assigns a sequence number or adds 1 to a number in the name. |
<vol_type> |
Type
of device/file to be added |
<size> |
Size
of the volume to be added; can be defined with the Database Manager parameter
AutoExtDirLog The default value is the size of the last log volume created. |
<mvol_name> |
Name of the mirror volume; can be defined with the Database Manager parameter AutoExtDirLogMirror If you do not enter a name and the AutoExtDirLogMirror parameter is not defined, the Database Manager creates the new log volume in the run directory of the database instance. |
<mvol_type> |
Type
of device/file that is to be added as a mirror volume The default value File. |
OK
<number>
<number> |
Only after use of the option -fd <filling_level>: Number of added volumes required to reach the target fill level |
In the event of errors, see Reply Format.