Cluvfy User Equivalence Check Fails Or Returns "Unsuccessful" Without Details

(Doc ID 734095.1)

Last updated on OCTOBER 11, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 10.1.0.2 to 11.1.0.7 [Release 10.1 to 11.1]
Information in this document applies to any platform.

Symptoms

Cluvfy user equivalence check fails when banner is enabled.

  1. When the cluvfy is run we may see the following error:
    $ cluvfy comp admprv -n node4,node5 -o user_equiv -sshonly -verbose

    Verifying administrative privileges

    Checking user equivalence...

    Check: User equivalence for user "oracle"
    Node Name Comment
    ------------------------------------ ------------------------
    node5 passed
    node4 failed
    Result: User equivalence check failed for user "oracle".

    Verification of administrative privileges was unsuccessful.
    Checks did not pass for the following node(s):
    node4

    The above command may return
         Result: User equivalence check passed for user "oracle".
    although a banner is enabled on the machines.
  2. Cluvfy returns unsuccessful

    $ cluvfy comp nodecon -n node4,node5 -verbose

    Verifying node connectivity

    Verification of node connectivity was unsuccessful on all the nodes.


    When enabling logging you might see output similar to this one:

    [main] [14:45:6:756] [CommandBuffer.checkCommandStatus:83] CommandBuffer:checkCommandStatus returning false, command number= 8 thread name= Thread[main,5,main]; Mon Sep 08 14:45:06 CDT 2008
    [main] [14:45:6:756] [ClusterConfig.submit:516] status=false; Mon Sep 08 14:45:06 CDT 2008
    [main] [14:45:6:763] [ClusterException.setErrorMessage:131] ClusterException.setErrorMessage: commands[0]=oracle.ops.verification.framework.command.GetExectaskVerCommand@d7725c4; Mon Sep 08 14:45:06 CDT 2008
    [main] [14:45:6:763] [ClusterException.setErrorMessage:131] ClusterException.setErrorMessage: commands[1]=oracle.ops.verification.framework.command.GetExectaskVerCommand@9506dc4; Mon Sep 08 14:45:06 CDT 2008
    [main] [14:45:6:763] [ClusterConfig.destroy:394] destroying resources for client thread Thread[main,5,main]; Mon Sep 08 14:45:06 CDT 2008
    [main] [14:45:6:763] [GlobalHandler.submit:165] GlobalHandler::EXCEPTION: ClusterException[Thread:main]: ; Mon Sep 08 14:45:06 CDT 2008
    [main] [14:45:6:764] [GlobalExecution.dumpTraceInfo:506] ---- Execution Trace for getExectaskVer from node: es0a226q -----; Mon Sep 08 14:45:06 CDT 2008
    [main] [14:45:6:764] [GlobalExecution.dumpTraceInfo:514] ::Inside execute() ; Mon Sep 08 14:45:06 CDT 2008
    [main] [14:45:6:764] [GlobalExecution.dumpTraceInfo:514] super.execute() failed for GetExectaskVerCommand...; Mon Sep 08 14:45:06 CDT 2008
    [main] [14:45:6:764] [GlobalExecution.dumpTraceInfo:506] ---- Execution Trace for getExectaskVer from node: es0a227q -----; Mon Sep 08 14:45:06 CDT 2008
    [main] [14:45:6:764] [GlobalExecution.dumpTraceInfo:514] ::Inside execute() ; Mon Sep 08 14:45:06 CDT 2008
    [main] [14:45:6:764] [GlobalExecution.dumpTraceInfo:514] super.execute() failed for GetExectaskVerCommand...; Mon Sep 08 14:45:06 CDT 2008rt code here]


Verifying ssh connectivity and note the additional output that is displayed:
$ ssh node5 date
No RSA host key is found in BoKS database for host node5.
You are authorized to use this System for approved business purposes only.
Use for any other purpose is prohibited. All transactional records, reports,
e-mail, software, and other data generated by or residing upon this System
are the property of the Company and may be used by the Company for any purpose.
Authorized and unauthorized activities may be monitored.

Wed Jul 30 14:53:21 SST 2008


Eventually the output 'the date' can be seen which would indicate initially that the command is running successfully.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms