124 PRGH-1000 to PRGH-1165

PRGH-1000: Invalid Oracle home type {0}

Cause: An unrecognized Oracle home type was specified.

Action: Ensure that a valid Oracle home type is entered. Supported home types are ORACLEDB and SOFTWARE.

PRGH-1001: Failed to get the name of the local node

Cause: An attempt to retrieve local host name failed.

Action: Examine the accompanying error messages.

PRGH-1002: Failed to copy files from {0} to {1}

Cause: An attempt to copy the files failed.

Action: Examine the accompanying error messages.

PRGH-1003: Provisioning of Oracle home at location {0} failed

Cause: One or more steps in provisioning the Oracle home failed.

Action: Examine the accompanying error messages.

PRGH-1004: Cloning operation for the Oracle home at location {0} failed

Cause: An attempt to clone an Oracle Database home directory created from a Rapid Home Provisioning image failed.

Action: Examine the accompanying error messages.

PRGH-1005: Creation of database {0} at Oracle home location {1} failed

Cause: An attempt to create database failed.

Action: Examine the accompanying error messages.

PRGH-1006: Changing the ownership for the software home at location {0} failed.

Cause: An attempt to change the ownership of software home failed.

Action: Take one of the following actions: 1) Examine the accompanying error messages. -or- 2) Make sure that any required Operating System patches are installed. To identify required patches, run 'cluvfy comp sys -p crs' command.

PRGH-1007: Changing the group ownership for the software home at location {0} failed

Cause: An attempt to change the group of software home failed.

Action: Examine the accompanying error messages.

PRGH-1008: Deletion of database {0} at Oracle home location {1} failed

Cause: An attempt to delete the database failed.

Action: Correct the problem indicated by the accompanying messages and retry the failed command

PRGH-1009: Deletion of Oracle home location {0} from inventory failed

Cause: An attempt to detach the Oracle home failed

Action: Correct the problem indicated by the accompanying messages and retry the failed command

PRGH-1010: Removal of Oracle home {0} failed

Cause: An attempt to remove the Oracle home failed

Action: Correct the problem indicated by the accompanying messages and retry the failed command.

PRGH-1011: Move of database {0} to Oracle home location {1} failed

Cause: An attempt to move the database to the new Oracle home failed.

Action: Examine the accompanying error messages.

PRGH-1012: Failed to execute sqlpatch for database {0} from Oracle home {1} on node {2}

Cause: An attempt to execute sqlpatch on the database failed.

Action: Examine the accompanying error messages.

PRGH-1013: The destination working copy at {0} on cluster {1} has the following Oracle patches installed: {2}. Execute the post-patch SQL scripts for these databases: {3}.

Cause: The post-patch SQL scripts were not executed because auto execution of the SQL script was not supported for this database version. Auto execution of the SQL script is not supported for Oracle Database versions prior to 12c.

Action: Execute the 'postinstall.sql' script for these patches if they are located under the SQL patch directory in the Oracle home. Also refer to the patch documentation for these patches and perform any applicable post-patch steps manually.

PRGH-1014: Creation of database {0} at Oracle home location {1} failed becuase the nodes {2} specified in "-nodes" option are not active

Cause: An attempt to create a database was rejected because the nodes specified in the "-nodes" option were not active.

Action: Specify nodes in the "-nodes" option that are active.

PRGH-1015: Database {0} does not exist

Cause: An attempt to operate on a database failed because the specified database did not exist.

Action: Specify a database name of a database that exists within the working copy.

PRGH-1016: Creation of database {0} at Oracle home location {1} succeeded with warnings.\n{2}

Cause: During Database Configuration Assistant (DBCA) database creation processing, one or more warning conditions occurred.

Action: Examine the logs generated by the Database Configuration Assistant (DBCA) for more information.

PRGH-1017: failed to retrieve the platform information from the specified Oracle home path "{0}"

Cause: An error occurred while attempting to retrieve the platform information.

