RAC VIP node application Failed
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 4 of 4

Thread: RAC VIP node application Failed

Hybrid View

  1. #1
    Join Date
    Aug 2006
    Posts
    3

    RAC VIP node application Failed

    Hi,

    I recently installed 2 x Compaq DL380G2, connecting to a shared SCSI array, with Redhat 4 EL Update 2 servers and the intention of getting Oracle RAC 10g R2 running.

    After following the steps provided on dbasupport and "Installing Oracle RAC 10g Release 2 on Linux x86" - by John Smiley, I keep getting stuck when running the clusterware "oracle cluster verification utility".

    I have run this command manually to find that it seems to have a problem with uppercase node names. Below I have pasted the output of the commands:
    > ./cluvfy stage -post crsinst -n TGDB01,TGDB02 -verbose
    and
    > ./cluvfy stage -post crsinst -n tgdb01,tgdb02 -verbose

    The command using uppercase node names fails while the lower case passes. Running the commands on either node produces the same result:

    FAILED:
    ./cluvfy stage -post crsinst -n TGDB01,TGDB02 -verbose

    Performing post-checks for cluster services setup

    Checking node reachability...

    Check: Node reachability from node "TGDB01"
    Destination Node Reachable?

    TGDB01 yes
    TGDB02 yes
    Result: Node reachability check passed from node "TGDB01".


    Checking user equivalence...

    Check: User equivalence for user "oracle"
    Node Name Comment

    TGDB02 passed
    TGDB01 passed
    Result: User equivalence check passed for user "oracle".

    Checking Cluster manager integrity...


    Checking CSS daemon...
    Node Name Status

    TGDB02 running
    TGDB01 running
    Result: Daemon status check passed for "CSS daemon".

    Cluster manager integrity check passed.

    Checking cluster integrity...

    Node Name

    tgdb01
    tgdb02

    Cluster integrity check passed

    Checking daemon liveness...

    Check: Liveness for "CRS daemon"
    Node Name Running

    TGDB02 yes
    TGDB01 yes
    Result: Liveness check passed for "CRS daemon".

    Checking daemon liveness...

    Check: Liveness for "CSS daemon"
    Node Name Running

    TGDB02 yes
    TGDB01 yes
    Result: Liveness check passed for "CSS daemon".

    Checking daemon liveness...

    Check: Liveness for "EVM daemon"
    Node Name Running

    TGDB02 yes
    TGDB01 yes
    Result: Liveness check passed for "EVM daemon".

    Liveness of all the daemons
    Node Name CRS daemon CSS daemon EVM daemon

    TGDB02 yes yes yes
    TGDB01 yes yes yes

    Checking CRS health...

    Check: Health of CRS
    Node Name CRS OK?

    TGDB02 yes
    TGDB01 yes
    Result: CRS health check passed.

    CRS integrity check passed.

    Checking node application existence...

    Checking existence of VIP node application
    Node Name Required Status Comment

    TGDB02 yes does not exist failed
    TGDB01 yes does not exist failed
    Result: Check failed.

    Checking existence of ONS node application
    Node Name Required Status Comment
    ------------ ------------------------ ------------------------ ----------
    TGDB02 no does not exist ignored
    TGDB01 no does not exist ignored
    Result: Check ignored.

    Checking existence of GSD node application
    Node Name Required Status Comment

    TGDB02 no does not exist ignored
    TGDB01 no does not exist ignored
    Result: Check ignored.


    Post-check for cluster services setup was unsuccessful on all the nodes.

    PASSES:

    ./cluvfy stage -post crsinst -n tgdb01,tgdb02 -verbose

    Performing post-checks for cluster services setup

    Checking node reachability...

    Check: Node reachability from node "TGDB01"
    Destination Node Reachable?

    tgdb02 yes
    tgdb01 yes
    Result: Node reachability check passed from node "TGDB01".


    Checking user equivalence...

    Check: User equivalence for user "oracle"
    Node Name Comment

    tgdb02 passed
    tgdb01 passed
    Result: User equivalence check passed for user "oracle".

    Checking Cluster manager integrity...


    Checking CSS daemon...
    Node Name Status

    tgdb02 running
    tgdb01 running
    Result: Daemon status check passed for "CSS daemon".

    Cluster manager integrity check passed.

    Checking cluster integrity...

    Node Name

    tgdb01
    tgdb02

    Cluster integrity check passed


    Checking OCR integrity...

    Checking the absence of a non-clustered configuration...
    All nodes free of non-clustered, local-only configurations.

    Uniqueness check for OCR device passed.

    Checking the version of OCR...
    OCR of correct Version "2" exists.

    Checking data integrity of OCR...
    Data integrity check for OCR passed.

    OCR integrity check passed.

    Checking CRS integrity...

    Checking daemon liveness...

    Check: Liveness for "CRS daemon"
    Node Name Running
    ------------------------------------ ------------------------
    tgdb02 yes
    tgdb01 yes
    Result: Liveness check passed for "CRS daemon".

    Checking daemon liveness...

    Check: Liveness for "CSS daemon"
    Node Name Running

    tgdb02 yes
    tgdb01 yes
    Result: Liveness check passed for "CSS daemon".

    Checking daemon liveness...

    Check: Liveness for "EVM daemon"
    Node Name Running

    tgdb02 yes
    tgdb01 yes
    Result: Liveness check passed for "EVM daemon".

    Liveness of all the daemons
    Node Name CRS daemon CSS daemon EVM daemon

    tgdb02 yes yes yes
    tgdb01 yes yes yes

    Checking CRS health...

    Check: Health of CRS
    Node Name CRS OK?

    tgdb02 yes
    tgdb01 yes
    Result: CRS health check passed.

    CRS integrity check passed.

    Checking node application existence...


    Checking existence of VIP node application
    Node Name Required Status Comment

    tgdb02 yes exists passed
    tgdb01 yes exists passed
    Result: Check passed.

    Checking existence of ONS node application
    Node Name Required Status Comment

    tgdb02 no exists passed
    tgdb01 no exists passed
    Result: Check passed.

    Checking existence of GSD node application
    Node Name Required Status Comment

    tgdb02 no exists passed
    tgdb01 no exists passed
    Result: Check passed.

    Post-check for cluster services setup was successful.

    I am hoping someone can tell me why this is as the runInstaller wants to verify the nodes using uppercase names.

    Thanks in advance
    Ryan

  2. #2
    Join Date
    Sep 2002
    Location
    England
    Posts
    7,333
    does it matter? if it works it works, probably something to do with hosts files or how you set up the cluster software

  3. #3
    Join Date
    Aug 2006
    Posts
    3
    Unfortunately it does seem to matter as the runInstaller is trying to use uppercase when testing the config:

    Output generated from configuration assistant "Oracle Cluster Verification Utility" (attempt 2):
    Command = /usr/local/oracle/product/10.2.0/crs/bin/cluvfy stage -post crsinst -n TGDB01,TGDB02

  4. #4
    Join Date
    Aug 2006
    Posts
    3

    Quick Resolution

    Hi All,

    I resolved this issue by removing the cluser software and renaming everything to lowercase. Everything being the hostnames, the entries in the host files and the config in the cluster.conf file.

    Regards,
    Ryan

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width