2.2 FS-10050 to FS-10099

FS-10050 Cannot remove resource %s from group. Resource %s is dependent upon it: Cause: Resources are dependent upon the resource you are trying to remove. The resource cannot be removed from the group if other resources are dependent upon it.; Action: Remove all resources that are dependent upon the resource you are trying to remove.

FS-10051 Failed to read Oracle Net configuration file %s: Cause: Cannot open the listener.ora or tnsnames.ora file. There are syntax errors in the file.; Action: Resolve any syntax errors in the listener.ora or tnsnames.ora file.

FS-10052 Failed to open Oracle Net configuration file %s: Cause: Cannot open the listener.ora or tnsnames.ora file.; Action: Check that the Oracle Net configuration file exists on the system.

FS-10053 Failed to read Oracle Net configuration file %s on %s: Cause: Cannot update or verify the listener.ora or tnsnames.ora file. There are syntax errors in the file. If an application uses this file, it will not see the changes made by Oracle Services for MSCS.; Action: Resolve any syntax errors in the listener.ora or tnsnames.ora file.

FS-10054 Failed to open Oracle Net configuration file %s on %s: Cause: Failed to open the listener.ora or tnsnames.ora file for update or verification. There are problems opening the file. If an application uses this file, it will not see the changes made by Oracle Services for MSCS.; Action: Resolve any error in the listener.ora or tnsnames.ora file or in the directory.

FS-10055 The value of %s parameter is %s in %s on node %s: Cause: The Oracle Net default domains do not match across nodes.; Action: See the secondary message.

FS-10059 Unable to locate the needed information: Cause: Cannot find information needed regarding Oracle Net.; Action: Report the problem to your Oracle support representative.

FS-10060 An identical service name %s already exists: Cause: Duplicate Oracle Net service names on the same node are not allowed.; Action: Use another Oracle Net service name to access the database.

FS-10061 Unable to find the corresponding Oracle Net service name %s: Cause: Unable to find the Oracle Net service name in the tnsnames.ora file.; Action: Make sure that the tnsnames.ora file is correctly configured for the database. Make sure that no one has changed the Oracle Net service name in the tnsnames.ora file. If you are not sure what the original Oracle Net service name was, check the backup file created in the Oracle_Home\Network\Admin directory for Oracle Fail Safe. The tnsnames.ora backup files are named tnsnames.00n, where n is an integer.

FS-10062 Oracle Net listener is not unique for the database instance: Cause: The Oracle Net listener is servicing multiple Oracle instances.; Action: Report the problem (including a copy of the listener.ora file) to your Oracle support representative. Check the listener.ora file for this listener.

FS-10063 Group does not have an assigned network name: Cause: You did not assign a network name to the group.; Action: Assign a network name to the group; each group must have a unique network name.

FS-10064 Error generating the Oracle Net listener configuration plan: Cause: An error was encountered when trying to generate the Oracle Net configuration plan.; Action: Check the secondary error.

FS-10065 Error trying to configure the Oracle Net listener: Cause: An error occurred trying to reconfigure the Oracle Net listener using the configuration plan.; Action: Check the secondary error.

FS-10066 Failed to start Windows service %s for the Oracle Net listener

Cause: Unable to start the service for the Oracle Net listener. Oracle Services for MSCS attempts to start a listener after it has changed the definition of a listener or defined a new listener. This failed attempt can be caused by either of the following two conditions, with the first being the most common:

Another running Oracle Net listener is already listening for a database. The Oracle Net listener checks that no two listeners on the system listen for the same address or database SID. When this problem is encountered, the listener.ora and tnsnames.ora files that contain the definition of the updated listeners and service names are saved as rollback files. The file names of the rollback files are name_rlb.ora, where name is listener or tnsnames.
The virtual address used by the listener is not active on the node where Oracle Services for MSCS is trying to start the listener.

Action: If you believe that the first problem is the cause, read the rollback file to find the definition of the listener. Compare this definition to the definitions of all other running listeners on the system. There should be no overlapping of addresses or database SID names among the listeners. Check all listener.ora files on the system with multiple Oracle homes. If you believe that the second problem is the cause, make sure the virtual address used by the listener is active on the node where Oracle Services for MSCS is trying to start the listener.

FS-10067 Failed to stop Windows service %s for the Oracle Net listener: Cause: Unable to stop the specified service for the Oracle Net listener.; Action: Check the listener.ora file on the cluster.

FS-10068 Failed to delete Windows service %s for the Oracle Net listener: Cause: Unable to delete the specified Oracle Net listener service.; Action: Check the listener.ora file on the cluster.

FS-10069 The Windows service %s does not exist for the Oracle Net listener: Cause: The specified Windows service does not exist for the Oracle Net listener.; Action: Check the listener.ora file on the cluster.

FS-10070 Oracle Net: %s

Cause: Unable to read or update data in the Oracle Net files. The cause can be any of the following:

These files are no longer valid due to an improper update or corruption.
The service name, database SID, or network name of the group is incorrect.
The database SID is included in more than one listener (in a multiple Oracle homes environment).

Action: If these files are no longer valid due to improper update or file corruption, they cannot be used to configure virtual server information. Retrieve a valid version of these files, or re-create them using Oracle Net Assistant.

If these files are valid, check that the service name, database SID, and the network name of the group used in the operation are correct. Incorrect information may cause this step to fail.

If you are using a system with a multiple Oracle homes environment, make sure that the database SID is not included in more than one listener. Check all listener.ora files on the system.

