6 UPG-00001 to UPG-26001

UPG-00001: An unexpected exception was raised during the upgrade prechecks.

Cause: An unexpected error caused the upgrade to abort.

Action: Based on the details in the message, correct the problem and run the upgrade again.

UPG-00002: The value of the shared_pool_size database parameter was not high enough for the upgrade.

Cause: The value of the shared_pool_size database parameter is too low.

Action: Increase the value of the shared_pool_size database parameter to 20 MB or greater. Run the upgrade again.

UPG-00003: The value of the java_pool_size database parameter was not high enough for the upgrade.

Cause: The value of the java_pool_size database parameter is too low.

Action: Increase the value of the java_pool_size database parameter to 20 MB or greater. Run the upgrade again.

UPG-00004: The optimizer_mode database parameter was incorrectly set to RULE.

Cause: The optimizer_mode database parameter is incorrectly set to RULE.

Action: Change the optimizer_mode database parameter to CHOOSE. Run the upgrade again.

UPG-00005: There was insufficient free space in the default tablespace.

Cause: There is less than 20 MB of free default tablespace.

Action: Create at least 20 MB of free default tablespace. Run the upgrade again.

UPG-00006: There was insufficient free space in the temporary tablespace.

Cause: There is less than 10 MB of free temporary tablespace.

Action: Create at least 10 MB of free temporary tablespace. Run the upgrade again.

UPG-00007: The _system_trig_enabled database parameter was incorrectly set to FALSE.

Cause: The _system_trig_enabled database parameter is incorrectly set to FALSE.

Action: Set the value for the _system_trig_enabled database parameter to TRUE, or do not set it. Run the upgrade again.

UPG-00008: There were jobs running in the DBMS jobs queue during the upgrade.

Cause: The upgrade cannot progress because there are DBMS jobs running.

Action: Either kill the DBMS jobs, or wait for them to finish before restarting the upgrade. Check the "Analyze Product Schema" step in the upgrade log for more information on the running jobs.

UPG-00009: The DBMS job queue was disabled. There were jobs that would have run immediately if it were enabled.

Cause: Jobs submitted for the current repository may not run properly under the upgraded version.

Action: You have two options: 1. Remove the jobs from the queue. 2. Re-enable the job queue by raising the job_queue_processes database parameter to a value greater than 0, and allow the jobs to complete. For a list of all jobs, look under the "Analyze Product Schema" step in the upgrade log.

UPG-00010: Some jobs in the DBMS job queue were incorrectly configured.

Cause: There are OracleAS Portal jobs in the DBMS job queue that were either incorrectly submitted as another user, or submitted as the OracleAS Portal user with another default schema or default privilege.

Action: Remove these jobs from the job queue. The upgrade correctly resubmits any jobs that are missing. For a list of all jobs, look under the "Analyze Product Schema" step in the upgrade log.

UPG-00011: Concurrent sessions were running for the schema you are upgrading.

Cause: Other sessions are running on the OracleAS Portal schema.

Action: Make sure the OracleAS 10g middle-tier is shut down and there are no other connections to the schema being upgraded. Look under "Open Sessions" in the upgrade log for a list of open sessions for the schema.

UPG-00012: Not all components of the JVM installation were present in the database or valid.

Cause: SYS Java objects are not present in the database or are invalid.

Action: Recompile the invalid Java objects in SYS. If this fails, reinstall the JVM in the database following the instructions found in the Oracle database documentation.

UPG-00013: Tables with UPG_ prefix were found in the OracleAS Portal schema.

Cause: The upgrade is aborted when UPG_ prefix tables are present in the OracleAS Portal schema.

Action: Back up all tables with the UPG_prefix, then delete them from the OracleAS Portal schema.

UPG-00014: Obtaining Oracle Text information failed.

Cause: An error occurred during the attempt to retrieve information about the Oracle Text installation.

Action: Ensure that the Oracle Text component is correctly installed. If necessary, reinstall the Oracle Text component. For installation instructions, refer to the Oracle Application Server Portal Configuration Guide, available on Portal Center.

UPG-00015: Oracle Text schema (CTXSYS) does not exist.

Cause: The database does not contain the CTXSYS schema. This indicates that Oracle Text is not installed.

Action: Install the Oracle Text component in the database. For installation instructions, refer to the Oracle Application Server Portal Configuration Guide, available on Portal Center.

UPG-00016: Oracle Text indextype is invalid or does not exist.

Cause: The Oracle Text context indextype is not valid or does not exist. This may indicate a problem with the Oracle Text installation.

Action: Ensure the Oracle Text context indextype is present and valid. If necessary, reinstall the Oracle Text component. For installation instructions, refer to the Oracle Application Server Portal Configuration Guide, available on Portal Center.

UPG-00017: Some Oracle Text packages are invalid.

Cause: Packages in the Oracle Text schema (CTXSYS) that begin with DRI or CTX_ are invalid.

