Cause: Operation was successful.

Cause: The command entered was invalid.

Cause: An attempt was made to reset the value of a parameter for which there is no default value.

Cause: An attempt was made to run or get help for a command from the command line which is available only in interactive mode.

Cause: The server aborted on the specified node.

Cause: It was not possible to create a name object for the configuration file.

Cause: The open of the configuration file failed.

Cause: A read of the configuration file failed.

Cause: It was not possible to close the configuration file.

Cause: The GNS server failed to start due to an error encountered by the server.

Cause: The line ended unexpectedly. For example, the line might have ended before the end of a quoted string was found.

Cause: Not enough arguments were specified for a parameter.

Cause: The number of arguments specified for a parameter was greater than maximum allowed.

Cause: The entry for a parameter in the configuration file does not contain the required number of fields.

Cause: The entry for a parameter in the configuration file contains more than the maximum number of fields.

Cause: The value specified for an integer parameter was not an integer.

Cause: The value specified for a boolean parameter was not a boolean value.

Cause: An unknown type was specified for the method used to store configuration information.

Cause: No name was specified for a configuration method which uses a file as the repository.

Cause: The initialization of GNS failed.

Cause: A value was not specified for the parameter.

Cause: The query type passed in is not supported by GNS.

Cause: Initialization of OCR to the specified level failed.

Cause: The IP address specified is neither in the v4 or v6 format.

Cause: The client program sent the wrong number of arguments over for a command.

Cause: The server received an unknown command from the client.

Cause: The value of a parameter sent over from the client to number failed.

Cause: An unexpected error occurred. The rest of the error stack contains details about the error.

Cause: The server process could not be spawned because the directory where the program resides could not be located or accessed.

Cause: The server program could not be accessed.

Cause: The client was unable to start the server process.

Cause: The GNS server was unable to create a backup configuration file.

Cause: GNS encountered an error when it tried to stop the advertisement of its service.

Cause: GNS was unable to register itself with Resource Discovery.

Cause: The client program was not able to locate a GNS server.

Cause: GNS was unable to initialize the transport that it uses to communicate between the client and server.

Cause: GNS was unable to initialize the transport that it was used to communicate between the client and server.

Cause: GNS was unable to send data either from the client to the server or from the server to the client.

Cause: An error occurred while the server was waiting for a connection from the client.

Cause: GNS was unable to receive data from its peer process.

Cause: The packet was ignored by the server because it was invalid. This may be caused by another process sending malformed packets.

Cause: The Grid Naming Service (GNS) server received a query which was not of the correct format. This could be due to an error by the server or because a malicious process is sending the GNS server invalid packets.

Cause: The buffer provided was too small to fit a piece of data.

Cause: The function called to initialize Bonjour for use by GNS failed.

Cause: The wait for data to be received from another process failed.

Cause: The GNS service could not be contacted because it is not running.

Cause: An attempt was made to start the GNS service, but it was already running.

Cause: An unknown option was specified either to a client program or the server.

Cause: The GNS client failed when it tried to initialize the Resource Discovery subsystem.

Cause: The server was unable to listen for requests on the specified endpoint.

Cause: The server was unable to listen on the specified port because it does not have privilege to do so. On Linux and Unix systems, this can occur because the server is not running as the root user.

Cause: Enough arguments were not specified for a command.

Cause: Too many arguments arguments specified for a command.

Cause: GNS was unable to send a query to the multicast DNS server because it is not running.

Cause: The specified alias already exists.

Cause: An alias for a name could not be found.

Cause: The specified name could not be found.

Cause: GNS was unable to find any interfaces on which it can listen for requests. This error is likely caused by the incorrect specification of the list of interfaces on which GNS is not to listen. Alternatively, it may be caused by an error in system configuration.

Cause: One or more GNS failed unexpectedly.

Cause: An attempt to acquire the privileges needed failed.

Cause: GNS was unable to initialize the layer the provides system-specific services.

Cause: The creation of the new version of the configuration file failed.

Cause: This is an information message to indicate that the trace level was set.

Cause: The facility used to control the GNS server dynamically failed.

Cause: The user which GNS is to run as in order to run operations which require special privileges does not exist.

Cause: The user which GNS is to run as in order to perform operations which do not require special privileges does not exist.

Cause: The group to which a user must belong in order to perform administrative operations does not exist.

Cause: It was not possible to retrieve the specified key from OCR because the user does not have the required privileges.

Cause: It was not possible to retrieve the specified value from OCR because the user does not have the required privileges.

