dsget [[--normal] [--profile [-f]] [--parameter]] Retrieves the discovery diskstring value that is used by the Oracle ASM Instance and its clients dsset The following example uses dsget to retrieve the current discovery diskstring value from the GPnP profile and the ASM_DISKSTRING parameter. ASMCMD [+] > dsget profile: /devices/disk* parameter: /devices/disk* normal profile force parameter The options for the dsget command are described below. --normal - Retrieves the discovery string from the Grid Plug and Play (GPnP) profile and the one that is set in the Oracle ASM instance. It returns one row each for the profile and parameter setting. This is the default setting. --profile [-f] - Retrieves the discovery string from the GPnP profile. If -f is specified, retrieves the discovery string from the local GPnP profile. --parameter - Retrieves the ASM_DISKSTRING parameter setting of the Oracle ASM instance. dsset [--normal] [--parameter] [--profile [-f]] diskstring Sets the discovery diskstring value that is used by the Oracle ASM instance and its clients. The specified diskstring must be valid for existing mounted disk groups. The updated value takes effect immediately. dsget The following example uses dsset to set the current value of the discovery diskstring in the GPnP profile. ASMCMD [+] > dsset /devices/disk* normal parameter profile force The options for the dsget command are described below. --normal - Sets the discovery string in the Grid Plug and Play (GPnP) profile and in the Oracle ASM instance. The update occurs after the Oracle ASM instance has successfully validated that the specified discovery string has discovered all the necessary disk groups and voting files. Note that this command fails if the instance is not using a server parameter file (SPFILE). This is the default setting. --profile [-f] - Specifies the discovery diskstring that is pushed to the GPnP profile without any validation by the Oracle ASM instance, ensuring that the instance can discover all the required disk groups. The update is guaranteed to be propagated to all the nodes that are part of the cluster If -f is specified, the specified diskstring is pushed to the local GPnP profile without any synchronization with other nodes in the cluster. Note that this command option updates only the local profile file. This option should only be used in the case of recovery. The command fails if the Oracle Clusterware stack is running. --parameter - Specifies that the diskstring is updated in memory after validating that the discovery diskstring discovers all the current mounted disk groups and voting files. The diskstring is not persistently recorded in either the SPFILE or the GPnP profile. diskstring - Specifies the value for the discovery diskstring lsct [-g] [--suppressheader] [diskgroup] Lists information about current Oracle ASM clients from the V$ASM_CLIENT view. A client, such as Oracle Database or Oracle ASM Dynamic Volume Manager (Oracle ADVM), uses disk groups that are manage by the Oracle ASM instance to which ASMCMD is currently connected. The following example displays information about the clients that are accessing the data disk group. ASMCMD [+] > lsct data DB_Name Status Software_Version Compatible_version Instance_Name Disk_Group +ASM CONNECTED 11.2.0.1.0 11.2.0.0.0 +ASM DATA asmvol CONNECTED 11.2.0.1.0 11.2.0.0.0 +ASM DATA orcl CONNECTED 11.2.0.1.0 11.2.0.0.0 orcl DATA g suppressheader The options for the lsct command are described below. (none) - Displays information about current clients from the V$ASM_CLIENT view. -g - Selects from the GV$ASM_CLIENT view. GV$ASM_CLIENT.INST_ID is included in the output. --suppressheader - Suppresses column headings. diskgroup - Specifies the disk group. If diskgroup is specified, then only information about that disk group is listed. lsop Lists the current operations on a disk group or Oracle ASM instance. The following are examples of the lsop command. The examples list operations on the disk groups of the current Oracle ASM instance. ASMCMD [+] > lsop Group_Name Dsk_Num State Power DATA REBAL WAIT 2 ASMCMD [+] > lsop Group_Name Dsk_Num State Power FRA REBAL REAP 3 lsop displays information from the V$ASM_OPERATION view lspwusr [--suppressheader] List the users from the local Oracle ASM password file The following is an example of the lspwusr example. The example lists the current current users in the local Oracle ASM password file. ASMCMD [+] > lspwusr Username sysdba sysoper sysasm SYS TRUE TRUE TRUE ASMSNMP TRUE FALSE FALSE suppressheader The options for the lspwusr command are described below. --suppressheader - Suppresses column headers from the output. orapwusr { { { --add | --modify [--password] }[--privilege {sysasm|sysdba|sysoper} ] } | --delete } user Add, drop, or modify an Oracle ASM password file user. The following is an example of the orapwusr command. This example adds the hruser to the Oracle ASM password file with the role of the user set to SYSDBA. ASMCMD [+] > orapwusr --add --privilege sysdba hruser add modify password privilege delete The options for the orapwusr command are described below. --add - Adds a user to the password file. Also prompts for a password. --delete - Drops a user from the password file. --modify - Changes a user in the password file. --privilege role - Sets the role for the user. The options are sysasm, sysdba, and sysoper. --password - Prompts for and then changes the password of a user. user - the user to add, drop, or modify. orapwusr attempts to update passwords on all nodes in a cluster. The command requires the SYSASM privilege to run. A user logged in as SYSDBA cannot change its password using this command. shutdown [ --normal |--abort|--immediate ] Shuts down an Oracle ASM 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. ASMCMD [+] > shutdown ASMCMD [+] > shutdown --normal ASMCMD [+] > shutdown --immediate ASMCMD [+] > shutdown --abort normal abort immediate The options for the shutdown command are described below. --normal - optional, if no option is specified, --normal is assumed. option specified --abort - Shut down aborting all existing operations. --immediate - Shut down immediately. The default action is a normal shutdown. Oracle strongly recommends that you shut down all database instances that use the Oracle ASM instance and dismount all file systems mounted on Oracle ASM Dynamic Volume Manager (Oracle ADVM) volumes before attempting to shut down the Oracle ASM instance with the abort (--abort) option. spbackup source destination Backs up an Oracle ASM SPFILE. The following are examples of the spbackup command. The first example backs up the Oracle ASM SPFILE from one operating system location to another. The second example backs up the SPFILE from an operating system location to the DATA disk group. ASMCMD>spbackup /u01/oracle/dbs/spfile+ASM.ora /u01/oracle/dbs/bakspfileASM.ora ASMCMD>spbackup /u01/oracle/dbs/spfile+ASM.ora +DATA/bakspfileASM.ora The options for the spbackup command are described below: source - specifies the source name destination - specifies the destination name spbackup does not affect the GPnP profile. The backup file that is created is not a special file type and is not identified as a SPFILE. The file cannot be copied with spcopy. To copy this backup file, use the ASMCMD cp command spget 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. ASMCMD [+] > spget +DATA/asm/asmparameterfile/registry.253.691575633 Note that the location retrieved by spget is the location in the GPnP profile, but not always the location of the SPFILE currently used. For example, the location could have been recently updated by spset or spcopy with the -u opiton on an Oracle ASM instance that has been restarted. After the next restart of the Oracle ASM, this location will point to the ASM SPFILE currently being used spcopy [-u] source destination Copies an Oracle ASM SPFILE from source to destination. The following are examples of the spcopy command. The first example copies the Oracle ASM SPFILE from one operating system location to another. The second example copies the SPFILE from an operating system location to the DATA disk group and updates the GPnP profile. ASMCMD> spcopy /u01/oracle/dbs/spfile+ASM.ora /u01/oracle/dbs/testspfileASM.ora ASMCMD> spcopy /u01/oracle/dbs/spfile+ASM.ora +DATA/testspfileASM.ora u The options for the spcopy command are described below. -u - Updates the Grid Plug and Play (GPnP) profile. source - Specifies the source file name. destination - Specifies the destination. Note the following about the use of spcopy spcopy can copy an Oracle ASM SPFILE from a disk group to a different disk group or to an operating system file. spcopy can copy an Oracle ASM SPFILE from an operating system file to a disk group or to an operating system file. spcopy can copy an Oracle ASM SPFILE when the SPFILE is being used by an open Oracle ASM instance. Include the -u option to update the GPnP profile. You can also use spset to update the GPnP profile. See "spset". For information about copying and moving an Oracle ASM instance initialization parameter file after upgrading, see "Backing Up, Copying, and Moving an Oracle ASM Initialization Parameter File". After copying the SPFILE, you must restart the instance with the SPFILE in the new location if you want to use that SPFILE. When the Oracle ASM instance is running with the SPFILE in the new location, you can remove the source SPFILE. To use spcopy to copy an Oracle ASM SPFILE into a disk group, the Note that the location retrieved by spget is the location in the GPnP profile, but not always the location of the SPFILE currently used. For example, the location could have been recently updated by spset or spcopy with the -u opiton on an Oracle ASM instance that has been restarted. After the next restart of the Oracle ASM, this location will point to the ASM SPFILE currently being used spmove source destination 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 the Oracle ASM SPFILE from one operating system location to another. The second example moves the SPFILE from an operating system location to the DATA disk group. ASMCMD> spmove /u01/oracle/dbs/spfile+ASM.ora /u01/oracle/dbs/testspfileASM.ora ASMCMD> spmove /u01/oracle/dbs/spfile+ASM.ora +DATA/testspfileASM.ora The options for the spmove command are described below. source Specifies the source file name. destination Specifies the destination file. Note the following about the use of spmove: spmove can move an Oracle ASM SPFILE when the open instance is using a PFILE or a different SPFILE. After moving the SPFILE, you must restart the instance with the SPFILE in the new location if you want the instance to use that SPFILE. spmove cannot move an Oracle ASM SPFILE when the SPFILE is being used by an open Oracle ASM instance. To use spmove to move an Oracle ASM SPFILE into a disk group, the disk group attribute COMPATIBLE.ASM must be set to 11.2 or greater. spset location Set the location of the ORACLE ASM SPFILE in Grid Plug and Play (GPnP) profile spset/spget should have --normal --profile and -f option as in dsset/dsget. The following is an example of spset command that sets the location of the Oracle ASM SPFILE command in the data disk group. ASMCMD> spset +DATA/asm/asmparameterfile/asmspfile.ora The options for the spset command are described below location - specifies the location of the Oracle ASM SPFILE. The location is the path to an Oracle ASM SPFILE startup [--nomount] [--restrict] [ --pfile pfile ] Starts up an Oracle ASM instance. The following is an example of the startup command that starts the Oracle ASM instance without mounting disk groups and uses the asm_init. ora initialization parameter file. ASMCMD> startup --nomount --pfile asm_init.ora nomount restrict pfile The options for the startup command are described below. --nomount - Specifies no mount operation. --restrict - Specifies restricted mode. --pfile pfile - Oracle ASM initialization parameter file. The default action is a start up that mounts disk groups and enables Oracle ADVM volumes. cd [dir] Changes the current directory to the specified directory. The following are examples of the cd command changing into various directories. ASMCMD [+data/hr] > cd +data/orcl ASMCMD [+data/orcl] > cd DATAFILE ASMCMD [+data/orcl/DATAFILE] >cd .. The options for the cd command are described below. dir - Name of the directory. dir can be specified as either an absolute path or a relative path, including the . and .. pseudo-directories. dir can contain wildcard characters. This setting affects all subsequent operations on filespecs that do not contain an absolute path cp [--service <name>] [--port <port>] [connect_str:]src_file [connect_str:]tgt_file Enables you to copy files between Oracle ASM disk groups on local instances to and from remote instances. The following are examples of the cp command. The first example shows a copy of a file in the data disk group to a file on the operating system. The second example shows a copy of a file on the operating system to the DATA disk group. The third and fourth example shows how to copy files from ASM to remote server (OS file). The fifth example shows how to copy a remote OS File to DATA diskgroup. The sixth example shows how to copy a remote OS File to DATA diskgroup when listener port is not default. sys is the user name on the remote server server is the remote server name asminstance ASM Instance name /scratch/file OS file. If password is not provided in the command line, it will be asked. ASMCMD [+] > cp +data/orcl/datafile/EXAMPLE.265.691577295 /mybackups/example.bak copying +data/orcl/datafile/EXAMPLE.265.691577295 -> /mybackups/example.bak ASMCMD [+] > cp /mybackups/examples.bak +data/orcl/datafile/myexamples.bak copying /mybackups/examples.bak -> +data/orcl/datafile/myexamples.bak ASMCMD [+] > cp +data/orcl/datafile/EXAMPLE.265.691577295 sys@server.asminstance:/scratch/file ASMCMD [+] > cp +data/orcl/datafile/EXAMPLE.265.691577295 sys/passwd@server.asminstance:/scratch/file ASMCMD [+] > cp sys@server.asminstance:/scratch/file +data/orcl/datafile/file ASMCMD [+] > cp --port 2500 sys@server.SID:/scratch/file +data/orcl/datafile/file copying /scratch/file -> +data/orcl/datafile/file The options for the cp command are described below. --service - name of the ASM instance name if not default +ASM. --port - Listener port number, default is 1521. connect_str - The connection string for use with a remote instance copy. src_file - Name of the source file to copy. tgt_file - A user alias for the created target file name or alias directory name. cp cannot copy files between two remote instances. The local Oracle ASM instance must be either the source or the target of the operation. You can use the cp command to: Copy files from a disk group to the operating system Copy files from a disk group to a disk group Copy files from the an OS File system to a disk group Some file types cannot be the source or destination of the cp command. These file types include OCR, OCR backup and SPFILE file types. To back up, copy, or move an ASM SPFILE, use the spbackup, spcopy, or spmove commands. connect_str is not required for a local instance copy, which is the default case. In the case of a remote instance copy, you must specify the connect string and Oracle ASM prompts for a password in a non-echoing prompt. The connect_str is in the form of: user@host.SID user, host, and SID are required in the connect_str parameter. The default port number is 1521. src_file must be either the fully qualified file name, the system-generated name, or the Oracle ASM alias. The cp command performs a binary copy without any data transformation. du [--suppressheader] [dir] Displays the total space used for files in the specified directory and in the entire directory tree under the directory. The following is an example of the du command. The example shows disk space used in the orcl directory in data, including all of the directories under the orcl directory. ASMCMD [+] > du DATA/orcl Used_MB Mirror_used_MB 1756 3519 suppressheader The options for the du command are described below. dir - Name of the directory. --suppressheader - Suppresses column headings from the output. If you do not specify dir, then information about the current directory is displayed. dir can contain wildcard characters. See "Wildcard Characters". The following two values are displayed, both in units of megabytes. Used_MB - This value does not include mirroring. Mirror_used_MB - This value includes mirroring. For example, if a normal redundancy disk group contains 100 MB of data, then assuming that each file in the disk group is 2-way mirrored, Used_MB is 100 MB and Mirror_used_MB is roughly 200 MB. Note that this command displays the information about the space usage of files inside the diskgroup not the size of the diskgroup. find [--type type] dir pattern Displays the absolute paths of all occurrences of the specified name pattern (with wildcards) in a specified directory and its subdirectories. The following are examples of the find command. The first example searches the data disk group for files that begin with UNDO. The second example returns the absolute path of all the control files (--type CONTROLFILE) in the +data/orcl directory. ASMCMD [+] > find +data undo* +data/ORCL/DATAFILE/UNDOTBS1.258.691577151 ASMCMD [+] > find --type CONTROLFILE +data/orcl * +data/orcl/CONTROLFILE/Current.260.691577263 type The options for the find command are described below. --type type - Type of target that you want to find. dir - Directory name where you want to start searching. pattern - Name of a target or a wildcard pattern. This command searches the specified directory and all subdirectories under it in the directory tree for the supplied pattern. The value that you use for pattern can be a directory name or a filename, and can include wildcard characters. See "Wildcard Characters". The ASMCMD find command is case insensitive. In the output of the command, directory names are suffixed with the slash character (/) to distinguish them from filenames. You use the --type flag to find all the files of a particular type (specified as type). For example, you can search for control files by specifying type as CONTROLFILE. The type values are listed in the type column of the V$ASM_FILE view. ls [-lsdtLg] [--absolutepath][--suppressheader] [--reverse][--permission][pattern] Lists the contents of an Oracle ASM directory, the attributes of the specified file, or the names and attributes of all disk groups from the V$ASM_DISKGROUP_STAT or V$ASM_DISKGROUP view. The default view is V$ASM_DISKGROUP_STAT. The following are examples of the ls command that display various information about directories and the contents of the directories. ASMCMD [+] > ls +data/orcl/datafile EXAMPLE.265.691577295 SYSAUX.257.691577149 SYSTEM.256.691577149 UNDOTBS1.258.691577151 USERS.259.691577151 ASMCMD [+] > ls -lt +data/orcl/datafile Type Redund Striped Time Sys Name DATAFILE MIRROR COARSE JUL 13 08:00:00 Y EXAMPLE.265.691577295 DATAFILE MIRROR COARSE JUL 13 05:00:00 Y SYSAUX.257.691577149 DATAFILE MIRROR COARSE JUL 13 02:00:00 Y USERS.259.691577151 DATAFILE MIRROR COARSE JUL 13 02:00:00 Y UNDOTBS1.258.691577151 DATAFILE MIRROR COARSE JUL 13 02:00:00 Y SYSTEM.256.691577149 ASMCMD [+] > ls -l +data/orcl/datafile/sy* Type Redund Striped Time Sys Name DATAFILE MIRROR COARSE JUL 13 05:00:00 Y SYSAUX.257.691577149 DATAFILE MIRROR COARSE JUL 13 02:00:00 Y SYSTEM.256.691577149 ASMCMD [+] > ls -s +data/orcl/datafile Block_Size Blocks Bytes Space Name 8192 12801 104865792 214958080 EXAMPLE.265.691577295 8192 88321 723525632 1452277760 SYSAUX.257.691577149 8192 88321 723525632 1452277760 SYSTEM.256.691577149 8192 7681 62922752 131072000 UNDOTBS1.258.691577151 8192 641 5251072 12582912 USERS.259.691577151 ASMCMD [+] > ls --permission +data/orcl/datafile User Group Permission Name rw-rw-rw- EXAMPLE.265.691577295 rw-rw-rw- SYSAUX.257.691577149 rw-rw-rw- SYSTEM.256.691577149 rw-rw-rw- UNDOTBS1.258.691577151 rw-rw-rw- USERS.259.691577151 l s d t L g absolutepath suppressheader reverse permission The options for the ls command are described below. (none) - Displays only filenames and directory names. -l - Displays extended file information, including striping and redundancy information and whether the file was system-generated (indicated by Y under the SYS column) or user-created (as in the case of an alias, indicated by N under the SYS column). When used in the "ls -l +" command, displays directory information. Note that not all possible file attributes or disk group attributes are included. To view the complete set of column values for a file or a disk group, query the V$ASM_FILE and V$ASM_DISKGROUP views. -s - Displays file space information. -d - If the value for the name argument is a directory, then ls displays information about that directory, rather than the directory contents. Typically used with another flag, such as the -l flag. --reverse - Reverses the sort order of the listing. -t - Sorts the listing by timestamp (latest first) instead of by name. -L - If the value for the name argument is an alias, then ASMCMD displays information about the file that it references. Typically used with another flag, such as the -l flag. --absolutepath - For each listed file, displays the absolute path of the alias that references it, if any. -g - Selects from GV$ASM_DISKGROUP_STAT, or from GV$ASM_DISKGROUP if the -c flag is also specified. GV$ASM_DISKGOUP.INST_ID is included in the output. --suppressheader - Suppresses column headings. --permission - Shows the permissions of a file (V$ASM_FILE.permission, V$ASM_FILE.owner, V$ASM_FILE.usergroup, V$ASM_ALIAS.name). pattern - Name of a file, directory, or pattern. Command options enable you to modify and customize the output of the command. Table 12-20 lists the options and their descriptions. For disk group information, this command queries the V$ASM_DISKGROUP_STAT view by default, which can be modified by using the -g option. If you specify all of the options, then the command shows a union of their attributes, with duplicates removed. If you enter ls +, then the command returns information about all disk groups, including information about whether the disk groups are mounted. name - can be a filename or directory name, including wildcard characters. If name is a directory name, then ls lists the contents of the directory and depending on flag settings, ls also lists information about each directory member. Directories are listed with a trailing slash (/) to distinguish them from files. If the value that you enter for name is a filename, then ls lists the file and depending on the flag settings, ls also lists information about the file. The file must be located in the current directory if the filename is specified with a relative path. lsof [--suppressheader] {-G diskgroup|--dbname db| -C instance} Lists the open files of the local clients. The following are examples of the lsof command. The first example lists the open files for the data disk group. The second example lists the open files for the Oracle ASM instance. ASMCMD [+] > lsof -G data DB_Name Instance_Name Path orcl orcl +data/orcl/controlfile/current.260.691577263 orcl orcl +data/orcl/datafile/example.265.691577295 orcl orcl +data/orcl/datafile/sysaux.257.691577149 orcl orcl +data/orcl/datafile/system.256.691577149 orcl orcl +data/orcl/datafile/undotbs1.258.691577151 orcl orcl +data/orcl/datafile/users.259.691577151 orcl orcl +data/orcl/onlinelog/group_1.261.691577267 orcl orcl +data/orcl/onlinelog/group_2.262.691577271 orcl orcl +data/orcl/onlinelog/group_3.263.691577275 orcl orcl +data/orcl/tempfile/temp.264.691577287 ASMCMD [+] > lsof -C +ASM DB_Name Instance_Name Path asmvol +ASM +data/VOLUME1.271.679226013 asmvol +ASM +data/VOLUME2.272.679227351 suppressheader G dbname C The options for the lsof command are described below. --suppressheader - Suppresses column headings. -G diskgroup - List files only from this specified disk group. --dbname db - List files only from this specified database. -C instance - List files only from this specified instance. mkalias file alias Creates an alias for the specified system-generated filename. The following example creates the sysaux.f alias for the fully qualified filename +data/orcl/DATAFILE/SYSAUX.257.691577149. Following the mkalias command, ls --absolutepath is run to check the results. ASMCMD [+data/orcl/datafile] > mkalias SYSAUX.257.691577149 sysaux.f ASMCMD [+data/orcl/datafile] > ls --absolutepath none => EXAMPLE.265.691577295 none => SYSTEM.256.691577149 none => UNDOTBS1.258.691577151 none => USERS.259.691577151 +DATA/ORCL/DATAFILE/sysaux.f => SYSAUX.257.691577149 sysaux.f The options for the mkalias command are described below. file - System-generated file name. alias - Alias for the file name. alias must be in the same disk group as the system-generated file. Only one alias is permitted for each Oracle ASM file. mkdir dir [dir . . .] Creates Oracle ASM directories under the current directory. The following is an example of the mkdir command. The example creates the directories subdir1 and subdir2 at the disk group level in the disk group data. ASMCMD [+data] > mkdir subdir1 subdir2 ASMCMD [+data] > ls ASM/ ORCL/ subdir1/ subdir2/ The options for the mkdir command are described below. dir - Directory name that you want to create. The current directory can be created by the system or by the user. You cannot create a directory at the root (+) level. pwd Displays the absolute path of the current directory. The following is an example of the pwd command. The example displays the current directory. ASMCMD [+data/orcl/datafile] > pwd +data/orcl/datafile rm [-f|-r] name [name...] Deletes the specified Oracle ASM files and directories. The following are examples of the rm command. The first example deletes the myexamples.bak file. The second example removes the subdir2 directory and its contents. ASMCMD [+data/orcl/datafile] > rm myexamples.bak ASMCMD [+data] > rm -r subdir2 You may delete multiple files and/or directories. Are you sure? (y/n) y f r The options for the rm command are described below. -r - Recursively deletes files and subdirectories. -f - Forces the deletion of files and subdirectories. name - Name of the file, pattern, or directory you want to remove. If name is a file or alias, then the rm command can delete the file or alias only if it is not currently in use. If name is a directory, then the rm command can delete it only if it is empty (unless the -r flag is used) and it is not a system-generated directory. If name is an alias, then the rm command deletes both the alias and the file to which the alias refers. To delete only an alias and retain the file that the alias references, use the rmalias command. Note: When you delete all of the files in a system-created directory, the directory is removed. If the parent directories are empty, all of the parent directories are also removed. name can contain wildcard characters. See "Wildcard Characters". If you use a wildcard, the rm command deletes all of the matches except nonempty directories, unless you use the -r flag. To recursively delete, use the -r flag. With -r option you can delete a nonempty directory, including all files and directories in it and in the entire directory tree underneath it. If you use the -r flag or a wildcard character, then the rm command prompts you to confirm the deletion before proceeding, unless you specify the -f flag. If a wildcard character matches an alias or a system-generated file that has an alias, then both the alias and the system-generated file that it references are deleted. When using the -r flag, either the system-generated file or the alias must be present in the directory in which you run the rm command. For example, if you have a user alias, +data/dir1/file.alias that points to +data/orcl/DATAFILE/System.256.146589651, then running the rm -r +data/dir1 command removes the +data/dir1/file.alias and +data/orcl/DATAFILE/System.256.146589651. rmalias [-r] alias [alias...] Removes the specified aliases, retaining the files that the aliases reference. The following is an example of the rmalias command. The example deletes the alias sysaux.f, retaining the data file that it references. ASMCMD [+data/orcl/datafile] > rmalias sysaux.f r The options for the rmalias command are described below. -r - Recursively removes aliases. alias - Alias for the file name or directory. The -r flag enables you to remove all of the aliases in the current directory and in the entire directory tree beneath the current directory. If any user-created directories become empty as a result of deleting aliases, they are also deleted. Files and directories created by the system are not deleted. chdg { config_file.xml | 'contents_of_xml_file' } Changes a disk group (adds disks, drops disks, or rebalances) based on a XML configuration file. The following example shows the basic structure and valid tags with thier respective attributes for the chdg XML configuration file. <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> name disk name path disk path size size of the disk to add </dsk> </chdg> For information about creating a disk group with ASMCMD mkdg see "mkdg" The following is an example of an XML Configuration filr for chdd. This XML file alters the disk group named data. The failure group fg1 is dropped and the disk data_001 is also dropped. The /dev/disk5 disk is added to failure group fg2. The rebalance power level is set to 3. <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 configuration file or configuration information on the command line. 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>' The options for the chdg command are described below: config_file - Name of the XML file that contains the changes for the disgroup. chdg searches the XML file in the directory where ASMCMD was started unless a path is specified. contents_of_xml_file - 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 diskgroup, and the setting rebalance power level. The power level can set from 0 to the maximum of 11, the same values as the ASM_POWER_LIMIT initialization parameter When adding disks to a disk group, the diskstring must be specified similar to ASM_DISKSTRING initialization parameter. The failure groups are optional parameters. The default causes every disk to belong to its own failure group. Dropping disks from a disk group can be performed through this operation. An individual disk can be referenced by its Oracle ASM disk name. The set of disks that belong to a failure group can be specified by the failure group name. You can resize a disk inside a diskgroup with chdg. The resize operation fails if there is not enough space for storing data after the resize chkdg [--repair] diskgroup 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. ASMCMD [+] > chkdg --repair data repair The options for the chkdg command are described below. --repair - Repairs the disk group. diskgroup - Name of disk group to check or repair. chkdg checks the metadata of a disk group for errors and optionally repairs the errors. dropdg [-r [-f]] diskgroup 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. ASMCMD [+] > dropdg -r -f data ASMCMD [+] > dropdg -r fra r f The options for the dropdg command are described below. -f - Force the operation. Only applicable if the disk group cannot be mounted. -r - Recursive, include contents. diskgroup - Name of disk group to drop. dropdg drops an existing disk group. The disk group cannot be mounted on more than one node. iostat [-et][--io] [--suppressheader] [--region] [-G diskgroup] [interval] 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. 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 e t suppressheader io region G iostat lists disk group statistics using the V$ASM_DISK_IOSTAT view. The options for the iostat command are described below. -e - Displays error statistics (Read_Err, Write_Err). -G diskgroup - Displays statistics for the disk group name. --suppressheader - Suppresses column headings. --io - Displays information in number of I/Os, instead of bytes. -t - Displays time statistics (Read_Time, Write_Time). --region - Displays information for cold and hot disk regions (Cold_Reads, Cold_Writes, Hot_Reads, Hot_Writes). interval - Refreshes the statistics display based on the interval value (seconds). The attribute descriptions for iostat command output are described below. To view the complete set of statistics for a disk group, use the V$ASM_DISK_IOSTAT view. Group_Name Name of the disk group. Dsk_Name Name of the disk. Reads Total number of bytes read from the disk. If the --io option is entered, then the value is displayed as number of I/Os. Writes Total number of bytes written from the disk. If the --io option is entered, then the value is displayed as number of I/Os. Cold_Reads Total number of bytes read from the cold disk region. If the --io option is entered, then the value is displayed as number of I/Os. Cold_Writes Total number of bytes written from the cold disk region. If the --io option is entered, then the value is displayed as number of I/Os. Hot_Reads Total number of bytes read from the hot disk region. If the --io option is entered, then the value is displayed as number of I/Os. Hot_Writes Total number of bytes written from the hot disk region. If the --io option is entered, then the value is displayed as number of I/Os. Read_Err Total number of failed I/O read requests for the disk. Write_Err Total number of failed I/O write requests for the disk. Read_Time Total I/O time (in hundredths of a second) for read requests for the disk if the TIMED_STATISTICS initialization parameter is set to TRUE (0 if set to FALSE). Write_Time Total I/O time (in hundredths of a second) for write requests for the disk if the TIMED_STATISTICS initialization parameter is set to TRUE (0 if set to FALSE). lsattr [-G diskgroup ] [-lm] [--suppressheader] [pattern] 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. ASMCMD [+] > lsattr -l -G DATA Name Value access_control.enabled FALSE access_control.umask 066 au_size 4194304 cell.smart_scan_capable FALSE compatible.advm 11.2.0.0.0 compatible.asm 11.2.0.0.0 compatible.rdbms 10.1.0.0.0 disk_repair_time 3.6h sector_size 512 ASMCMD [+] > lsattr -l -G FRA %compat* Name Value compatible.asm 11.2.0.0.0 compatible.rdbms 10.1.0.0.0 G l m suppressheader The options for the lsattr command are described below. -G diskgroup - Disk group name. -l - Display names with values. -m - Displays additional information, such as the RO and Sys columns. --suppressheader - Suppresses column headings. pattern - Display the attributes that contain pattern expression. Information about disk group attributes is retrieved from the V$ASM_ATTRIBUTE view. 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". lsdg [-g][--suppressheader][--discovery][pattern] Lists 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. ASMCMD [+] > lsdg data State Type Rebal Sector Block AU Total_MB Free_MB Req_mir_free_MB MOUNTED NORMAL N 512 4096 4194304 12288 8835 1117 Usable_file_MB Offline_disks Voting_files Name 3859 0 N DATA g suppressheader discovery The options for the lsdg command are described below. (none) - Displays the disk group attributes --discovery - Selects from V$ASM_DISKGROUP, or from GV$ASM_DISKGROUP if the -g flag is also specified. This option is always enabled if the Oracle ASM instance is version 10.1 or earlier. This flag is disregarded if lsdsk is running in non-connected mode. -g - Selects from GV$ASM_DISKGROUP_STAT, or from GV$ASM_DISKGROUP if the -c flag is also specified. GV$ASM_DISKGOUP.INST_ID is included in the output. The REBALcolumn of the GV$ASM_OPERATION view is also included in the output. --suppressheader - Suppresses column headings. pattern - Returns only information about the specified disk group or disk groups that match the supplied pattern. The attribute descriptions for lsdg command output are described below. To view the complete set of attributes for a disk group, use the V$ASM_DISKGROUP_STAT or V$ASM_DISKGROUP view. The attribute descriptions for lsdg command output are described below. To view the complete set of attributes for a disk group, use the V$ASM_DISKGROUP_STAT or V$ASM_DISKGROUP view. State - State of the disk group. Values include BROKEN, CONNECTED, DISMOUNTED, MOUNTED, QUIESCING, and UNKNOWN. Type - Disk group redundancy (NORMAL, HIGH, EXTERNAL). Rebal - Y if a rebalance operation is in progress. 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 V$ASM_DISKGROUP view. 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 REQUIRED_MIRROR_FREE_MB column from the V$ASM_DISKGROUP view. Usable_file_MB - Amount of free space, adjusted for mirroring, that is available for new files. From the V$ASM_DISKGROUP view. Offline_disks - Number of offline disks in the disk group. Offline disks are eventually dropped. Voting_files - Specifies whether the disk group contains voting disks (Y or N). Name - Disk group name. lsdsk [-kptgMI][-G diskgroup ] [--suppressheader] [ --member|--candidate] [--discovery][--statistics][pattern] List Oracle ASM disks. 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. 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 ... k p t g M I G suppressheader member candidate discovery statistics The options for the lsdsk command are described below. (none) - Displays the PATH column of the V$ASM_DISK view. -k - Displays the TOTAL_MB, FREE_MB, OS_MB,NAME, FAILGROUP, LIBRARY, LABEL, UDID, PRODUCT, REDUNDANCY, and PATH columns of the V$ASM_DISK view. --statistics - Displays the READS, WRITES, READ_ERRS, WRITE_ERRS, READ_TIME, WRITE_TIME, BYTES_READ, BYTES_WRITTEN, and the PATH columns of the V$ASM_DISK view. -p - Displays the GROUP_NUMBER, DISK_NUMBER, INCARNATION, MOUNT_STATUS, HEADER_STATUS, MODE_STATUS, STATE, and the PATH columns of the V$ASM_DISK view. -t - Displays the CREATE_DATE, MOUNT_DATE, REPAIR_TIMER, and the PATH columns of the V$ASM_DISK view. -g - Selects from GV$ASM_DISK_STAT, or from GV$ASM_DISK if the --discovery flag is also specified. GV$ASM_DISK.INST_ID is included in the output. --discovery - Selects from V$ASM_DISK, or from GV$ASM_DISK if the -g flag is also specified. This option is always enabled if the Oracle ASM instance is version 10.1 or earlier. This flag is disregarded if lsdsk is running in non-connected mode. -I - Scans disk headers for information rather than extracting the information from an Oracle ASM instance. This option forces non-connected mode. -G - Restricts results to only those disks that belong to the group specified by diskgroup. -M - Displays the disks that are visible to some but not all active instances. These are disks that, if included in a disk group, will cause the mount of that disk group to fail on the instances where the disks are not visible. --suppressheader - Suppresses column headings. --candidate - Restricts results to only disks having membership status equal to CANDIDATE. --member - Restricts results to only disks having membership status equal to MEMBER. pattern - 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 Microsoft 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. 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. lsod [-G diskgroup] [--suppressheader] [--process process] [pattern] Lists the open 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. 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 G suppressheader The options for the lsod command are described below. -G diskgroup - Specifies the disk group that contains the open disks. --suppressheader - Suppresses column header information from the output. --process - Specifies a pattern to filter the list of processes. pattern - 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. md_backup backup_file [-G diskgroup [,diskgroup,...]] The md_backup command creates a backup file containing metadata for one or more disk groups. Volume and Oracle Automatic Storage Management Cluster File System (Oracle ACFS) file system information is not backed up. The first example shows the use of the backup command when you run it without the disk group option. This example backs up all of the mounted disk groups and creates the backup image in the current working directory. The second example creates a backup of disk group DATA and FRA. The backup that this example creates is saved in the /tmp/dgbackup20090716 file. ASMCMD [+] > md_backup /tmp/dgbackup20090716 ASMCMD [+] > md_backup /tmp/dgbackup20090716 -G DATA,FRA Disk group metadata to be backed up: DATA Disk group metadata to be backed up: FRA Current alias directory path: ASM/ASMPARAMETERFILE Current alias directory path: ORCL/DATAFILE Current alias directory path: ORCL/TEMPFILE Current alias directory path: ORCL/CONTROLFILE Current alias directory path: ORCL/PARAMETERFILE Current alias directory path: ASM Current alias directory path: ORCL/ONLINELOG Current alias directory path: ORCL Current alias directory path: ORCL/CONTROLFILE Current alias directory path: ORCL/ARCHIVELOG/2009_07_13 Current alias directory path: ORCL/BACKUPSET/2009_07_14 Current alias directory path: ORCL/ARCHIVELOG/2009_07_14 Current alias directory path: ORCL Current alias directory path: ORCL/DATAFILE Current alias directory path: ORCL/ARCHIVELOG Current alias directory path: ORCL/BACKUPSET Current alias directory path: ORCL/ONLINELOG G The options for the md_backup command are described below. backup_file - Specifies the backup file in which you want to store the metadata. -G diskgroup - 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. md_restore backup_file [--silent][--full|--nodg|--newdg -o 'old_diskgroup:new_diskgroup [,...]'][-S sql_script_file] [-G 'diskgroup [,diskgroup...]'] This command restores a disk group metadata backup. 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 called DATA2. The fourth example restores from the backup file after applying the overrides defined in the override.sql script file ASMCMD [+] > md_restore --full -G data --silent /tmp/dgbackup20090714 ASMCMD [+] > md_restore --nodg -G data --silent /tmp/dgbackup20090714 ASMCMD [+] > md_restore --newdg -o 'data:data2' --silent /tmp/dgbackup20090714 ASMCMD [+] > md_restore -S override.sql --silent /tmp/dgbackup20090714 silent full nodg newdg o S G The options for the md_restore command are described below. backup_file - Reads the metadata information from backup_file. --silent - Ignore errors. Normally, if md_restore encounters an error, it will stop. Specifying this flag ignores any errors. --full - Specifies to create a disk group and restore metadata. --nodg - Specifies to restore metadata only. --newdg -o old_diskgroup:new_diskgroup - Specifies to create a disk group with a different name when restoring metadata. The -o option is required with --newdg. -S sql_script_file - Write SQL commands to the specified SQL script file instead of executing the commands. -G diskgroup - Select the disk groups to be restored. If no disk groups are defined, then all disk groups will be restored. mkdg <<config_file.xml | 'contents_of_xml_file'>> Creates a disk group based on an XML configuration file. The following example shows the basic structure and the valid tags with their respective attributes for the 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 path disk path size size of the disk to add </dsk> <a>attribute name attribute name value attribute value </a> </dg> The following is an example of an XML configuration file for mkdg. The configuration 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 <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 follwoing are examples of the mkdg command. The first example executes mkdg with a XML Configuration file in the directory where ASMCMD was started. The second example executes mkdg using information on the command line. ASMCMD[+]>mkdg data_config.xml ASMCMD[+]>mkdg '<dg name="data"><dsk path="/dev/disk*"/></dg> The options for the mkdg command are described below. config_file - Name of the XML file that contains the configuration for the new disk group. mkdg searches for the XML file in the directory where ASMCMD was started unless a path is specified. contents_of_xml_file - 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, every disk will be in its own failure group. It is possible to set some of the 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. 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. mount [--restrict] { [-a] | [-f] diskgroup[ diskgroup ...] } Mounts a disk group. The following are examples of the mount command showing the use of the -force, -restrict, and -a options. ASMCMD [+] > mount -f data ASMCMD [+] > mount --restrict data ASMCMD [+] > mount -a restrict a f The options for the mount command are described below. diskgroup - Name of the disk group. -a - Mounts all disk groups. --restrict - Mounts in restricted mode. -f - 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. offline -G diskgroup { -F failgroup |-D disk} [-t {minutes | hours}] 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. ASMCMD [+] > offline -G DATA -F FAILGROUP1 ASMCMD [+] > offline -G DATA -D data_0001 -t 1.5h G F D t The options for the offline command are described below. -G diskgroup - Disk group name. -F failgroup - Failure group name. -D disk - Specifies a single disk name. -t - minutes | hours Specifies the time before the specified disk is dropped as nm or nh, where m specifies minutes and h specifies hours. The default unit is hours. When a failure group is specified, this implies all the disks that belong to it should be offlined. online { [-a] -G diskgroup | -F failgroup |-D disk} [-w] 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. ASMCMD [+] > online -G DATA -F failgroup1 -w ASMCMD [+] > online -G DATA -D data_0001 a G F D w The options for the online command are described below. -a - Online all offline disks in the disk group. -G diskgroup - Disk group name. -F failgroup - Failure group name. When a failure group is specified, this implies all the disks that belong to it should be onlined. -D disk - Disk name. -w - Wait option. Causes ASMCMD to wait for the disk group to be rebalanced before returning control to the user. The default is not waiting. rebal [--power power] [-w] diskgroup Rebalances a disk group. lsop The following is an example of the rebal command that rebalances the FRA disk group with a power level set to 4. ASMCMD [+] > rebal --power 4 FRA ASMCMD [+] > lsop Group_Name Dsk_Num State Power FRA REBAL RUN 4 power w The options for the rebal command are described below. diskgroup - Disk group name. --power power - Power setting (0 to 11). -w - 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 from 0 to 11. 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. You can determine if a rebalance operation is occurring with the ASMCMD lsop command. remap diskgroup disk block_range 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 ASMCMD [+] > remap DATA DATA_0001 5000-5999 ASMCMD [+] > remap FRA FRA_0002 6230-6339 The options for the remap command are described below. diskgroup - Disk group name in which a disk must have data relocated. disk - Name of the disk that must have data relocated. The name must match the NAME column in the V$ASM_DISK view. block_range - Range of physical blocks to relocate in the format start_range_number-end_range_number. 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. setattr -G diskgroup attribute_name attribute_value 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 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. ASMCMD [+] > setattr -G DATA compatible.asm 11.2.0.0.0 ASMCMD [+] > setattr -G DATA compatible.rdbms 11.2.0.0.0 G The options for the lsct command are described below. -G diskgroup - Disk group name. attribute_name - Name of the attribute. attribute_value - Value of the attribute. umount { -a | [-f] diskgroup } 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. ASMCMD [+] > umount -a ASMCMD [+] > umount -f DATA a f The options for the umount command are described below. diskgroup - Name of the disk group. -a - Dismounts all mounted disk groups. These disk groups are listed in the output of the V$ASM_DISKGROUP view. -f - Forces the dismount operation. chtmpl -G diskgroup { [--striping {coarse|fine}] [--redundancy {high|mirror|unprotected} ] [--primary {hot|cold}] [--secondary {hot|cold}]} template Changes the attributes of a template. The following is an example of the chtmpl command that updates the mytemplate template of the DATA disk group. The redundancy attribute is set to high and the striping attribute is set to fine. ASMCMD [+]>chtmpl -G DATA --redundancy high --striping fine mytemplate G striping redundancy primary secondary The options for the chtmpl command are described below. -G diskgroup - Name of the disk group. template - Name of the template to change. --striping {coarse | fine} - Striping specification, either coarse or fine. --redundancy { high | mirror | unprotected} - Redundancy specification, either high, mirror, or unprotected. --primary { hot | cold } - Intelligent Data Placement specification for primary extents, either hot or cold region. --secondary { hot | cold } - Intelligent Data Placement specification for secondary extents, either hot or cold region. At least one of these options is required: --striping, --redundancy, --primary, or --secondary. lstmpl [-l] [--suppressheader] [-G diskgroup] [pattern] Lists all templates or the templates for a specified disk group. The following is an example of the lstmpl command. The example lists all details of the templates in the DATA disk group. ASMCMD [+] > lstmpl -l -G DATA Group_Name Group_Num Name Stripe Sys Redund PriReg MirrReg DATA 1 ARCHIVELOG COARSE Y MIRROR COLD COLD DATA 1 ASMPARAMETERFILE COARSE Y MIRROR COLD COLD DATA 1 AUTOBACKUP COARSE Y MIRROR COLD COLD DATA 1 BACKUPSET COARSE Y MIRROR COLD COLD DATA 1 CHANGETRACKING COARSE Y MIRROR COLD COLD DATA 1 CONTROLFILE FINE Y HIGH COLD COLD DATA 1 DATAFILE COARSE Y MIRROR COLD COLD DATA 1 DATAGUARDCONFIG COARSE Y MIRROR COLD COLD DATA 1 DUMPSET COARSE Y MIRROR COLD COLD DATA 1 FLASHBACK COARSE Y MIRROR COLD COLD DATA 1 MYTEMPLATE FINE N HIGH COLD COLD DATA 1 OCRFILE COARSE Y MIRROR COLD COLD DATA 1 ONLINELOG COARSE Y MIRROR COLD COLD DATA 1 PARAMETERFILE COARSE Y MIRROR COLD COLD DATA 1 TEMPFILE COARSE Y MIRROR COLD COLD DATA 1 XTRANSPORT COARSE Y MIRROR COLD COLD G suppressheader l The options for the lstmpl command are described below. -G diskgroup - Specifies disk group name. --suppressheader - Suppresses column headings. -l - Displays all details. pattern - Displays the templates that match pattern expression. mktmpl -G diskgroup [--striping {coarse|fine}][--redundancy {high|mirror|unprotected} ] [--primary {hot|cold}][--secondary {hot|cold}] template Adds a template to a disk group. The following is an example of the mktmpl command that add the mytemplate template to the DATA disk group. The new template has the redundancy set to mirror and the striping set to coarse. ASMCMD [+]>mktmpl -G DATA --redundancy mirror --striping coarse mytemplate G striping redundancy primary secondary The options for the mktmpl command are described below. -G diskgroup - Name of the disk group. template - Name of the template to create. --striping {coarse | fine} - Striping specification, either coarse or fine. --redundancy { high | mirror | unprotected} - Redundancy specification, either high, mirror, or unprotected. --primary { hot | cold } - Intelligent Data Placement specification for primary extents, either hot or cold region. --secondary { hot | cold } - Intelligent Data Placement specification for secondary extents, either hot or cold region. rmtmpl -G diskgroup template Removes a template from a disk group. The following is an example of the rmtmpl command that removes the mytemplate template from the DATA disk group. ASMCMD [+]>rmtmpl -G DATA mytemplate G The options for the rmtmpl command are described below. -G diskgroup - Name of the disk group. template - Name of the template to delete. chgrp usergroup file [file ...] Changes the user group of a file or list of files. The following are examples of the chgrp command that change the Oracle ASM user group of the specified files. ASMCMD [+] > chgrp asm_data +data/orcl/controlfile/Current.260.684924747 ASMCMD [+fra/orcl/archivelog/flashback] > chgrp asm_fra log_7.264.684968167 log_8.265.684972027 The options for the chgrp command are described below. usergroup - Name of the user group. file - Name of a file. Only the file owner or the Oracle ASM administrator can use this command. If the user is the file owner, then he must also be either the owner or a member of the group for this command to succeed. This command accepts a file name or a multiple file names separated by spaces. chmod mode file [file ...] Changes permissions of a file or list of files. ls The following are examples of the chmod command that change the permissions of the specified files. ASMCMD [+fra/orcl/archivelog/flashback]>chmod ug+rw log_7.264.684968167 log_8.265.684972027 ASMCMD [+fra/orcl/archivelog/flashback]>chmod 640 log_7.264.684968167 log_8.265.684972027 ASMCMD [+]>ls --permission +fra/orcl/archivelog/flashback User Group Permission Name grid asm_fra rw-r----- log_7.264.684968167 grid asm_fra rw-r----- log_8.265.684972027 mode can one of the following forms: { ugo | ug | uo | go | u | g | o | a } {+|- } {r|w |rw} a specifies permissions for all users, u specifies permissions for the owner of the file, g specifies the group permissions, and o specifies permissions for other users. { 0|4|6} {0|4|6} {0|4|6} The first digit specifies owner permissions, the second digit specifies group permissions, and the third digit specifies other permissions. The options for the chmod command are described below. 6 - Read write permissions 4 - Read only permissions 0 - No permissions u - Owner permissions, used with r or w g - Group permissions, used with r or w o - Other user permissions, used with r or w a - All user permissions, used with r or w + - Add a permission, used with r or w - - Removes a permission, used with r or w r - Read permission w - Write permission file - Name of a file This command accepts a file name or multiple file names separated by spaces. The specified files must be closed. You can only set file permissions to read-write, read-only, and no permissions. You cannot set file permissions to write-only. To view the permissions on a file, use the ASMCMD ls command with the --permission option. See "ls". chown user[:usergroup ] file [file ...] Changes the owner of a file or list of files. The following are examples of the chown command that change the owner of the specified files to the oracle1 operating system user. ASMCMD [+fra/orcl/archivelog/flashback]>chown oracle1 log_7.264.684968167 log_8.265.684972027 ASMCMD [+fra/orcl/archivelog/flashback]>chown oracle1:asm_fra log_9.264.687650269 The options for the chown command are described below. user - The name of the user that becomes the new owner. usergroup - Name of the user group to which the user belongs. file - Name of a file. user typically refers to the user that owns the database instance home. Oracle ASM File Access Control uses the operating system (OS) name to identify a database. This command accepts a file name or multiple file names separated by spaces. The specified files must be closed. Only the Oracle ASM administrator can use this command. groups diskgroup user Lists all the user groups to which the specified user belongs. The following is an example of the groups command that displays the user groups of the DATA disk group to which the oracle1 user belongs. ASMCMD [+]>groups DATA oracle1 asm_data The options for the groups command are described below. diskgroup - Name of the disk group to which the user belongs. user - Name of the user. grpmod { --add | --delete } diskgroup usergroup user [user...] Adds or removes operating system (OS) users to and from an existing Oracle ASM user group. The following are examples of the grpmod command. The first example adds the oracle1 and oracle2 users to the asm_fra user group of the FRA disk group. The second example removes the oracle2 user from the asm_data user group of the DATA disk group. ASMCMD [+]grpmod --add fra asm_fra oracle1 oracle2 ASMCMD [+]grpmod --delete data asm_data oracle2. add delete The options for the grpmod command are described below. --add - Specifies to add users to the user group. --delete - Specifies to delete users from the user group. diskgroup - Name of the disk group to which the user group belongs usergroup - Name of the user group. user - Name of the user to add or remove from the user group. Only the owner of the user group can use this command. The command requires the SYSASM privilege to run. This command accepts an operating system user name or multiple user names separated by spaces. The operating system users are typically owners of a database instance home. lsgrp [-a] [--suppressheader] [ -G diskgroup ] [ pattern ] Lists all Oracle ASM user groups or only groups that match a specified pattern. The first example displays a subset of information about the user groups whose name matches the asm% pattern. The second example displays all information about all the user groups. ASMCMD [+] > lsgrp asm% DG_Name Grp_Name Owner FRA asm_fra grid DATA asm_data grid ASMCMD [+] > lsgrp -a DG_Name Grp_Name Owner Members FRA asm_fra grid oracle1 DATA asm_data grid oracle1 oracle2 a suppressheader G The options for the lsgrp command are described below. -a - Lists all columns. --suppressheader - Suppresses column headings. -G diskgroup - Limits the results to the specified disk group name. pattern - Displays the user groups that match the pattern expression. lsusr [-a] [--suppressheader] [ -G diskgroup ] [ pattern ] Lists Oracle ASM users in a disk group. The example lists users in the DATA disk group and also shows the operating system user Id assigned to the user. ASMCMD [+] > lsusr -G DATA User_Num OS_ID OS_Name 3 1001 grid 1 1021 oracle1 2 1022 oracle2 a suppressheader G The options for the lsusr command are described below. -a - List all users and the disk groups to which the users belongs. --suppressheader - Suppresses column headings. -G diskgroup - Limits the results to the specified disk group name. pattern - Displays the users that match the pattern expression. mkgrp diskgroup usergroup [user] [user...] Creates a new Oracle ASM user group. This example creates the asm_data user group in the DATA disk group and adds the oracle1 and oracle2 users to the user group. ASMCMD [+] > mkgrp data asm_data oracle1 oracle2 The options for the mkgrp command are described below. diskgroup - Name of the disk group to which the user group will be added. usergroup - Name of the user group to add. 30 is the maximum number of characters. user - Name of the database user to add to the user group. You can optionally specify a list of users to be included as members of the new user group. mkusr diskgroup user Adds an operating system (OS) user to a disk group. The first example adds the oracle1 user to the DATA disk group. The second example adds the oracle2 user to the FRA disk group. ASMCMD [+] > mkusr DATA oracle1 ASMCMD [+] > mkusr FRA oracle2 The options for the mkusr command are described below. diskgroup - Specifies the name of the disk group to which the user is to be added. user - Name of the user that you want to add. The user to be added must be a valid operating system user. Only a user authenticated as SYSASM can execute this command. passwd user Changes the password of a user. This example changes the password of the oracle2 user. ASMCMD [+] > passwd oracle2 Enter old password (optional): Enter new password: ****** The options for the passwd command are described below. user - Name of the user. An error is raised if the user does not exist in the Oracle ASM password file. The user is first prompted for the current password, then the new password. The command requires the SYSASM privilege to run. rmgrp diskgroup usergroup Removes a user group from a disk group. This example removes the asm_data user group from the DATA disk group. ASMCMD [+] > rmgrp DATA asm_data The options for the rmgrp command are described below. diskgroup - Name of the disk group to which the user group belongs usergroup - Name of the user group to delete. Note that removing a group might leave some files without a valid group. To ensure that those files have a valid group, explicitly update those files to a valid group. See "chgrp". The command must be run by the owner of the group and also requires the SYSASM privilege to run. rmusr [-r] diskgroup user Deletes an operating system (OS) user from a disk group. This example removes the oracle2 user from the DATA disk group. ASMCMD [+] > rmusr DATA oracle2 r The options for the rmusr command are described below. -r - Removes all files in the disk group that the user owns at the same time that the user is removed. diskgroup - Specifies the name of the disk group from which the user is to be deleted. user - Name of the user that you want to delete. Only a user authenticated as SYSASM can execute this command. volcreate -G diskgroup -s size [ --column number ] [ --width stripe_width ] [--redundancy {high|mirror|unprotected} ] [--primary {hot|cold}] [--secondary {hot|cold}] volume Creates an Oracle ADVM volume in the specified disk group. This creates volume1 in the DATA disk group with the size set to 10 gigabytes. ASMCMD [+] > volcreate -G DATA -s 10G --width 64K --column 8 volume1 ASMCMD [+] > volinfo -G DATA volume1 Diskgroup Name: DATA Volume Name: VOLUME1 Volume Device: /dev/asm/volume1-123 State: ENABLED Size (MB): 10240 Resize Unit (MB): 512 Redundancy: MIRROR Stripe Columns: 8 Stripe Width (K): 64 Usage: Mountpath: G s column width redundancy primary secondary The options for the volcreate command are described below. -G diskgroup - Name of the disk group containing the volume. -s size - Size of the volume to be created in units of K, M, G, or T. The unit designation must be appended to the number specified. No space is allowed. For example: 20G --column number - Number of columns in a stripe set. Values range from 1 to 8. The default value is 4. --width stripe - Stripe width of a volume. The value can range from 4 KB to 1 MB, at power-of-two intervals, with a default of 128 KB. --redundancy {high|mirror|unprotected} - Redundancy of the Oracle ADVM volume which can be specified for normal redundancy disk groups. The range of values are as follows: unprotected for non-mirrored redundancy, mirror for double-mirrored redundancy, or high for triple-mirrored redundancy. If redundancy is not specified, the setting defaults to the redundancy level of the disk group. --primary {hot|cold} - Intelligent Data Placement specification for primary extents, either hot or cold region. --secondary {hot|cold} - Intelligent Data Placement specification for secondary extents, either hot or cold region. volume - Name of the volume to be created. Can be a maximum of 11 alphanumeric characters; dashes are not allowed. The first character must be alphabetic. When creating an Oracle ADVM volume, a volume device name is created with a unique Oracle ADVM persistent disk group number that is concatenated to the end of the volume name. The unique number can be one to three digits. On Linux, the volume device name is in the format volume_name-nnn. On Windows the volume device name is in the format asm-volume_name-nnn. The volume device file can be used as any other disk or logical volume to mount file systems or for applications to use directly. You can determine the volume device name with the volinfo command, described in "volinfo". A successful volume creation automatically enables the volume device. The volume device file can be used as any other disk or logical volume to mount file systems or for applications to use directly. voldelete -G diskgroup volume Deletes an Oracle ADVM volume. This example deletes volume1 from the DATA disk group. ASMCMD [+] > voldelete -G DATA volume1 G The options for the voldelete command are described below. -G diskgroup - Name of the disk group containing the volume. volume - Name of the volume to be operated on. To successfully execute this command, the local Oracle ASM instance must be running and the disk group required by this command must be mounted in the Oracle ASM instance. Before deleting a volume, you must ensure that there are no active file systems associated with the volume. voldisable { -a | -G diskgroup -a | -G diskgroup volume } Disables Oracle ADVM volumes in mounted disk groups and removes the volume device on the local node. This example disables volume1 in the DATA disk group. ASMCMD [+] > voldisable -G DATA volume1 a G The options for the voldisable command are described below. -a - When used without a disk group name, specifies all volumes within all disk groups. When used with a disk group name (-G diskgroup -a), specifies all volumes within that disk group. -G diskgroup - Name of the disk group containing the volume. volume - Name of the volume to be operated on. Can be maximum of 30 alphanumeric characters. The first character must be alphabetic. You can disable volumes before shutting down an Oracle ASM instance or dismounting a disk group to verify that the operations can be accomplished normally without including a force option due to open volume files. Disabling a volume also prevents any subsequent opens on the volume or device file as it no longer exists. Before disabling a volume, you must ensure that there are no active file systems associated with the volume. You must first dismount the Oracle ACFS file system before disabling the volume. You can delete a volume without first disabling the volume. volenable { -a | -G diskgroup -a | -G diskgroup volume } Enables Oracle ADVM volumes in mounted disk groups. This example enables volume1 in the DATA disk group. ASMCMD [+] > volenable -G DATA volume1 a G The options for the volenable command are described below. -a - When used without a disk group name, specifies all volumes within all disk groups. When used with a disk group name (-G diskgroup -a), specifies all volumes within that disk group. -G diskgroup - Name of the disk group containing the volume. volume - Name of the volume to be operated on. A volume is enabled when it is created. volinfo { -a | -G diskgroup -a | -G diskgroup volume } volinfo {--show_diskgroup |--show_volume} volumedevice Displays information about Oracle ADVM volumes. This example displays information about the volume1 volume in the DATA disk group. ASMCMD [+] > volinfo -G DATA volume1 Diskgroup Name: DATA Volume Name: VOLUME1 Volume Device: /dev/asm/volume1-123 State: ENABLED Size (MB): 10240 Resize Unit (MB): 512 Redundancy: MIRROR Stripe Columns: 8 Stripe Width (K): 64 Usage: ACFS Mountpath: /u01/app/acfsmounts/acfs1 a G show_diskgroup show_volume The options for the volinfo command are described below. -a - When used without a disk group name, specifies all volumes within all disk groups. When used with a disk group name (-G diskgroup -a), specifies all volumes within that disk group. -G diskgroup - Name of the disk group containing the volume. volume - Name of the volume. --show_diskgroup - Returns only the disk group name. A volume device name is required. --show_volume - Returns only the volume name. A volume device name is required. volumedevice - Name of the volume device. volresize -G diskgroup -s size [ -f ] volume Resizes an Oracle ADVM volume. This example resizes volume1 in the DATA disk group to 20 gigabytes. ASMCMD [+] > volresize -G DATA -s 20G volume1 G s f The options for the volresize command are described below. -G diskgroup - Name of the disk group containing the volume. -f - Force the shrinking of a volume that is not an Oracle ACFS volume to suppress the warning message. volume - Name of the volume to be operated on. -s size - New size of the volume in units of M, G, or T. If the volume is not an Oracle ACFS volume and the new size is smaller than current, you are warned of possible data corruption. Unless the -f (force) option is specified, you are prompted whether to continue with the operation. If there is an Oracle ACFS file system on the volume you cannot resize the volume with the volresize command. You must use the acfsutil size command, which also resizes the volume and file system. volset -G diskgroup [ --usagestring string] [--mountpath mount_path ] [--primary {hot|cold}] [--secondary {hot|cold}] volume Sets attributes of an Oracle ADVM volume in mounted disk groups. This example sets the usage string for a volume that is not attached to a file system. ASMCMD[+]>volset -G DATA --usagestring 'no file system attached' volume1 G usagestring mountpath primary secondary The options for the volset command are described below. -G diskgroup - Name of the disk group containing the volume. --usagestring string - Optional usage string to tag a volume which can be up to 30 characters. This string is set to ACFS when the volume is attached to a file system and should not be changed. --mountpath mount_path - Optional string to tag a volume with its mount path string which can be up to 1024 characters. This string is for user information only. --primary {hot|cold} - Intelligent Data Placement specification for primary extents, either hot or cold region. --secondary {hot|cold} - Intelligent Data Placement specification for secondary extents, either hot or cold region. volume Name of the volume to be operated on. volstat [-G diskgroup][volume] Reports I/O statistics for Oracle ADVM volumes The following is an example of the volstat command that displays information about volumes in the data disk group. ASMCMD [+] > volstat -G data DISKGROUP NUMBER / NAME: 1 / DATA --------------------------------------- VOLUME_NAME READS BYTES_READ READ_TIME READ_ERRS WRITES BYTES_WRITTEN WRITE_TIME ------------------------------------------------------------------------------------------ VOLUME1 10085 2290573312 22923 0 1382 5309440 1482 (continued)WRITE_ERRS ------- 0 G The options for the volstat command are described below -G diskgroup - Name of the mounted disk group containing the volume volume - Name of the volume to be operated on. The following apply when using volstat command. If the disk group is not specified and the volume name is specified, all mounted disk groups are searched for the specified volume name. If the disk group name is specified and the volume name is omitted, then all volumes are displayed for the named disk group If both the disk group name and volume name are omitted, all volumes on all disk groups are displayed. analyze [-G diskgroup] [--node node] [--events regex] [--starttime time] [--endtme time] [--tracedirectory directory] This command looks at the system (or the set of logs/traces) to identify siginificant events that have happened in the cluster that affect the workings of the storage subsystem provided by Automatic Storage Management (ASM). The compute node is analyzed to identify anomolies that might be of interest to explain the system behavior. The events that are collected are sorted in chronological order. ASMCMD [+] >analyze HOSTNAME INSTANCE DG NAME PID EVENT RESOLUTION DISK PATH TRACEFILE ---------------------------------------------------------------------------------------------------------------- hostname1 +ASM1 +DATA DBW0(1524) Write Error Disk offlined /dev/raw/raw1 +asm1_dbw0_1 G node starttime endtime events tracedirectory The options for the analyze command are described below. -G - Comma seperated list of diskgroups to operate on, or patterns of the diskgroup names. By default all the diskgroups that are discovered in the cluster are scanned --node - Comma seperated list of nodes that are considered for the analysis. Specifying -N automatically implies -g. When the option is not specified the current list of configured nodes are discovered by querying the CRS framework. --events - The specific events that user is interested in, the event specification can be made as a pattern. The list of events are enumerated in the events table. --starttime - The starting time for the analysis phase. The time can be specified in any one of the formats that appear in the trace files. --endtime - The ending time of the epoch that is to be analyzed. The format of the time specification is same as that of the --starttime. --tracedirectory - The directory that contains the set of logs and trace files that needs to be analyzed. The analyze commands understand the various traces that are generated by the oracle stack. The command will analyze the contents of those containers to find the relevant data. When the --tracedirectory parameter is not specified the default list of traces are collected. asmcmd [-V] [-v <errors|warnings|normal|info|debug> [--privilege <sysasm|sysdba>] [-p] [command] Starts asmcmd (if no parameters) or executes with given parameters V v a p c Specify the connect string after the -c option to use the listener to connect. By default, ASMCMD asks for a password in a non-echoing prompt, unless the password is specified as part of the connect string. The connect identifier is in the form of "host:port:sid", with the host and the port being option. Host defaults to "localhost" and port to 1521. If the sid is not specified as a part of the connect identifier, then it is read from the environment variable ORACLE_SID. If no connect string is used, then the environment variables ORACLE_HOME and ORACLE_SID determine the instance to which the program connects, and asmcmd establishes a bequeath connection to the it, in the same manner as a SQLPLUS / AS SYSASM. The user must be a member of the SYSDBA group to exercise this option. Specifying the -V option prints the asmcmd version number and exits immediately. Specifying the -v option prints extra information that can help advanced users diagnose problems. Specify the --privilege option to choose the type of connection. There are only two possibilities: connecting as SYSASM or as SYSDBA. The default value if this option is unspecified is SYSDBA. Specifying the -p option allows the current directory to be displayed in the command prompt, like so: ASMCMD [+DATA/ORCL/CONTROLFILE] > The parameter command specifies one of the following commands, along with its parameters. Type "help [command]" to get help on a specific ASMCMD command.'; asmcmd [-V] [-v <errors|warnings|normal|info|debug>] [--privilege <sysasm|sysdba>] [-p] [command] Starts asmcmd or executes the command V v a p The environment variables ORACLE_HOME and ORACLE_SID determine the instance to which the program connects, and ASMCMD establishes a bequeath connection to it, in the same manner as a SQLPLUS / AS SYSASM. The user must be a member of the OSASM group. Specifying the -V option prints the asmcmd version number and exits immediately. Specifying the -v option prints extra information that can help advanced users diagnose problems. Specify the --privilege option to choose the type of connection. There are only two possibilities: connecting as SYSASM or as SYSDBA. The default value if this option is unspecified is SYSASM. Specifying the -p option allows the current directory to be displayed in the command prompt, like so: ASMCMD [+DATA/ORCL/CONTROLFILE] > [command] specifies one of the following commands, along with its parameters. Type "help [command]" to get help on a specific ASMCMD command.'; help [command] Displays help for the specified command.