42 UPGAST-00001 to UPGAST-05022

UPGAST-00001: unable to continue due to an unexpected error: Cause: An unexpected error occurred.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00002: Invalid argument {0}; an argument must begin with a hyphen. Enter the command "{1} -help" for details.: Cause: A command-line argument did not start with a hyphen.; Action: Run the command again, using a hyphen to identify any arguments.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00003: invalid argument {0}. Enter the command "{0} -help" for details.: Cause: The specified argument was not recognized.; Action: Run the command again, specifying a valid argument.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00004: Value for argument {0} not supplied. Enter the command "{1} -help" for details.: Cause: The value for a command-line argument was not specified.; Action: Run the command again, specifying the required value for the command-line argument.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00007: Domain {0} is configured as a compact domain which is not a valid starting point for upgrade.: Cause: A compact configured domain was specified.; Action: Specify a domain that is not configured as a compact domain.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00008: failed to copy {0} to domain: Cause: Unable to copy the specified file to the domain.; Action: See the Upgrade Assistant log file for details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00009: Invalid log level: {0}. Enter the command "{1} -help" for details.: Cause: The log level specified was not recognized.; Action: Run the command again, specifying a valid log level.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00010: Port number {0} is not valid.: Cause: The port number specified was not a positive numeric value or was out of range.; Action: Specify a valid port number.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00011: Host name {0} is not valid or unknown.: Cause: Lookup of the specified host name failed.; Action: Specify a valid host name.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00012: Required port is missing.: Cause: A required port was not entered.; Action: Enter the required port.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00013: Required user name is missing.: Cause: A required user name was not entered.; Action: Enter the required user name.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00014: unable to connect to WebLogic Server at {0}:{1}: Cause: Failed connecting to the WebLogic Server at the specified host and port.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00015: Required listen address is missing.: Cause: A required listen address was not entered.; Action: Enter the required listen address.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00016: Required password is missing.: Cause: A required password was not entered.; Action: Enter the required password.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00017: Required confirm password is missing.: Cause: A required confirm password was not entered.; Action: Enter the required confirm password.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00018: Password and confirm password do not match.: Cause: The password and confirm password do not have the same value.; Action: Enter the same value for the password and confirm password.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00019: User name may not contain commas, tabs, spaces, or any of the following characters: {0}: Cause: An invalid user name was specified.; Action: Enter the user name using only valid characters.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00020: Listen address {0} is not valid or unknown.: Cause: Lookup of the specified listen address failed.; Action: Specify a valid listen address.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00021: WLST script failure, see {0} for details: Cause: The execution of a WLST script has failed; Action: Check the specified WLST output file for the details of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00023: Standalone template {0} does not exist for component {1} of type {2}.: Cause: A template was not found for the listed component.; Action: Install the components standalone environment and then rerun the upgrade in that standalone environment.
Level: 1

Type: WARNING

Impact: Upgrade

UPGAST-00024: failed reading {0}: Cause: Unable to read or parse the specified file.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00025: The password must be at least 8 alphanumeric characters with at least one number or special character.: Cause: An invalid password was specified.; Action: Enter a password using 8 alphanumeric characters with at least one number or special character.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00026: failed reading {0}: Cause: Unable to read or parse the specified OPMN file.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00027: OPMN file {0} does not exist in the instance directory.: Cause: The specified OPMN file did not exist.; Action: Specify a valid instance directory where the specified OPMN file exists
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00028: Template {0} does not exist for component {1} of type {2}.: Cause: A template was not found for the listed component.; Action: Install the listed component and then rerun the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00029: Directory is not a valid domain for upgrade. {0}: Cause: The specified directory was not a valid Oracle WebLogic domain for standalone upgrades. The domain was not created during a previous standalone upgrade.; Action: Specify an Oracle WebLogic domain that is created during a previous standalone upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00030: The specified domain name {0} is invalid. It must include only alphanumeric characters, hyphens ("-") or underscore characters ("_") and contain at least one letter but must not start with a number.: Cause: An invalid domain name was specified.; Action: Enter a valid domain name.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00031: unable to get the active DomainMBean for the WebLogic Server domain: Cause: Failed getting the active DomainMBean for the WebLogic Server domain.; Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00032: unable to communicate with the WebLogic Server: Cause: Communication with the WebLogic Administrative Server was either lost or never established.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00033: Required domain directory is missing.: Cause: A required domain directory was not entered.; Action: Enter the required domain directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00037: unable to fetch or store attribute "{0}" in the WebLogic Server: Cause: The most common cause is an incorrect attribute name.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00039: failed deleting {0}: Cause: Unable to delete the specified file.; Action: Manually delete the specified file.
Level: 1

Type: WARNING

Impact: Upgrade

