Modify the listener used by Oracle ASM, the disk group discovery string used by Oracle ASM, or the SPFILE used by Oracle ASM for a noncluster database or a cluster database.
Note:
To manage Oracle ASM on Oracle Database 12c installations, use the SRVCTL binary in the Oracle Grid Infrastructure home for a cluster (Grid home). If you have Oracle RAC or Oracle Database installed, then you cannot use the SRVCTL binary in the database home to manage Oracle ASM.
Use the srvctl modify asm command with the following syntax:
srvctl modify asm [-listener listener_name] [-pwfile password_file_path] [-count {number_of_instances | ALL}] [-diskstring asm_diskstring] [-spfile spfile_path_name [-proxy] [-force]]
Table A-75 srvctl modify asm Parameters
| Parameter | Description |
|---|---|
-listener listener_name |
The listener name with which Oracle ASM registers |
-pwfile password_file_path |
The full path to the ___location of the password file for Oracle ASM. |
-count {number_of_instances | ALL} |
Specify the number of Oracle ASM instances to create or that an Oracle ASM instance should be created on all nodes. |
-diskstring asm_diskstring |
The new Oracle ASM disk group discovery string |
-spfile spfile_path_name |
The path name of the new spfile to be used by Oracle ASM |
|
|
Indicates a remote ASM instance. You can specify the number of instances or ALL to have instances on all nodes. |
-proxy |
Specifies an Oracle ASM proxy instance |
-force |
Force modification |
|
|
Specifies an ASM rim instance |
The srvctl modify asm command with the -listener listener_name parameter can be used only with Oracle Clusterware.
The -diskstring asm_diskstring and -spfile spfile_path_name parameters are available only with Oracle Restart.
See Also:
Oracle Database Administrator's Guide for more information about using the srvctl modify asm command with Oracle Restart