123 PRGR-00100 to PRGR-00173
- PRGR-00100: The specified state "{0}" is invalid.
-
Cause: An incorrect image state was specified.
- PRGR-00101: The specified privilege "{0}" is invalid.
-
Cause: An incorrect privilege name was sepcified.
- PRGR-00102: Failed to connect to repository database "{0}": {1}
-
Cause: An attempt to establish a database connection for the Grid Infrastructure Management Repository database failed.
- PRGR-00103: The repository object already exists in the database : \n{0}
-
Cause: An attempt was made to store a repository object to the database when it was already present in it.
- PRGR-00104: The database connection context is in incorrect state and therefore cannot be written to the database.
-
Cause: The connection to the database may have been closed.
- PRGR-00105: Illegal argument passed to the entity manager.
-
Cause: An illegal argument was passed to an entity manager operation.
- PRGR-00106: Storing this repository object requires a transaction but no transaction exists.
-
Cause: Internal error.
- PRGR-00107: Failed to close database connection context.
-
Cause: An attempt to close database connection context for repository failed.
- PRGR-00108: Failed to get current OS user.
-
Cause: An attempt to get current OS user failed.
- PRGR-00109: Invalid repository object version "{0}".
-
Cause: The repository object had previously been stored with invalid version.
- PRGR-00110: Repository object "{0}" of class "{1}" does not exist.
-
Cause: The specified repository object does not exist in the repository database.
- PRGR-00111: The site type specified "{0}" is invalid; allowed values are "{1}".
-
Cause: An invalid site type was specified.
- PRGR-00112: Failed to get current cluster name.
-
Cause: An attempt to get the current cluster name failed.
- PRGR-00113: Invalid access control entry type specified.
-
Cause: The access control entry type can only be USER or ROLE, but an invalid type was specified.
- PRGR-00114: Image "{0}" does not exist.
-
Cause: An attempt to fetch the specified image from the repository failed because the object does not exist in the repository.
- PRGR-00115: Image series "{0}" does not exist.
-
Cause: An attempt to fetch the specified image series from the repository failed because the object does not exist in the repository.
- PRGR-00116: User "{0}" does not exist.
-
Cause: An attempt to fetch the specified user from the repository failed because the object does not exist in the repository.
- PRGR-00117: Role "{0}" does not exist.
-
Cause: An attempt to fetch the specified role from the repository failed because the object does not exist in the repository.
- PRGR-00118: Working copy "{0}" does not exist.
-
Cause: An attempt to fetch the specified working copy from the repository failed because the object does not exist in the repository.
- PRGR-00119: Site "{0}" does not exist.
-
Cause: An attempt to fetch the specified site data from the repository failed because the object does not exist in the repository.
- PRGR-00120: Failed to get an image name.
-
Cause: An internal error occurred.
- PRGR-00121: Image {0} was not found in this series. Make sure the series and image names are correct.
-
Cause: The specified image name was not found in the image list of the series.
- PRGR-00122: The specified image type "{0}" has an invalid base type.
-
Cause: An incorrect image type was specified.
- PRGR-00123: Image "{0}" already exists.
-
Cause: An attempt to add the specified image to the repository failed because the object already exists in the repository.
- PRGR-00124: Image series "{0}" already exists.
-
Cause: An attempt to add the specified image series to the repository failed because the object already exists in the repository.
- PRGR-00125: User "{0}" already exists.
-
Cause: An attempt to add the specified user to the repository failed because the object already exists in the repository.
- PRGR-00126: Role "{0}" already exists.
-
Cause: An attempt to add the specified role to the repository failed because the object already exists in the repository.
- PRGR-00127: Working copy "{0}" already exists.
-
Cause: An attempt to add the specified working copy to the repository failed because the object already exists in the repository.
- PRGR-00128: Site "{0}" already exists.
-
Cause: An attempt to add the specified site to the repository failed because the object already exists in the repository.
- PRGR-00129: Invalid holder type "{0}" specified, allowed values are "{1}"
-
Cause: This is an Oracle internal error.
- PRGR-00130: Invalid ACE string: "{0}"
-
Cause: This is an internal error.
- PRGR-00131: Failed to access the database: {0}
-
Cause: An attempt to access the Grid Infrastructure Management Repository database failed.
- PRGR-00132: Client cluster name {0} is the same as the Rapid Home Provisioning Server cluster name.
-
Cause: An attempt to add the specified client cluster to the repository failed because the client cluster name is the same as the Rapid Home Provisioning Server cluster name.
- PRGR-00133: failed to retrieve the platform information from the specified Oracle home path "{0}"
-
Cause: An error occurred while attempting to retrieve the platform information.
- PRGR-00134: failed to execute the requested command to act on the Rapid Home Provisioning repository because the Rapid Home Provisioning Server is running
-
Cause: A request to act on the Rapid Home Provisioning repository was rejected because this requires the Rapid Home Provisioning Server to be stopped.
- PRGR-00136: invalid version "{0}" specified
-
Cause: The version specified was an invalid version from which to upgrade.
- PRGR-00137: failed to upgrade objects of type {0} due to the following errors:\n{1}
-
Cause: An attempt to upgrade the objects of the mentioned type failed.
- PRGR-00138: failed to get a user name
-
Cause: An internal error occurred.
- PRGR-00139: User action "{0}" already exists.
-
Cause: An attempt to add the specified user action to the repository failed because an action with that name already exists.
- PRGR-00140: User action "{0}" does not exist.
-
Cause: An attempt to fetch the specified user action from the repository failed because the object did not exist in the repository.
- PRGR-00141: Image type "{0}" already exists.
-
Cause: An attempt to add the specified image type to the repository failed because the image type already existed in the repository.
- PRGR-00142: Image type "{0}" does not exist.
-
Cause: An attempt to fetch the specified image type from the repository failed because the object did not exist in the repository.
- PRGR-00143: The specified operation type "{0}" is invalid.
-
Cause: The specified operation type was not supported by user actions in Rapid Home Provisioning.
- PRGR-00144: failed to modify the audit record limit because the number of written records is higher than the limit provided
-
Cause: An attempt to modify the audit record limit failed.
- PRGR-00145: The specified run scope "{0}" is invalid.
-
Cause: An invalid value was specified for the '-runscope' parameter.
- PRGR-00146: The value specified for 'onerror' "{0}" is invalid.
-
Cause: An invalid value was specified for the '-onerror' parameter.
- PRGR-00147: The starting date specified {0} for an audit query is later than the ending date specified {1}.
-
Cause: An audit query specified an invalid date range.
- PRGR-00152: Client "{0}" already exists.
-
Cause: An attempt to add the indicated client failed because that client already existed.
- PRGR-00153: The policy type "{0}" is invalid.
-
Cause: An attempt to create a policy was rejected because the specified policy type was invalid.
- PRGR-00154: failed to export or import the RHP repository
-
Cause: An attempt to export or import the Rapid Home Provisioning (RHP) repository failed. The accompanying messages provide detailed failure information.
- PRGR-00170: Client "{0}" does not exist.
-
Cause: An attempt to delete a client failed because the indicated client was not found in the repository.
- PRGR-00171: failed to update working copy drift metadata in the repository for client "{0}"
-
Cause: An attempt to update the working copy drift metadata for the indicated client encountered a failure. The accompanying messages provide detailed failure information.
- PRGR-00172: failed to fetch working copy drift metadata for client "{0}"
-
Cause: An attempt to update the working copy drift metadata for the indicated client encountered a failure. The accompanying messages provide detailed failure information.
- PRGR-00173: Credential "{0}" does not exist.
-
Cause: An attempt to fetch the specified credential from the repository failed because the object did not exist in the repository.