Cause: The '-role' option was specified but neither '-user' nor '-grantee' was specified.

Cause: The '-role' option was specified but neither '-user' nor '-grantee' was specified.

Cause: Internal error.

Cause: A 'rhpctl' command was submitted on Rapid Home Provisioning Client.

Cause: While accessing GNS, an attempt to retrieve the host name failed.

Cause: Neither the '-identity' option nor the '-role' option was specified

Cause: Neither the '-identity' option nor the '-role' option was specified

Cause: An invalid combination of the '-series', '-image' and '-client' options was specified.

Cause: An existing working copy of the same name was found when adding a new working copy.

Cause: An existing disk group of the same name was found when adding a new disk group.

Cause: Removal of a disk group failed because the specified disk group was not configured for Rapid Home Provisioning Server.

Cause: Removal of the disk group failed because the specified disk group was in use for data storage by the Rapid Home Provisioning Server.

Cause: The user running the 'rhpctl add role' command did not have the required authorization.

Cause: The user running the 'rhpctl query role' command did not have the required authorization.

Cause: The user running the 'rhpctl delete role' command did not have the required authorization.

Cause: The user running the 'rhpctl grant role' command did not have the required authorization.

Cause: The user running the 'rhpctl revoke role' command did not have the required authorization.

Cause: The user running the 'rhpctl add image' command did not have the required authorization.

Cause: The user running the operation on the image did not have the required authorization.

Cause: The user running the 'rhpctl delete image' command did not have the required authorization.

Cause: The user running the 'rhpctl query image' command did not have the required authorization.

Cause: The user running the 'rhpctl allow image' command did not have the required authorization.

Cause: The user running the 'rhpctl disallow image' command did not have the required authorization.

Cause: The user running the 'rhpctl add series' command did not have the required authorization.

Cause: The user running the 'rhpctl insertimage series' command did not have the required authorization.

Cause: The user running the 'rhpctl delete series' command did not have the required authorization.

Cause: The user running the 'rhpctl deleteimage series' command did not have the required authorization.

Cause: The user running the 'rhpctl query series' command did not have the required authorization.

Cause: The user running the 'rhpctl delete workingcopy' command did not have the required authorization.

Cause: The user running the 'rhpctl query workingcopy' command did not have the required authorization.

Cause: Operations for the Rapid Home Provisioning application were not registered with the managed object server.

Cause: A RHPS name was received when a Rapid Home Provisioning Client (RHPC) name was expected.

Cause: An existing image of the same name was found when adding a new image.

Cause: An existing role of the same name was found when adding a new role.

Cause: An attempt to delete an image series was rejected because the image series contained images.

Cause: An attempt to retrieve the disk group resources failed because no disk group was configured.

Cause: An attempt to connect to Rapid Home Provisioning Server (RHPS) failed, possibly because it was not running.

Cause: An internal error occurred.

Cause: An attempt to delete a working copy failed because the specified working copy had not been created by this Rapid Home Provisioning Client.

Cause: An attempt to add an image to a series failed because the image was already added to the series.

Cause: An attempt to delete an image from a series failed because the image was not found in the series.

Cause: The client was disabled and could not run RHPCTL commands.

Cause: An error occurred while checking if the cluster was enabled.

Cause: The syntax of the '-maproles' option supplied was incorrect.

Cause: While looking up Rapid Home Provisioning Client connection details in GNS, an attempt to retrieve the host name and port number failed.

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.

Cause: An attempt to delete an image failed because there were working copies configured for the image.

Cause: An attempt to remove a role from a user failed because the user does not have that role.

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.

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.

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.

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.

Cause: An attempt to grant READ privilege for the specified image failed because the image state is NEW."

Cause: An attempt to remove READ privilege for the specified image failed because the image state is NEW."

Cause: An attempt to retrieve the owner of the image failed.

Cause: An attempt to retrieve the owner of the working copy failed.

Cause: An error occurred while updating the Rapid Home Provisioning Client's GNS information.

Cause: An attempt to grant a role to a given user failed because the role was already granted to that user.

Cause: An attempt to revoke a role from a given user failed because the role was not granted to that user.

Cause: An attempt was made to create a working copy owned by the root user.

Cause: An attempt to connect to the management database failed because it was not running.

Cause: The '-oraclebase' option was omitted for an image type that requires it.

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.

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.

Cause: The specified '-oraclebase' option value was a non-writable path to the Grid user or cannot be created by the Grid user.

Cause: The check for the existence of the specified path failed on the indicated nodes.

Cause: The specified database resource was already registered in Oracle Clusterware.

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.

Cause: An attempt to add a working copy failed because the specified storage path was not shared among the cluster nodes.

Cause: The requested operation was rejected because the indicated nodes did not exist in the cluster.

Cause: An attempt to create a working copy failed because some or all of the specified nodes are Leaf Nodes.

Cause: The specified server pool was not found.

Cause: An attempt to create a working copy was rejected because the specified server pool has a category with CSS_ACTIVE_ROLE=LEAF.

Cause: The '-pqpool' option was specified for provisioning a database on a target cluster that was not an Oracle Flex Cluster.

Cause: An attempt to create a working copy failed because RHPS does not support the '-newpqpool' and '-pqcardinality' options.

Cause: User equivalence did not exist among the nodes indicated.

Cause: An attempt to create a working copy failed because the user did not exist.

Cause: An attempt to create a working copy failed because the specified storage path is not a directory.

Cause: An attempt to create a working copy failed because the specified storage path did not exist.

Cause: An attempt to delete a role failed because the role has been granted one or more roles.

Cause: An attempt to delete a role failed because the role has been granted to one or more users.

Cause: A Rapid Home Provisioning Client 'rhpctl' command was submitted on the Rapid Home Provisioning Server.

Cause: An attempt to connect to Rapid Home Provisioning Client (RHPC) failed, possibly because it was not running on the remote cluster.

Cause: The supplied database name contained invalid characters.

Cause: A delete client operation failed because one or more working copies exist on the specified client.

Cause: A repository query failed unexpectedly. This is an internal error.

Cause: The user running the 'rhpctl promote image' command did not have the required authorization.

Cause: A request was made to delete a built-in role.

Cause: The user running the 'rhpctl add client' command did not have the required authorization.

Cause: The user running the 'rhpctl add workingcopy' command did not have the required authorization.

Cause: The user running the 'rhpctl query client' command did not have the required authorization.

Cause: The user running the 'rhpctl delete client' command did not have the required authorization.

Cause: The user running the 'rhpctl delete workingcopy' command did not have the required authorization.

Cause: The user running the 'rhpctl modify client' command did not have the required authorization.

Cause: An attempt was made to revoke the built-in GH_SA role from the user of the Oracle Grid Infrastructure home.

Cause: An attempt was made to revoke the built-in GH_CA role from the user of the Oracle Grid Infrastructure home.

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.

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.

Cause: The user running 'rhpctl grant role' command did not have the privilege to 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_CA 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 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.

Cause: An attempt to move the database failed because the source and patched working copy versions are different.

Cause: An attempt to move the database failed because the source and patched working copy owners are different.

Cause: The working copy was not created by this Rapid Home Provisioning Client.

Cause: A 'rhpctl' request was not processed because client authentication failed at the server.

Cause: An internal error occurred.

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.

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.

Cause: The user running the 'rhpctl export client' command did not have the required authorization.

Cause: An attempt to move the database was rejected because the specified source and patched working copies are the same.

Cause: A rhpctl request was not processed because user authentication failed at the server.

Cause: An attempt to create a working copy failed because the maximum number of snapshots has been reached for the image.

Cause: An attempt to create a volume for an import image failed because the configured disk group did not have enough available space.

Cause: An attempt to create a volume failed because the number of tries attempted for generating the volume name was exhausted.

Cause: An attempt to create an image from the working copy failed because the maximum number of snapshots has been reached.

Cause: An attempt to add Rapid Home Provisioning Client failed because the HAVIP resource was not registered with Oracle Clusterware.

Cause: The image created on the Rapid Home Provisioning Server did not contain the templates directory.

Cause: A 'rhpctl add client' command failed because neither GNS server nor GNS client was configured on this cluster.

Cause: An attempt to create or delete a database was rejected because the working copy was not created from an image of type ORACLEDBSOFTWARE.

Cause: An attempt to delete, move, or upgrade the specified database was rejected because the working copy specified was not the one used to create the database.

Cause: An attempt to add a database was rejected because the specified working copy was not provisioned on this cluster.

Cause: An attempt to add a database was rejected because the specified working copy was not created properly.

Cause: The attempt to move database using 'rhpctl move database' was rejected because

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.

Cause: An attempt to move the database failed because the patched working copy was not created from an image of type ORACLEDBSOFTWARE.

Cause: The source working copy was in a partially completed state.

Cause: An attempt to add an image from a working copy was rejected because creation of the specified working copy was not complete.

Cause: No options were specified to modify.

Cause: An attempt to add a working copy from an image was rejected because creation of the specified image was not complete.

Cause: An attempt to move a database from a working copy failed because the specified working copy did not have a database configured.

Cause: An attempt to move a database failed because the source working copy was not created from an image of type 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.

Cause: An attempt to delete a database was rejected because the specified working copy was not provisioned on this cluster.

Cause: An invalid value was specified for the '-storage' option. Either the storage does not exist, or it is not shared.

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.

Cause: An attempt to delete the working copy was rejected because the working copy contained one or more running databases.

Cause: The user did not have the required authorization to run the command.

Cause: An attempt to delete a given user failed because the user owned one or more working copies in the repository.

Cause: An option was supplied which can only be used from a Rapid Home Provisioning Server.

Cause: The '-dbtemplate' option value specified is neither an absolute path nor of the form '<image_name>:<relative_path_of_template>'.

Cause: An error occurred while attempting to export the database template image file system.

Cause: An error occurred while attempting to remove the export file system for the database template image.

Cause: An attempt to export a database template image file system was rejected because creation of the specified image was not complete.

Cause: An attempt to create a database failed because the specified database template path does not exist.

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.

Cause: The value specified for the '-node' option contained multiple nodes.

Cause: An attempt to add a working copy failed because the file system resource of the image supplied was offline.

Cause: An attempt to move the database failed because the source and patched working copies are configured in different clusters.

Cause: An attempt to move a database on a Rapid Home Provisioning Server failed because the '-path' option was specified without remote provisioning.

Cause: Writing the checkpoint for the previous operation failed because the checkpoint file system was offline.

Cause: An attempt to create a local file system failed because a disk group was not configured.

Cause: The working copy could not be added because '-path' option value was on ACFS.

Cause: An attempt to add the indicated image to local storage failed because the source working copy was on local storage or on Rapid Home Provisioning Client ACFS storage.

Cause: The specified path for local storage on the Rapid Home Provisioning Client did not have write access by the user.

Cause: There was insufficient free space on the nodes to copy the working copy.

Cause: An attempt to delete a given user failed because the specified user was a built-in user.

Cause: An attempt to create a single instance database failed because the specified server pool did not have a configured candidate server.

Cause: An attempt to create a single instance database failed because a server pool with maximum size greater than one server was specified.

Cause: An attempt to create a single instance database failed because a server pool with more than one candidate server was specified.

Cause: An attempt to add a working copy was rejected because the specified path duplicates the internal path used to mount the working copy.

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 did not have a configured disk group.

Cause: The image supplied was for a different platform than the one for which the working copy was requested.

Cause: An attempt was made to grant a role to a root user.

Cause: An attempt to disallow the user access from the image failed because the user owned the image.

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.

Cause: An attempt to allow the role access to the image failed because the role was a built-in role associated with the image.

Cause: An attempt was made to grant a role to a built-in role.

Cause: An attempt was made to revoke a role from a built-in 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.

Cause: An attempt to add a role starting with "GH_" failed because "GH_" is a prefix reserved by Oracle for built-in roles.

Cause: An error occurred while attempting to import the indicated image.

Cause: The patched working copy was in a partially completed state.

Cause: One or more Cluster Verification checks for database home provisioning failed.

Cause: An attempt to add the specified database using 'rhpctl add workingcopy' was rejected because the working copy specified was already in existence.

Cause: An error occurred while attempting to access the specified database template file.

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.

Cause: An attempt to create a policy-managed database failed because only administrator-managed databases are supported in pre 11.2 version.

