PRGO-01003 to PRGO-17731

125 PRGO-01003 to PRGO-17731

PRGO-01003: Invalid option specified when granting a role to a client user or another role: Cause: The '-role' option was specified but neither '-user' nor '-grantee' was specified.; Action: Supply the '-user' option or the '-grantee' option when running 'rhpctl grant role' with '-role' option.
PRGO-01004: Invalid option specified when revoking a role from client user or another role: Cause: The '-role' option was specified but neither '-user' nor '-grantee' was specified.; Action: Supply the '-user' option or '-grantee' option when running 'rhpctl revoke role' with '-role' option.
PRGO-01005: Invalid container type "{0}": Cause: Internal error.; Action: Contact Oracle Support Services.
PRGO-01006: An unsupported 'rhpctl' command was issued on Rapid Home Provisioning Client.: Cause: A 'rhpctl' command was submitted on Rapid Home Provisioning Client.; Action: Run the 'rhpctl' command on Rapid Home Provisioning Server.
PRGO-01007: Unable to retrieve Rapid Home Provisioning Server host name: Cause: While accessing GNS, an attempt to retrieve the host name failed.; Action: Make sure that both the GNS and the Rapid Home Provisioning Server are running.
PRGO-01019: Invalid option specified when adding visibility to an image for either client user or role: Cause: Neither the '-identity' option nor the '-role' option was specified; Action: Supply the '-identity' option or the '-role' option when running 'rhpctl allow image'.
PRGO-01020: Invalid option specified when removing visibility from an image for either client user or role: Cause: Neither the '-identity' option nor the '-role' option was specified; Action: Supply the '-identity' option or the '-role' option when running 'rhpctl disallow image'.
PRGO-01021: Invalid option specified when retrieving information for image series: Cause: An invalid combination of the '-series', '-image' and '-client' options was specified.; Action: Supply the correct combination of the '-series', '-image' and '-client' options when running 'rhpctl query series'. Only the following combinations are allowed: 1) no option 2) -client option only 3) -image option only 4) -series option only 5) -series and -client options only
PRGO-01022: Working copy "{0}" already exists.: Cause: An existing working copy of the same name was found when adding a new working copy.; Action: Supply another working copy name or delete the working copy and retry.
PRGO-01028: Disk group "{0}" already exists.: Cause: An existing disk group of the same name was found when adding a new disk group.; Action: Supply another disk group name and retry the operation.
PRGO-01029: Disk group "{0}" does not exist.: Cause: Removal of a disk group failed because the specified disk group was not configured for Rapid Home Provisioning Server.; Action: Supply the name of a disk group that is configured for Rapid Home Provisioning Server.
PRGO-01030: Disk group "{0}" is in use.: Cause: Removal of the disk group failed because the specified disk group was in use for data storage by the Rapid Home Provisioning Server.; Action: Supply another disk group and retry the operation.
PRGO-01031: User "{0}" lacks the authority to perform the 'add role' operation.: Cause: The user running the 'rhpctl add role' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01032: User "{0}" lacks the authority to perform the 'query role' operation.: Cause: The user running the 'rhpctl query role' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01033: User "{0}" lacks the authority to perform the 'delete role' operation.: Cause: The user running the 'rhpctl delete role' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01034: User "{0}" lacks the authority to perform the 'grant role' operation.: Cause: The user running the 'rhpctl grant role' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01035: User "{0}" lacks the authority to perform the 'revoke role' operation.: Cause: The user running the 'rhpctl revoke role' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01036: User "{0}" lacks the authority to perform the 'add image' operation.: Cause: The user running the 'rhpctl add image' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01037: User "{0}" lacks the authority to perform operation '{1}'.: Cause: The user running the operation on the image did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01038: User "{0}" lacks the authority to perform the 'delete image' operation.: Cause: The user running the 'rhpctl delete image' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01039: User "{0}" lacks the authority to perform the 'query image' operation.: Cause: The user running the 'rhpctl query image' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01040: User "{0}" lacks the authority to grant viewing access to image "{1}".: Cause: The user running the 'rhpctl allow image' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01041: User "{0}" lacks the authority to disallow viewing access to image "{1}".: Cause: The user running the 'rhpctl disallow image' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01042: User "{0}" lacks the authority to add a new series.: Cause: The user running the 'rhpctl add series' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01043: User "{0}" lacks the authority to add an image to a series.: Cause: The user running the 'rhpctl insertimage series' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01044: User "{0}" lacks the authority to delete a series.: Cause: The user running the 'rhpctl delete series' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01045: User "{0}" lacks the authority to delete an image from a series.: Cause: The user running the 'rhpctl deleteimage series' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01046: User "{0}" lacks the authority to view series.: Cause: The user running the 'rhpctl query series' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01047: User "{0}" lacks the authority to perform the 'delete workingcopy' operation.: Cause: The user running the 'rhpctl delete workingcopy' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01048: User "{0}" lacks the authority to perform the 'query workingcopy' operation.: Cause: The user running the 'rhpctl query workingcopy' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01049: Rapid Home Provisioning operations cannot be registered with the managed object server.: Cause: Operations for the Rapid Home Provisioning application were not registered with the managed object server.; Action: Ensure that the management database is up and running and either the Rapid Home Provisioning Server or the Rapid Home Provisioning Client resource is registered with CRSD.
PRGO-01058: The client name "{0}" supplied is a Rapid Home Provisioning Server (RHPS).: Cause: A RHPS name was received when a Rapid Home Provisioning Client (RHPC) name was expected.; Action: Provide only RHPC names to the command.
PRGO-01059: Image "{0}" already exists.: Cause: An existing image of the same name was found when adding a new image.; Action: Supply another image name or delete the existing image and retry.
PRGO-01060: Role "{0}" already exists.: Cause: An existing role of the same name was found when adding a new role.; Action: Supply another role name or delete the existing role and retry.
PRGO-01062: Unable to remove image series "{0}" because it contains images and the '-force' option was not specified.: Cause: An attempt to delete an image series was rejected because the image series contained images.; Action: Either specify the '-force' flag, or delete all images in the image series before attempting to delete the image series.
PRGO-01067: No disk group has been configured for Rapid Home Provisioning Server.: Cause: An attempt to retrieve the disk group resources failed because no disk group was configured.; Action: Use the 'rhpctl add diskgroup' command to add a disk group and retry the command.
PRGO-01068: Failed to connect to Rapid Home Provisioning Server (RHPS): Cause: An attempt to connect to Rapid Home Provisioning Server (RHPS) failed, possibly because it was not running.; Action: Start Rapid Home Provisioning Server (RHPS) using 'srvctl start rhpserver' and retry the command.
PRGO-01069: Internal error [# {0} #].: Cause: An internal error occurred.; Action: Contact Oracle Support Services.
PRGO-01070: Working copy "{0}" cannot be deleted from Rapid Home Provisioning Client cluster "{1}".: Cause: An attempt to delete a working copy failed because the specified working copy had not been created by this Rapid Home Provisioning Client.; Action: Execute the command from the cluster that created this working copy or specify a working copy that was created on this client cluster.
PRGO-01071: Image "{0}" already exists in the series "{1}".: Cause: An attempt to add an image to a series failed because the image was already added to the series.; Action: Supply another image name or delete the existing image and retry.
PRGO-01072: Image "{0}" does not exist in the series "{1}".: Cause: An attempt to delete an image from a series failed because the image was not found in the series.; Action: Supply an existing image name and retry.
PRGO-01073: Rapid Home Provisioning Client "{0}" is disabled.: Cause: The client was disabled and could not run RHPCTL commands.; Action: Contact the Rapid Home Provisioning Server site administrator to enable the client.
PRGO-01074: failed while checking if cluster "{0}" is enabled to run RHPCTL commands: Cause: An error occurred while checking if the cluster was enabled.; Action: Examine the accompanying errors for more information.
PRGO-01076: Incorrect syntax in the '-maproles' option: "{0}": Cause: The syntax of the '-maproles' option supplied was incorrect.; Action: Modify the '-maproles' argument to use the following syntax and retry the command: 'role=username[+username...][,role=username[+username...]...]'.
PRGO-01077: Failed to retrieve Rapid Home Provisioning Client host name and port number: Cause: While looking up Rapid Home Provisioning Client connection details in GNS, an attempt to retrieve the host name and port number failed.; Action: Ensure that both the GNS and the Rapid Home Provisioning Client are running.
PRGO-01078: Failed to retrieve Rapid Home Provisioning Server host name and port number: Cause: While looking up Rapid Home Provisioning Server connection details in Grid Naming Service (GNS), an attempt to retrieve the host name and port number failed.; Action: Ensure that both the GNS and the Rapid Home Provisioning Server are running on the RHPS cluster.
PRGO-01079: Failed to remove image "{0}" because working copies "{1}" have been configured for this image.: Cause: An attempt to delete an image failed because there were working copies configured for the image.; Action: Use the 'rhpctl remove workingcopy' command to remove associated working copies and retry the command.
PRGO-01081: User "{0}" does not have the role "{1}". The list of roles that the user has is:\n{2}: Cause: An attempt to remove a role from a user failed because the user does not have that role.; Action: Check the arguments supplied and retry the command.
PRGO-01082: User "{0}" for cluster "{1}" was already allowed access to image {2}.: Cause: An attempt to allow access privilege to the user was rejected because the user had already been granted access privilege to the image using the 'rhpctl allow image' command.; Action: Ensure the correct user was specified.
PRGO-01083: Role "{0}" was already allowed access to image "{1}".: Cause: An attempt to allow access privilege to the role was rejected because the role had already been granted access privilege to the image using the 'rhpctl allow image' command.; Action: Ensure the correct role was specified.
PRGO-01084: User "{0}" for cluster "{1}" has never been granted access to image {2}.: Cause: An attempt to disallow the user from access privilege to the image failed because the user had never been granted access privilege to the image using the 'rhpctl allow image' command.; Action: Use the 'rhpctl disallow image' command to disallow access privilege from another user.
PRGO-01085: Role "{0}" has never been granted access to image "{1}".: Cause: An attempt to disallow the role from access privilege to the image failed because the role had never been granted access privilege to the image using the 'rhpctl allow image' command.; Action: Use the 'rhpctl disallow image' command to disallow access privilege from another role.
PRGO-01087: READ privilege cannot be granted for image "{0}" because the image state is NEW.: Cause: An attempt to grant READ privilege for the specified image failed because the image state is NEW."; Action: Use the 'rhpctl promote image' command to promote the image to TESTABLE, RESTRICTED or PUBLISHED state before retrying.
PRGO-01088: READ privilege cannot be removed for image "{0}" because the image state is NEW.: Cause: An attempt to remove READ privilege for the specified image failed because the image state is NEW."; Action: Use the 'rhpctl promote image' command to promote the image to TESTABLE, RESTRICTED or PUBLISHED state before retrying.
PRGO-01090: failed to retrieve the owner of the image "{0}": Cause: An attempt to retrieve the owner of the image failed.; Action: Examine the accompanying error messages for more information.
PRGO-01091: failed to retrieve the owner of the working copy "{0}": Cause: An attempt to retrieve the owner of the working copy failed.; Action: Examine the accompanying error messages for more information.
PRGO-01092: Failed to update the GNS information of the Rapid Home Provisioning Client.: Cause: An error occurred while updating the Rapid Home Provisioning Client's GNS information.; Action: Examine the accompanying error messages for more information.
PRGO-01097: Grant operation failed because role "{0}" is already granted to user "{1}".: Cause: An attempt to grant a role to a given user failed because the role was already granted to that user.; Action: Confirm that the role and the user supplied are correct and retry if either is not.
PRGO-01098: Revoke operation failed because role "{0}" is not granted to user "{1}".: Cause: An attempt to revoke a role from a given user failed because the role was not granted to that user.; Action: Confirm that the role and the user supplied are correct and retry if either is not.
PRGO-01099: root user is not allowed to add working copy "{0}": Cause: An attempt was made to create a working copy owned by the root user.; Action: Either run 'rhpctl add workingcopy' command as a non-root user or specify the '-user' option with a non-root user.
PRGO-01100: Failed to connect to the management database because it is not running: Cause: An attempt to connect to the management database failed because it was not running.; Action: Use 'srvctl start mgmtdb' command to start the management database.
PRGO-01101: Missing Oracle base for working copy "{0}" for image "{1}" because image type is {2}.: Cause: The '-oraclebase' option was omitted for an image type that requires it.; Action: Supply the '-oraclebase' option with the 'rhpctl add workingcopy' command.
PRGO-01103: add image "{0}" failed: Cause: An attempt was made to perform an add image operation with the same image name during a rerun of the failed import image operation.; Action: Rerun the failed import image command to complete the image creation.
PRGO-01104: import image "{0}" failed: Cause: An attempt was made to perform an import image operation with the same image name during a rerun of the failed add image operation.; Action: Rerun the failed add image command to complete the image creation.
PRGO-01105: The specified '-oraclebase' option value "{0}" is a non-writable directory or cannot be created on nodes "{1}".: Cause: The specified '-oraclebase' option value was a non-writable path to the Grid user or cannot be created by the Grid user.; Action: Ensure that the Oracle base path directory or its parent directory is writable by the Grid user or the directory path can be created by the Grid user.
PRGO-01106: failure while checking for the existence of specified path "{0}" on nodes "{1}": Cause: The check for the existence of the specified path failed on the indicated nodes.; Action: Examine the accompanying error messages for details and proceed as indicated by those messages.
PRGO-01107: Database "{0}" already exists.: Cause: The specified database resource was already registered in Oracle Clusterware.; Action: Specify another database name and retry the command.
PRGO-01108: The specified disk group "{0}" does not exist.: Cause: The resource for the specified disk group could not be found. Either the disk group name was misspelled or the disk group has not been mounted.; Action: Correct the disk group spelling or use SQL*Plus to create the disk group.
PRGO-01109: The specified path "{0}" is not a shared path.: Cause: An attempt to add a working copy failed because the specified storage path was not shared among the cluster nodes.; Action: Specify a path that is shared by all cluster nodes.
PRGO-01110: The specified nodes "{0}" do not exist on the cluster.: Cause: The requested operation was rejected because the indicated nodes did not exist in the cluster.; Action: 1) If the specified node names were incorrect, then reissue the command with the correct node list; 2) If the specified node is on another cluster and expected database type is Oracle RAC, then supply the client cluster name and required credentials; 3) If the specified node is on another cluster and expected database type is SINGLE, then supply the database type and required credentials.
PRGO-01111: An administrator-managed database cannot be created on specified Leaf Nodes "{0}".: Cause: An attempt to create a working copy failed because some or all of the specified nodes are Leaf Nodes.; Action: Specify only Hub Nodes for an administrator-managed database and retry the command.
PRGO-01112: The specified server pool "{0}" does not exist.: Cause: The specified server pool was not found.; Action: Specify another server pool name or create a server pool with the given name and retry the command.
PRGO-01113: server pool "{0}" category of 'leaf' not supported for policy-managed database: Cause: An attempt to create a working copy was rejected because the specified server pool has a category with CSS_ACTIVE_ROLE=LEAF.; Action: Specify a server pool that can only contain Hub servers for a policy-managed database.
PRGO-01114: invalid use of -pqpool option for provisioning database on cluster "{0}": Cause: The '-pqpool' option was specified for provisioning a database on a target cluster that was not an Oracle Flex Cluster.; Action: Omit the '-pqpool' option if the cluster where the database needs to be provisioned is not an Oracle Flex Cluster, or choose a target cluster for database provisioning that is an Oracle Flex Cluster and would, therefore, accept the '-pqpool' option.
PRGO-01115: '-newpqpool' and '-pqcardinality' options cannot be specified for provisioning database on Rapid Home Provisioning Server (RHPS).: Cause: An attempt to create a working copy failed because RHPS does not support the '-newpqpool' and '-pqcardinality' options.; Action: Omit the '-newpqpool' and '-pqcardinality' options when provisioning databases on RHPS.
PRGO-01116: User equivalence does not exist on nodes "{0}".: Cause: User equivalence did not exist among the nodes indicated.; Action: Ensure that user equivalence exists on all cluster nodes.
PRGO-01117: The specified user name "{0}" does not exist in the operating system.: Cause: An attempt to create a working copy failed because the user did not exist.; Action: Ensure that the user exists and retry.
PRGO-01118: The specified storage path "{0}" is not a directory.: Cause: An attempt to create a working copy failed because the specified storage path is not a directory.; Action: Ensure that the specified storage option value is an absolute directory path or a disk group name and retry.
PRGO-01119: The specified storage path "{0}" does not exist.: Cause: An attempt to create a working copy failed because the specified storage path did not exist.; Action: Ensure that the specified storage path exists or specify an existing disk group name and retry.
PRGO-01125: Delete operation failed because role "{0}" has the following roles: "{1}".: Cause: An attempt to delete a role failed because the role has been granted one or more roles.; Action: Revoke or delete the roles granted to this role and retry.
PRGO-01126: Delete operation failed because role "{0}" has been granted to the following users: "{1}".: Cause: An attempt to delete a role failed because the role has been granted to one or more users.; Action: Revoke this role from the users and retry.
PRGO-01128: An unsupported 'rhpctl' command was issued on Rapid Home Provisioning Server: Cause: A Rapid Home Provisioning Client 'rhpctl' command was submitted on the Rapid Home Provisioning Server.; Action: Run the 'rhpctl' command on a Rapid Home Provisioning Client.
PRGO-01129: failed to connect to Rapid Home Provisioning Client (RHPC): Cause: An attempt to connect to Rapid Home Provisioning Client (RHPC) failed, possibly because it was not running on the remote cluster.; Action: Start Rapid Home Provisioning Client (RHPC) using 'srvctl start rhpclient' on the remote cluster and retry the command.
PRGO-01130: Database name "{0}" contains invalid characters.: Cause: The supplied database name contained invalid characters.; Action: Supply a valid database name. The valid character set for database names is [a-z, A-Z, 0-9, $, #, _].
PRGO-01131: Delete operation failed, client "{0}" has the following working copies: "{1}".: Cause: A delete client operation failed because one or more working copies exist on the specified client.; Action: Delete the specified working copies and retry the operation.
PRGO-01132: Rapid Home Provisioning Server (RHPS) user "{0}" does not exist in the repository.: Cause: A repository query failed unexpectedly. This is an internal error.; Action: Contact Oracle Support Services.
PRGO-01133: User "{0}" lacks the authority to perform the 'promote image' operation.: Cause: The user running the 'rhpctl promote image' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01134: built-in role "{0}" cannot be deleted: Cause: A request was made to delete a built-in role.; Action: Refer to the product documentation.
PRGO-01135: User "{0}" lacks the authority to perform the 'add client' operation.: Cause: The user running the 'rhpctl add client' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01136: User "{0}" lacks the authority to perform the 'add workingcopy' operation.: Cause: The user running the 'rhpctl add workingcopy' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01137: User "{0}" lacks the authority to perform the 'query client' operation.: Cause: The user running the 'rhpctl query client' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01138: User "{0}" lacks the authority to perform the 'delete client' operation.: Cause: The user running the 'rhpctl delete client' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01139: User "{0}" lacks the authority to perform the 'delete workingcopy' operation.: Cause: The user running the 'rhpctl delete workingcopy' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01140: User "{0}" lacks the authority to perform the 'modify client' operation.: Cause: The user running the 'rhpctl modify client' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01141: built-in GH_SA role cannot be revoked from Oracle Grid Infrastructure user "{0}": Cause: An attempt was made to revoke the built-in GH_SA role from the user of the Oracle Grid Infrastructure home.; Action: Specify another user name or role name in the 'rhpctl revoke role' command.
PRGO-01142: built-in GH_CA role cannot be revoked from Oracle Grid Infrastructure user "{0}" of cluster "{1}": Cause: An attempt was made to revoke the built-in GH_CA role from the user of the Oracle Grid Infrastructure home.; Action: Specify another user name or role name in the 'rhpctl revoke role' command.
PRGO-01143: built-in GH_SA role cannot be revoked from role "{0}" by user "{1}" at cluster {2}: Cause: The user running 'rhpctl revoke role' command did not have the privilege to revoke the built-in GH_SA role from the specified role.; Action: Grant the GH_SA role to the user running the 'rhpctl revoke role' command.
PRGO-01144: built-in GH_CA role cannot be revoked from role "{0}" by user "{1}" at cluster {2}: Cause: The user running 'rhpctl revoke role' command did not have the privilege to revoke the built-in GH_CA role from the specified role.; Action: Grant the GH_CA and GH_ROLE_ADMIN roles, or the GH_SA role, to the user running the 'rhpctl revoke role' command.
PRGO-01145: User "{0}" on cluster "{1}" cannot grant the built-in GH_SA role to another user.: Cause: The user running 'rhpctl grant role' command did not have the privilege to grant the built-in GH_SA role to another user.; Action: Grant the GH_SA role to the user running 'rhpctl grant role' command.
PRGO-01146: User "{0}" on cluster "{1}" cannot grant the built-in GH_CA role to another user.: Cause: The user running 'rhpctl grant role' command did not have the privilege to grant the built-in GH_CA role to another user.; Action: Grant the GH_CA and GH_ROLE_ADMIN roles, or the GH_SA role, to the user running the 'rhpctl grant role' command.
PRGO-01147: User "{0}" on cluster "{1}" cannot grant the built-in GH_SA role to another role.: Cause: The user running 'rhpctl grant role' command did not have the privilege to grant the built-in GH_SA role to another role.; Action: Grant the GH_SA role to the user running 'rhpctl grant role' command.
PRGO-01148: User "{0}" on cluster "{1}" cannot grant the built-in GH_CA role to another role.: Cause: The user running 'rhpctl grant role' command did not have the privilege to grant the built-in GH_CA role to another role.; Action: Grant the GH_CA and GH_ROLE_ADMIN roles, or the GH_SA role, to the user running the 'rhpctl grant role' command.
PRGO-01149: The source working copy version and the patched working copy version are different.: Cause: An attempt to move the database failed because the source and patched working copy versions are different.; Action: Ensure that the source and patched working copy versions are the same for the move database operation.
PRGO-01150: The source working copy owner and the patched working copy owner are different.: Cause: An attempt to move the database failed because the source and patched working copy owners are different.; Action: Ensure that the source and patched working copy owners are the same for the move database operation.
PRGO-01151: The database 'move' for the specified working copy cannot be performed from Rapid Home Provisioning Client (RHPC) "{0}".: Cause: The working copy was not created by this Rapid Home Provisioning Client.; Action: Execute the command from the cluster that created this working copy.
PRGO-01152: operation not allowed because client authentication failed: Cause: A 'rhpctl' request was not processed because client authentication failed at the server.; Action: Run the 'rhpctl' command from a valid Rapid Home Provisioning Client.
PRGO-01153: failed to validate the client authentication: Cause: An internal error occurred.; Action: Contact Oracle Support Services.
PRGO-01158: User "{0}" on cluster "{1}" cannot revoke the built-in GH_SA role from another user.: Cause: The user issuing a 'rhpctl revoke role' command did not have the privilege to revoke the built-in GH_SA role from another user.; Action: To enable the revocation, grant the GH_SA role to the user.
PRGO-01159: User "{0}" on cluster "{1}" cannot revoke the built-in GH_CA role from another user.: Cause: The user issuing a 'rhpctl revoke role' command did not have the privilege to revoke the built-in GH_CA role from another user.; Action: Grant the GH_CA and GH_ROLE_ADMIN roles, or the GH_SA role, to the user running the 'rhpctl revoke role' command.
PRGO-01160: User "{0}" lacks the authority to perform the 'export client' operation.: Cause: The user running the 'rhpctl export client' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01161: The source working copy and the patched working copy cannot be the same.: Cause: An attempt to move the database was rejected because the specified source and patched working copies are the same.; Action: Ensure that the source and patched working copy are different for the move database operation.
PRGO-01162: operation not allowed because user authentication failed for user "{0}": Cause: A rhpctl request was not processed because user authentication failed at the server.; Action: Run the 'rhpctl' command as a user whose primary group is the 'oinstall' group.
PRGO-01163: Failed to create working copy "{0}" because maximum number of snapshots has been reached for image "{1}": Cause: An attempt to create a working copy failed because the maximum number of snapshots has been reached for the image.; Action: Import a copy of the same image by running 'rhpctl import image' command and then retry the operation.
PRGO-01164: Failed to create a volume for import image because the configured disk group "{0}" does not have enough available space. Detailed error:\n{1}: Cause: An attempt to create a volume for an import image failed because the configured disk group did not have enough available space.; Action: Add more disks to the configured disk group.
PRGO-01165: Failed to create volume because the generated volume name already exists: Cause: An attempt to create a volume failed because the number of tries attempted for generating the volume name was exhausted.; Action: Retry the command.
PRGO-01166: Failed to create image "{0}" from working copy "{1}" because maximum number of snapshots has been reached: Cause: An attempt to create an image from the working copy failed because the maximum number of snapshots has been reached.; Action: Issue 'rhpctl import image' specifying the working copy path for '-path' to create a new image.
PRGO-01167: HAVIP resource does not exist in Oracle Clusterware.: Cause: An attempt to add Rapid Home Provisioning Client failed because the HAVIP resource was not registered with Oracle Clusterware.; Action: Use the command 'srvctl add havip' on the Rapid Home Provisioning Server cluster to create a HAVIP resource.
PRGO-01170: The default templates directory "{0}" does not exist in the image specified.: Cause: The image created on the Rapid Home Provisioning Server did not contain the templates directory.; Action: Specify an image that includes the templates directory as shown in the message.
PRGO-01188: failed to add client on Rapid Home Provisioning Server (RHPS) because neither GNS server nor GNS client are configured on this cluster: Cause: A 'rhpctl add client' command failed because neither GNS server nor GNS client was configured on this cluster.; Action: Configure either GNS server or GNS client using the command 'srvctl add gns' in this cluster and retry the command.
PRGO-01189: provisioning of databases not supported on working copy of image type "{0}": Cause: An attempt to create or delete a database was rejected because the working copy was not created from an image of type ORACLEDBSOFTWARE.; Action: Specify a working copy that was created from an image of type ORACLEDBSOFTWARE.
PRGO-01190: The database "{0}" was not created using working copy "{1}".: 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.; Action: Specify a working copy with which the database was created.
PRGO-01191: The specified working copy "{0}" is not provisioned on the cluster "{1}".: Cause: An attempt to add a database was rejected because the specified working copy was not provisioned on this cluster.; Action: Specify a working copy that is provisioned on the cluster on which the 'rhpctl add database' is issued.
PRGO-01192: failed to create database "{0}" because the specified working copy was not created properly: Cause: An attempt to add a database was rejected because the specified working copy was not created properly.; Action: Specify the command 'rhpctl add workingcopy' to properly create the working copy and retry the command.
PRGO-01195: The '-path' option required for creating working copy on the client cluster is not specified.: Cause: The attempt to move database using 'rhpctl move database' was rejected because; Action: Retry the 'rhpctl move database' command specifying the '-path' option.
PRGO-01196: The '-image' option required for creating the working copy is not specified.: Cause: The attempt to move the database using 'rhpctl move database' failed because the '-image' option was not specified. The '-image' option is required to create a new working copy to specify the image from which to create the working copy.; Action: Either request a new working copy using both -image and -patchedwc or specify an existing working copy using the -patchedwc option.
PRGO-01197: The patched working copy was not created from an image of type ORACLEDBSOFTWARE.: Cause: An attempt to move the database failed because the patched working copy was not created from an image of type ORACLEDBSOFTWARE.; Action: Ensure that the patched working copy is created from an image of type ORACLEDBSOFTWARE.
PRGO-01198: The source working copy is incomplete.: Cause: The source working copy was in a partially completed state.; Action: Retry the 'rhpctl move database' command after ensuring that the source working copy has been created successfully.
PRGO-01201: cannot add image from working copy "{0}" because creation of this working copy was not complete.: Cause: An attempt to add an image from a working copy was rejected because creation of the specified working copy was not complete.; Action: Specify a complete working copy from which add the image.
PRGO-01202: Nothing to modify.: Cause: No options were specified to modify.; Action: Specify at least one option to modify. See the command usage for available options.
PRGO-01203: cannot add working copy from image "{0}" because creation of this image was not complete: Cause: An attempt to add a working copy from an image was rejected because creation of the specified image was not complete.; Action: Specify a complete image from which to add the working copy.
PRGO-01204: The specified working copy has no databases to move.: Cause: An attempt to move a database from a working copy failed because the specified working copy did not have a database configured.; Action: Specify a working copy that has at least one database.
PRGO-01205: The source working copy was not created from an image of type ORACLEDBSOFTWARE.: Cause: An attempt to move a database failed because the source working copy was not created from an image of type ORACLEDBSOFTWARE.; Action: Ensure that the source working copy was created from an image of type ORACLEDBSOFTWARE for the move database operation.
PRGO-01206: The '-oraclebase' option is not allowed when creating working copy "{0}" for image "{1}" because the image type of this working copy is not ORACLEDBSOFTWARE.: Cause: An attempt to add a working copy was rejected because the '-oraclebase' option was specified to create a working copy from an image with the type SOFTWARE. The '-oraclebase' option is valid only for images of type ORACLEDBSOFTWARE.; Action: Retry the command 'rhpctl add workingcopy' without the '-oraclebase' option or specify a working copy that was created from an image of type ORACLEDBSOFTWARE.
PRGO-01207: failed to delete database "{0}" because the specified working copy {0} is not provisioned on this cluster: Cause: An attempt to delete a database was rejected because the specified working copy was not provisioned on this cluster.; Action: Specify a working copy that is provisioned on the cluster on which the 'rhpctl delete database' is issued.
PRGO-01208: Shared storage verification failed for path "{0}". Detailed error: "{1}": Cause: An invalid value was specified for the '-storage' option. Either the storage does not exist, or it is not shared.; Action: Ensure that the location specified with the '-storage' option exists, is shared and is writable, and rerun the command.
PRGO-01209: unable to delete working copy "{0}" because it contains databases and the force option was not specified: Cause: An attempt to delete the working copy was rejected because databases were configured to run from the working copy and the '-force' option was not specified.; Action: Stop any running databases in the working copy and either specify the '-force' option or delete all databases in the working copy before attempting to delete the working copy.
PRGO-01210: unable to delete working copy "{0}" because it contains one or more running databases: Cause: An attempt to delete the working copy was rejected because the working copy contained one or more running databases.; Action: Either stop the running databases using 'srvctl stop database' or delete all databases configured to run from the working copy and retry the 'delete' command.
PRGO-01211: User "{0}" lacks the authority to perform the operation.: Cause: The user did not have the required authorization to run the command.; Action: Request the authorization from the administrator or perform the operation as a user ID that has the required authorization.
PRGO-01212: unable to delete user "{0}" because working copies "{1}" are owned by this user: Cause: An attempt to delete a given user failed because the user owned one or more working copies in the repository.; Action: Delete the working copies owned by the user supplied and then delete the user.
PRGO-01213: option "{0}" is not allowed from a Rapid Home Provisioning Client: Cause: An option was supplied which can only be used from a Rapid Home Provisioning Server.; Action: Either execute the command with the option from a Rapid Home Provisioning Server or avoid the use of the option from a Rapid Home Provisioning Client.
PRGO-01217: Invalid value "{0}" specified for database template option.: Cause: The '-dbtemplate' option value specified is neither an absolute path nor of the form '<image_name>:<relative_path_of_template>'.; Action: Supply a valid dbtemplate path and retry.
PRGO-01218: failed to export the image file system specified by the database template option value "{0}": Cause: An error occurred while attempting to export the database template image file system.; Action: Examine the accompanying errors for more information.
PRGO-01219: failed to remove the export file system for the image specified by the database template option: Cause: An error occurred while attempting to remove the export file system for the database template image.; Action: Examine the accompanying errors for more information.
PRGO-01220: failed to export the database template image file system because creation of the image "{0}" was not complete: Cause: An attempt to export a database template image file system was rejected because creation of the specified image was not complete.; Action: Specify a complete image and retry the operation.
PRGO-01222: The specified database template path "{0}" does not exist: Cause: An attempt to create a database failed because the specified database template path does not exist.; Action: Ensure that the specified database template path exists and retry.
PRGO-01223: The specified template file "{0}" does not exist on nodes {1}.: Cause: The specified database template file did not exist either on all of the specified nodes for administration managed database, or on all of the cluster nodes for policy managed database.; Action: Ensure that the database template file specified with the '-dbtemplate' option exists either on all of the specified nodes for administration managed database, or on all of the cluster nodes for policy managed database.
PRGO-01224: cannot create a single instance database on multiple nodes "{0}": Cause: The value specified for the '-node' option contained multiple nodes.; Action: Specify a single node that is part of the cluster for the '-node' option and retry.
PRGO-01225: failed to add a working copy from image {0} because file system {1} contained within volume device {2} is offline: Cause: An attempt to add a working copy failed because the file system resource of the image supplied was offline.; Action: Use the 'srvctl start filesystem' command with corresponding volume device to start the file system resource for the image; then retry the command.
PRGO-01226: The source working copy is configured in a different cluster from the patched working copy: Cause: An attempt to move the database failed because the source and patched working copies are configured in different clusters.; Action: Ensure that the source and patched working copies are configured in the same cluster.
PRGO-01227: The '-path' option is not allowed when moving a database on Rapid Home Provisioning Server (RHPS).: Cause: An attempt to move a database on a Rapid Home Provisioning Server failed because the '-path' option was specified without remote provisioning.; Action: Retry the command 'rhpctl move database' without the '-path' option.
PRGO-01228: failed to write a checkpoint for the operation because the checkpoint file system "{0}" is not mounted: Cause: Writing the checkpoint for the previous operation failed because the checkpoint file system was offline.; Action: Use the 'srvctl start filesystem' command to start the file system resource for checkpoints and retry the command.
PRGO-01229: A disk group has not been configured for Rapid Home Provisioning Client.: Cause: An attempt to create a local file system failed because a disk group was not configured.; Action: Use 'srvctl modify rhpclient' command to add a disk group and retry the command.
PRGO-01233: The specified '-path' option value "{0}" is on ACFS: Cause: The working copy could not be added because '-path' option value was on ACFS.; Action: Ensure that the '-path' option value is a shared path that is not on ACFS.
PRGO-01234: failed to add image "{0}" from working copy "{1}" using local storage or Rapid Home Provisioning Client ACFS storage: 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.; Action: Use 'rhpctl import image' to add the image.
PRGO-01235: Path "{0}" is not writable by "{1}".: Cause: The specified path for local storage on the Rapid Home Provisioning Client did not have write access by the user.; Action: Ensure that the '-path' option value has writable permission for the user.
PRGO-01236: Path "{0}" does not have "{1}" KB of free space on nodes {2}.: Cause: There was insufficient free space on the nodes to copy the working copy.; Action: Ensure that the specified path has sufficient free space on all nodes of the cluster.
PRGO-01237: cannot delete built-in user "{0}": Cause: An attempt to delete a given user failed because the specified user was a built-in user.; Action: Do not try to delete a built-in user.
PRGO-01238: specified server pool "{0}" has no candidate server for single instance database "{1}": Cause: An attempt to create a single instance database failed because the specified server pool did not have a configured candidate server.; Action: Specify a different server pool with a maximum of one server, or modify the specified server pool using the command 'srvctl modify srvpool' with '-servers' option to configure exactly one candidate server.
PRGO-01239: specified server pool "{0}" has a maximum size "{1}" too large for single instance database {2}: Cause: An attempt to create a single instance database failed because a server pool with maximum size greater than one server was specified.; Action: Specify a different server pool with maximum size of one, or modify the specified server pool using the command 'srvctl modify srvpool' with '-max 1' option to have at most one server.
PRGO-01240: specified server pool "{0}" has more than one candidate server: Cause: An attempt to create a single instance database failed because a server pool with more than one candidate server was specified.; Action: Specify a different server pool with a maximum of one server, or modify the specified server pool using the command 'srvctl modify srvpool' with '-servers' option to configure exactly one candidate server.
PRGO-01241: The path "{0}" specified for the working copy duplicates the internal path used to mount working copy.: Cause: An attempt to add a working copy was rejected because the specified path duplicates the internal path used to mount the working copy.; Action: Specify a different path and retry.
PRGO-01242: failed to add a working copy with local storage type because the path option was not specified and disk group was not configured for the Rapid Home Provisioning Client cluster: Cause: A command to add a working copy with local storage type was issued without the path option and for a Rapid Home Provisioning Client cluster that did not have a configured disk group.; Action: Specify the '-path' option or configure a disk group for the Rapid Home Provisioning Client with 'srvctl modify rhpclient' and retry the command.
PRGO-01243: An attempt to create a working copy from image "{0}" failed because it is for the "{1}" platform, whereas the detected platform is {2}.: Cause: The image supplied was for a different platform than the one for which the working copy was requested.; Action: Retry the command specifying an image created for the target platform.
PRGO-01244: Cannot grant any role to a root user: Cause: An attempt was made to grant a role to a root user.; Action: Specify a different user and retry.
PRGO-01245: User "{0}" for cluster "{1}" is the owner of image "{2}".: Cause: An attempt to disallow the user access from the image failed because the user owned the image.; Action: Specify a different user and retry.
PRGO-01246: Role "{0}" cannot be disallowed from image "{1}".: Cause: An attempt to disallow the role access from the image failed because the role was a built-in role associated with the image and was not granted access using the 'rhpctl allow image' command.; Action: Specify a different role and retry the command.
PRGO-01247: Role "{0}" cannot be allowed for image "{1}".: Cause: An attempt to allow the role access to the image failed because the role was a built-in role associated with the image.; Action: Specify a different role and retry.
PRGO-01248: cannot grant role "{0}" to a built-in role "{1}": Cause: An attempt was made to grant a role to a built-in role.; Action: Specify a non built-in role for the '-grantee' option and retry.
PRGO-01249: cannot revoke role "{0}" from a built-in role "{1}": Cause: An attempt was made to revoke a role from a built-in role.; Action: Specify a non built-in role for the '-grantee' option and retry.
PRGO-01250: cannot revoke role "{0}" from role "{1}" because role "{1}" has only one associated role: Cause: An attempt to revoke a role from another role with only one associated role failed because that role was a user defined role.; Action: Specify a user defined role with more than one associated roles for the '-grantee' option and retry.
PRGO-01251: Role "{0}" cannot start with "GH_".: Cause: An attempt to add a role starting with "GH_" failed because "GH_" is a prefix reserved by Oracle for built-in roles.; Action: Specify another role name and retry.
PRGO-01257: failed to import image "{0}": Cause: An error occurred while attempting to import the indicated image.; Action: Examine the accompanying error messages for more information.
PRGO-01258: The specified patched working copy is incomplete.: Cause: The patched working copy was in a partially completed state.; Action: Use the 'rhpctl add workingcopy' command to create a complete patched working copy. Ensure that options such as '-oraclebase', '-user', and '-client' are set the same as in the source working copy. Then retry 'rhpctl move database' command.
PRGO-01260: Cluster Verification checks for database home provisioning failed for the specified working copy {0}.: Cause: One or more Cluster Verification checks for database home provisioning failed.; Action: Review the underlying error messages and take appropriate action.
PRGO-01261: unable to add database {0} because the specified working copy {1} already exists: Cause: An attempt to add the specified database using 'rhpctl add workingcopy' was rejected because the working copy specified was already in existence.; Action: Use 'rhpctl add database' command to create the database on an existing working copy or use 'rhpctl add workingcopy' specifying a different working copy.
PRGO-01262: unable to verify the existence of the specified file {0} on nodes {1}: Cause: An error occurred while attempting to access the specified database template file.; Action: Examine the accompanying errors for more information.
PRGO-01263: The option '-storagetype LOCAL' is required for provisioning a pre-11.2 version database home.: Cause: An attempt to provision a pre-11.2 version database home was rejected because it can only be provisioned on local, non-ACFS storage.; Action: Retry the operation with the option '-storagetype LOCAL'.
PRGO-01264: The options {0} are not allowed and the '-nodes' option is required for pre 11.2 version database because they cannot be policy-managed.: Cause: An attempt to create a policy-managed database failed because only administrator-managed databases are supported in pre 11.2 version.; Action: Retry the operation with '-nodes' option to create an administrator-managed database.
PRGO-01265: The version of the specified home is {0} and is not 10.2.0.5.: Cause: An attempt to import a version 10.2 image was rejected because the specified Oracle home was not version 10.2.0.5.; Action: Retry the operation with a version 10.2.0.5 Oracle home specified for the '-path' option.
PRGO-01266: The version of the specified home is {0} and is not supported.: Cause: An attempt to import a version 11.1 image was rejected because this version is not supported.; Action: Retry the operation specifying a valid version (10.2.0.5 or 11.2 and above) of Oracle home for the '-path' option.
PRGO-01267: failed to add a database {0} using working copy {1} because the image file system {2} using the volume device {3} is offline: Cause: An attempt to add a database failed because the file system resource of the image containing the working copy supplied was offline.; Action: Use the 'srvctl start filesystem' command with the corresponding volume device to start the file system resource for the image containing the working copy; then retry the command.
PRGO-01268: failed to add a database {0} using working copy {1} because the file system {2} using volume device {3} is offline in the Rapid Home Provisioning Client cluster: Cause: An attempt to add a database failed because the file system resource in the Rapid Home Provisioning Client containing the working copy supplied was offline.; Action: Use the 'srvctl start filesystem' command in the Rapid Home Provisioning Client cluster with the corresponding volume device to start the indicated file system resource. Then retry the command.
PRGO-01269: failed to delete a working copy {0} because the image file system {1} using the volume device {2} is offline: Cause: An attempt to delete a working copy failed because the file system resource of the image containing the working copy supplied was offline.; Action: Use the 'srvctl start filesystem' command with the corresponding volume device to start the file system resource for the image containing the working copy. Then retry the command.
PRGO-01270: failed to delete a working copy {0} because the file system {1} using volume device {2} is offline in the Rapid Home Provisioning Client cluster: Cause: An attempt to delete a working copy failed because the file system resource in the Rapid Home Provisioning Client containing the working copy supplied was offline.; Action: Use the 'srvctl start filesystem' command in the Rapid Home Provisioning Client cluster with the corresponding volume device to start the indicated file system resource. Then retry the command.
PRGO-01271: failed to move database using working copy {0} because the image file system {1} using the volume device {2} is offline: Cause: An attempt to move database failed because the file system resource of the image containing the working copy supplied was offline.; Action: Use the 'srvctl start filesystem' command with the corresponding volume device to start the file system resource for the image containing the working copy; then retry the command.
PRGO-01272: failed to move database using working copy {0} because the file system {1} using volume device {2} is offline in the Rapid Home Provisioning Client cluster: Cause: An attempt to move database failed because the file system resource in the Rapid Home Provisioning Client containing the working copy supplied was offline.; Action: Use the 'srvctl start filesystem' command in the Rapid Home Provisioning Client cluster with the corresponding volume device to start the indicated file system resource. Then retry the command.
PRGO-01273: The specified Oracle home path {0} is already in use by working copy {1} on site {2}.: Cause: An attempt to add the specified working copy was rejected because the specified Oracle home path was already in use.; Action: Retry the command specifying the path for an Oracle home that is not already in use.
PRGO-01274: The directory indicated by the specified NFS Oracle home path {0} was not empty on nodes {1}.: Cause: An attempt to add the specified working copy was rejected because the working copy will be NFS mounted on the directory specified by the path, making the existing files inaccessible.; Action: Retry the command specifying the path for an Oracle home that is empty.
PRGO-01275: failed to verify the emptiness of the specified directory {0} on nodes {1}: Cause: An error occurred while attempting to access the specified directory.; Action: Examine the accompanying errors for more information.
PRGO-01276: failed to delete Rapid Home Provisioning Client (RHPC) because it was running: Cause: An attempt to delete a Rapid Home Provisioning Client (RHPC) failed because it was running on the client cluster.; Action: Either specify the '-force' option on the delete command, or first issue 'srvctl stop rhpclient' on the client cluster.
PRGO-01277: The directory indicated by the specified local Oracle home path {0} was not empty on nodes {1}.: Cause: An attempt to add the specified working copy was rejected because a non-empty directory may contain files that belong to other Oracle software homes when the storage type is LOCAL.; Action: Retry the command specifying the path for an Oracle home that is empty.
PRGO-01280: The revoke operation failed because role "{0}" is not granted to role "{1}".: Cause: An attempt to revoke a role from the grantee role failed because the role had not been granted to the grantee role.; Action: Specify a role that is part of the associated roles of the grantee role.
PRGO-01281: failed to add a working copy because the database version is not compatible with ASM client: Cause: An attempt to add a working copy on an ASM client cluster was rejected because the database version was 12.1.0.1 or lower. ASM client access is supported only for database versions 12.1.0.2 or higher.; Action: Retry the command with a database version of 12.1.0.2 or higher, or on a cluster including the ASM server.
PRGO-01282: The '-path' option required for creating a working copy using local storage on an ASM client cluster is not specified.: Cause: The attempt to create a working copy using local storage on an ASM client cluster was rejected because the '-path' option was not specified.; Action: Retry the 'rhpctl add workingcopy' command specifying the '-path' option.
PRGO-01283: Authentication failure while connecting to Rapid Home Provisioning Client (RHPC): Cause: An attempt to connect to the Rapid Home Provisioning Client failed because the connection could not be authenticated.; Action: Execute the following steps and retry the command: 1) Generate the credentials file at Rapid Home Provisioning Server using the 'rhpctl export client' command. 2) Securely transfer the credentials file from Rapid Home Provisioning Server to Rapid Home Provisioning Client. 3) Modify the Rapid Home Provisioning Client credentials with the credentials file using the 'srvctl modify rhpclient' command on the client cluster.
PRGO-01284: Rapid Home Provisioning Client "{0}" was never started.: Cause: The Rapid Home Provisioning Client daemon did not register its endpoint with the Rapid Home Provisioning Server.; Action: Add and start Rapid Home Provisioning Client on the remote cluster.
PRGO-01285: failed to create database "{0}" because the database version {1} does not support the options '-cdb', '-numberOfPDBs' and '-pdbName': Cause: An attempt to add a database was rejected because the database version was 12.1.0.0 or lower. The options '-cdb', '-numberOfPDBs' and '-pdbName' are supported only for database versions 12.1.0.1 or higher.; Action: Retry the command with a database version of 12.1.0.1 or higher, or do not use the options '-cdb', '-numberOfPDBs' and '-pdbName'.
PRGO-01286: Option '-datafileDestination' does not specify the absolute path to create a database of a version before 11.2.: Cause: An attempt to create a database of a version before 11.2 failed because the '-datafileDestination' argument was not an absolute path.; Action: Supply an absolute path for the '-datafileDestination' option and retry the command.
PRGO-01287: failed to move database because the software home path for working copy {0} is shared and the one for working copy {1} is not: Cause: An attempt to move a database between Oracle homes was rejected because one Oracle home was shared and the other was not.; Action: Either specify source and destination Oracle homes that are both shared, or specify source and destination Oracle homes that are both non-shared.
PRGO-01289: failed to move database because the path was not provided for the patched working copy: Cause: An attempt to move a database between Oracle homes was rejected because the source working copy is not shared and the path was not provided for the patched working copy.; Action: Either specify source and destination Oracle homes that are both shared, or specify a valid path for the patched working copy.
PRGO-01290: unable to create snapshot for the database template because maximum number of snapshots has been reached for image "{0}": Cause: An attempt to create a database failed because the maximum number of snapshots had been reached for the image.; Action: Import a copy of the same image by running the command 'rhpctl import image' and retry the operation specifying the new image.
PRGO-01293: Rerun of 'add workingcopy' rejected because -{0} option differs from the one originally specified: {1}.: Cause: A rerun of an 'add workingcopy' request failed because one of the options specified did not match the one used originally.; Action: Retry the command with the same option entered on the first run of the command.
PRGO-01294: The '-nonrolling' option is required for moving a release 11.1 or earlier database.: Cause: The attempt to move a release 11.1 or earlier database was rejected because the '-nonrolling' option was not specified.; Action: Retry the command with a release 11.2 or higher database, or specify the '-nonrolling' option.
PRGO-01298: Database "{0}" is not configured in working copy "{1}".: Cause: The specified database did not exist in the supplied working copy.; Action: Specify a database which is configured in the supplied working copy.
PRGO-01299: The '-pqpool' option is not supported in a non-Exadata environment.: Cause: The '-pqpool' option was specified in a non-Exadata environment.; Action: Reissue the command without the '-pqpool' option or with the '-pqpool' option in an Exadata environment.
PRGO-01300: The '-newpqpool' option is not supported in a non-Exadata environment.: Cause: The '-newpqpool' option was specified in a non-Exadata environment.; Action: Reissue the command without the '-newpqpool' option or with the '-newpqpool' option in an Exadata environment.
PRGO-01301: Invalid use of '-pqpool' option in standard cluster {0}.: 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.; Action: Reissue the command without the '-pqpool' option or choose an Oracle Flex Cluster as the target cluster.
PRGO-01302: Invalid use of '-newpqpool' option in standard cluster {0}.: 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.; Action: Reissue the command without the '-newpqpool' option or choose an Oracle Flex Cluster as the target cluster.
PRGO-01303: ACFS is not available on PQ nodes.: Cause: The ACFS storage type is not available on PQ nodes.; Action: Use '-pqpool' or '-newpqpool' option with non-ACFS storage types.
PRGO-01304: missing '-oraclebase' option for creating the non-existing patched working copy: {0}: Cause: An attempt to create a patched working copy was rejected because the '-oraclebase' option required for creating a new working copy was not specified.; Action: Reissue the command and supply the '-oraclebase' option.
PRGO-01305: Improper '-oraclebase' option specified for existing working copy: {0}.: Cause: An attempt to move the databases was rejected because the '-oraclebase' option was specified for an existing patched working copy that does not require it.; Action: Rerun the 'rhpctl move database' command without the '-oraclebase' option.
PRGO-01306: failed to move database because the software home path {0} is shared and the one for working copy {1} is not: Cause: An attempt to move a database between Oracle homes was rejected because the source Oracle home was shared while the destination was not.; Action: To move databases between Oracle homes, specify source and destination Oracle homes that are either both shared or both not shared, or where the source Oracle home is not shared and the destination is shared.
PRGO-01307: failed to move database because the user specified '-path' or '-image' option for an existing patched working copy: Cause: An attempt to move database was rejected because the '-path' or '-image' option was specified. The '-path' or '-image' option should not be entered if the patched working copy has been created.; Action: Retry the command without the '-path' or '-image' option.
PRGO-01309: An attempt to import image "{0}" failed because the software home specified is for the "{1}" platform, whereas the cluster platform is "{2}".: Cause: The software home supplied was for a different platform than the one on cluster.; Action: Retry the command specifying a software home that matches the cluster platform.
PRGO-01310: Database type RacOneNode is not supported in pre-11.2 versions.: Cause: An attempt to create a database of type 'RacOneNode' was rejected because database type RacOneNode is not supported in pre-11.2 versions.; Action: Retry the operation specifying a supported database type.
PRGO-01311: failed to get the directory size of path "{0}" during import image of "{1}": 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.; Action: Ensure that either the current user or the owner specified with '-pathowner' has read and execute permissions for the specified directory. Examine the accompanying error messages for more information.
PRGO-01312: failed to move database because the path was not provided for the patched working copy: Cause: An attempt to move a database between Oracle homes was rejected because the source working copy is shared and a shared path was not provided for the patched working copy.; Action: Either specify source and destination Oracle homes that are both local non-shared, or specify a valid shared path for the patched working copy.
PRGO-01313: Rapid Home Provisioning Client (RHPC) is not reachable.: Cause: An error occurred while attempting to connect to the Rapid Home Provisioning Client (RHPC).; Action: Examine the accompanying errors for more information.
PRGO-01314: Rapid Home Provisioning Client cluster "{0}" GUID {1} does not match the value stored in repository {2}.: Cause: An attempt to connect to the Rapid Home Provisioning Server failed because the cluster GUID of the Rapid Home Provisioning Client did not match the cluster GUID stored in the Rapid Home Provisioning Server repository.; Action: Contact the Rapid Home Provisioning Server site administrator to enable the client.
PRGO-01315: Invalid value "{0}" specified for the platform option. The valid values are:\n{1}: Cause: The command was rejected because the value specified for the '-platform' option was not a valid OS platform.; Action: Supply a valid platform and retry the command.
PRGO-01317: The owner "{0}" of the source home does not match the owner "{1}" of the patched working copy "{2}".: Cause: An attempt to move the database failed because the source software home path and patched working copy ownerships are different.; Action: Create or specify a patched working copy with the same owner as the source home and retry the move database operation.
PRGO-01318: The database "{0}" was not created using software home path "{1}".: 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.; Action: Specify the software home path with which the database was created.
PRGO-01319: The specified software home path has no databases to move.: 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.; Action: Specify a software home path that has at least one database.
PRGO-01320: failed to validate that home {0} in cluster {1} is of platform {2}: Cause: An error occurred while validating the platform of the home to be imported.; Action: Examine the accompanying error messages.
PRGO-01321: invalid storage type "RHP_MANAGED" specified for a client without a disk group: Cause: An attempt to add a working copy failed because the storage type was specified as RHP_MANAGED for a client without disk groups.; Action: Add disk groups to the client or specify another storage type.
PRGO-01322: failed to find available servers for pool "{0}": 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.; Action: Either specify an existing pool with active servers, or create a new pool and make sure that: 1) for a new server pool in an Oracle Flex Cluster, there is at least one free Hub Node server; 2) for a new server pool in a Regular Cluster, there is at least one free server; 3) for a new PQ pool, there is at least one free Leaf Node server in an Oracle Flex Cluster.
PRGO-01323: Pool {0} already exists.: Cause: The specified pool already exists.; Action: Use the existing pool or specify another name for the new pool.
PRGO-01324: The Grid Infrastruture software version of the specified home path {0} is invalid for import operation.: Cause: The command was rejected because the Grid Infrastruture software version is not a valid version for this operation.; Action: Supply a home path with the Grid Infrastructure software version 11.2.0.3 and above.
PRGO-01327: The Grid Infrastruture software cannot be provisioned from Rapid Home Provisioning Client.: Cause: The command was rejected because the Grid Infrastruture could not be provisioned from Rapid Home Provisioning Client.; Action: Issue the provisioning command from the Rapid Home Provisioning Server.
PRGO-01331: failed to execute the command because it was not issued from Rapid Home Provisioning Server (RHPS): Cause: The command was rejected because it can only be issued from Rapid Home Provisioning Server (RHPS).; Action: Retry the command from Rapid Home Provisioning Server (RHPS).
PRGO-01332: Image type of the image "{0}" is not ORACLEGISOFTWARE.: Cause: An incorrect image type was specified for Oracle Grid Infrastructure provisoning.; Action: Specify an image with image type ORACLEGISOFTWARE.
PRGO-01333: Databases are currently being moved from or to working copy {0}.: Cause: An attempt to start moving databases from or to the indicated working copy was rejected because of an ongoing move operation.; Action: Retry after completing or aborting the ongoing move operation.
PRGO-01334: No databases are being moved to working copy {0}.: 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.; Action: None
PRGO-01335: Unexpected option '{0}' specified for Oracle home {1} of version {2}.: Cause: The attempted operation was rejected because the indicated option was not supported for the indicated version of Oracle home.; Action: Retry the command without the indicated option.
PRGO-01338: Databases are currently being moved from or to the Oracle home at {0}.: Cause: An attempt to start moving databases from or to the indicated Oracle home was rejected because of an ongoing move operation.; Action: Retry after completing or aborting the ongoing move operation.
PRGO-01340: Re-execution of 'add workingcopy' rejected because node list specified does not contain the local node {0} originally specified.: 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.; Action: Reissue the failed command ensuring that the local node is part of the node list specified.
PRGO-01341: Re-execution of 'add workingcopy' rejected because the value '{1}' supplied for the response file parameter '{0}' differs from the value originally specified: '{2}'.: Cause: Re-execution of the 'add workingcopy' command failed because the response file contents did not match the one used for the original execution.; Action: Retry the command with the same response file contents used for the first execution of the command.
PRGO-01342: identical source and destination working copies: Cause: An attempt to upgrade the database was rejected because the specified source and destination working copies were the same.; Action: Ensure that the source and destination working copies are different for the upgrade database operation.
PRGO-01343: The source working copy was not created from an image of type ORACLEDBSOFTWARE.: Cause: An attempt to upgrade a database failed because the source working copy was not created from an image of type ORACLEDBSOFTWARE.; Action: Ensure that the source working copy was created from an image of type ORACLEDBSOFTWARE for the upgrade database operation.
PRGO-01344: The database upgrade operation for the specified working copy cannot be performed from Rapid Home Provisioning Client (RHPC) "{0}".: Cause: The working copy was not created by this Rapid Home Provisioning Client.; Action: Execute the command from the cluster that created this working copy.
PRGO-01345: failed to upgrade database because the user specified '-image' option for an existing destination working copy: 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.; Action: Retry the command without the '-image' option.
PRGO-01346: The destination working copy was not created from an image of type ORACLEDBSOFTWARE.: Cause: An attempt to upgrade the database failed because the destination working copy was not created from an image of type ORACLEDBSOFTWARE.; Action: Ensure that the destination working copy is created from an image of type ORACLEDBSOFTWARE.
PRGO-01347: The source working copy version {0} and the destination working copy version {1} are incorrect.: Cause: An attempt to upgrade the database failed because the source and destination working copy versions were incorrect.; Action: Ensure that the source working copy version is equal to Oracle Database 10g Release 5 (10.2.0.5), or later than Oracle Database 11g Release 2 (11.2.0.2) but earlier than Oracle Database 12c Release 2 (12.2). Also, ensure that the destination working copy version is equal to or later than Oracle Database 12c Release 1 (12.1.0.1).
PRGO-01348: The source working copy and destination working copy version {0} is the same.: Cause: An attempt to upgrade the database failed because the source working copy and destination working copy version were the same.; Action: Ensure that the source working copy version is equal to Oracle Database 10g Release 5 (10.2.0.5), or later than Oracle Database 11g Release 2 (11.2.0.2) but earlier than Oracle Database 12c Release 2 (12.2). Also, ensure that the destination working copy version is equal to or later than Oracle Database 12c Release 1 (12.1.0.1).
PRGO-01349: The destination working copy version {0} is lower than the source working copy version {1}.: Cause: An attempt to upgrade the database failed because the destination working copy version was lower than the source working copy version.; Action: Ensure that the source working copy version is equal to Oracle Database 10g Release 5 (10.2.0.5), or later than Oracle Database 11g Release 2 (11.2.0.2) but earlier than Oracle Database 12c Release 2 (12.2). Also, ensure that the destination working copy version is is equal to or later than Oracle Database 12c Release 1 (12.1.0.1).
PRGO-01350: The source working copy owner and the destination working copy owner are different.: Cause: An attempt to upgrade the database failed because the source and destination working copy owners were different.; Action: Ensure that the source and destination working copy owners are the same for the upgrade database operation.
PRGO-01351: The source working copy is configured in a different cluster from the destination working copy.: Cause: An attempt to upgrade the database failed because the source and destination working copies were configured in different clusters.; Action: Ensure that the source and destination working copies are configured in the same cluster.
PRGO-01352: The '-image' option required for creating the working copy is not specified.: 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.; Action: Either request a new working copy using both '-image' and '-dstwc' or specify an existing working copy using the '-dstwc' option.
PRGO-01353: failed to upgrade database using working copy {0} because the image file system {1} using the volume device {2} is offline: Cause: An attempt to upgrade a database failed because the file system resource of the image containing the supplied working copy was offline.; Action: Use the 'srvctl start filesystem' command with the corresponding volume device to start the file system resource for the image containing the working copy. Retry the command.
PRGO-01354: failed to upgrade database using working copy {0} because the file system {1} using volume device {2} is offline in the Rapid Home Provisioning Client cluster: Cause: An attempt to upgrade a database failed because the file system resource in the Rapid Home Provisioning Client containing the supplied working copy was offline.; Action: Use the 'srvctl start filesystem' command in the Rapid Home Provisioning Client cluster with the corresponding volume device to start the indicated file system resource. Retry the command.
PRGO-01357: The source working copy is incomplete.: Cause: The source working copy was in a partially completed state.; Action: Retry the 'rhpctl upgrade database' command after ensuring that the source working copy has been created successfully.
PRGO-01358: The specified destination working copy is incomplete.: Cause: The destination working copy was in a partially completed state.; Action: Use the 'rhpctl add workingcopy' command to create a complete destination working copy. Ensure that options such as '-oraclebase', '-user', and '-client' are set the same as in the source working copy. Retry the 'rhpctl upgrade database' command.
PRGO-01361: failed to upgrade database because the path was not provided for the destination working copy: 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.; Action: Either specify source and destination Oracle homes that are both local non-shared, or specify a valid shared path for the destination working copy.
PRGO-01362: failed to upgrade database because the software home path for source working copy {0} is shared and the one for destination working copy {1} is not shared: 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.; Action: Specify a pair of working copies where if the source working copy is shared the destination is also shared.
PRGO-01364: failed to retrieve patch information from the working copy "{0}": Cause: An attempt to query working copy information failed because the patch information could not be retrieved from the indicated working copy.; Action: Examine the accompanying error messages for more information, address reported issues, and retry.
PRGO-01365: The image type "{0}" is inappropriate for single instance database provisioning.: Cause: Image of type SOFTWARE was used for standalone provisioning.; Action: Reissue the command with image of type either ORACLEDBSOFTWARE or ORACLEGISOFTWARE.
PRGO-01366: The specified path "{0}" for provisioning software home is not empty.: 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.; Action: Retry the command ensuring that the specified directory for an Oracle home is empty.
PRGO-01367: The specified value "{0}" for "-datafileDestination" did not exist.: Cause: The specified datafileDestination did not exist.; Action: Reissue the command specifying a valid database storage location.
PRGO-01368: The specified location "{0}" for "-datafileDestination" is not writable.: Cause: A supplied database storage location was not writable by the user.; Action: Either specify a location writable by the user or reissue the command as a user with write authorization to the location.
PRGO-01369: The specified working copy "{0}" is not provisioned on node "{1}".: Cause: An attempt to add a database was rejected because the specified working copy was not provisioned on the specified node.; Action: Specify a working copy that is provisioned on the specified node.
PRGO-01370: The specified working copy "{0}" is not provisioned on a standalone node.: Cause: An attempt to add a database was rejected because the specified working copy was not provisioned on any standalone node.; Action: Specify a working copy that is provisioned on the standalone node.
PRGO-01371: The specified Oracle home path {0} is already in use by working copy {1} on node {2}.: Cause: An attempt to add the specified working copy was rejected because the specified Oracle home path was already in use.; Action: Retry the command specifying the path for an Oracle home that is not already in use.
PRGO-01372: Node "{0}" does not exist.: Cause: The provided node does not exist.; Action: Reissue the command with existing node.
PRGO-01373: The credentials required for remote node connection are missing.: Cause: The requested standalone provisioning was rejected because credentials required for remote node connection were not provided.; Action: Provide either the credentials needed for remote connection or a working copy with RHP target.
PRGO-01374: The credentials are not needed for Rapid Home Provisioning.: Cause: Credentials were provided for Rapid Home Provisioning.; Action: Reissue the command either without the credentials for remote connection, but including the -client option, or with the working copy existing on a standalone node. To determine whether the working copy exists on a standalone node, issue the command 'rhpctl query workingcopy -workingcopy <workingcopy_name>'.
PRGO-01375: Option '-datafileDestination' does not specify the absolute path to create a single instance database on a standalone node.: Cause: An attempt to provision a single instance database on standalone node was rejected because the '-datafileDestination' argument was not an absolute path.; Action: Supply an absolute path for the '-datafileDestination' option and retry the command.
PRGO-01376: User does not exist on nodes "{0}".: Cause: The user did not exist on one or more nodes as indicated.; Action: Ensure that user exists on all the specified nodes.
PRGO-01378: The version of the specified image is "{0}" and is not supported.: Cause: An image with an unsupported version was specified for Oracle Grid Infrastructure provisoning.; Action: Specify an image with version 11.2.0.3.0, 11.2.0.4.0, 12.1.0.2.0, or higher and retry.
PRGO-01379: Oracle Grid Infrastructure response file {0} does not exist.: Cause: An attempt to locate the specified Oracle Grid Infrastructure response file failed.; Action: Ensure that the full path of the Oracle Grid Infrastructure response file is correctly specified.
PRGO-01380: Oracle Grid Infrastructure response file {0} is not a file.: Cause: The specified Oracle Grid Infrastructure response file was a directory.; Action: Ensure that the full path of the Oracle Grid Infrastructure response file is correctly specified.
PRGO-01381: Parameter "{0}" is empty.: Cause: A value was not specified for the parameter in the response file or command line.; Action: Specify a usable value for the parameter and retry.
PRGO-01382: Invalid parameter "{0}" specified in the Oracle Grid Infrastructure response file.: Cause: An invalid parameter was specified in the response file.; Action: Specify valid parameters in the response file and retry.
PRGO-01383: response file generate path not supplied: Cause: This is an internal error.; Action: Contact Oracle Support Services.
PRGO-01384: Input parameter is null or empty.: Cause: This is an internal error.; Action: Contact Oracle Support Services.
PRGO-01385: User "{0}" lacks the authority to perform the 'subscribe series' operation.: Cause: The user running the 'rhpctl subscribe series' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01386: User "{0}" lacks the authority to perform the 'unsubscribe series' operation.: Cause: The user running the 'rhpctl unsubscribe series' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01387: User "{0}" is not registered with an email address.: Cause: An attempt to unregister the email address of the user was rejected because the user was not registered with an email address.; Action: Supply a user with registered email address and retry.
PRGO-01388: User "{0}" is already subscribed to the series "{1}".: Cause: An attempt to subscribe a user to a series failed because the user was already subscribed to the series.; Action: Supply another user name or series name and retry.
PRGO-01390: User "{0}" is not subscribed to the series "{1}".: Cause: An attempt to unsubscribe a user from a series failed because the user was not subscribed to the series.; Action: Supply a subscribed user name and retry.
PRGO-01391: User "{0}" is already registered with an email address "{1}".: Cause: An attempt to register an email address for a user failed because the user was already registered with an email address.; Action: Use the 'rhpctl modify user' command to modify the email address of the user or unregister the email address using 'rhpctl unregister user' command and retry.
PRGO-01392: failed to send the email notification to the registered users, but the issued command completed successfully: 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.; Action: Ensure that the registered email for Rapid Home Provisioning (RHP) is correct and that the email server is reachable.
PRGO-01402: The specified user "{0}" is not registered with an email address to receive email notifications.: Cause: The command was rejected because the user did not have a registered email address.; Action: Specify the '-notify' option with a user for whom an email address is registered.
PRGO-01410: User "{0}" lacks the authority to perform the 'add useraction' operation.: Cause: The user running the 'rhpctl add useraction' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01411: User action "{0}" already exists.: Cause: An existing user action with the same name was found when adding a new user action.; Action: Supply another user action name or delete the existing user action name and retry.
PRGO-01412: User "{0}" lacks the authority to perform the 'query useraction' operation.: Cause: The user running the 'rhpctl query useraction' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01423: User "{0}" lacks the authority to perform the 'delete useraction' operation.: Cause: The user running the 'rhpctl delete useraction' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01424: Delete operation failed because user action "{0}" is being used by the following image types: "{1}".: Cause: An attempt to delete a user action failed because the user action is being used by one or more image types.; Action: Remove the user action for the following image types and retry.
PRGO-01425: User "{0}" lacks the authority to perform the 'add imagetype' operation for image type "{1}".: Cause: The user running the 'rhpctl add imagetype' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01426: Image type "{0}" already exists.: Cause: An existing image type with the same name was found when adding a new image type.; Action: Supply another image type name or delete the existing image type name and retry.
PRGO-01427: Invalid user actions: {0}: Cause: One or more of the supplied user actions did not exist in the repository.; Action: Supply valid user actions and retry.
PRGO-01428: User "{0}" lacks the authority to perform the 'delete imagetype' operation for image type "{1}".: Cause: The user running the 'rhpctl delete imagetype' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01429: Delete operation failed because image type "{0}" is being used by the following images: "{1}".: Cause: An attempt to delete an image type failed because the image type was being used by one or more images.; Action: Remove the specified images from the repository or make sure that they have different image types before attempting to delete the image type.
PRGO-01435: User "{0}" lacks the authority to perform the 'modify imagetype' operation for image type "{1}".: Cause: The user running the 'rhpctl modify imagetype' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01436: User "{0}" lacks the authority to perform the 'allow imagetype' operation for image type "{1}".: Cause: The user running the 'rhpctl allow imagetype' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01437: User "{0}" lacks the authority to perform the 'disallow imagetype' operation for image type "{1}".: Cause: The user running the 'rhpctl disallow imagetype' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01438: User "{0}" for cluster "{1}" was already allowed access to image type {2}.: Cause: An attempt to allow access privilege to the user was rejected because the user had already been granted access privilege to the image type using the 'rhpctl allow imagetype' command.; Action: Ensure the correct user was specified.
PRGO-01439: Role "{0}" cannot be allowed for image type "{1}".: 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.; Action: Specify a different role and retry.
PRGO-01440: Role "{0}" was already allowed access to image type "{1}".: Cause: An attempt to allow access privilege to the role was rejected because the role had already been granted access privilege to the image type using the 'rhpctl allow imagetype' command.; Action: Ensure the correct role was specified.
PRGO-01441: User "{0}" for cluster "{1}" has never been granted access to image type {2}.: 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.; Action: Use the 'rhpctl disallow imagetype' command to revoke access privilege from another user.
PRGO-01442: Role "{0}" has never been granted access to image type "{1}".: 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.; Action: Use the 'rhpctl disallow imagetype' command to disallow access privilege from another role.
PRGO-01443: Role "{0}" cannot be disallowed from image type "{1}".: 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.; Action: Specify a different role and retry the command.
PRGO-01444: User "{0}" lacks the authority to perform the 'query imagetype' operation for image type "{1}".: Cause: The user running the 'rhpctl query imagetype' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01445: User "{0}" lacks the authority to perform the 'modify image' operation.: Cause: The user running the 'rhpctl modify image' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01446: The base type of the image type "{0}" does not match the base type or built-in image type of the image.: 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.; Action: Retry the command with a target image type that has the same base type or built in image type of the image.
PRGO-01447: Failed to retrieve image type information: Cause: Internal error.; Action: Contact Oracle Support Services.
PRGO-01448: Delete operation failed because image type "{0}" is a built-in image type.: 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.; Action: Specify a different image type and retry the command.
PRGO-01449: The specified path {0} is not an Oracle Database Home: Cause: The specified home path does not contain the 'oracle' binary or it is an Oracle Grid Infrastructure home.; Action: Make sure that the home path is an Oracle database home path.
PRGO-01450: The specified path {0} is not an Oracle Grid Infrastructure Home: Cause: The specified home path for the import image operation does not contain the 'crsd' binary.; Action: Make sure that the home path is an Oracle Grid Infrastructure home path.
PRGO-01451: Option '-pathowner' cannot be specified for image type which has base type ORACLEDBSOFTWARE: Cause: A request to import an image was rejected because the '-pathowner' option was specified for importing the Oracle Database home.; Action: Omit the '-pathowner' option.
PRGO-01452: Improper '-version' option (or obsolete '-dbversion' option) specified with image type with base type SOFTWARE.: 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.; Action: Either remove the '-version' option (or obsolete '-dbversion' option) or specify an image type with base type other than SOFTWARE and retry the command.
PRGO-01453: The base type of the image type "{0}" does not match the base type of the image type of the working copy image.: 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.; Action: Retry the command with a target image type that has the same base type as the base type of the image type of the working copy image.
PRGO-01454: Delete operation failed because image type "{0}" does not exist.: Cause: An attempt to delete an image type failed because the image type did not exist.; Action: Specify a different image type and retry the command.
PRGO-01455: User "{0}" lacks the authority to perform the 'query imagetype' operation.: Cause: The user running the 'rhpctl query imagetype' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01456: Query operation failed because image type "{0}" does not exist.: Cause: An attempt to get the image type configuration failed because the image type did not exist.; Action: Specify a different image type and retry the command.
PRGO-01457: Delete operation failed because user action "{0}" does not exist.: Cause: An attempt to delete a user action failed because the user action did not exist.; Action: Specify a different user action and retry the command.
PRGO-01458: Service availability factor (SAF) of {0}% is not feasible for service {1}.: 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.; Action: Retry the command by specifying an appropriate service availability factor.
PRGO-01462: failed to move the Oracle Grid Infrastructure home because the source and the destination working copy cannot be the same: Cause: An attempt to move the Oracle Grid Infrastructure home was rejected because the specified source and destination working copies are the same.; Action: Specify different source and destination working copies and retry the operation.
PRGO-01463: could not perform Oracle Grid Infrastructure home 'move' for the specified working copy from Rapid Home Provisioning Client (RHPC) "{0}": Cause: The Oracle Grid Infrastructure home could not be moved because the working copy was not created by this Rapid Home Provisioning Client.; Action: Execute the command from the cluster that created this working copy.
PRGO-01464: failed to move the Oracle Grid Infrastructure home because the source working copy "{0}" is incomplete: Cause: The source working copy was in a partially completed state.; Action: Retry the 'rhpctl move gihome' command after ensuring that the source working copy has been created successfully.
PRGO-01465: invalid '-path', '-image', or '-aupath' option specified for the move of Oracle Grid Infrastructure home and that was an existing destination working copy: 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."; Action: Retry the command without the '-path', '-image', or '-aupath' option.
PRGO-01472: failure to move or upgrade Oracle Grid Infrastructure home to destination working copy whose base image type is not ORACLEGISOFTWARE: 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.; Action: Retry the command with a destination working copy created from an image of base image type ORACLEGISOFTWARE.
PRGO-01473: The source working copy is not created from an image 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.; Action: Retry the command with a source working copy created from an image of base image type ORACLEGISOFTWARE.
PRGO-01474: failed to move the Oracle Grid Infrastructure home because source and the destination working copy version were different: Cause: An attempt to move the Oracle Grid Infrastructure home failed because the source and destination working copy versions were different.; Action: Retry the command with the same version of source and destination working copy.
PRGO-01475: failed to move the Oracle Grid Infrastructure home because the source working copy owner and the destination working copy owner were different: Cause: An attempt to move the Oracle Grid Infrastructure home failed because the source and destination working copy owners were different.; Action: Ensure that the source and destination working copy owners are the same for the move gihome operation.
PRGO-01476: failed to move the Oracle Grid Infrastructure home because the owner "{0}" of the source home does not match the owner "{1}" of the destination working copy "{2}": 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.; Action: Create or specify a destination working copy with the same owner as the source home and retry the move gihome operation.
PRGO-01477: failed to move the Oracle Grid Infrastructure home because the source working copy was configured in a different cluster from the destination working copy: Cause: An attempt to move the Oracle Grid Infrastructure home failed because the source and destination working copies were configured in different clusters.; Action: Retry the command with the source and destination working copies configured in the same cluster.
PRGO-01478: failed to move the Oracle Grid Infrastructure home because the '-image' option required for creating the destination working copy was not specified: 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.; Action: Either request a new working copy using both -image and -destwc or specify an existing working copy using the -destwc option.
PRGO-01479: failed to move the Oracle Grid Infrastructure home on the Rapid Home Provisoning client "{0}": 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.; Action: Examine the accompanying error messages and retry the command after addressing the cause for the error.
PRGO-01480: illegal option "{0}" specified for standalone provisioning on cluster version other than 11.2.0.4: Cause: The specified option was invalid for a standalone provisioning on cluster version other than 11.2.0.4.; Action: Reissue the command without the forbidden option.
PRGO-01481: Disk group "{0}" does not exist.: Cause: An attempt to provision a database was rejected because the specified disk group was not configured on the standalone target.; Action: Supply the name of a disk group that is configured for the standalone target.
PRGO-01482: The specified node "{0}" is not one on which the working copy is provisioned.: Cause: The requested operation was rejected because the specified node was not part of the nodes on which the working copy was provisioned.; Action: Reissue the command with a node on which the working copy was provisioned or specify the working copy that exists on the specified node.
PRGO-01483: missing "-node" option for creating an administrator-managed database on a cluster whose release is earlier than 12.2: 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.; Action: Reissue the command specifying the '-node' option.
PRGO-01484: More than one node was specified for standalone single instance database provisioning.: Cause: The number of nodes specified for single instance database provisioning was not one.; Action: Specify only one node for the -node option.
PRGO-01485: Specified target node "{0}" is part of cluster "{1}" not managed by Rapid Home Provisioning Server.: Cause: The specified target node was part of a cluster that is not managed by Rapid Home Provisioning Server.; Action: Use 'rhpctl move gihome' command to make this cluster managed by Rapid Home Provisioning Server and retry."
PRGO-01486: Unexpected option '{0}' specified for moving a database between Oracle single-instance database homes which are on a node that does not belong to a cluster.: Cause: The attempted 'move database' operation was rejected because the indicated option was not supported.; Action: Retry the command without the indicated option.
PRGO-01487: Option '{0}' was not specified for moving a single-instance database.: Cause: The attempted 'move database' operation was rejected because the indicated option was not specified.; Action: Specify the indicated option and retry the command.
PRGO-01488: Working copy "{0}" is not an Oracle RAC home.: Cause: An attempt to move or upgrade a database failed because both the source and patched working copies were not Oracle RAC homes.; Action: Specify an Oracle RAC home as the patched working copy and retry the command.
PRGO-01489: The patched working copy is not on the same node as the source working copy or Oracle home.: 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.; Action: Ensure that the source working copy or Oracle home and the patched working copy are on the same node.
PRGO-01491: Unexpected option '{0}' specified for moving databases on a cluster whose version is at least {1}.: Cause: The attempted 'move database' operation was rejected because the indicated option was not needed.; Action: Retry the command without the indicated option.
PRGO-01492: Unexpected option '{0}' specified for moving a database between Oracle single-instance database homes which are on a node that belongs to a cluster of version {1}.: Cause: The attempted 'move database' operation was rejected because the indicated option was not supported.; Action: Retry the command without the indicated option.
PRGO-01493: Unexpected option '{0}' specified for moving a single-instance database between Oracle homes.: Cause: The attempted 'move database' operation was rejected because the indicated option was not supported.; Action: Retry the command without the indicated option.
PRGO-01494: operation not allowed because an existing operation is currently in progress on entity "{0}" previously submitted by user "{1}" on node "{2}" in cluster "{3}": 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.; Action: Wait until the existing active operation finishes, then retry the command.
PRGO-01495: The '-newnodes' option contains node roles for a cluster that is not an Oracle Flex Cluster.: 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.; Action: Specify the value for the '-newnodes' option in the form of "<node_name>:<node_vip>" or specify an Oracle Flex Cluster as the target cluster.
PRGO-01496: missing required option '-targetnode' for performing 'add nodes' operation on a cluster that has no RHP client: 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; Action: Retry specifying the '-targetnode' option.
PRGO-01497: The base image type "{1}" of working copy "{0}" is incompatible with the requested operation.: Cause: The attempted 'addnodes' or 'deletenodes' operation was rejected because the base image type of the specified working copy was not ORACLEGISOFTWARE.; Action: None
PRGO-01498: Working copy "{0}" is software-only.: Cause: An attempt to add or delete nodes from the indicated working copy failed because it was software-only.; Action: Retry specifying a working copy that is not software-only.
PRGO-01499: Working copy "{0}" is incomplete.: Cause: An attempt to run an operation on the indicated working copy failed because it was incomplete.; Action: Retry the command making sure that the working copy supplied is complete.
PRGO-01500: illegal attempt to to provision a working copy on ACFS for a cluster with Leaf nodes: Cause: An attempt to provision a working copy was rejected because the client cluster contains Leaf nodes which cannot access ACFS storage.; Action: Specify the storage type to be NFS or LOCAL with non-ACFS path.
PRGO-01501: failed to upgrade the Oracle Grid Infrastructure home because the specified source working copy version "{0}" is earlier than "{1}": Cause: An attempt to upgrade the Oracle Grid Infrastructure home failed because the source working copy version is incorrect.; Action: Ensure that the source working copy version is later than Oracle Database 11g Release 2 (11.2.0.2.0).
PRGO-01502: failed to upgrade the Oracle Grid Infrastructure home because the specified destination working copy version "{0}" must be later than "{1}": Cause: An attempt to upgrade the Oracle Grid Infrastructure home failed because the destination working copy version is incorrect.; Action: Ensure that the destination working copy version is later than Oracle Database 12c Release 1 (12.1.0.1.0).
PRGO-01503: failed to upgrade the Oracle Grid Infrastructure home because the source and the destination working copy are the same: Cause: An attempt to upgrade the Oracle Grid Infrastructure home was rejected because the specified source and destination working copies are the same.; Action: Specify different source and destination working copies and retry the operation.
PRGO-01504: could not perform Oracle Grid Infrastructure home 'upgrade' for the specified working copy from Rapid Home Provisioning Client (RHPC) "{0}": Cause: The Oracle Grid Infrastructure home could not be upgraded because the working copy was not created by this Rapid Home Provisioning Client.; Action: Execute the command from the cluster that created this working copy or specify a different working copy.
PRGO-01505: failed to upgrade the Oracle Grid Infrastructure home because the source working copy "{0}" is incomplete: Cause: The source working copy was in a partially completed state.; Action: Retry the 'rhpctl upgrade gihome' command after ensuring that the source working copy has been created successfully or specify a different source working copy that is complete.
PRGO-01506: The specified destination working copy is incomplete.: Cause: The destination working copy was in a partially completed state.; Action: Retry the move or upgrade command after ensuring that the destination working copy has been created successfully or specify a different destination working copy that is complete.
PRGO-01507: invalid '-path' or '-image' option specified for upgrade of Oracle Grid Infrastructure home that was an existing destination working copy: 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.; Action: Retry the command without the '-path' and '-image' option.
PRGO-01522: User "{0}" lacks the authority to perform the 'query audit' operation.: Cause: The user running the 'rhpctl query audit' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01523: User "{0}" lacks the authority to perform the 'modify audit' operation.: Cause: The user running the 'rhpctl modify audit' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01524: User "{0}" lacks the authority to perform the 'delete audit' operation.: Cause: The user running the 'rhpctl delete audit' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01525: no target node specified: Cause: An attempt to delete an active working copy of type ORACLEGISOFTWARE was rejected because no target node was specified.; Action: Retry specifying the target node.
PRGO-01526: The specified node role "{0}" is not HUB or LEAF.: Cause: The previously submitted command was rejected because the specified node role was invalid.; Action: Retry the previously submitted command providing a valid node role, HUB or LEAF.
PRGO-01527: The value supplied for node "{0}" is invalid.: Cause: The command was rejected because the indicated value supplied as a node specification was invalid.; Action: Retry the command providing a node specification in the form "<node_name>" for an Application cluster, in the form "<node_name>:<node_vip>[:<node_role>]" for a Flex cluster, and in the form "<node_name>:<node_vip>" for a non-Flex cluster.
PRGO-01528: Modify operation failed because user action "{0}" does not exist.: Cause: An attempt to modify a user action failed because the user action did not exist.; Action: Specify the correct name of a user action that exists and retry the command.
PRGO-01529: The operation failed because the user action "{0}" did not execute successfully.: Cause: The operation failed because the indicated user action configured for the image did not execute successfully.; Action: Specify a different image or modify the user action to be non-fatal and retry the command.
PRGO-01530: Modify operation failed because image type "{0}" does not exist.: Cause: An attempt to modify an image type failed because the image type did not exist.; Action: Specify the correct name of an image type that exists and retry the command.
PRGO-01531: Failed to copy file "{0}" between Rapid Home Provisioning server and client. Detailed error:\n{1}: 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.; Action: Retry the command making sure that the file system is not full and the destination directory has requisite permissions.
PRGO-01534: failed to upgrade database "{0}" because the database does not exist on cluster "{1}": Cause: An attempt to upgrade a database failed because the indicated database was not registered with the Oracle Clusterware.; Action: Ensure the database is configured in the current cluster or provide the correct cluster name.
PRGO-01535: Working copy "{0}" is not an Oracle RAC home.: Cause: The attempted 'addnodes' or 'deletenodes' operation was rejected because the indicated working copy was an Oracle single-instance database home.; Action: None
PRGO-01536: Working copy "{0}" was not created by Rapid Home Provisioning Client "{1}".: Cause: The attemped operation was rejected because the indicated working copy was not created by the indicated Rapid Home Provisioning Client.; Action: Retry the command from the cluster that created this working copy.
PRGO-01537: cannot delete all nodes from working copy "{0}": 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.; Action: Use 'rhpctl delete workingcopy' to delete the indicated working copy.
PRGO-01538: Databases belonging to working copy "{0}" have instances running on nodes: "{1}".: 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.; Action: Retry after removing database instances running on the indicated nodes.
PRGO-01539: The base image type "{1}" of working copy "{0}" is incompatible with the requested operation.: Cause: An attempted 'addnodes' or 'deletenodes' operation was rejected because the base image type of the specified working copy was not ORACLEDBSOFTWARE.; Action: None
PRGO-01540: failed to extend working copy "{0}" to nodes "{1}": Cause: An attempt to extend the indicated Oracle RAC home to the indicated nodes failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages, address issues described and retry.
PRGO-01541: failed to remove working copy "{0}" from nodes "{1}": Cause: An attempt to remove the indicated Oracle RAC home from the indicated nodes failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages, address issues described and retry.
PRGO-01542: missing '{0}', '{1}' or '{2}' option for rapid home provisioning: Cause: The requested operation was rejected because either '-dbname' or '-datafileDestination' was specified without '-node', '-serverpool' or '-newpool'.; Action: Reissue the command with one of '-node', '-serverpool', or '-newpool'; or specify '-target' as STANDALONE.
PRGO-01543: illegal option '{0}' specified for single instance database provisioning: Cause: The specified option was invalid for single instance database provisioing.; Action: Reissue the command without the forbidden option.
PRGO-01544: Invalid -dbtemplate option specified for an image of base type other than ORACLEDBSOFTWARE: Cause: The query image command was rejected because -dbtemplate option was only supported for ORACLEDBSOFTWARE images.; Action: Retry the command without the -dbtemplate option.
PRGO-01545: invalid image type for working copy "{0}" deletion request from Rapid Home Provisioning Client: Cause: An attempt to delete a working copy of image type ORACLEGISOFTWARE from Rapid Home Provisioning Client was rejected.; Action: Run the 'delete workingcopy' command on Rapid Home Provisioning Server.
PRGO-01546: failed to delete Oracle Home with error:\n{0}: 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.; Action: Examine the accompanying error messages and address the issues as described to complete the Oracle Grid Infrastructure cleanup.
PRGO-01547: failed to detach Oracle Home\n{0}: 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.; Action: Examine the accompanying error messages and address the issues as described to complete the Oracle Grid Infrastructure cleanup.
PRGO-01548: failed to delete snapshot of the image "{0}"\n{1}: 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.; Action: Examine the accompanying error messages and address the issues as described to complete the Oracle Grid Infrastructure cleanup.
PRGO-01549: failed to unmount the NFS file system with error:\n{0}: 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.; Action: Examine the accompanying error messages and address the issues as described to complete the Oracle Grid Infrastructure cleanup.
PRGO-01550: User "{0}" is not authorized to perform the 'register user' operation for a different user.: 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.; Action: Contact your system administrator for the GH_USER_ADMIN role or perform the operation with a user ID having the GH_USER_ADMIN_ROLE.
PRGO-01551: User "{0}" is not authorized to perform the 'modify user' operation for a different user.: 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.; Action: Contact your system administrator for the GH_USER_ADMIN role or perform the operation with a user ID having the GH_USER_ADMIN_ROLE.
PRGO-01552: User "{0}" is not authorized to perform the 'unregister user' operation for a different user.: 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.; Action: Contact your system administrator for the GH_USER_ADMIN role or perform the operation with a user ID having the GH_USER_ADMIN_ROLE.
PRGO-01554: missing '-targetnode' option to move the source working copy of version "{0}": 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.; Action: Reissue the command specifying the '-targetnode' option.
PRGO-01555: Maximum wait time reached to advertise Rapid Home Provisioning Server with GNS: Cause: While looking up Rapid Home Provisioning Server connection details, an attempt to query Grid Naming Service (GNS) failed.; Action: Make sure that both the GNS and the Rapid Home Provisioning Server are running.
PRGO-01556: cannot retrieve the Oracle release version of the image from image path "{0}" while adding or importing a new image on node {1}.: Cause: An attempt to retrieve the Oracle release version of the image from an image path using SRVCTL and SQLPLUS failed.; Action: Examine the accompanying error messages, address the described issues, and retry.
PRGO-01557: cannot retrieve the Oracle release version of the image from image path "{0}" while adding or importing a new image on node {1}.: Cause: An attempt to retrieve the Oracle release version of the image from an image path using SQLPLUS failed.; Action: Examine the accompanying error messages, address the described issues, and retry.
PRGO-01558: Rapid Home Provisioning Server (RHPS) is not reachable.: Cause: An error occurred while attempting to connect to the Rapid Home Provisioning Server (RHPS), possibly because the RHPS was not running.; Action: Examine the accompanying errors for more information. Make sure the RHPS is running before retrying the command.
PRGO-01559: Inappropriate image type {0} of working copy {1} specified for 'rhpctl query working copy' on a cluster version earlier than 12.2: Cause: The requested operation was rejected because clients of versions earlier than 12.2 cannot query working copies based on image type ORACLEGISOFTWARE.; Action: Retry the command from a cluster of version 12.2 or higher
PRGO-01560: no target node specified: 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.; Action: Rerun the 'add workingcopy' command specifying the target node.
PRGO-01561: target node not required: 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.; Action: Rerun the 'add workingcopy' command without specifying the target node.
PRGO-01562: Cluster already exists on node "{0}" with Oracle home at path "{1}".: Cause: The requested operation was rejected because the indicated node was already a member of an existing Oracle Grid Infrastructure cluster.; Action: Retry the command specifying nodes that are not members of an existing Oracle Grid Infrastructure cluster.
PRGO-01565: failed to create gold image path: {0}: 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.; Action: Examine the accompanying error messages, address the issues described, and then retry.
PRGO-01566: failed to create the read/write path: {0}: 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.; Action: Examine the accompanying error messages, address issues described and retry.
PRGO-01567: The supplied path "{0}" is on ACFS resource "{1}", which is managed by the Rapid Home Provisioning application.: 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.; Action: Specify a working copy path that is not on an ACFS file system managed by the Rapid Home Provisioning application or retry, omitting the '-path' option to let the RHP choose the path on the RHP-managed ACFS file system.
PRGO-01568: unexpected option '-targetnode' specified for provisioning Oracle home on a Rapid Home Provisioning Client (RHPC) cluster: 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.; Action: Reissue the command specifying the '-client' option instead of the '-targetnode' option.
PRGO-01569: missing '-user' option for provisioning a workingcopy on a standalone target.: Cause: The '-user' option was missing for standalone provisioning.; Action: Reissue the command specifying the '-user' option.
PRGO-01571: The move operation was rejected because the patched working copy "{0}" is missing the patches for bug numbers "{1}" which are present in the source working copy "{2}".: Cause: Some patches were present in the source working copy that were missing in the patched working copy.; Action: Rerun the move command with the '-ignorewcpatches' option or specify a patched working copy with at least the same patches applied as the source working copy.
PRGO-01572: no target node specified: 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.; Action: Retry the move operation specifying the '-targetnode' option.
PRGO-01573: failed to retrieve information from source home "{0}": Cause: An attempt to query source home information failed.; Action: Examine the accompanying error messages for more information, address reported issues, and retry.
PRGO-01576: Specified operation is not supported on this entity in version {0} of Rapid Home Provisioning Clients.: Cause: The requested operation was rejected because it was not supported on clients of the indicated version.; Action: Retry the command from a cluster of higher version.
PRGO-01577: Destination working copy "{0}" already exists.: 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.; Action: Reissue the 'move gihome' command specifying a destination working copy that does not exist.
PRGO-01578: failed to move the Oracle Grid Infrastructure home because the software-only 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 destination working copy has more nodes than the source working copy.; Action: Specify a software-only destination working copy that is on the same set of nodes as the source working copy and retry the operation.
PRGO-01579: failed to upgrade the Oracle Grid Infrastructure home because the software-only 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.; Action: Specify a software-only destination working copy that is on the same set of nodes as the source working copy and retry the operation.
PRGO-01580: failed to move the Oracle Grid Infrastructure home because the software-only destination working copy did not have nodes {0} from 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.; Action: Specify a software-only destination working copy that is on the same set of nodes as the source working copy and retry the operation.
PRGO-01581: failed to upgrade the Oracle Grid Infrastructure home because the software-only destination working copy did not have nodes {0} from the source working copy: 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.; Action: Specify a software-only destination working copy that is on the same set of nodes as the source working copy and retry the operation.
PRGO-01582: illegal specification of disk group "{0}" for provisioning single instance database on a non-cluster node: 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.; Action: Reissue the command, either specifying a path for the '-datafileDestination' option or omitting it altogether.
PRGO-01583: missing '-targetnode' option for deleting Oracle RAC home on a cluster that has no RHP client: 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.; Action: Reissue the command specifying the '-targetnode' option.
PRGO-01584: missing '-targetnode' option for deleting Oracle RAC database on a cluster that has no RHP client: 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.; Action: Reissue the command specifying the '-targetnode' option.
PRGO-01585: spurious '-node' option for delete: Cause: The '-node' option was specified on an operation that does not need it.; Action: Reissue the command without the '-node' option.
PRGO-01586: invalid cluster name "{0}": 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.; Action: Specify a valid cluster name and retry the operation.
PRGO-01587: illegal '-agpath' option provided where source working copy is 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 provided when source working copy was already based on an Oracle Layered File System.; Action: Reissue the 'rhpctl move gihome' command without specifying the '-agpath' option.
PRGO-01588: illegal '-path' option provided where source working copy is 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.; Action: Reissue the 'rhpctl move gihome' command without specifying the '-path' option.
PRGO-01589: illegal '-aupath' and '-agpath' option for image version earlier than 12.2: 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.; Action: Reissue the 'add workingcopy' command specifying neither the '-agpath' nor the '-aupath' option or specify an image with version 12.2 or later.
PRGO-01590: No target node specified.: 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.; Action: Retry the 'rhpctl deletenode gihome' command specifying the target node.
PRGO-01591: Delete node with '-targetnode' option rejected.: 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.; Action: Retry the 'rhpctl deletenode gihome' command without specifying the '-targetnode' option.
PRGO-01592: Nodes "{0}" are not part of working copy "{1}".: Cause: An attempt to delete nodes from a working copy was rejected because the specified nodes were not part of the working copy.; Action: Retry the 'rhpctl deletenode gihome' command specifying nodes that are part of the working copy.
PRGO-01593: illegal attempt to delete all Hub nodes "{0}": 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.; Action: If appropriate, retry the 'rhpctl deletenode gihome' command with fewer nodes.
PRGO-01594: illegal attempt to delete all nodes "{0}": 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.; Action: Retry the 'rhpctl deletenode gihome' command specifying a node list that does not contain all of the nodes in the working copy, or use the 'rhpctl delete workingcopy' command to remove the working copy.
PRGO-01595: missing mandatory option '{0}' for a 'move database' or 'upgrade database' operation on a cluster whose version is older than 12.2: Cause: An attempt was made to move or upgrade a database without specifying the indicated option.; Action: Specify the indicated option and retry the command.
PRGO-01596: unexpected option '-targetnode' specified for moving a database from working copy "{0}" which is a single instance Oracle home: Cause: An attempt to move a database was rejected because the '-targetnode' option was not needed.; Action: Retry the operation without specifying the '-targetnode' option.
PRGO-01597: illegal '-force' option provided: 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.; Action: Reissue the 'rhpctl delete workingcopy' command without specifying the '-force' option.
PRGO-01598: Patched working copy "{0}" is not a single-instance Oracle home.: 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.; Action: Retry the command specifying a single-instance Oracle home for the patched working copy.
PRGO-01599: Oracle Grid Infrastructure home upgrade failed with destination working copy version "{0}" earlier than or equal to the source working copy version "{1}": 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.; Action: Ensure that the destination working copy version is later than the source working copy version.
PRGO-01600: missing mandatory option '-aupath' where the source working copy is 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 '-aupath' option was not provided when the source working copy was based on an Oracle Layered File System.; Action: Reissue the 'rhpctl move gihome' command specifying the '-aupath' option.
PRGO-01601: missing mandatory option '-agpath': Cause: An attempt to move to an Oracle home based on an Oracle Layered File System failed because the '-agpath' option was not provided.; Action: Reissue the 'rhpctl move gihome' command specifying the '-agpath' option.
PRGO-01602: missing mandatory option '-path': Cause: An attempt to move to an Oracle home based on an Oracle Layered File System failed because the '-path' option was not provided.; Action: Reissue the 'rhpctl move gihome' command specifying the '-path' option.
PRGO-01603: unexpected option '-softwareonly' specified when adding working copy "{0}" from an image of base type other than ORACLEGISOFTWARE: 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.; Action: Retry the operation without specifying the '-softwareonly' option.
PRGO-01608: Cluster {0} is already being moved from working copy {1} to working copy {2}.: Cause: An attempt to move the indicated cluster was rejected because the indicated cluster was not completely moved between the indicated working copies.; Action: Retry after completing or reverting the ongoing move operation.
PRGO-01609: Cluster {0} is already being moved from Oracle home at {1} to working copy {2}.: 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.; Action: Retry after completing or reverting the ongoing move operation.
PRGO-01610: No cluster is being moved to working copy {0}.: 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.; Action: None
PRGO-01612: Unexpected option '{0}' specified for 'move' operation on a cluster of version {1}.: Cause: The attempted 'move' operation was rejected because the specified option was not supported for the indicated cluster version.; Action: Retry the command without the specified option.
PRGO-01613: illegal attempt to provision a working copy with a policy-managed database on storage managed by RHP for a cluster with Leaf Nodes: 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).; Action: Specify LOCAL or NFS for the '-storagetype' option for the provisioning of Oracle database home on all nodes of the cluster.
PRGO-01614: missing '-path' option for creating destination working copy: 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.; Action: Retry the command specifying the '-path' option.
PRGO-01615: missing '-responsefile' option for creating Oracle Grid Infrastructure working copy that is not software-only: 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.; Action: Retry the command specifying the '-responsefile' option or specifying '-softwareonly' option for software-only provisioning.
PRGO-01618: The groups "{0}" of the source home do not match the groups "{1}" of the patched working copy.: Cause: An attempt to move or upgrade the database failed because the source groups and patched working copy groups were different.; Action: Create or specify a patched working copy with the same groups as the source home and retry the move or upgrade database operation.
PRGO-01619: The groups "{0}" of the source home are not configured in the patched working copy.: Cause: An attempt to move or upgrade the database failed because some of the source groups were not configured in the patched working copy.; Action: Create or specify a patched working copy which contains the missing groups and retry the move or upgrade database operation.
PRGO-01620: The groups "{0}" of the patched working copy are not configured in the source home.: Cause: An attempt to move the database failed because some of the patched working copy groups were not configured in the source home.; Action: Create or specify a patched working copy which does not contain the additional groups and retry the move database operation.
PRGO-01623: A previously failed 'addnode' operation with nodelist "{0}" exists. Use '-force' option to override.: 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.; Action: Reissue the command 'rhpctl addnode gihome' either specifying a node list that is a proper subset of the indicated node list of the failed 'addnode' operation or specifying the '-force' option to clear the previously failed 'addnode' operation.
PRGO-01624: A complete working copy was not found on the specified client {0}.: Cause: An attempt to add nodes to a cluster was rejected because a complete working copy was not found on the specified client.; Action: Reissue the command 'rhpctl addnode gihome' either after performing a 'move gihome' operation on the specified client, or specifying a client with a complete working copy.
PRGO-01627: The groups "{0}" of the Oracle Grid Infrastructure home do not match the groups "{1}" of the patched working copy.: 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.; Action: Create or specify a patched working copy with the same groups as the source home and retry the command.
PRGO-01628: The groups "{0}" of the Oracle Grid Infrastructure home are not configured in the patched working copy.: 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.; Action: Create or specify a patched working copy which contains the missing groups and retry the command.
PRGO-01629: The groups "{0}" of the patched working copy are not configured in the Oracle Grid Infrastructure home.: 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.; Action: Create or specify a patched working copy which does not contain the additional groups and retry the command.
PRGO-01630: Disk group "{0}" already exists on the target system.: Cause: The attempted 'verify client' operation failed because the disk group name provided in the response file already existed on the target system.; Action: Specify a different disk group name in the response file.
PRGO-01632: Improper '-dbversion' option specified with image type with base type ORACLEGISOFTWARE.: 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.; Action: Either specify the version with '-version' option or specify an image type with base type ORACLEDBSOFTWARE and retry the command.
PRGO-01633: unexpected option '-responsefile' specified when adding working copy "{0}" from an image of base type other than ORACLEGISOFTWARE: 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.; Action: Retry the operation without specifying the '-responsefile' option.
PRGO-01634: Invalid '-sourcehome' option specified for 'move gihome' operation.: Cause: The '-sourcehome' option value specified is not a valid absolute path for the source home.; Action: Supply a valid source home path and retry.
PRGO-01635: unable to retrieve group information for user "{0}": Cause: An attempt to retrieve the indicated user's group information using the 'id' command failed.; Action: Examine the accompanying error messages, address the described issues, and retry.
PRGO-01636: Oracle Inventory already exists on nodes "{0}".: Cause: An attempt to add a working copy was rejected as Oracle Inventory exists on the indicated nodes.; Action: Reissue the 'add working copy' command after cleaning up the Oracle Inventory on the indicated nodes. Refer to the Oracle documentation for details.
PRGO-01637: The '-asmclientdata' option required for creating a working copy on an application cluster is not specified.: Cause: An attempt to create a working copy on an application cluster was rejected because the '-asmclientdata' option was not specified.; Action: Retry the 'rhpctl add workingcopy' command specifying the '-asmclientdata' option.
PRGO-01638: The GI home of cluster {0} is not an RHP working copy.: 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).; Action: Execute the 'rhpctl move gihome' operation for the specified cluster and retry the 'rhpctl deletenode gihome' operation, or retry the 'rhpctl deletenode gihome' operation specifying a client with a complete working copy.
PRGO-01640: failed to validate that Oracle home "{0}" on node {1} is of platform {2}: 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.; Action: Examine the accompanying error messages for more information, address the reported issues, and retry.
PRGO-01641: The specified user "{0}" is not registered with an email address to receive email notifications.: Cause: An attempt to subscribe to a series failed because the specified user did not have a registered email address.; Action: Execute the command with a user having a registered email address.
PRGO-01642: destination working copy "{0}" is not based on Oracle Layered File System: 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.; Action: Reissue the 'move gihome' command specifying a destination working copy that is based on an Oracle Layered File System.
PRGO-01646: Working copy "{0}" is not provisioned on this RHP Client.: 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.; Action: Either 1) Retry the command on the RHP Client where the specified working copy is provisioned, or 2) Retry the command from the RHP Server.
PRGO-01647: Database "{0}" is a single-instance database.: Cause: An attempt to add or delete an instance of the indicated database was rejected because single-instance databases do not support these operations.; Action: None
PRGO-01648: Working copy '{0}' is an Oracle single-instance database home.: Cause: An attempt to add or delete a database instance was rejected because single-instance databases do not support these operations.; Action: None
PRGO-01649: The base image type "{0}" of working copy "{1}" is incompatible with 'addnode database' and 'deletenode database'.: 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.; Action: Specify a working copy with base image type ORACLEDBSOFTWARE and retry the command.
PRGO-01650: Database "{0}" is not running.: Cause: An attempt to add or delete an instance of the specified database was rejected because the database was not running.; Action: Start the specified database and retry the command.
PRGO-01651: Database "{0}" is not an administrator-managed database.: 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.; Action: Refer to the product documentation for details on how to add or delete instances of a policy-managed database.
PRGO-01653: An invalid value "{0}" for the cluster type parameter was specified in the response file: Cause: An attempt to validate the response file or provision; Action: Refer to the product documentation for valid cluster type values.
PRGO-01654: 'addnode' and 'deletenode' for an Oracle Grid Infrastructure home is not supported by the Rapid Home Provisioning Client.: 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.; Action: Retry the command from the Rapid Home Provisioning Server.
PRGO-01655: Rolling patch is not possible because there is only one active Hub Node. Specify the '-nonrolling' option to perform non-rolling patch.: Cause: An attempt to perform a rolling patch was rejected because there was only one active Hub Node on the client cluster.; Action: Reissue the command 'move gihome' providing the '-nonrolling' option to perform non-rolling patch.
PRGO-01656: specified destination working copy has different Oracle base "{0}" from source working copy "{1}": Cause: An attempt to move to the specified working copy failed because it had a different Oracle base from the indicated source working copy.; Action: Reissue the command 'move gihome' specifying a destination working copy that has the same Oracle base as the source working copy.
PRGO-01657: The -targetnode and either the -root or -sudouser option must be specified.: 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.; Action: Retry the operation specifying the -targetnode and either the -root or the -sudouser option.
PRGO-01660: unsupported option '-local' specified when adding working copy "{0}" from an image of base type other than ORACLEGISOFTWARE: 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.; Action: Retry the operation without specifying the '-local' option.
PRGO-01661: The specified command is not supported on version "{0}".: Cause: The attempted operation was rejected because it was not supported for the indicated version.; Action: Refer to the product documentation for the supported version and retry.
PRGO-01662: The specified command is not supported.: Cause: The attempted operation was rejected because it was not supported.; Action: Refer to the product documentation.
PRGO-01664: The specified source working copy "{0}" is a software-only working copy.: 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.; Action: Retry the operation specifying an active, configured Oracle Grid Infrastructure home as the source.
PRGO-01666: deleting the last instance of database "{0}" is not permitted: 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.; Action: Retry the operation specifying a subset of instances.
PRGO-01667: The database "{0}" does not belong to working copy "{1}".: Cause: An attempt to operate on the specified database was rejected because the specified database does not belong to the specified working copy.; Action: Retry the operation specifying a database with its associated working copy.
PRGO-01668: The value supplied "{0}" for cluster node is more or less than the required information.: Cause: The command was rejected because the indicated value supplied as a node specification was either more or less than the required information.; Action: Retry the command providing a node specification in the form "<node_name>" for an Application cluster, in the form "<node_name>:<node_vip>[:<node_role>]" for a Flex cluster, and in the form "<node_name>:<node_vip>" for a non-Flex cluster.
PRGO-01669: Invalid credentials option specified for target node {0} belonging to cluster {1}, which is of version 12.2 or higher, and which has RHPC 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 enabled.; Action: Retry the operation using the -client option instead of the -sudouser or -root options.
PRGO-01670: Invalid credentials option was specified for target node {0} belonging to cluster {1}, which is of version 12.2 or higher, and which has the RHPC 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 disabled.; Action: Enable the RHPC on the indicated cluster, then retry the operation using the -client option instead of the -sudouser or -root options.
PRGO-01671: Invalid credentials option specified for target node {0} belonging to cluster {1}, which is of version 12.2 or higher, and where RHPC is not configured.: 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.; Action: Configure and start an RHPC on the indicated cluster, then retry the operation using the -client option instead of the -sudouser or -root options.
PRGO-01672: First node "{0}" is not a Hub Node.: Cause: An attempt to patch Oracle Clusterware was rejected because the indicated node, specified as the first node, was not a Hub Node.; Action: Reissue the command specifying a Hub Node as the first node.
PRGO-01673: An invalid value "{0}" for the cluster configuration parameter was specified in the response file: Cause: An attempt to validate the response file or provision; Action: Refer to the product documentation for valid
PRGO-01674: error while importing the client cluster certificate: Cause: An error occurred while importing the client cluster certificate.; Action: Examine the accompanying errors for more information, address issues and retry.
PRGO-01675: failed to delete working copy\n{0}: Cause: An attempt to delete working copy failed during the cleanup of the Oracle Grid Infrastructure. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages, address the described issues, and retry.
PRGO-01676: Re-execution of 'add workingcopy' rejected because the file '{0}' specified by response file parameter '{1}' differs from the one originally specified.: Cause: Re-execution of the 'add workingcopy' command failed because the file contents did not match the one used for the original execution.; Action: Retry the command with the same file contents used for the first execution of the command.
PRGO-01677: The specified target node "{0}" option is invalid for the cluster of version "{1}".: 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.; Action: Reissue the command after revising the target node option.
PRGO-01678: Option '-continue' is supported only for batch and smart move operations.: 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.; Action: Resume the move operation by reissuing the command with the options that were originally specified.
PRGO-01679: The specified node "{0}" is not a part of the specified cluster "{1}".: Cause: The command was rejected because the indicated node was not a member of the indicated cluster.; Action: Reissue the command with a valid pair of cluster and node name.
PRGO-01684: Option -client is invalid when executing from an RHPC 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.; Action: Reissue the command without specifying the -client option.
PRGO-01685: Oracle home "{0}" does not exist on nodes "{1}".: 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.; Action: If the indicated home is an Oracle RAC home, specify a node using -targetnode on which the home does exist, or specify -force to remove the working copy metadata.
PRGO-01686: Move of gihome is not allowed from Rapid Home Provisioning Client where both the source and the destination working copies are based on the Oracle Layered File System.: 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.; Action: Reissue the 'move gihome' command from the Rapid Home Provisioning Server.
PRGO-01687: failure to add node "{0}" because the GNS is not configured: 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.; Action: Specify a Hub Node or configure the GNS using the command 'srvctl add gns' and retry the operation.
PRGO-01688: The '-clustermanifest' option required for creating a working copy on an application cluster is not specified.: Cause: An attempt to create a working copy on an application cluster was rejected because the '-clustermanifest' option was not specified.; Action: Retry the 'rhpctl add workingcopy' command specifying the '-clustermanifest' option.
PRGO-01689: The target node option is specified for the cluster of version "{0}".: 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.; Action: Reissue the command without specifying the target node option.
PRGO-01690: The -targetnode and either the -root or -sudouser option must be specified.: 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.; Action: Retry the operation specifying the -targetnode and either the -root or the -sudouser option.
PRGO-01691: The move operation was rejected because the patched working copy "{0}" is missing the patches for bug numbers "{1}" which are present in the source Oracle home "{2}".: Cause: Some patches were present in the source Oracle home that were missing in the patched working copy.; Action: Rerun the move command with the '-ignorewcpatches' option or specify a patched working copy with at least the same patches applied as the source Oracle home.
PRGO-01693: The database patching cannot be completed in a rolling manner because the target patched home at "{0}" contains non-rolling bug fixes "{1}" compared to the source home at "{2}".: Cause: The bug numbers listed are marked as non-rolling in the metadata, and therefore cannot be applied in a rolling manner.; Action: Reissue the command specifying the '-nonrolling' option to complete the database patching in a non-rolling manner or remove the listed patches from the target patched home and continue to patch in a rolling manner.
PRGO-01694: The 'setupSSH' option is not supported for images whose version is earlier than 12.2.: Cause: An attempt to set up passwordless SSH user equivalence was rejected because the image was of a version earlier than 12.2.; Action: None
PRGO-01695: The credentials required for passwordless SSH user equivalence set up are missing.: Cause: An attempt to set up passwordless SSH user equivalence using the '-setupSSH' option of rhpctl was rejected because the required credentials were missing.; Action: Provide the credentials needed for passwordless SSH user equivalence set up and retry the operation.
PRGO-01696: Rapid Home Provisioning pre-check failed.: Cause: Rapid Home Provisioning pre-check failed on the cluster to be provisioned. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages, address the issues described, and retry.
PRGO-01697: Rapid Home Provisioning pre-check failed because SSH user equivalence was not set up on the remote nodes.: 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.; Action: Run the 'rhpctl verify client' command with the '-fixup' and '-setupSSH' options to set up passwordless SSH user equivalence and retry the provisioning operation.
PRGO-01698: File "{0}" already exists.: Cause: An attempt to export the Rapid Home Provisioning (RHP) schema to the specified file failed because the file already existed.; Action: Remove or rename the existing file or specify a file that does not exist and retry the command.
PRGO-01699: More than one node is specified for provisioning a single instance database home.: Cause: The number of nodes specified for a single instance database home provisioning was greater than one.; Action: Specify only one node for the -node option.
PRGO-01700: Failure occurred while adding user "{0}" to authorize operations on the Oracle ACFS file system using volume device "{1}".: 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.; Action: Examine the accompanying error messages, address the issues described, and retry the operation.
PRGO-01701: failure to copy Oracle home "{0}" to node "{1}": Cause: An attempt to copy the specified Oracle home to the given node encountered a failure. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages, address the issues described, and retry the operation.
PRGO-01702: Failure occurred while provisioning an Oracle home.: Cause: An attempt to provision an Oracle home encountered a failure. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages, address the issues described, and retry the operation.
PRGO-01703: Failure occurred while provisioning an Oracle Grid Infrastructure working copy "{0}".: Cause: An attempt to provision an Oracle Grid Infrastructure working copy encountered a failure. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages, address the issues described, and retry the operation.
PRGO-01704: Failure occurred while deconfiguring an Oracle Grid Infrastructure cluster.: Cause: An attempt to deconfigure an Oracle Grid Infrastructure cluster encountered a failure. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages, address the issues described, and retry the operation.
PRGO-01705: Failure occurred while adding client "{0}".: Cause: An attempt to add a client encountered a failure. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages, address the issues described, and retry the operation.
PRGO-01706: Failure occurred while adding nodes "{0}" to an Oracle Grid Infrastructure cluster.: Cause: An attempt to add the specified nodes to an Oracle Grid Infrastructure cluster encountered a failure. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages, address the issues described, and retry the operation.
PRGO-01707: Failure occurred while executing Cluster Verification Utility.: Cause: An attempt to execute a command using the Cluster Verification Utility encountered a failure. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages, address the issues described, and retry the operation.
PRGO-01708: Failure occurred while executing discover client operation.: Cause: An attempt to execute a discover client operation encountered a failure. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages, address the issues described, and retry the operation.
PRGO-01709: Failure occurred while upgrading an Oracle Grid Infrastructure cluster.: Cause: An attempt to upgrade an Oracle Grid Infrastructure cluster encountered a failure. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages, address the issues described, and retry the operation.
PRGO-01710: Failure occurred while moving Oracle Grid Infrastructure home "{0}" to "{1}".: 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.; Action: Examine the accompanying error messages, address the issues described, and retry the operation.
PRGO-01711: Failure occurred during export of credentials for client "{0}".: Cause: An attempt to export the credentials for the specified client encountered a failure. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages, address the issues described, and retry the operation.
PRGO-01712: failure to retrieve the Rapid Home Provisioning Server user: Cause: An attempt to retrieve the Rapid Home Provisioning server user encountered a failure. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages, address the issues described, and retry the operation.
PRGO-01713: failure to retrieve working copy "{0}" information: Cause: An attempt to retrieve the specified working copy information encountered a failure. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages, address the issues described, and retry the operation.
PRGO-01714: Failure occurred during deletion of database "{0}" at Oracle home location "{1}".: Cause: An attempt to delete the specified database at the indicated Oracle home location encountered a failure. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages, address the issues described, and retry the operation.
PRGO-01716: The site version {0} is lower than the destination working copy version {1}.: Cause: An attempt to upgrade an Oracle RAC database failed because the site version was lower than the destination working copy version.; Action: Ensure that the destination working copy version is equal to or lower than the site version.
PRGO-01717: Databases "{0}" are currently being moved from working copy {1} to working copy {2}.: Cause: An attempt to move databases was rejected because the indicated databases were not completely moved between the indicated working copies.; Action: Retry after completing or reverting the ongoing move operation.
PRGO-01718: Databases "{0}" are currently being moved from Oracle home at {1} to working copy {2}.: 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.; Action: Retry after completing or reverting the ongoing move operation.
PRGO-01719: Option '-continue' is supported only for batch and smart move operations.: 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.; Action: Resume the move operation by reissuing the command with the options that were originally specified. Revert the move operation by swapping the values for options '-sourcewc' and '-destwc' in the original command. Do not specify the '-continue' option.
PRGO-01720: Rapid Home Provisioning pre-check fails with warning messages.: Cause: The Rapid Home Provisioning pre-check failed with warning messages on the cluster to be provisioned. The accompanying messages provide detailed information.; Action: Examine the accompanying warning messages, address the described issues, and retry, or ignore the warnings.
PRGO-01721: invalid '-oraclebase' option provided for provisioning a software-only GI working copy where '-local' was not specified and the local node is not a member of the 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 '-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.; Action: When provisioning a software-only Oracle Grid Infrastructure working copy for the local node in RHPS cluster, specify the '-oraclebase' option and the '-local' option. The '-local' option is not supported for nodes in client clusters.
PRGO-01722: unable to delete working copy {0} because the home path is different across nodes "{1}": Cause: An attempt to delete the indicated working copy was rejected because the home path was different across nodes.; Action: Perform the necessary steps to complete any earlier patching or upgrade operation and ensure that the home path is same on all nodes before attempting to delete the working copy.
PRGO-01723: The specified target node "{0}" is a part of the RHPS cluster.: 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.; Action: Reissue the command with a target node outside of the RHPS cluster.
PRGO-01724: missing '-path' option when '-local' option was not specified: 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.; Action: Retry the command specifying the '-path' option.
PRGO-01725: Removing node {0} as a candidate server for Oracle RAC One Node database {1} is not permitted.: 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.; Action: Retry the operation specifying a different node or reissue the same command after relocating the specified database.
PRGO-01726: Option -{0} is invalid when executing from an RHPC cluster.: Cause: An attempt to execute an operation was rejected because the specified option was not allowed on a Rapid Home Provisioning Client (RHPC) cluster.; Action: Reissue the command specifying a valid option.
PRGO-01728: failed to parse the date "{0}": Cause: An attempt to execute an operation was rejected because the indicated date specification did not conform with the format "yyyy-MM-dd".; Action: Retry the operation specifying a valid date.
PRGO-01729: Database "{0}" has no instances configured on nodes: "{1}".: 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.; Action: None
PRGO-01730: User "{0}" lacks the authority to perform the 'enable osconfig' operation.: Cause: An attempt to run the command 'rhpctl enable osconfig' was rejected because the user did not have root or Administrator privileges.; Action: Retry the command from a user ID that has root or Administrator privileges.
PRGO-01731: User "{0}" lacks the authority to perform the 'disable osconfig' operation.: Cause: An attempt to run the command 'rhpctl disable osconfig' was rejected because the user did not have root or Administrator privileges.; Action: Retry the command from a user ID that has root or Administrator privileges.
PRGO-01732: No working copy is configured on cluster "{0}".: 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.; Action: Retry the operation after provisioning working copies from images of type ORACLEDBSOFTWARE on the indicated cluster.
PRGO-01733: No database in cluster "{0}" is being moved.: 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.; Action: Retry the operation after ensuring that the inputs for options: '-dbhomes', '-only', and '-except' are not excluding all databases in the indicated cluster from being patched.
PRGO-01734: No database exists in cluster "{0}".: Cause: An attempt to patch Oracle databases in the specified cluster using the '-auto' option failed because no database existed in the cluster.; Action: Reissue the command without specifying the '-auto' option.
PRGO-01735: Working copy "{0}" is not a valid patched working copy for source working copy "{1}".: 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.; Action: Examine the accompanying messages and resolve any issues identified there. Reissue command specifying a valid pairing of source working copy to the patched working copy using the '-dbhomes' option.
PRGO-01740: Working copy "{0}" is not a valid patched working copy for source Oracle home "{1}".: 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.; Action: Examine the accompanying messages and resolve any issues identified there. Reissue the command specifying a valid pairing of source Oracle home to patched working copy using the '-dbhomes' option.
PRGO-01750: One or more of the specified batches contain multiple nodes.: 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.; Action: Retry the operation ensuring that every batch contains only one node.
PRGO-01754: Batches "{0}" have already been completed.: 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.; Action: Retry the operation specifying nodes that have not been patched.
PRGO-01755: The option '-targetnode' is invalid when adding a working copy for an image of type '{0}'.: Cause: An attempt to add a working copy for the indicated image type was rejected because an invalid option ('-targetnode') was specified.; Action: Rerun the command 'add workingcopy' specifying the '-node' option instead of the '-targetnode' option.
PRGO-01756: The patched working copy "{0}" is missing the mandatory patches for bug numbers "{1}".: 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.; Action: Apply the mandatory patches in the patched working copy or specify an image with the mandatory patches to create the patched working copy, and then retry the command.
PRGO-01757: The groups "{0}" specified in the '-groups' option in the command 'add workingcopy' is missing one or more groups for this image type and version.: 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.; Action: Reissue the command with all valid groups for this image type and version. Valid group keywords for Grid Infrastructure Provisioning: Versions 11.2,12.1,12.2: OSDBA,OSOPER,OSASM Valid group keywords for Database Provisioning: Version 11.2: OSDBA,OSOPER Version 12.1: OSDBA,OSOPER,OSBACKUP,OSDG,OSKM Version 12.2: OSDBA,OSOPER,OSBACKUP,OSDG,OSKM,OSRAC
PRGO-01758: 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 Infrastructure Management Repository disk group were specified in the response file.; Action: Refer to the product documentation for valid Grid Infrastructure Management Repository disk group settings for configuring Oracle Domain Services Cluster. Specify the required details to create a new disk group in the response file and retry the command.
PRGO-01759: invalid configuration details specified for configuring Grid Naming Service 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.; Action: Refer to the product documentation for valid Grid Naming Service settings for configuring Oracle Domain Services Cluster. Specify the required details to create Grid Naming Service in the response file and retry the command.
PRGO-01760: storage type other than LOCAL specified for provisioning an Oracle home 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 storage type specified was not LOCAL.; Action: Retry the command specifying the storage type as LOCAL or by leaving it unspecified and accepting the default.
PRGO-01761: Rapid Home Provisioning precheck failed because of invalid value or values in the response file "{0}": Cause: Rapid Home Provisioning precheck failed on the cluster that was to be provisioned. The accompanying messages provide detailed failure information.; Action: Modify the response file to address the issues described by the accompanying messages, and retry the operation.
PRGO-01762: cannot complete the delete-database operation because there was no instance of database "{0}" running on any node: 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.; Action: Start an instance of the database, if necessary, by first adding the working copy for the indicated database on at least one node.
PRGO-01763: unable to delete working copy "{0}" because the remote cluster has other active Oracle homes in the inventory: 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.; Action: Perform the necessary steps to remove other active Oracle homes on the remote cluster before attempting to delete the specified working copy.
PRGO-01766: The specified target node "{0}" is one of the new nodes to be added to the 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.; Action: Reissue the command, specifying one of the existing nodes as the target node.
PRGO-01767: The nodes "{0}" to be added already exist in the cluster.: Cause: An attempt to add nodes to a cluster was rejected because the indicated nodes were already part of cluster.; Action: Reissue the command, excluding nodes that are already part of the cluster.
PRGO-01768: Failed to delete image series "{0}" because there are users subscribed to it.: Cause: An attempt to delete an image series failed because there were users subscribed to it.; Action: Unsubscribe all users from the series and reissue the command.
PRGO-01769: Cluster nodes string "{0}" has roles specified which are not valid unless provisioning an Oracle Flex Cluster.: Cause: An attempt to add a working copy was rejected because node roles were specified when provisioning a non-flex Cluster.; Action: Specify the value for the cluster nodes in the form "<node_name>:<node_vip>" or specify the cluster type as FLEX.
PRGO-01770: illegal combination of options '-node' and '-targetnode': 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.; Action: Reissue the command specifying either '-targetnode' or '-node', but not both.
PRGO-01771: The site version {0} was lower than the image version {1}.: Cause: An attempt to provision an Oracle RAC database failed because the site version was lower than the image version.; Action: Retry the command, specifying an image whose version is less than or equal to the version of this site.
PRGO-01772: invalid storage type 'NFS' specified for pre-12.2 cluster: Cause: An attempt to provision a working copy on NFS storage was rejected because the target cluster version was not 12.2 or later.; Action: Reissue the command specifying a non-NFS storage type.
PRGO-01773: The compressed file {0} is not valid for import.: Cause: An attempt to import an image from the specified home failed. The indicated file was either non-existent or was corrupted.; Action: Retry the operation specifying a valid compressed file.
PRGO-01774: The evaluation revealed potential failure for command "{0}".: 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.; Action: Examine the accompanying messages, resolve the issues, and then retry the operation.
PRGO-01775: "{0}" operation on the client side is skipped for the cluster "{1}" of version "{2}".: Cause: This operation was not supported on the client site of the indicated version.; Action: Not an error.
PRGO-01776: Only one server pool should be provided when adding a single instance database.: Cause: An attempt to add a single instance database was rejected because more than one server pool was specified.; Action: Retry the operation specifying only one server pool.
PRGO-01777: The cluster manifest file "{0}" is invalid for cluster "{1}": 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.; Action: Retry the command supplying a valid cluster manifest file.
PRGO-01778: failed to validate the cluster manifest file "{0}" for cluster "{1}": 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.; Action: Modify the cluster manifest file to address the issues described by the accompanying messages, and retry the operation.
PRGO-01779: The specified local path "{0}" is invalid.: 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.; Action: Ensure that the specified path directory or its parent directory is writable and has sufficient free space.
PRGO-01780: Series "{0}" has no images.: Cause: An attempt to add a workingcopy was rejected because the indicated series had no images.; Action: Add at least one image to the specified series, and then retry the operation.
PRGO-01781: User "{0}" lacks the authority to perform the 'add workingcopy' operation on all of the images in the image series "{1}".: 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.; Action: Request authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01782: The image "{0}" in state "{1}" was skipped from the image series "{2}" as the user "{3}" lacks the authority to perform the 'add workingcopy' operation on it.: Cause: The user running the 'rhpctl add workingcopy' command with the '-series' option did not have the required authorization for the image specified.; Action: Request authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-01800: error encountered during update Oracle Database Appliance client operation: Cause: An attempt to update an Oracle Database Appliance client encountered a failure. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages, address the issues described, and retry the operation.
PRGO-01801: unpacked Oracle Database Appliance patch bundle version "{0}" does not match the image version "{1}": Cause: An attempt to update an Oracle Database Appliance client failed because the unpacked patch bundle version was different from the image version.; Action: Retry the command specifying the deployed image or execute the command 'rhpctl deploy image' to deploy the specified image.
PRGO-01802: unpacked Oracle Database Appliance patch bundle version "{0}" on node "{1}" does not match the patch bundle version "{2}" on node "{3}": Cause: An attempt to update an Oracle Database Appliance (ODA) client failed because the unpacked patch bundle version was different on the two nodes.; Action: Retry the command after executing the command 'rhpctl deploy image' to deploy the specified image on both nodes.
PRGO-01803: Oracle Database Appliance cluster has "{0}" nodes: Cause: An attempt to update an Oracle Database Appliance (ODA) client failed because the ODA cluster did not have two nodes.; Action: Reissue the command specifying the correct target node.
PRGO-01807: components not updated: on node '{0}' {1} and on node '{2}' {3}: 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.; Action: Examine the oakcli update command output, resolve the problems identified there, and then retry the operation.
PRGO-01809: User interrupt caught. Commands already running on remote node will continue to execute.: Cause: An attempt to update an Oracle Database Appliance client failed because the user interrupted the command.; Action: Reissue the command.
PRGO-01810: node '{0}' down for more than {1} minutes: Cause: An attempt to update an Oracle Database Appliance client failed. The node was down for an unexpected amount of time.; Action: Reissue the command after the node is up again.
PRGO-01811: error while executing the oakcli command '{0}': Cause: An attempt to update an Oracle Database Appliance client failed. There was an error while executing the oakcli update command.; Action: Examine the oakcli update command output, resolve the problems identified there, and then retry the operation.
PRGO-01812: The ODA patch version "{0}" is not recognized.: 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).; Action: Ensure that the specified image is of the correct version and patching for that version is supported through RHP, and then retry the operation.
PRGO-01813: error encountered during deploy image operation: Cause: An attempt to deploy an Oracle Database Appliance image encountered a failure. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages, address the described issues, and retry the operation.
PRGO-01814: The image path specified contains invalid files "{0}": 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.; Action: Reissue the command specifying the correct path.
PRGO-01815: The image version "{0}" specified is invalid.: Cause: An attempt to deploy an Oracle Database Appliance (ODA) image was rejected because an invalid image version was specified.; Action: Reissue the command specifying a valid ODA patch version.
PRGO-01816: The '-version' option required for importing an image of type ODAPATCHSOFTWARE is not specified.: Cause: An attempt to import the image was rejected because; Action: Retry the command specifying the '-version' option.
PRGO-01817: invalid option '-version' specified: Cause: An attempt to import an image was rejected because the '-version' option was specified, but is only allowed for images of type ODAPATCHSOFTWARE.; Action: Retry the command without the '-version' option.
PRGO-01818: The '-batch' option is not allowed for this patch since the storage components {0} must be updated.: 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.; Action: Retry the command without the '-batch' option.
PRGO-01820: components not updated: on node '{0}' {1}: Cause: An attempt to update Oracle Database Appliance client failed because the required components were not updated. The accompanying messages provide detailed failure information.; Action: Examine the oakcli update command output, resolve the problems identified there, and then retry the operation.
PRGO-01824: More than one node was specified for the '-batch' option.: Cause: An attempt to update an Oracle Database Appliance client was rejected because more than one node was specified for the '-batch' option.; Action: Retry the command specifying only one node for the '-batch' option.
PRGO-01825: Node '{0}' was not patched successfully. Node '{1}' can be patched only after successfully patching node '{0}': Cause: An attempt to run the update Oracle Database Appliance client command for the indicated node failed because another node was not patched successfully.; Action: Complete patching of the other node and then retry the command.
PRGO-01826: Node '{0}' already patched successfully to version '{1}': 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.; Action: No action.
PRGO-01827: The '-batch' option is not valid since 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 without the '-batch' option was already issued for this Oracle database Appliance system and image.; Action: Execute the command without the '-batch' option.
PRGO-01828: The '-batch' option is mandatory since an instance of the command with 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.; Action: Execute the command with the '-batch' option.
PRGO-01831: Could not find any job with job ID {0}.: Cause: An attempt to fetch the job details failed because the specified job ID did not exist in the repository.; Action: Retry the operation with a job ID that exists in the repository.
PRGO-01832: osconfig already enabled: Cause: The operation was rejected because osconfig was already enabled.; Action: Retry the operation specifying the '-force' flag.
PRGO-01833: User "{0}" lacks the authority to perform the 'osconfig' operation.: Cause: An osconfig operation was rejected because the user did not have the necessary privileges. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01843: The specified osconfig "{0}" does not exist.: Cause: An attempt to operate on an osconfig collection was rejected because the specified osconfig was not found.; Action: Retry the operation specifying an osconfig collection that exists.
PRGO-01844: The specified osconfig "{0}" does not include node "{1}".: Cause: An attempt to compare osconfig was rejected because the specified osconfig did not include the specified node.; Action: Retry the operation specifying a valid node name or an osconfig collection that includes the specified node.
PRGO-01846: failed to compare the osconfig collections: Cause: An attempt to compare the specified osconfig collection failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01849: failed to restore the osconfig collection {0} for node {1}: Cause: An attempt to restore the osconfig collection failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01850: failed to determine the available osconfig collections for site {0}: Cause: An attempt to query the osconfig collection failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01851: backup osconfig operation scheduled at {0} for site {1} failed: Cause: An attempt to backup an osconfig collection failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01853: osconfig not yet enabled for site {0}: Cause: The operation was rejected because osconfig was not enabled for the indicated site.; Action: Enable osconfig and reissue the command.
PRGO-01854: failed to archive osconfig for node {0}: Cause: An attempt to backup an osconfig collection failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01855: failure to create directory "{0}": Cause: An attempt to create the specified directory failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01856: failure to read or write to the file "{0}": Cause: An attempt to read or write to the specified file failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages, address the issues described, and retry the operation.
PRGO-01859: The operation is not supported on version "{0}".: Cause: The attempted operation was rejected because it was not supported by the indicated version.; Action: Refer to the product documentation for the supported versions and retry the operation.
PRGO-01860: osconfig was already disabled: Cause: An attempt to disable osconfig was rejected because osconfig was already disabled.; Action: Retry the operation specifying the '-force' flag.
PRGO-01862: failed to collect osconfig for client "{0}": Cause: An attempt to backup an osconfig collection failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01863: The name "{0}" was specified as the name of a peer server, but it is the name of a Rapid Home Provisioning Client (RHPC).: 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.; Action: Retry the command providing the name of an RHP server.
PRGO-01864: The name "{0}" was specified as the name of a client, but it is the name of a peer Rapid Home Provisioning Server (RHPS).: 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.; Action: Retry the command providing the name of an RHP Client.
PRGO-01865: User "{0}" does not have permission to perform the 'query peerserver' operation.: Cause: An attempt to execute the command 'rhpctl query peerserver' was rejected because the indicated user did not have permission.; Action: Request authorization from an administrator and retry the command or perform the operation from a user ID that has the required authorization.
PRGO-01866: User "{0}" does not have permission to perform the 'register server' operation.: Cause: An attempt to execute the command 'rhpctl register server' was rejected because the indicated user did not have permission.; Action: Request authorization from an administrator and retry the command or perform the operation from a user ID that has the required authorization.
PRGO-01869: Failed to create a single instance database on the Leaf Node "{0}".: Cause: An attempt to create a single instance database was rejected because the indicated node was a Leaf Node.; Action: Retry the operation, specifying a single Hub Node using the '-node' option.
PRGO-01870: The unzipped directory {0} is not a proper Oracle home.: Cause: An attempt to import an image from the indicated path failed. The indicated extracted directory was not a proper Oracle home.; Action: Retry the import operation supplying a compressed file containing a valid Oracle home as the top directory in the archive.
PRGO-01871: The specified nodes "{0}" do not belong to cluster "{1}".: 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.; Action: Retry the command ensuring that either none of the nodes specified by '-node' are configured with GI or all of them are configured with the same client cluster.
PRGO-01872: The database "{0}" does not belong to Oracle home "{1}".: Cause: An attempt to operate on the specified database was rejected because the specified database did not belong to the specified Oracle home.; Action: Retry the operation specifying a database with its associated Oracle home.
PRGO-01873: The GoldenGate working copy "{0}" is not complete.: Cause: An attempt to upgrade a database with zero downtime was rejected because the specified GoldenGate working copy was incomplete.; Action: Retry after completely provisioning the specified GoldenGate working copy or specify a different working copy.
PRGO-01874: The GoldenGate working copy "{0}" of base image type "{1}" is not valid for Oracle home version "{2}".: 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.; Action: Retry the operation specifying a GoldenGate working copy of the appropriate base image type.
PRGO-01875: The GoldenGate working copy "{0}" is not owned by user "{1}".: 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.; Action: Retry the operation specifying a GoldenGate working copy owned by the indicated user.
PRGO-01876: The GoldenGate working copy "{0}" is not on an ASM Cluster File System (ACFS).: 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.; Action: Retry the operation specifying a GoldenGate working copy on an ACFS file system.
PRGO-01877: The source Oracle home is missing mandatory patches.: 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 -------------------|------------------------------------------------; Action: Move the database to an Oracle home with the required patches and retry.
PRGO-01878: failed to upgrade database "{0}" with zero downtime: Cause: An attempt to upgrade the specified database with zero downtime failed. The accompanying messages provide more details.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01887: The database "{0}" does not have services.: Cause: An attempt to upgrade the indicated database with zero downtime was rejected because it does not have services.; Action: Add services to the database and retry.
PRGO-01892: The destination working copy is missing mandatory patches.: 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 -------------------|-----------------|------------------------------; Action: Retry the operation specifying a destination working copy containing the required patches.
PRGO-01893: The snapshot database "{0}" is not running.: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01895: The database "{0}" is not the primary database.: Cause: An attempt to upgrade the specified database with zero downtime was rejected because it was not the primary database.; Action: Retry the operation specifying the primary database.
PRGO-01896: unable to connect to database "{0}" with the SYSDBA system privilege: 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.; Action: Retry the operation after ensuring that the database is online.
PRGO-01897: The database "{0}" is not in OPEN mode.: Cause: An attempt to upgrade the indicated database with zero downtime was rejected because the database was not open.; Action: Retry the operation after ensuring that the database is open.
PRGO-01898: The database "{0}" is in backup mode.: Cause: An attempt to upgrade the indicated database with zero downtime was rejected because the database was in backup mode.; Action: Retry the operation after the database backup has completed.
PRGO-01899: The data files of database "{0}" exist on an ASM disk group.: Cause: An attempt to upgrade the specified database with zero downtime was rejected because its data files were on an ASM disk group.; Action: None
PRGO-01900: The database "{0}" is not in ARCHIVELOG mode.: Cause: An attempt to upgrade the specified database with zero downtime was rejected because it was not in ARCHIVELOG mode.; Action: Retry the operation after configuring the database in ARCHIVELOG mode.
PRGO-01901: The data files of database "{0}" do not exist on ASM Cluster File System (ACFS) snapshots.: Cause: An attempt to upgrade the specified database with zero downtime was rejected because its data files do not exist on ACFS snapshots.; Action: None
PRGO-01902: The data files "{0}" of database "{1}" are missing.: Cause: An attempt to upgrade the indicated database with zero downtime was rejected because the indicated data files were missing.; Action: Restore the missing data files from a backup, and then retry the operation.
PRGO-01903: The database "{0}" does not have all its data files on ASM Cluster File System (ACFS) snapshots.: 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.; Action: Upgrade the indicated database in a non-rolling fashion.
PRGO-01904: The data files "{0}" of database "{1}" are not online.: Cause: An attempt to upgrade the indicated database with zero downtime was rejected because the indicated data files were not online.; Action: Ensure that the indicated data files are all online, and then retry the operation.
PRGO-01905: invalid Oracle database home "{0}": Cause: An attempt to upgrade a database with zero downtime was rejected because the indicated Oracle home was not a database home.; Action: Retry the operation specifying an Oracle database home.
PRGO-01906: Oracle database home "{0}" does not exist: Cause: An attempt to upgrade a database to the specified Oracle home with zero downtime was rejected because the home did not exist.; Action: Retry the operation specifying an Oracle home that does exist.
PRGO-01907: could not retrieve the version of Oracle database home "{0}": 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01908: The version of Oracle database home "{0}" is the same as the source database.: 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.; Action: Retry the operation specifying a destination Oracle home of a higher version.
PRGO-01909: The version of Oracle database home "{0}" is lower than the source database.: 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.; Action: Retry the operation specifying a destination home of a higher version.
PRGO-01910: invalid number of job_queue_processes for database "{0}": 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.; Action: Retry the operation after setting the job_queue_processes parameter equal to or greater than 4.
PRGO-01911: failed to set up Oracle GoldenGate requirements for database "{0}": 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01912: failed to add sequence support to database "{0}": 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01913: The required size of REDO space is {0}G but only {1}G is available.: 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.; Action: Retry the operation after increasing the REDO space.
PRGO-01914: failed to create an ASM Cluster File System (ACFS) snapshot: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01915: failed to alter the backup mode for database "{0}": 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01916: failed to retrieve the archive finish time for database "{0}": 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01917: failed to retrieve the archive destination ID for database "{0}": 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01918: failed to create the control file for the temporary database: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01919: failed to recover the temporary database: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01920: failed to open the temporary database with the RESETLOGS option: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01921: failed to set temporary table spaces for the temporary database: Cause: An attempt to upgrade a database with zero downtime failed because an error occurred while setting temporary table spaces for the temporary database.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01922: failed to set read-only 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01923: failed to change the database ID for the temporary database: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01924: failed to create the SPFILE for the temporary database: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01925: failed to add the temporary database as a Clusterware resource: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01926: The temporary database does not exist.: Cause: An attempt to upgrade a database with zero downtime failed because the temporary database was missing. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01927: The temporary database is not running.: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01928: failed to check the status of Oracle GoldenGate: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01929: The status of Oracle GoldenGate is unhealthy.: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01930: Internal error [# {0} #].: Cause: An attempt to upgrade a database with zero downtime failed because of an internal error.; Action: Contact Oracle Support Services.
PRGO-01931: failed to create services for the temporary database: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01932: Oracle GoldenGate synchronization did not complete.: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01933: failed to disable the database service "{0}": 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01934: failed to enable the database service "{0}": 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-01937: User "{0}" lacks the authority to perform the 'recover node' operation.: Cause: An attempt to run the command 'rhpctl recover node' was rejected because the user did not have root or Administrator privileges.; Action: Retry the command from a user ID that has root or Administrator privileges.
PRGO-01938: User "{0}" lacks the authority to perform the 'deploy image' operation.: Cause: An attempt to run the command 'rhpctl deploy image' was rejected because the user did not have root or Administrator privileges.; Action: Retry the command from a user ID that has root or Administrator privileges.
PRGO-01939: User "{0}" lacks the authority to perform the 'collect osconfig' operation.: Cause: An attempt to run the command 'rhpctl collect osconfig' was rejected because the user did not have root or sudo privileges.; Action: Retry the command specifying the user ID that has root or sudo privileges.
PRGO-01940: Path {0} does not designate an Oracle Golden Gate Home.: 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.; Action: Retry ensuring that the supplied path is an Oracle Golden Gate home path.
PRGO-01941: Path {0} does not designate an Oracle Golden Gate Home because the inventory file was not found.: 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.; Action: Retry ensuring that the supplied path is an Oracle Golden Gate home path.
PRGO-01942: The working copy "{0}" is an Oracle single-instance database home on a non-cluster node.: 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.; Action: None
PRGO-01943: ASM is not running on cluster "{0}".: Cause: An attempt to upgrade a database with zero downtime on the indicated cluster was rejected because ASM was not running on the cluster.; Action: Retry after starting ASM on the indicated cluster.
PRGO-01945: The database "{0}" is not running.: Cause: An attempt to upgrade the indicated database with zero downtime was rejected because the database was not running.; Action: Retry after starting the indicated database.
PRGO-01946: The database "{0}" does not have its data files on an ASM Cluster File System (ACFS) or an ASM diskgroup.: 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.; Action: None
PRGO-01947: The database "{0}" does not have its REDO logs on an ASM Cluster File System (ACFS).: Cause: An attempt to upgrade the indicated database with zero downtime was rejected because its REDO logs were not on an ACFS file system.; Action: None
PRGO-01948: The database "{0}" does not have its fast recovery area on an ASM Cluster File System (ACFS).: 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.; Action: None
PRGO-01949: Version '{0}' is not a valid Oracle database release.: 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.; Action: Reissue the command specifying a valid Oracle database release version identifier for the -release option.
PRGO-01950: The PSU string '{0}' is not a valid Oracle database PSU version.: 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.; Action: Reissue the command specifying the correct Oracle database PSU for the -psu option.
PRGO-01951: The patches string '{0}' does not contain valid Oracle Database patch numbers.: 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.; Action: Reissue the command specifying the correct Oracle database patch version for the -patches option. The specified patches string could be a list of comma-separated valid bug numbers.
PRGO-01952: Directory '{0}' does not have sufficient space to store archive file.: 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.; Action: Free up space in the specified directory and reissue the command.
PRGO-01953: failure to write file:'{0}' in directory: '{1}': Cause: An attempt to write the gold image archive file failed because the current user did not have write permission for the indicated directory.; Action: Retry the command ensuring that the specified directory has the requisite permissions.
PRGO-01954: While scheduling job, GIAAS server returned error message: '{0}'.: Cause: An attempt to schedule a Gold Image As Service (GIAAS) job failed because the GIAAS server returned the indicated error.; Action: Check the GIAAS logs for the specified error message from the GIAAS server, address the issue, and reissue the command.
PRGO-01955: The derived image type '{0}' is not supported for scheduling GIAAS job.: 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.; Action: Retry the command ensuring that the base image type of the derived image is either ORACLEGISOFTWARE or ORACLEDBSOFTWARE.
PRGO-01956: HTTP Post request to URL '{0}' failed with HTTP status code '{1}'.: Cause: An attempt to post to the indicated URL failed because of the HTTP error denoted by the indicated status code.; Action: Ensure that the specified URL is correct and that the HTTP server is running using the 'ping' command. Otherwise, contact Oracle Support Services.
PRGO-01957: HTTP Get request to URL '{0}' failed with error message: '{1}'.: Cause: An attempt to access the indicated URL failed because the HTTP server returned the specified HTTP status code.; Action: Retry the command ensuring that the specified URL is correct and that the HTTP server is running using the 'ping' command.
PRGO-01958: HTTP Post request to URL '{0}' failed with error message: '{1}'.: Cause: An attempt to post to the indicated URL failed because the HTTP server returned the indicated error.; Action: Examine the specified error message from the HTTP server for more information, address the reported issues, and retry.
PRGO-01959: No email address configured for user '{0}'.: 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.; Action: Use the 'rhpctl register user' command to specify the email address for the specified user and retry.
PRGO-01960: failed to modify the RHP user of user "{0}" because it is not a REST user: Cause: An attempt to modify the Rapid Home Provisioning (RHP) user failed because the user was not a REST user.; Action: Provide a REST user or create a new REST user using the command "rhpctl register user".
PRGO-01961: failed to set the RHP user "{0}" because it is a REST user: Cause: An attempt to set the Rapid Home Provisioning (RHP) user failed because the user should not be a REST user.; Action: Retry the operation, specifying an RHP user.
PRGO-01962: Invalid REST user "{0}" supplied for granting or revoking a role.: Cause: An attempt to grant or revoke a role for the indicated user failed because the user was a REST user.; Action: Retry the command, specifying a non-REST user.
PRGO-01966: failed to modify the REST user "{0}" because its roles are not a subset of "{1}" roles: 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.; Action: Grant the correct roles to the RHP user and try again.
PRGO-01974: cannot upgrade an Oracle Grid Infrastructure home in a Rapid Home Provisioning Server (RHPS) cluster: Cause: An attempt to upgrade Oracle Grid Infrastructure home failed because the target node was configured with RHPS. RHPS self-upgrade is not supported.; Action: Manually upgrade the home without using the Rapid Home Provisioning commands.
PRGO-01975: unexpected option '-oraclebase' specified when adding working copy "{0}" from an image of Golden Gate base type: 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.; Action: Retry the operation without specifying the '-oraclebase' option.
PRGO-02040: Adding a working copy failed. The specified software home is for the "{0}" operating system, and the cluster operating system is "{1}".: 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.; Action: Import an Oracle Grid Infrastructure image of the current version and target platform, and then reissue the command.
PRGO-02041: Databases "{0}" have not been completely reverted.: 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.; Action: Complete reverting the indicated databases and then continue patching the remaining databases.
PRGO-02042: Databases "{0}" are not being moved.: Cause: An attempt to continue or revert patching for the indicated databases was rejected because the databases were not involved in a move operation.; Action: Do not specify the indicated databases to continue or revert patching.
PRGO-02048: Oracle GoldenGate does not provide full capture process support for one or more tables in database "{0}".: 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.; Action: Query the DBA_GOLDENGATE_SUPPORT_MODE view in the indicated database to get additional information about the level of Oracle GoldenGate capture process support for the tables in the database. To ignore this warning and retry the operation, specify the '-ignoreprereq' option.
PRGO-02049: Failed to query view DBA_GOLDENGATE_SUPPORT_MODE. Query output:\n{0}: Cause: An attempt to upgrade database with zero downtime failed because a query of view DBA_GOLDENGATE_SUPPORT_MODE failed.; Action: Review the accompanying output for details and retry after resolving the error.
PRGO-02050: failed to create obey file: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-02051: Failed to set GoldenGate requirements for database "{0}".: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-02065: Cannot create a snapshot of an existing snapshot of an ASM Cluster File System (ACFS) on ASM disk group "{0}".: 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.; Action: None. Creation of a snapshot from an existing ACFS snapshot cannot be performed. Even if the ADVM compatibility attribute for the indicated disk group is updated to 12.1, creation of a snapshot from an existing snapshot is not possible due to the presence of a snaphot that was created with the ADVM compatibility set to less than 12.1.
PRGO-02066: Cannot create a read-write snapshot of an ASM Cluster File System (ACFS) on ASM disk group "{0}".: 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.; Action: Set the ADVM comptatibility attribute for the indicated disk group to 11.2.0.3.0 or higher, and then retry the operation.
PRGO-02067: Database "{0}" is not owned by "{1}".: Cause: An attempt to retrieve information about the indicated database was rejected because it was not owned by the indicated user.; Action: Specify a working copy owned by the correct user, and then retry the operation.
PRGO-02069: failed to apply osconfig retention plan for client "{0}": Cause: An attempt to perform osconfig retention failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-02081: cannot add working copy from image "{0}" because creation of this image was stored on external file system: Cause: An attempt to add a working copy from an image was rejected because; Action: Specify a non-external image from which to add the working copy.
PRGO-02083: Image "{0}" is already replicated to client "{1}".: Cause: An attempt to replicate the indicated image to the specified client was rejected, because the image was already replicated to the client.; Action: None
PRGO-02084: Image "{0}" cannot be replicated to client "{1}" because the image is incomplete.: Cause: An attempt to replicate the indicated image to the indicated client was rejected, because the image was incomplete.; Action: Retry the 'replicate image' command, specifying a complete image.
PRGO-02085: failed to start database service "{0}": Cause: An error occurred while attempting to start the indicated service. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02086: failed to stop database service "{0}": Cause: An error occurred while attempting to stop the indicated service. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02087: The server data file provided is for cluster {0}, not for the specified cluster {1}.: Cause: An attempt to register a peer server was rejected because the specified server data file was for a different cluster.; Action: Retry the operation, ensuring that the name of the RHP Server cluster specified using the '-server' option is the name of the cluster where the command 'rhpctl export server' was run to generate the server data file.
PRGO-02108: No job ID specified in the command arguments.: Cause: An attempt to delete a scheduled job was rejected because there was no job ID was found in the command arguments.; Action: Retry the 'delete job' command specifying a valid job id or comma separated list of job ids.
PRGO-02115: The move operation was rejected because the patched working copy "{0}" has the same patches which are present in the source working copy "{1}".: 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.; Action: Rerun the 'rhpctl move gihome' command specifying a patched working copy with more patches applied as the source working copy.
PRGO-02121: could not find any matching jobs: 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.; Action: Retry the operation, specifying valid conditional arguments.
PRGO-02122: Rapid Home Provisioning (RHP) client is running on node "{0}", preventing a recover node operation.: Cause: An attempt to perform a recover node operation was rejected because the Rapid Home Provisioning (RHP) client was running on the indicated node.; Action: Start the RHP client on a different node, and then retry the operation.
PRGO-02128: Failed to create the pluggable database "{0}" because the specified working copy creation was incomplete.: Cause: An attempt to add a pluggable database was rejected because the specified working copy creation was incomplete.; Action: Run the command 'rhpctl add workingcopy' to re-create the working copy, and then retry the operation.
PRGO-02129: missing required option '-targetnode' for performing "{0}" operation on a cluster whose version is older than 12.2: Cause: An attempt to perform the indicated operation failed because the '-targetnode' option was not specified.; Action: Retry specifying the '-targetnode' option.
PRGO-02130: Image "{0}" does not exist in the specified mapping file "{1}".: Cause: An attempt to download the indicated image failed because the image details for that image were not found in the indicated mapping file.; Action: Retry the command specifying the correct image and mapping file after adding the image to the mapping file if both indicated values are correct.
PRGO-02131: JSON parsing failed for mapping file "{0}".: 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.; Action: Retry the operation after correcting the indicated file or specifying the correct mapping file.
PRGO-02132: file "{0}" not found at path: "{1}": Cause: An attempt to download the indicated file failed because the indicated path was not valid.; Action: Ensure that the specified file exists and retry.
PRGO-02135: The directory '{0}' does not have sufficient space to store archive file.: Cause: An attempt to download an archive failed because the indicated directory did not have sufficient storage space.; Action: Free up space in the specified directory and reissue the command.
PRGO-02136: Oracle Grid Infrastructure software-only home "{0}" does not exist on nodes "{1}".: 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.; Action: Retry the operation, specifying an Oracle Grid Infrastructure software-only working copy that exists on all nodes in the cluster being patched.
PRGO-02137: missing mandatory option '-agpath', '-path', or both: 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.; Action: Reissue the 'rhpctl move gihome' command specifying both the '-agpath' and '-path' options.
PRGO-02140: failed to delete the RHP user "{0}" because the REST user "{1}" is linked with this user: Cause: An attempt to delete the indicated Rapid Home Provisioning (RHP) user was rejected because it was associated the indicated REST user.; Action: Remove the indicated REST user, or change the RHP user associated with the REST user, and then retry the operation.
PRGO-02141: The specified string "{0}" is not the name of an RHP client.: 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.; Action: Retry the operation, specifying a valid client name.
PRGO-02142: The specified string "{0}" is not the name of a peer RHP server.: 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.; Action: Retry the operation, specifying a valid server name.
PRGO-02143: failed to move Oracle Grid Infrastructure home to destination working copy "{0}" with storage type RHP_MANAGED: Cause: An attempt to move an Oracle Grid Infrastructure home failed because the storage type of the destination working copy was RHP_MANAGED,; Action: Retry the move operation specifying a working copy that does not have the storage type RHP_MANAGED.
PRGO-02144: The image zip file {0} contains invalid files "{1}": 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.; Action: Retry the operation, ensuring that the specified zip file does not contain indicated invalid files.
PRGO-02145: The zip file {0} is not an Oracle Database Home: Cause: An attempt to deploy an Oracle Database home image was rejected because the indicated zip file did not contain the Oracle Database binary.; Action: Retry the operation, ensuring that the zip file specified is an Oracle Database home image.
PRGO-02146: Zip file {0} does not contain an Oracle Golden Gate home.: Cause: An attempt to import a Golden Gate home software image was rejected because the indicated zip file did not contain the 'ggcmd' binary.; Action: Retry the operation, ensuring that the specified zip file contains an Oracle Golden Gate home.
PRGO-02147: Zip file {0} does not contain an Oracle Golden Gate home because the inventory file was not found.: 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.; Action: Retry the operation, ensuring that the specified zip file contains an Oracle Golden Gate home.
PRGO-02148: The zip file {0} does not contain an Oracle Grid Infrastructure home: 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.; Action: Retry the operation, ensuring that the specified zip file contains an Oracle Grid Infrastructure home.
PRGO-02149: User "{0}" lacks the authority to schedule the operation.: Cause: An attempt to schedule an rhpctl command was rejected because the indicated user did not have the required authorization.; Action: Retry the operation after requesting the authorization from the administrator or retry the operation from a user ID that has the required authorization.
PRGO-02150: User "{0}" lacks the authority to delete the scheduled job {1}.: Cause: An attempt to delete a scheduled job was rejected because the indicated user did not have the required authorization.; Action: Retry the operation after requesting the authorization from the administrator or retry the operation from a user ID that has the required authorization.
PRGO-02151: cannot replicate image "{0}" stored on an external file system: Cause: An attempt to replicate the indicated image was rejected because it; Action: None
PRGO-02152: The move operation was rejected because the patched working copy home path is the same as the source home path "{0}".: 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.; Action: Rerun the 'rhpctl move database' command specifying a patched working copy with a different Oracle home path.
PRGO-02153: Image "{0}" is not replicated to client "{1}".: Cause: An attempt to fetch the indicated image from the indicated client failed, because the image was not replicated to the client.; Action: Retry the operation, specifying an image that already exists on the indicated client. Alternatively, store the indicated image into the repository, and then retry the operation.
PRGO-02154: User "{0}" does not have permission to perform the 'unregister server' operation.: Cause: An attempt to execute the command 'rhpctl unregister server' was rejected because the indicated user did not have permission.; Action: Request authorization from an administrator and retry the command or perform the operation from a user ID that has the required authorization.
PRGO-02155: The name "{0}" was specified as the name of a client, but it is the name of a peer Rapid Home Provisioning Server (RHPS).: 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.; Action: Retry the command providing the name of an RHP Client.
PRGO-02156: The name "{0}" was specified as the name of a peer server, but it is the name of a Rapid Home Provisioning Client (RHPC).: 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.; Action: Retry the command providing the name of an RHP Server.
PRGO-02157: Cannot delete the job "{0}" because it has child jobs associated with it. To forcibly delete a parent job, specify -force option.: 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.; Action: Retry the operation, specifying -force option if the job needs to be deleted forcibly.
PRGO-02158: The value {0} of JSON element {2} has an invalid format for an instance of type {1}.: Cause: A Rapid Home Provisioning REST request was rejected because the indicated JSON element was not in the expected format.; Action: Retry the operation, ensuring that the indicated JSON element is formatted correctly for the indicated type.
PRGO-02159: An unexpected character ("{0}" (code "{1}")) was found at position "{2}" in the JSON message body of this request.: Cause: A Rapid Home Provisioning REST request was rejected because the body of the request did not conform to the JSON syntax specification.; Action: Retry the operation, ensuring that the request body is syntactically valid JSON. The client should not retry the request without modifying the request body.
PRGO-02160: An unrecognized field name "{0}" was found in the JSON message body of this request. The valid field names for the operation are : {1}.: Cause: A Rapid Home Provisioning REST request was rejected because the request body contained a field name that was not recognized.; Action: Retry the operation, ensuring that the request body contains only the indicated, valid field names. The client should not retry the request without modifying the request body.
PRGO-02161: Warning: The option '-image' has been deprecated. Use separate invocations of rhpctl to provision a working copy, and then to perform the required operations on the working copy.: Cause: Warning message.; Action: Not an error.
PRGO-02162: invalid configuration details specified for configuring the Grid Naming Service in the response file: 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.; Action: Refer to the product documentation for valid Grid Naming Service settings for configuring an Oracle Cluster. Specify the required details to create the Grid Naming Service in the response file and retry the command.
PRGO-02163: No databases are being moved from working copy "{0}".: 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.; Action: Retry the operation, ensuring that the inputs for options '-dbhomes', '-only', and '-except' are not excluding all databases in the indicated working copy from being patched.
PRGO-02164: No databases are being moved from Oracle home "{0}".: 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.; Action: Retry the operation, ensuring that the inputs for options '-dbhomes', '-only', and '-except' are not excluding all databases in the indicated Oracle home from being patched.
PRGO-02165: The image path specified contains invalid files "{0}": Cause: An attempt to deploy an Exadata image failed because the image path contained files which were not Exadata patch zip files.; Action: Reissue the command specifying the correct path.
PRGO-02166: The '-version' option required for importing an image of type EXAPATCHSOFTWARE is not specified.: Cause: An attempt to import an image was rejected because; Action: Retry the command specifying the '-version' option.
PRGO-02167: error encountered during update Exadata operation: Cause: An attempt to update an Exadata system encountered a failure. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages, address the issues described, and then retry the operation.
PRGO-02168: Image type of the image "{0}" is not EXAPATCHSOFTWARE.: Cause: An incorrect image type was specified for Exadata patching.; Action: Specify an image with image type EXAPATCHSOFTWARE.
PRGO-02169: The '-fromnode' option required for patching the specified Exadata nodes is not specified.: Cause: An attempt to update Exadata nodes was rejected because; Action: Retry the command specifying the '-fromnode' option.
PRGO-02170: error while executing the patchmgr command '{0}' on node '{1}': Cause: An attempt to update Exadata nodes failed. There was an error while executing the patchmgr command.; Action: Examine the patchmgr command output, resolve the problems identified there, and then retry the operation.
PRGO-02172: The root user credentials required for Exadata nodes are missing.: Cause: The requested Exadata patching operation was rejected because root user credentials were required, but were not provided.; Action: Retry the operation, providing credentials using the '-root' option.
PRGO-02173: The list of database servers, storage servers or ibswitches to be patched is missing.: Cause: The requested Exadata patching operation was rejected because neither dbnodes, nor cells, nor ibswitches were specified.; Action: Retry the operation, specifying either the 'dbnodes', 'cells' or 'ibswitches' option.
PRGO-02174: The image version "{0}" specified is invalid.: Cause: An attempt to deploy an Exadata image was rejected because an invalid image version was specified.; Action: Reissue the command specifying a valid Exadata patch version.
PRGO-02175: The image zip file {0} contains invalid files "{1}".: 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.; Action: Retry the operation, ensuring that the specified zip file does not contain the indicated invalid files.
PRGO-02176: The working copy specifed "{0}" does not exist.: Cause: The requested Exadata patching operation was rejected because the working copy specified did not exist.; Action: Retry the operation, specifying a valid working copy name. When patching an Exadata system for the first time using Rapid Home Provisioning (RHP), a new working copy can be created using the command 'add workingcopy'.
PRGO-02187: User "{0}" is not a valid RHP user.: Cause: An attempt to modify a Rapid Home Provisioning (RHP) user failed because the indicated RHP user was not valid.; Action: Provide a different RHP user or create a new RHP user using the command "rhpctl register user".
PRGO-02188: User "{0}" already exists.: 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.; Action: Retry specifying a different user name.
PRGO-02189: REST user "{0}" is already associated with the RHP user "{1}".: 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.; Action: Retry specifying a different RHP user.
PRGO-02190: The admin-managed database "{0}" is not supported on leaf nodes "{1}".: 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.; Action: Retry the operation, specifying a hub node.
PRGO-02191: invalid '-path' option provided for provisioning a software-only GI home on an Oracle Layered File System: 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.; Action: Reissue the 'add workingcopy' command without the '-path' option or specifying the -path option in conjuction with '-agpath' option.
PRGO-02193: An invalid value "{0}" for the storage option parameter STORAGE_OPTION was specified in the response file.: 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.; Action: Refer to the product documentation for valid storage options. Retry the operation, specifying a valid value for the storage option parameter in the response file.
PRGO-02194: Cross-platform import image is not supported because the image version {0} being imported is older than version {1}.: 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.; Action: Retry the operation, specifying a path to an image which is not older than the indicated version.
PRGO-02195: Importing an image of type {0} before importing an Oracle Grid Infrastucture image of version {1} is not allowed for cross-platform imports.: 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.; Action: Import an Oracle Grid Infrastructure software image of the indicated version and then retry the operation.
PRGO-02196: missing '-path' option for 'add workingcopy': 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.; Action: Retry the 'add workingcopy' command, specifying the '-path' option.
PRGO-02201: error while executing the command '{0}' on node '{1}': Cause: An attempt to update Exadata nodes failed. The command output provides detailed failure information.; Action: Examine the command output, resolve the problems identified, and then retry the operation.
PRGO-02204: The {0} patch files are missing in the image "{1}".: Cause: An attempt to update Exadata nodes failed because the image specified did not contain the necessary patch files.; Action: Retry the operation specifying an image containing the necessary patch files.
PRGO-02205: The format of the node list file "{0}" is invalid.: Cause: An attempt to update Exadata nodes failed because the format of the specified node list file was invalid.; Action: Retry the operation specifying a valid node list file.
PRGO-02206: The node list file "{0}" is empty.: Cause: An attempt to update Exadata nodes failed because the specified node list file was empty.; Action: Retry the operation specifying a valid node list file.
PRGO-02213: The database server specified using the '-fromnode' option is the same as the node to be patched.: 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.; Action: Retry the command specifying a different node for the '-fromnode' option.
PRGO-02214: The specified string "{0}" is not the name of an RHP client.: 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.; Action: Retry the operation, specifying a valid client name.
PRGO-02215: The specified string "{0}" is not the name of a peer RHP server.: 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.; Action: Retry the operation, specifying a valid server name.
PRGO-02216: option '-tgip' specified when the patched working copy "{0}" has the same patches that are present in the source working copy "{1}": 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.; Action: Rerun the 'rhpctl move gihome' command specifying a patched working copy with more patches applied than the source working copy, or remove the '-tgip' option.
PRGO-02232: unable to convert JSON file "{0}" to Java object: Cause: An attempt to convert a JSON file to a Java object failed. The accompanying messages provide detailed failure information.; Action: Contact Oracle Support Services.
PRGO-02233: unable to convert data to JSON format: Cause: An attempt to convert data to JSON format failed. The accompanying messages provide detailed failure information.; Action: Contact Oracle Support Services.
PRGO-02240: configuration data not found for cluster {0}: Cause: An attempt to retrieve configuration information failed. The accompanying messages provide detailed failure information.; Action: Run the command 'rhpctl collect osconfig' to re-create the cluster configuration data, and then retry the operation.
PRGO-02241: configuration data not found for node {0}: Cause: An attempt to retrieve configuration information failed. The accompanying messages provide detailed failure information.; Action: Ensure that the specified node is up and run the command 'rhpctl collect osconfig' to re-create the cluster configuration data, and then retry the operation.
PRGO-02242: failed to process configuration data for site {0}: Cause: An attempt to process the osconfig collection failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-02251: GoldenGate replication lag did not stabilize for database "{0}".: Cause: An attempt to upgrade a database with zero downtime failed because the GoldenGate replication lag did not stabilize for the indicated database.; Action: Check the status of the GoldenGate replication process. Retry the operation after the lag has stabilized.
PRGO-02253: operation succeeded with warnings\n{0}: Cause: The intended operation completed with warning messages. The accompanying messages provide detailed information.; Action: Examine the accompanying warning messages, address the described issues, and retry, or ignore the warnings.
PRGO-02254: The database "{0}" does not have its REDO logs 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 ASM diskgroup.; Action: None
PRGO-02255: The database "{0}" does not have its fast recovery area 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.; Action: None
PRGO-02256: Backup location "{0}" does not exist.: Cause: An attempt to upgrade a database with zero downtime was rejected because the specified backup location does not exist.; Action: Retry the operation, specifying a valid backup location.
PRGO-02257: ASM diskgroup "{0}" does not exist.: Cause: An attempt to upgrade a database with zero downtime was rejected because the indicated diskgroup does not exist.; Action: Ensure that the database is configured properly and then retry the operation.
PRGO-02258: failed to create client data file "{0}": 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.; Action: Ensure that the indicated file does not exist. Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02259: The '-clonedatadg' option required for creating a clone of database "{0}" is missing.: Cause: An attempt to upgrade the indicated database with zero downtime was rejected because the '-clonedatadg' option was not specified.; Action: Retry the operation, specifying the '-clonedatadg' option with a valid diskgroup name.
PRGO-02260: Database "{0}" could not be started.: 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.; Action: Examine the accompanying warning messages, address the described issues, and retry.
PRGO-02261: Failed to set cluster database thread parameter for database "{0}".: 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.; Action: Examine the accompanying warning messages, address the described issues, and retry.
PRGO-02262: failed to retrieve the maximum redo log thread number for database "{0}": Cause: An attempt to upgrade the indicated database with zero downtime failed because the maximum redo log thread number could not be determined.; Action: Examine the accompanying warning messages, address the described issues, and retry.
PRGO-02263: Query of DBA_TABLESPACES failed. Query output:\n{0}: Cause: An attempt to upgrade a database with zero downtime failed because a query of DBA_TABLESPACES failed.; Action: Review the accompanying output for details and retry after resolving the error.
PRGO-02264: Truststore file "{0}" does not exist.: Cause: An attempt to connect to a URL using an HTTPS connection failed because the indicated truststore file did not exist.; Action: Ensure that the indicated truststore file exists or execute the command 'crskeytoolctl -copycacerts -storepass password' to create a cacerts file.
PRGO-02265: failed to duplicate the password file of database instance "{0}": 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.; Action: Verify the permissions of the password file and its parent directory. Ensure that the password file of the indicated database instance can be duplicated and retry.
PRGO-02268: Missing Oracle base to register working copies for image "{0}" of image type {1}.: Cause: An attempt to register working copies was rejected because the '-oraclebase' option was omitted for an image type that requires it.; Action: Retry the command supplying the '-oraclebase' option.
PRGO-02269: The '-oraclebase' option is not allowed when registering working copies for image "{0}" because the image type is {1}.: Cause: An attempt to register working copies was rejected because the '-oraclebase' option was specified for an image type that does not support it.; Action: Retry the command without the '-oraclebase' option.
PRGO-02270: Unexpected number of attributes specified for working copy "{0}".: 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.; Action: Ensure that the attribute file provides all and only the required attributes on each line and then retry the operation.
PRGO-02271: Cannot upgrade single-instance database "{0}" with zero downtime.: Cause: An attempt to upgrade the indicated database with zero downtime was rejected because that operation was not supported for single-instance databases.; Action: Upgrade the indicated database using "rhpctl upgrade database".
PRGO-02272: The replication policy for the specified image "{0}" and site "{1}" already exists.: 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.; Action: Run "rhpctl uninstantiate image" for the indicated image and site and then retry the operation.
PRGO-02273: The replication policy for the specified image series "{0}" and site "{1}" already exists.: 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.; Action: Run "rhpctl uninstantiate image" for the indicated imageseries and site and then retry the operation.
PRGO-02274: The replication policy for the specified image type "{0}" and site "{1}" already exists.: 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.; Action: Run "rhpctl uninstantiate image" for the indicated imagetype and site and then retry the operation.
PRGO-02275: The replication policy for the specified image "{0}" and site "{1}" does not exist.: 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.; Action: Run "rhpctl instantiate image" for the indicated image and site and then retry the operation.
PRGO-02276: The replication policy for the specified image series "{0}" and site "{1}" does not exist.: 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.; Action: Run "rhpctl instantiate image" for the indicated imageseries and site and then retry the operation.
PRGO-02277: The replication policy for the specified image type "{0}" and site "{1}" does not exist.: 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.; Action: Run "rhpctl instantiate image" for the indicated imagetype and site and then retry the operation.
PRGO-02278: Failed to delete the job "{0}": "{1}".: Cause: An attempt to delete the indicated job failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages, resolve the indicated problems and then retry the operation.
PRGO-02280: Invalid job IDs provided: "{0}".: Cause: An attempt to delete the indicated jobs failed because the job IDs provided were invalid.; Action: Retry the operation, specifying valid job IDs.
PRGO-02281: Failed to delete the jobs: "{0}".\nFailure details:\n{1}: Cause: An attempt to delete the indicated jobs failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages, resolve the indicated problems and then retry the operation.
PRGO-02282: Could not find the following jobs: "{0}".: Cause: An attempt to delete the indicated jobs failed because the indicated jobs were not found.; Action: Retry the operation, specifying valid job IDs.
PRGO-02283: Failed to modify schedule time for the job "{0}" as the job status currently is: "{1}".: Cause: An attempt to modify the indicated job failed because the indicated job was not in the TIMER_RUNNING state.; Action: Retry the operation, specifying a job in the TIMER_RUNNING state.
PRGO-02284: ASM disk group "{0}" does not exist on cluster "{1}".: Cause: An attempt to upgrade a database with zero downtime was rejected because the indicated disk group was invalid.; Action: Retry the operation, specifying a valid disk group.
PRGO-02350: Password file "{0}" does not exist.: 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.; Action: Create the indicated password file, and then retry the operation.
PRGO-02351: The source Oracle home is missing mandatory fixes for bugs "{0}".: 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.; Action: Move the database to an Oracle home with the required patches, and then retry the operation.
PRGO-02352: The destination Oracle home is missing mandatory fixes for bugs "{0}".: 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.; Action: Specify a destination Oracle home with the required patches, and then retry the operation.
PRGO-02353: failed to start database "{0}" using the MOUNT option: Cause: An attempt to upgrade a database with zero downtime failed because the indicated clone database could not be started using the MOUNT option.; Action: Examine the accompanying warning messages, resolve the described issues, and then retry the operation.
PRGO-02354: failed to start redo apply: Cause: An attempt to upgrade a database with zero downtime failed because the redo apply could not be started.; Action: Examine the accompanying warning messages, resolve the described issues, and then retry the operation.
PRGO-02355: Path "{0}" is not a valid ACFS file system.: Cause: An attempt to upgrade a database with zero downtime was rejected because the indicated path was not a valid ACFS file system.; Action: Retry the operation, specifying a valid ACFS file system path.
PRGO-02356: failed to start database "{0}": Cause: An attempt to upgrade a database with zero downtime failed because the indicated database could not be started.; Action: Examine the accompanying warning messages, resolve the described issues, and then retry the operation.
PRGO-02357: failed to switch the role of database "{0}" from "{1}" to "{2}": Cause: An attempt to upgrade a database with zero downtime failed because the role of the indicated database could not be modified.; Action: Examine the accompanying warning messages, resolve the described issues, and then retry the operation.
PRGO-02358: Service "{0}" for database "{1}" does not exist.: Cause: An attempt to upgrade a database with zero downtime failed because the indicated database service did not exist.; Action: Examine the accompanying messages, resolve the described issues, and then retry the operation.
PRGO-02359: Query of FLASH_RECOVERY_AREA_USAGE for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02360: Flashback Database is not enabled for database "{0}".: Cause: An attempt to upgrade the indicated database with zero downtime was rejected because Flashback Database was not enabled for the database.; Action: Enable Flashback Database for the database, and then retry the operation.
PRGO-02361: RHP client "{0}" of version 12.2 is missing mandatory fixes for bugs "{1}".: 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.; Action: Patch the RHP client's Grid Infrastructure using 'rhpctl move gihome', and then retry the operation.
PRGO-02362: DBUA execution failed for database "{0}"\n{1}: Cause: An attempt to upgrade the indicated database failed because Database Upgrade Assistant (DBUA) execution failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages, resolve the indicated problems, and then retry the operation.
PRGO-02363: Query to verify whether Flashback Database is enabled for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02364: SQL query to retrieve Data Guard Broker status for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02365: SQL query to retrieve job_queue_processes parameter of database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02366: Query of V$RESTORE_POINT for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02367: SQL statement to drop a restore point failed.\n{0}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02368: SQL statement to create a restore point failed.\n{0}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02369: Query of GV$INSTANCE for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02370: SQL statement to disable CLUSTER_DATABASE for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02371: Query of DATABASE_ROLE in V$DATABASE for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02372: Query of CLUSTER_DATABASE in V$SPPARAMETER for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02373: Query of PROTECTION_MODE in V$DATABASE for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02374: DBMS_STATS.SET_GLOBAL_PREFS procedure failed.\n{0}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02375: Query of DBA_LOGSTDBY_UNSUPPORTED for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02376: SQL statement to start redo apply for standby database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02377: SQL statement to stop redo apply for standby database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02378: SQL statement to switch logs for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02379: Query of APPLIED_SCN in V$LOGSTDBY_PROGRESS for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02380: Query of CURRENT_SCN in V$DATABASE for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02381: Query of V$RECOVERY_PROGRESS for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02382: Query of V$LOGSTBY_STATE for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02383: SQL statement to convert physical standby database "{0}" to transient logical standby failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02384: DBMS_LOGSTDBY.BUILD procedure to start logical standby instantiation failed.\n{0}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02385: Query of OPEN_MODE in V$DATABASE for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02386: SQL statement to open database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02387: SQL statement to stop transient logical standby database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02388: DBMS_LOGSTDBY.APPLY_SET procedure to set rolling upgrade parameters for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02389: SQL statement to start transient logical standby database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02390: SQL query to check for completion of dictionary loading failed.\n{0}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02391: SQL statement to enable CLUSTER_DATABASE for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02392: DBMS_STATS.GATHER_DICTIONARY_STATS procedure to gather statistics for dictionary schemas failed.\n{0}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02393: SQL statement to switch primary database "{0}" to transient logical standby failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02394: Query of SWITCHOVER_STATUS in V$DATABASE for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02395: SQL statement to start recovery for standby database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02396: SQL statement to switch transient logical standby database "{0}" to primary failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02397: SQL statement to restore database "{0}" to restore point "{1}" failed.\n{2}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02398: SQL statement to switch database "{0}" to physical standby failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02399: Query of SCN in V$RESTORE_POINT for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02400: SQL statement to set _transient_logical_clear_hold_mrp_bit parameter to true for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02401: SQL statement to backup control files of database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02402: SQL statement to add standby redo log file group "{0}" to standby database "{1}" and assign it to thread "{2}" failed.\n{3}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02403: Query to retrieve THREAD# and BYTES from V$LOG for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02404: Query to retrieve the maximum redo log group identifier number from V$LOGFILE for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02405: Query to retrieve the maximum redo log group identifier number from V$STANDBY_LOG for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02406: Query to retrieve the number of redo log members from V$STANDBY_LOG for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02407: SQL statement to put database "{0}" into FORCE LOGGING mode failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02408: Query to verify whether media recovery is running for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02409: SQL statement to stop media recovery for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02410: Query of V$TEMPFILE to verify existence of a temp file for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02411: SQL statement to enable supplemental logging for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02412: SQL statement to enable change tracking for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02413: SQL statement to enable Flashback Database for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02414: Query of DB_UNIQUE_NAME in V$DATABASE for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02415: Query of V$INSTANCE for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02416: SQL statement to set DG_CONFIG value for LOG_ARCHIVE_CONFIG parameter for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02417: SQL statement to enable automatic standby file management for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02418: Query to retrieve parameter LOG_ARCHIVE_DEST of database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02419: Query to retrieve parameter FAL_SERVER of database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02420: Query to retrieve parameter LOG_ARCHIVE_CONFIG of database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02421: SQL statement to set standby parameters for primary database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02422: Service "{0}" of database "{1}" is not running.: Cause: An attempt to upgrade a database with zero downtime failed because the indicated database service was not running.; Action: Start the indicate database services, and then retry the operation.
PRGO-02423: failed to determine status of service "{0}" of database "{1}"\n{2}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02424: failed to update the startup mode of database "{0}" to OPEN\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02425: failed to migrate the password file for database "{0}"\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02426: failed to copy password file "{0}" to path "{1}": 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.; Action: Check the permissions of the password file and source and target parent directories. Verify that the indicated password file can be copied, and then retry the operation.
PRGO-02427: failed to change owner to "{0}" and group to "{1}" for password file "{2}": 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.; Action: Check that the directory of the indicated file has execute permission. Verify that the ownership of the password file can be modified as indicated, and then retry the operation.
PRGO-02428: failed to modify the password file of database "{0}"\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02429: failed to create ACFS snapshot "{0}"\n{1}: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-02430: failed to create directory "{0}"\n{1}: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-02431: failed to stop clone database "{0}"\n{1}: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-02432: RMAN failed to start clone database "{0}".\n{1}: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-02433: RMAN failed to backup and restore the SPFILE for clone database "{0}".\n{1}: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-02434: failed to register clone database "{0}"\n{1}: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-02435: failed to modify instance for clone database "{0}"\n{1}: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-02436: failed to modify the resource dependencies of database "{0}"\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02437: failed to start auxiliary listener "listener_clone".\n{0}: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-02438: failed to stop auxiliary listener "listener_clone".\n{0}: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-02439: Source database "{0}" is using Flash Cache.: 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.; Action: Disable Flash Cache for the indicated database by setting the DB_FLASH_CACHE_SIZE parameter to 0, and then retry the operation.
PRGO-02440: failed to disable the database service "{0}"\n{1}: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-02441: failed to enable the database service "{0}"\n{1}: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-02442: failed to start database service "{0}"\n{1}: Cause: An error occurred while attempting to start the indicated service. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02443: failed to stop database service "{0}"\n{1}: Cause: An error occurred while attempting to stop the indicated service. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02444: MRP process is not running for database "{0}".: Cause: An attempt to upgrade a database with zero downtime failed because the Managed Recovery Process (MRP) was not running for the indicated database.; Action: Start MRP for the indicated database, and then retry the operation.
PRGO-02445: timed out after "{0}" minutes of inactivity: Cause: An attempt to upgrade a database with zero downtime failed because an operation timed out. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02446: Number of restore points for database "{0}" exceeds maximum of {1}.: 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.; Action: Retry the operation after freeing up restore points for the indicated database such that the total number of restore points is less than the indicated maximum.
PRGO-02447: Flash recovery area usage by database "{0}" exceeds {1} percent.: 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.; Action: Free up enough of the flash recovery area to reduce the area usage to less than the indicated percentage, and then retry the operation.
PRGO-02448: Data Guard Broker is active for database "{0}".: Cause: An attempt to upgrade a database with zero downtime was rejected because Data Guard Broker was active for the indicated database.; Action: Disable Data Guard Broker for the indicated database by setting the DG_BROKER_START parameter to false, and then retry the operation.
PRGO-02449: failed to stop instance "{0}" of database "{1}"\n{2}: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-02450: failed to start instance "{0}" of database "{1}"\n{2}: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-02451: failed to stop database "{0}"\n{1}: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-02452: failed to start database "{0}"\n{1}: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-02453: Database "{0}" is not a "{1}" database.: Cause: An attempt to upgrade a database with zero downtime failed because the indicated database was not in the indicated role.; Action: Switch the indicated database to the indicated role, and then retry the operation.
PRGO-02454: Database "{0}" is running in maximized protection mode.: Cause: An attempt to upgrade a database with zero downtime failed because the indicated database was running in maximized protection mode.; Action: Ensure that the indicated database is not running in maximized protection mode, and then retry the operation.
PRGO-02455: Database "{0}" is not mounted.: Cause: An attempt to upgrade a database with zero downtime failed because the indicated database was not mounted.; Action: Ensure that the indicated database is mounted, and then retry the operation.
PRGO-02456: Database "{0}" is not in read/write mode.: Cause: An attempt to upgrade a database with zero downtime failed because the indicated database was not in read/write mode.; Action: Ensure that the indicated database is in read/write mode, and then retry the operation.
PRGO-02457: Database "{0}" is in "OPEN MIGRATE" mode.: Cause: An attempt to upgrade a database with zero downtime failed because the indicated database was in the "OPEN MIGRATE" mode.; Action: Ensure that the indicated database is not in the "OPEN MIGRATE" mode, and then retry the operation.
PRGO-02458: Options required for creating a clone of database "{0}" are missing.: Cause: An attempt to upgrade the indicated database with zero downtime was rejected because neither the '-clonedatadg' option nor the '-clonedatafs' option was specified.; Action: Retry the operation, specifying either the '-clonedatadg' option or the '-clonedatafs' option and related options.
PRGO-02459: ACFS file system "{0}" does not exist on cluster "{1}".: Cause: An attempt to upgrade a database with zero downtime was rejected because the indicated ASM Cluster File System (ACFS) did not exist.; Action: Retry the operation, specifying a valid ACFS file system.
PRGO-02460: failed to open file "{0}": Cause: An attempt to open the indicated file failed because the file did not exist or the permissions for the file were incorrect.; Action: Verify the existence and permissions of the file, and retry. If the problem persists, contact Oracle Support Services.
PRGO-02461: The preupgrd.sql script reported one or more errors for database "{0}". Log file "{1}" contains additional details.\n{2}: Cause: An attempt to upgrade the indicated database with zero downtime was rejected because the Pre-Upgrade Information Tool reported one or more errors.; Action: Review the indicated preupgrade.log file for details, and retry the operation after fixing the flagged issues.
PRGO-02462: The preupgrd.sql script reported one or more warnings for database "{0}". Log file "{1}" contains additional details.\n{2}: Cause: An attempt to upgrade the indicated database with zero downtime was rejected because the Pre-Upgrade Information Tool reported one or more warnings.; Action: Review the indicated log file for details. To ignore the warnings and retry the operation, specify the '-ignoreprereq' option.
PRGO-02463: SQL statement to run Pre-Upgrade information tool on the database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-02464: Image "{0}" already exists on cluster "{1}".: Cause: An attempt to replicate the specified image was rejected because the indicated image already existed on the target.; Action: Specify a different image and retry the operation.
PRGO-02467: Working copy "{0}" already exists with the specified path "{1}".: Cause: An existing working copy was found with the same home path while adding a new working copy.; Action: Supply another home path or delete the working copy and retry.
PRGO-02468: cannot retrieve the full version of the image from image path "{0}" while registering or importing a new image on node {1}.: 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.; Action: Examine the accompanying error messages, resolve the described issues, and then retry the operation.
PRGO-02469: CVU checks for adding a node failed for the specified node list {0}.: Cause: One or more Cluster Verification Utility (CVU) checks for adding a node failed.; Action: Review the underlying error messages and take the appropriate action.
PRGO-02470: Working copy "{0}" is involved in an incomplete move or upgrade operation.: Cause: An attempt to delete the indicated working copy was rejected because it is involved in an ongoing move or upgrade operation.; Action: Retry deleting the indicated working copy after completing or aborting the ongoing move or upgrade operation.
PRGO-02471: Missing '-targetnode' option for Single-Instance High Availability Grid Infrastructure provisioning.: 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.; Action: Reissue the command specifying the '-targetnode' option.
PRGO-02473: invalid format "{0}" specified in preference file "{1}": Cause: The format specified in the preference file was invalid.; Action: Specify preference in valid format and retry. Valid preference keywords for the database are DBUA_ARGS or DBUA_ARGS followed by an underscore and the database home release version like 12.1.0.2.
PRGO-02474: A direct upgrade of database from version {0} to version {1} is not supported.: Cause: An attempt to upgrade the database failed because the source working copy version was lower than the supported versions for upgrade.; Action: Refer to the product documentation for the supported versions for upgrade. Upgrade the database to one of the supported versions, and then upgrade to the destination working copy version.
PRGO-02475: Neither GNS server nor GNS client are configured on this RHP Server cluster.: 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.; Action: Configure either the GNS server or GNS client using the command 'srvctl add gns' in this RHP Server cluster, and retry the command.
PRGO-02485: The derived image type '{0}' did not match the image type '{1}' from the user input.: 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.; Action: Confirm the image type and retry the command with correct options.
PRGO-03002: missing '-rsp' option for migrating database to the cloud: Cause: An attempt to migrate database to the cloud was rejected because the '-rsp' option is required.; Action: Retry the command specifying the '-rsp' option.
PRGO-03003: Zero downtime migration (ZDM) response file {0} does not exist.: Cause: An attempt to locate the specified Zero downtime migration (ZDM) response file failed.; Action: Ensure that the path and name of the response file were entered correctly and that the file exists and is readable.
PRGO-03004: Zero downtime migration (ZDM) template file {0} is not a file.: Cause: The specified template file was a directory.; Action: Specify the absolute file path of the template file.
PRGO-03007: failed to migrate database "{0}" with zero downtime: Cause: An attempt to migrate the specified database with zero downtime failed. The accompanying messages provide more details.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-04001: SQL statement to start the REDO APPLY statement for standby database "{0}" failed \n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04002: SQL statement to add standby redo log file group "{0}" to standby database "{1}" and assign it to thread "{2}" failed.\n{3}: 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.; Action: Review the accompanying messages, resolve the specified problems, and then retry the operation.
PRGO-04003: Failed to authenticate object store credentials. Invalid username or password.: Cause: An attempt to authenticate input credentials failed.; Action: Verify the credentials and then retry the operation.
PRGO-04004: failed to retrieve Oracle object storage service container "{0}"\n{1}: Cause: An error occurred while trying to retrieve the specified Oracle object storage service container. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04005: The storage container "{0}" does not exist.: Cause: The specified storage container did not exist.; Action: Verify the storage container and then retry the operation.
PRGO-04007: OSS cloud backup module installation failed.\n{0}: Cause: An attempt to install the Oracle Storage Service (OSS) cloud backup module failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04008: ASM disk group "{0}" does not exist.: Cause: An attempt to migrate a database with zero downtime was rejected because the specified disk group did not exist.; Action: Ensure that the specified disk group exists and then retry the operation.
PRGO-04010: The database "{0}" is not in ARCHIVELOG mode.: Cause: An attempt to migrate the specified database was rejected because it was not in ARCHIVELOG mode.; Action: Retry the operation after configuring the database in ARCHIVELOG mode.
PRGO-04011: The path "{0}" is not a valid Oracle ACFS file system path.: 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.; Action: Retry the operation, specifying a valid Oracle ACFS file system path.
PRGO-04012: OSS cloud backup for database "{0}" failed.\n{1}: Cause: An attempt to create the Oracle Storage Service (OSS) cloud backup for the specified database failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04027: SPFILE creation failed.\n{0}: Cause: An attempt to create the SPFILE failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04028: Database resource modification failed.\n{0}: Cause: An attempt to modify the database resource using 'srvctl modify database' failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04029: unable to move the password file "{0}"\n{1}: Cause: An attempt to move the database password file failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04033: failed to create initial parameter file "{0}": Cause: An attempt to create the indicated database initialization parameter file failed.; Action: Verify that the parent directory exists with the permissions to write and then retry the operation.
PRGO-04036: SQL statement to switch logs for database "{0}" 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04037: query of the V$RECOVERY_PROGRESS view for database "{0}" failed: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04038: query of the V$LOGSTBY_STATE view for database "{0}" failed: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04039: SQL statement to switch primary database "{0}" to transient logical standby database failed: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04040: SQL statement to start recovery for standby database "{0}" failed: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04041: SQL statement to switch transient logical standby database "{0}" to primary database failed: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04042: query to verify whether media recovery is running for database "{0}" failed: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04047: unable to create the password file "{0}"\n{1}: Cause: An attempt to create the database password file failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04048: failed to change owner to "{0}" for password file "{1}": 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.; Action: Check that the directory of the indicated file has execute permission. Ensure that the ownership of the password file can be modified, and then retry the operation.
PRGO-04049: failed to register clone database "{0}"\n{1}: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-04052: Restoration of control file and database files failed.\n{0}: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-04053: query of DBA_TABLESPACES failed on database "{0}".: Cause: An attempt to migrate a database with zero downtime failed because a query of DBA_TABLESPACES failed.; Action: Examine the accompanying messages, resolve the indicated problems, and retry.
PRGO-04054: Oracle RAC option not enabled for database "{0}": 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.; Action: Enable the Oracle RAC option, and then retry the operation.
PRGO-04055: SQL statement to stop the REDO APPLY statement for standby database "{0}" failed: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04056: SQL statement to enable supplemental logging for standby database "{0}" failed: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04058: failed to execute the statment to convert the database "{0}" to physical standby database: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04059: failed to execute the statment to enable force logging for database "{0}": 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04060: failed to add log file with thread number "{0}", group "{1}" and size "{2}" for database "{3}": Cause: An attempt to migrate the specified database with zero downtime failed because the operation to add the indicated log file failed.; Action: Examine the accompanying messages, resolve the indicated problems, and retry.
PRGO-04061: failed to enable thread number "{0}" for database "{1}": Cause: An attempt to migrate the specified database with zero downtime failed because the operation to enable the indicated thread number failed.; Action: Examine the accompanying messages, resolve the indicated problems, and retry.
PRGO-04062: failed to create undo tablespace "{0}" for database "{1}": Cause: An attempt to migrate the specified database with zero downtime failed because the operation to create the indicated undo tablespace failed.; Action: Examine the accompanying messages, resolve the indicated problems, and retry.
PRGO-04063: query of the V$BLOCK_CHANGE_TRACKING view for database "{0}" 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04064: SQL statement to enable block change tracking for database "{0}" failed: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04065: SQL statement to enable flashback mode for database "{0}" failed: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04066: failed to update the primary database "{0}" \n"{1}": 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04068: OSS cloud full backup for database "{0}" failed.\n{1}: Cause: An attempt to create the Oracle Storage Service (OSS) cloud backup for the specified database failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04071: OSS cloud incremental backup for database "{0}" failed.\n{1}: Cause: An attempt to create the Oracle Storage Service (OSS) cloud backup for the specified database failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04074: OSS cloud differential backup for database "{0}" failed.\n{1}: Cause: An attempt to create the Oracle Storage Service (OSS) cloud backup for the specified database failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04077: OSS cloud cumulative backup for database "{0}" failed.\n{1}: Cause: An attempt to create the Oracle Storage Service (OSS) cloud backup for the specified database failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04079: open with resetlogs failed for database "{0}".\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04080: failed to set "{1}" parameter to "{2}" for database "{0}": 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04081: failed to set the "{1}" parameter for database "{0}": 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04082: failed to reset the "{1}" parameter for database "{0}": 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04083: failed to query the "{1}" parameter from the view "{2}" for database "{0}": 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04084: failed to create directory "{0}"\n{1}: 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.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-04085: failed to change owner to "{0}" and group to "{1}" for file "{2}"\n{3}: 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.; Action: Check that the directory of the indicated file has execute permission. Ensure that the ownership of the password file can be modified, and then retry the operation.
PRGO-04086: failed to query the "{1}" details from the view "{2}" for database "{0}": 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04087: Zero impact patching cannot be performed during revert of Oracle Grid Infrastructure home.: Cause: An attempt to revert the Oracle Grid Infrastructure home was rejected because zero impact patching cannot be performed during the revert operation.; Action: Retry the revert operation without specifying the '-tgip' option.
PRGO-04091: failed to create PFILE "{0}" from the SPFILE for database "{1}": Cause: An attempt to migrate the specified database with zero downtime failed because the operation to create the indicated PFILE from the SPFILE failed.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-04092: failed to copy file "{0}"\n{1}: Cause: An attempt to copy the indicated file failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-04093: failed to open directory "{0}"\n{1}: Cause: An attempt to open the specified directory failed.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGO-04095: failed to enable thread number "{0}" for database "{1}": Cause: An attempt to upgrade a database with zero downtime failed because the operation to enable the specified thread number for specified database failed.; Action: Examine the accompanying messages, resolve the indicated problems, and retry the operation.
PRGO-04096: Query to retrieve the maximum redo log size for database "{0}" 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04097: Query to retrieve the maximum redo log group for database "{0}" failed.: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04098: SQL statement to add redo log file group "{0}" to database "{1}" and assign it to thread "{2}" failed.: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04099: The standby database "{0}" does not exist.: Cause: An attempt to upgrade a database with zero downtime failed because the specified standby database was unexpectedly missing.; Action: Retry after aborting the ongoing upgrade operation.
PRGO-04100: The database "{0}" does not have enabled services.: Cause: An attempt to upgrade the specified database with zero downtime was rejected because it did not have enabled services.; Action: Enable at least one database service and retry.
PRGO-04101: RHP client is running on node "{0}", preventing "{1}" option.: 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.; Action: Specify a valid option and retry the operation.
PRGO-04105: Parameter 'ORACLE_HOME' is missing or empty in the specified response file for 'add workingcopy'.: 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.; Action: Retry the 'add workingcopy' command, specifying the 'ORACLE_HOME' parameter in the response file.
PRGO-04106: Query of the log_archive_dest parameter for database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04107: The database "{0}" is missing required Oracle GoldenGate RDBMS patches.: 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.; Action: Refer to MOS note 1557031.1, and retry the operation after applying the relevant Oracle GoldenGate RDBMS patch.
PRGO-04108: The credentials required for remote node connection to the site "{0}" are missing.: 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.; Action: Retry the 'rhpctl upgrade gihome' command, providing the credentials.
PRGO-04109: failed to re-create client "{0}" because working copies have been configured for it.: Cause: An attempt to re-create a client was rejected because there were working copies configured for it.; Action: Use the 'rhpctl remove workingcopy' command to first remove the associated working copies and retry the command.
PRGO-04113: SQL query to retrieve PROCESSES parameter of database "{0}" failed.\n{1}: 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.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGO-04115: The number of processes for database "{0}" is less than "{1}", which is the minimum required.: 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.; Action: Retry the operation after setting the PROCESSES parameter equal to or greater than 500.
PRGO-04116: failed to resume the job "{0}" as the job status currently is: "{1}": Cause: An attempt to resume the specified job was rejected because the specified job was not in the PAUSED state.; Action: Retry the operation, specifying a job in the PAUSED state.
PRGO-04119: pause phase {0} does not exist: Cause: An attempt to locate the specified pause phase failed.; Action: Ensure that the pause phase exists using -eval option to show valid phases.
PRGO-04125: DV_PATCH_ADMIN role cannot be granted to the SYS user for database with instance "{0}".: Cause: An attempt to perform database patching failed because the database with the indicated instance was Oracle Database Vault enabled, but the DV_PATCH_ADMIN role could not be granted to the SYS user.; Action: Ensure that it is possible to grant the DV_PATCH_ADMIN role to the SYS user and retry the command.
PRGO-10211: Invalid option specified when retrieving information for image series: Cause: An invalid combination of the '-series', '-image' and '-client' options was specified.; Action: Supply the correct combination of the '-series', '-image' and '-client' options when running 'rhpctl config series'. Only the following combinations are allowed: 1) no option 2) -client option only 3) -image option only 4) -series option only 5) -series and -client options only
PRGO-10321: User "{0}" lacks the authority to perform the 'config role' operation.: Cause: The user running the 'rhpctl config role' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-10391: User "{0}" lacks the authority to perform the 'config image' operation.: Cause: The user running the 'rhpctl config image' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-10461: User "{0}" lacks the authority to query series.: Cause: The user running the 'rhpctl query series' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-10481: User "{0}" lacks the authority to perform the 'config working copy' operation.: Cause: The user running the 'rhpctl config workingcopy' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-11371: User "{0}" lacks the authority to perform the 'query client' operation.: Cause: The user running the 'rhpctl query client' command did not have the required authorization.; Action: Request the authorization from the administrator or perform the operation from a user ID that has the required authorization.
PRGO-12571: failed to register image "{0}": Cause: An error occurred while attempting to register the indicated image.; Action: Examine the accompanying error messages for more information.
PRGO-13111: failed to get the directory size of path "{0}" during register image of "{1}": Cause: An attempt to determine the directory size during register image failed because either the current user or the owner specified did not have read and execute permissions for the specified directory.; Action: Ensure that either the current user or the owner specified with '-pathowner' has read and execute permissions for the specified directory. Examine the accompanying error messages for more information.
PRGO-17731: The compressed file {0} is not valid for registering.: Cause: An attempt to register an image from the specified home failed. The indicated file was either non-existent or was corrupted.; Action: Retry the operation specifying a valid compressed file.