Action: Revalidate the Oracle Text invalid packages. If necessary, reinstall the Oracle Text component. For installation instructions, refer to the Oracle Application Server Portal Configuration Guide, available on Portal Center.

UPG-00018: Oracle Text version does not match the database version.

Cause: The version of the database is more recent than the Oracle Text component. This may indicate that the Oracle Text component upgrade was not successful. Oracle Text manual upgrade steps may have failed or been omitted. On some platforms, this may also indicate that patch 2658339 was not applied.

Action: Depending on the situation, either rerun the Oracle Text upgrade or download and apply the patch.

UPG-00019: Could not find the schema(s) on which Portlet Builder (Web View) applications are based.

Cause: The schema on which the Portlet Builder application is based is missing.

Action: There are two ways to fix this issue: 1. Drop the applications that are using the schema. 2. Re-create the missing schema and all objects in it.

UPG-00020: One or more one-off patches with schema changes have been applied.

Cause: One or more one-off patches that include schema changes have been applied to the OracleAS Portal schema. The upgrade cannot proceed because these changes have not been tested with this release of the upgrade scripts.

Action: See if a version of the upgrade based on the next patchset has been released on Metalink. If so, download and run the new version. If not, wait until it is released.

UPG-00021: The following mandatory object(s) are missing or invalid:

Cause: Mandatory objects that OracleAS Portal relies on are invalid or are not present in the database. If they are missing due to a faulty upgrade of the database, this could also cause failures in the OracleAS Portal upgrade.

Action: Review the database installation and upgrade procedures. If the object is present but invalid, run the rdbms/admin/utlrp.sql script under the database Oracle home to recompile all invalid objects.

UPG-00022: Version %0 of Oracle Portal/WebDB is not supported for upgrade.

Cause: The OracleAS Portal version being upgraded is not supported by this upgrade installation.

Action: If your OracleAS Portal instance is version 9.0.2, 9.0.2.3, or 9.0.2.6, make sure you have followed the instructions for applying Patch 2778342 or 4045812 mentioned in the Oracle Application Server Upgrade and Compatibility Guide. If you are starting with version 3.0.9, follow the instructions on http://portalcenter.oracle.com/upgrades to upgrade to version 9.0.4. If you are running a different version, it is not supported by this upgrade installation. Contact Oracle Support Services.

UPG-00023: Version %0 of Oracle Database is not supported for upgrade.

Cause: The version of the database against which the upgrade was run is not supported for this upgrade.

Action: Upgrade to the minimum database version of Oracle9i Database 9.0.1.5 Enterprise or Standard edition.

UPG-00024: The compatible database parameter is less than 9.0.0.

Cause: The compatible database parameter is set to less than 9.0.0.

Action: Set the value of the compatible database parameter to at least 9.0.0.

UPG-00025: VPD was not installed properly.

Cause: One of the VPD checks has failed.

Action: This error is followed by a detailed message. Resolve the issue by examining the information provided in the message.

UPG-00026: VPD context value is not set.

Cause: The OracleAS Portal login trigger that sets the VPD context is disabled or is not installed.

Action: Verify that the OracleAS Portal login trigger was installed and enabled on the database. If you must install the trigger, run the wwhost/logintrg.sql script from SQL*Plus while logged in as SYS user. You'll find this script under the upgrade directory.

UPG-00027: VPD context value is incorrect.

Cause: The login trigger(s) is not setting the correct context.

Action: Verify that the login trigger is correctly installed. To install the trigger, run the wwhost/logintrg.sql script from SQL*Plus while logged in as SYS user. You'll find this script under the upgrade directory.

UPG-00028: Portal schema user is not set up to use VPD.

Cause: The OracleAS Portal schema user has the EXEMPT ACCESS POLICY system privilege.

Action: Revoke the EXEMPT ACCESS POLICY privilege from the OracleAS Portal schema user by running the following SQL command in SQL*Plus: 'REVOKE EXEMPT ACCESS POLICY FROM PORTAL_SCHEMA_NAME;'. In this command, replace PORTAL_SCHEMA_NAME with the actual OracleAS Portal schema name. Also verify that the OracleAS Portal schema user does not inherit the EXEMPT ACCESS POLICY privilege from any of its assigned roles.

UPG-00029: VPD is not being enforced in the database.

Cause: A problem occurred in the database that caused the VPD check to fail.

Action: Consult the database documentation to find possible actions.

UPG-00031: %0 Unable to bind as the application.

Cause: An error was encountered while connecting to the Oracle Internet Directory server.

Action: The error message above may provide more information about the cause. Make sure that the Oracle Internet Directory server is up and running on host %1 and port %2 and OracleAS Portal has been wired correctly against it.

UPG-01000: Back up the database before running the upgrade.

Cause: You have answered n (no) when asked if the schema has been backed up.

Action: Back up the database, and restart the upgrade.