Cause: An attempt to import a version 10.2 image was rejected because the specified Oracle home was not version 10.2.0.5.

Cause: An attempt to import a version 11.1 image was rejected because this version is not supported.

Cause: An attempt to add a database failed because the file system resource of the image containing the working copy supplied was offline.

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.

Cause: An attempt to delete a working copy failed because the file system resource of the image containing the working copy supplied was offline.

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.

Cause: An attempt to move database failed because the file system resource of the image containing the working copy supplied was offline.

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.

Cause: An attempt to add the specified working copy was rejected because the specified Oracle home path was already in use.

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.

Cause: An error occurred while attempting to access the specified directory.

Cause: An attempt to delete a Rapid Home Provisioning Client (RHPC) failed because it was running on the client cluster.

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.

Cause: An attempt to revoke a role from the grantee role failed because the role had not been granted to the grantee role.

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.

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.

Cause: An attempt to connect to the Rapid Home Provisioning Client failed because the connection could not be authenticated.

Cause: The Rapid Home Provisioning Client daemon did not register its endpoint with the Rapid Home Provisioning Server.

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.

Cause: An attempt to create a database of a version before 11.2 failed because the '-datafileDestination' argument was not an absolute path.

Cause: An attempt to move a database between Oracle homes was rejected because one Oracle home was shared and the other was not.

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.

Cause: An attempt to create a database failed because the maximum number of snapshots had been reached for the image.

Cause: A rerun of an 'add workingcopy' request failed because one of the options specified did not match the one used originally.

Cause: The attempt to move a release 11.1 or earlier database was rejected because the '-nonrolling' option was not specified.

Cause: The specified database did not exist in the supplied working copy.

Cause: The '-pqpool' option was specified in a non-Exadata environment.

Cause: The '-newpqpool' option was specified in a non-Exadata environment.

Cause: The attempted operation was rejected because the '-pqpool' option, which is supported only in Oracle Flex Cluster, was specified in the indicated cluster, which was a standard cluster.

Cause: An attempt to create a new parallel query server pool was rejected because the '-newpqpool' option, which is supported only in Oracle Flex Cluster, was specified in the indicated cluster, which was a standard cluster.

Cause: The ACFS storage type is not available on PQ nodes.

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.

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.

Cause: An attempt to move a database between Oracle homes was rejected because the source Oracle home was shared while the destination was not.

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.

Cause: The software home supplied was for a different platform than the one on cluster.

Cause: An attempt to create a database of type 'RacOneNode' was rejected because database type RacOneNode is not supported in pre-11.2 versions.

Cause: An attempt to determine the directory size during import image failed because either the current user or the owner specified did not have read and execute permissions for the specified directory.

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.

Cause: An error occurred while attempting to connect to the Rapid Home Provisioning Client (RHPC).

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.

Cause: The command was rejected because the value specified for the '-platform' option was not a valid OS platform.

Cause: An attempt to move the database failed because the source software home path and patched working copy ownerships are different.

Cause: An attempt to delete or move the specified database was rejected because the software home path was not the one used to create the database.

Cause: An attempt to move a database from a software home path failed because the specified software home path did not have any databases configured.

Cause: An error occurred while validating the platform of the home to be imported.

Cause: An attempt to add a working copy failed because the storage type was specified as RHP_MANAGED for a client without disk groups.

Cause: 1) If "{0}" is an existing pool, it does not have any active servers to host the new database instance. 2) If "{0}" is a new pool to be added, there are no free servers that can be assigned to the new pool.

Cause: The specified pool already exists.

Cause: The command was rejected because the Grid Infrastruture software version is not a valid version for this operation.

Cause: The command was rejected because the Grid Infrastruture could not be provisioned from Rapid Home Provisioning Client.

Cause: The command was rejected because it can only be issued from Rapid Home Provisioning Server (RHPS).

Cause: An incorrect image type was specified for Oracle Grid Infrastructure provisoning.

Cause: An attempt to start moving databases from or to the indicated working copy was rejected because of an ongoing move operation.

Cause: An attempt to resume or abort moving databases from the indicated working copy was rejected because a move operation had not been initiated for the indicated working copy.

Cause: The attempted operation was rejected because the indicated option was not supported for the indicated version of Oracle home.

Cause: An attempt to start moving databases from or to the indicated Oracle home was rejected because of an ongoing move operation.

Cause: An attempt to re-execute 'add workingcopy' was rejected because the specified node list did not contain the indicated local node originally specified. Some operations had already been performed on the local node during the earlier execution, so that node must be included when re-running the command.

Cause: Re-execution of the 'add workingcopy' command failed because the response file contents did not match the one used for the original execution.

Cause: An attempt to upgrade the database was rejected because the specified source and destination working copies were the same.

Cause: An attempt to upgrade a database failed because the source working copy was not created from an image of type ORACLEDBSOFTWARE.

Cause: The working copy was not created by this Rapid Home Provisioning Client.

Cause: An attempt to upgrade a database was rejected because the '-image' option was specified. The '-image' option must not be entered if the destination working copy has been created.

Cause: An attempt to upgrade the database failed because the destination working copy was not created from an image of type ORACLEDBSOFTWARE.

Cause: An attempt to upgrade the database failed because the source and destination working copy versions were incorrect.

Cause: An attempt to upgrade the database failed because the source working copy and destination working copy version were the same.

Cause: An attempt to upgrade the database failed because the destination working copy version was lower than the source working copy version.

Cause: An attempt to upgrade the database failed because the source and destination working copy owners were different.

Cause: An attempt to upgrade the database failed because the source and destination working copies were configured in different clusters.

Cause: The attempt to upgrade the database using 'rhpctl upgrade 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.

Cause: An attempt to upgrade a database failed because the file system resource of the image containing the supplied working copy was offline.

Cause: An attempt to upgrade a database failed because the file system resource in the Rapid Home Provisioning Client containing the supplied working copy was offline.

Cause: The source working copy was in a partially completed state.

Cause: The destination working copy was in a partially completed state.

Cause: An attempt to upgrade a database between Oracle homes was rejected because the source working copy was shared and a shared path was not provided for the destination working copy.

Cause: An attempt to upgrade a database between Oracle homes was rejected because the source Oracle home was shared and the destination Oracle home was not shared.

Cause: An attempt to query working copy information failed because the patch information could not be retrieved from the indicated working copy.

Cause: Image of type SOFTWARE was used for standalone provisioning.

Cause: An attempt to provision software home was rejected because a non-empty directory might have contained files that belonged to other Oracle software homes.

Cause: The specified datafileDestination did not exist.

Cause: A supplied database storage location was not writable by the user.

Cause: An attempt to add a database was rejected because the specified working copy was not provisioned on the specified node.

Cause: An attempt to add a database was rejected because the specified working copy was not provisioned on any standalone node.

Cause: An attempt to add the specified working copy was rejected because the specified Oracle home path was already in use.

Cause: The provided node does not exist.

Cause: The requested standalone provisioning was rejected because credentials required for remote node connection were not provided.

Cause: Credentials were provided for Rapid Home Provisioning.

Cause: An attempt to provision a single instance database on standalone node was rejected because the '-datafileDestination' argument was not an absolute path.

Cause: The user did not exist on one or more nodes as indicated.

Cause: An image with an unsupported version was specified for Oracle Grid Infrastructure provisoning.

Cause: An attempt to locate the specified Oracle Grid Infrastructure response file failed.

Cause: The specified Oracle Grid Infrastructure response file was a directory.

Cause: A value was not specified for the parameter in the response file or command line.

Cause: An invalid parameter was specified in the response file.

Cause: This is an internal error.

Cause: This is an internal error.

Cause: The user running the 'rhpctl subscribe series' command did not have the required authorization.

Cause: The user running the 'rhpctl unsubscribe series' command did not have the required authorization.

Cause: An attempt to unregister the email address of the user was rejected because the user was not registered with an email address.

Cause: An attempt to subscribe a user to a series failed because the user was already subscribed to the series.

Cause: An attempt to unsubscribe a user from a series failed because the user was not subscribed to the series.

Cause: An attempt to register an email address for a user failed because the user was already registered with an email address.

Cause: Rapid Home Provisioning (RHP) failed to send user notifications via the registered email account. Either the account credentials were incorrect or the email server was not reachable.

Cause: The command was rejected because the user did not have a registered email address.

Cause: The user running the 'rhpctl add useraction' command did not have the required authorization.

Cause: An existing user action with the same name was found when adding a new user action.

Cause: The user running the 'rhpctl query useraction' command did not have the required authorization.

Cause: The user running the 'rhpctl delete useraction' command did not have the required authorization.

Cause: An attempt to delete a user action failed because the user action is being used by one or more image types.

Cause: The user running the 'rhpctl add imagetype' command did not have the required authorization.

Cause: An existing image type with the same name was found when adding a new image type.

Cause: One or more of the supplied user actions did not exist in the repository.

Cause: The user running the 'rhpctl delete imagetype' command did not have the required authorization.

Cause: An attempt to delete an image type failed because the image type was being used by one or more images.

Cause: The user running the 'rhpctl modify imagetype' command did not have the required authorization.

Cause: The user running the 'rhpctl allow imagetype' command did not have the required authorization.

Cause: The user running the 'rhpctl disallow imagetype' command did not have the required authorization.

Cause: An attempt to allow access privilege to the user was rejected because the user had already been granted access privilege to the image type using the 'rhpctl allow imagetype' command.

Cause: An attempt to allow the role access to the image type failed because the role was a built-in role associated with the imagetype.

Cause: An attempt to allow access privilege to the role was rejected because the role had already been granted access privilege to the image type using the 'rhpctl allow imagetype' command.

Cause: An attempt to revoke access privilege to the image type failed because the user had never been granted access to the image type using the 'rhpctl allow imagetype' command.

Cause: An attempt to revoke access privilege to the image type failed because the role had never been granted access to the image type using the 'rhpctl allow imagetype' command.

Cause: An attempt to revoke access to the image type failed because the role was a built-in role associated with the image type and was not granted access using the 'rhpctl allow imagetype' command.

Cause: The user running the 'rhpctl query imagetype' command did not have the required authorization.

Cause: The user running the 'rhpctl modify image' command did not have the required authorization.

Cause: An attempt to modify the image type of the image failed because the base type of the target image type did not match the base type or built-in image type of the image.

Cause: Internal error.

Cause: An attempt to delete an image type was rejected because the image type was a built-in image type and was not added using the 'rhpctl add imagetype' command.

Cause: The specified home path does not contain the 'oracle' binary or it is an Oracle Grid Infrastructure home.

Cause: The specified home path for the import image operation does not contain the 'crsd' binary.

Cause: A request to import an image was rejected because the '-pathowner' option was specified for importing the Oracle Database home.

Cause: An attempt to query images was rejected because the '-version' option (or obsolete '-dbversion' option) was specified together with an image type with base type SOFTWARE.

Cause: An attempt to add the image failed because the base type of the target image type did not match the base type of the image type of the working copy image.

Cause: An attempt to delete an image type failed because the image type did not exist.

Cause: The user running the 'rhpctl query imagetype' command did not have the required authorization.

Cause: An attempt to get the image type configuration failed because the image type did not exist.

Cause: An attempt to delete a user action failed because the user action did not exist.

Cause: An attempted 'move database' operation was rejected because the indicated service availability could not have been maintained for the indicated service because it was not running on a sufficient number of instances.

Cause: An attempt to move the Oracle Grid Infrastructure home was rejected because the specified source and destination working copies are the same.

Cause: The Oracle Grid Infrastructure home could not be moved because the working copy was not created by this Rapid Home Provisioning Client.

Cause: The source working copy was in a partially completed state.

Cause: An attempt to move the Oracle Grid Infrastructure home was rejected because the '-path', '-image', or '-aupath' option was specified when there was an existing destination working copy."

Cause: An attempt to move or upgrade the Oracle Grid Infrastructure home failed because the destination working copy (to be created) was not of base image type ORACLEGISOFTWARE.

Cause: An attempt to move the Oracle Grid Infrastructure home failed because the source working copy was not created from an image of base image type ORACLEGISOFTWARE.

Cause: An attempt to move the Oracle Grid Infrastructure home failed because the source and destination working copy versions were different.

Cause: An attempt to move the Oracle Grid Infrastructure home failed because the source and destination working copy owners were different.

