Skip Headers
Oracle® Database Error Messages
12c Release 1 (12.1)

E49325-05
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

49 KFOD-00316 to KFOD-00403

KFOD-00316: Error acquiring ASM discovery string: string
Cause: Call to the Grid Plug and Play service to request disk discovery string failed.
Action: Ensure that the Grid Plug and Play component of Cluster Ready Services is available. If Grid Plug and Play is operational and command still fails, contact Oracle Support Services.
KFOD-00317: error returned from Patch Query API: string
Cause: A call to the Patch Query API returned unsuccessfully.
Action: See the returned error message for details.
KFOD-00318: unable to retrieve error message from Patch Query API: string
Cause: A call to the Patch Query API returned unsuccessfully.
Action: See the returned error message for details.
KFOD-00320: Invalid operation or option for this cluster type
Cause: This operation is invalid for this cluster type
Action: Retry the operation with cluster=true
KFOD-00321: failed to read the credential file string
Cause: The credential file was not valid.
Action: Verify that the credential file is valid and accessible. Ensure that the user has read access permission on the credential file. Rerun the command.
KFOD-00322: credential file not specified
Cause: The previous 'kfod' command was rejected because it did not include a valid credential file name.
Action: Reexecute the 'kfod' command providing a valid credential file name. Refer to the command line help for information.
KFOD-00323: Client Cluster version 'string' in the credential file does not match software version 'string'
Cause: There was a version mismatch between the Client Cluster version in the credential file and the software version.
Action: Install a version of the Client Cluster that matches the version in the credential file.
KFOD-00324: The Client Cluster version 'string' is incompatible with the Storage Server version 'string'.
Cause: The Client Cluster installation or upgrade was not supported by the Storage Server configured at the version listed in the message.
Action: Install or upgrade the Client Cluster to a version that is compatible with the Storage Server. Refer to the product documentation for information.
KFOD-00325: failed to verify Client Cluster 'string' string
Cause: The Client Cluster installation verification failed. The possible causes are:

- A Client Cluster with the same name was already configured.

- A Client Cluster with the same name was deinstalled, but the Client Cluster's configuration was not removed at the Storage Server.

Action: Verify if there is already a Client Cluster with the name listed in the message by executing the 'asmcmd lscc' command on the Storage Server. If the Client Cluster is configured and in use, execute the 'asmcmd mkcc' command on the Storage Server, and provide an unused Client Cluster name to generate a new credential file. Retry the Grid Infrastructure installation using the new credential file. If the Client Cluster is configured and not in use, deinstall the existing Client Cluster. Execute the 'asmcmd rmcc' command on the Storage Server to delete the Client Cluster configuration. Retry the Grid Infrastructure installation. If the Client Cluster is not configured or if the error persists, contact Oracle Support Services.
KFOD-00326: Client Cluster(s) 'string' will be incompatible if the Storage Server is upgraded to version 'string'.
Cause: Storage Server upgrade to the listed version failed because the listed Client Cluster will become incompatible.
Action: Upgrade the Storage Server to a version that is compatible with all of the configured Client Clusters. If the Storage Server could not be upgraded to a compatible version, forcibly upgrade the Storage Server using the procedure documented in the product documentation.
KFOD-00327: failed to delete Client Cluster 'string' string
Cause: There was a failure in deleting the Client Cluster configuration.
Action: See the returned error message for details.
KFOD-00328: Client Cluster installation or upgrade failed because the Storage Server is in 'rolling migration' or 'rolling patch' state
Cause: The Client Cluster installation or upgrade was rejected because the Storage Server was in 'rolling migration' or 'rolling patch' state.
Action: Retry the installation or upgrade procedure after the Storage Server upgrade or patching has completed.
KFOD-00329: no cluster name specified
Cause: The previous 'kfod' command was rejected because it did not include a cluster name.
Action: Reexecute the 'kfod' command providing a valid cluster name. Refer to the command line help for information.
KFOD-00330: invalid cluster name 'string' specified
Cause: An invalid cluster name was supplied to the 'kfod' utility.
Action: Specify a cluster name which is at least one character but no more than 15 characters in length. The cluster name must be alphanumeric, it cannot begin with a numeric character, and it may contain hyphen (-) characters. However, it cannot end with a hyphen (-) character.
KFOD-00331: forcibly deleted Client Cluster 'string'
Cause: The configuration for the Client Cluster listed in the message was was forcibly deleted.
Action: The Client Cluster listed in the message will no longer be able to access the Storage Server. Follow the steps to enable access from the Client Cluster.

- Delete all the Oracle Clusterware files in the '+<diskgroup_name>/<client_cluster_name>/' directory in all disk groups.

- Deinstall the Client Cluster.

- Install the Client Cluster.

KFOD-00400: OS system dependent operation: string failed with status: string
Cause: OS system call error
Action: contact Oracle Support
KFOD-00401: OS failure message: string
Cause: OS system call error
Action: contact Oracle Support
KFOD-00402: failure occurred at: string
Cause: OS system call error
Action: contact Oracle Support
KFOD-00403: additional information: string
Cause: OS system call error
Action: contact Oracle Support