This section describes the ASMCMD disk group management commands.
Table 12-27 provides a summary of the disk group management commands.
Table 12-27 Summary of ASMCMD Disk group management commands
| Command | Description |
|---|---|
|
Changes a disk group (add, drop, or rebalance). |
|
|
Checks or repairs a disk group. |
|
|
Drops a disk group. |
|
|
Displays I/O statistics for disks. |
|
|
Lists the attributes of a disk group. |
|
|
Lists disk groups and their information. |
|
|
Lists disks Oracle ASM disks. |
|
|
Lists open devices. |
|
|
Creates a backup of the metadata of mounted disk groups. |
|
|
Restores disk groups from a backup of the metadata. |
|
|
Creates a disk group. |
|
|
Mounts a disk group. |
|
|
Offlines a disk or a failure group. |
|
|
Onlines a disk or a failure group. |
|
|
Rebalances a disk group. |
|
|
Relocates data in a range of physical blocks on a disk. |
|
|
Sets attributes in a disk group. |
|
|
Dismounts a disk group. |
Changes a disk group (adds disks, drops disks, resizes disks, or rebalances a disk group) based on an XML configuration file.
chdg { config_file.xml | 'contents_of_xml_file' }Table 12-28 lists the syntax options for the chdg command.
Table 12-28 Options for the chdg command
| Option | Description |
|---|---|
|
|
Name of the XML file that contains the changes for the disk group. For examples of the valid tags and XML configuration file, see Example 12-30 and Example 12-31. |
|
|
The XML script enclosed in single quotations. |
chdg modifies a disk group based on an XML configuration file. The modification includes adding or deleting disks from an existing disk group, and the setting rebalance power level. The power level can be set to the same values as the ASM_POWER_LIMIT initialization parameter. For information about the initialization parameter, see "ASM_POWER_LIMIT".
When adding disks to a disk group, the diskstring must be specified in a format similar to the ASM_DISKSTRING initialization parameter. For information about the initialization parameter, see "ASM_DISKSTRING".
The failure groups are optional parameters. The default causes every disk to belong to a its own failure group. For information about failure groups, see"Oracle ASM Failure Groups".
Dropping disks from a disk group can be performed through this operation. An individual disk can be referenced by its Oracle ASM disk name. A set of disks that belong to a failure group can be specified by the failure group name. For information about dropping disks, see"Dropping Disks from Disk Groups".
You can resize a disk inside a disk group with chdg. The resize operation fails if there is not enough space for storing data after the resize. For information about resizing disks, see"Resizing Disks in Disk Groups".
Example 12-30 shows the basic structure and the valid tags with their respective attributes for the chdg XML configuration file.
Example 12-30 Tags for the chdg XML configuration template
<chdg> update disk clause (add/delete disks/failure groups)
name disk group to change
power power to perform rebalance
<add> items to add are placed here
</add>
<drop> items to drop are placed here
</drop>
<fg> failure group
name failure group name
</fg>
<dsk> disk
name disk name
string disk path
size size of the disk to add
force true specifies to use the force option
</dsk>
</chdg>
For information about creating a disk group with ASMCMD mkdg, see "mkdg". For information about altering disk groups, see "Altering Disk Groups".
The following is an example of an XML configuration file for chdg. This XML file alters the disk group named data. The failure group fg1 is dropped and the disk data_0001 is also dropped. The /dev/disk5 disk is added to failure group fg2. The rebalance power level is set to 3.
Example 12-31 chdg sample XML configuration file
<chdg name="data" power="3">
<drop>
<fg name="fg1"></fg>
<dsk name="data_0001"/>
</drop>
<add>
<fg name="fg2">
<dsk string="/dev/disk5"/>
</fg>
</add>
</chdg>
The following are examples of the chdg command with the configuration file or configuration information on the command line.
Checks or repairs the metadata of a disk group.
chkdg [--repair] diskgroupTable 12-29 lists the syntax options for the chkdg command.
Table 12-29 Options for the chkdg command
| Option | Description |
|---|---|
|
|
Repairs the disk group. |
|
|
Name of disk group to check or repair. |
chkdg checks the metadata of a disk group for errors and optionally repairs the errors.
The following is an example of the chkdg command used to check and repair the data disk group.
Drops a disk group.
dropdg [-r -f] [-r] diskgroupTable 12-30 lists the syntax options for the dropdg command.
Table 12-30 Options for the dropdg command
| Option | Description |
|---|---|
|
|
Force the operation. Only applicable if the disk group cannot be mounted. |
|
|
Recursive, include contents. |
|
|
Name of disk group to drop. |
dropdg drops an existing disk group. The disk group should not be mounted on multiple nodes.
These are examples of the use of dropdg. The first example forces the drop of the disk group data, including any data in the disk group. The second example drops the disk group fra, including any data in the disk group.
Displays I/O statistics for Oracle ASM disks in mounted disk groups.
iostat [--suppressheader] [-et] [--io] [--region] [-G diskgroup] [interval]iostat lists disk group statistics using the V$ASM_DISK_IOSTAT view.
Table 12-31 lists the syntax options for the iostat command.
Table 12-31 Options for the iostat command
| Option | Description |
|---|---|
|
|
Displays error statistics (Read_Err, Write_Err). |
|
|
Displays statistics for the disk group name. |
|
|
Suppresses column headings. |
|
|
Displays information in number of I/Os, instead of bytes. |
|
|
Displays time statistics (Read_Time, Write_Time). |
|
|
Displays information for cold and hot disk regions (Cold_Reads, Cold_Writes, Hot_Reads, Hot_Writes). |
|
|
Refreshes the statistics display based on the interval value (seconds). Use Ctrl-C to stop the interval display. |
Table 12-32 shows the statistics for a disk group. To view the complete set of statistics for a disk group, use the V$ASM_DISK_IOSTAT view.
Table 12-32 Attribute descriptions for iostat command output
| Attribute Name | Description |
|---|---|
|
Group_Name |
Name of the disk group. |
|
Dsk_Name |
Name of the disk. |
|
Reads |
Number of bytes read from the disk. If the |
|
Writes |
Number of bytes written to the disk. If the |
|
Cold_Reads |
Number of bytes read from the cold disk region. If the |
|
Cold_Writes |
Number of bytes written from the cold disk region. If the |
|
Hot_Reads |
Number of bytes read from the hot disk region. If the |
|
Hot_Writes |
Number of bytes written to the hot disk region. If the |
|
Read_Err |
Number of failed I/O read requests for the disk. |
|
Write_Err |
Number of failed I/O write requests for the disk. |
|
Read_Time |
I/O time (in hundredths of a second) for read requests for the disk if the |
|
Write_Time |
I/O time (in hundredths of a second) for write requests for the disk if the |
If a refresh interval is not specified, the number displayed represents the total number of bytes or I/Os. If a refresh interval is specified, then the value displayed (bytes or I/Os) is the difference between the previous and current values, not the total value.
The following are examples of the iostat command. The first example displays disk I/O statistics for the data disk group in total number of bytes. The second example displays disk I/O statistics for the data disk group in total number of I/O operations.
Example 12-35 Using the ASMCMD iostat command
ASMCMD [+] > iostat -G data Group_Name Dsk_Name Reads Writes DATA DATA_0000 180488192 473707520 DATA DATA_0001 1089585152 469538816 DATA DATA_0002 191648256 489570304 DATA DATA_0003 175724032 424845824 DATA DATA_0004 183421952 781429248 DATA DATA_0005 1102540800 855269888 DATA DATA_0006 171290624 447662592 DATA DATA_0007 172281856 361337344 DATA DATA_0008 173225472 390840320 DATA DATA_0009 288497152 838680576 DATA DATA_0010 196657152 375764480 DATA DATA_0011 436420096 356003840 ASMCMD [+] > iostat --io -G data Group_Name Dsk_Name Reads Writes DATA DATA_0000 2801 34918 DATA DATA_0001 58301 35700 DATA DATA_0002 3320 36345 DATA DATA_0003 2816 10629 DATA DATA_0004 2883 34850 DATA DATA_0005 59306 38097 DATA DATA_0006 2151 10129 DATA DATA_0007 2686 10376 DATA DATA_0008 2105 8955 DATA DATA_0009 9121 36713 DATA DATA_0010 3557 8596 DATA DATA_0011 17458 9269
Lists the attributes of a disk group.
lsattr [--suppressheader][-G diskgroup ] [-lm] [pattern]Table 12-33 lists the syntax options for the lsattr command.
Table 12-33 Options for the lsattr command
| Option | Description |
|---|---|
|
|
Disk group name. |
|
|
Suppresses column headings. |
|
|
Display names with values. |
|
|
Displays additional information, such as the RO and Sys columns. |
|
|
Display the attributes that contain pattern expression. |
Information about disk group attributes is retrieved from the V$ASM_ATTRIBUTE view. For information about disk group attributes, see "Disk Group Attributes".
The RO (read-only) column identifies those attributes that can only be set when a disk group is created. The Sys column identifies those attributes that are system-created.
To display information about the disk group template attributes, see "lstmpl".
To set disk group attributes, see "setattr".
The following are examples of the lsattr command. The first displays information about all attributes for the data disk group. The second example displays only those attributes with names containing the string compat for the fra disk group. Note the use of both the % and * wildcard characters on Linux.
Example 12-36 Using the ASMCMD lsattr command
ASMCMD [+] > lsattr -G data -l Name Value access_control.enabled FALSE access_control.umask 066 au_size 1048576 cell.smart_scan_capable FALSE compatible.advm 11.2.0.0.0 compatible.asm 11.2.0.0.0 compatible.rdbms 11.2.0.0.0 disk_repair_time 3.6h sector_size 512 ASMCMD [+] > lsattr -G fra -l %compat* Name Value compatible.asm 11.2.0.0.0 compatible.rdbms 10.1.0.0.0
Lists mounted disk groups and their information. lsdg queries V$ASM_DISKGROUP_STAT by default. If the --discovery flag is specified, the V$ASM_DISKGROUP is queried instead. The output also includes notification of any current rebalance operation for a disk group. If a disk group is specified, then lsdg returns only information about that disk group.
lsdg [--suppressheader] [-g] [--discovery] [pattern]
Table 12-34 lists the options for the lsdg command.
Table 12-34 Options for the lsdg command
| Option | Description |
|---|---|
|
(none) |
Displays the disk group attributes listed in Table 12-35. |
|
|
Selects from |
|
|
Selects from |
|
|
Suppresses column headings. |
|
|
Returns only information about the specified disk group or disk groups that match the supplied pattern. See "Wildcard Characters". |
Table 12-35 shows the attributes for each disk group. To view the complete set of attributes for a disk group, use the V$ASM_DISKGROUP_STAT or V$ASM_DISKGROUP view.
See Also:
Oracle Database Reference for descriptions of disk group information displayed in theV$ASM_DISKGROUP viewTable 12-35 Attribute descriptions for lsdg command output
| Attribute Name | Description |
|---|---|
|
State |
State of the disk group. Values include |
|
Type |
Disk group redundancy ( |
|
Rebal |
|
|
Sector |
Sector size in bytes. |
|
Block |
Block size in bytes. |
|
AU |
Allocation unit size in bytes. |
|
Total_MB |
Size of the disk group in megabytes. |
|
Free_MB |
Free space in the disk group in megabytes, without regard to redundancy. From the |
|
Req_mir_free_MB |
Amount of space that must be available in the disk group to restore full redundancy after the most severe failure that can be tolerated by the disk group. This is the |
|
Usable_file_MB |
Amount of free space, adjusted for mirroring, that is available for new files. From the |
|
Offline_disks |
Number of offline disks in the disk group. Offline disks are eventually dropped. |
|
Voting_files |
Specifies whether the disk group contains voting files ( |
|
Name |
Disk group name. |
The following example lists the attributes of the data disk group.
Lists Oracle ASM disks.
lsdsk [--suppressheader] [-kptgMI] [-G diskgroup ] [ --member|--candidate] [--discovery][--statistics][pattern]Table 12-36 lists the options for the lsdsk command.
Table 12-36 Options for the lsdsk command
| Option | Description |
|---|---|
|
(none) |
Displays the |
|
|
Displays the |
|
|
Displays the |
|
|
Displays the |
|
|
Displays the |
|
|
Selects from |
|
|
Selects from |
|
|
Suppresses column headings. |
|
|
Scans disk headers for information rather than extracting the information from an Oracle ASM instance. This option forces non-connected mode. |
|
|
Restricts results to only those disks that belong to the group specified by |
|
|
Displays the disks that are visible to some but not all active instances. These are disks that, if included in a disk group, cause the mount of that disk group to fail on the instances where the disks are not visible. |
|
|
Restricts results to only disks having membership status equal to |
|
|
Restricts results to only disks having membership status equal to |
|
|
Returns only information about the specified disks that match the supplied pattern. |
The lsdsk command can run in connected or non-connected mode. The connected mode is always attempted first. The -I option forces non-connected mode.
In connected mode, lsdsk uses the V$ASM_DISK_STAT and V$ASM_DISK dynamic views to retrieve disk information. The V$ASM_DISK_STAT view is used by default.
In non-connected mode, lsdsk scans disk headers to retrieve disk information. Some information is not available in this mode and some options are not valid combinations with this mode.
Note:
The non-connected mode is not supported on Windows.pattern restricts the output to only disks that match the pattern specified. Wild-card characters and slashes (/ or \) can be part of the pattern. pattern should be specified as the last option for the command. For information about wildcards, see "Wildcard Characters".
The -k, -p, -t, and --statistics options modify how much information is displayed for each disk. If any combination of the options are specified, then the output shows the union of the attributes associated with each flag.
The following are examples of the lsdsk command. The first and second examples list information about disks in the data disk group. The third example lists information about candidate disks.
Example 12-38 Using the ASMCMD lsdsk command
ASMCMD [+] > lsdsk -t -G data
Create_Date Mount_Date Repair_Timer Path
13-JUL-09 13-JUL-09 0 /devices/diska1
13-JUL-09 13-JUL-09 0 /devices/diska2
13-JUL-09 13-JUL-09 0 /devices/diska3
13-JUL-09 13-JUL-09 0 /devices/diskb1
13-JUL-09 13-JUL-09 0 /devices/diskb2
13-JUL-09 13-JUL-09 0 /devices/diskb3
13-JUL-09 13-JUL-09 0 /devices/diskc1
13-JUL-09 13-JUL-09 0 /devices/diskc2
...
ASMCMD [+] > lsdsk -p -G data /devices/diska*
Group_Num Disk_Num Incarn Mount_Stat Header_Stat Mode_Stat State Path
1 0 2105454210 CACHED MEMBER ONLINE NORMAL /devices/diska1
1 1 2105454199 CACHED MEMBER ONLINE NORMAL /devices/diska2
1 2 2105454205 CACHED MEMBER ONLINE NORMAL /devices/diska3
ASMCMD [+] > lsdsk --candidate -p
Group_Num Disk_Num Incarn Mount_Stat Header_Stat Mode_Stat State Path
0 5 2105454171 CLOSED CANDIDATE ONLINE NORMAL /devices/diske1
0 25 2105454191 CLOSED CANDIDATE ONLINE NORMAL /devices/diske2
0 18 2105454184 CLOSED CANDIDATE ONLINE NORMAL /devices/diske3
0 31 2105454197 CLOSED CANDIDATE ONLINE NORMAL /devices/diskk1
0 21 2105454187 CLOSED CANDIDATE ONLINE NORMAL /devices/diskk2
0 26 2105454192 CLOSED CANDIDATE ONLINE NORMAL /devices/diskk3
0 14 2105454180 CLOSED CANDIDATE ONLINE NORMAL /devices/diskl1
...
Lists the open Oracle ASM disks.
lsod [--suppressheader] [-G diskgroup] [--process process] [pattern]Table 12-37 lists the syntax options for the lsod command.
Table 12-37 Options for the lsod command
| Option | Description |
|---|---|
|
|
Suppresses column header information from the output. |
|
|
Specifies the disk group that contains the open disks. |
|
|
Specifies a pattern to filter the list of processes. |
|
|
Specifies a pattern to filter the list of disks. |
The rebalance operation (RBAL) opens a disk both globally and locally so the same disk may be listed twice in the output for the RBAL process.
The following are examples of the lsod command. The first example lists the open devices associated with the data disk group and the LGWR process. The second example lists the open devices associated with the LGWR process for disks that match the diska pattern.
Example 12-39 Using the ASMCMD lsod command
ASMCMD [+] > lsod -G data --process *LGWR* Instance Process OSPID Path 1 oracle@dadvmn0652 (LGWR) 26593 /devices/diska1 1 oracle@dadvmn0652 (LGWR) 26593 /devices/diska2 1 oracle@dadvmn0652 (LGWR) 26593 /devices/diska3 1 oracle@dadvmn0652 (LGWR) 26593 /devices/diskb1 1 oracle@dadvmn0652 (LGWR) 26593 /devices/diskb2 1 oracle@dadvmn0652 (LGWR) 26593 /devices/diskb3 1 oracle@dadvmn0652 (LGWR) 26593 /devices/diskd1 ASMCMD [+] > lsod --process *LGWR* *diska* Instance Process OSPID Path 1 oracle@dadvmn0652 (LGWR) 26593 /devices/diska1 1 oracle@dadvmn0652 (LGWR) 26593 /devices/diska2 1 oracle@dadvmn0652 (LGWR) 26593 /devices/diska3
For another example of the lsod command, see Example 12-2.
The md_backup command creates a backup file containing metadata for one or more disk groups.
md_backup backup_file [-G 'diskgroup [,diskgroup,...]']Table 12-38 describes the options for the md_backup command.
Table 12-38 Options for the md_backup command
| Option | Description |
|---|---|
|
|
Specifies the backup file in which you want to store the metadata. |
|
|
Specifies the disk group name of the disk group that must be backed up |
By default all the mounted disk groups are included in the backup file, which is saved in the current working directory if a path is not specified with the file name.
Oracle Automatic Storage Management Cluster File System (Oracle ACFS) volume and file system information is not backed up.
The first example shows the use of the backup command when run without the disk group option. This example backs up all the mounted disk groups and creates the backup image in the /scratch/backup/alldgs20100422 file. The second example creates a backup of the data disk group. The metadata backup that this example creates is saved in the /scratch/backup/data20100422 file.
Example 12-40 Using the ASMCMD md_backup command
ASMCMD [+] > md_backup /scratch/backup/alldgs20100422 Disk group metadata to be backed up: DATA Disk group metadata to be backed up: FRA Current alias directory path: ORCL/ONLINELOG Current alias directory path: ORCL/PARAMETERFILE Current alias directory path: ORCL Current alias directory path: ASM Current alias directory path: ORCL/DATAFILE Current alias directory path: ORCL/CONTROLFILE Current alias directory path: ASM/ASMPARAMETERFILE Current alias directory path: ORCL/TEMPFILE Current alias directory path: ORCL/ARCHIVELOG/2010_04_20 Current alias directory path: ORCL Current alias directory path: ORCL/BACKUPSET/2010_04_21 Current alias directory path: ORCL/ARCHIVELOG/2010_04_19 Current alias directory path: ORCL/BACKUPSET/2010_04_22 Current alias directory path: ORCL/ONLINELOG Current alias directory path: ORCL/BACKUPSET/2010_04_20 Current alias directory path: ORCL/ARCHIVELOG Current alias directory path: ORCL/BACKUPSET Current alias directory path: ORCL/ARCHIVELOG/2010_04_22 Current alias directory path: ORCL/DATAFILE Current alias directory path: ORCL/CONTROLFILE Current alias directory path: ORCL/ARCHIVELOG/2010_04_21 ASMCMD [+] > md_backup /scratch/backup/data20100422 -G data Disk group metadata to be backed up: DATA Current alias directory path: ORCL/ONLINELOG Current alias directory path: ASM Current alias directory path: ORCL/CONTROLFILE Current alias directory path: ASM/ASMPARAMETERFILE Current alias directory path: ORCL/PARAMETERFILE Current alias directory path: ORCL Current alias directory path: ORCL/DATAFILE Current alias directory path: ORCL/TEMPFILE
The md_restore command restores disk groups from a metadata backup file.
md_restore backup_file [--silent] [--full|--nodg|--newdg -o 'old_diskgroup:new_diskgroup [,...]'] [-S sql_script_file] [-G 'diskgroup [,diskgroup...]']Table 12-39 describes the options for the md_restore command.
Table 12-39 Options for the md_restore command
| Option | Description |
|---|---|
|
|
Reads the metadata information from |
|
|
Ignore errors. Typically, if |
|
|
Specifies to create a disk group and restore metadata. |
|
|
Specifies to restore metadata only. |
|
|
Specifies to create a disk group with a different name when restoring metadata. The |
|
|
Write SQL commands to the specified SQL script file instead of executing the commands. |
|
|
Select the disk groups to be restored. If no disk groups are defined, then all disk groups are restored. |
The first example restores the disk group data from the backup script and creates a copy. The second example takes an existing disk group data and restores its metadata. The third example restores disk group data completely but the new disk group that is created is named data2. The fourth example restores from the backup file after applying the overrides defined in the override.sql script file.
Example 12-41 Using the ASMCMD md_restore command
ASMCMD [+] > md_restore –-full –G data –-silent /scratch/backup/alldgs20100422 ASMCMD [+] > md_restore –-nodg –G data –-silent /scratch/backup/alldgs20100422 ASMCMD [+] > md_restore –-newdg -o 'data:data2' --silent /scratch/backup/data20100422 ASMCMD [+] > md_restore -S override.sql --silent /scratch/backup/data20100422
Creates a disk group based on an XML configuration file.
mkdg { config_file.xml | 'contents_of_xml_file' }Table 12-40 lists the syntax options for the mkdg command.
Table 12-40 Options for the mkdg command
| Option | Description |
|---|---|
|
|
Name of the XML file that contains the configuration for the new disk group. For examples of the valid tags and XML configuration file, see Example 12-42 and Example 12-43. |
|
|
The XML script enclosed in single quotations. |
mkdg creates a new disk group with an XML configuration file that specifies the name of the disk group, redundancy, attributes, and paths of the disks that form the disk group. Redundancy is an optional parameter; the default is normal redundancy. For some types of redundancy, disks are required to be gathered into failure groups. In the case that failure groups are not specified for a disk group, each disk in the disk group belongs to its own failure group.
Note that mkdg only mounts a disk group on the local node.
It is possible to set some disk group attribute values during disk group creation. Some attributes, such as AU_SIZE and SECTOR_SIZE, can be set only during disk group creation. For more information about disk groups attributes, refer to "Disk Group Attributes".
The default disk group compatibility settings are 10.1 for Oracle ASM compatibility, 10.1 for database compatibility, and no value for Oracle ADVM compatibility. For information about disk group compatibility attributes, see "Disk Group Compatibility".
Example 12-42 shows the basic structure and the valid tags with their respective attributes for the mkdg XML configuration file.
Example 12-42 Tags for mkdg XML configuration file
<dg> disk group
name disk group name
redundancy normal, external, high
<fg> failure group
name failure group name
</fg>
<dsk> disk
name disk name
string disk path
size size of the disk to add
force true specifies to use the force option
</dsk>
<a> attribute
name attribute name
value attribute value
</a>
</dg>
For information about altering a disk group with ASMCMD chdg, see "chdg". For information about creating a disk group, see "Creating Disk Groups".
The following is an example of an XML configuration file for mkdg. The configuration file creates a disk group named data with normal redundancy. Two failure groups, fg1 and fg2, are created, each with two disks identified by associated disk strings. The disk group compatibility attributes are all set to 11.2.
Example 12-43 mkdg sample XML configuration file
<dg name="data" redundancy="normal">
<fg name="fg1">
<dsk string="/dev/disk1"/>
<dsk string="/dev/disk2"/>
</fg>
<fg name="fg2">
<dsk string="/dev/disk3"/>
<dsk string="/dev/disk4"/>
</fg>
<a name="compatible.asm" value="11.2"/>
<a name="compatible.rdbms" value="11.2"/>
<a name="compatible.advm" value="11.2"/>
</dg>
The following are examples of the mkdg command. The first example runs mkdg with an XML configuration file in the directory where ASMCMD was started. The second example runs mkdg using information on the command line.
Mounts a disk group.
mount [--restrict] { [-a] | [-f] diskgroup[ diskgroup ...] }Table 12-41 lists the syntax options for the mount command.
Table 12-41 Options for the mount command
| Option | Description |
|---|---|
|
|
Name of the disk group. |
|
|
Mounts all disk groups. |
|
|
Mounts in restricted mode. |
|
|
Forces the mount operation. |
This operation mounts one or more disk groups. A disk group can be mounted with or without force or restricted options. For more information about mounting disk groups, see "Mounting and Dismounting Disk Groups".
The following are examples of the mount command showing the use of the force, restrict, and all options.
Offline disks or failure groups that belong to a disk group.
offline -G diskgroup { -F failgroup |-D disk} [-t {minutes | hours}]Table 12-42 lists the syntax options for the offline command.
Table 12-42 Options for the offline command
| Option | Description |
|---|---|
|
|
Disk group name. |
|
|
Failure group name. |
|
|
Specifies a single disk name. |
|
|
Specifies the time before the specified disk is dropped as |
When a failure group is specified, this implies all the disks that belong to it should be offlined.
The following are examples of the offline command. The first example offlines the failgroup1 failure group of the data disk group. The second example offlines the data_0001 disk of the data disk group with a time of 1.5 hours before the disk is dropped.
Online all disks, a single disk, or a failure group that belongs to a disk group.
online -G diskgroup { -a | -F failgroup |-D disk} [-w]Table 12-43 lists the syntax options for the online command.
Table 12-43 Options for the online command
| Option | Description |
|---|---|
|
|
Online all offline disks in the disk group. |
|
|
Disk group name. |
|
|
Failure group name. |
|
|
Disk name. |
|
|
Wait option. Causes ASMCMD to wait for the disk group to be rebalanced before returning control to the user. The default is not waiting. |
When a failure group is specified, this implies all the disks that belong to it should be onlined.
The following are examples of the online command. The first example onlines all disks in the failgroup1 failure group of the data disk group with the wait option enabled. The second example onlines the data_0001 disk in the data disk group.
Rebalances a disk group.
rebal [--power power] [-w] diskgroupTable 12-44 lists the syntax options for the rebal command.
Table 12-44 Options for the rebal command
| Option | Description |
|---|---|
|
|
Disk group name. |
|
|
Power setting. |
|
|
Wait option. Causes ASMCMD to wait for the disk group to be rebalanced before returning control to the user. The default is not waiting. |
The power level can be set to the same values as the ASM_POWER_LIMIT initialization parameter. A value of 0 disables rebalancing. If the rebalance power is not specified, the value defaults to the setting of the ASM_POWER_LIMIT initialization parameter. For information about the power level, see "ASM_POWER_LIMIT" and "Tuning Rebalance Operations".
You can determine if a rebalance operation is occurring with the ASMCMD lsop command. See "lsop". For more information about rebalancing a disk group, see "Manually Rebalancing Disk Groups".
The following is an example of the rebal command that rebalances the fra disk group with a power level set to 4.
Marks a range of blocks as unusable on the disk and relocates any data allocated in that range.
remap diskgroup disk block_range
Table 12-45 lists the syntax options for the remap command.
Table 12-45 Options for the remap command
| Option | Description |
|---|---|
|
|
Disk group name in which a disk must have data relocated. |
|
|
Name of the disk that must have data relocated. The name must match the |
|
|
Range of physical blocks to relocate in the format |
The remap command only relocates blocks. It does not correct or repair blocks that contain corrupted contents. The command uses a physical block size based on the SECTOR_SIZE disk group attribute.
The first example remaps blocks 5000 through 5999 for disk DATA_0001 in disk group DATA. The second example remaps blocks 6230 through 6339 for disk FRA_0002 in disk group FRA
Sets the attributes for an Oracle ASM disk group.
setattr -G diskgroup attribute_name attribute_valueTable 12-46 lists the syntax options for the setattr command.
Table 12-46 Options for the setattr command
| Option | Description |
|---|---|
|
|
Disk group name. |
|
|
Name of the attribute. |
|
|
Value of the attribute. |
The COMPATIBLE.ASM attribute must be advanced before advancing other disk group compatibility attributes and its value must be greater than or equal to the value of other disk group compatibility attributes.
For information about disk group attributes, see "Disk Group Attributes".
The following are examples of the setattr command. The first example sets the disk group attribute COMPATIBLE.ASM to 11.2 for the data disk group. The second example sets the disk group attribute COMPATIBLE.RDBMS to 11.2 for the data disk group.
Dismounts a disk group.
umount { -a | [-f] diskgroup }Table 12-47 lists the syntax options for the umount command.
Table 12-47 Options for the umount command
| Option | Description |
|---|---|
|
|
Name of the disk group. |
|
|
Dismounts all mounted disk groups. These disk groups are listed in the output of the |
|
|
Forces the dismount operation. |
The following are examples of the umount command. The first example dismounts all disk groups mounted on the Oracle ASM instance. The second example forces the dismount of the data disk group.