FS-10071 Failed to get the Oracle Net default domain: Cause: Failed to retrieve the Oracle Net default domain from the sqlnet.ora file.; Action: Check that the sqlnet.ora file on the cluster contains a value for the NAMES.DEFAULT_DOMAIN parameter. If the value is missing, see the Oracle Net Services Administrator's Guide for information on how to modify this file.

FS-10072 Error trying to perform a checkpoint on database %s: Cause: Unable to perform a checkpoint operation on the database.; Action: Check the secondary error.

FS-10073 Failed to bring the cluster resource offline for group %s: Cause: Unable to bring the resources in the specified group offline.; Action: Check the secondary error.

FS-10074 Error configuring Oracle Net for the requested operation: Cause: An error was encountered trying to configure Oracle Net for the requested operation.; Action: Check the secondary error.

FS-10075 Error trying to configure the Oracle Net service name: Cause: An error occurred trying to reconfigure the Oracle Net service name using the configuration plan.; Action: Check the secondary error.

FS-10077 Oracle shared sockets are enabled for listeners in %s home on node %s. Please disable shared sockets: Cause: The USE_SHARED_SOCKET environment variable is set to TRUE. When shared sockets are enabled, Oracle Services for MSCS may not be able to restart a listener.; Action: Make sure that the USE_SHARED_SOCKET environment variable is set to FALSE on the specified node.

FS-10078 Error resetting resource restart policies for resources in group %s: Cause: Unable to reset the restart policy for resources in the specified group.; Action: Make sure that the restart policy for the resources in the specified group is correct. The default setting is for each resource to restart and affect the group.

FS-10080 Failed to verify the network name resource: Cause: Unable to verify the network name resource.; Action: Check the secondary error.

FS-10081 Oracle database instance %s exists on more than one node of the cluster: Cause: An Oracle database instance exists on multiple nodes of the cluster.; Action: The Oracle database instance for a standalone database should reside on only one node of the cluster. Issue the Verify Standalone Database command (from the Oracle Fail Safe Manager menu bar, choose Troubleshooting, then Verify Standalone Database) to clean up the cluster environment, and then try to add the database to the group again.

FS-10082 Oracle database instance %s already exists: Cause: The specified Oracle database instance already exists on the node.; Action: The specified Oracle database instance must be removed from the node, and then you can retry the operation.

FS-10084 The disk %s used by the standalone resource is not online on node %s: Cause: The standalone resource is on node %s, but the disk used by the resource is either offline or it is online on another node.; Action: If the disk is offline, use MSCS Cluster Administrator to place it online. If it is online on another node, use MSCS Cluster Administrator to move the group containing the specified disk to another node. If there are other resources in the group, consider creating a new group, moving the disk to the new group, and then moving the new group to the node where the standalone resource is.

FS-10085 The instance name %s specified for this operation is not the same as the instance name %s found in net service name %s: Cause: An incorrect SID name was probably specified.; Action: Make sure that the correct SID name is specified for the database.

FS-10086 See the cluster log for more information: Cause: The cluster is unable to bring a resource online.; Action: See the cluster log for detailed information about the cause.

FS-10087 Oracle Net configuration is not supported: Cause: The Oracle Net configuration on the system is not supported.; Action: See the secondary error for an explanation.

FS-10088 The listener serving the database instance listens on multiple hosts and different ports: Cause: The listener serving the database instance listens on multiple hosts and different port numbers. This type of configuration is not supported.; Action: Oracle Services for MSCS supports listeners that listen on multiple hosts with the same port numbers. Change the configuration of the listener accordingly, if possible.

FS-10089 The network name resource %s is not online: Cause: The network name resource is not in an online state.; Action: Check the secondary error.

FS-10090 Rolling back Oracle Net changes on node %s: Cause: Rolling back Oracle Net changes on the specified node.; Action: Check the secondary error.

FS-10091 Failed to put Oracle Net listener (%s) information into the persistent cluster registry for group %s: Cause: The operation encountered a problem when putting listener information into the persistent cluster registry (PCR).; Action: Report the problem to your Oracle support representative.

FS-10092 Failed to delete Oracle Net listener (%s) information from the persistent cluster registry for group %s: Cause: The operation encountered a problem when deleting listener information from the persistent cluster registry (PCR).; Action: Report the problem to your Oracle support representative.

FS-10093 Cluster node %s is required for the specified operation, but is currently not available: Cause: The specified cluster node is down or the cluster service is not running on the node.; Action: Bring the specified cluster node or cluster service online.

FS-10094 Failed to retrieve Oracle Net listener (%s) information from persistent cluster registry for group %s: Cause: The specified cluster node is down or the cluster service is not running there.; Action: Bring the specified cluster node or cluster service online.

FS-10095 You cannot move the group because the cluster has only one node: Cause: There must be at least two cluster nodes to move a group.; Action: Add another node to the cluster.

FS-10096 You must specify a destination node to move the group: Cause: The cluster has more than two nodes, so a destination node must be specified.; Action: Specify the destination node.

FS-10097 Nodes %s and %s have mismatched Oracle Net default domains in the Oracle home of the highest database version: Cause: The Oracle Net default domains do not match across nodes.; Action: See the secondary message.

FS-10098 Inconsistent Oracle Net default domains across the cluster nodes may lead to database access problems: Cause: The Oracle Net default domains do not match across nodes.; Action: Make the Oracle Net default domains consistent across the cluster nodes.

FS-10099 Database resource name %s cannot be used to access the database from a non-owner node. It must be qualified with a domain name: Cause: An Oracle Net default domain is necessary.; Action: Add the domain name to the database resource name.