Alejandro Vargas' Blog

  • May 21, 2007

Clusterware Install hang when running root.sh on second node

Alejandro Vargas
Technical Leader, ACS Global Delivery, Infrastructure & BigData

Lately I've seen this behavior  twice, one on HPUX and another on Linux:

Oracle clusterware install went on smoothly and then hang when running root.sh on the 2nd node, while displaying this message:

Startup will be queued to init within 90 seconds.

There were no errors logged on the second server, truss or strace showed the processes waiting...

On the first server we saw errors logged on $ORA_CRS_HOME/log/<servername>/alert<servername>.log pointing to a problem accessing the OCR raw device.

on HP the problem was solved configuring the raw devices using a whole LUN as described on the install guide.
on Linux the problem was solved pointing directly to the raw devices instead of soft links to them.

Join the discussion

Comments ( 4 )
  • Cristian Cudizio Thursday, June 14, 2007
    i've made two installations of clusterware 10.2 on Suse Linux Enterprise Server 9 (SLES9) and i've used soft links pointing su raw devices for ocr and voting and i haven't get such problem, why?
  • Alejandro Vargas Thursday, June 14, 2007
    thanks for the comment. I don't know the reason of the different behaviour you experienced on Suse.
    As a matter of fact technically I don't see a reason for the soft links to be a problem, I just added the note as the workaround that worked for us in ONE specific case. I'll try to check it again.
  • Cristian Cudizio Thursday, June 14, 2007
    thank's to you for your informations.
    sorry, i've forgot to say that were versions 64 bit.
  • roy Saturday, July 7, 2007
    Hi! im experiencing almost the same problem but mine is when running the root.sh on the first node. It hangs up when queued to init within 90sec. My hardware is an IA64T based architecture. and my linux is RHEL 64bit
    Your help would be much appreciate.
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.