Oracle ASMCMD is ASM command-line utility that you can use to manage Oracle ASM instances, disk groups, file access control for disk groups, files and directories within disk groups, templates for disk groups, and volumes.
When you start Oracle ASMCMD, the current directory is set to root (+). For an Oracle ASM Instance with two disk groups, for example, data and fra, entering an ls command with the root directory as the current directory produces the following output:
ASMCMD> ls data/ fra/
The following example demonstrates navigating the Oracle ASM directory tree (refer to the fully qualified file name shown previously):
ASMCMD> cd +data/orcl/CONTROLFILE ASMCMD> ls Current.256.541956473 Current.257.541956475
You can create your own directories as subdirectories of the system-generated directories using the ASMCMD mkdir command. The directories that you create can have subdirectories, and you can navigate the hierarchy of both system-generated directories and user-created directories with the cd command.
The following example creates the directory mydir under orcl in the disk group data:
ASMCMD> mkdir +data/orcl/mydirIf you start ASMCMD with the -p flag, then ASMCMD shows the current directory as part of its prompt.
$ asmcmd -p ASMCMD [+] > cd data ASMCMD [+data] >
Displaying the ASMCMD Version Number
You can specify the -V option when starting asmcmd to display the asmcmd version number. After displaying the version number, asmcmd immediately exits.
For example:
$ asmcmd -V asmcmd version 19.0.0.0.0
Using an absolute path enables the command to access the file or directory regardless of where the current directory is set. The following rm command uses an absolute path for the file name:
ASMCMD [+] > rm +data/orcl/datafile/users.259.555341963
The following cd command uses an absolute path to the directory.
ASMCMD [+data/mydir] > cd +data/orcl/CONTROLFILE
A relative path includes only the part of the file name or directory name that is not part of the current directory. That is, the path to the file or directory is relative to the current directory.
In the following example, the rm command operates on the file undotbs1.272.557429239, which in this case is a relative path. ASMCMD appends the current directory to the command argument to obtain the absolute path to the file. In this example this is +data/orcl/DATAFILE/undotbs1.272.557429239.
ASMCMD [+] > cd +data ASMCMD [+data] > cd orcl/DATAFILE ASMCMD [+data/orcl/DATAFILE] > ls EXAMPLE.269.555342243 SYSAUX.257.555341961 SYSTEM.256.555341961 UNDOTBS1.258.555341963 UNDOTBS1.272.557429239 USERS.259.555341963 ASMCMD [+data/orcl/DATAFILE] > rm undotbs1.272.557429239
Paths to directories can also be relative. You can go up or down the hierarchy of the current directory tree branch by providing a directory argument to the cd command whose path is relative to the current directory.
In addition, you can use the pseudo-directories “.” and “..” rather than a directory name. The “.” pseudo-directory is the current directory. The “..” pseudo-directory is the parent directory of the current directory.
The following example demonstrates how to use relative directory paths and pseudo-directories:
ASMCMD [+data/orcl] > cd DATAFILE ASMCMD [+data/orcl/DATAFILE] >cd .. ASMCMD [+data/orcl] >
Using wildcards with ASMCMD commands
ASMCMD [+] > cd +data/orcl/*FILE ASMCMD-08005: +data/orcl/*FILE: ambiguous ASMCMD [+] > cd +data/orcl/C* ASMCMD [+data/orcl/CONTROLFILE] > ASMCMD [+] > ls +fra/orcl/A% 2009_07_13/ 2009_07_14/ ASMCMD [+] > ls +fra/orcl/ARCHIVELOG/2009% +fra/orcl/ARCHIVELOG/2009_07_13/: thread_1_seq_3.260.692103543 thread_1_seq_4.261.692108897 thread_1_seq_5.262.692125993 thread_1_seq_6.263.692140729 thread_1_seq_7.264.692143333 +fra/orcl/ARCHIVELOG/2009_07_14/: thread_1_seq_8.271.692158265 thread_1_seq_9.272.692174597 ASMCMD [+] > ls data/orcl/* +data/orcl/CONTROLFILE/: Current.260.692103157 +data/orcl/DATAFILE/: EXAMPLE.265.692103187 SYSAUX.257.692103045 SYSTEM.256.692103045 UNDOTBS1.258.692103045 USERS.259.692103045 +data/orcl/ONLINELOG/: group_1.261.692103161 group_2.262.692103165 group_3.263.692103169 +data/orcl/PARAMETERFILE/: spfile.266.692103315 +data/orcl/TEMPFILE/: TEMP.264.692103181 spfileorcl.ora
Specifying the Verbose Mode
You can specify the -v option with the asmcmd command to display additional information with some commands to help users diagnose problems as shown in the following example:
$ asmcmd -v debug
The syntax for starting ASMCMD in interactive mode is:
asmcmd [-V]
asmcmd [--nocp] [-v {errors|warnings|normal|info|debug}]
[--privilege connection_type ] [-p]
[--inst instance_name] [--discover]Running ASMCMD commands in noninteractive mode:-
$ asmcmd ls -l State Type Rebal Name MOUNTED NORMAL N DATA/ MOUNTED NORMAL N FRA/ $ asmcmd lsod --suppressheader -G data > my_lsod_test $ asmcmd lsdsk -G data '/devices/diska*' Path /devices/diska1 /devices/diska2 /devices/diska3
Displaying a return code when running ASMCMD in noninteractive mode
$ asmcmd ls -l dat ASMCMD-08001: diskgroup 'dat' does not exist or is not mounted $ echo $? 255
Running ASMCMD commands in a script
#!/bin/sh for ((i = 1; i <=3; i++)) do asmcmd lsdsk -G data '/devices/diska'$i done $ ./asmcmd_test_script Path /devices/diska1 Path /devices/diska2 Path /devices/diska3
Getting Help
Type help at the ASMCMD prompt or as a command in noninteractive mode to view general information about ASMCMD and a list of available ASMCMD commands.
You can type help command to display help text for a specific command, including usage information about how to run the command with its options.
The following is an example of the use of the help command.
Displaying ASMCMD help text
ASMCMD [+] > help startup
startup [--nomount] [--restrict] [--pfile <pfile.ora>]
Start the ASM instance.
[--nomount] specifies the nomount option.
[--restrict] start the instance in restricted mode.
[--pfile <pfile.ora>] specifies the location of the pfile.Using the ASMCMD lsct command
ASMCMD [+] > lsct data DB_Name Status Software_Version Compatible_version Instance_Name Disk_Group +ASM CONNECTED 19.0.0.0.0 19.0.0.0.0 +ASM DATA asmvol CONNECTED 19.0.0.0.0 19.0.0.0.0 +ASM DATA orcl CONNECTED 19.0.0.0.0 19.0.0.0.0 orcl DATA
lsop
Lists the current operations on a disk group in an Oracle ASM instance.
Using the ASMCMD lsop command
ASMCMD [+] > lsop Group_Name Dsk_Num State Power DATA REBAL WAIT 2 ASMCMD [+] > lsop Group_Name Dsk_Num State Power FRA REBAL REAP 3
lspwusr
List the users from the local Oracle ASM password file.
Using the ASMCMD lspwusr command
ASMCMD [+] > lspwusr
Username sysdba sysoper sysasm
SYS TRUE TRUE TRUE
ASMSNMP TRUE FALSE FALSE orapwusr
Add, drop, or modify an Oracle ASM password file user.
Using the ASMCMD orapwusr command
ASMCMD [+] > orapwusr --add hruser
pwcopy
Copies an Oracle ASM or database instance password file to the specified location.
Using the ASMCMD pwcopy command
ASMCMD [+] > pwcopy --asm +DATA/orapwasm +FRA/orapwasm_new copying +DATA/orapwasm -> +FRA/orapwasm_new
showclustermode
Displays the current mode of the Oracle ASM cluster.
showclustermode displays the mode that the Oracle ASM cluster is currently in. The possible return values are ASM cluster : Flex mode enabled or ASM cluster : Flex mode disabled.
The following example shows the use of the showclustermode command.
Using the ASMCMD showclustermode command
ASMCMD [+] > showclustermode ASM cluster : Flex mode disabled
showclusterstate
Displays the current state of the cluster.
showclusterstate displays the state that the Oracle ASM cluster is currently in. The possible values returned are Normal, In Rolling Patch, or In Rolling Upgrade mode.
Example
This example shows the use of the showclusterstate command.
Using the ASMCMD showclusterstate command
ASMCMD [+] > showclusterstate
showpatches
Lists the patches applied on the Oracle Grid Infrastructure home.
This example shows the use of the showpatches command.
Using the ASMCMD showpatches command
ASMCMD [+] > showpatches -l Oracle ASM release patch level is [0] and no patches have been applied on the local node. The release patch string is [18.1.0.0.0].
showversion
Displays the patch levels of the Oracle ASM cluster release and software.
This example shows the use of the showversion command.
Using the ASMCMD showversion command
ASMCMD [+] > showversion --active Oracle ASM active version on the cluster is [19.0.0.0.0]. The cluster upgrade state is [NORMAL]. The cluster active patch level is [0].
shutdown
Shuts down an instance.
The following are examples of the shutdown command. The first example performs a shut down of the Oracle ASM instance with normal action. The second example performs a shut down with immediate action. The third example performs a shut down that aborts all existing operations.
Using the ASMCMD shutdown command
ASMCMD [+] > shutdown --target ASM --normal ASMCMD [+] > shutdown --target ASM --immediate ASMCMD [+] > shutdown --target ASM --abort
spbackup
Backs up an Oracle ASM SPFILE to a backup file.
The following are examples of the spbackup command. The first example backs up the SPFILE in the data disk group. The second example backs up the SPFILE from the data disk group to the fra disk group.
Using the ASMCMD spbackup command
ASMCMD> spbackup +DATA/asm/asmparameterfile/registry.253.721810181
+DATA/spfileBackASM.bak
ASMCMD> spbackup +DATA/asm/asmparameterfile/registry.253.721810181
+FRA/spfileBackASM.bakspcopy
Copies an Oracle ASM SPFILE from the source location to an SPFILE in the destination location.
The following are examples of the spcopy command. The first example copies the Oracle ASM SPFILE from the data disk group to the fra disk group. The second example copies the Oracle ASM SPFILE from the data disk group to an operating system location. The third example copies an Oracle ASM SPFILE from an operating system location to the data disk group and updates the GPnP profile with the -u option.
Using the ASMCMD spcopy command
ASMCMD> spcopy +DATA/asm/asmparameterfile/registry.253.721810181
+FRA/spfileCopyASM.ora
ASMCMD> spcopy +DATA/asm/asmparameterfile/registry.253.721810181
$ORACLE_HOME/dbs/spfileCopyASM.ora
ASMCMD> spcopy -u /oracle/product/11.2.0/grid/dbs/spfileTestASM.ora
+DATA/ASM/spfileCopyASM.oraspget
Retrieves the location of the Oracle ASM SPFILE from the Grid Plug and Play (GPnP) profile.
The following is an example of the spget command that retrieves and displays the location of the SPFILE from the GPnP profile.
Using the ASMCMD spget command
ASMCMD [+] > spget +DATA/ASM/ASMPARAMETERFILE/registry.253.813507611
spmove
Moves an Oracle ASM SPFILE from source to destination and automatically updates the GPnP profile.
The following are examples of the spmove command. The first example moves an Oracle ASM SPFILE from the data disk group to an operating system location. The second example moves an SPFILE from an operating system location to the data disk group.
Using the ASMCMD spmove command
ASMCMD> spmove +DATA/spfileASM.ora
/oracle/product/11.2.0/grid/dbs/spfileMoveASM.ora
ASMCMD> spmove /oracle/product/11.2.0/grid/dbs/spfile+ASM.ora
+DATA/ASM/spfileMoveASM.oraspset
Sets the location of the Oracle ASM SPFILE in the Grid Plug and Play (GPnP) profile.
The following is an example of the spset command that sets the location of the Oracle ASM SPFILE command in the data disk group.
Using the ASMCMD spset command
ASMCMD> spset +DATA/asm/asmparameterfile/asmspfile.ora
startup
Starts up the default instance.
The following is an example of the startup command that starts the Oracle ASM instance (ORACLE_SID=+ASM) without mounting disk groups and uses the asm_init.ora initialization parameter file.
Using the ASMCMD startup command
ASMCMD> startup --nomount --pfile asm_init.ora
chdg
Changes a disk group (adds disks, drops disks, resizes disks, or rebalances a disk group) based on an XML configuration file.
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 or replace
<add> items to add are placed here
</add>
<replace> items to replace are placed here
</replace>
<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>
Example
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.
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.
Using the ASMCMD chdg command
ASMCMD [+] > chdg data_config.xml
ASMCMD [+] > chdg '<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>'chkdg
Checks or repairs the metadata of a disk group.
The following is an example of the chkdg command used to check and repair the data disk group.
Using the ASMCMD chkdg command
ASMCMD [+] > chkdg --repair data
dropdg
Drops a disk group.
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.
Using the ASMCMD dropdg command
ASMCMD [+] > dropdg -r -f data ASMCMD [+] > dropdg -r fra
iostat
Displays I/O statistics for Oracle ASM disks in mounted disk groups.
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.
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
lsattr
Lists the attributes of a disk group.
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.
Using the ASMCMD lsattr command
ASMCMD [+] > lsattr -lm -G data Group_Name Name Value RO Sys DATA access_control.enabled FALSE N Y DATA access_control.umask 066 N Y DATA appliance._partnering_type GENERIC Y Y DATA ate_conversion_done true Y Y DATA au_size 1048576 Y Y DATA cell.smart_scan_capable FALSE N N DATA cell.sparse_dg allnonsparse N N DATA compatible.advm 19.0.0.0.0 N Y DATA compatible.asm 19.0.0.0.0 N Y DATA compatible.rdbms 19.0.0.0.0 N Y DATA content.check FALSE N Y DATA content.type data N Y DATA content_hardcheck.enabled FALSE N Y DATA disk_repair_time 12.0h N Y DATA failgroup_repair_time 24.0h N Y DATA idp.boundary auto N Y DATA idp.type dynamic N Y DATA logical_sector_size 512 N Y DATA phys_meta_replicated true Y Y DATA preferred_read.enabled FALSE N Y DATA scrub_async_limit 1 N Y DATA scrub_metadata.enabled TRUE N Y DATA sector_size 512 N Y DATA thin_provisioned FALSE N Y DATA vam_migration_done false Y Y ASMCMD [+] > lsattr -G fra -l %compat* Name Value compatible.advm 19.0.0.0.0 compatible.asm 19.0.0.0.0 compatible.rdbms 19.0.0.0.0
lsdg
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.
The following example lists the attributes of the data disk group.
Using the ASMCMD lsdg command
ASMCMD [+] > lsdg data
State Type Rebal Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB
MOUNTED NORMAL N 512 4096 4194304 12288 8835 1117 3859
(continued)
Offline_disks Voting_files Name
0 N DATAlsdsk
Lists Oracle ASM disks.
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.
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
...lsod
Lists the open Oracle ASM disks.
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.
Using the ASMCMD lsod command
ASMCMD [+] > lsod -G data --process *LGWR* Instance Process OSPID Path 1 oracle@myserver02 (LGWR) 26593 /devices/diska1 1 oracle@myserver02 (LGWR) 26593 /devices/diska2 1 oracle@myserver02 (LGWR) 26593 /devices/diska3 1 oracle@myserver02 (LGWR) 26593 /devices/diskb1 1 oracle@myserver02 (LGWR) 26593 /devices/diskb2 1 oracle@myserver02 (LGWR) 26593 /devices/diskb3 1 oracle@myserver02 (LGWR) 26593 /devices/diskd1 ASMCMD [+] > lsod --process *LGWR* *diska* Instance Process OSPID Path 1 oracle@myserver02 (LGWR) 26593 /devices/diska1 1 oracle@myserver02 (LGWR) 26593 /devices/diska2 1 oracle@myserver02 (LGWR) 26593 /devices/diska3
md_backup
The md_backup command creates a backup file containing metadata for one or more disk groups.
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.
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
md_restore
The md_restore command restores disk groups from a metadata backup file.
Note the following when restoring Oracle ACFS information:
- When restoring the metadata of a file system, the user id is set to the user id that owned the file system when the metadata backup was created. This user id should exist on the restore cluster.
md_restorerestores Oracle ACFS metadata information. To run the metadata restore for Oracle ACFS file systems, a script is created. This script must be run asrootto format file systems. Metadata for the contained Oracle ADVM volumes, such as stripe size and redundancy, is restored. Oracle ACFS file system configuration metadata, such as compression and resize attributes, block size, and created snapshots, is also restored. Oracle ACFS file System data and ACFS CRS Resource information is not restored.- If using the
--silentoption while specifying a single disk group, and there is a dependency due to Oracle ADVM metadata or Oracle ACFS accelerators on another disk group, that dependency is dropped, and you must manually recreate that dependency later. - When restoring Oracle ACFS encryption or security, file system extended attributes (xattrs) must be restored with the user data. It is very important to document that xattrs need to be stored and restored with the file system application data. Without the xattrs, there is no security or encryption. xattrs describe which security realms the file is a part of. With no xattr, the file ends up in no realm. The converse is that a file with xattrs, but no security initialized, ends up in no realm.
- During metadata restore, a file with a list of previously configured snapshots is created. Snapshot data is not restored, as the point in time sparse snapshot views cannot be recreated.
- If Oracle ACFS security is in use, and the metadata security information for the file system has not been backed up, this information may be copied by the security administrator to the metadata backup file location, and then restored with the rest of the disk group information.
- If Oracle ACFS security and encryption is being restored, the user and password may be pre-initialized. If it is not, the username provided is used to initialize Oracle ACFS security and encryption, with a default password which is displayed.
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.
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
mkdg
Creates a disk group based on an XML configuration file.
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>
Example
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 19.0.
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="19.0"/>
<a name="compatible.rdbms" value="19.0"/>
<a name="compatible.advm" value="19.0"/>
</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.
Using the ASMCMD mkdg command
ASMCMD [+] > mkdg data_config.xml ASMCMD [+] > mkdg '<dg name="data"><dsk string="/dev/disk*"/></dg>'
mount
Mounts a disk group.
The following are examples of the mount command showing the use of the force, restrict, and all options.
Using the ASMCMD mount command
ASMCMD [+] > mount -f data ASMCMD [+] > mount --restrict data ASMCMD [+] > mount -a
offline
Offline disks or failure groups that belong to a disk group.
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.
Using the ASMCMD offline command
ASMCMD [+] > offline -G data -F failgroup1 ASMCMD [+] > offline -G data -D data_0001 -t 1.5h
online
Online all disks, a single disk, or a failure group that belongs to a disk group.
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.
Using the ASMCMD online command
ASMCMD [+] > online -G data -F failgroup1 -w ASMCMD [+] > online -G data -D data_0001
rebal
Rebalances a disk group.
In the following example, the first rebal command rebalances the FRA disk group with a power level set to 4, performing only the balance and compact phases. The second rebal command rebalances the DATA disk group with the rebalance power set to 1, but does not restart the rebalance operation.
Using the ASMCMD rebal command
ASMCMD [+] > rebal --with balance,compact --power 4 FRA
ASMCMD [+] > lsop
Group_Name Operation State Power
FRA REBAL RUN 4
ASMCMD [+] > rebal --modify 1 DATA
remap
Marks a range of blocks as unusable on the disk and relocates any data allocated in that range.
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
Using the ASMCMD remap command
ASMCMD [+] > remap DATA DATA_0001 5000-5999 ASMCMD [+] > remap FRA FRA_0002 6230-6339
setsparseparent
Sets the parent for a sparse child file.
The following are the examples of setsparseparent command. The first example sets a parent file in the data disk group to a sparse file in the sparse disk group. The second example sets a parent file in the data disk group to multiple sparse files in the sparse disk group.
Using the ASMCMD setsparseparent command
ASMCMD [+] > setsparseparent +SPARSEDG/child.1.10 +DATA/parent.1.f setting parent of +SPARSEDG/child.1.10 to +DATA/parent.1.f ASMCMD [+] > setsparseparent +SPARSEDG/child.1a.10 +SPARSEDG/child.1b.11 +SPARSEDG/child.1c.12 +DATA/parent.1.f setting parent of +SPARSEDG/child.1a.10 to +DATA/parent.1.f setting parent of +SPARSEDG/child.1b.11 to +DATA/parent.1.f setting parent of +SPARSEDG/child.1c.12 to +DATA/parent.1.f
setattr
Sets the attributes for an Oracle ASM disk group.
The following are examples of the setattr command. The first example sets the disk group attribute COMPATIBLE.ASM for the data disk group. The second example sets the disk group attribute COMPATIBLE.RDBMS for the data disk group.
Using the ASMCMD setattr command
ASMCMD [+] > setattr -G data compatible.asm 19.0 ASMCMD [+] > setattr -G data compatible.rdbms 19.0
stamp
Stamps the disk, site, and failure group labels in disk headers.
The following example shows the use of the ASMCMD stamp command on the disks identified by the /dev/sd* disk discovery string.
Using ASMCMD stamp
ASMCMD [+] > stamp --dscstr "/dev/sd*" --site "SALTLAKE-CENTER" --failgroup "fg1" --disk "DISK1"
stamplist
Displays the disk, site and failure group labels in disk headers.
The following example shows the use of the ASMCMD stamplist command to display site, failure group, and disk labels of the disks identified by the /dev/sd* disk discovery string.
Using ASMCMD stamplist
ASMCMD [+] > stamplist --dscstr "/dev/sd*" --site --failgroup --disk
umount
Dismounts a disk group.
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.
Using the ASMCMD umount command
ASMCMD [+] > umount -a ASMCMD [+] > umount -f data
No comments:
Post a Comment