• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 799
  • Last Modified:

oracle auto start asm and mount diskgroups on boot server

Hello,

Instance oracle asm doesn't start on boot.
I have created raw devices  :

vi /etc/udev/rules.d/63-oracle-raw.rules
ACTION=="add", KERNEL=="sdc1", RUN+="/bin/raw /dev/raw/raw1 %N"
ACTION=="add", KERNEL=="sdd1", RUN+="/bin/raw /dev/raw/raw2 %N"
ACTION=="add", KERNEL=="sdf1", RUN+="/bin/raw /dev/raw/raw3 %N"
KERNEL=="raw[1-3]*", OWNER="oracle", GROUP="oinstall", MODE="644
[root@srvtest raw]# chmod 777  /dev/raw/raw1
[root@srvtest raw]# chmod 777  /dev/raw/raw2
[root@srvtest raw]# chmod 777  /dev/raw/raw3

[root@srvtest raw]# chown oracle:dba /dev/raw/raw1
[root@srvtest raw]# chown oracle:dba /dev/raw/raw2
[root@srvtest raw]# chown oracle:dba /dev/raw/raw3

and I have created asmdiskgroup with dbca.

But on boot, asm diskgroup are not mounted

I have to execute chmod and chown on raws and "/etc/init.d/init.cssd stop" then "/etc/init.d/init.cssd start"

Why?

Thanks
0
bibi92
Asked:
bibi92
1 Solution
 
cheers4beersCommented:
What is your OS and Oracle version?
0
 
bibi92Author Commented:
Redhat 5 and oracle 10.2.0.5 thanks
0
 
SurranoSystem EngineerCommented:
In udev rules, you wrote permissions 644 and owner oracle:oinstall
but in chmod/chown commands you wrote 777 and oracle:dba

I believe the correct one (in both places) would be 664 oracle:oinstall
I assume it's either user oracle or grid or crs that runs ASM but typically it's a member of oinstall group so it should work.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now