Cause: An attempt to move the Oracle Grid Infrastructure home failed because the owner of the source software home path and the destination working copy were different.

Cause: An attempt to move the Oracle Grid Infrastructure home failed because the source and destination working copies were configured in different clusters.

Cause: An attempt to move the Oracle Grid Infrastructure failed because the '-image' option from which to create the new working copy was not specified.

Cause: An attempt to move the Oracle Grid Infrastructure home on the node where Rapid Home Provisoning client was running failed because the last node 'move gihome' actions either failed with an error or timed out.

Cause: The specified option was invalid for a standalone provisioning on cluster version other than 11.2.0.4.

Cause: An attempt to provision a database was rejected because the specified disk group was not configured on the standalone target.

Cause: The requested operation was rejected because the specified node was not part of the nodes on which the working copy was provisioned.

Cause: An attempt to create an administrator-managed database on a cluster whose release is earlier than 12.2 was rejected because the '-node' option was not specified.

Cause: The number of nodes specified for single instance database provisioning was not one.

Cause: The specified target node was part of a cluster that is not managed by Rapid Home Provisioning Server.

Cause: The attempted 'move database' operation was rejected because the indicated option was not supported.

Cause: The attempted 'move database' operation was rejected because the indicated option was not specified.

Cause: An attempt to move or upgrade a database failed because both the source and patched working copies were not Oracle RAC homes.

Cause: An attempt to move or upgrade a single-instance database failed because the source working copy or Oracle home and the patched working copy are on different nodes.

Cause: The attempted 'move database' operation was rejected because the indicated option was not needed.

Cause: The attempted 'move database' operation was rejected because the indicated option was not supported.

Cause: The attempted 'move database' operation was rejected because the indicated option was not supported.

Cause: An attempt to initiate an operation was rejected because an existing operation was currently in progress on the target entity. Only one operation can be in progress at a time on any entity.

Cause: An attempt to add nodes with node roles specified in the '-newnodes' option was rejected because the target cluster was not an Oracle Flex Cluster.

Cause: An attempt to add nodes to a database home or a cluster failed because the '-targetnode' option was not specified for cluster that has no Rapid Home Provisioning (RHP) client

Cause: The attempted 'addnodes' or 'deletenodes' operation was rejected because the base image type of the specified working copy was not ORACLEGISOFTWARE.

Cause: An attempt to add or delete nodes from the indicated working copy failed because it was software-only.

Cause: An attempt to run an operation on the indicated working copy failed because it was incomplete.

Cause: An attempt to provision a working copy was rejected because the client cluster contains Leaf nodes which cannot access ACFS storage.

Cause: An attempt to upgrade the Oracle Grid Infrastructure home failed because the source working copy version is incorrect.

Cause: An attempt to upgrade the Oracle Grid Infrastructure home failed because the destination working copy version is incorrect.

Cause: An attempt to upgrade the Oracle Grid Infrastructure home was rejected because the specified source and destination working copies are the same.

Cause: The Oracle Grid Infrastructure home could not be upgraded because the working copy was not created by this Rapid Home Provisioning Client.

Cause: The source working copy was in a partially completed state.

Cause: The destination working copy was in a partially completed state.

Cause: An attempt to upgrade the Oracle Grid Infrastructure home was rejected because the '-path' or '-image' option was specified when there was an existing destination working copy.

Cause: The user running the 'rhpctl query audit' command did not have the required authorization.

Cause: The user running the 'rhpctl modify audit' command did not have the required authorization.

Cause: The user running the 'rhpctl delete audit' command did not have the required authorization.

Cause: An attempt to delete an active working copy of type ORACLEGISOFTWARE was rejected because no target node was specified.

Cause: The previously submitted command was rejected because the specified node role was invalid.

Cause: The command was rejected because the indicated value supplied as a node specification was invalid.

Cause: An attempt to modify a user action failed because the user action did not exist.

Cause: The operation failed because the indicated user action configured for the image did not execute successfully.

Cause: An attempt to modify an image type failed because the image type did not exist.

Cause: The copy operation failed either because the file system was full or the destination directory did not have write permissions for the specified user.

Cause: An attempt to upgrade a database failed because the indicated database was not registered with the Oracle Clusterware.

Cause: The attempted 'addnodes' or 'deletenodes' operation was rejected because the indicated working copy was an Oracle single-instance database home.

Cause: The attemped operation was rejected because the indicated working copy was not created by the indicated Rapid Home Provisioning Client.

Cause: An attempt to remove the indicated Oracle home software from a set of nodes using the command 'rhpctl deletenodes dbhome' was rejected because the 'deletenodes' operation cannot be used to delete a working copy.

Cause: An attempt to remove the indicated Oracle home software from the indicated nodes failed because databases belonging to the Oracle home have instances running on those nodes.

Cause: An attempted 'addnodes' or 'deletenodes' operation was rejected because the base image type of the specified working copy was not ORACLEDBSOFTWARE.

Cause: An attempt to extend the indicated Oracle RAC home to the indicated nodes failed. The accompanying messages provide detailed failure information.

Cause: An attempt to remove the indicated Oracle RAC home from the indicated nodes failed. The accompanying messages provide detailed failure information.

Cause: The requested operation was rejected because either '-dbname' or '-datafileDestination' was specified without '-node', '-serverpool' or '-newpool'.

Cause: The specified option was invalid for single instance database provisioing.

Cause: The query image command was rejected because -dbtemplate option was only supported for ORACLEDBSOFTWARE images.

Cause: An attempt to delete a working copy of image type ORACLEGISOFTWARE from Rapid Home Provisioning Client was rejected.

Cause: An attempt to delete the Oracle Home directory failed during the cleanup of Oracle Grid Infrastructure. The accompanying messages provide detailed failure information. The 'delete workingcopy' operation completed, but additional action may be needed to complete the cleanup.

Cause: An attempt to detach Oracle Home failed during the cleanup of Oracle Grid Infrastructure. The accompanying messages provide detailed failure information. The 'delete workingcopy' operation completed, but additional action may be needed to complete the cleanup.

Cause: An attempt to delete the snapshot of the image failed during the cleanup of Oracle Grid Infrastructure. The accompanying messages provide detailed failure information. The 'delete workingcopy' operation completed, but additional action may be needed to complete the cleanup.

Cause: An attempt to unmount failed during the cleanup of Oracle Grid Infrastructure. The accompanying messages provide detailed failure information. The 'delete workingcopy' operation completed, but additional action may be needed to complete the cleanup.

Cause: An attempt to execute the command 'rhpctl register user' on behalf of another user failed because the indicated user did not have the required authorization.

Cause: An attempt to execute the command 'rhpctl modify user' on behalf of another user failed because the indicated user did not have the required authorization.

Cause: An attempt to execute the command 'rhpctl unregister user' on behalf of another user failed because the indicated user did not have the required authorization.

Cause: An attempt to move a working copy was rejected because the working copy version was earlier than release 12.2 and the '-targetnode' option was not provided.

Cause: While looking up Rapid Home Provisioning Server connection details, an attempt to query Grid Naming Service (GNS) failed.

Cause: An attempt to retrieve the Oracle release version of the image from an image path using SRVCTL and SQLPLUS failed.

Cause: An attempt to retrieve the Oracle release version of the image from an image path using SQLPLUS failed.

Cause: An error occurred while attempting to connect to the Rapid Home Provisioning Server (RHPS), possibly because the RHPS was not running.

Cause: The requested operation was rejected because clients of versions earlier than 12.2 cannot query working copies based on image type ORACLEGISOFTWARE.

Cause: An attempt to add a software-only working copy was rejected because the client had no Rapid Home Provisioning (RHP) client and no target node was provided. A target node must be specified when adding a software-only working copy on a client that has no RHP client.

Cause: An attempt to add a software-only working copy was rejected because the target node was provided for provisioning on a cluster with an RHP client. The target node must not be specified when adding a software-only working copy on a client that has Rapid Home Provisioning (RHP) client.

Cause: The requested operation was rejected because the indicated node was already a member of an existing Oracle Grid Infrastructure cluster.

Cause: An attempt to provision an Oracle home based on an Oracle Layered File System failed because the directory to store the gold image contents could not be created.

Cause: An attempt to provision an Oracle home based on an Oracle Layered File System failed because the read/write path could not be created.

Cause: A request to add a working copy was rejected because the supplied path was on an ACFS file system managed by the Rapid Home Provisioning application.

Cause: An attempt to provision an Oracle home on an RHPC cluster of version 12.2.0.1 or above was rejected because the '-targetnode' option was specified.

Cause: The '-user' option was missing for standalone provisioning.

Cause: Some patches were present in the source working copy that were missing in the patched working copy.

Cause: An attempt to move the Oracle Grid Infrastructure home was rejected because the client had no Rapid Home Provisioning (RHP) client and no target node was provided. A target node must be specified when moving an Oracle Grid Infrastructure home in a cluster that has no RHP client.

Cause: An attempt to query source home information failed.

Cause: The requested operation was rejected because it was not supported on clients of the indicated version.

Cause: An attempt to move to an Oracle home based on an Oracle Layered File System failed because the specified destination working copy already existed.

Cause: An attempt to move the Oracle Grid Infrastructure home was rejected because the specified destination working copy has more nodes than the source working copy.

Cause: An attempt to upgrade the Oracle Grid Infrastructure home was rejected because the specified destination working copy has more nodes than the source working copy.

Cause: An attempt to move the Oracle Grid Infrastructure home was rejected because the specified source and destination working copies have different sets of nodes.

Cause: An attempt to upgrade the Oracle Grid Infrastructure home was rejected because the specified source and destination working copies have different set of nodes.

Cause: An attempt to provision a database using the indicated disk group was rejected because a disk group cannot be used for provisioning a single instance database on a non-clustered node.

Cause: An attempt to delete an Oracle RAC database home on a cluster that had no Rapid Home Provisioning (RHP) client was rejected because the '-targetnode' option was not specified.

Cause: An attempt to delete an Oracle RAC database home on a cluster that had no Rapid Home Provisioning (RHP) client was rejected because the '-targetnode' option was not specified.

Cause: The '-node' option was specified on an operation that does not need it.

Cause: An attempt to validate the specified cluster name failed as the cluster name supplied was illegal. The supplied cluster name must be at most 15 characters long and can be any combination of lower and uppercase alphanumeric characters, and hyphen.

Cause: An attempt to move to an Oracle home based on an Oracle Layered File System failed because the '-agpath' option was provided when source working copy was already based on an Oracle Layered File System.

Cause: An attempt to move to an Oracle home based on an Oracle Layered File System failed because the '-path' option was provided when source working copy was already based on an Oracle Layered File System.

Cause: An attempt to provision an Oracle home based on an Oracle Layered File System failed because the version of the specified image was earlier than 12.2.

Cause: An attempt to delete nodes from a working copy was rejected because the working copy was provisioned with no Rapid Home Provisioning (RHP) client and no target node was provided. A target node must be specified when deleting nodes from a working copy provisioned with no RHP client.

Cause: An attempt to delete nodes from a working copy was rejected because the target node was provided for a working copy whose release was Oracle Database 12c Release 2 (12.2) or later. The target node must not be specified while deleting nodes from a working copy whose release is Oracle Database 12c Release 2 (12.2) or later.

Cause: An attempt to delete nodes from a working copy was rejected because the specified nodes were not part of the working copy.

Cause: An attempt to delete nodes from a working copy was rejected because all the Hub nodes were present in the specified node list. At least one Hub node should not be specified for deletion while deleting nodes from a working copy.

Cause: An attempt to delete nodes from a working copy was rejected because all of the nodes were present in the specified node list. At least one node should not be specified for deletion while deleting nodes from a working copy.

Cause: An attempt was made to move or upgrade a database without specifying the indicated option.

Cause: An attempt to move a database was rejected because the '-targetnode' option was not needed.

Cause: An attempt to delete the specified working copy with the image type ORACLEGISOFTWARE was rejected because the '-force' option was not valid for the working copy with the image type ORACLEGISOFTWARE.

Cause: An attempt to move or upgrade a database failed because the source working copy was a single-instance Oracle home, but the indicated patched working copy was not.

Cause: An attempt to upgrade the Oracle Grid Infrastructure home failed because the destination working copy version (shown in the message) was not later than the indicated version for the source working copy.

