3 Replies Latest reply: Mar 7, 2014 4:20 PM by user130038 RSS

    why "asmca" is changing ownership of disks from "oracle:oinstall" to "root:disk"?

    user130038

      Hi

       

      I am preparing a new oracle server with following config:

       

      Oracle Grid Infra 11.2.0.3 (patched to 11.2.0.3.6) - 64-bit

      Oracle 11gR2 11.2.0.3 (patched to 11.2.0.3.6) - 64-bit

      Platform: OEL 6.2 64-bit

      VMWare Virtual Machine

      Device persistence is being handled by VMWare - I am not suing ASMLib.

       

      I have completed the installation. Here are the steps I followed:

       

      Install GI 11.2.0.3 (OSDBA for ASM=asmdba, OSOPER for ASM=asmdba, OSASM=asmadmin)

      Patch it to 11.2.0.3.6 (applied Apr 2013 PSU)

      Install RDBMS 11.2.0.3 (OSDBA=dba, OSOPER=dba)

      Patch it to 11.2.0.3.6 (applied Apr 2013 PSU)

       

      I checked the permissions of the raw devices and they were:

       

      brw-rw---- 1 oracle oinstall 8,  48 Feb 28 16:53 /dev/sdd

      brw-rw---- 1 oracle oinstall 8,  64 Feb 28 16:53 /dev/sde

      brw-rw---- 1 oracle oinstall 8,  80 Feb 28 16:53 /dev/sdf

      brw-rw---- 1 oracle oinstall 8,  96 Feb 28 16:53 /dev/sdg

      brw-rw---- 1 oracle oinstall 8, 112 Feb 28 16:53 /dev/sdh

      brw-rw---- 1 oracle oinstall 8, 128 Feb 28 16:53 /dev/sdi

      brw-rw---- 1 oracle oinstall 8, 144 Feb 28 16:53 /dev/sdj

      brw-rw---- 1 oracle oinstall 8, 160 Feb 28 16:53 /dev/sdk

      brw-rw---- 1 oracle oinstall 8, 176 Feb 28 16:53 /dev/sdl

      brw-rw---- 1 oracle oinstall 8, 192 Feb 28 16:53 /dev/sdm

       

      Now I started the "asmca" to configure the ASM Instance. Initially there were no disk-devices displayed. So I pressed the "Change disk discovery path" button. The moment I press the "OK" button, the permissions of the disks change to "root disk" from "oracle oinstall".

       

      brw-rw---- 1 root disk 8,  48 Feb 28 17:15 /dev/sdd

      brw-rw---- 1 root disk 8,  64 Feb 28 17:15 /dev/sde

      brw-rw---- 1 root disk 8,  80 Feb 28 17:15 /dev/sdf

      brw-rw---- 1 root disk 8,  96 Feb 28 17:15 /dev/sdg

      brw-rw---- 1 root disk 8, 112 Feb 28 17:15 /dev/sdh

      brw-rw---- 1 root disk 8, 128 Feb 28 17:15 /dev/sdi

      brw-rw---- 1 root disk 8, 144 Feb 28 17:15 /dev/sdj

      brw-rw---- 1 root disk 8, 160 Feb 28 17:15 /dev/sdk

      brw-rw---- 1 root disk 8, 176 Feb 28 17:15 /dev/sdl

      brw-rw---- 1 root disk 8, 192 Feb 28 17:15 /dev/sdm

       

      Any clue?

       

      Please help - dead line is fast approaching (Monday).

       

      Best regards

       

      Message was edited by: user130038

        • 1. Re: why "asmca" is changing permissions of disks to "root"?
          Ali Gusainov

          Hi.

          Maybe mknod will be better for ur configuration.

          Does the node rebooted between 16:53 and 17:15? If so, udev must be configured. ORACLE-BASE - UDEV SCSI Rules Configuration for ASM in Oracle Linux 5 and 6

           

          Regards

          • 2. Re: why "asmca" is changing permissions of disks to "root"?
            Hemant K Chitale

            The OK button for "Change discovery path" wouldn't change ownerships from oracle to root.  The change would have happened earlier.   How was the ownership set to "oracle" ?  Was there a reboot before running asmca ?

             

             

            Hemant K Chitale


            • 3. Re: why "asmca" is changing permissions of disks to "root"?
              user130038

              What I meant by "OK" button was the button you press after inputting the "disk discovery path". I was watching the disk ownership in a separate putty session using following script:

               

              while true

              do

                  ls -l /dev/sd*

                  date

                  sleep 1

                  clear

              done

               

              It may not be the OK button code but maybe some Oracle background process (ocssd or something like that) who changed the ownership.

               

              The ownership was set using chown and is made effective at boot time using "/etc/rc.local". We did reboot the server to check if the ownership stays after reboot - it did remain what it was set to (oracle:oinstall).

               

              I am puzzled why oracle is changing the ownership of disks from correct (oracle:oinstall) to incorrect (root:root) and then start complaining about it?

               

              Is this a BUG?

               

              I opened an SR with support. They asked me to follow MOS Doc ID 1313687.1 (disk aliases - "mknod" as Ali said in his response above). I did follow this document but "asmca" was not able to see/detect the disk devices.

               

              I was about to miss the deadline but I was asked to go ahead to use filesystem instead of ASM.

               

              Now my server has GI installed but the databases are on filesystem. I did not have time to try and uninstall the GI. It is a bit of mess I guess.

               

              Best regards

               

              Message was edited by: user130038