Upgrade a Database Manually
SQL> @utlrp.sql
Verify that all expected packages and classes are valid:
SQL> SELECT count(*) FROM dba_invalid_objects;
SQL> SELECT distinct object_name FROM dba_invalid_objects;
16. Exit SQL*Plus.
Your database is now upgraded to the new Oracle Database 11g release. Complete the procedures described in Chapter 4, "After Upgrading to the New Release".
string
ORA-01651: unable to extend save undo segment by string for tablespace string ORA-01652: unable to extend temp segment by string in tablespace string ORA-01653: unable to extend table string.string by string in tablespace string ORA-01654: unable to extend index string.string by string in tablespace string ORA-01655: unable to extend cluster string.string by string in tablespace string
To avoid these errors, set AUTOEXTEND ON MAXSIZE UNLIMITED for the SYSTEM and SYSAUX tablespaces.
■ Shared memory
You might require larger shared memory pool sizes in some cases. The error message indicates which shared memory initialization parameter must be increased.
ORA-04031: unable to allocate string bytes of shared memory ("string","string","string","string")
■ Rollback segments/undo tablespace
If you are using rollback segments, then you must have a single large (100 MB) PUBLIC rollback segment online while the upgrade scripts are being run. Smaller public rollback segments should be taken offline during the upgrade. Typically you get the following error if your rollback segment size is insufficient:
ORA-01562: failed to extend rollback segment number string
If you are using an undo tablespace, then be sure it is at least 400 MB.
■ Fast Recovery Area
If you are using a Fast Recovery Area and it fills up during the upgrade, you will see the following error in the alert log, followed by some suggestions for
recovering from the problem:
ORA-19815: WARNING: db_recovery_file_dest_size of string bytes is 98.99%
used, and has string remaining bytes available.
Identify the root cause of the problem and take appropriate actions to proceed with the upgrade. To avoid issues during the upgrade, increase the amount of space available in your Fast Recovery Area prior to starting the upgrade.
Manual Workaround for ORA-01408
The ORA-01408 error on the index is a known problem with Oracle Application databases, because the same index exists with a different name in these databases.
SQL> create index system.repcat$_audit_column_f2_idx on
2 system.repcat$_audit_column(base_sname,base_oname,base_conflict_type_id, 3 base_reference_name)
4 /
system.repcat$_audit_column(base_sname,base_oname,base_conflict_type_id, *
ERROR at line 2:
ORA-01408: such column list already indexed
See Also: Oracle Database Reference for information about shared memory initialization parameters.
Upgrade a Database Manually
The workaround is to drop the REPCAT$_AUDIT_COLUMN_IDX1 index and rerun the upgrade as described in "Rerunning the Upgrade" on page 3-45.
Running the DBMS_DST Package After Upgrade Can Result in ORA-01822 Running the DBMS_DST package after upgrading to Oracle Database 11g Release 2 (11.2) can result in the ORA-01882: timezone region not found error.
This error is returned if the user sets the time zone file version incorrectly, which results in the region IDs of several time zone regions being stored incorrectly in the database. For example:
ERROR at line 1:
@ ORA-01882: timezone region not found
@ ORA-06512: at "SYS.DBMS_DST", line 113
@ ORA-06512: at "SYS.DBMS_DST", line 1101
@ ORA-06512: at line 1
To fix this problem, update the time zone version as described in "TIMESTAMP WITH TIME ZONE Data Type" on page 14 and rerun the upgrade as described in "Rerunning the Upgrade" on page 3-45.
Component Status
The Post-Upgrade Status Tool should report VALID status for all components at the end of the upgrade. The following list shows and briefly describes other status values that you might see:
■ NO SCRIPT
The component upgrade script was not found in ORACLE_HOME. Check the install logs, install the component software, and then rerun catupgrd.sql.
■ OPTION OFF
The server option required for the component was not installed or was not linked with the server. Check the V$OPTION view as well as the install logs. Install the component or relink the server with the required option, and then rerun catupgrd.sql.
■ REMOVED
The component was not upgraded because it was removed from the database.
■ INVALID
Some objects for the component were invalid at the completion of the upgrade. If there were no errors during the component upgrade, then running utlrp.sql might change the status to VALID without rerunning the entire upgrade. Check the DBA_REGISTRY view after running utlrp.sql.
■ UPGRADING
The component upgrade did not complete. Resolve the problem and rerun catupgrd.sql.
Rerunning the Upgrade
Follow these steps to rerun the upgrade:
1. Shut down the database:
SQL> SHUTDOWN IMMEDIATE
2. Restart the database in UPGRADE mode:
SQL> STARTUP UPGRADE
3. Set the system to spool results to a log file for later verification of success:
SQL> SPOOL upgrade.log 4. Rerun catupgrd.sql:
SQL> @catupgrd.sql
5. Rerun utlu112s.sql:
SQL> @utlu112s.sql