Cause: An attempt to move to an Oracle home based on an Oracle Layered File System failed because the '-aupath' option was not provided when the source working copy was based on an Oracle Layered File System.

Cause: An attempt to move to an Oracle home based on an Oracle Layered File System failed because the '-agpath' option was not provided.

Cause: An attempt to move to an Oracle home based on an Oracle Layered File System failed because the '-path' option was not provided.

Cause: An attempt to add the indicated working copy was rejected because the '-softwareonly' option was supplied and this option is permitted only when adding a working copy from an image of base type ORACLEGISOFTWARE.

Cause: An attempt to move the indicated cluster was rejected because the indicated cluster was not completely moved between the indicated working copies.

Cause: An attempt to move the indicated cluster was rejected because the indicated cluster was not completely moved from the indicated Oracle home to the indicated working copy.

Cause: An attempt to resume or abort moving a cluster to the specified working copy was rejected because a move operation had not been initiated for the specified working copy.

Cause: The attempted 'move' operation was rejected because the specified option was not supported for the indicated cluster version.

Cause: An attempt to provision a working copy with a policy-managed database was rejected because the client cluster contained Leaf Nodes which cannot access ACFS storage managed by Rapid Home Provisioning (RHP).

Cause: An attempt to move or upgrade Oracle Grid Infrastructure was rejected because the '-path' option was not specified. The '-path' option is required for creating the destination working copy as part of an 'rhpctl move gihome' or 'rhpctl upgrade gihome' command operation.

Cause: An attempt to add Oracle Grid Infrastructure working copy was rejected because the '-responsefile' option is required for creating Oracle Grid Infrastructure working copy unless it is software-only provisioning.

Cause: An attempt to move or upgrade the database failed because the source groups and patched working copy groups were different.

Cause: An attempt to move or upgrade the database failed because some of the source groups were not configured in the patched working copy.

Cause: An attempt to move the database failed because some of the patched working copy groups were not configured in the source home.

Cause: An attempt to add nodes to a working copy was rejected because a previously failed 'addnode' operation with the indicated node list was detected, and the specified node list was not a proper subset of the indicated node list, or the '-force' option was not provided.

Cause: An attempt to add nodes to a cluster was rejected because a complete working copy was not found on the specified client.

Cause: An attempt to move or upgrade the Oracle Grid Infrastructure home was rejected because the source groups and patched working copy groups were different.

Cause: An attempt to move or upgrade the Oracle Grid Infrastructure home was rejected because some of the source groups were not configured in the patched working copy.

Cause: An attempt to move the Oracle Grid Infrastructure home was rejected because some of the patched working copy groups were not configured in the Oracle Grid Infrastructure home.

Cause: The attempted 'verify client' operation failed because the disk group name provided in the response file already existed on the target system.

Cause: An attempt to query images was rejected because the '-dbversion' option was specified together with an image type with base type ORACLEGISOFTWARE. The obsolete '-dbversion' option is applicable only with image types with base type ORACLEDBSOFTWARE.

Cause: An attempt to add the indicated working copy was rejected because the '-responsefile' option was supplied and this option is permitted only when adding a working copy from an image of base type ORACLEGISOFTWARE.

Cause: The '-sourcehome' option value specified is not a valid absolute path for the source home.

Cause: An attempt to retrieve the indicated user's group information using the 'id' command failed.

Cause: An attempt to add a working copy was rejected as Oracle Inventory exists on the indicated nodes.

Cause: An attempt to create a working copy on an application cluster was rejected because the '-asmclientdata' option was not specified.

Cause: An attempt to delete nodes from the specified cluster was rejected because the Grid Infrastructure home of that cluster was not deployed by Rapid Home Provisioning (RHP).

Cause: An attempt to import the specified Oracle home as an image failed because it could not be validated that the specified Oracle home on the specified node was of the indicated platform.

Cause: An attempt to subscribe to a series failed because the specified user did not have a registered email address.

Cause: An attempt to move to the specified working copy failed as the specified working copy was not based on an Oracle Layered File System.

Cause: An attempt to add or delete a database instance was rejected because the specified working copy was not provisioned on this Rapid Home Provisioning (RHP) Client.

Cause: An attempt to add or delete an instance of the indicated database was rejected because single-instance databases do not support these operations.

Cause: An attempt to add or delete a database instance was rejected because single-instance databases do not support these operations.

Cause: An attempt to add or delete a database instance was rejected because the base image type of the specified working copy was not ORACLEDBSOFTWARE.

Cause: An attempt to add or delete an instance of the specified database was rejected because the database was not running.

Cause: An attempt to add or delete an instance of the specified database was rejected because these operations are only required for administrator-managed databases.

Cause: An attempt to validate the response file or provision

Cause: The attempted 'addnode' or 'deletenode' operation for an Oracle Grid Infrastructure home was rejected because it is not supported by the Rapid Home Provisioning Client.

Cause: An attempt to perform a rolling patch was rejected because there was only one active Hub Node on the client cluster.

Cause: An attempt to move to the specified working copy failed because it had a different Oracle base from the indicated source working copy.

Cause: An attempt to add a working copy was rejected because the working copy version was less than 12.2 and either the -targetnode was not specified, or the targetnode was specified without the -root or -sudouser option.

Cause: An attempt to add the indicated working copy was rejected because the '-local' option was supplied and this option is permitted only when adding a working copy from an image of base type ORACLEGISOFTWARE.

Cause: The attempted operation was rejected because it was not supported for the indicated version.

Cause: The attempted operation was rejected because it was not supported.

Cause: An attempt to move or upgrade an Oracle Grid Infrastructure working copy was rejected because the indicated working copy was a software-only working copy.

Cause: An attempt to delete instances of the specified database was rejected because 'rhpctl deletenode database' may not be used to delete the last instance of a database.

Cause: An attempt to operate on the specified database was rejected because the specified database does not belong to the specified working copy.

Cause: The command was rejected because the indicated value supplied as a node specification was either more or less than the required information.

Cause: An attempt to import an image was rejected because either -sudouser or -root was specified with -targetnode for a node belonging to a cluster of version 12.2 or higher where the Rapid Home Provisioning Client (RHPC) was enabled.

Cause: An attempt to import an image was rejected because either -sudouser or -root was specified with -targetnode for a node belonging to a cluster of version 12.2 or higher where the Rapid Home Provisioning Client (RHPC) was disabled.

Cause: An attempt to import an image was rejected because either -sudouser or -root was specified with -targetnode for a node belonging to a cluster of version 12.2 or higher, where the Rapid Home Provisioning Client (RHPC) was not configured.

Cause: An attempt to patch Oracle Clusterware was rejected because the indicated node, specified as the first node, was not a Hub Node.

Cause: An attempt to validate the response file or provision

Cause: An error occurred while importing the client cluster certificate.

Cause: An attempt to delete working copy failed during the cleanup of the Oracle Grid Infrastructure. The accompanying messages provide detailed failure information.

Cause: Re-execution of the 'add workingcopy' command failed because the file contents did not match the one used for the original execution.

Cause: An attempt to add nodes to a cluster failed because the cluster was of a version prior to 12.2, and the target node specified was not one of the existing cluster nodes.

Cause: An attempt to move the Oracle Grid Infrastructure home was rejected because the '-continue' option was specified, but the move operation requested was not a batch move or a smart move operation.

Cause: The command was rejected because the indicated node was not a member of the indicated cluster.

Cause: An attempt to add a working copy was rejected because the command was executed specifying the -client option, which was not allowed on a Rapid Home Provisioning Client (RHPC) cluster.

Cause: An attempt to delete a working copy with base image type ORACLEDBSOFTWARE failed because the indicated path did not exist on the indicated nodes.

Cause: An attempt to move to the specified working copy on the Rapid Home Provisioning Client was rejected because both the source and the destination working copies are based on the Oracle Layered File System.

Cause: The Oracle Grid Infrastructure did not allow a Leaf Node to be added as part of this Oracle Cluster configuration because the Grid Naming Service (GNS) was not configured.

Cause: An attempt to create a working copy on an application cluster was rejected because the '-clustermanifest' option was not specified.

Cause: An attempt to add nodes to a cluster failed because the cluster was version 12.2 or later, and the target node option was specified but should not have been.

Cause: An attempt to move a Grid Infrastructure home in a nonrolling manner was rejected because the -targetnode was not specified or the targetnode was specified without the -root or -sudouser option.

Cause: Some patches were present in the source Oracle home that were missing in the patched working copy.

Cause: An attempt to move an Oracle RAC database was rejected because the destination Oracle home contained the indicated patch which was a non-rolling patch, but the '-nonrolling' option was not specified.

Cause: An attempt to set up passwordless SSH user equivalence was rejected because the image was of a version earlier than 12.2.

Cause: An attempt to set up passwordless SSH user equivalence using the '-setupSSH' option of rhpctl was rejected because the required credentials were missing.

Cause: Rapid Home Provisioning pre-check failed on the cluster to be provisioned. The accompanying messages provide detailed failure information.

Cause: Rapid Home Provisioning pre-check failed on the cluster to be provisioned because the nodes did not have passwordless SSH user equivalence for the provisioning user.

Cause: An attempt to export the Rapid Home Provisioning (RHP) schema to the specified file failed because the file already existed.

Cause: The number of nodes specified for a single instance database home provisioning was greater than one.

Cause: An attempt to add the specified user to authorize operations on the Oracle ACFS file system using the indicated volume device encountered a failure. The accompanying messages provide detailed failure information.

Cause: An attempt to copy the specified Oracle home to the given node encountered a failure. The accompanying messages provide detailed failure information.

Cause: An attempt to provision an Oracle home encountered a failure. The accompanying messages provide detailed failure information.

Cause: An attempt to provision an Oracle Grid Infrastructure working copy encountered a failure. The accompanying messages provide detailed failure information.

Cause: An attempt to deconfigure an Oracle Grid Infrastructure cluster encountered a failure. The accompanying messages provide detailed failure information.

Cause: An attempt to add a client encountered a failure. The accompanying messages provide detailed failure information.

Cause: An attempt to add the specified nodes to an Oracle Grid Infrastructure cluster encountered a failure. The accompanying messages provide detailed failure information.

Cause: An attempt to execute a command using the Cluster Verification Utility encountered a failure. The accompanying messages provide detailed failure information.

Cause: An attempt to execute a discover client operation encountered a failure. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade an Oracle Grid Infrastructure cluster encountered a failure. The accompanying messages provide detailed failure information.

Cause: An attempt to move Oracle Grid Infrastructure home from the specified source to the specified destination encountered a failure. The accompanying messages provide detailed failure information.

Cause: An attempt to export the credentials for the specified client encountered a failure. The accompanying messages provide detailed failure information.

Cause: An attempt to retrieve the Rapid Home Provisioning server user encountered a failure. The accompanying messages provide detailed failure information.

Cause: An attempt to retrieve the specified working copy information encountered a failure. The accompanying messages provide detailed failure information.

Cause: An attempt to delete the specified database at the indicated Oracle home location encountered a failure. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade an Oracle RAC database failed because the site version was lower than the destination working copy version.

Cause: An attempt to move databases was rejected because the indicated databases were not completely moved between the indicated working copies.

Cause: An attempt to move databases was rejected because the indicated databases were not completely moved from the indicated Oracle home to the indicated working copy.

Cause: An attempt to move databases was rejected because the '-continue' option was specified, but the move operation requested was not a batch move or a smart move operation.

Cause: The Rapid Home Provisioning pre-check failed with warning messages on the cluster to be provisioned. The accompanying messages provide detailed information.

Cause: An attempt to provision a software-only Oracle Grid Infrastructure working copy with the 'rhpctl add workingcopy' command was rejected because the '-oraclebase' option was supplied incorrectly. The '-oraclebase' option can be supplied only in conjunction with the '-local' option to create a local working copy only when the local node is a member of the Rapid Home Provisioning Server (RHPS) cluster.

Cause: An attempt to delete the indicated working copy was rejected because the home path was different across nodes.

Cause: An attempt to add a client on the target node was rejected because this node was already registered with the Rapid Home Provisioning Server (RHPS) cluster.

Cause: An attempt to provision a software-only Oracle Grid Infrastructure working copy with the 'rhpctl add workingcopy' command was rejected because the '-path' option was missing. The '-path' option is mandatory when the '-local' option is not supplied.

