This article will introduce to you the problem that the solution to the asm disk cannot be found when dbca creates a db in Oracle. If you encounter such problems, you will not be able to access the reference.
If you use dbca to create a database, select the asm disk, but the asm disk cannot be found.
When installing grid, there are two scripts to be executed. One of the scripts is/u01/app/oraInventory/orainstRoot. sh, which will modify the permission. I think it may be a permission issue.
On the asmcmd side, you can view the asm disk group.
[Grid @ rac22 ~] $ Asmcmd
ASMCMD> ls
DATA/
DATA1/
DATA2/
See the following statement on the Internet:
After Grid Infrastructure and Database are installed, the owner of the installation directory may change to root. do not modify the owner of the installation directory or modify the permissions of the Directory and its files when you reinstall or upgrade it. If the owner is modified, for example, after the directory owner is changed from root: oinstall to grid: oinstall, or the read and write permissions of the Directory and its files are changed to 777, the created ASM disk may not be found when dbca creates a database.
[Root @ rhel1 bin] # su-grid
[Grid @ rhel1 ~] $ Cd $ GRID_HOME/bin
[Grid @ rhel1 bin] $ chmod + s oracle
Chmod + s meaning:
To facilitate normal users to execute some privileged commands, the SUID/SGID program allows normal users to temporarily execute the program as root and resume their identities after the execution is complete. Chmod + s gives suid permission to a program or script.