When you start ASM after manually writing the ASM parameter file, the following error occurs:
ORA-29701: unable to connect to Cluster Manager
Through the explanation of the online document, I learned the reason why the CSS service was not added, run the/u01/app/Oracle/product/10.2/db_1/bin/localconfig add command under the root user to add the CSS service! The problem solved, but the ORA-15110: nodiskgroups mounted error was reported when the asm instance was started (ORA-15110 error occurs when the instance was started, very normal because I have not created diskgroup before)
SQL> select path, mount_status from v $ asm_disk order by disk_number;
PATH MOUNT_S
---------------------------------------------------------
ORCL: VOL01 CLOSED
ORCL: VOL02 CLOSED
Check the disk status. If not, the set asm_diskstring parameter is incorrect and needs to be adjusted.
PATH MOUNT_S
---------------------------------------------------------
ORCL: VOL01 CACHED
ORCL: VOL02 CACHED
Create a disk group
SQL> create diskgroup syasm normal redundancy disk 'orcl: vol01 ';
SQL> alterdiskgroup syasm add disk 'orcl: vol02 ';
Diskgroupcreated.
After the disk group is created, query the v $ asm_disk view again and find that the status of the ASM disk is changed from closed to cached.
SQL> select path, mount_status from v $ asm_disk order by disk_number;
PATH MOUNT_S
---------------------------------------------------------
ORCL: VOL01 CACHED
ORCL: VOL02 CACHED
Create spfile and restart the instance
SQL> create spfile from pfile;
File created.
SQL> shutdown immediate
ASM diskgroups dismounted
ASM instance shutdown
SQL> startup
ASM instance started
Total System Global Area 92274688 bytes
Fixed Size 1217884 bytes
Variable Size 65890980 bytes
ASM Cache 25165824 bytes
ORA-15110: no diskgroups mounted
Unable to start the disk group, and reported ORA-15110 error, decided to manually start the disk group
SQL> alterdiskgroup all mount;
Alterdiskgroup all mount
*
ERROR at line1:
ORA-15110: nodiskgroups mounted.
It cannot be started manually. What is the problem ~
Use SQL> show paramter asm;
NAME TYPE VALUE
-----------------------------------------------------------------------------
Asm_diskgroups string
Asm_diskstring string
Asm_power_limit integer 1
The value after asm_diskgroups is actually vacant. No wonder the disk group cannot be started. Add it manually!
SQL> altersystem set asm_diskgroups = SHIYUEASM scope = both;
Good! Start the disk group again!
SQL> alterdiskgroup all mount;
SQL> startup
ASM instance started
Total System Global Area 92274688 bytes
Fixed Size 1217884 bytes
Variable Size 65890980 bytes
ASM Cache 25165824 bytes
ASM diskgroups mounted
The disk is up. You have created an ASM disk manually!