Cause: An attempt to remove the specified node as a candidate server for the specified Oracle RAC One Node database was rejected because the specified database was running on the node.

Cause: An attempt to execute an operation was rejected because the specified option was not allowed on a Rapid Home Provisioning Client (RHPC) cluster.

Cause: An attempt to execute an operation was rejected because the indicated date specification did not conform with the format "yyyy-MM-dd".

Cause: An attempt to delete instances of the indicated database on the indicated nodes failed because that database had no instances configured on those nodes.

Cause: An attempt to run the command 'rhpctl enable osconfig' was rejected because the user did not have root or Administrator privileges.

Cause: An attempt to run the command 'rhpctl disable osconfig' was rejected because the user did not have root or Administrator privileges.

Cause: An attempt to patch Oracle databases in the indicated cluster using the '-auto' option failed because the cluster had no working copy created from an image of type ORACLEDBSOFTWARE.

Cause: An attempt to patch Oracle databases in the indicated cluster using the '-auto' option failed because the specified user input resulted in none of the databases in the cluster being identified as databases which needed to be patched.

Cause: An attempt to patch Oracle databases in the specified cluster using the '-auto' option failed because no database existed in the cluster.

Cause: An attempt to patch Oracle databases using the '-auto' option failed because the pairing of the specified source working copy to the specified patched working copy using the '-dbhomes' option was invalid. The accompanying messages provide more details.

Cause: An attempt to patch Oracle databases using the '-auto' option failed because the pairing of the specified source Oracle home to the specified patched working copy using the '-dbhomes' option was invalid. The accompanying messages provide more details.

Cause: An attempt to perform a patching operation in batch mode on a cluster whose version was earlier than 12.2.0.1 was rejected because one or more of the specified batches contained multiple nodes. Batches containing more than one node was not supported for Grid Infrastructure versions prior to 12.2.0.1.

Cause: An attempt to perform a patching operation in batch mode was rejected because the patching operation had already been completed on the specified batches.

Cause: An attempt to add a working copy for the indicated image type was rejected because an invalid option ('-targetnode') was specified.

Cause: An attempt to move or upgrade a database to the indicated patched working copy was rejected because it did not include the mandatory patches for the indicated bugs.

Cause: All the required groups were not specified in the '-groups' option in the command 'add workingcopy', given the type and version of the image.

Cause: An attempt to validate the response file or provision an Oracle Domain Services Cluster failed because invalid configuration details for the Grid Infrastructure Management Repository disk group were specified in the response file.

Cause: An attempt to validate the response file or provision an Oracle Domain Services Cluster failed because invalid configuration details for the Grid Naming Service were specified in the response file.

Cause: An attempt to provision an Oracle home based on an Oracle Layered File System failed because the storage type specified was not LOCAL.

Cause: Rapid Home Provisioning precheck failed on the cluster that was to be provisioned. The accompanying messages provide detailed failure information.

Cause: An attempt to delete the indicated database using the '-targetnode' option was rejected because there was no instance of that database running on any node.

Cause: An attempt to delete the indicated working copy was rejected because other active Oracle homes were found in the inventory on the remote cluster.

Cause: An attempt to add nodes to a cluster failed because the target node specified was one of the new nodes to be added.

Cause: An attempt to add nodes to a cluster was rejected because the indicated nodes were already part of cluster.

Cause: An attempt to delete an image series failed because there were users subscribed to it.

Cause: An attempt to add a working copy was rejected because node roles were specified when provisioning a non-flex Cluster.

Cause: An attempt to provision a single instance Oracle home on a standalone non-cluster node was rejected because both '-targetnode' and '-node' were specified.

Cause: An attempt to provision an Oracle RAC database failed because the site version was lower than the image version.

Cause: An attempt to provision a working copy on NFS storage was rejected because the target cluster version was not 12.2 or later.

Cause: An attempt to import an image from the specified home failed. The indicated file was either non-existent or was corrupted.

Cause: The preexecution evaluation check for the indicated command showed that some prerequisites of the command were not met. The accompanying messages provide detailed failure information.

Cause: This operation was not supported on the client site of the indicated version.

Cause: An attempt to add a single instance database was rejected because more than one server pool was specified.

Cause: An attempt to add a working copy was rejected because the supplied cluster manifest file was either invalid or was not for the indicated remote cluster.

Cause: An attempt to add a working copy was rejected because the supplied cluster manifest file could not be validated.The accompanying messages provide detailed failure information.

Cause: 1) The path was on Oracle Automatic Storage Management Cluster File System (Oracle ACFS) but the storage type was LOCAL. Or 2) The path was not writable on all of the nodes. Or 3) The path had insufficient free space.

Cause: An attempt to add a workingcopy was rejected because the indicated series had no images.

Cause: The user running the 'rhpctl add workingcopy' command with the '-series' option did not have the required authorization for all of the images in the specified image series.

Cause: The user running the 'rhpctl add workingcopy' command with the '-series' option did not have the required authorization for the image specified.

Cause: An attempt to update an Oracle Database Appliance client encountered a failure. The accompanying messages provide detailed failure information.

Cause: An attempt to update an Oracle Database Appliance client failed because the unpacked patch bundle version was different from the image version.

Cause: An attempt to update an Oracle Database Appliance (ODA) client failed because the unpacked patch bundle version was different on the two nodes.

Cause: An attempt to update an Oracle Database Appliance (ODA) client failed because the ODA cluster did not have two nodes.

Cause: An attempt to update an Oracle Database Appliance (ODA) client failed because the required components were not updated. The accompanying oakcli update command output provides detailed failure information.

Cause: An attempt to update an Oracle Database Appliance client failed because the user interrupted the command.

Cause: An attempt to update an Oracle Database Appliance client failed. The node was down for an unexpected amount of time.

Cause: An attempt to update an Oracle Database Appliance client failed. There was an error while executing the oakcli update command.

Cause: An attempt to update an Oracle Database Appliance (ODA) client was rejected because the indicated ODA patch version was not recognized by Rapid Home Provisioning (RHP).

Cause: An attempt to deploy an Oracle Database Appliance image encountered a failure. The accompanying messages provide detailed failure information.

Cause: An attempt to deploy an Oracle Database Appliance (ODA) image failed because the image path contained files which were not ODA patch zip files.

Cause: An attempt to deploy an Oracle Database Appliance (ODA) image was rejected because an invalid image version was specified.

Cause: An attempt to import the image was rejected because

Cause: An attempt to import an image was rejected because the '-version' option was specified, but is only allowed for images of type ODAPATCHSOFTWARE.

Cause: An attempt to update an Oracle Database Appliance client with the '-batch' option was rejected because the storage components were required to be updated.

Cause: An attempt to update Oracle Database Appliance client failed because the required components were not updated. The accompanying messages provide detailed failure information.

Cause: An attempt to update an Oracle Database Appliance client was rejected because more than one node was specified for the '-batch' option.

Cause: An attempt to run the update Oracle Database Appliance client command for the indicated node failed because another node was not patched successfully.

Cause: An attempt to run the update Oracle Database Appliance client command for this node was rejected because the node had already been patched successfully.

Cause: An attempt to run the update Oracle Database Appliance client command for this node was rejected because an instance of the command without the '-batch' option was already issued for this Oracle database Appliance system and image.

Cause: An attempt to run the update Oracle Database Appliance client command for this node was rejected because an instance of the command with the '-batch' option was already issued for this Oracle database Appliance system and image.

Cause: An attempt to fetch the job details failed because the specified job ID did not exist in the repository.

Cause: The operation was rejected because osconfig was already enabled.

Cause: An osconfig operation was rejected because the user did not have the necessary privileges. The accompanying messages provide detailed failure information.

Cause: An attempt to operate on an osconfig collection was rejected because the specified osconfig was not found.

Cause: An attempt to compare osconfig was rejected because the specified osconfig did not include the specified node.

Cause: An attempt to compare the specified osconfig collection failed. The accompanying messages provide detailed failure information.

Cause: An attempt to restore the osconfig collection failed. The accompanying messages provide detailed failure information.

Cause: An attempt to query the osconfig collection failed. The accompanying messages provide detailed failure information.

Cause: An attempt to backup an osconfig collection failed. The accompanying messages provide detailed failure information.

Cause: The operation was rejected because osconfig was not enabled for the indicated site.

Cause: An attempt to backup an osconfig collection failed. The accompanying messages provide detailed failure information.

Cause: An attempt to create the specified directory failed. The accompanying messages provide detailed failure information.

Cause: An attempt to read or write to the specified file failed. The accompanying messages provide detailed failure information.

Cause: The attempted operation was rejected because it was not supported by the indicated version.

Cause: An attempt to disable osconfig was rejected because osconfig was already disabled.

Cause: An attempt to backup an osconfig collection failed. The accompanying messages provide detailed failure information.

Cause: An attempt to query the peer server was rejected because the indicated name was the name of a Rapid Home Provisioning Client (RHPC), where the name of a peer Rapid Home Provisioning Server (RHPS) was expected.

Cause: An attempt to query the client was rejected because the indicated name was the name of a peer Rapid Home Provisioning Server (RHPS), where the name of a Rapid Home Provisioning Client (RHPC) was expected.

Cause: An attempt to execute the command 'rhpctl query peerserver' was rejected because the indicated user did not have permission.

Cause: An attempt to execute the command 'rhpctl register server' was rejected because the indicated user did not have permission.

Cause: An attempt to create a single instance database was rejected because the indicated node was a Leaf Node.

Cause: An attempt to import an image from the indicated path failed. The indicated extracted directory was not a proper Oracle home.

Cause: An attempt to provision a standalone working copy was rejected because either some of the specified nodes were not configured with Oracle Grid Infrastructure (GI), or they belonged to different clusters.

Cause: An attempt to operate on the specified database was rejected because the specified database did not belong to the specified Oracle home.

Cause: An attempt to upgrade a database with zero downtime was rejected because the specified GoldenGate working copy was incomplete.

Cause: An attempt to upgrade a database with zero downtime was rejected because the version of the specified GoldenGate working copy was not suitable for the indicated Oracle home version.

Cause: An attempt to upgrade a database with zero downtime was rejected because the specified GoldenGate working copy was not owned by the indicated user.

Cause: An attempt to upgrade a database with zero downtime was rejected because the specified GoldenGate working copy was not on an ACFS file system.

Cause: An attempt to upgrade a database with zero downtime was rejected because the database belonged to an Oracle home which was missing mandatory patches. Oracle home version|Minimum patches required -------------------|------------------------------------------------ 11.2.0.4 |11.2.0.4.160419 PSU and patch 24342770 -------------------|------------------------------------------------

Cause: An attempt to upgrade the specified database with zero downtime failed. The accompanying messages provide more details.

Cause: An attempt to upgrade the indicated database with zero downtime was rejected because it does not have services.

Cause: An attempt to upgrade a database with zero downtime was rejected because the destination working copy was missing mandatory patches. Oracle home version|Min. GI version |Minimum patches required -------------------|-----------------|------------------------------ 12.1.0.2 |12.1.0.2 |12.1.0.2.160419 PSU -------------------|-----------------|------------------------------ 12.1.0.2 |12.2.0.1 |12.1.0.2.160419 PSU and | |bugs 21626377,21780146 -------------------|-----------------|------------------------------

Cause: An attempt to upgrade a database with zero downtime failed because the snapshot database was not started. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade the specified database with zero downtime was rejected because it was not the primary database.

Cause: An attempt to upgrade the indicated database with zero downtime was rejected because Rapid Home Provisioning (RHP) could not connect to the database with the SYSDBA system privilege.

Cause: An attempt to upgrade the indicated database with zero downtime was rejected because the database was not open.

Cause: An attempt to upgrade the indicated database with zero downtime was rejected because the database was in backup mode.

Cause: An attempt to upgrade the specified database with zero downtime was rejected because its data files were on an ASM disk group.

Cause: An attempt to upgrade the specified database with zero downtime was rejected because it was not in ARCHIVELOG mode.

Cause: An attempt to upgrade the specified database with zero downtime was rejected because its data files do not exist on ACFS snapshots.

Cause: An attempt to upgrade the indicated database with zero downtime was rejected because the indicated data files were missing.

Cause: An attempt to upgrade the indicated database with zero downtime was rejected because one or more its data files were not on ACFS snapshots.

Cause: An attempt to upgrade the indicated database with zero downtime was rejected because the indicated data files were not online.

