MINI MINI MANI MO
/ Copyright (c) 2001, 2017, Oracle and/or its affiliates. All rights reserved.
/
/ NAME
/ kfodus.msg
/
/ DESCRIPTION
/ Error messages for Kernel Files Oracle Storage Manager Discovery tool(KFOD)
/
/ NOTES
/
/ MODIFIED
/ gmengel 05/10/16 - Add numeric sequence #s to placeholders for 102 & 300
/ gmengel 02/08/16 - Add KFOD-338 msg for kfod API.
/ samjo 01/29/16 - BUG 19404447: Client Cluster --> member cluster
/ emsu 01/21/16 - Add KFOD-106 and KFOD-342,343 for cell=true option
/ gmengel 04/28/15 - 20668853: Add msgs for mismatched args
/ gmengel 04/08/15 - 20834434: Repurpose KFOD-302 for kgfd error callback.
/ mchimang 01/23/15 - 20394895: Add new error messages
/ samjo 10/16/14 - Bug 19803231: Add mesg KFOD-334
/ somgupta 08/22/14 - 18369237: Add error messages for lscc
/ samjo 04/10/14 - 18301913: Add error messages for creddelclus
/ mchimang 04/06/14 - 18301913: Add error messages for credverify
/ skiyer 11/02/12 - 14731131:Add kfod-320 for op=version non-clustered mode
/ sahajaga 08/31/12 - #14115207: add KFOD-319.
/ gmengel 07/31/12 - 14266533: add KFOD-317 & KFOD-318 to report pq errors.
/ gmengel 03/21/11 - 11873495: add detail to KFOD-316.
/ gmengel 08/07/08 - add KFOD-316 for gpnp failure.
/ nchoudhu 07/21/08 - xbranchmerge sage from 11.1.0.7
/ sidatta 05/05/08 - Adding error message for Cell IO Error
/ gmengel 03/17/08 - Add KFOD-00314 message.
/ gmengel 03/13/08 - Fix kfod usage message.
/ gmengel 12/17/07 - Improve message 301.
/ gmengel 08/15/07 - Add message for no ASM instances available.
/ dfriedma 11/17/04 - Discovery errors
/ dfriedma 02/20/04 - osmlib -> asmlib
/ dfriedma 09/15/03 - Add error code for version mismtach
/ dfriedma 05/15/03 - Add messages for failed library load
/ pbagal 01/21/03 - pbagal_kfod
/ pbagal 01/20/03 - Creation
/
/
/
/ Initialization Errors: 100-199
0100, 0, "initialization of CORE/NLS failed"
0101, 1, "LRM error [%d] while parsing command line arguments"
0102, 1, "LRM error [%(1)d] while parsing argument %(2)s"
0103, 1, "LRM message: %s"
0104, 2, "Value for argument '%(1)s' exceeds limit of %(2)s."
0105, 1, "Could not open pfile '%s'"
0106, 0, "Option 'cell=true' is only supported on Oracle Exadata."
// *Cause: An attempt was made to run an operation with an option that is only
// supported on Oracle Exadata.
// *Action: Retry the operation without the 'cell=true' option.
//
/
/ Usage Errors: 200-299
/
/
/ Runtime Errors: 300-399
/
0300, 2, "OCI error [%(1)d] %(2)s"
0301, 2, "Unable to contact Cluster Synchronization Services (CSS). Return code %d from kgxgncin."
0302, 1, "Error encountered in device access layer: %s"
// *Cause: The device access layer failed with the included error message.
// *Action: See the returned error message for details.
//
0310, 1, "Cluster services error [%s]"
0311, 2, "Error scanning device %s"
0312, 2, "Error discovering diskstring %s"
0313, 3, "No ASM instances available. CSS group services were successfully initialized by kgxgncin."
0314, 3, "No local ASM instance available for OCI connection"
0315, 4, "Operating system error doing cell I/O, operation: [%(1)s], disk: [%(2)s], offset: [%(3)s], length [%(4)s]."
0316, 1, "Error acquiring ASM discovery string: %s"
// *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.
//
0317, 1, "error returned from Patch Query API: %s"
// *Cause: A call to the Patch Query API returned unsuccessfully.
// *Action: See the returned error message for details.
//
0318, 1, "unable to retrieve error message from Patch Query API: %s"
// *Cause: A call to the Patch Query API returned unsuccessfully.
// *Action: See the returned error message for details.
//
0319, 3, "No ASM instance available for OCI connection"
0320, 1, "Invalid operation or option for this cluster type"
// *Cause: This operation is invalid for this cluster type
// *Action: Retry the operation with cluster=true
//
0321, 1, "failed to read the credential file %s"
// *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.
/
0322, 1, "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.
/
0323, 1, "Member cluster version '%(1)s' in the credential file does not match software version '%(2)s'."
// *Cause: There was a version mismatch between the member cluster version in
// the credential file and the software version.
// *Action: Install a version of the member cluster that matches the version
// in the credential file.
/
0324, 1, "The member cluster version '%(1)s' is incompatible with the storage server version '%(2)s'."
// *Cause: The member cluster installation or upgrade was not supported by the
// storage server configured at the version listed in the message.
// *Action: Install or upgrade the member cluster to a version that is
// compatible with the storage server.
// Refer to the product documentation for information.
/
0325, 1, "failed to verify member cluster '%(1)s'\n%(2)s"
// *Cause: The member cluster installation verification failed.
// The possible causes are:
// - A member cluster with the same name was already configured.
// - A member cluster with the same name was deinstalled, but the
// member cluster's configuration was not removed at the Storage
// Server.
// *Action: Verify if there is already a member cluster with the name listed
// in the message by executing the 'asmcmd lscc' command on the
// storage server.
// If the member cluster is configured and in use, execute the
// 'asmcmd mkcc' command on the storage server, and provide an unused
// member cluster name to generate a new credential file. Retry the
// Grid Infrastructure installation using the new credential file.
// If the member cluster is configured and not in use, deinstall the
// existing member cluster. Execute the 'asmcmd rmcc' command on the
// storage server to delete the member cluster configuration. Retry
// the Grid Infrastructure installation.
// If the member cluster is not configured or if the error persists,
// contact Oracle Support Services.
/
0326, 1, "Member cluster(s) '%(1)s' will be incompatible if the storage server is upgraded to version '%(2)s'."
// *Cause: Storage server upgrade to the listed version failed because the
// listed member cluster will become incompatible.
// *Action: Upgrade the storage server to a version that is compatible with all
// of the configured member 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.
/
0327, 1, "failed to delete member cluster '%(1)s'\n%(2)s"
// *Cause: There was a failure in deleting the member cluster configuration.
// The accompanying error message provides the details.
// *Action: Examine the accompanying error message, address the reported issue
// and retry the operation.
/
0328, 1, "Member cluster installation or upgrade failed because the storage server is in the 'In Rolling Upgrade' or the 'In Rolling Patch' state."
// *Cause: The member cluster installation or upgrade was rejected because the
// storage server was in the 'In Rolling Upgrade' or the
// 'In Rolling Patch' state.
// *Action: Retry the installation or upgrade procedure after the Storage
// Server upgrade or patching has completed.
/
0329, 1, "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.
/
0330, 1, "invalid cluster name '%s' 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.
/
0331, 1, "forcibly deleted member cluster '%s'"
// *Cause: The configuration for the member cluster listed in the message was
// was forcibly deleted.
// *Action: The member cluster listed in the message will no longer be able
// to access the storage server. Follow the steps to enable access
// from the member cluster.
// - Delete all the Oracle Clusterware files in the
// '+<diskgroup_name>/<client_cluster_name>/' directory in all
// disk groups.
// - Deinstall the member cluster.
// - Install the member cluster.
/
0332, 0, "no member clusters configured"
0333, 1, "member cluster '%s' is not configured"
/
0334, 1, "failed to list the configured member clusters\n%s"
// *Cause: A failure occurred while attempting to display the member cluster
// configuration. The accompanying error message provides the details.
// *Action: Examine the accompanying error message, address the reported issue
// and retry the operation.
/
0335, 0, "command not supported"
// *Cause: An attempt was made to run an operation that is not supported by
// the configured cluster.
// *Action: Refer to the command line help for usage.
/
0336, 1, "failed to enable Oracle Flex ASM\n%s"
// *Cause: There was a failure in enabling the Oracle Flex ASM configuration.
// The accompanying error message provides the details.
// *Action: Examine the accompanying error message, address the reported issue
// and retry the operation.
/
0337, 1, "failed to create member cluster '%(1)s'\n%(2)s"
// *Cause: There was a failure in creating the member cluster configuration.
// The accompanying error message provides the details.
// *Action: Examine the accompanying error message, address the reported issue
// and retry the operation.
/
0338, 1, "failed to get OS user; failing function: '%s'\n"
// *Cause: There was an error retrieving the operating system user.
// The named function did not succeed.
// *Action: Contact Oracle Support Services
/
0340, 2, "incompatible input arguments '%(1)s' and '%(2)s'"
// *Cause: A command line argument was specified that was incompatible either
// with another argument or with the current cluster type.
// *Action: Refer to the command line help for usage.
/
0341, 0, "Oracle ASM File Security operation failed"
// *Cause: This is an internal error.
// *Action: Contact Oracle Support Services.
/
0342, 1, "Site GUID for disk '%s' is invalid."
// *Cause: This is an internal error.
// *Action: Examine the Globally Unique Identifier for the site using the
// command 'cellcli -e list cell attributes siteId'. Contact Oracle
// Support Services.
/
0343, 1, "Rack GUID for disk '%s' is invalid."
// *Cause: This is an internal error.
// *Action: Examine the Globally Unique Identifier for the rack using the
// command 'cellcli -e list cell attributes rackId'. Contact Oracle
// Support Services.
/
0344, 1, "unable to access credential file '%s'"
// *Cause: The specified credential file could not be read.
// *Action: Ensure that the specified credential file can be read.
/
/ Slos reporting: 400-449
/
400, 00000, "Operating system dependent operation: %(1)s failed with status: %(2)s"
// *Cause: Operating system call error.
// *Action: Contact Oracle Support Services.
/
401, 00000, "Operating system failure message: %s"
// *Cause: Operating system call error.
// *Action: Contact Oracle Support Services.
//
402, 00000, "failure occurred at: %s"
// *Cause: Operating system call error.
// *Action: Contact Oracle Support Services.
//
403, 00000, "additional information: %s"
// *Cause: Operating system call error.
// *Action: Contact Oracle Support Services.
/
/
/ INTERNAL Errors: 600-699
/
/
0600, 2, "OCI error [%(1)d] %(2)s"
0601, 1, "Could not allocate memory %d"
0602, 1, "Could not initialize sub heap %s"
0610, 2, "Internal error [%(1)s] [%(2)s] [%(3)s]"
/
/ Informational Messages: 1000-1099
/
1000, 0, "Usage: kfod op=<op> asm_diskstring=... | pfile=..."
/ Used by kfod op=credverify
1001, 0, "%(1)s: %(2)s"
1002, 0 , "Flex ASM is already configured"
OHA YOOOO