oraclebase
commented
2 years ago Hi.
No. Look at the build. Everything is owned by the "grid" user. The only reason to have a separate "grid" user is if you have separation of duties. DBAs looking after the database and non-DBAs looking after the grid infrastructure and storage. Having the two separate users is an additional complication if the DBAs are the only people looking after both the database and grid infrastructure.
If you prefer you can separate the two, but I dislike it. I've never worked in a company that has the grid infrastructure managed by someone other than the DBAs.
Cheers
Tim...
Hi Dear, in the https://github.com/oraclebase/vagrant/blob/master/rac/ol8_19/shared_scripts/configure_shared_disks.sh
the owner would be grid but not oracle ,right?
cat > /etc/udev/rules.d/99-oracle-asmdevices.rules <<EOF KERNEL=="sd?1", SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/\$parent", RESULT=="${ASM_DISK1}", SYMLINK+="oracleasm/asm-crs-disk1", OWNER="oracle", GROUP="dba", MODE="0660" KERNEL=="sd?1", SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/\$parent", RESULT=="${ASM_DISK2}", SYMLINK+="oracleasm/asm-crs-disk2", OWNER="oracle", GROUP="dba", MODE="0660" KERNEL=="sd?1", SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/\$parent", RESULT=="${ASM_DISK3}", SYMLINK+="oracleasm/asm-crs-disk3", OWNER="oracle", GROUP="dba", MODE="0660" KERNEL=="sd?1", SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/\$parent", RESULT=="${ASM_DISK4}", SYMLINK+="oracleasm/asm-data-disk1", OWNER="oracle", GROUP="dba", MODE="0660" KERNEL=="sd?1", SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/\$parent", RESULT=="${ASM_DISK5}", SYMLINK+="oracleasm/asm-reco-disk1", OWNER="oracle", GROUP="dba", MODE="0660" EOF