UPGAST-00040: unable to get the DomainRuntimeMBean for the WebLogic Server domain: Cause: Failed getting the DomainRuntimeMBean for the current WebLogic Server domain.; Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00041: unable to connect to WebLogic Server at {0}:{1}: Cause: Failed connecting to the WebLogic Server at the specified host and port.; Action: See the Upgrade Assistant log file for details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00047: failed to read the installer inventory: Cause: The install inventory could not be accessed.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00048: unable to open the file: Cause: Failed to open the file.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00049: unable to read the file: Cause: Failed to read the file.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00050: unable to create logging directory: {0}: Cause: The directory for log files could not be created.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00051: unable to create the log file: Cause: Failed to create the log file.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00052: unable to initialize logging: Cause: Initialization of logging failed.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00053: No upgrade components were found in the config file {0}.: Cause: No upgrade components in the specified configuration file.; Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00054: An error occurred loading the domain configuration file {0}: Cause: Either the specified directory does not contain the expected file, or the file does not conform to the expected syntax.; Action: Specify a valid WebLogic domain root directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00055: An error occurred loading the schema creation configuration file {0}: Cause: An unexpected error occurred loading the schema creation configuration file.; Action: Contact My Oracle Support. See the secondary error message for additional details.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00056: error initializing upgrade plug-in for {0}: Cause: An unexpected error occurred initializing an upgrade plug-in.; Action: Contact My Oracle Support. See the secondary error message for additional details.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00058: {0} file does not exist or cannot be accessed.: Cause: The specified file did not exist or could not be accessed.; Action: Make sure the path to the file is correct.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00079: failed to create temporary directory: {0}: Cause: An error was encountered creating a temporary directory.; Action: Ensure that the directory location exists and is not protected.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00093: {0} directory does not exist or is not a directory.: Cause: The specified directory did not exist or was not a directory.; Action: Specify a valid directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00094: {0} directory already exists.: Cause: The specified directory already existed.; Action: Specify a valid directory that does not exist.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00095: {0} directory is not writable.: Cause: The specified directory must have write permissions.; Action: Specify a directory that is writable or correct the permissions.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00096: error initializing the help system: Cause: An error occurred while setting up the help system.; Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00097: The IP address of the host {0} cannot be determined.: Cause: The network address of the specified host could not be determined.; Action: Check the validity of the specified host.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00098: error setting the Oracle look-and-feel for the graphical user interface: Cause: An error occurred while setting the appearance for the graphical user interface.; Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00107: The DISPLAY environment variable is not set. The graphical user interface (GUI) requires that this environment variable be set on UNIX.: Cause: The required DISPLAY environment variable was not defined.; Action: Set the required DISPLAY environment variable and then rerun the Upgrade Assistant.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00173: The plugin for {0} has requested an input value named {1} but that name is not in the upgrade descriptor.: Cause: There was an inconsistency between the plugin descriptor definition and the input values requested by the plugin.; Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00174: failed to create or write to response file: Cause: The file specified for saving responses could not be created or written to.; Action: Specify a file in a location that is writable.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00175: Can not read response file {0}.: Cause: The file specified for reading responses does not exist, or can not be read.; Action: Specify a readable response file.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00176: Response file specifies an unknown upgrade step {0}.: Cause: The response file specifies an upgrade that is unknown in this Fusion Middleware installation. Either the response file is for some other environment, or the Upgrade Descriptor files have not been properly installed.; Action: Specify a response file generated for this installation.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00177: Response file line is not understood: {0}: Cause: The response file contains syntax errors.; Action: Correct the syntax errors in the response file and run the Upgrade Assistant again.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00178: Response file specifies a bad input name, {0}.: Cause: The response file contains syntax errors, or is not of the correct version.; Action: Correct the syntax errors in the response file and run the Upgrade Assistant again.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00180: error loading upgrade plug-in for {0}: Cause: An unexpected error occurred loading an upgrade plug-in.; Action: Contact My Oracle Support. See the secondary error message for additional details.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00181: error during execution of upgrade plug-in for {0}: Cause: An unexpected error occurred during execution of an upgrade plug-in.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00182: The examination phase for plug-in {0} will not be run due to a previous error.: Cause: An error occurred when loading or initializing the plug-in which prevented the examination phase from running.; Action: Review the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00183: The upgrade phase for plug-in {0} will not be run due to a previous error.: Cause: An error occurred when loading or initializing the plug-in which prevented the upgrade phase from running.; Action: Review the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00185: failed to load JDBC driver: Cause: There was a failure loading a JDBC driver.; Action: See the log file for details. Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00186: unable to connect to database as the DBA user name {0}: Cause: Required fields to connect to a database were not supplied.; Action: Enter the missing required fields and rerun.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00187: Unable to connect to WebLogic Admin Server. Some fields are empty.: Cause: Required fields to connect to a WebLogic Admin Server were not supplied.; Action: Enter the missing required fields and rerun.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00189: Exception raised while running an external command.: Cause: An exception was raised while running an external command (such as sqlplus) in a subprocess. Check the stack trace for detailed information.; Action: Attempt to correct the environment problem if any, then retry the upgrade. Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00190: {0} component version is {1}, status is {2}, upgraded flag is {3}: Cause: After a successful schema upgrade the SCHEMA_VERSION_REGISTRY status column is not "VALID", or the upgraded column is not "Y".; Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00191: unable to validate the SCHEMA_VERSION_REGISTRY for component {0}: Cause: An unexpected error occurred validating the SCHEMA_VERSION_REGISTRY.; Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00192: A dependency by component {0} on component {1} is unresolved.: Cause: A required component was not found while discovering upgrade components and their dependencies.; Action: Make sure the required component has been installed and that its upgrade descriptor XML file is in the plugins/upgrade directory of their product home.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00193: unable to connect to database for creating schemas {0}: Cause: Required fields to connect to a database were not supplied.; Action: Specify the missing required fields and rerun.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00194: An invalid component id for creating schemas was specified: {0}.: Cause: An invalid component id was specified in the response file.; Action: Specify a valid component for creating schemas.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00195: Edition name {0} specified in response file does not exist in database.: Cause: The response file specified an edition name for creating schemas that does not exist.; Action: Specify an existing edition name and rerun.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00196: The validate method for plug-in {0} will not be called due to a previous error.: Cause: An error occurred when loading or initializing the plug-in which prevents the validate method from executing.; Action: Review the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00198: Descriptor tag {0} is only allowed in components of type={1}: Cause: An upgrade plugin descriptor is improperly formed.; Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00200: Message reference {0} is not defined in resource bundle {1}.: Cause: An upgrade plugin descriptor is referencing an undefined message.; Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00202: Unable to validate credentials. Some fields are empty.: Cause: Required fields to validate credentials were not supplied.; Action: Enter the missing required fields and rerun.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00203: validate method is not implemented by plug-in {0} for input named {1}.: Cause: Required validate method was not implemented by plug-in or the signature of the validate method is incorrect.; Action: Implement the required validate method with the correct signature.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00204: Response file specifies an unknown field "{0}".: Cause: The response file specifies an input value with a qualified field name that is unknown for inputs of this type.; Action: Specify a response file generated for this installation or correct your editing error.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00205: Response file specifies an incorrect or no format version. Version must be {0}.: Cause: The fileFormatVersion specified in the [GENERAL] section of the file is either missing or incorrect for this program.; Action: Generate new response files using the same version of the program that is going to read them.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00206: No upgrade descriptor files were found in the Oracle home, yet a response file was specified.: Cause: Either this Oracle home contains no upgradable components and you are using a response file generated for a different installation, or the installation is incomplete or damaged.; Action: Make sure that this installation is the one you intended to upgrade, and that the Upgrade Descriptor files are in the plugins/upgrade/ directories
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00207: The Upgrade Descriptor in file {0} specifies a bad value "{1}" for the attribute named "{2}".: Cause: An attribute in a tag in an Upgrade Descriptor, which provides information to the Upgrade Assistant about individual upgrade plugins, contains an improper value.; Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00208: An unrecognized database type "{0}" was specified in a descriptor or response file.: Cause: Database type names in descriptor and response files must come from a fixed list of names. A name was encountered which is not on the list.; Action: Correct the spelling of your database type and run the program again.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00209: directory path is not specified: Cause: A required directory path was not entered.; Action: Enter the required directory path.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00210: file path is not specified: Cause: A required file path was not entered.; Action: Enter the required file path.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00211: The response file specified a dependency on a plugin numbered {0} but either no plugin in the file has that as an INSTANCE value, or the descriptor file does not indicate that such a dependency is possible.: Cause: All dependsOnPluginInstance properties must refer to numbers defined earlier in the response file with a pluginInstance property, and must refer to a plugin to which such a dependency is allowed by the upgrade descriptor file.; Action: If you created or edited the response file, correct the error and try again. If this is a response file generated by the Upgrade Assistant, contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00212: unable to connect to database as the schema user {0}: Cause: Required fields to connect to a database were not supplied.; Action: Enter the missing required fields and rerun.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00213: Unable to connect to database as the dba user "{0}".: Cause: The database connection failed for the specified reason.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00214: Unable to connect to database as the schema user "{0}".: Cause: The database connection failed for the specified reason.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00215: Upgrade is not being done due to examine failures.: Cause: When using a response file, actual upgrades are not done if any plugin can not complete its EXAMINE phase.; Action: Correct the problem using information provided in the log file; then retry the operation.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00216: A library file "{0}" referred to in an Upgrade Descriptor file does not exist.: Cause: Upgrade Plugins can refer to other JAR files. A file in such a reference can not be found. This can be caused by an incorrect installation.; Action: Contact My Oracle Support
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00217: directory path is not specified {0}: Cause: A required directory path was not entered.; Action: Enter the required directory path.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00218: file path is not specified {0}: Cause: A required file path was not entered.; Action: Enter the required file path.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00219: No schemas were found for component {0} in the Schema Version Registry.: Cause: A database query to get a list of schemas from the Schema Version Registry returned an empty list.; Action: Verify that you have schemas for the specified component.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00220: failed to get a list of schemas from the Schema Version Registry: Cause: A database query to get a list of schemas from the Schema Version failed.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00221: unexpected error upgrading schema: Cause: An unexpected error occurred during schema upgrade.; Action: Check the error messages in the Upgrade Assistant log files. Correct the problem before running the Upgrade Assistant again.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00222: invalid database type specified: Cause: An invalid database type was specified.; Action: The database type specified is not supported by the RCU JDBCEngine. Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00223: The upgrade of "{0}" is being skipped because the upgrade for "{1}" has either failed or been skipped.: Cause: One component upgrade which is a pre-requisite for a second component's upgrade has not finished successfully. Therefore the second component's upgrade has not been executed.; Action: Fix the original problem and run Upgrade again.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00224: The specified database does not contain any schemas for {0} or the database user lacks privilege to view the schemas.: Cause: The database you have specified does not contain any schemas registered as belonging to the component you are upgrading, or else the current database user lacks privilege to query the contents of the schema version registry.; Action: Verify that the database contains schema entries in schema version registry. If it does not, specify a different database. Verify that the user has DBA privilege. Connect to the database as DBA.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00225: The response file contains a non-numeric value "{0}" where a number is required.: Cause: Plugin ID numbers must be decimal integers.; Action: Correct the response file and run the program again.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00226: The database connect string format is incorrect. The correct format is: {0}: Cause: The database connect string format was specified incorrectly.; Action: Enter the database connect string using the correct format.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00227: Oracle instance directory path is not specified: Cause: A required Oracle instance directory path was not entered.; Action: Enter the required Oracle instance directory path.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00228: Oracle instance directory path is not specified {0}: Cause: A required Oracle instance directory path was not entered.; Action: Enter the required Oracle instance directory path.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00229: The directory {0} is not an 11g Oracle instance directory.: Cause: The directory specified was not a valid 11g Oracle instance directory.; Action: Enter a valid 11g Oracle instance directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00230: No editions were found: Cause: A database query to get a list of editions returned an empty list.; Action: Verify that you have editions enabled and have created one or more editions.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00231: failed to get a list of editions: Cause: A database query to get a list of editions failed; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00232: database query for compatibility failed: {0}: Cause: A database query to check that database compatibility is 11.2.0 or greater failed; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00233: database compatibility must be 11.2.0 or greater not {0}: Cause: An EBR-enabled Oracle database requires that compatibility parameter be set to "11.2.0" or greater. However the actual compatibility was less than version 11.2.0; Action: Issue the SQL command ALTER SYSTEM SET COMPATIBLE = '11.2.0' SCOPE=SPFILE.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00234: Unable to connect to database using SSL settings as the dba user "{0}".: Cause: The database connection failed for the specified reason. The connection failure could be due to incorrect SSL settings or incorrect database setup.; Action: See the secondary error message(s) and the Upgrade Assistant log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00235: Schema version registry table does not exist for component {0}: Cause: An attempt to list the contents of the schema version registry table for the component failed because the schema version registry does not exist.; Action: This is an informational message. No further action is necessary.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGAST-00236: There is no schema version registry entry for component {0}: Cause: An attempt to list the contents of the schema version registry table for the component failed because no registry entry exists for the component.; Action: This is an informational message. No further action is necessary.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGAST-00237: A duplicate component definition for component {0} has been detected in product home {1}.: Cause: Component names must be unique within an Oracle home. Either the component descriptor files are incorrect, or multiple copies of the same component have been installed in the same Oracle home.; Action: Remove the duplicate installations, or contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00238: Warning: A dependency by component {0} on component {1} is unresolved. Upgrades of component {0} will be disabled.: Cause: A dependent component was not found while discovering upgrade components and their dependencies.; Action: Make sure the required component has been installed.
Level: 1

