Oracle on RHEL4 with ASM problem
Lunt, Nick
Nick.Lunt at wesleyan.co.uk
Mon May 8 13:01:07 UTC 2006
Tom/Jack,
I think we'll stick with the block devices for now. I really need to setup ASM on a dev box and see what I can come up with.
Thanks for the detailed advice and explanations you've both offered, it's been a tremendous help in getting me to understand whats going on.
Cheers,
Nick .
> -----Original Message-----
> From: Tom Callahan [mailto:callahant at tessco.com]
> Sent: 08 May 2006 13:51
> To: General Red Hat Linux discussion list
> Subject: Re: Oracle on RHEL4 with ASM problem
>
>
> I just tried this exact same exercise, and I get the same errors......
>
> I realize it says you must use raw devices in the document that was
> linked......but I don't know if I believe it. I would belive that the
> ASMLIB for Linux may not support System-based adding of raw
> devices, and
> that you may have to do it within the ASM instance.....
>
> I would try this on a test instance if you can, but try
> logging into the
> ASM instance and issue the following:
>
> < alter diskgroup YOURDSKGRP add disk '/dev/raw/raw1'
> rebalance power 8; >
>
> This will attempt to add the new disk, and rebalance the ASM
> Storage..... But again, PLEASE do this on a Test or Dev box....
>
> This may require and Oracle TAR asking about ASM and Block
> vs. Character
> devices.
>
> Tom Callahan
> TESSCO Technologies
> Desk: (410)-229-1361
> Cell: (410)-588-7605
> Email: callahant at tessco.com
>
> A real engineer only resorts to documentation when the
> keyboard dents on the forehead get too noticeable.
>
>
>
> Lunt, Nick wrote:
>
> >
> >
> >>-----Original Message-----
> >>From: Tom Callahan [mailto:callahant at tessco.com]
> >>
> >>
> >
> >
> >
> >>Go into /etc/udev/permissions.d/50-udev-permissions and ABOVE the
> >>exising lines for raw devices, put the following:
> >>
> >># Oracle 10g Devices
> >>raw/raw1:oracle:oinstall:0640
> >># End Oracle 10g Devices
> >>
> >>
> >>You can add rawdevices to that list as well. You MUST do this
> >>with UDEV,
> >>and it has to be above the existing raw* lines, otherwise
> it will not
> >>work correctly.
> >>
> >>
> >
> >Thanks Tom,
> >
> >I did as you suggested and now the permissions on
> /dev/raw/raw1 change to oracle:oinstall when I restart
> rawdevices but I still get this error when I add in raw1 to ASM :
> >
> >[root at bounty sysconfig]$ /etc/init.d/oracleasm createdisk
> VOL14 /dev/raw/raw1
> >Marking disk "/dev/raw/raw1" as an ASM disk: asmtool: Unable
> to open device "/dev/raw/raw1": Block device required [FAILED]
> >
> >[root at bounty sysconfig]$ ll /dev/raw
> >total 0
> >crw-r----- 1 oracle oinstall 162, 1 May 8 13:30 raw1
> >
> >[root at bounty sysconfig]$ grep raw1
> /etc/udev/permissions.d/50-udev.permissions
> >raw/raw1:oracle:oinstall:0640
> >
> >[root at bounty sysconfig]$ service rawdevices status
> >/dev/raw/raw1: bound to major 8, minor 240
> >
> >Cheers,
> >Nick .
> >
> >Wesleyan Administration Services Ltd registered number
> 5188850 and Wesleyan Unit Trust Managers Ltd registered
> number 2114859 ("WUTM Ltd") are wholly owned subsidiary
> companies of Wesleyan Assurance Society, whose registered
> number is ZC145. WUTM Ltd is a member of IMA. For
> ISA/PEP/Unit Trusts Administration Centre: PO Box 9033,
> Chelmsford, SM99 2WQ Telephone: 0870 601 6129 Wesleyan
> Assurance Society and WUTM Ltd are authorised and regulated
> by the Financial Services Authority. Head Office, Colmore
> Circus, Birmingham B4 6AR. Telephone: 0121 200 3003 Fax 0121
> 200 2971. Website: www.wesleyan.co.uk Telephone calls may be
> recorded for monitoring and training purposes.
> >
> >CONFIDENTIALITY NOTICE
> >
> >This communication and the information it contains is
> intended for the person or organisation to whom it is
> addressed. Its contents are confidential and may be protected
> in law. Unauthorised use, copying or disclosure of any of it
> may be unlawful. If you are not the intended recipient,
> please contact us immediately.
> >
> >The contents of any attachments in this e-mail may contain
> software viruses, which could damage your own computer
> system. While every reasonable precaution to minimise this
> risk has been taken, we cannot accept liability for any
> damage that you sustain as a result of software viruses. You
> should carry out your own virus checking procedure before
> opening any attachment.
> >
> >Delivered using mail2.wesleyan.co.uk
> >
> >
> >
> >
>
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list
>
> Delivered using mail2.wesleyan.co.uk
>
More information about the redhat-list
mailing list