UPG-01001: Connection to the Portal repository failed.

Cause: Incorrect OracleAS Portal schema, password, or connect string.

Action: Supply the correct OracleAS Portal schema, password, and connect string.

UPG-01002: Connection as SYS to the Portal repository failed.

Cause: An invalid SYS password was supplied, or the orapw file is missing.

Action: Supply the correct SYS password. If the password is correct, verify that you can connect remotely to SYS as SYSDBA using an orapwSID file. Refer to the Oracle database documentation for instructions on creating an orapw file.

UPG-01003: An unexpected exception was raised.

Cause: An unexpected error caused the upgrade to abort.

Action: Based on the details in the message, correct the problem, restore the database from backup, and run the upgrade again.

UPG-01004: Missing strings reported in %0 file.

Cause: The sqlldr utility encountered issues when trying to load message translation data.

Action: Look for specific issues in the .bad file and the corresponding .log file in the upgrade tmp directory. Give these to Oracle Support Services along with the upgrade logs.

UPG-01005: Version not updated, fatal errors found in upgrade log.

Cause: This message indicates that the earlier version of OracleAS Portal will not be updated to the new version. Errors have occurred in the upgrade that will prevent OracleAS Portal from functioning properly. A summary of the errors is listed at the end of the upgrade log.

Action: Search through the errors in the log and apply any fixes mentioned. Then restore the database from backup and run another upgrade. If this fails, or if unexpected errors are encountered, contact Oracle Support Services.

UPG-01007: Unable to create directory %0.

Cause: You do not have the required permissions to create the directory.

Action: Change the permissions on the parent directory.

UPG-01008: Write permission not available for directory %0.

Cause: You do not have the required permissions to write to the directory.

Action: Change the permissions on the directory, or specify a different temporary directory, then rerun the upgrade.

UPG-01009: Unable to create %0. Check permissions on the directory.

Cause: The permissions on the temporary directory do not allow the creation of a login.sql script for the user profile.

Action: Change the permissions on the temporary directory, and run the upgrade again.

UPG-01010: SQL*Plus version %0 not supported for upgrade.

Cause: The version of SQL*Plus you are trying to execute is not supported for this upgrade.

Action: Verify that the version of bin/sqlplus under the Oracle home is at least 9.0.1.

UPG-01011: Restart the upgrade.

Cause: You have answered n (no) when asked if input details are correct.

Action: Correct the input details, and restart the upgrade.

UPG-25000: Removed session cleanup job: %0 from the SYS schema.

Cause: The session cleanup job usually exists in the OracleAS Portal schema. However, an earlier operation, such as the database upgrade, has resulted in removing this job as a part of the upgrade.

Action: If the database instance where the upgrade is being performed does not contain any other OracleAS Portal schema, then no action is required. This is because the session clean-up job gets created in the OracleAS Portal schema during upgrade. However, if there are other OracleAS Portal schemas in the database instance, then verify that they all have their respective session clean-up jobs. Run the script wwc/ctxjget.sql under the upgrade directory from SQL*Plus in an OracleAS Portal schema to check whether the session clean-up job exists. If this job is missing in any OracleAS Portal schema, then you can create it by running the script wwc/ctxjsub.sql in that schema from SQL*Plus.

UPG-25001: VPD check found some issues.

Cause: One of the VPD checks has failed.

Action: This warning is followed by a detailed message. Resolve the issue by examining the information provided in the message.

UPG-25003: Portlet Builder (WebView) components have unknown issues.

Cause: The Portlet Builder components (packages) are invalid.

Action: Try resolving the cause of the errors when compiling the packages that are listed in the log. For example, a report may be based on a table that has been dropped. In this case, the report is no longer valid, so you can drop the report.

UPG-25004: Only %0% of the components in the wwv_modules$ table are production components.

Cause: This informational message indicates that there is a relatively large number of archive versions of Portlet Builder components (formerly WebView). This may be because in Oracle9iAS Portal 3.0.9, a new version of a component was created each time the component was edited and saved.

Action: Delete as many of the archive versions of components as possible. This reduces the size of the tables where attributes for all the archive versions are stored.

UPG-25005: Table without VPD policy: %0.

Cause: The VPD policy on the table indicated in the message was not installed properly in the OracleAS Portal schema.

Action: If the table indicated in the message is not part of the OracleAS Portal product, it is safe to ignore the warning.

UPG-26000: Component %0 has errors. Check that all the objects it is based on are present.

Cause: The component is based on one or more missing objects. For example, a Query By Example report was based on table MY_TABLE. Then MY_TABLE is dropped.

Action: Supply the missing object. If the component is no longer being used, delete it using the OracleAS Portal Navigator.

UPG-26001: Non-Portal objects have errors. See %0 for details.

Cause: Non-OracleAS Portal objects in the OracleAS Portal schema cannot be compiled and have errors.

Action: Find out what is causing the object not to compile, and rectify it.