117 PRGO-01003 to PRGO-11371
- PRGO-01003: Invalid option specified when granting a role to a client user or another role
-
Cause: The '-role' option was specified but neither '-user' nor '-grantee' was specified.
- PRGO-01004: Invalid option specified when revoking a role from client user or another role
-
Cause: The '-role' option was specified but neither '-user' nor '-grantee' was specified.
- PRGO-01005: Invalid container type "{0}"
-
Cause: Internal error.
- PRGO-01006: An unsupported 'rhpctl' command was issued on Rapid Home Provisioning Client
-
Cause: A 'rhpctl' command was submitted on Rapid Home Provisioning Client.
- PRGO-01007: Unable to retrieve Rapid Home Provisioning Server host name
-
Cause: While accessing GNS, an attempt to retrieve the host name failed.
- PRGO-01019: Invalid option specified when adding visibility to an image for either client user or role
-
Cause: Neither the '-identity' option nor the '-role' option was specified
- PRGO-01020: Invalid option specified when removing visibility from an image for either client user or role
-
Cause: Neither the '-identity' option nor the '-role' option was specified
- PRGO-01021: Invalid option specified when retrieving information for image series
-
Cause: An invalid combination of the '-series', '-image' and '-client' options was specified.
- PRGO-01022: Working copy "{0}" already exists.
-
Cause: An existing working copy of the same name was found when adding a new working copy.
- PRGO-01028: Disk group "{0}" already exists.
-
Cause: An existing disk group of the same name was found when adding a new disk group.
- PRGO-01029: Disk group "{0}" does not exist.
-
Cause: Removal of a disk group failed because the specified disk group was not configured for Rapid Home Provisioning Server.
- PRGO-01030: Disk group "{0}" is in use.
-
Cause: Removal of the disk group failed because the specified disk group was in use for data storage by the Rapid Home Provisioning Server.
- PRGO-01031: User "{0}" lacks the authority to perform the 'add role' operation.
-
Cause: The user running the 'rhpctl add role' command did not have the required authorization.
- PRGO-01032: User "{0}" lacks the authority to perform the 'query role' operation.
-
Cause: The user running the 'rhpctl query role' command did not have the required authorization.
- PRGO-01033: User "{0}" lacks the authority to perform the 'delete role' operation.
-
Cause: The user running the 'rhpctl delete role' command did not have the required authorization.
- PRGO-01034: User "{0}" lacks the authority to perform the 'grant role' operation.
-
Cause: The user running the 'rhpctl grant role' command did not have the required authorization.
- PRGO-01035: User "{0}" lacks the authority to perform the 'revoke role' operation.
-
Cause: The user running the 'rhpctl revoke role' command did not have the required authorization.
- PRGO-01036: User "{0}" lacks the authority to perform the 'add image' operation.
-
Cause: The user running the 'rhpctl add image' command did not have the required authorization.
- PRGO-01037: User "{0}" lacks the authority to perform the 'import image' operation.
-
Cause: The user running the operation on the image did not have the required authorization.
- PRGO-01038: User "{0}" lacks the authority to perform the 'delete image' operation.
-
Cause: The user running the 'rhpctl delete image' command did not have the required authorization.
- PRGO-01039: User "{0}" lacks the authority to perform the 'query image' operation.
-
Cause: The user running the 'rhpctl query image' command did not have the required authorization.
- PRGO-01040: User "{0}" lacks the authority to grant viewing access to image "{1}".
-
Cause: The user running the 'rhpctl allow image' command did not have the required authorization.
- PRGO-01041: User "{0}" lacks the authority to disallow viewing access to image "{1}".
-
Cause: The user running the 'rhpctl disallow image' command did not have the required authorization.
- PRGO-01042: User "{0}" lacks the authority to add a new series.
-
Cause: The user running the 'rhpctl add series' command did not have the required authorization.
- PRGO-01043: User "{0}" lacks the authority to add an image to a series.
-
Cause: The user running the 'rhpctl insertimage series' command did not have the required authorization.
- PRGO-01044: User "{0}" lacks the authority to delete a series.
-
Cause: The user running the 'rhpctl delete series' command did not have the required authorization.
- PRGO-01045: User "{0}" lacks the authority to delete an image from a series.
-
Cause: The user running the 'rhpctl deleteimage series' command did not have the required authorization.
- PRGO-01046: User "{0}" lacks the authority to view series.
-
Cause: The user running the 'rhpctl query series' command did not have the required authorization.
- PRGO-01047: User "{0}" lacks the authority to perform the 'delete workingcopy' operation.
-
Cause: The user running the 'rhpctl delete workingcopy' command did not have the required authorization.
- PRGO-01048: User "{0}" lacks the authority to perform the 'query workingcopy' operation.
-
Cause: The user running the 'rhpctl query workingcopy' command did not have the required authorization.
- PRGO-01049: Rapid Home Provisioning operations cannot be registered with the managed object server
-
Cause: Operations for the Rapid Home Provisioning application were not registered with the managed object server.
- PRGO-01058: The client name "{0}" supplied is a Rapid Home Provisioning Server (RHPS).
-
Cause: A RHPS name was received when a Rapid Home Provisioning Client (RHPC) name was expected.
- PRGO-01059: Image "{0}" already exists.
-
Cause: An existing image of the same name was found when adding a new image.
- PRGO-01060: Role "{0}" already exists.
-
Cause: An existing role of the same name was found when adding a new role.
- PRGO-01062: Unable to remove image series "{0}" because it contains images and the '-force' option was not specified.
-
Cause: An attempt to delete an image series was rejected because the image series contained images.
- PRGO-01067: No disk group has been configured for Rapid Home Provisioning Server
-
Cause: An attempt to retrieve the disk group resources failed because no disk group was configured.
- PRGO-01068: Failed to connect to Rapid Home Provisioning Server (RHPS)
-
Cause: An attempt to connect to Rapid Home Provisioning Server (RHPS) failed, possibly because it was not running.
- PRGO-01069: Internal error [# {0} #].
-
Cause: An internal error occurred.
- PRGO-01070: Working copy "{0}" cannot be deleted from Rapid Home Provisioning Client cluster "{1}".
-
Cause: An attempt to delete a working copy failed because the specified working copy had not been created by this Rapid Home Provisioning Client.
- PRGO-01071: Image "{0}" already exists in the series "{1}".
-
Cause: An attempt to add an image to a series failed because the image was already added to the series.
- PRGO-01072: Image "{0}" does not exist in the series "{1}".
-
Cause: An attempt to delete an image from a series failed because the image was not found in the series.
- PRGO-01073: Rapid Home Provisioning Client "{0}" is disabled.
-
Cause: The client was disabled and could not run RHPCTL commands.
- PRGO-01074: failed while checking if cluster "{0}" is enabled to run rhpctl commands
-
Cause: An error occurred while checking if the cluster was enabled.
- PRGO-01076: Incorrect syntax in the '-maproles' option: "{0}"
-
Cause: The syntax of the '-maproles' option supplied was incorrect.
- PRGO-01077: Unable to retrieve Rapid Home Provisioning client host name and port number
-
Cause: While looking up Rapid Home Provisioning Client connection details in GNS, an attempt to retrieve the host name and port number failed.
- PRGO-01078: unable to retrieve Rapid Home Provisioning Server host name and port number
-
Cause: While looking up Rapid Home Provisioning Server connection details in Grid Naming Service (GNS), an attempt to retrieve the host name and port number failed.
- PRGO-01079: Unable to remove image "{0}" because working copies "{1}" have been configured for this image.
-
Cause: An attempt to delete an image failed because there were working copies configured for the image.
- PRGO-01081: User "{0}" does not have the role "{1}". The list of roles that the user has is:\n{2}
-
Cause: An attempt to remove a role from a user failed because the user does not have that role.
- PRGO-01082: User "{0}" for cluster "{1}" was already allowed access to image {2}.
-
Cause: An attempt to allow access privilege to the user was rejected because the user had already been granted access privilege to the image using the 'rhpctl allow image' command.
- PRGO-01083: Role "{0}" was already allowed access to image "{1}".
-
Cause: An attempt to allow access privilege to the role was rejected because the role had already been granted access privilege to the image using the 'rhpctl allow image' command.
- PRGO-01084: User "{0}" for cluster "{1}" has never been granted access to image {2}.
-
Cause: An attempt to disallow the user from access privilege to the image failed because the user had never been granted access privilege to the image using the 'rhpctl allow image' command.
- PRGO-01085: Role "{0}" has never been granted access to image "{1}".
-
Cause: An attempt to disallow the role from access privilege to the image failed because the role had never been granted access privilege to the image using the 'rhpctl allow image' command.
- PRGO-01087: READ privilege cannot be granted for image "{0}" because the image state is NEW.
-
Cause: An attempt to grant READ privilege for the specified image failed because the image state is NEW."
- PRGO-01088: READ privilege cannot be removed for image "{0}" because the image state is NEW.
-
Cause: An attempt to remove READ privilege for the specified image failed because the image state is NEW."
- PRGO-01090: failed to retrieve the owner of the image "{0}"
-
Cause: An attempt to retrieve the owner of the image failed.
- PRGO-01091: failed to retrieve the owner of the working copy "{0}"
-
Cause: An attempt to retrieve the owner of the working copy failed.
- PRGO-01092: Failed to update Rapid Home Provisioning Client's GNS information
-
Cause: An error occurred while updating the Rapid Home Provisioning Client's GNS information.
- PRGO-01097: Grant operation failed because role "{0}" is already granted to user "{1}".
-
Cause: An attempt to grant a role to a given user failed because the role was already granted to that user.
- PRGO-01098: Revoke operation failed because role "{0}" is not granted to user "{1}".
-
Cause: An attempt to revoke a role from a given user failed because the role was not granted to that user.
- PRGO-01099: root user is not allowed to add working copy "{0}"
-
Cause: An attempt was made to create a working copy owned by the root user.
- PRGO-01100: Failed to connect to the management database because it is not running
-
Cause: An attempt to connect to the management database failed because it was not running.
- PRGO-01101: Missing Oracle base for working copy "{0}" for image "{1}" because image type is {2}.
-
Cause: The '-oraclebase' option was omitted for an image type that requires it.
- PRGO-01103: add image "{0}" failed
-
Cause: An attempt was made to perform an add image operation with the same image name during a rerun of the failed import image operation.
- PRGO-01104: import image "{0}" failed
-
Cause: An attempt was made to perform an import image operation with the same image name during a rerun of the failed add image operation.
- PRGO-01105: The specified '-oraclebase' option value "{0}" is a non-writable directory or cannot be created on nodes "{1}".
-
Cause: The specified '-oraclebase' option value was a non-writable path to the Grid user or cannot be created by the Grid user.
- PRGO-01106: The specified path "{0}" does not exist on nodes "{1}".
-
Cause: The mount path specified did not exist on all cluster nodes.
- PRGO-01107: Database "{0}" already exists.
-
Cause: The specified database resource was already registered in Oracle Clusterware.
- PRGO-01108: The specified disk group "{0}" does not exist.
-
Cause: The resource for the specified disk group could not be found. Either the disk group name was misspelled or the disk group has not been mounted.
- PRGO-01109: The specified path "{0}" is not a shared path.
-
Cause: An attempt to add a working copy failed because the specified storage path was not shared among the cluster nodes.
- PRGO-01110: The specified nodes "{0}" do not exist on the cluster.
-
Cause: The specified nodes could not be found on the cluster.
- PRGO-01111: An administrator-managed database cannot be created on specified Leaf Nodes "{0}".
-
Cause: An attempt to create a working copy failed because some or all of the specified nodes are Leaf Nodes.
- PRGO-01112: The specified server pool "{0}" does not exist.
-
Cause: The specified server pool was not found.
- PRGO-01113: server pool "{0}" category of 'leaf' not supported for policy-managed database
-
Cause: An attempt to create a working copy was rejected because the specified server pool has a category with CSS_ACTIVE_ROLE=LEAF.
- PRGO-01114: invalid use of -pqpool option for provisioning database on cluster "{0}"
-
Cause: The '-pqpool' option was specified for provisioning a database on a target cluster that was not an Oracle Flex Cluster.
- PRGO-01115: -newpqpool and -pqcardinality options can not be specified for provisioning database on Rapid Home Provisioning Server (RHPS).
-
Cause: An attempt to create workingcopy failed because RHPS does not support the '-newpqpool' and '-pqcardinality' options.
- PRGO-01116: User equivalence does not exist on nodes "{0}".
-
Cause: User equivalence did not exist among the nodes indicated.
- PRGO-01117: The specified user name "{0}" does not exist in the operating system.
-
Cause: An attempt to create a working copy failed because the user did not exist.
- PRGO-01118: The specified storage path "{0}" is not a directory.
-
Cause: An attempt to create a working copy failed because the specified storage path is not a directory.
- PRGO-01119: The specified storage path "{0}" does not exist.
-
Cause: An attempt to create a working copy failed because the specified storage path did not exist.
- PRGO-01125: Delete operation failed because role "{0}" has the following roles: "{1}".
-
Cause: An attempt to delete a role failed because the role has been granted one or more roles.
- PRGO-01126: Delete operation failed because role "{0}" has been granted to the following users: "{1}".
-
Cause: An attempt to delete a role failed because the role has been granted to one or more users.
- PRGO-01128: An unsupported 'rhpctl' command was issued on Rapid Home Provisioning server
-
Cause: A Rapid Home Provisioning client 'rhpctl' command was submitted on the Rapid Home Provisioning server.
- PRGO-01129: failed to connect to Rapid Home Provisioning Client (RHPC)
-
Cause: An attempt to connect to Rapid Home Provisioning Client (RHPC) failed, possibly because it was not running on the remote cluster.
- PRGO-01130: Database name "{0}" contains invalid characters.
-
Cause: The supplied database name contained invalid characters.
- PRGO-01131: Delete operation failed, client "{0}" has the following working copies: "{1}".
-
Cause: A delete client operation failed because one or more working copies exist on the specified client.
- PRGO-01132: Rapid Home Provisioning Server (RHPS) user "{0}" does not exist in the repository.
-
Cause: A repository query failed unexpectedly. This is an internal error.
- PRGO-01133: User "{0}" lacks the authority to perform the 'promote image' operation.
-
Cause: The user running the 'rhpctl promote image' command did not have the required authorization.
- PRGO-01134: built-in role "{0}" cannot be deleted
-
Cause: A request was made to delete a built-in role.
- PRGO-01135: User "{0}" lacks the authority to perform the 'add client' operation.
-
Cause: The user running the 'rhpctl add client' command did not have the required authorization.
- PRGO-01136: User "{0}" lacks the authority to perform the 'add workingcopy' operation.
-
Cause: The user running the 'rhpctl add workingcopy' command did not have the required authorization.
- PRGO-01137: User "{0}" lacks the authority to perform the 'query client' operation.
-
Cause: The user running the 'rhpctl query client' command did not have the required authorization.
- PRGO-01138: User "{0}" lacks the authority to perform the 'delete client' operation.
-
Cause: The user running the 'rhpctl delete client' command did not have the required authorization.
- PRGO-01139: User "{0}" lacks the authority to perform the 'delete workingcopy' operation.
-
Cause: The user running the 'rhpctl delete workingcopy' command did not have the required authorization.
- PRGO-01140: User "{0}" lacks the authority to perform the 'modify client' operation.
-
Cause: The user running the 'rhpctl modify client' command did not have the required authorization.
- PRGO-01141: built-in GH_SA role cannot be revoked from Oracle Grid Infrastructure user "{0}"
-
Cause: An attempt was made to revoke the built-in GH_SA role from the user of the Oracle Grid Infrastructure home.
- PRGO-01142: built-in GH_CA role cannot be revoked from Oracle Grid Infrastructure user "{0}" of cluster "{1}"
-
Cause: An attempt was made to revoke the built-in GH_CA role from the user of the Oracle Grid Infrastructure home.
- PRGO-01143: built-in GH_SA role cannot be revoked from role "{0}" by user "{1}" at cluster {2}
-
Cause: The user running 'rhpctl revoke role' command did not have the privilege to revoke the built-in GH_SA role from the specified role.
- PRGO-01144: built-in GH_CA role cannot be revoked from role "{0}" by user "{1}" at cluster {2}
-
Cause: The user running 'rhpctl revoke role' command did not have the privilege to revoke the built-in GH_CA role from the specified role.
- PRGO-01145: User "{0}" on cluster "{1}" cannot grant the built-in GH_SA role to another user.
-
Cause: The user running 'rhpctl grant role' command did not have the privilege to grant the built-in GH_SA role to another user.
- PRGO-01146: User "{0}" on cluster "{1}" cannot grant the built-in GH_CA role to another user.
-
Cause: The user running 'rhpctl grant role' command did not have the privilege to grant the built-in GH_CA role to another user.
- PRGO-01147: User "{0}" on cluster "{1}" cannot grant the built-in GH_SA role to another role.
-
Cause: The user running 'rhpctl grant role' command did not have the privilege to grant the built-in GH_SA role to another role.
- PRGO-01148: User "{0}" on cluster "{1}" cannot grant the built-in GH_CA role to another role.
-
Cause: The user running 'rhpctl grant role' command did not have the privilege to grant the built-in GH_CA role to another role.
- PRGO-01149: The source working copy version and the patched working copy version are different.
-
Cause: An attempt to move the database failed because the source and patched working copy versions are different.
- PRGO-01150: The source working copy owner and the patched working copy owner are different.
-
Cause: An attempt to move the database failed because the source and patched working copy owners are different.
- PRGO-01151: The database 'move' for the specified workingcopy cannot be performed from Rapid Home Provisioning Client (RHPC) "{0}".
-
Cause: The working copy was not created by this Rapid Home Provisioning Client.
- PRGO-01152: operation not allowed because client authentication failed
-
Cause: A 'rhpctl' request was not processed because client authentication failed at the server.
- PRGO-01153: failed to validate the client authentication
-
Cause: An internal error occurred.
- PRGO-01158: User "{0}" on cluster "{1}" cannot revoke the built-in GH_SA role from another user.
-
Cause: The user issuing a 'rhpctl revoke role' command did not have the privilege to revoke the built-in GH_SA role from another user.
- PRGO-01159: User "{0}" on cluster "{1}" cannot revoke the built-in GH_CA role from another user.
-
Cause: The user issuing a 'rhpctl revoke role' command did not have the privilege to revoke the built-in GH_CA role from another user.
- PRGO-01160: User "{0}" lacks the authority to perform the 'export client' operation.
-
Cause: The user running the 'rhpctl export client' command did not have the required authorization.
- PRGO-01161: The source working copy and the patched working copy cannot be the same.
-
Cause: An attempt to move the database was rejected because the specified source and patched working copies are the same.
- PRGO-01162: operation not allowed because user authentication failed for user "{0}"
-
Cause: A RHPCTL request was not processed because user authentication failed at the server.
- PRGO-01163: unable to create working copy "{0}" because maximum number of snapshots has been reached for image "{1}"
-
Cause: An attempt to create a working copy failed because the maximum number of snapshots has been reached for the image.
- PRGO-01164: failed to create a volume for import image because the configured disk group "{0}" does not have enough available space. Detailed error:\n{1}
-
Cause: An attempt to create a volume for an import image failed because the configured disk group did not have enough available space.
- PRGO-01165: unable to create volume because the generated volume name already exists
-
Cause: An attempt to create a volume failed because the number of tries attempted for generating the volume name was exhausted.
- PRGO-01166: unable to create image "{0}" from working copy "{1}" because maximum number of snapshots has been reached
-
Cause: An attempt to create a image from the working copy failed because the maximum number of snapshots has been reached.
- PRGO-01167: HA VIP resource does not exist in Oracle Clusterware.
-
Cause: An attempt to add Rapid Home Provisioning Client failed because no HA VIP resource was registered with Oracle Clusterware.
- PRGO-01170: The default templates directory "{0}" does not exist in the image specified.
-
Cause: The image created on the Rapid Home Provisioning Server did not contain the templates directory.
- PRGO-01188: failed to add client on Rapid Home Provisioning Server (RHPS) because neither GNS server nor GNS client are configured on this cluster
-
Cause: A 'rhpctl add client' command failed because neither GNS server nor GNS client was configured on this cluster.
- PRGO-01189: provisioning of databases not supported on working copy of image type "{0}"
-
Cause: An attempt to create or delete a database was rejected because the working copy was not created from an image of type ORACLEDBSOFTWARE.
- PRGO-01190: The database "{0}" was not created using working copy "{1}".
-
Cause: An attempt to delete the specified database was rejected because the working copy specified was not the one used to create the database.
- PRGO-01191: The specified working copy "{0}" is not provisioned on the cluster "{1}".
-
Cause: An attempt to add a database was rejected because the specified working copy was not provisioned on this cluster.
- PRGO-01192: failed to create database "{0}" because the specified working copy was not created properly
-
Cause: An attempt to add a database was rejected because the specified working copy was not created properly.
- PRGO-01195: The '-path' option required for creating working copy on the client cluster is not specified.
-
Cause: The attempt to move database using 'rhpctl move database' was rejected because
- PRGO-01196: The '-image' option required for creating the working copy is not specified.
-
Cause: The attempt to move the database using 'rhpctl move database' failed because the '-image' option was not specified. The '-image' option is required to create a new working copy to specify the image from which to create the working copy.
- PRGO-01197: The patched working copy was not created from an image of type ORACLEDBSOFTWARE.
-
Cause: An attempt to move the database failed because the patched working copy was not created from an image of type ORACLEDBSOFTWARE.
- PRGO-01198: The source working copy is incomplete.
-
Cause: The source working copy was in a partially completed state.
- PRGO-01201: cannot add image from working copy "{0}" because creation of this working copy was not complete.
-
Cause: An attempt to add an image from a working copy was rejected because creation of the specified working copy was not complete.
- PRGO-01202: Nothing to modify.
-
Cause: No options were specified to modify.
- PRGO-01203: cannot add working copy from image "{0}" because creation of this image was not complete
-
Cause: An attempt to add a working copy from an image was rejected because creation of the specified image was not complete.
- PRGO-01204: The specified working copy has no databases to move.
-
Cause: An attempt to move a database from a working copy failed because the specified working copy did not have a database configured.
- PRGO-01205: The source working copy was not created from an image of type ORACLEDBSOFTWARE.
-
Cause: An attempt to move a database failed because the source working copy was not created from an image of type ORACLEDBSOFTWARE.
- PRGO-01206: The '-oraclebase' option is not allowed when creating working copy "{0}" for image "{1}" because the image type of this working copy is not ORACLEDBSOFTWARE.
-
Cause: An attempt to add a working copy was rejected because the '-oraclebase' option was specified to create a working copy from an image with the type SOFTWARE. The '-oraclebase' option is valid only for images of type ORACLEDBSOFTWARE.
- PRGO-01207: failed to delete database "{0}" because the specified working copy {0} is not provisioned on this cluster
-
Cause: An attempt to delete a database was rejected because the specified working copy was not provisioned on this cluster.
- PRGO-01208: Shared storage verification failed for path "{0}". Detailed error: "{1}"
-
Cause: An invalid value was specified for the '-storage' option. Either the storage does not exist, or it is not shared.
- PRGO-01209: unable to delete working copy "{0}" because it contains databases and the force option was not specified
-
Cause: An attempt to delete the working copy was rejected because databases were configured to run from the working copy and the '-force' option was not specified.
- PRGO-01210: unable to delete working copy "{0}" because it contains one or more running databases
-
Cause: An attempt to delete the working copy was rejected because the working copy contained one or more running databases.
- PRGO-01211: User "{0}" lacks the authority to perform the operation.
-
Cause: The user did not have the required authorization to run the command.
- PRGO-01212: unable to delete user "{0}" because working copies "{1}" are owned by this user
-
Cause: An attempt to delete a given user failed because the user owned one or more working copies in the repository.
- PRGO-01213: option "{0}" is not allowed from a Rapid Home Provisioning Client
-
Cause: An option was supplied which can only be used from a Rapid Home Provisioning Server.
- PRGO-01217: Invalid value "{0}" specified for database template option.
-
Cause: The '-dbtemplate' option value specified is neither an absolute path nor of the form '<image_name>:<relative_path_of_template>'.
- PRGO-01218: failed to export the image file system specified by the database template option value "{0}"
-
Cause: An error occurred while attempting to export the database template image file system.
- PRGO-01219: failed to remove the export file system for the image specified by the database template option
-
Cause: An error occurred while attempting to remove the export file system for the database template image.
- PRGO-01220: failed to export the database template image file system because creation of the image "{0}" was not complete
-
Cause: An attempt to export a database template image file system was rejected because creation of the specified image was not complete.
- PRGO-01222: The specified database template path "{0}" does not exist
-
Cause: An attempt to create a database failed because the specified database template path does not exist.
- PRGO-01223: The specified template file "{0}" does not exist on nodes {1}.
-
Cause: The specified database template file did not exist either on all of the specified nodes for administration managed database, or on all of the cluster nodes for policy managed database.
- PRGO-01224: cannot create a single instance database on multiple nodes "{0}"
-
Cause: The value specified for the '-node' option contained multiple nodes.
- PRGO-01225: failed to add a working copy from image {0} because file system {1} contained within volume device {2} is offline
-
Cause: An attempt to add a working copy failed because the file system resource of the image supplied was offline.
- PRGO-01226: The source working copy is configured in a different cluster from the patched working copy
-
Cause: An attempt to move the database failed because the source and patched working copies are configured in different clusters.
- PRGO-01227: The '-path' option is not allowed when moving a database on Rapid Home Provisioning Server (RHPS).
-
Cause: An attempt to move a database on a Rapid Home Provisioning Server failed because the '-path' option was specified without remote provisioning.
- PRGO-01228: failed to write a checkpoint for the operation because the checkpoint file system "{0}" is not mounted
-
Cause: Writing the checkpoint for the previous operation failed because the checkpoint file system was offline.
- PRGO-01229: No disk group has been configured for Rapid Home Provisioning Client.
-
Cause: An attempt to create a local file system failed because no disk group was configured.
- PRGO-01233: The specified '-path' option value "{0}" is on ACFS
-
Cause: The working copy could not be added because '-path' option value was on ACFS.
- PRGO-01234: unable to add image "{0}" from workingcopy "{1}" using local storage
-
Cause: The working copy was stored on local storage on the Rapid Home Provisioning Client cluster.
- PRGO-01235: path "{0}" is not writable by "{1}"
-
Cause: The specified path for local storage on the Rapid Home Provisioning Client did not have write access by the user.
- PRGO-01236: path "{0}" does not have "{1}" KB of free space on nodes {2}
-
Cause: There was insufficient free space on the nodes to copy the working copy.
- PRGO-01237: cannot delete built-in user "{0}"
-
Cause: An attempt to delete a given user failed because the specified user was a built-in user.
- PRGO-01238: specified server pool "{0}" has no candidate server for single instance database "{1}"
-
Cause: An attempt to create a single instance database failed because the specified server pool did not have a configured candidate server.
- PRGO-01239: specified server pool "{0}" has a maximum size "{1}" too large for single instance database {2}
-
Cause: An attempt to create a single instance database failed because a server pool with maximum size greater than one server was specified.
- PRGO-01240: specified server pool "{0}" has more than one candidate server
-
Cause: An attempt to create a single instance database failed because a server pool with more than one candidate server was specified.
- PRGO-01241: The path "{0}" specified for the working copy duplicates the internal path used to mount working copy.
-
Cause: An attempt to add a working copy was rejected because the specified path duplicates the internal path used to mount the working copy.
- PRGO-01242: failed to add a working copy with local storage type because no path option was specified and no disk group was configured for the Rapid Home Provisioning Client cluster
-
Cause: A command to add a working copy with local storage type was issued without the path option and for a Rapid Home Provisioning Client cluster that had no configured disk group.
- PRGO-01243: An attempt to create a working copy from image "{0}" failed because it is for the "{1}" platform, whereas the detected platform is {2}.
-
Cause: The image supplied was for a different platform than the one for which the working copy was requested.
- PRGO-01244: Cannot grant any role to a root user
-
Cause: An attempt was made to grant a role to a root user.
- PRGO-01245: User "{0}" for cluster "{1}" is the owner of image "{2}".
-
Cause: An attempt to disallow the user access from the image failed because the user owned the image.
- PRGO-01246: Role "{0}" cannot be disallowed from image "{1}".
-
Cause: An attempt to disallow the role access from the image failed because the role was a built-in role associated with the image and was not granted access using the 'rhpctl allow image' command.
- PRGO-01247: Role "{0}" cannot be allowed for image "{1}".
-
Cause: An attempt to allow the role access to the image failed because the role was a built-in role associated with the image.
- PRGO-01248: cannot grant role "{0}" to a built-in role "{1}"
-
Cause: An attempt was made to grant a role to a built-in role.
- PRGO-01249: cannot revoke role "{0}" from a built-in role "{1}"
-
Cause: An attempt was made to revoke a role from a built-in role.
- PRGO-01250: cannot revoke role "{0}" from role "{1}" because role "{1}" has only one associated role
-
Cause: An attempt to revoke a role from another role with only one associated role failed because that role was a user defined role.
- PRGO-01251: Role "{0}" cannot start with "GH_".
-
Cause: An attempt to add a role starting with "GH_" failed because "GH_" is a prefix reserved by Oracle for built-in roles.
- PRGO-01257: failed to import image "{0}"
-
Cause: An error occurred while attempting to import an image.
- PRGO-01258: The specified patched working copy is incomplete.
-
Cause: The patched working copy was in a partially completed state.
- PRGO-01260: Cluster Verification checks for database home provisioning failed for the specified working copy {0}.
-
Cause: One or more Cluster Verification checks for database home provisioning failed.
- PRGO-01261: unable to add database {0} because the specified working copy {1} already exists
-
Cause: An attempt to add the specified database using 'rhpctl add workingcopy' was rejected because the working copy specified was already in existence.
- PRGO-01262: unable to verify the existence of the specified file {0} on nodes {1}
-
Cause: An error occurred while attempting to access the specified database template file.
- PRGO-01263: The options '-storagetype LOCAL' and '-path' with non-ACFS path are required for provisioning pre 11.2 version database home
-
Cause: An attempt to provision a pre 11.2 version database home was rejected because it can only be provisioned on local, non-ACFS storage.
- PRGO-01264: The '-nodes' option is required for pre 11.2 version database because it cannot be policy-managed.
-
Cause: An attempt to create a policy-managed database failed because only administrator-managed databases are supported in pre 11.2 version.
- PRGO-01265: The version of the specified home is {0} and is not 10.2.0.5.
-
Cause: An attempt to import a version 10.2 image was rejected because the specified Oracle home was not version 10.2.0.5.
- PRGO-01266: The version of the specified home is {0} and is not supported.
-
Cause: An attempt to import a version 11.1 image was rejected because this version is not supported.
- PRGO-01267: failed to add a database {0} using working copy {1} because the image file system {2} using the volume device {3} is offline
-
Cause: An attempt to add a database failed because the file system resource of the image containing the working copy supplied was offline.
- PRGO-01268: failed to add a database {0} using working copy {1} because the file system {2} using volume device {3} is offline in the Rapid Home Provisioning Client cluster
-
Cause: An attempt to add a database failed because the file system resource in the Rapid Home Provisioning Client containing the working copy supplied was offline.
- PRGO-01269: failed to delete a working copy {0} because the image file system {1} using the volume device {2} is offline
-
Cause: An attempt to delete a working copy failed because the file system resource of the image containing the working copy supplied was offline.
- PRGO-01270: failed to delete a working copy {0} because the file system {1} using volume device {2} is offline in the Rapid Home Provisioning Client cluster
-
Cause: An attempt to delete a working copy failed because the file system resource in the Rapid Home Provisioning Client containing the working copy supplied was offline.
- PRGO-01271: failed to move database using working copy {0} because the image file system {1} using the volume device {2} is offline
-
Cause: An attempt to move database failed because the file system resource of the image containing the working copy supplied was offline.
- PRGO-01272: failed to move database using working copy {0} because the file system {1} using volume device {2} is offline in the Rapid Home Provisioning Client cluster
-
Cause: An attempt to move database failed because the file system resource in the Rapid Home Provisioning Client containing the working copy supplied was offline.
- PRGO-01273: The specified Oracle home path {0} is already in use by working copy {1} on site {2}.
-
Cause: An attempt to add the specified working copy was rejected because the specified Oracle home path was already in use.
- PRGO-01274: The directory indicated by the specified NFS Oracle home path {0} was not empty on nodes {1}.
-
Cause: An attempt to add the specified working copy was rejected because the working copy will be NFS mounted on the directory specified by the path, making the existing files inaccessible.
- PRGO-01275: failed to verify the emptiness of the specified directory {0} on nodes {1}
-
Cause: An error occurred while attempting to access the specified directory.
- PRGO-01276: failed to delete Rapid Home Provisioning Client (RHPC) because it was running
-
Cause: An attempt to delete a Rapid Home Provisioning Client (RHPC) failed because it was running on the client cluster.
- PRGO-01277: The directory indicated by the specified local Oracle home path {0} was not empty on nodes {1}.
-
Cause: An attempt to add the specified working copy was rejected because a non-empty directory may contain files that belong to other Oracle software homes when the storage type is LOCAL.
- PRGO-01280: The revoke operation failed because role "{0}" is not granted to role "{1}".
-
Cause: An attempt to revoke a role from the grantee role failed because the role had not been granted to the grantee role.
- PRGO-01281: failed to add a working copy because the database version is not compatible with ASM client
-
Cause: An attempt to add a working copy on an ASM client cluster was rejected because the database version was 12.1.0.1 or lower. ASM client access is supported only for database versions 12.1.0.2 or higher.
- PRGO-01282: The '-path' option required for creating a working copy using local storage on an ASM client cluster is not specified.
-
Cause: The attempt to create a working copy using local storage on an ASM client cluster was rejected because the '-path' option was not specified.
- PRGO-01283: Authentication failure while connecting to Rapid Home Provisioning Client (RHPC)
-
Cause: An attempt to connect to the Rapid Home Provisioning Client failed because the connection could not be authenticated.
- PRGO-01284: Rapid Home Provisioning Client "{0}" was never started.
-
Cause: The Rapid Home Provisioning Client daemon did not register its endpoint with the Rapid Home Provisioning Server.
- PRGO-01285: failed to create database "{0}" because the database version {1} does not support the options '-cdb', '-numberOfPDBs' and '-pdbName'
-
Cause: An attempt to add a database was rejected because the database version was 12.1.0.0 or lower. The options '-cdb', '-numberOfPDBs' and '-pdbName' are supported only for database versions 12.1.0.1 or higher.
- PRGO-01286: Option -datafileDestination does not specify the absolute path to create a database of a version before 11.2.
-
Cause: An attempt to create a database of a version before 11.2 failed because the '-datafileDestination' argument was not an absolute path.
- PRGO-01287: failed to move database because the software home path for working copy {0} is shared and the one for working copy {1} is not
-
Cause: An attempt to move a database between Oracle homes was rejected because one Oracle home was shared and the other was not.
- PRGO-01289: failed to move database because the path was not provided for the patched working copy
-
Cause: An attempt to move a database between Oracle homes was rejected because the source working copy is not shared and the path was not provided for the patched working copy.
- PRGO-01290: unable to create snapshot for the database template because maximum number of snapshots has been reached for image "{0}"
-
Cause: An attempt to create a database failed because the maximum number of snapshots had been reached for the image.
- PRGO-01293: Rerun of 'add workingcopy' rejected because -{0} option differs from the one originally specified: {1}.
-
Cause: A rerun of an 'add workingcopy' request failed because one of the options specified did not match the one used originally.
- PRGO-01294: The '-nonrolling' option is required for moving a release 11.1 or earlier database.
-
Cause: The attempt to move a release 11.1 or earlier database was rejected because the '-nonrolling' option was not specified.
- PRGO-01296: failed to get the directory size of path "{0}" during import image of "{1}"
-
Cause: An attempt to determine directory size during import image failed because either the current user or the owner specified does not have read and execute permissions for the specified directory.
- PRGO-01299: failed to move database because the user specified '-path' or '-image' option for an existing patched working copy
-
Cause: An attempt to move database was rejected because the '-path' or '-image' option was specified. The '-path' or '-image' option should not be entered if the patched working copy has been created.
- PRGO-01300: Database "{0}" is not configured in working copy "{1}".
-
Cause: The specified database did not exist in the supplied working copy.
- PRGO-01301: Rapid Home Provisioning Client cluster "{0}" GUID {1} does not match the value stored in repository {2}
-
Cause: An attempt to connect to the Rapid Home Provisioning Server failed because the cluster GUID of the Rapid Home Provisioning Client did not match the cluster GUID stored in the Rapid Home Provisioning Server repository.
- PRGO-01303: The '-pqpool' option is not supported in a non-Exadata environment.
-
Cause: The '-pqpool' option was specified in a non-Exadata environment.
- PRGO-01304: The '-newpqpool' option is not supported in a non-Exadata environment.
-
Cause: The '-newpqpool' option was specified in a non-Exadata environment.
- PRGO-01305: PQ pool is supported only on Flex cluster, this cluster {0} is a regular cluster.
-
Cause: The '-pqpool' option was specified on a regular cluster.
- PRGO-01306: New PQ Pool is supported only on Flex cluster, this cluster {0} is a regular cluster.
-
Cause: The '-newpqpool' option was specified on a regular cluster.
- PRGO-01307: ACFS is not available on PQ nodes.
-
Cause: The ACFS storage type is not available on PQ nodes.
- PRGO-01308: missing '-oraclebase' option for creating the non-existing patched working copy: {0}
-
Cause: An attempt to create a patched working copy was rejected because the '-oraclebase' option required for creating a new working copy was not specified.
- PRGO-01309: Improper '-oraclebase' option specified for existing working copy: {0}.
-
Cause: An attempt to move the databases was rejected because the '-oraclebase' option was specified for an existing patched working copy that does not require it.
- PRGO-01310: failed to move database because the software home path {0} is shared and the one for working copy {1} is not
-
Cause: An attempt to move a database between Oracle homes was rejected because one Oracle home was shared and the other was not.
- PRGO-01311: Invalid value "{0}" specified for the platform option. The valid options are the following:\n{1}
-
Cause: The command was rejected because the value specified for the '-platform option was not a valid OS platform.
- PRGO-01313: failed to move database because the path was not provided for the patched working copy
-
Cause: An attempt to move a database between Oracle homes was rejected because the source working copy is shared and a shared path was not provided for the patched working copy.
- PRGO-01314: An attempt to import image "{0}" failed because the software home specified is for the "{1}" platform, whereas the cluster platform is "{2}".
-
Cause: The software home supplied was for a different platform than the one on cluster.
- PRGO-01315: Database type RacOneNode is not supported in pre-11.2 versions.
-
Cause: An attempt to create a database of type 'RacOneNode' was rejected because database type RacOneNode is not supported in pre-11.2 versions.
- PRGO-01316: The options {0} are not allowed and the '-nodes' option is required for pre 11.2 version database because they cannot be policy-managed.
-
Cause: An attempt to create a policy-managed database failed because only administrator-managed databases are supported in pre 11.2 version.
- PRGO-10211: Invalid option specified when retrieving information for image series
-
Cause: An invalid combination of the '-series', '-image' and '-client' options was specified.
- PRGO-10321: User "{0}" lacks the authority to perform the 'config role' operation.
-
Cause: The user running the 'rhpctl config role' command did not have the required authorization.
- PRGO-10391: User "{0}" lacks the authority to perform the 'config image' operation.
-
Cause: The user running the 'rhpctl config image' command did not have the required authorization.
- PRGO-10461: User "{0}" lacks the authority to query series.
-
Cause: The user running the 'rhpctl query series' command did not have the required authorization.
- PRGO-10481: User "{0}" lacks the authority to perform the 'config working copy' operation.
-
Cause: The user running the 'rhpctl config workingcopy' command did not have the required authorization.
- PRGO-11371: User "{0}" lacks the authority to perform the 'query client' operation.
-
Cause: The user running the 'rhpctl query client' command did not have the required authorization.