27 UPGAST-00001 to UPGAST-00267
- 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-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-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 Oracle Support Services.
Level: 1
Type: INCIDENT_ERROR
Impact: Upgrade
- UPGAST-00190: {0} component version is {1}, status is {2}, upgraded flag is {3}
-
Cause: During upgrade a component reported a successful upgrade but the SCHEMA_VERSION_REGISTRY was not updated correctly. This is an internal error.
-
Action: Contact Oracle Support Services.
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 it's upgrade descriptor XML file is in the upgrade/components/ directory of it's Oracle Home.
Level: 1
Type: ERROR
Impact: Upgrade
- UPGAST-00203: Internal Error, validate method is not implemented by plug-in for input named {0}.
-
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 Fusion Middleware home, yet a response file was specified.
-
Cause: Either this Middleware 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 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-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 Oracle Support.
Level: 1
Type: ERROR
Impact: Upgrade
- UPGAST-00213: Unable to connect to database as the dba user "{0}". {1}.
-
Cause: The database connection failed for the specified reason.
-
Action: Correct the problem using information provided in the log file; then retry the operation. In particular if the indicated reason is 'Login has timed out' verify that the host and port are correct and make sure the database is up and is configured for network access.
Level: 1
Type: ERROR
Impact: Upgrade
- UPGAST-00214: Unable to connect to database as the schema user "{0}". {1}.
-
Cause: The database connection failed for the specified reason.
-
Action: Correct the problem using information provided in the log file; then retry the operation. In particular if the indicated reason is 'Login has timed out' verify that the host and port are correct and make sure the database is up and is configured for network access.
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 it's 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 Oracle Support Services
Level: 1
Type: 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-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-00235: Schema version registry table does not exist for component {0}
-
Cause: An attempt to check list the contents of schema version registry table for the component failed because schema version registry does not exist. This is expected only in the case of ODI 11.1.1.3.0 schemas that were created by ODI Studio.
-
Action: If this error occurs when upgrading a non-ODI 11.1.1.3.0 schema there is an error. Contact Oracle Corporation
Level: 1
Type: ERROR
Impact: Upgrade
- UPGAST-00236: There is no schema version registry entry for component {0}
-
Cause: An attempt to check list the contents of schema version registry table for the component failed because no registry entry exists the component. This is expected only in the case of ODI 11.1.1.3.0 schemas that were created by ODI Studio.
-
Action: If this error occurs when upgrading a non-ODI 11.1.1.3.0 schema there is an error. Contact Oracle Corporation
Level: 1
Type: ERROR
Impact: Upgrade
- UPGAST-00237: A duplicate component definition for component {0} has been detected in Oracle Home {1}.
-
Cause: Component names must be unique with a Fusion Middleware Home. Either the component descriptor files are incorrect, or multiple copies of the same component have been installed in the same FMW Home.
-
Action: Remove the duplicate installations, or contact Oracle Support Services.
Level: 1
Type: INCIDENT_ERROR
Impact: Upgrade
- UPGAST-00238: 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-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-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-00249: Internal Error, isOptionalInputRequired method is not implemented by plug-in for input named {0}.
-
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-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-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: Internal Error, getInitialValue method is not implemented by plug-in for input named {0}.
-
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 necessesary 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