Cause: An attempt to upgrade a database with zero downtime was rejected because the indicated Oracle home was not a database home.

Cause: An attempt to upgrade a database to the specified Oracle home with zero downtime was rejected because the home did not exist.

Cause: An attempt to upgrade a database to the indicated Oracle home with zero downtime was rejected because the version of the home could not be retrieved. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime was rejected because the specified destination Oracle home and the source database were of the same version.

Cause: An attempt to upgrade a database with zero downtime was rejected because the specified destination Oracle home was of a lower version than the source database.

Cause: An attempt to upgrade the indicated database with zero downtime was rejected because the current value of the job_queue_processes parameter was less than 4, which was the minimum.

Cause: An attempt to upgrade the indicated database with zero downtime failed because an error occurred while setting up Oracle GoldenGate requirements for the database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade the indicated database with zero downtime failed because an error occurred while adding sequence support to the database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because an ASM Cluster File System (ACFS) snapshot could not be created for the temporary database due to insufficient REDO space.

Cause: An attempt to upgrade a database with zero downtime failed because an ACFS snapshot could not be created for the temporary database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade the indicated database with zero downtime failed because an error occurred while altering the backup mode for the database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because an error occurred while retrieving the archive finish time for the specified database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because an error occurred while retrieving the archive destination ID for the specified database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because an error occurred while creating the control file for the temporary database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because an error occurred while performing recovery for the temporary database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because an error occurred while opening the temporary database with the RESETLOGS option. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because an error occurred while setting temporary table spaces for the temporary database.

Cause: An attempt to upgrade a database with zero downtime failed because an error occurred while setting read-only table spaces for the temporary database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because an error occurred while changing the database ID for the temporary database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because an error occurred while creating the SPFILE for the temporary database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the temporary database could not be added as a Clusterware resource. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the temporary database was missing. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the temporary database was not started. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because an error occurred while checking the status of Oracle GoldenGate. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the status of Oracle GoldenGate was abnormal. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because of an internal error.

Cause: An attempt to upgrade a database with zero downtime failed because an error occurred while creating services for the temporary database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because an error occurred while synchronizing the source and temporary databases using Oracle GoldenGate. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because an error occurred while disabling the indicated database service. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because an error occurred while enabling the indicated database service. The accompanying messages provide detailed failure information.

Cause: An attempt to run the command 'rhpctl recover node' was rejected because the user did not have root or Administrator privileges.

Cause: An attempt to run the command 'rhpctl deploy image' was rejected because the user did not have root or Administrator privileges.

Cause: An attempt to run the command 'rhpctl collect osconfig' was rejected because the user did not have root or sudo privileges.

Cause: An attempt to import the software image was rejected because the directory designated by the indicated path did not contain the 'ggcmd' binary and so could not be an Oracle Golden Gate home.

Cause: An attempt to import an Oracle Golden Gate Home software image was rejected because the directory designated by the indicated path did not contain the Oracle Universal Installer (OUI) inventory file and so could not be an Oracle Golden Gate home.

Cause: An attempt to upgrade a database to the indicated Oracle home with zero downtime was rejected because the database was not configured in an Oracle Grid Infrastructure environment.

Cause: An attempt to upgrade a database with zero downtime on the indicated cluster was rejected because ASM was not running on the cluster.

Cause: An attempt to upgrade the indicated database with zero downtime was rejected because the database was not running.

Cause: An attempt to upgrade the indicated database with zero downtime was rejected because its data files were neither on an ACFS file system nor on an ASM diskgroup.

Cause: An attempt to upgrade the indicated database with zero downtime was rejected because its REDO logs were not on an ACFS file system.

Cause: An attempt to upgrade the indicated database with zero downtime was rejected because its fast recovery area was not on an ACFS file system.

Cause: An attempt to schedule a gold image creation job on the Gold Image As Service (GIAAS) server failed because the supplied Oracle database version identifier was not valid.

Cause: An attempt to schedule a gold image creation job on the Gold Image As Service (GIAAS) server failed because the supplied patch set updates (PSU) version was not a valid Oracle database version.

Cause: An attempt to schedule a gold image creation job on the Gold Image As Service (GIAAS) server failed because the supplied patches string was not a list of valid bug numbers.

Cause: An attempt to download the gold image from the Gold Image As Service (GIAAS) server failed because the specified directory did not have sufficient storage space.

Cause: An attempt to write the gold image archive file failed because the current user did not have write permission for the indicated directory.

Cause: An attempt to schedule a Gold Image As Service (GIAAS) job failed because the GIAAS server returned the indicated error.

Cause: An attempt to schedule a Gold Image As Service (GIAAS) job on the GIAAS server failed because the base image type of the specified image name was not of the type ORACLEGISOFTWARE or ORACLEDBSOFTWARE.

Cause: An attempt to post to the indicated URL failed because of the HTTP error denoted by the indicated status code.

Cause: An attempt to access the indicated URL failed because the HTTP server returned the specified HTTP status code.

Cause: An attempt to post to the indicated URL failed because the HTTP server returned the indicated error.

Cause: An attempt to schedule a Gold Image As Service (GIAAS) job on the GIAAS server failed because because there was no email address configured for the indicated user.

Cause: An attempt to modify the Rapid Home Provisioning (RHP) user failed because the user was not a REST user.

Cause: An attempt to set the Rapid Home Provisioning (RHP) user failed because the user should not be a REST user.

Cause: An attempt to grant or revoke a role for the indicated user failed because the user was a REST user.

Cause: An attempt to modify the indicated REST user was rejected because that user had more privileges than the indicated Rapid Home Provisioning (RHP) user.

Cause: An attempt to upgrade Oracle Grid Infrastructure home failed because the target node was configured with RHPS. RHPS self-upgrade is not supported.

Cause: An attempt to add the indicated working copy was rejected because the '-oraclebase' option was supplied and this option was not permitted when adding a working copy from an image of base type ORACLEGGSOFTWARE.

Cause: An attempt to provision a working copy was rejected because the platform of the software home specified was different from that of the cluster, and the platform-specific files for the target platform were not found in the rhpboot directory.

Cause: An attempt to continue database patching was rejected because a request was previously made to revert the indicated databases, but the revert operation was not completed on all the required nodes.

Cause: An attempt to continue or revert patching for the indicated databases was rejected because the databases were not involved in a move operation.

Cause: An attempt to upgrade the indicated database with zero downtime was rejected because GoldenGate did not fully support the capture process for one or more tables owned by non-Oracle maintained users.

Cause: An attempt to upgrade database with zero downtime failed because a query of view DBA_GOLDENGATE_SUPPORT_MODE failed.

Cause: An attempt to upgrade the indicated database with zero downtime was rejected because the GoldenGate obey file could not be created. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade the indicated database with zero downtime was rejected because the GoldenGate requirements could not be set for the database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime was rejected because the database had data files on an ACFS snapshot, but the ASM Dynamic Volume Manager (ADVM) compatibility attribute for the disk group containing the ACFS was less than 12.1, which meant that a snapshot of the data files could not be created.

Cause: An attempt to upgrade a database with zero downtime was rejected because the database had data files on an ACFS, but the ASM Dynamic Volume Manager (ADVM) compatibility attribute for the disk group containing the ACFS was less than 11.2.0.3.0, which meant that a snapshot of the data files could not be created.

Cause: An attempt to retrieve information about the indicated database was rejected because it was not owned by the indicated user.

Cause: An attempt to perform osconfig retention failed. The accompanying messages provide detailed failure information.

Cause: An attempt to add a working copy from an image was rejected because

Cause: An attempt to replicate the indicated image to the specified client was rejected, because the image was already replicated to the client.

Cause: An attempt to replicate the indicated image to the indicated client was rejected, because the image was incomplete.

Cause: An error occurred while attempting to start the indicated service. The accompanying messages provide detailed failure information.

Cause: An error occurred while attempting to stop the indicated service. The accompanying messages provide detailed failure information.

Cause: An attempt to register a peer server was rejected because the specified server data file was for a different cluster.

Cause: An attempt to delete a scheduled job was rejected because there was no job ID was found in the command arguments.

Cause: An attempt to move to an Oracle home based on an Oracle Layered File System was rejected because the destination workingcopy had the same patches as the source workingcopy, which was also based on an Oracle Layered File System.

Cause: An attempt to find jobs based on the specified conditional arguments failed because no matching jobs were found. This was probably due to invalid conditional arguments.

Cause: An attempt to perform a recover node operation was rejected because the Rapid Home Provisioning (RHP) client was running on the indicated node.

Cause: An attempt to add a pluggable database was rejected because the specified working copy creation was incomplete.

Cause: An attempt to perform the indicated operation failed because the '-targetnode' option was not specified.

Cause: An attempt to download the indicated image failed because the image details for that image were not found in the indicated mapping file.

Cause: An attempt to download an image failed because the indicated mapping file could not be parsed because it was not in valid JSON format.

Cause: An attempt to download the indicated file failed because the indicated path was not valid.

Cause: An attempt to download an archive failed because the indicated directory did not have sufficient storage space.

Cause: An attempt to move or upgrade Oracle Grid Infrastructure was rejected because the specified destination Oracle Grid Infrastructure home did not exist on the indicated cluster nodes.

Cause: An attempt to move to an Oracle home based on an Oracle Layered File System failed because the '-agpath', '-path' option, or both options were not provided.

Cause: An attempt to delete the indicated Rapid Home Provisioning (RHP) user was rejected because it was associated the indicated REST user.

Cause: An attempt to execute a command for the specified client failed because the name specified did not correspond to a Rapid Home Provisioning (RHP) client.

Cause: An attempt to execute a command for the specified server failed because the name specified did not correspond to a peer Rapid Home Provisioning (RHP) server.

Cause: An attempt to move an Oracle Grid Infrastructure home failed because the storage type of the destination working copy was RHP_MANAGED,

Cause: An attempt to deploy an Oracle Database Appliance (ODA) image was rejected because the indicated image zip file contained files which were not ODA patch zip files.

Cause: An attempt to deploy an Oracle Database home image was rejected because the indicated zip file did not contain the Oracle Database binary.

Cause: An attempt to import a Golden Gate home software image was rejected because the indicated zip file did not contain the 'ggcmd' binary.

Cause: An attempt to import an Oracle Golden Gate home software image was rejected because the indicated zip file did not contain the Oracle Universal Installer (OUI) inventory file.

Cause: An attempt to import an Oracle Grid Infrastructure home software image was rejected because the indicated zip file did not contain the 'crsd' binary.

Cause: An attempt to schedule an rhpctl command was rejected because the indicated user did not have the required authorization.

Cause: An attempt to delete a scheduled job was rejected because the indicated user did not have the required authorization.

Cause: An attempt to replicate the indicated image was rejected because it

Cause: An attempt to move a database was rejected because the destination working copy home path was the same as the indicated source home path.

Cause: An attempt to fetch the indicated image from the indicated client failed, because the image was not replicated to the client.

Cause: An attempt to execute the command 'rhpctl unregister server' was rejected because the indicated user did not have permission.

Cause: An attempt to delete a client was rejected because the indicated name was the name of a peer Rapid Home Provisioning Server (RHPS), where the name of a Rapid Home Provisioning Client (RHPC) was expected.

Cause: An attempt to unregister a peer server was rejected because the indicated name was the name of a Rapid Home Provisioning Client (RHPC) where the name of a Rapid Home Provisioning Server (RHPS) was expected.

Cause: An attempt to delete a scheduled job was rejected because the indicated job was a parent job and had one or more child jobs.

Cause: A Rapid Home Provisioning REST request was rejected because the indicated JSON element was not in the expected format.

Cause: A Rapid Home Provisioning REST request was rejected because the body of the request did not conform to the JSON syntax specification.

Cause: A Rapid Home Provisioning REST request was rejected because the request body contained a field name that was not recognized.

Cause: Warning message.

Cause: An attempt to validate the response file or provision an Oracle Cluster failed because invalid configuration details for the Grid Naming Service were specified in the response file.

Cause: An attempt to patch Oracle databases using the '-auto' option was rejected because the specified user input resulted in no database being identified as a database which needed to be moved from the indicated working copy.

Cause: An attempt to patch Oracle databases using the '-auto' option was rejected because the specified user input resulted in no database being identified as a database which needed to be moved from the indicated Oracle home.

