Action: If you are upgrading an older release of Clusterware this is not an error. Action: Bring the GNS resource online using 'srvctl start gns' command.
Action: Make sure that the nodes of the cluster are accessible from the current node. Make sure that the user executing the check has permission to execute commands on nodes using 'ssh'. Contact Oracle support services. If it is not the expected state then use the command 'crsctl start res ora. Action: Make sure that the nodes listed are accessible from the current node. Make sure that the user executing the check has permission to executed commands on the node s listed using 'ssh'.
Action: Ensure that correct installation of CRS exists. Action: Verify command specified can be exectued on node listed. Action: Review the error reported and resolve the issue specified. See Oracle Local Repository documentation for further information.
Cause: Cannot access the file specified. Action: Verify that the specified file exists and can be access on the node identified. Action: Verify installation of CRS on the identified node. If the warning is due to partial upgrade of Oracle Clusterware stack then continue with upgrade and finish it. Action: Ensure that the install of Oracle Restart has completed successfully and the Oracle Restart home is set up correctly.
Cause: An error was encountered when trying to verify the status of Oracle Cluster Synchronization Services. Action: Verify the state of the Oracle Cluster Synchronization Services using 'crsctl check cluster'. Action: Make sure that the user executing the CVU check has read permission for the file and the file exists in the specified path.
Action: Ensure that the install of Oracle Restart has completed successfully. Action: Correlate with the other failure messages displayed and fix those failures.
Action: Configure NTP on the node if not done so yet. Refer to your NTP vendor documentation for details. The failure is due to a reason like incorrect permissions on the configuration file, communications error with the node, missing or inaccessible remote execution binary on the node, etc.
Action: Review the error messages that follow this message and fix the problem s indicated. Action: If you want to use NTP for time synchronization, create this file and setup its configuration as described in your vendor's NTP document.
Action: Look at the related error messages and fix them. If there are none, reconfigure all of the nodes in the cluster to synchronize with at least one common NTP Time Server.
Action: Make sure that the NTP query command 'ntpq' is available on all nodes and the user running the CVU check has execute privilege for it. Action: Make sure that the Time Server is functioning properly, and if yes, adjust the system clock so that the offset is within limits. Cannot proceed further for the NTP tests Cause: Attempt to check existence of config file failed on all nodes.
Action: Look at the individual error messages displayed for the respective nodes and the overall result message and take appropriate action. Action: Look at the accompanying error messages for the nodes on which the check failed and fix the problem.
Action: Make sure that the NTP query command 'ntpq' is available on all nodes and make sure that user running the CVU check has permissions to execute it. Action: Look at the individual messages displayed and fix the problems indicated. PRVF Voting disk configuration does not meet Oracle's recommendation of three voting disk locations Cause: For high availability, Oracle recommends that you have a minimum of three voting disk locations.
Action: Add additional voting disk locations to meet the Oracle recommended amount of three voting disks. Action: Review Clusterware and Voting Disk configuration. PRVF The current voting disk state is at high risk Cause: The current state of the voting disk locations is susceptible to the loss of one voting disk location resulting in failure of the cluster. Action: Add additional voting disk locations, or bring existing locations online, to reduce the risk of losing one voting disk location.
PRVF Voting disk configuration does not meet Oracle's recommendation Cause: For high availability, Oracle recommends that you have more than two voting disk locations. Action: Add additional voting disk locations. Action: Shut down and restart the NTP daemon with the slewing option set.
In each case add -x to the ntpd command line options. Action: Make sure that the NTP daemon is running on the node. Also look at other messages accompanying this message. Action: Make sure that the NTP daemon is running on all the nodes. Make sure that slewing option is set on all the nodes of the cluster. Action: Ensure that Clusterware is up and running and verify Voting Disk configuration. Action: Verify Voting Disk configuration and ensure all Voting Disk locations are shared across all cluster nodes and are of the same storage type.
Action: Verify the owner, group and permissions settings on the location indicated. Action: Make sure that the space constraint data is well formed and consistent in the constratint xml.
Action: Verify that the space constraint data is correctly specified in the constraint xml. Verify that the space constraint check reference data is correctly specified in the constraint xml.
Action: Make sure that correct data is specified, using the values indicated in the message. Action: Make sure that the correct qualifier is specified. PRVF Invalid constraint. Compatibility check cannot proceed Cause: The specified constraint is invalid.
Action: Specify the correct constraint for the compatibility check. Action: Make sure that the slewing option is specified in the file listed. For a list of nodes on which this check failed look at the accompanying error messages. Action: The NTP daemon's boot time configuration file is listed with the messages accompanying this message.
Make sure that slewing option is set in configuration file. Action: Make sure that the NTP daemon is configured on the node and will be started when the node boots up. Make sure that the user running this check has access to the configuration file specified. Cause: Time Zone value is missing in specified configuration file.
Action: Enter appropriate Time Zone value in the specified configuration file on the indicated node. PRVF Time zone is not the same on all cluster nodes. Cause: Nodes have different time zone settings. Action: Ensure that time zone is same on all nodes.
Cause: NTP Daemon may have aborted , shut down or may not have been installed. The failure is due to a reason like incorrect setup, communications error with the node, missing or inaccessible remote execution binary on the node, etc. Action: Examine the status of ntp on each of the nodes indicated after this message and restart the daemon or install the NTP software if necessary.
Action: Review the error that follow this message and fix the problem s in the indicated nodes. Cause: A check for the indicated timezone file did not find it on the node shown. Action: Restore the file on the indicated node by reinstalling timezone patches for your operating system. Action: The accompanying messages will list the NTP daemon or service names along with the nodes on which they are running.
Make sure that only one time synchronization service is active on all nodes of the cluster at any given time by shutting down others. Action: NTP configuration must be uninstalled on all nodes of the cluster. Restart your system to make your changes effective after enabling the Automount feature. Action: Ensure that the specified subkey exists in registry and access permissions for the Oracle user allow access to the Windows Registry. Restart your system to make your changes effective after changing the registry.
Action: Ensure that the specified subkey exists in registry and the access permissions for the Oracle user allow access to the Windows Registry. Cause: An error occurred while attempting to retrieve the information about Automount feature. Action: Look at the accompanying messages and respond accordingly.
Action: Correct the errors indicated. On UNIX the general format of file resolv. For more details refer to resolv. Action: Look at the file specified on all nodes. Make sure that either 'domain' entry is defined on all nodes or is not defined on any nodes.
Action: Make sure that all nodes of the cluster have same 'domain' entry in the file specified. Action: Make sure that the file is either present on all nodes or is not present on any node. Action: Reduce the number of 'nameserver' entries on the nodes specified to the allowed number.
Action: Make sure that there is only one 'option attempts:' entry in the file specified. Action: Make sure that the file specified has only one 'domain' entry. Action: Make sure that there is only one 'search' entry in the file specified. Multiple domains can be listed in the same search entry. Make sure that either 'nameserver' entry is defined on all nodes or is not defined any nodes.
Action: Make sure that all nodes of the cluster have same 'nameserver' entry in the file specified. Make sure that either 'search' entry is defined on all nodes or is not defined any nodes. Action: Make sure that all nodes of the cluster have same 'search' entry in the file specified. Also look for messages accompanying this message for details.
Action: Make sure that 'options timeout', 'options attempts' and 'nameserver' entries in file resolv. On HPUX these entries will be 'retrans', 'retry' and 'nameserver'.
On Solaris these will be 'options retrans', 'options retry' and 'nameserver'. Make sure that the DNS server responds back to name lookup request within the specified time when looking up an unknown host name. Action: Make sure that 'nslookup' command exists on the nodes listed and the user executing the CVU check has execute privileges for it.
Action: Make sure that only one of these entries exist in file resolv. It is preferable to use entry 'search' in resolv. If the DHCP servers are listening to a different port then specify it by using -port option. Make sure that the DHCP server listening on port specified in above messages has sufficient number of IP addresses to give out. Action: Look at messages accompanying this message for more information. Action: This check is network load sensitive and can yield different result at different times.
Make sure that the DHCP server and the network is not overloaded. Action: If there are IP addresses that are not needed stop them in the operating system specific way. If too many resources are running on this node then relocate them to other nodes of the cluster relocate using 'srvctl relocate' command. PRVF Unable to obtain network interface details on local node Cause: An attempt to obtain network interface details on local node failed.
Action: Make sure that the user executing CVU has sufficient permissions to query network interfaces on the node. Also look at accompanying messages and take action as per those messages. Action: Refer to the specified output and fix the error.
Action: Examine the messages displayed for each node and take action as per those messages. Check messages of the 'cluvfy comp dns -server' instance to make sure that there are no errors.
If the address has been started then make sure that there are no firewalls between the local node and node on which this IP address has been started. Action: Look at messages on the 'cluvfy comp dns -server' instance to make sure that the test DNS server was stared. Also look at any messages accompanying this message. Also look at any messages from 'cluvfy comp dns -server' invocation for CVU.
Action: Make sure that the specified IP address is a valid IP address and is assigned to an interface on the node on which 'cluvfy comp dns -server' was run. Make sure that there are no firewalls between local node and node on which specified IP address is assigned. Action: Make sure that the specified address and port is correct. Make sure that there are no firewalls between the node on which 'cluvfy comp dns -server' was run and the node on which this command was run.
Also look at any error messages on the node on which 'cluvfy comp dns -server' was run. Action: Make sure that there are no firewalls between the local node and the DNS. Make sure that there are no firewalls between DNS and the node on which 'cluvfy comp dns -server' was run. Action: A valid domain name starts with an alphabetic character and consists only of characters [A-Z], [a-z], [], '.
Refer to the RFC standard for more information. Action: On Linux and AIX make sure that 'options timeout', 'options attempts' and 'nameserver' entries in file resolv. Action: Ensure that the interface is installed and online on the nodes in the cluster. Action: Ensure that the interface is installed and online on the nodes specified. Action: Verify state of network interface adapters on the specified node.
PRVF Could not find a fully connected subnet that covers all the nodes Cause: Could not find a network interface adapter that exists in the same subnet on every node in the cluster.
Action: Ensure that the network interface adapters are installed and configured correctly on each node in the cluster. Action: Ensure that the nodes specified are accessible with the OS ping utility. Action: Verify network interface s operational status on the node identified. Action: Define a gateway for the specified subnet. PRVF Core file name pattern is not same on all the nodes. Cause: The core file name pattern is not same on all the nodes.
RSA key fingerprint is bdaa:9d:da:ab:0c:ba:fd:db2:fe Run this sshUserSetup. Do you want to learn Linux System Administration for Beginners, then read the following articles.
Previous ORA maximum number of sessions exceeded. Next ORA error in identifying control file, check alert log for more info. Leave a Reply Cancel reply.
By Carlos Pimentel. Share this: Twitter Facebook. Like this: Like Loading Leave a Reply Cancel reply Enter your comment here Fill in your details below or click an icon to log in:. Email required Address never made public. Name required. Follow Following.
0コメント