KFNDG-00200 to KFNDG-00701

41 KFNDG-00200 to KFNDG-00701

KFNDG-00200: invalid syntax: Cause: Invalid syntax for renamedg was specified.; Action: Try renamedg -help for more information.
KFNDG-00201: invalid arguments: Cause: Invalid key or value was specified for renamedg.; Action: Try renamedg -help for more information.
KFNDG-00202: invalid value (<varname>string</varname>) for parameter phase: Cause: Incorrect value for parameter PHASE was specified.; Action: Valid values for parameter PHASE are ONE, TWO, BOTH. Retry with correct values.
KFNDG-00203: disk group name (<varname>string</varname>) exceeds maximum allowed length <varname>number</varname>: Cause: Invalid disk group name was specified.; Action: Disk group name can be a maximum of 32 characters.
KFNDG-00204: disk group name <varname>string</varname> has invalid characters: Cause: Invalid disk group name was specified.; Action: Disk group name can only contain alphabetic, numeric and the underscore (_) characters.
KFNDG-00205: failed to interpret configuration file name: Cause: Invalid configuration file name was specified.; Action: Verify configuration file name and folder permissions and retry renamedg.
KFNDG-00301: new disk group (<varname>string</varname>) already exists, ignorning renamedg: Cause: disk group specified in NEWDGNAME already exists.; Action: None
KFNDG-00302: disk (<varname>string</varname>:<varname>string</varname>) does not contain a valid header: Cause: Device header could not be located or corrupt.; Action: Verify if the device mentioned is an ASM disk device.
KFNDG-00303: failed to update disk group name for <varname>string</varname>: Cause: Insufficient privileges or write error in disk.; Action: Verify disk permissions and retry renamedg. Also, see log for additional information.
KFNDG-00304: unable to access heartbeat block of the device <varname>string</varname>:<varname>string</varname>: Cause: Heartbeat block of the disk was corrupt.; Action: Verify disk header with ASM utilities, retry renamedg.
KFNDG-00305: failed to create configuration file: Cause: Insufficient privileges or invalid path.; Action: Verify folder permissions and retry the command.
KFNDG-00306: unable to write to configuration file: Cause: Insufficient privileges.; Action: Check file permissions and retry renamedg.
KFNDG-00307: unable to read configuration file: Cause: Insufficient privileges or disk read error.; Action: Check file permissions and retry renamedg.
KFNDG-00308: failed to process configuration file entry: <varname>string</varname>: Cause: Configuration file was corrupt.; Action: Check file information and retry renamedg.
KFNDG-00401: allocation unit size conflict (<varname>number</varname>, <varname>number</varname>): Cause: Allocation unit size of disk group and the disk did not match.; Action: Verify that the device is not corrupt and retry renamedg.
KFNDG-00402: ASM metadata block size conflict (<varname>number</varname>, <varname>number</varname>): Cause: Metadata block size of the disk group and disk did not match.; Action: Verify if the device is not corrupt and retry renamedg.
KFNDG-00403: not all disks of disk group <varname>string</varname> were discovered: Cause: Offine disks were present in the specified disk group.; Action: Refer to Oracle Database Storage Administator's Guide for more details.
KFNDG-00404: disk group <varname>string</varname> contains offline disks, ignoring renamedg: Cause: Disk group with offline disks could not be renamed.; Action: Refer to Oracle Database Storage Administator's Guide for more details.
KFNDG-00405: specified disk group <varname>string</varname> appears to be mounted: Cause: Disk group was mounted.; Action: Unmount the disk group and retry renamedg.
KFNDG-00406: disk group (<varname>string</varname>) is in use by CSS: Cause: Cluster Synchronization Service(CSS) was using the disk group to be renamed.; Action: Refer to crsctl command to relocate voting disks from disk group.
KFNDG-00407: Could not find disks for disk group <varname>string</varname>: Cause: No disks were discovered for disk group.; Action: Try renamedg with a different discovery string.
KFNDG-00408: disk (<varname>string</varname>:<varname>string</varname>) could not be discovered: Cause: Disk was either deleted or moved.; Action: None
KFNDG-00409: disk (<varname>string</varname>) doesn't belong to disk group (<varname>string</varname>): Cause: Disk is not part of the specified disk group.; Action: None
KFNDG-00410: failed to discover devices in folder <varname>string</varname>: Cause: Insufficient privileges or invalid discovery string.; Action: See log for additional details.
KFNDG-00600: internal error <varname>string</varname>: Cause: An internal error occured while executing renamedg.; Action: Contact Oracle Support Services.
KFNDG-00601: fatal error <varname>string</varname>: Cause: A fatal error occurred while executing renamedg.; Action: Contact Oracle Support Services.
KFNDG-00603: failed to initialize device discovery: Cause: Error occurred while communicating with generic services layer.; Action: Contact Oracle Support Services.
KFNDG-00700: system dependent error (<varname>number</varname>, <varname>string</varname>, <varname>string</varname>, <varname>string</varname>) occurred: Cause: Internal system error occurred.; Action: Contact Oracle Support Services.
KFNDG-00701: Error <varname>number</varname> while performing I/O: Cause: I/O failure.; Action: Contact Oracle Support Services.