Cause: An attempt to deploy an Exadata image failed because the image path contained files which were not Exadata patch zip files.

Cause: An attempt to import an image was rejected because

Cause: An attempt to update an Exadata system encountered a failure. The accompanying messages provide detailed failure information.

Cause: An incorrect image type was specified for Exadata patching.

Cause: An attempt to update Exadata nodes was rejected because

Cause: An attempt to update Exadata nodes failed. There was an error while executing the patchmgr command.

Cause: The requested Exadata patching operation was rejected because root user credentials were required, but were not provided.

Cause: The requested Exadata patching operation was rejected because neither dbnodes, nor cells, nor ibswitches were specified.

Cause: An attempt to deploy an Exadata image was rejected because an invalid image version was specified.

Cause: An attempt to deploy an Exadata image was rejected because the indicated image zip file contained files which were not Exadata patch zip files.

Cause: The requested Exadata patching operation was rejected because the working copy specified did not exist.

Cause: An attempt to modify a Rapid Home Provisioning (RHP) user failed because the indicated RHP user was not valid.

Cause: An attempt to add the indicated name as a Rapid Home Provisioning (RHP) user failed because there was already an existing user with that name.

Cause: An attempt to link the indicated REST user to a Rapid Home Provisioning (RHP) user was rejected because the indicated RHP user was already linked to a different REST user.

Cause: An attempt to add or delete an instance of the indicated database on a leaf node was rejected because the database was administrator managed, and running an admin-managed database on a leaf node was not supported.

Cause: An attempt to provision a software-only GI home based on an Oracle Layered File System was rejected because the '-path' option was supplied erroneously. The '-path' option can be supplied only in conjunction with the '-agpath' option.

Cause: An attempt to validate the response file or provision an Oracle cluster failed because an invalid value for the storage option parameter was specified in the response file.

Cause: An attempt to import a cross-platform image was rejected because the indicated image version was older than the indicated version. Such an import would create binary file incompatibilities and missing binaries under the directory that stores platform-specific files used during provisioning operations.

Cause: An attempt to import an image of the indicated type was rejected to prevent incompatible and missing binaries under the directory that stores platform-specific files used during provisioning operations.

Cause: An attempt to provision an Oracle Grid Infrastructure working copy of version 12.2.0.2 or later was rejected because the mandatory '-path' option was missing.

Cause: An attempt to update Exadata nodes failed. The command output provides detailed failure information.

Cause: An attempt to update Exadata nodes failed because the image specified did not contain the necessary patch files.

Cause: An attempt to update Exadata nodes failed because the format of the specified node list file was invalid.

Cause: An attempt to update Exadata nodes failed because the specified node list file was empty.

Cause: An attempt to update Exadata nodes was rejected because the node specified using the '-fromnode' option was the same as the node to be patched.

Cause: An attempt to replicate the image for the indicated client failed because the specified name did not correspond to a Rapid Home Provisioning (RHP) client.

Cause: An attempt to replicate the image for the indicated server failed because the specified name did not correspond to a peer Rapid Home Provisioning (RHP) server.

Cause: An attempt to move an Oracle home was rejected because the '-tgip' option was specified when the destination working copy had the same patches as the source working copy.

Cause: An attempt to convert a JSON file to a Java object failed. The accompanying messages provide detailed failure information.

Cause: An attempt to convert data to JSON format failed. The accompanying messages provide detailed failure information.

Cause: An attempt to retrieve configuration information failed. The accompanying messages provide detailed failure information.

Cause: An attempt to retrieve configuration information failed. The accompanying messages provide detailed failure information.

Cause: An attempt to process the osconfig collection failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the GoldenGate replication lag did not stabilize for the indicated database.

Cause: The intended operation completed with warning messages. The accompanying messages provide detailed information.

Cause: An attempt to upgrade the indicated database with zero downtime was rejected because its REDO logs were not on an ASM diskgroup.

Cause: An attempt to upgrade the indicated database with zero downtime was rejected because its fast recovery area was not on an ASM diskgroup.

Cause: An attempt to upgrade a database with zero downtime was rejected because the specified backup location does not exist.

Cause: An attempt to upgrade a database with zero downtime was rejected because the indicated diskgroup does not exist.

Cause: An attempt to create the indicated client data file for setting up a Rapid Home Provisioning Client (RHPC) in a remote cluster failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade the indicated database with zero downtime was rejected because the '-clonedatadg' option was not specified.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated database from which it was cloned could not be converted to a RAC database.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated database from which it was cloned could not be converted to a RAC database.

Cause: An attempt to upgrade the indicated database with zero downtime failed because the maximum redo log thread number could not be determined.

Cause: An attempt to upgrade a database with zero downtime failed because a query of DBA_TABLESPACES failed.

Cause: An attempt to connect to a URL using an HTTPS connection failed because the indicated truststore file did not exist.

Cause: An attempt to upgrade, with zero downtime, the database with the indicated instance failed because the database could not be cloned because the password file of the instance could not be duplicated. This is most likely due to incorrect permissions for the file or its parent directory.

Cause: An attempt to register working copies was rejected because the '-oraclebase' option was omitted for an image type that requires it.

Cause: An attempt to register working copies was rejected because the '-oraclebase' option was specified for an image type that does not support it.

Cause: An attempt to register the specified working copy was rejected because an incorrect number of attributes was supplied for it in the attribute file.

Cause: An attempt to upgrade the indicated database with zero downtime was rejected because that operation was not supported for single-instance databases.

Cause: An attempt to set the image policy for the indicated image was rejected because the indicated image name was already associated with a replication policy for the indicated site.

Cause: An attempt to set the image policy for the indicated image series was rejected because the indicated image series name was already associated with a replication policy for the indicated site.

Cause: An attempt to set the image policy for the indicated image type was rejected because the indicated image type name was already associated with a replication policy for the indicated site.

Cause: An attempt to unset the image policy for the indicated image was rejected because the indicated image name was not associated with a replication policy for the indicated site.

Cause: An attempt to unset the image policy for the indicated image series was rejected because the indicated image series name was not associated with a replication policy for the indicated site.

Cause: An attempt to unset the image policy for the indicated image type was rejected because the indicated image type name was not associated with a replication policy for the indicated site.

Cause: An attempt to delete the indicated job failed. The accompanying messages provide detailed failure information.

Cause: An attempt to delete the indicated jobs failed because the job IDs provided were invalid.

Cause: An attempt to delete the indicated jobs failed. The accompanying messages provide detailed failure information.

Cause: An attempt to delete the indicated jobs failed because the indicated jobs were not found.

Cause: An attempt to modify the indicated job failed because the indicated job was not in the TIMER_RUNNING state.

Cause: An attempt to upgrade a database with zero downtime was rejected because the indicated disk group was invalid.

Cause: An attempt to upgrade a database with zero downtime was rejected because the indicated password file required for cloning the database was not found.

Cause: An attempt to upgrade a database with zero downtime was rejected because the database belonged to an Oracle home which was missing mandatory fixes for the indicated bugs.

Cause: An attempt to upgrade a database with zero downtime was rejected because the destination Oracle home was missing mandatory fixes for the indicated bugs.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated clone database could not be started using the MOUNT option.

Cause: An attempt to upgrade a database with zero downtime failed because the redo apply could not be started.

Cause: An attempt to upgrade a database with zero downtime was rejected because the indicated path was not a valid ACFS file system.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated database could not be started.

Cause: An attempt to upgrade a database with zero downtime failed because the role of the indicated database could not be modified.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated database service did not exist.

Cause: An attempt to upgrade a database with zero downtime failed because a query of FLASH_RECOVERY_AREA_USAGE failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade the indicated database with zero downtime was rejected because Flashback Database was not enabled for the database.

Cause: An attempt to upgrade a database with zero downtime using the indicated version 12.2 RHP client was rejected because the RHP client's Grid Infrastructure was missing fixes for the indicated bugs.

Cause: An attempt to upgrade the indicated database failed because Database Upgrade Assistant (DBUA) execution failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a query of FLASHBACK_ON in V$DATABASE failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a query to retrieve Data Guard Broker status failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a query to retrieve the job_queue_processes parameter failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a query of V$RESTORE_POINT failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a SQL statement to drop a restore point failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a SQL statement to create a restore point failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a query of GV$INSTANCE failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a SQL statement to disable CLUSTER_DATABASE failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a query of DATABASE_ROLE in V$DATABASE failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a query of CLUSTER_DATABASE in V$SPPARAMETER failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a query of DATABASE_ROLE in V$DATABASE failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the DBMS_STATS.SET_GLOBAL_PREFS procedure failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a query to verify datatype support for the transient logical standby failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because redo apply could not be started for the indicated standby database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because redo apply could not be stoppped for the indicated standby database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the logs could not be switched for the indicated database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a query of APPLIED_SCN in V$LOGSTDBY_PROGRESS failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a query of CURRENT_SCN in V$DATABASE failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a query of V$RECOVERY_PROGRESS failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a query of V$LOGSTBY_STATE failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated physical standby database could not be converted to a transient logical standby. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because logical standby instantiation could not be started by the DBMS_LOGSTDBY.BUILD procedure. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a query of OPEN_MODE in V$DATABASE failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because indicated database could not be opened. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated transient logical standby database could not be stopped. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the DBMS_LOGSTDBY.APPLY_SET procedure could not set rolling upgrade parameters for the indicated database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated transient logical standby database could not be started. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a query to check for completion of dictionary loading failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a SQL statement to enable CLUSTER_DATABASE failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the DBMS_STATS.GATHER_DICTIONARY_STATS procedure could not gather statistics for dictionary schemas. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated primary database could not be switched to the transient logical standby. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a query of SWITCHOVER_STATUS in V$DATABASE failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because recovery could not be started for the indicated standby database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated transient logical standby database could not be switched to primary. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated database could not be restored to the indicated restore point. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated database could not be switched to physical standby. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a query of SCN in V$RESTORE_POINT failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the _transient_logical_clear_hold_mrp_bit parameter could not be set to true for the indicated database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the control files of the indicated database could not be backed up. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated standby redo log file group could not be added to the indicated standby database and assigned to the indicated thread. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a query to retrieve THREAD# and BYTES from V$LOG failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a query to retrieve the maximum GROUP# from V$LOGFILE failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a query to retrieve the maximum GROUP# from V$STANDBY_LOG failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a query to retrieve the number of redo log members from V$STANDBY_LOG failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated database could not be put into FORCE LOGGING mode. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a query to verify whether media recovery was running for the indicated database failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because media recovery could not be stopped for the indicated database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a query to the existence of a temp file for the indicated database failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because supplemental logging could not be enabled for the indicated database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because change tracking could not be enabled for the indicated database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because Flashback Database could not be enabled for the indicated database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a query of DB_UNIQUE_NAME in V$DATABASE failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a query of V$INSTANCE failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the LOG_ARCHIVE_CONFIG parameter could not be updated for the indicated database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the STANDBY_FILE_MANAGEMENT parameter could not be updated for the indicated database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a query to retrieve parameter LOG_ARCHIVE_DEST of the indicated database failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a query to retrieve parameter FAL_SERVER of the indicated database failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a query to retrieve parameter LOG_ARCHIVE_CONFIG of the indicated database failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because standby parameters could not be set for the indicated primary database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated database service was not running.

Cause: An attempt to upgrade a database with zero downtime failed because the status of the indicated database service could not be determined. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because "srvctl update database" failed for indicated database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the migration of the password file for the indicated database failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated password file could not be copied. This was most likely due to incorrect permissions for the file, its parent directory, or the target directory.

Cause: An attempt to upgrade a database with zero downtime failed because because the ownership of the indicated password file could not be changed as indicated. This was most likely due to missing execute permission for the parent directory of the indicated file.

Cause: An attempt to upgrade a database with zero downtime failed because "srvctl modify database" failed for the indicated database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated ASM Cluster File System (ACFS) snapshot could not be created. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated directory could not be created. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated clone database could not be stopped. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because RMAN could not start the indicated clone database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because RMAN could not backup and restore the SPFILE for the indicated clone database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated clone database could not be registered using 'srvctl add database'. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because an instance could not be modified for the indicated clone database using 'srvctl modify database'. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because "srvctl modify database" failed to modify the resource dependencies for the indicated database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because 'lsnrctl' could not start the indicated auxiliary listener. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because 'lsnrctl' could not stop the indicated auxiliary listener. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade the indicated database with zero downtime was rejected because the database was using Flash Cache, which prevented the creation of a clone database.