Cause: A user tried to run a command but has no permission to do so.

Cause: An exception occurred on the server process.

Cause: The name to be used for a GNS operation was not valid. The name may have no domain or be qualified with the name of subdomain serviced by GNS.

Cause: A value was not configured for a mandatory parameter.

Cause: The query for network addresses for the given name failed.

Cause: The command requires at least one thread name to be specified.

Cause: The name of the thread was unknown to GNS.

Cause: The specified key cannot be found in the Oracle Cluster Registry.

Cause: A mapping for a address to a name already exists.

Cause: An error occurred while trying to open the root OCR used by GNS.

Cause: An attempt was made to create a GNS subdomain which already exists.

Cause: The specified GNS subdomain does not exist.

Cause: The specified address is not served by GNS.

Cause: The specified address is not known to GNS.

Cause: The name of the alias to be advertised was not valid. The name may have no domain or be qualified with the name of subdomain serviced by GNS.

Cause: The domain specified for the name does not specify the subdomain served by GNS.

Cause: The self-check performed by GNS failed.

Cause: The name specified for the subdomain to be served by GNS is longer than the maximum.

Cause: The name of the subdomain does not conform to Internet standards. It must meet the following requirments: 1. Only alphanumeric characters, periods are hyphens are allowed; 2. It must start and end with an alphanumeric character; 3. Consecutive periods are not allowed. In addition, the subdomain must not end with with ".local" as it is reserved for multicast DNS.

Cause: The trace level specified is lower than the minimum supported.

Cause: The trace level specified is greater than the maximum supported.

Cause: GNS was unable to process a command because it is either starting up or shutting down.

Cause: The call to set the trace level on the GNS server failed.

Cause: When GNS attempted to advertise a name and address upon re-start, it failed because the address can no longer be serviced. This can happen if the subnet used by GNS was changed between the time that GNS was stopped and it was started.

Cause: GNS was unable to contact Cluster Synchronization Services in order to retrieve the name of the cluster.

Cause: GNS was unable to get the name of the cluster from Cluster Synchronization Services.

Cause: GNS is not running as a privileged user e.g. root.

Cause: GNS was unable to create the specified OCR key.

Cause: An operation was attempted which is not currently supported by GNS.

Cause: When GNS starts, it re-creates the advertisements and aliases that existed when it was shut down. The attempt to re-create an advertisement or alias failed.

Cause: GNS was unable to spawn a thread. This may be due to low system resources.

Cause: A GNS thread failed when it tried to start.

Cause: The name of the alias to be advertised was not valid. The name must have no domain or be qualified with the name of subdomain serviced by GNS.

Cause: The domain specified for an alias does not match the domain serviced by GNS.

Cause: An operation on the Grid Naming Service (GNS) failed because GNS had not been configured.

Cause: GNS received a duplicate packet from a client. The connection was dropped as a consequence.

Cause: The packet was ignored by the server because it was invalid. This may be caused by another process sending malformed packets. This error is usually accompanied by another error which describes the exact error that occurred.

Cause: The check of the security attributes of a packet failed.

Cause: GNS received a packet whose type is unknown.

Cause: GNS failed to retrieve the address of the specified name.

Cause: A query was not forwarded from DNS to GNS for a name in the subdomain that it services.

Cause: This message is displayed when the GNS self-check fails.

Cause: This is an informational message which accompanies other messages describing a self-check failure.

Cause: An operation failed after the maximum number of retries.

