Start a Conversation

Unsolved

This post is more than 5 years old

966

June 1st, 2010 09:00

dd error on cluster, installing oracle 10g

Hi, I'm trying to install Oracle 10G on two nodes with OS AIX 5.3, using emc storage and powerpath 5.3

when I execute the next command at same time, on both nodes, I'm receving the next error:

{node1:root}/ -> dd if=/dev/zero of=/dev/ora_vote_raw bs=8192 count=25000
25000+0 records in.
25000+0 records out.

{node2:root}/ -> dd if=/dev/zero of=/dev/ora_vote_raw bs=8192 count=25000
dd: 0511-053 The write failed.
: The requested resource is busy.


This is the procedure executed on both nodes

1. Install EMC ODM drivers

2. run cfgmgr to detect devices

3. Install PowerPath version 5.3

4. register PowerPath
{node1:root}/ -> emcpreg –install

5. initialize PowerPath devices
{node1:root}/ -> powermt config

6. save PowerPath configuration
{node1:root}/ -> powermt save

7. Identify hdiskpower devices for ocr and voting disk

{node1:root}/ -> ls -la /dev/rhdiskpower0
crw-rw----    1 root     system       45,  0 Jun 01 10:17 rhdiskpower0

{node1:root}/ -> ls -la /dev/rhdiskpower10
crw-rw----    1 root     system       45, 10 Jun 01 10:17 rhdiskpower10

8. Create a device on each node for ocr and voting disk.

{node1:root}/ -> mknod /dev/ora_ocr_raw c 45 0

{node1:root}/ -> mknod /dev/ora_vote_raw c 45 10

9. configure the reserve_lock, attribute must be set to "no"
{node1:root}/ -> chdev -l hdiskpower0 -a reserve_lock=no
{node1:root}/ -> chdev -l hdiskpower10 -a reserve_lock=no

10. Verify the attribute is set
{node1:root}/ -> lsattr –El hdiskpower0
{node1:root}/ -> lsattr –El hdiskpower10

5 Practitioner

 • 

274.2K Posts

June 22nd, 2010 12:00

There is an issue with PP 5.3 in a cluster where some times it will leave an invalid reserve behind.  From what I'm reading in your post this is likely the cause of your issue.

In fact there is a number of patches for this in SP1.  As well there is at least one more invalid reserve issue. There is supposed to be a hot fix coming for that.

Customers I've worked with in the past have downgraded to PP 5.1.1 in order to get past this.

You have two paths you can try to see if it resolves your issue.

1.  Upgrade to 5.3 SP1 or

2.  Downgrade to 5.1.1

JTC

AFSS

1 Rookie

 • 

137 Posts

August 2nd, 2010 23:00

Hi,  Just wondering if moving to SP1 or down a level resolved your issue?

Regards,

  Nollaig

No Events found!

Top