3 Replies Latest reply: May 4, 2012 6:13 PM by onedbguru RSS

    ASM installation fails on Solaris 11

    Mithzz
      Hi,

      I am trying to install Oracle 11.2.0.3 on Solaris 11 x64 server (installed as a vm) with ASM. Plan is to install grid and configured ASM on standalone type of a setup and create database on ASM.

      While creating ASM disks i am getting

      >
      ORA-15018: diskgroup cannot be created :
      ORA-00600: internal error code, arguments: [kfmNew], [2], [], [], [], [], [], [], [], [], [], []
      >

      &
      >
      ORA-15036: disk "/dev/rdsk/c4t5d0s8" is truncated"
      {quote}
      errors

      Can anyone guide me for a solution.

      Solaris 11 version :
      {quote}
      avamar@Solaris11Oracle11g:~$ uname -a
      SunOS Solaris11Oracle11g 5.11 11.0 i86pc i386 i86pc
      {quote}

      --Amith

      --Amith
        • 1. Re: ASM installation fails on Solaris 11
          415289
          Troubleshooting : ORA-600/ORA-7445 Error Look-up Tool on MOS
          if no detail available then raise SR to oracle.
          • 2. Re: ASM installation fails on Solaris 11
            G Srikanth
            ORA-15036: disk "/dev/rdsk/c4t5d0s8" is truncated" This generally happens when O/S Disk is been altered after creating ASM Disks. did you make any changes to the existing disks in O/S after creating ASM DISKS.

            Edited by: G Srikanth on May 3, 2012 4:27 PM
            • 3. Re: ASM installation fails on Solaris 11
              onedbguru
              G Srikanth wrote:
              ORA-15036: disk "/dev/rdsk/c4t5d0s8" is truncated" This generally happens when O/S Disk is been altered after creating ASM Disks. did you make any changes to
              the existing disks in O/S after creating ASM DISKS.
              more specifically this occurs when you overwrite the VTOC. You can avoid this by creating the main partition as starting at cylinder 0-1 and partition 2 as cylinder 2 through <last cylinder> making /dev/rdsk/c4t5d0s8{p1|p2} This will skip the first 1M (block 0 and 1) where the VTOC is stored. You will need to do this for ALL ASM devices.

              To prevent this on any OS, I have adopted that as a standard for all ASM devices. My disk discovery path is /dev/mapper/*p2 (Linux using multipath) Then make sure *p2 has owner:group <gridOwner>:<dba>

              >
              Edited by: G Srikanth on May 3, 2012 4:27 PM