Cause: An operation failed because it could not be performed at this time and should be tried again later`.

Cause: An argument was passed to a function which was incorrect. In the case of a string, for example, a string will be invalid if it is null or has a zero length.

Cause: The user attempted an operation for which he or she does not have sufficient privileges.

Cause: The address specified as the address on which GNS is to listen is not on the public network.

Cause: The value for a parameter is outside the range of permitted values.

Cause: No records could be found for the specified name in GNS.

Cause: A query was made for the names registered in GNS but none were found.

Cause: GNS was unable to open the specified OCR key.

Cause: GNS was unable to delete the specified OCR key.

Cause: Name resolution took longer than the expected time.

Cause: The self-check failed because it was not possible to resolve the self-check name into the address used for reference.

Cause: GNS was unable to resolve the name that it uses for the self-check the first time after it started.

Cause: GNS was unable run the self-check the first time after it started.

Cause: The self-check had previously succeeded after a failure but has failed again.

Cause: The creation of a listening endpoint failed.

Cause: The creation of a listening endpoint failed because the server did not have the needed permissions.

Cause: The creation of an endpoint failed because another process is using it.

Cause: Listening for requests from the DNS server(s) failed because another process is using the address.

Cause: It was not possible to retrieve the specified value from OCR.

Cause: Setting a set of OCR key values failed.

Cause: The service was required in an SRV record, bug not specified.

Cause: The service specified was not valid.

Cause: The target was required in an SRV record, but not specified.

Cause: The target in the SRV record specified was not a valid DNS name.

Cause: An SRV record for the specified service did not exist.

Cause: An SRV record for the specified service already existed.

Cause: The value specified for the port number of an SRV record was invalid.

Cause: The value specified for the priority of an SRV record was invalid.

Cause: The value specified for the weight of an SRV record was invalid.

Cause: The name of the SRV record was not specified.

Cause: The name specified for the SRV record was not a valid DNS name.

Cause: The protocol specified for the SRV record was not valid.

Cause: The protocol for the SRV record was not specified.

Cause: No PTR records could be found for the specified name.

Cause: An attempt was made to add a PTR record which already exists.

Cause: An attempt was made to add a TXT record which already exists.

Cause: No TXT records could be found for the specified name.

Cause: The TXT record was longer than the maximum.

Cause: The TXT record specified does not conform with the standard (RFC 1035).

Cause: The PTR record specified does not conform with the standard (RFC 1035).

Cause: An attempt was made to add a record which already exists.

Cause: An attempt was made to query a record which does not exist.

Cause: The length of a name specified exceeds the allowed limit.

Cause: The length of a name plus the GNS subdomain specified exceeded the allowed limit.

Cause: A name was not specified for a Pointer Resource (PTR) record.

Cause: A name was not specified as the target of the Pointer Resource (PTR) record.

Cause: A name was not specified for a text (TXT) record.

Cause: A value was not specified for a text (TXT) record.

Cause: A name was not specified for a refresh operation.

Cause: GNS rebind failed.

Cause: A key supplied for an operation is invalid.

Cause: Opening the specified credentials file failed.

Cause: The credentials file specifed could not be found.

Cause: The steps required to initialize the import of credentials failed.

Cause: The credentials file specified already exists.

Cause: The credentials file specified could not be created.

Cause: The steps required to initialize the export of credentials failed.

Cause: GNS was unable to verify the contents of a credentials file.

Cause: An error occurred while importing credentials used to contact the GNS server.

Cause: An error occurred while exporting credentials used to contact the GNS server.

Cause: The length of the specified service instance exceeded the maximum allowed.

Cause: The service instance contained characters which are not allowed under the draft standard for DNS-based service discovery (see http://files.dns-sd.org/draft-cheshire-dnsext-dns-sd.txt)

Cause: More than two discovery addresses were found in the cluster configuration.

Cause: The Grid Naming Service (GNS) configuration was found to have two IPv4 or two IPv6 discovery addresses.

Cause: No addresses were found in the Grid Plug and Play (GPnP) profile which could be used to locate an instance of the Grid Naming Service (GNS).

Cause: An attempt to initialize Grid Plug and Play (GPnP) while modifying the Grid Naming Service (GNS) configuration failed.

Cause: An attempt to access the Grid Plug and Play (GPnP) profile or a value within the profile failed while modifying Grid Naming Service (GNS) configuration.

Cause: An attempt to modify Grid Naming Service (GNS) discovery address failed.

Cause: This error is used internally by GNS to indicate that a thread has been stopped.

Cause: The attempt to validate the provided Grid Naming Service (GNS) credentials failed.

Cause: Initialization of the subsystem used for credentials validation failed.

Cause: Grid Naming Service (GNS) was unable to initialize Cluster Ready Services (CRS) for its use.

Cause: A Cluster Ready Services (CRS) operation failed.

Cause: The version of an object or operation was not supported by Grid Naming Service (GNS).

Cause: The Oracle Cluster Registry (OCR) was not available yet for use by Grid Naming Service (GNS).

Cause: An error occurred while importing GNS key.

Cause: An operation which attempted to access the Oracle Cluster Registry failed because the Cluster Ready Services (CRS) was not running.

Cause: An attempt to import client data failed because client data has already been imported.

Cause: The record type specified was unsupported.

Cause: Credential import failed because the import file was empty or corrupt.

Cause: An error occurred while removing the GNS credentials from client cluster.

Cause: GNS was unable to set the ownership for OCR key.

Cause: The attempted operation failed because the file referenced by the indicated pathname was of the wrong type.

Cause: The length of a component of a name exceeded the maximum allowed.

Cause: A group of threads belonging to the Grid Naming Service (GNS) process failed to stop. This can happen if one or more threads in the group becomes unresponsive because of a system problem.

Cause: A thread belonging to the Grid Naming Service (GNS) process failed to stop. This can happen if the thread becomes unresponsive because of a system problem.

Cause: An invalid string was specified for the target of a PTR record. The target must be a valid DNS name.

Cause: The Grid Naming Service (GNS) was unable to find a port to listen on.

Cause: The instance role specified was not a valid role.

Cause: The Grid Naming Service (GNS) did not get any value for for the indicated CRS attribute.

Cause: The Grid Naming Service (GNS) was unable to contact the Domain Name System (DNS) to get the name server (NS) record for the subdomain that it serves.

Cause: No name server (NS) record for the Grid Naming Service instance was found in the Domain Name System (DNS).

Cause: The name of this instance of the Grid Naming Service either contained characters which are not valid in a DNS label or was longer than the maximum length of a DNS label.

Cause: Start of primary GNS instance failed because it was already running. There must be only one primary GNS instance running in a multi-cluster environment.

Cause: A zone transfer failed because the fetch of a record from a transfer message failed.

Cause: Zone data received was not in the expected format.

Cause: An attempt to save the zone data on a peer instance failed.

Cause: A zone operation failed because an invalid domain name was found in a transfer message.

Cause: The verification of the signature attached to a record failed.

Cause: A record with the same type with a different time to live was detected. This is a violation of RFC 4034 issued by the Internet Engineering Task Force (www.ietf.org).

Cause: An error occurred while validating a record.

Cause: An operation failed because it could not get CRS active version.

Cause: Initialization of OLR to the specified level failed.

Cause: An advertise operation failed because an error occurred when setting zone data.

Cause: An attempt was made to modify the GNS instance role, but it was running with the specified role.

Cause: An attempt to modify the GNS instance role to primary failed because no existing primary instance was found and the '-force' option was not supplied.

Cause: An attempt to modify the GNS instance role to primary failed because a primary instance was found and the '-force' option was supplied.

Cause: An attempt to modify the GNS instance role failed because propagation to the primary instance was unsuccessful.

Cause: An operation to modify the GNS instance role failed.

Cause: An operation failed because it could not get CRS software version.

Cause: Removing GNS failed because one or more leaf nodes were still running in the cluster.

Cause: A GNS operation failed because it could not get node information from CSS.

Cause: The specified name expired.

Cause: The specified record expired.

Cause: An error occurred while upgrading Grid Naming Service (GNS) records.

Cause: An attempt to change the role of a Grid Naming Service (GNS) client cluster was rejected because the role can only be modified on a (GNS) server cluster.

Cause: An attempt to process the Cluster Manifest File failed because the indicated section for the Grid Naming Service (GNS) was not found.

Cause: An attempt was made to register the specified cluster with the Grid Naming Service (GNS) but an entry for the cluster already existed. A cluster can only be registered once.

Cause: An attempt was made to perform an operation from the specified cluster with the Grid Naming Service (GNS) but the cluster was not registered with GNS.

Cause: An attempt was made to delete the primary instance of the Grid Naming Service (GNS) but clusters were still registered with it.

Cause: An operation failed because it was attempted on an instance of the Grid Naming Service (GNS) which is not primary.

Cause: An attempt by the Grid Naming Service (GNS) server to perform an operation encountered an unexpected authorization error.

Cause: The cluster GUID was invalid. A GUID may only contain ASCII characters.

Cause: The registration of a cluster with the Grid Naming Service (GNS) failed. The accompanying messages provide detailed failure information.

Cause: The Grid Naming Service (GNS) server attempted to rename a cluster but the operation failed.

Cause: The cluster GUID was invalid. Its length must match the specified value.

Cause: An attempt to create a member cluster failed because an error occurred in generating a member cluster certificate as part of creating the manifest file.

Cause: An attempt to create an instance of the Grid Naming Service was not fully successful. The wallet that holds security information about the instance could not be created.

Cause: An attempt to execute a command on the Grid Naming Service failed because the wallet needed to verify the identity of the cluster where the command is being invoked could not be retrieved.

Cause: A command attempted on the Grid Naming Service (GNS) server failed because it was not possible to verify the identity of the cluster from the command was being sent.