Type: WARNING

Impact: Upgrade

UPGAST-00239: messageclass attribute must be specified for message reference {0}: Cause: A resource bundle was not specified in the component's upgrade descriptor.; Action: Specify the component's resource bundle using the messageclass attribute.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00240: An unexpected error was encountered while monitoring the progress of a plugin.: Cause: During the upgrade phase of a plugin, the upgrade monitor thread encountered an error while shutting down; Action: The Fusion Middleware schema upgrade was not impacted and the error can be ignored.
Level: 1

Type: WARNING

Impact: Upgrade

UPGAST-00244: unable to connect to {0} Server {1}: Cause: Required fields to connect to the specified Server were not supplied.; Action: Enter the missing required fields and rerun.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00245: An unexpected error has occurred while initializing internal data structures.: Cause: A problem was encountered while setting up the internal WLS descriptor.; Action: Contact My Oracle Support
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00246: The selected domain has a version of {0} which is less than the minimum of {1}.: Cause: Upgrade requires the domain to be at a certain minimum version, which this domain does not meet.; Action: Select a different domain, or run the Reconfiguration tool before trying to upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00247: unable to connect to WebLogic Server at {0}:{1} {2}: Cause: Failed connecting to the WebLogic Server at the specified host and port.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00248: Descriptor item {0} missing required "text" attribute.: Cause: The named input tag in an upgrade descriptor does not have a required "text" attribute.; Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00249: isOptionalInputRequired method is not implemented by plug-in {0} for input named {1}.: Cause: Required isOptionalInputRequired method was not implemented by plug-in or the signature of the isOptionalInputRequired is incorrect.; Action: Implement the required isOptionalInputRequired method with the correct signature.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00250: Required input {0} is missing from section {1} in the response file.: Cause: The response file does not supply any values for a required input.; Action: Correct the response file and retry the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00251: An error occurred reading Upgrade Descriptor file {0}: Cause: The file does not conform to the expected syntax.; Action: See the secondary message for additional information. Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00252: Required input {0} is missing from section {1} in response file.: Cause: The response file does not supply any values for an optional input that the plugin indicates it needs in this case.; Action: Correct the response file and retry the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00254: invalid response file contents: Cause: The response file is not a valid response file.; Action: Specify a response file generated for this installation or correct your editing error. See secondary message for details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00255: More than one component definition contains an upgrade for a component. The following component descriptor files each contain an upgrade for component {0}: {1}: Cause: There must be only one upgrader of a component within an Oracle home. Two or more schema input declarations exist that are upgrading the same component-id.; Action: Remove the duplicate upgrades, or contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00256: Upgrade is being skipped because the -examine flag is set: Cause: When using a response file, actual upgrades are not done when the -examine command line option is set.; Action: If you want to perform an actual upgrade in response file mode remove the -examine flag from the command line. If you intended to perform just the examine phase, no action is necessary.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00257: The -examine flag is only allowed with the -response flag: Cause: You cannot specify -examine command line option without the -response option.; Action: You cannot specify the -examine flag when running the upgrade tool in GUI mode. If you want to perform an examine without an actual upgrade you must also specify -response on the command line.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00258: Component plugin {0} named in response file is not in domain {1}.: Cause: The response file references a component plugin which is not configured in the specified domain.; Action: Specify a response file generated for this domain.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00259: The getInitialValue method for plug-in {0} will not be called due to a previous error.: Cause: An error occurred when loading or initializing the plug-in which prevents the getInitialValue method from executing.; Action: Review the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00260: getInitialValue method is not implemented by plug-in {0} for input named {1}.: Cause: Required getInitialValue method was not implemented by plug-in or the signature of the getInitialValue method is incorrect.; Action: Implement the required getInitialValue method with the correct signature.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00261: The isOptionalInputRequired method for plug-in {0} will not be called due to a previous error.: Cause: An error occurred when loading or initializing the plug-in which prevents the isOptionalInputRequired method from executing.; Action: Review the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00262: The log directory did not exist or cannot be accessed: {0}.: Cause: The log directory specified was not recognized as an existing, writable directory.; Action: Run the command again, specifying a valid log directory. If necessary create the log directory and make sure it is a writable directory. See the command line help for details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00263: The response file contained both configuration type and schema type upgrades.: Cause: The response file contains a mix of configuration type and schema type upgrades.; Action: Change the response file to specify only configuration type or schema type upgrades then rerun the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00264: Bad "name" attribute value in Upgrade Descriptor.: Cause: Names in Upgrade Descriptor files must be alphanumeric.; Action: Correct the name.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00265: Directory is not a valid domain for upgrade. {0}: Cause: The specified directory was not a valid Oracle WebLogic domain.; Action: Specify an existing WebLogic domain directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00266: Oracle instance directory {0} is not a unique directory path.: Cause: A duplicate Oracle instance directory path was specified.; Action: Specify Oracle instance directoies that are not duplicated.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00267: isUpgradeRequired method is not implemented by plug-in {0}.: Cause: Required isUpgradeRequired method was not implemented by plug-in or the signature of the isUpgradeRequired is incorrect.; Action: Implement the required isUpgradeRequired method with the correct signature.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00268: The response file specified is not for a standalone upgrade.: Cause: The response file contained WebLogic credentials that are not valid during a standalone upgrade.; Action: Regenerate the response file and rerun the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00269: The response file specified is not for an upgrade requiring WebLogic credentials.: Cause: The response file does not contain WebLogic credentials that are required during an online upgrade.; Action: Regenerate the response file and rerun the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00270: Directory is not a valid domain for upgrade. {0}: Cause: The specified directory was not a valid Oracle WebLogic domain.; Action: See the log file for details. Specify a valid WebLogic domain directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00271: Validation of specified domain failed. {0}: Cause: The specified domain failed validation which will prevent domain reconfiguration.; Action: Refer to the Troubleshooting section of your upgrade documentation for info on supported domain upgrades. See the log file for details of the validation failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00272: Unable to connect to EBR-enabled Oracle database for schema {0} because an edition name was not specified.: Cause: An edition name must be provided to establish a connection to an EBR-enabled Oracle Database.; Action: Add an edition name to the response file (when using response file mode).
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00273: Initialization of the inputs for schema {0} in component {1} failed with the error: {2}: Cause: One of the inputs was not valid.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00280: The -examine flag is not allowed with the -readiness flag: Cause: You cannot specify -examine command line option with the -readiness option.; Action: You cannot specify the -examine flag when running the upgrade tool in readiness check mode. If you want to perform an examine without an actual upgrade you must remove the -response option from the command line.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00281: Upgrade is being skipped because the -readiness flag is set: Cause: Actual upgrades are not done when the -readiness command line option is set.; Action: If you want to perform an actual upgrade remove the -readiness flag from the command line. If you intended to perform just the readiness phase, no action is necessary.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00282: Upgrade readiness check completed with one or more errors.: Cause: Examine the readiness check report file and the log file to understand which checks failed.; Action: Correct the problem using information provided in the log file; then retry the operation.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00283: The readiness check phase for plug-in {0} will not be run due to a previous error.: Cause: An error occurred when loading or initializing the plug-in which prevents the readiness check phase from running.; Action: Review the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00284: The isUpgradeRequired method for plug-in {0} will not be called due to a previous error.: Cause: An error occurred when loading or initializing the plug-in which prevents the isUpgradeRequired method from executing.; Action: Review the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00286: A response file referenced one or more schema user names that did not have a matching datasource in the specified domain.: Cause: The auto-datasource option found one or more schema user names that did not have a matching datasource.; Action: Review the domain's datasources and response file specified during upgrade to identify the mismatch.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00287: The getPluginInstantiationCount method for plug-in {0} will not be called due to a previous error.: Cause: An error occurred when loading or initializing the plug-in which prevents the getPluginInstantiationCount method from executing.; Action: Review the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00288: Duplicate schema version registry entries matched the auto-datasource query.: Cause: The auto-datasource option found more than one schema version registry entry that matched the component-id and data source user name.; Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00289: Plugin {0} disabled, isUpgradeRequired returned exception.: Cause: The plugin threw an exception while processing the request to determine if it has schemas within the domain to upgrade.; Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00290: Plugin {0} disabled, the auto-datasource request returned an error.: Cause: The auto-datasource option failed while processing the request for this plugin.; Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00291: The schema newversion attribute is missing for component {0}: Cause: The upgrade framework has detected that the required schema newversion= attribute was missing in an upgrade descriptor file.; Action: Correct the upgrade descriptor file. Starting in release 12.1.3 the <schema> tags must include a newversion= attribute that shows what the schema version number will become after sucecssful upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00292: Null value found in UAWLSINTERNAL field "{0}" of the response file.: Cause: A value necessary for identifying the WLS domain is missing.; Action: Correct the response file and rerun the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00294: Unable to establish a connection to a WLS server.: Cause: Attempt was made to connect to a WLS server during an offline upgrade.; Action: Correct the response file and rerun the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00295: The selected domain has a version of {0} which must be less than the current version {1}.: Cause: Running readiness checks requires the domain to be at a version prior to the current version. This prerequisite has not been met.; Action: Choose a different domain that is for a previous version of Oracle Fusion Middleware.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00296: The Upgrade Descriptor in file {0} specifies an illegal combination of attributes "{1}" and "{2}".: Cause: A tag in an Upgrade Descriptor, which provides information to the Upgrade Assistant about individual upgrade plugins, contains two attributes whose values are incompatible with each other.; Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00297: no text found for offset {0}, read amount {1}, document length {2}: Cause: Unknown; possibly the result of previous errors.; Action: Refresh the file viewer window if possible.
Level: 1