Action: Examine the accompanying errors for more information.

PRGH-1018: The creation of database "{0}" at Oracle home location "{1}" failed because the patches for bugs {2} have not been applied.

Cause: An attempt to create a database was rejected because the required patches were not applied to the Oracle home.

Action: Apply the required patches and retry the command.

PRGH-1019: Removal of working copy directory {0} failed.

Cause: An attempt to remove the working copy directory failed.

Action: Correct the problem indicated by the accompanying error messages and retry the command.

PRGH-1020: Upgrade of database {0} at Oracle home location {1} failed.

Cause: An attempt to upgrade a database failed.

Action: Examine the accompanying error messages.

PRGH-1021: Upgrade of database {0} at Oracle home location {1} succeeded with warnings.\n{2}

Cause: During DBUA database upgrade processing, one or more warning conditions occurred.

Action: Examine the logs generated by the Database Upgrade Assistant (DBUA) for more information.

PRGH-1022: failed to get patch details from node "{0}" at Oracle home location "{1}" owned by user "{2}"

Cause: An attempt to query working copy information failed because the patch details could not be retrieved from the indicated node, possibly because the Oracle home did not exist.

Action: Ensure that the Oracle home exists. Examine the accompanying error messages for more information, address reported issues, and retry.

PRGH-1023: invalid image type {0}

Cause: An unrecognized image type was specified.

Action: Ensure that a valid image type is entered. Supported image types can be found by using the 'rhpctl query imagetype' command.

PRGH-1024: 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 set the force flag and retry the command.

PRGH-1025: failed to attach Oracle home {0} on nodes "{1}"

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

Action: Examine the accompanying error messages, address issues described and retry.

PRGH-1026: failed to update the node list for Oracle home {0} in the inventory

Cause: An attempt to run "runInstaller -updateNodeList" for the indicated Oracle home failed. The accompanying messages provide detailed failure information.

Action: Examine the accompanying error messages, address issues described and retry.

PRGH-1027: failed to stop listeners in Oracle home {0}

Cause: An attempt to stop listeners in the indicated Oracle home failed. The accompanying messages provide detailed failure information.

Action: Examine the accompanying error messages, address issues described and retry.

PRGH-1028: failed to execute "addnode.sh" to extend Oracle RAC home {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.

PRGH-1029: An I/O error occurred during installer exclude file creation.

Cause: An unexpected I/O error occurred. As a result, the appropriate exclude file could not be created.

Action: Examine the accompanying error messages for more information, address the reported issues, and retry.

PRGH-1030: The environments on nodes '{0}' do not satisfy some of the prerequisite checks.\n{1}

Cause: An attempt to add the specified working copy was rejected because the target environment did not meet some of the prerequisites. The accompanying messages provide detailed information about the prerequisites that were not met.

Action: Resolve the issues described in the accompanying messages, and then retry the provisioning operation.

PRGH-1031: The group keyword "{0}" specified in '-groups' option in 'add workingcopy' command is not valid for this image type and image version.

Cause: A group keyword was specified in the '-groups' option in the 'add workingcopy' command which was not valid based on the type and version of the image.

Action: Reissue the command with valid group keywords 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

PRGH-1032: failed to get user ID of operating system user {0}

Cause: An attempt to get the user ID for an operating system user name failed during the 'add workingcopy' operation.

Action: Correct the problem indicated by the accompanying messages and retry the failed command.

PRGH-1033: failed to get primary group ID of operating system user {0}

Cause: An attempt to get the primary group ID for an operating system user name failed during the 'add workingcopy' operation.

Action: Correct the problem indicated by the accompanying messages and retry the failed command.

PRGH-1034: required '-inventory' option missing

Cause: An attempt to create a working copy was rejected because the oraInst.loc file was not found in the default location and the '-inventory' option was not specified.

Action: Specify the inventory location using the '-inventory' option.

PRGH-1035: failed to run the deinstallation tool with error:\n{0}

Cause: An attempt to run the deinstallation tool failed during the cleanup of Oracle Grid Infrastructure. The accompanying messages provide detailed failure information. The 'delete workingcopy' operation completed, but additional action might 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.

PRGH-1036: Oracle Grid Infrastructure configuration tool failed with error '{0}' because one or more mandatory checks failed

Cause: An attempt to add the specified working copy failed because one or more mandatory checks failed in the target environment .

Action: Examine the accompanying messages and retry the command after resolving the reported failures.

PRGH-1037: failed to add instance of database {0} on node {1}

Cause: An attempt to add an instance to the indicated database on the indicated node failed. The accompanying messages provide detailed failure information.

Action: Examine the accompanying error messages, address the issues described and retry.

PRGH-1038: An error occurred while copying the installer exclude file.

Cause: The remote copy operation failed. As a result, the installer exclude file could not be copied to the node on which the 'import image' command was issued.

Action: Examine the accompanying error messages for more information, address the reported issues, and retry the operation.

PRGH-1039: Deletion of database {0} at Oracle home location {1} succeeded with warnings.\n{2}

Cause: During Database Configuration Assistant (DBCA) database deletion processing, one or more warning conditions occurred.

Action: Examine the accompanying warning messages for more information.

PRGH-1040: Upgrade of Oracle Grid Infrastructure home failed because the patches for bugs {0} have not been applied.

Cause: An attempt to upgrade the Oracle Grid Infrastructure home was rejected because the required patches were not applied to the Oracle home.

Action: Apply the required patches and retry the command.

PRGH-1041: failed to remove instance of database "{0}" on node "{1}"

Cause: An attempt to delete an instance of the specified database that is running on the specified node failed. The accompanying messages provide detailed failure information.

Action: Examine the accompanying error messages, address the issues described and retry.

PRGH-1042: failure to remove an Oracle Layered File System driver

Cause: An attempt to remove an Oracle Layered File System driver encountered a failure. The accompanying messages provide detailed failure information.

Action: Examine the accompanying error messages, address the issues described, and retry the operation.

PRGH-1043: failure to install an Oracle Layered File System driver

Cause: An attempt to install an Oracle Layered File System driver encountered a failure. The accompanying messages provide detailed failure information.

Action: Examine the accompanying error messages, address the issues described, and retry the operation.

PRGH-1044: failure to retrieve the names of the Oracle Grid Infrastructure cluster nodes

Cause: An attempt to retrieve the names of the Oracle Grid Infrastructure cluster nodes encountered a failure. The accompanying messages provide detailed failure information.

Action: Examine the accompanying error messages, address the issues described, and retry the operation.

PRGH-1045: failure while checking if "{0}" is on Oracle ACFS

Cause: An attempt to check if the specified Oracle home path was on Oracle

Action: Examine the accompanying error messages, address the issues described, and retry the operation.

PRGH-1046: failure while getting the required bug numbers for the given Oracle Database home "{0}"

Cause: An attempt to get the required bug numbers for the specified Oracle Database 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.

PRGH-1047: failure while checking if the patch "{0}" could be applied in rolling mode

Cause: An attempt to check if the specified patch could be applied in the rolling mode encountered a failure. The accompanying messages provide detailed failure information.

Action: Examine the accompanying error messages, address the issues described, and retry the operation.

PRGH-1048: failure to read or write to the file "{0}"

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

Action: Examine the accompanying error messages, address the issues described, and retry the operation.

PRGH-1049: failure to copy file "{0}" to node "{1}"

Cause: An attempt to copy the specified file 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.

PRGH-1050: failure to create directory "{0}"

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

Action: Examine the accompanying error messages, address the issues described, and retry the operation.

PRGH-1051: failure while getting the patch delta between Oracle home "{0}" and "{1}"

Cause: An attempt to get the patch delta between the specified Oracle homes encountered a failure. The accompanying messages provide detailed failure information.

Action: Examine the accompanying error messages, address the issues described, and retry the operation.

PRGH-1052: failure while getting Oracle Grid Infrastructure cluster name

Cause: An attempt to get the Oracle Grid Infrastructure cluster name encountered a failure. The accompanying messages provide detailed failure information.

Action: Examine the accompanying error messages, address the issues described, and retry the operation.

PRGH-1053: failure while deconfiguring the Oracle Grid Infrastructure

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

Action: Examine the accompanying error messages, address the issues described, and retry the operation.

PRGH-1054: failure while instantiating parameter file for addition of a node to an Oracle Grid Infrastructure cluster

Cause: An attempt to instantiate the parameter file for addition of a node 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.

PRGH-1055: failure while copying Grid Infrastructure configuration files

Cause: An attempt to copy Grid Infrastructure configuration files during an Oracle Grid Infrastructure home move 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.

PRGH-1056: failure during upgrade of an Oracle Grid Infrastructure home

Cause: An attempt to execute root scripts during an Oracle Grid Infrastructure home upgrade 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.

PRGH-1057: failure during move of an Oracle Grid Infrastructure home

Cause: An attempt to execute root scripts during an Oracle Grid Infrastructure home move 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.

PRGH-1058: failure to start the Rapid Home Provisioning Client

Cause: An attempt to start the Rapid Home Provisioning 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.

PRGH-1059: failure to add the Rapid Home Provisioning Client

Cause: An attempt to add the Rapid Home Provisioning 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.

PRGH-1060: failure while deleting node "{0}"

Cause: An attempt to delete the specified node from 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.

PRGH-1061: failure to unpin the node "{0}"

Cause: An attempt to unpin the specified node in 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.

PRGH-1062: failure while executing the Oracle Grid Infrastructure configuration tool

Cause: An attempt to execute the Oracle Grid Infrastructure configuration tool encountered a failure. The accompanying messages provide detailed failure information.

Action: Examine the accompanying error messages, address the issues described, and retry the operation.

PRGH-1063: failure while executing the scripts for Oracle Grid Infrastructure configuration

Cause: An attempt to execute scripts for Oracle Grid Infrastructure configuration encountered a failure. The accompanying messages provide detailed failure information.

Action: Examine the accompanying error messages, address the issues described, and retry the operation.

PRGH-1064: failure to retrieve the location of the Oracle Grid Infrastructure home

Cause: An attempt to retrieve the location of the Oracle Grid Infrastructure 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.

PRGH-1065: failure to retrieve the status of database "{0}"

Cause: An attempt to retrieve the status of the specified database encountered a failure. The accompanying messages provide detailed failure information.

Action: Examine the accompanying error messages, address the issues described, and retry the operation.

PRGH-1066: failure to retrieve the configuration of database "{0}"

Cause: An attempt to retrieve the configuration of the specified database encountered a failure. The accompanying messages provide detailed failure information.

Action: Examine the accompanying error messages, address the issues described, and retry the operation.

PRGH-1067: failure to retrieve the name of the node on which database "{0}" is running

Cause: An attempt to retrieve the name of the node on which the specified database was running failed. The accompanying messages provide detailed failure information.

Action: Examine the accompanying error messages, address the issues described, and retry the operation.

PRGH-1068: failure to retrieve the patch details from Oracle home "{0}" owned by user "{1}"

Cause: An attempt to to retrieve the patch details from the specified 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.

PRGH-1069: failure while checking the required bug numbers for database "{0}"

Cause: An attempt to check the required bug numbers for the specified database encountered a failure. The accompanying messages provide detailed failure information.

Action: Examine the accompanying error messages, address the issues described, and retry the operation.

PRGH-1070: failure while checking if database "{0}" is running from Oracle home "{1}"

Cause: An attempt to check if the specified database was running from the specified 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.

PRGH-1071: failure to retrieve the names of the databases running from Oracle home "{0}"

Cause: An attempt to retrieve the names of the databases running from the specified 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.

PRGH-1072: failure to retrieve the location of the Oracle home from which database "{0}" is running

Cause: An attempt to retrieve the location of the Oracle home from which the specified database was running encountered a failure. The accompanying messages provide detailed failure information.

Action: Examine the accompanying error messages, address the issues described, and retry the operation.

PRGH-1073: failure to retrieve the type of database "{0}"

Cause: An attempt to retrieve the type of the specified database encountered a failure. The accompanying messages provide detailed failure information.

Action: Examine the accompanying error messages, address the issues described, and retry the operation.

PRGH-1074: failure to retrieve the names of the nodes on which database "{0}" is running

Cause: An attempt to retrieve the names of the nodes on which the specified database was running encountered a failure. The accompanying messages provide detailed failure information.

Action: Examine the accompanying error messages, address the issues described, and retry the operation.

PRGH-1075: failed to stop instance "{0}" of database "{1}" on node "{2}"

Cause: An attempt to stop the indicated database instance failed. The accompanying messages provide detailed failure information.

Action: Examine the accompanying error messages, address the issues described and retry.

PRGH-1076: Operation to extend Oracle RAC home "{0}" to nodes "{1}" succeeded with warnings.\n{2}

Cause: While extending the specified Oracle RAC home to the specified nodes, one or more warning conditions occurred. The accompanying messages provide more information.

Action: Examine the accompanying warning messages for more information.

PRGH-1077: failed to add candidate servers to Oracle RAC One Node database {0}

Cause: An attempt to add candidate servers to the specified database failed. The accompanying messages provide detailed failure information.

Action: Examine the accompanying error messages, address the issues described, and retry the operation.

PRGH-1078: failed to remove candidate servers for Oracle RAC One Node database {0}

Cause: An attempt to remove candidate servers for the specified database failed. The accompanying messages provide detailed failure information.

Action: Examine the accompanying error messages, address the issues described, and retry the operation.

PRGH-1079: failed to execute script 'rootpre.sh' to perform preinstallation operating system preparations on nodes "{0}"

Cause: An attempt to perform preinstallation operating system preparations on the indicated nodes failed. The accompanying messages provide detailed failure information.

Action: Examine the accompanying error messages, address the issues described and retry.

PRGH-1100:

Cause: Message no longer in use.

Action: Message no longer in use.

PRGH-1101:

Cause: Message no longer in use.

Action: Message no longer in use.

PRGH-1102: The ORAchk utility in Oracle home {0} failed to execute completely.

Cause: An attempt to move a database failed because the ORAchk utility could not check the database status.

Action: Ensure that the file orachk.zip exists in the srvm/admin directory in the current Oracle Grid Infrastructure home and that the destination home is complete and writable by the database owner. Retry the command after fixing the issues.

PRGH-1103: The ORAchk utility (version {0}) is obsolete.

Cause: An attempt to move a database failed because the installed ORAchk utility was obsolete and could not determine the database status.

Action: Refer to My Oracle Support Notes and Obtain the latest ORAchk utility. Retry the command after fixing the issues.

PRGH-1104: The ORAchk report {0} at node {1} revealed failures. Move database operation cannot be done in rolling mode.

Cause: An attempt to move databases in rolling mode was rejected because some of the databases could only be moved in non-rolling mode. The ORAchk report provides additional details.

Action: Retry the command specifying non-rolling mode.

PRGH-1105: could not open file or directory.\n{0}

Cause: An attempt to move a database failed because the indicated file or directory could not be accessed.

Action: Ensure that the indicated file or directory exists and is accessible to the database owner.

PRGH-1106: could not connect to database.\n{0}

Cause: An attempt to move a database failed because it was not possible to connect to the indicated database.

Action: Ensure that it is possible to connect to the database and retry the command.

PRGH-1107: Creation of pluggable database {0} for the given multitenant container database {1} failed.

Cause: An attempt to create the indicated pluggable database failed. The accompanying messages provide detailed failure information.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

PRGH-1108: Creation of pluggable database {0} for the given multitenant container database {1} succeeded with warnings.\n{2}

Cause: During Database Configuration Assistant (DBCA) pluggable database creation processing, one or more warning conditions occurred.

Action: Examine the logs generated by the DBCA for more information.

PRGH-1109: Deletion of pluggable database {0} from the given multitenant container database {1} failed.

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

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

PRGH-1110: Deletion of pluggable database {0} from the given multitenant container database {1} succeeded with warnings.\n{2}

Cause: During Database Configuration Assistant (DBCA) pluggable database deletion processing, one or more warning conditions occurred.

Action: Examine the logs generated by the DBCA for more information.

PRGH-1111: Changing the permissions of path {0} failed.

Cause: An attempt to change the permissions of the indicated path failed. The accompanying messages provide detailed failure information.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

PRGH-1112: Pre-upgrade checks on database {0} at Oracle home location {1} succeeded with warnings.\n{2}

Cause: During Pre-Upgrade Information Tool pre-upgrade checks on the indicated database, one or more warning conditions occurred.

Action: Examine the logs generated by the Pre-Upgrade Information Tool (preupgrade.jar) for more information.

PRGH-1113: Pre-upgrade checks of database {0} at Oracle home location {1} failed.

Cause: An attempt to perform pre-upgrade checks failed. The accompanying messages provide detailed failure information.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

PRGH-1114: Move pluggable database {0} from source multitenant container database {1} to destination multitenant container database {2} failed.

Cause: An attempt to move the indicated pluggable database failed. The accompanying messages provide detailed failure information.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

PRGH-1115: Move pluggable database {0} from source multitenant container database {1} to destination multitenant container database {2} succeeded with warnings.\n{3}

Cause: During the Oracle Database Configuration Assistant (DBCA) pluggable database move process, one or more warning conditions occurred.

Action: Examine the logs generated by the DBCA for more information.

PRGH-1116: The PDB move operation is not supported because the source CDB is on node {0} and the destination CDB is on node {1}.

Cause: The pluggable database (PDB) move operation was not supported because the source multitenant container database (CDB) and the destination CDB were on different nodes or the data file of the source CDB location was not shared.

Action: Retry the PDB move operation with the source CDB and destination CDB on the same node or the data file of the source CDB location is shared.

PRGH-1117: The PDB move operation is not supported because the source CDB is version {0} and the destination CDB is version {1}.

Cause: The pluggable database (PDB) move operation was not supported because the versions of the source multitenant container database (CDB) and the destination CDB were not the same.

Action: Retry the PDB move operation with versions of the source CDB and destination CDB that are the same.

PRGH-1118: unsupported option '-ignoreprereq' specified during creation of database {0} at Oracle home location {1}

Cause: An attempt to add the specified database was rejected because the '-ignoreprereq' option was supplied and this option is permitted only when adding a database of release 12.1 or later.

Action: Retry the operation without specifying the '-ignoreprereq' option.

PRGH-1119: The specified source database {0} is not a multitenant container database.

Cause: The pluggable database (PDB) move operation was rejected because the specified source database using the -sourcecdb option was not a multitenant container database (CDB).

Action: Ensure that the source database is a CDB database.

PRGH-1120: The specified destination database {0} is not a multitenant container database.

Cause: The pluggable database (PDB) move operation was rejected because the specified desination database using the -destcdb option was not a multitenant container database (CDB).

Action: Ensure that the destination database is a CDB database.

PRGH-1121: Pluggable database "{0}" specified in the exclude list does not exist in the source multitenant container database.

Cause: The pluggable database (PDB) move operation was rejected because the specified PDB using the -excludepdblist option did not exist in the source multitenant container database (CDB).

Action: Ensure that all the PDB's, specified in the exclude list exists in the source CDB.

PRGH-1125: invalid value found {0} for the remote authentication plugin argument {1}

Cause: An attempt to execute the 'rhpctl' command with the '-auth' option failed because the specified argument value was invalid.

Action: Ensure that the specified argument has a valid value with format key:value and retry the command.

PRGH-1126: failed to add read-only database working copy because the version of the image specified is earlier than release 18c

Cause: An attempt to add a read-only database working copy was rejected because the version of the image was earlier than release 18c and was not supported.

Action: Retry the operation by specifying the database image with release 18c or later.

PRGH-1127: failed to move the database because the source working copy specified "{0}" is not a read-only home

Cause: An attempt to move the database from a source working copy to a patched working copy failed because the source working copy specified by the option -sourcewc was not a read-only home while the patched working copy was a read-only home.

Action: Retry the operation by specifying a read-only source working copy for the option -sourcewc.

PRGH-1128: failed to move the database because the patched working copy specified "{0}" is not a read-only home

Cause: An attempt to move the database from a source working copy to a patched working copy failed because the patched working copy specified by the option -patchedwc was not a read-only home while the source working copy was a read-only home.

Action: Retry the operation by specifying a read-only patched working copy for the option -patchedwc.

PRGH-1129: The specified destination home {0} is not a RAC enabled home.

Cause: An attempt to upgrade or move the Oracle Grid Infrastructure (GI) was rejected because the destination home was not configured as a RAC enabled home.

Action: Retry the move or upgrade command specifying a different destination home that is RAC enabled.

PRGH-1130: CRS stack is running on more than one node.

Cause: An attempt to upgrade or move the Oracle Grid Infrastructure (GI) was rejected because CRS stack was running on two or more nodes. For self-patching in non-rolling mode, CRS stack should be running only on local node.

Action: Manually shut down the CRS stack on other nodes and retry the move or upgrade command.

PRGH-1131: The location on target "{0}" did not match with the image.

Cause: An attempt to provision a working copy was rejected because the checksum validation for the indicated file failed. If this file is not specified by the "-location" option, it points to the default location file of the image on the target.

Action: Ensure that the specified or the default location file on the target is the same file that is associated with the image.

PRGH-1132: The specified storage type "{0}" is incompatible with the local mount option.

Cause: An attempt to provision a working copy was rejected because only the LOCAL storage type was supported in the local mount mode when the "-localmount" option was specified.

Action: Retry the command with the LOCAL storage type.

PRGH-1133: The specified image "{0}" is incompatible with the local mount option.

Cause: An attempt to provision a working copy was rejected because the specified image did not support provisioning in the local mount mode. The compatible images should be imported with -location option.

Action: Either specify the same image without the option -localmount, or specify an image that is imported with -location option.

PRGH-1135: There are no servers matching the specified regular expression "{0}".

Cause: An attempt to run an operation on Rapid Home Provisioning (RHP) servers failed because neither the name of the local RHP server nor of any of its peer servers matched the specified expression.

Action: Verify the regular expression specified and retry the operation.

PRGH-1136: database by name {0} and {1} exist in target cluster

Cause: The specified database could not be migrated because a database with the same name already exists.

Action: Ensure that the database by name of source database does not exist in the target and retry.

PRGH-1137: The specified Oracle home path {0} is a symbolic link path on nodes {1}.

Cause: An attempt to add the specified working copy was rejected because the the specified path is a symbolic link.

Action: Retry the command specifying the path for an Oracle home that is not symbolic path.

PRGH-1138: Creation of database {0} at Oracle home location {1} using DBCA failed on the indicated node {2} of cluster {3}.\nError details: "{4}"

Cause: During Database Configuration Assistant (DBCA) database creation processing, one or more error conditions occurred due to incorrect input to DBCA.

Action: Examine the the accompanying messages for more information.

PRGH-1139: Creation of database {0} at Oracle home location {1} using DBCA failed on the indicated node {2}.\nError details: "{3}"

Cause: During Database Configuration Assistant (DBCA) database creation processing, one or more error conditions occurred due to incorrect input to DBCA.

Action: Examine the the accompanying messages for more information.

PRGH-1140: The specified bug numbers "{0}" are not present in the working copy.

Cause: An attempt to remove the bug numbers from the working copy bug list failed because the specified bug numbers were not associated with the existing workingcopy.

Action: Verify the argument value and retry the operation.

PRGH-1143: Cloning operation for the Oracle home at location {0} failed on the nodes {1}.

Cause: An attempt to clone an Oracle Database home directory created from a Rapid Home Provisioning image failed.

Action: Examine the accompanying error messages.

PRGH-1144: User "{0}" lacks the authority to perform the 'replicate image' operation.

Cause: The user running the 'rhpctl replicate 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.

PRGH-1145: User "{0}" lacks the authority to perform the 'instantiate image' operation.

Cause: The user running the 'rhpctl instantiate 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.

PRGH-1146: Command execution not allowed because the user lacks the authority.

Cause: Command execution was rejected because the user was not authorized to perform the operation.

Action: Run the command as the user who installed and configured the server.

PRGH-1147: User "{0}" does not have permission to perform the 'allow client' operation.

Cause: An attempt to execute the command 'rhpctl allow client' 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.

PRGH-1148: User "{0}" does not have permission to perform the 'disallow client' operation.

Cause: An attempt to execute the command 'rhpctl disallow client' 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.

PRGH-1149: User "{0}" for cluster "{1}" was already allowed access to client {2}.

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

Action: Ensure the correct user was specified.

PRGH-1150: Role "{0}" was already allowed access to client "{1}".

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

Action: Ensure the correct role was specified.

PRGH-1151: User "{0}" for cluster "{1}" has never been granted access to client {2}.

Cause: An attempt to disallow the user from access privilege to the client failed because the user had never been granted access privilege to the client using the 'rhpctl allow client' command.

Action: Use the 'rhpctl disallow client' command to disallow access privilege from another user.

PRGH-1152: Role "{0}" has never been granted access to client "{1}".

Cause: An attempt to disallow the role from access privilege to the client failed because the role had never been granted access privilege to the client using the 'rhpctl allow client' command.

Action: Use the 'rhpctl disallow client' command to disallow access privilege from another role.

PRGH-1153: RHPHelper call to get runing nodes failed for DB: "{0}".

Cause: An attempt to get Running Nodes failed during the ssh call.

Action: Go through rhphelper logs in the target nodes and find the detailed reason for the failure.

PRGH-1154: Invalid option '-{0}' specified when adding a client.

Cause: An invalid option to map roles was specified while adding a client.

Action: Add the client without the option to map roles and then grant the roles individually.

PRGH-1161: The fast recovery area parameter is already set for database "{0}" and is different from the value passed in the -fra argument.

Cause: An attempt to setup autoupgrade tool to perform the upgrade of the database failed because there is already a fast recovery area set for the database and the argument -fra was used to set a different value.

Action: Verify the argument value and retry the operation.

PRGH-1162: The version of the software at the specified path "{0}" is incompatible with the image version "{1}".

Cause: An attempt to provision a working copy was rejected because the version of the image associated with the path specified was not the same as the version of the image specifed.

Action: Retry the command with a different path.

PRGH-1163: The integrity check failed for the zip file "{0}".

Cause: An attempt to import an image was rejected because the specified zip file and the 'location on target' file had different checksums.

Action: Ensure that the zip file to be imported is identical to the 'location on target' file.

PRGH-1164: Failed to verify the integrity of the file "{0}".

Cause: An attempt to provision a working copy was rejected because the checksum validation for the 'location on target' file failed. If this file is not specified by the "-locationontarget" option, it points to the default 'location on target' file of the image.

Action: Ensure that the specified or the default 'location on target' file is readable from the target node for the intended user.

PRGH-1165: Failed to update the configuration files {0} on node {1}.\n"{2}"

Cause: An error occurred while updating the configuration files.

Action: Examine the accompanying error messages, address the issues described and retry the operation.