119 PRGH-01001 to PRGH-01135
- PRGH-01001: Failed to get the name of the local node
-
Cause: An attempt to retrieve local host name failed.
- PRGH-01002: Failed to copy files from {0} to {1}
-
Cause: An attempt to copy the files failed.
- PRGH-01003: Provisioning of Oracle home at location {0} failed
-
Cause: One or more steps in provisioning the Oracle home failed.
- PRGH-01004: 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.
- PRGH-01005: Creation of database {0} at Oracle home location {1} failed
-
Cause: An attempt to create database failed.
- PRGH-01006: Changing the ownership for the software home at location {0} failed.
-
Cause: An attempt to change the ownership of software home failed.
- PRGH-01007: Changing the group ownership for the software home at location {0} failed
-
Cause: An attempt to change the group of software home failed.
- PRGH-01008: Deletion of database {0} at Oracle home location {1} failed
-
Cause: An attempt to delete the database failed.
- PRGH-01009: Deletion of Oracle home location {0} from inventory failed
-
Cause: An attempt to detach the Oracle home failed
- PRGH-01010: Removal of Oracle home {0} failed
-
Cause: An attempt to remove the Oracle home failed
- PRGH-01011: Move of database {0} to Oracle home location {1} failed
-
Cause: An attempt to move the database to the new Oracle home failed.
- PRGH-01012: Failed to execute sqlpatch for database {0} from Oracle home {1} on node {2}
-
Cause: An attempt to execute sqlpatch on the database failed.
- PRGH-01013: 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.
- PRGH-01014: 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.
- PRGH-01015: Database {0} does not exist
-
Cause: An attempt to operate on a database failed because the specified database did not exist.
- PRGH-01016: Creation of database {0} at Oracle home location {1} succeeded with warnings.\n{2}
-
Cause: During DBCA database creation processing, one or more warning conditions occurred.
- PRGH-01017: failed to retrieve the platform information from the specified Oracle home path "{0}"
-
Cause: An error occurred while attempting to retrieve the platform information.
- PRGH-01018: 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.
- PRGH-01019: Removal of working copy directory {0} failed.
-
Cause: An attempt to remove the working copy directory failed.
- PRGH-01020: Upgrade of database {0} at Oracle home location {1} failed.
-
Cause: An attempt to upgrade a database failed.
- PRGH-01021: 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.
- PRGH-01022: 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.
- PRGH-01023: invalid image type {0}
-
Cause: An unrecognized image type was specified.
- PRGH-01024: 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.
- PRGH-01025: 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.
- PRGH-01026: 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.
- PRGH-01027: 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.
- PRGH-01028: 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.
- PRGH-01029: 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.
- PRGH-01030: 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.
- PRGH-01031: 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.
- PRGH-01032: 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.
- PRGH-01033: 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.
- PRGH-01034: 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.
- PRGH-01035: 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.
- PRGH-01036: 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 .
- PRGH-01037: 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.
- PRGH-01038: 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.
- PRGH-01039: Deletion of database {0} at Oracle home location {1} succeeded with warnings.\n{2}
-
Cause: During DBCA database deletion processing, one or more warning conditions occurred.
- PRGH-01040: 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.
- PRGH-01041: 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.
- PRGH-01042: 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.
- PRGH-01043: 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.
- PRGH-01044: 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.
- PRGH-01045: failure while checking if "{0}" is on Oracle ACFS
-
Cause: An attempt to check if the specified Oracle home path was on Oracle
- PRGH-01046: 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.
- PRGH-01047: 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.
- PRGH-01048: 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.
- PRGH-01049: 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.
- PRGH-01050: failure to create directory "{0}"
-
Cause: An attempt to create the specified directory encountered a failure. The accompanying messages provide detailed failure information.
- PRGH-01051: 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.
- PRGH-01052: 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.
- PRGH-01053: 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.
- PRGH-01054: 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.
- PRGH-01055: 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.
- PRGH-01056: 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.
- PRGH-01057: 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.
- PRGH-01058: 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.
- PRGH-01059: 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.
- PRGH-01060: 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.
- PRGH-01061: 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.
- PRGH-01062: 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.
- PRGH-01063: 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.
- PRGH-01064: 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.
- PRGH-01065: 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.
- PRGH-01066: 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.
- PRGH-01067: 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.
- PRGH-01068: 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.
- PRGH-01069: 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.
- PRGH-01070: 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.
- PRGH-01071: 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.
- PRGH-01072: 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.
- PRGH-01073: 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.
- PRGH-01074: 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.
- PRGH-01075: 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.
- PRGH-01076: 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.
- PRGH-01077: 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.
- PRGH-01078: 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.
- PRGH-01079: 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.
- PRGH-01100:
-
Cause: Message no longer in use.
- PRGH-01101:
-
Cause: Message no longer in use.
- PRGH-01102: 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.
- PRGH-01103: 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.
- PRGH-01104: 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.
- PRGH-01105: 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.
- PRGH-01106: 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.
- PRGH-01107: 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.
- PRGH-01108: 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.
- PRGH-01109: 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.
- PRGH-01110: 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.
- PRGH-01111: 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.
- PRGH-01112: 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.
- PRGH-01113: 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.
- PRGH-01114: 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.
- PRGH-01115: 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.
- PRGH-01116: 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.
- PRGH-01117: 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.
- PRGH-01118: 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.
- PRGH-01119: 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).
- PRGH-01120: 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).
- PRGH-01121: 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).
- PRGH-01125: 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.
- PRGH-01126: 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.
- PRGH-01127: 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.
- PRGH-01128: 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.
- PRGH-01129: 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.
- PRGH-01130: 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.
- PRGH-01131: The integrity check failed for the file "{0}".
-
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.
- PRGH-01132: 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.
- PRGH-01133: 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.
- PRGH-01135: 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.