Cause: An attempt to upgrade a database with zero downtime failed because an error occurred while disabling the indicated database service. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because an error occurred while enabling the indicated database service. The accompanying messages provide detailed failure information.

Cause: An error occurred while attempting to start the indicated service. The accompanying messages provide detailed failure information.

Cause: An error occurred while attempting to stop the indicated service. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the Managed Recovery Process (MRP) was not running for the indicated database.

Cause: An attempt to upgrade a database with zero downtime failed because an operation timed out. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime was rejected because the number of restore points for the indicated database exceeded the indicated maximum value.

Cause: An attempt to upgrade a database with zero downtime was rejected because the flash recovery area usage by the indicated database exceeded the indicated percentage.

Cause: An attempt to upgrade a database with zero downtime was rejected because Data Guard Broker was active for the indicated database.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated instance of the indicated database could not be stopped using 'srvctl stop instance'. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated instance of the indicated database could not be started using 'srvctl start instance'. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated database could not be stopped using 'srvctl stop database'. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated database could not be started using 'srvctl start database'. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated database was not in the indicated role.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated database was running in maximized protection mode.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated database was not mounted.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated database was not in read/write mode.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated database was in the "OPEN MIGRATE" mode.

Cause: An attempt to upgrade the indicated database with zero downtime was rejected because neither the '-clonedatadg' option nor the '-clonedatafs' option was specified.

Cause: An attempt to upgrade a database with zero downtime was rejected because the indicated ASM Cluster File System (ACFS) did not exist.

Cause: An attempt to open the indicated file failed because the file did not exist or the permissions for the file were incorrect.

Cause: An attempt to upgrade the indicated database with zero downtime was rejected because the Pre-Upgrade Information Tool reported one or more errors.

Cause: An attempt to upgrade the indicated database with zero downtime was rejected because the Pre-Upgrade Information Tool reported one or more warnings.

Cause: An attempt to upgrade the indicated database with zero downtime failed because the SQL statement to run the Pre-Upgrade Information Tool failed. The accompanying messages provide detailed failure information.

Cause: An attempt to replicate the specified image was rejected because the indicated image already existed on the target.

Cause: An existing working copy was found with the same home path while adding a new working copy.

Cause: An attempt to retrieve the full version of the image from the indicated image path using ORAVERSION failed. The accompanying messages provide detailed failure information.

Cause: One or more Cluster Verification Utility (CVU) checks for adding a node failed.

Cause: An attempt to delete the indicated working copy was rejected because it is involved in an ongoing move or upgrade operation.

Cause: An attempt to provision Single-Instance High Availability Grid Infrastructure was rejected because the '-targetnode' option is required for provisioning Single-Instance High Availability Grid Infrastructure.

Cause: The format specified in the preference file was invalid.

Cause: An attempt to upgrade the database failed because the source working copy version was lower than the supported versions for upgrade.

Cause: An 'rhpctl upgrade gihome' command was rejected because neither the Grid Naming Service (GNS) server nor GNS client was configured on this Rapid Home Provisioning (RHP) Server cluster.

Cause: An attempt to register or import an image was rejected because the image type derived from the file specified by '-getfromOSS' option was different from the image type specified by '-imagetype' option.

Cause: An attempt to migrate database to the cloud was rejected because the '-rsp' option is required.

Cause: An attempt to locate the specified Zero downtime migration (ZDM) template file failed.

Cause: The specified template file was a directory.

Cause: An attempt to migrate the specified database with zero downtime failed. The accompanying messages provide more details.

Cause: An attempt to migrate a database with zero downtime failed because starting the REDO APPLY statement failed for the specified standby database. The accompanying messages provide detailed failure information.

Cause: An attempt to migrate a database with zero downtime failed because the indicated standby redo log file group could not be added to the specified standby database and assigned to the indicated thread. The accompanying messages provide detailed failure information.

Cause: An attempt to authenticate input credentials failed.

Cause: An error occurred while trying to retrieve the specified Oracle object storage service container. The accompanying messages provide detailed failure information.

Cause: The specified storage container did not exist.

Cause: An attempt to install the Oracle Storage Service (OSS) cloud backup module failed. The accompanying messages provide detailed failure information.

Cause: An attempt to migrate a database with zero downtime was rejected because the specified disk group did not exist.

Cause: An attempt to migrate the specified database was rejected because it was not in ARCHIVELOG mode.

Cause: An attempt to migrate a database with zero downtime was rejected because the specified path was not a valid Oracle Automatic Storage Management Cluster File System (Oracle ACFS) path.

Cause: An attempt to create the Oracle Storage Service (OSS) cloud backup for the specified database failed. The accompanying messages provide detailed failure information.

Cause: An attempt to create the SPFILE failed. The accompanying messages provide detailed failure information.

Cause: An attempt to modify the database resource using 'srvctl modify database' failed. The accompanying messages provide detailed failure information.

Cause: An attempt to move the database password file failed. The accompanying messages provide detailed failure information.

Cause: An attempt to create the indicated database initialization parameter file failed.

Cause: An attempt to migrate a database with zero downtime failed because the logs could not be switched for the specified database. The accompanying messages provide detailed failure information.

Cause: An attempt to migrate a database with zero downtime failed because a query of the V$RECOVERY_PROGRESS view failed. The accompanying messages provide detailed failure information.

Cause: An attempt to migrate a database with zero downtime failed because a query of the V$LOGSTBY_STATE view failed. The accompanying messages provide detailed failure information.

Cause: An attempt to migrate a database with zero downtime failed because the specified primary database could not be switched to the transient logical standby database. The accompanying messages provide detailed failure information.

Cause: An attempt to migrate a database with zero downtime failed because recovery could not be started for the specified standby database. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated migrate logical standby database could not be switched to the primary database. The accompanying messages provide detailed failure information.

Cause: An attempt to migrate a database with zero downtime failed because a query to verify whether media recovery was running for the standby database failed. The accompanying messages provide detailed failure information.

Cause: An attempt to create the database password file failed. The accompanying messages provide detailed failure information.

Cause: An attempt to migrate a database with zero downtime failed because the ownership of the password file could not be changed as specified. This was most likely due to missing execute permission for the parent directory of the indicated file.

Cause: An attempt to migrate a database with zero downtime failed because the indicated clone database could not be registered. The accompanying messages provide detailed failure information.

Cause: An attempt to migrate a database with zero downtime failed because restoration of the control files and database files failed. The accompanying messages provide detailed failure information.

Cause: An attempt to migrate a database with zero downtime failed because a query of DBA_TABLESPACES failed.

Cause: An attempt to migrate a database with zero downtime failed because Oracle Real Application Clusters (Oracle RAC) was not enabled for the specified database.

Cause: An attempt to migrate a database with zero downtime failed because stopping the REDO APPLY statement failed for the specified database. The accompanying messages provide detailed failure information.

Cause: An attempt to migrate a database with zero downtime failed because a query to enable supplemental logging failed for the specified standby database. The accompanying messages provide detailed failure information.

Cause: An attempt to migrate a database with zero downtime failed because the execution of the statement to convert the specified database as PHYSICAL STANDBY failed. The accompanying messages provide detailed failure information.

Cause: An attempt to migrate a database with zero downtime failed because the execution of the statement to enable force logging for the specified database failed. The accompanying messages provide detailed failure information.

Cause: An attempt to migrate the specified database with zero downtime failed because the operation to add the indicated log file failed.

Cause: An attempt to migrate the specified database with zero downtime failed because the operation to enable the indicated thread number failed.

Cause: An attempt to migrate the specified database with zero downtime failed because the operation to create the indicated undo tablespace failed.

Cause: An attempt to migrate a database with zero downtime failed because a query of $BLOCK_CHANGE_TRACKING failed. The accompanying messages provide detailed failure information.

Cause: An attempt to migrate a database with zero downtime failed because the query to enable block change tracking failed for the specified database. The accompanying messages provide detailed failure information.

Cause: An attempt to migrate a database with zero downtime failed because the query to enable flashback mode failed for the specified database. The accompanying messages provide detailed failure information.

Cause: An attempt to migrate a database with zero downtime failed because the update of the primary database failed during the standby database registration. The accompanying messages provide detailed failure information.

Cause: An attempt to create the Oracle Storage Service (OSS) cloud backup for the specified database failed. The accompanying messages provide detailed failure information.

Cause: An attempt to create the Oracle Storage Service (OSS) cloud backup for the specified database failed. The accompanying messages provide detailed failure information.

Cause: An attempt to create the Oracle Storage Service (OSS) cloud backup for the specified database failed. The accompanying messages provide detailed failure information.

Cause: An attempt to create the Oracle Storage Service (OSS) cloud backup for the specified database failed. The accompanying messages provide detailed failure information.

Cause: An attempt to migrate a database with zero downtime failed because the operation to open the specified database with resetlogs failed. The accompanying messages provide detailed failure information.

Cause: An attempt to migrate a database with zero downtime failed because the operation to set the indicated parameter to the indicated value for the specified database failed. The accompanying messages provide detailed failure information.

Cause: An attempt to migrate a database with zero downtime failed because the operation to set the indicated parameter for the specified database failed. The accompanying messages provide detailed failure information.

Cause: An attempt to migrate a database with zero downtime failed because the operation to reset the indicated parameter for the specified database failed. The accompanying messages provide detailed failure information.

Cause: An attempt to migrate a database with zero downtime failed because the operation to query the indicated parameter from the indicated view for the specified database failed. The accompanying messages provide detailed failure information.

Cause: An attempt to migrate a database with zero downtime failed because the indicated directory could not be created. The accompanying messages provide detailed failure information.

Cause: An attempt to migrate a database with zero downtime failed because the ownership of the specified file could not be changed as indicated. This was most likely due to missing execute permission for the parent directory of the indicated file.

Cause: An attempt to migrate a database with zero downtime failed because the operation to query the indicated details from the indicated view for the specified database failed. The accompanying messages provide detailed failure information.

Cause: An attempt to revert the Oracle Grid Infrastructure home was rejected because zero impact patching cannot be performed during the revert operation.

Cause: An attempt to migrate the specified database with zero downtime failed because the operation to create the indicated PFILE from the SPFILE failed.

Cause: An attempt to copy the indicated file failed. The accompanying messages provide detailed failure information.

Cause: An attempt to open the specified directory failed.

Cause: An attempt to upgrade a database with zero downtime failed because the operation to enable the specified thread number for specified database failed.

Cause: An attempt to upgrade a database with zero downtime failed because a query to retrieve BYTES from V$LOG for the specified database failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because a query to retrieve the maximum GROUP# from V$LOG for specified database failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the indicated redo log file group could not be added to the specified database and assigned to the indicated thread. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade a database with zero downtime failed because the specified standby database was unexpectedly missing.

Cause: An attempt to upgrade the specified database with zero downtime was rejected because it did not have enabled services.

Cause: An attempt to perform the operation the with indicated option was rejected because the Rapid Home Provisioning (RHP) client was running on the indicated node.

Cause: An attempt to provision an Oracle Grid Infrastructure working copy of version earlier than release 12.2.0.2 was rejected because the mandatory 'ORACLE_HOME' parameter was missing or empty in the specified response file.

Cause: An attempt to upgrade a database with zero downtime failed because a query of the log_archive_dest parameter failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade the specified database with zero downtime was rejected because the database does not have the required Oracle GoldenGate RDBMS patches.

Cause: The requested upgrade Oracle Grid Infrastructure operation was rejected because the specified site was not a Rapid Home Provisioning (RHP) client, and the credentials required for remote node connection were not provided.

Cause: An attempt to re-create a client was rejected because there were working copies configured for it.

Cause: An attempt to upgrade a database with zero downtime failed because a query to retrieve the PROCESSES parameter failed. The accompanying messages provide detailed failure information.

Cause: An attempt to upgrade the indicated database with zero downtime was rejected because the current value of the PROCESSES parameter was less than 500, which was the minimum.

Cause: An attempt to resume the specified job was rejected because the specified job was not in the PAUSED state.