Type: WARNING

Impact: Upgrade

UPGAST-00298: find position {0}, offset, {1}, search string {2}: Cause: Unknown; possibly the result of previous errors.; Action: Refresh the file viewer window if possible.
Level: 1

Type: WARNING

Impact: Upgrade

UPGAST-00300: The preselected check box for {0} has been deselected by the user: Cause: The user has manually unchecked an upgrade item that was preselected by Upgrade Assistant.; Action: Make sure that Oracle's recommendation to always upgrade this item really does not apply to your situation. If you are unsure then this box should be checked in most cases
Level: 1

Type: WARNING

Impact: Upgrade

UPGAST-00301: getTableRowCount method is not implemented by plug-in {0} for input named {1}.: Cause: Required getTableRowCount method was not implemented by plug-in or the signature of the getTableRowCount method is incorrect.; Action: Implement the required getTableRowCount method with the correct signature.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00302: An exception occurred while constructing the backing model for table input {0}.: Cause: A call to the plugin method "getTableRowCount" or "getInitialValue" failed.; Action: See the log file for exception details.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00303: Schema upgrade disabled for plugin {0} because feature set {1} is not installed.: Cause: A plugin declared a dependency on a feature set, and the needed feature set is not installed. Schema upgrade of the component is disallowed.; Action: No action is necessary.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00304: The updateOptionalInputPage method cannot be called for the non-optional input {0}.: Cause: An error occurred calling the updateOptionalInputPage method.; Action: Change the specified input to be optional.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00305: The updateOptionalCustomInput method cannot be called for the non-optional input {0}.: Cause: An error occurred calling the updateOptionalCustomInput method.; Action: Change the specified input to be optional.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00306: The updateOptionalInputPage method can only be called for top level inputs. Input {0} is a custom input or option input.: Cause: An error occurred calling the updateOptionalInputPage method.; Action: Change the specified input to be a top level input.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00307: The updateOptionalCustomInput method cannot be called for the non-custom input {0}.: Cause: An error occurred calling the updateOptionalCustomInput method.; Action: Change the specified input to be a custom input.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00308: An exception occurred while resizing the backing model for table input {0}.: Cause: A call to the plugin method "getTableRowCount" failed.; Action: See the log file for exception details.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00309: An invalid database URL was specified for schema {0}: {1}: Cause: An incorrectly formed database URL was identified.; Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00310: An invalid database URL was specified for datasource {0} with schema {1}: {2}: Cause: An incorrectly formed database URL was identified for the specified datasource.; Action: Fix the datasource definition in your domain configuration using the WebLogic Server Administration Console.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00311: configUpgrade is not allowed in combination with schemaUpgrade.: Cause: You cannot use both schemaUpgrade and configUpgrade in the same command.; Action: Use only schemaUpgrade if you intend to upgrade your FMW schemas; use only configUpgrade if you intend to upgrade your FMW configurations.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00312: readiness is not allowed with configUpgrade or schemaUpgrade.: Cause: You cannot use readiness with either configUpgrade or schemaUpgrade.; Action: When performing readiness do not specify either the -configUpgrade option or the -schemaUpgrade option. When performing an upgrade do not specify the -readiness option.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00313: The response file contains components that do not match the specified upgrade type.: Cause: The response file does not contain inputs that match the type of upgrade specified.; Action: Regenerate the response file if necessary and rerun the upgrade. Specify a response file with schema inputs when performing a schema upgrade.Specify a response file with configuration inputs when performing a configuration upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00314: The XML parser reported a problem.: Cause: Something unexpected occurred while parsing an XML file.; Action: No action is necessary unless XML processing was aborted and the Upgrade Assistant was unable to continue. In which case the XML file in question should be identified and corrected. See the log file for exception details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00315: The Repository Creation Utility (RCU) API returned an unexpected result.: Cause: The RCU API completed with an unexpected result.; Action: See the log file for details. Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00320: Exception raised while running a concurrent upgrade task. {0}: Cause: An exception was raised while running a upgrade task in a concurrent thread. Check the stack trace for detailed information.; Action: Attempt to correct the environment problem if any, then retry the upgrade. Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00321: The -threads option was passed an illegal value for number of threads: {0}. Must be an integer from {1} to {2}.: Cause: The -threads option was passed a value that is outside the permitted range of threads.; Action: Run the command again, specifying a valid number of threads, this value determines the number of schema upgrade plugins that can be run at the same time. See the command line help for details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00323: Was unable to terminate the thread executor pool: Cause: The thread pool that is used to schedule multiple plugins concurrently, could not be terminated after being shut down. The cause of this is unknown.; Action: There is a very long timeout in order to give the thread pool ample time to terminate but the timeout period was still exceeded. There should not be any adverse affect due to this error
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00324: Was unable to terminate the thread executor pool, timeout reached while performing {0}.: Cause: The thread pool that is used to schedule multiple plugins concurrently, could not be terminated after being shut down. The timeout period was reached; Action: There is a very long timeout in order to give the thread pool ample time to terminate but the timeout period was still exceeded. There should not be any adverse affect due to this error.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00325: database query for server identify failed: {0}: Cause: A database query to compare database server identity failed; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00328: The schema version registry table does not exist on this database.: Cause: The schema version registry table does not exist, because the required 12c schemas, such as the new Service Table schema, have not been created by RCU. The registry table must exist in order to run Upgrade Assistant.; Action: Create the required 12c schema using RCU before running the Upgrade Assistant. Refer to the upgrade planning guide for the list of required schemas for this release.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00330: Unable to query schema version registry for schema: {0}: Cause: An attempt to perform schema version registry queries failed.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00352: The -readiness option is not allowed in a standalone environment.: Cause: You cannot specify the -readiness option in a standalone installation.; Action: No action is necessary.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00353: Upgrade readiness check was unable to locate a standard query method for {0}: Cause: Readiness check was unable to locate the code for a standard query.; Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00355: The selected domain has a version of {0} which appears to not be a valid version number.: Cause: Upgrade requires the domain to be at a certain version, which this domain does not meet.; Action: Select a different domain, or run the Reconfiguration tool before trying to upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00356: The specified domain has a version of {0} which is less than the minimum of {1}.: Cause: The domain is at a version less than the minimum version.; Action: Specify a domain that is more recent than the minimum viable version.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00357: Upgrade readiness check returned an empty result set for test {0}, schema tag {1}, database object {2}: Cause: Readiness check encountered an error during execution of a standard query.; Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00358: Upgrade readiness check encountered an unexpected error for test {0}, schema tag {1}, database object {2}: Cause: Readiness check encountered an error during execution of a standard query.; Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00359: Upgrade readiness check encountered a method invocation error for test {0}, schema tag {1}, database object {2}, query {3}: Cause: Readiness check encountered an error during execution of a standard query.; Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00370: getTablespaceName is only supported for Oracle Database not {0}.: Cause: An upgrade plugin used an API that is only supported for the Oracle Database.; Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00371: A database query to return tablespace name failed: {0}: Cause: A database query to identify the tablespace failed; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00372: A database query to detect consolidated schema failed: {0}: Cause: A database query to detect if this schema is consolidated failed; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00373: A readiness check that does not apply to consolidated schemas has been skipped for test {0}, schema tag {1}, database object {2}: Cause: A standard readiness test was called that does not apply to consolidated schemas. The upgrade framework has skipped the test. This is a successful outcome.; Action: No further action is necessary.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGAST-00374: SQL Query failed because it is only applicable to a consolidated schema: {0}: Cause: A database query that obtains information specific to consolidated schemas was called for a non-consolidated schema.; Action: No further action is necessary.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGAST-05001: Error connecting to {0} as user {1}.: Cause: A error occurred attempting to connect to the specified database.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-05002: Error creating Java DB schema {0}.: Cause: A error occurred attempting to create the specified Java DB schema.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-05003: Error getting the Java DB Schema Version Registry table.: Cause: A error occurred locating the Schema Version Registry table for a Java DB.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-05004: Error registering the JDBC drver class {0}.: Cause: A error occurred registering the specified JDBC driver.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-05005: Unsupported database {0} identified.: Cause: A database that is not supported was specified.; Action: Specify a supported database.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-05006: Error moving the Schema Version Registry table.: Cause: A error occurred while moving the Schema Version Registry table from SYSTEM to FMWREGISTRY.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-05007: Error dropping the view SYSTEM.SCHEMA_VERSION_REGISTRY.: Cause: A error occurred while dropping the database view SYSTEM.SCHEMA_VERSION_REGISTRY.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-05008: Error copying the contents of schema version registry table.: Cause: A error occurred while copying the contents of table SYSTEM.SCHEMA_VERSION_REGISTRY$ to table FMWREGISTRY.SCHEMA_VERSION_REGISTRY$.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-05009: Error adding triggers to the schema version registry table.: Cause: A error occurred while adding triggers to the table SYSTEM.SCHEMA_VERSION_REGISTRY$.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-05010: Error getting the metadata for the database connection.: Cause: A error occurred while requesting the metadata for a database connection.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-05011: Error testing if the database environment allows creation of system objects.: Cause: A error occurred while testing if the database connection allows the creation of system objects.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-05012: Error testing if the database table exists.: Cause: A error occurred while testing if the table {0} exists.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-05013: Error creating a SYSTEM instance of the schema version registry table.: Cause: A error occurred while creating a schema version registry table in SYSTEM for compatibility with pre-FMWREGISTRY code.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-05014: Error creating the database view SYSTEM.SCHEMA_VERSION_REGISTRY.: Cause: A error occurred while creating a database view for for the schema version registry table.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-05015: Error granting access for SYSTEM instance of the schema version registry.: Cause: A error occurred while creating access rights for the SYSTEM instance of the schema version registry to access the FMWREGISTRY instance.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-05016: Unrecognized database type of {0} was specified.: Cause: A database type that is not recognized was specified.; Action: Specify a supported database type.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-05017: Error creating the public synonym SCHEMA_VERSION_REGISTRY.: Cause: An error occurred while creating the database synonym SCHEMA_VERSION_REGISTRY.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-05018: Error dropping the public synonym SCHEMA_VERSION_REGISTRY.: Cause: An error occurred while dropping the database synonym SCHEMA_VERSION_REGISTRY.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-05019: Error dropping the trigger SYSTEM.{0}.: Cause: An error occurred while dropping the database trigger specified.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-05020: Error dropping the view {0}.SCHEMA_VERSION_REGISTRY.: Cause: An error occurred while dropping the database view specified.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-05021: Error dropping the table {0}.SCHEMA_VERSION_REGISTRY$.: Cause: An error occurred while dropping the database table specified.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-05022: Error dropping the user {0}.: Cause: An error occurred while dropping the database user specified.; Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade