I was very used to create ASM instance manually before 11gR2. With 11gR2 we must to install Grid Infrastructure even on sigle instance databases if we’re going to use ASM. In my last installation i had strange errors that i’ll share below. First error was complaining about the password and the log file is:
INFO: Executing ASMCAINFO: Command /u01/app/oracle/product/11.2.0/grid/bin/asmca -silent -oui_internal -configureASM -diskString '/dev/ORACLE/ASMDISKS/*' -diskGroupName DATA -diskList /dev/ORACLE/ASMDISKS/hostx_asm0,/dev/ORACLE/ASMDISKS/hostx_asm1 -redundancy EXTERNALINFO: ... GenericInternalPlugIn.handleProcess() entered.INFO: ... GenericInternalPlugIn: getting configAssistantParmas.INFO: ... GenericInternalPlugIn: checking secretArguments.INFO: ... GenericInternalPlugIn: starting read loop.INFO: Read: SYS_PASSWORD_PROMPTINFO: Processing: SYS_PASSWORD_PROMPT for argument tag -sysAsmPasswordINFO: Read: ASMSNMP_PASSWORD_PROMPTINFO: Processing: ASMSNMP_PASSWORD_PROMPT for argument tag -asmMonitorPasswordINFO: End of argument passing to stdinINFO: Read:INFO: Read: Configuring ASM failed with the following message:INFO: Read: Adding Monitor user failed. The following error occured:INFO: Read: ORA-00922: missing or invalid optionINFO: Read:INFO: Read:INFO: Completed Plugin named: Automatic Storage Management Configuration AssistantINFO: Automatic Storage Management Configuration Assistant failed.INFO: Automatic Storage Management Configuration Assistant failed.INFO: ConfigClient.executeToolsInAggregate action performed
Installer raised error and quit. Because ASM configuration failed, i run” asmca” to create ASM instance. However, asmca also failed to create the instance and raised the same error.
I was familiar with these errors. What i know was two reasons may cause this.
- Misconfigured ”asm_diskstring” parameter: If wildcard was not set correctly, this errors may occur. I tried some different discovery paths but no chance :(
- Not empty ASM disks as stated on the following doc.
“Disk Is not Discovered in ASM, Diskgroup Creation Fails with Ora-15018 Ora-15031 Ora-15014 [ID 431013.1]
Use the option FORCE of the "create diskgroup" or "alter diskgroup add disk" to enforce overriding the previous content of the disk.
If it really doesn't work, then in very last option :
Use dd to clean up the disk header of all the disks that are not discovered by the ASM instance.”
This also didn’t work. I checked the headers and disks were all empty.
Then i remember the strange error about the ASM sys password and thought if this may be related with the entries (disk path, name etc.) that i write on the asmca screen. Maybe what i see on the screen was not same with what oracle see :)
Then decided to use silent installation on the command line to be sure (and hoping) that this is not the cause. And the result is below:
bash-3.2$ ./asmca -silent -configureASM -sysAsmPassword oracle -asmsnmpPassword oracle -diskString '/dev/ORACLE/ASM/*' -diskGroupName DATA -disk '/dev/ORACLE/ASM/hostx_asm0' -redundancy external
ASM created and started successfully.
DiskGroup DATA created successfully.