// Copyright (c) 2008, 2015, Oracle and/or its affiliates. All rights reserved. // // NAME // PrGsMsg.msg // // DESCRIPTION // Message file for GridHome Server Storage apis. // used by the GridHome Server Operation layer. // // NOTES // // MODIFIED (MM/DD/YY) // smadabhu 06/23/15 - Proj 47205 - OLFS support // ocordova 01/30/13 - Fix Bug 13901932 // sowong 11/05/12 - fix bug13879779 // xesquive 02/07/12 - Bug fix 13566257 // ksviswan 07/13/11 - Creation // // */ // // PACKAGE=package oracle.gridhome.resources; // IMPORT=import oracle.ops.mgmt.nls.MessageKey; 100, VOL_CREATE_FAIL, "Failed to create volume {0}" // *Cause: An attempt to create a volume device for the specified volume name failed. // *Action: Review the accompanying error messages that provide the details of why the volume creation failed. // Resolve the reported problem and retry. / 101, DG_NOT_ENOUGH_SPACE, "Insufficient space in diskgroup {0}" // *Cause: Diskgroup does not have enough space for the specified operation. // *Action: Add more disks to the diskgroup and re-try the operation. / 102, VOL_ALREADY_INUSE, "Volume {0} already in use" // *Cause: The volume name specified was already being used by another volume device. // *Action: Specify a different volume name and retry. / 103, DG_NOT_EXIST, "Disk group {0} does not exist" // *Cause: The specified disk group was either not created or was not accessible. // *Action: Review the accompanying error messages that provide the details. // Resolve the reported problem and retry. / 104, VOL_NOT_EXIST, "volume {0} does not exist" // *Cause: The specified volume did not exist. // *Action: Create the specified volume or specify a volume that exists and retry the operation. / 105, GET_VOLDEV_FAIL, "Failed to get volume device for volume {0} " // *Cause: An attempt to get the volume device path for the specified volume failed. // *Action: Review the accompanying error messages that provide the details. Resolve the reported problem and retry. / 106, VOL_DELETE_FAIL, "Failed to delete volume {0}" // *Cause: An attempt to delete the volume device for the specified volume name failed. // *Action: Review the accompanying error messages that provide the details of why the volume creation failed. // Resolve the reported problem and retry. / 107, CREATE_ACFS_FAIL, "Failed to create ACFS on volume device {0}" // *Cause: The operation to create an Oracle ASM Cluster File System on the specified volume device failed. // *Action: Review the accompanying error messages that provide the details of why the file system creation failed. // Resolve the reported problem and retry. / 108, DELETE_ACFS_FAIL, "Failed to delete ACFS on volume device {0}" // *Cause: The operation to delete an Oracle ASM Cluster File System on the specified volume device failed. // *Action: Review the accompanying error messages that provide the details of why the file system creation failed. // Resolve the reported problem and retry. / 109, SNAP_CREATE_FAIL, "Failed to create snapshot {0}" // *Cause: An attempt to create a snapshot on the Oracle ASM Cluster File System failed. // *Action: Review the accompanying error messages that provide the details of why the snapshot creation failed. // Resolve the reported problem and retry. / 110, SNAP_DELETE_FAIL, "Failed to delete snapshot {0}" // *Cause: An attempt to delete a snapshot on the Oracle ASM Cluster File System failed. // *Action: Review the accompanying error messages that provide the details of why the snapshot deletion failed. // Resolve the reported problem and retry. / 111, SNAP_LIMIT_REACHED, "Unable to create snapshot {0} as the limit is reached" // *Cause: The maximum number of snapshots is already reached on the specified ASM Cluster File System. // *Action: Reduce the number of snapshots and retry. / 112, SNAP_ALREADY_EXIST, "snapshot {0} already exists" // *Cause: The specified snapshot name is being already used by another snapshot in the specified ASM Cluster File System. // *Action: Specify a different snapshot name and retry. / 113, SNAP_NOT_EXIST, "snapshot {0} does not exist" // *Cause: Snapshot with the specified name did not exist. // *Action: Create the snapshot or specify a snapshot that exists and retry the operation. / 114, INVALID_SNAPTYPE, "snapshot type {0} is not valid" // *Cause: An invalid snapshot type was passed for snapshot creation. // *Action: Pass either read-only or read-write as snapshot type to create the snapshot. / 115, INVALID_MOUNTTYPE, "mount type {0} is not valid" // *Cause: An invalid mount type was specified for mount operation. // *Action: Internal error. Contact Oracle Support Services. / 116, VOL_RESIZE_FAIL, "Failed to resize volume {0} for file system path {1}" // *Cause: An attempt to resize the volume for the specified file system path failed when creating a snapshot. // *Action: Review the accompanying error messages that provide details of the failure. // Resolve the reported problem and retry. / 117, LPM_SETUP_FAILED, "failed to configure Oracle Layered File System" // *Cause: An attempt to configure Oracle Layered File System failed because the new file system drivers could not be installed. // *Action: Examine the accompanying error messages, address the issues described, and then retry. / 118, MOUNT_OLFS_FAILED, "failed to mount the gold image path \'{0}\' and read-write path \'{1}\' on the Oracle Grid Infrastructure home path \'{2}\'" // *Cause: An attempt to instantiate the home path failed because the \'mount\' command completed with errors. // *Action: Examine the accompanying error messages, address the issues described, and then retry. / 119, LPM_SETUP_FAILED_NODES, "failed to configure Oracle Layered File System on nodes {0}" // *Cause: An attempt to configure Oracle Layered File System failed because the new file system drivers could not be installed. // *Action: Examine the accompanying error messages, address the issues described, and then retry. / 120, MOUNT_OLFS_FAILED_NODES, "failed to mount the gold image path \'{0}\' and read-write path \'{1}\' on the Oracle Grid Infrastructure home path \'{2}\' on nodes \'{3}\'" // *Cause: An attempt to instantiate the home path failed because the \'mount\' command completed with errors. // *Action: Examine the accompanying error messages, address issues described and retry. /