cancel
Showing results for 
Search instead for 
Did you mean: 

Oracle 10.2.0.4 to 11.2.0.3 upgrade

Former Member
0 Kudos

Hi All,

I have a BI EHP2 system with Linux / Oracle 10.2.0.4 .

We are into the upgrade process > We are getting some error during the pre_upgrade scripts.

SQL> @pre_upgrade_tasks.sql ================================ === PRE-UPGRADE Tasks: START === ================================ Date Time -


-
2012-03-08 18:33:58 Recompiling invalid objects This reduces the number of invalid objects as much as possible. TIMESTAMP -
COMP_TIMESTAMP UTLRP_BGN 2012-03-08 18:33:58 PL/SQL procedure successfully completed. TIMESTAMP -
COMP_TIMESTAMP UTLRP_END 2012-03-08 18:34:15 PL/SQL procedure successfully completed. DOC> The following query reports the number of objects that have compiled DOC> with errors (objects that compile with errors have status set to 3 in DOC> obj$). If the number is higher than expected, please examine the error DOC> messages reported with each object (using SHOW ERRORS) to see if they DOC> point to system misconfiguration or resource constraints that must be DOC> fixed before attempting to recompile these objects. DOC># OBJECTS WITH ERRORS -
7 DOC> The following query reports the number of errors caught during DOC> recompilation. If this number is non-zero, please query the error DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors DOC> are due to misconfiguration or resource constraints that must be DOC> fixed before objects can compile successfully. DOC># ERRORS DURING RECOMPILATION -
1 PL/SQL procedure successfully completed. Purging Recyclebin This reduces the time needed for upgrading the database. SQL> PURGE DBA_RECYCLEBIN; DBA Recyclebin purged. SQL> SET ECHO OFF Gathering Oracle Dictionary Statistics This reduces the time needed for upgrading the database. SQL> EXECUTE dbms_stats.gather_dictionary_stats; PL/SQL procedure successfully completed. SQL> SET ECHO OFF Running Pre-Upgrade-Information Tool utlu112i.sql This is a mandatory task for manual database upgrades. This tool is also run in pre_upgrade_status.sql. Oracle Database 11.2 Pre-Upgrade Information Tool 03-08-2012 18:37:32 Script Version: 11.2.0.3.0 Build: 001 . Database: --> name: CD1 --> version: 10.2.0.4.0 --> compatible: 10.2.0 --> blocksize: 8192 --> platform: Linux x86 64-bit --> timezone file: V4 . Tablespaces: [make adjustments in the current environment] --> SYSTEM tablespace is adequate for the upgrade. .... minimum required size: 966 MB --> PSAPUNDO tablespace is adequate for the upgrade. .... minimum required size: 400 MB --> SYSAUX tablespace is adequate for the upgrade. .... minimum required size: 377 MB --> PSAPTEMP tablespace is adequate for the upgrade. .... minimum required size: 60 MB . Flashback: OFF Update Parameters: [Update Oracle Database 11.2 init.ora or spfile] Note: Pre-upgrade tool was run on a lower version 64-bit database. --> If Target Oracle is 32-Bit, refer here for Update Parameters: -- No update parameter changes are required. . --> If Target Oracle is 64-Bit, refer here for Update Parameters: -- No update parameter changes are required. . Renamed Parameters: [Update Oracle Database 11.2 init.ora or spfile] -- No renamed parameters found. No changes are required. . Obsolete/Deprecated Parameters: [Update Oracle Database 11.2 init.ora or spfile] --> remote_os_authent 11.1 DEPRECATED --> background_dump_dest 11.1 DEPRECATED replaced by "diagnostic_dest" --> user_dump_dest 11.1 DEPRECATED replaced by "diagnostic_dest" . Components: [The following database components will be upgraded or installed] --> Oracle Catalog Views [upgrade] VALID --> Oracle Packages and Types [upgrade] INVALID . Miscellaneous Warnings WARNING: --> Database is using a timezone file older than version 14. .... After the release migration, it is recommended that DBMS_DST package .... be used to upgrade the 10.2.0.4.0 database timezone version .... to the latest version which comes with the new release. WARNING: --> Database contains INVALID objects prior to upgrade. .... The list of invalid SYS/SYSTEM objects was written to .... registry$sys_inv_objs. .... The list of non-SYS/SYSTEM objects was written to .... registry$nonsys_inv_objs. .... Use utluiobj.sql after the upgrade to identify any new invalid .... objects due to the upgrade. .... USER SYS has 8 INVALID objects. . =================================== === PRE-UPGRADE Tasks: FINISHED === =================================== SQL> spool off

There are 2 errors

1.)Object with errors or invalid objects

2.) recompilation error

1.) Object with errors or invalid objects

These are 7 object

AQ$_KUPC$DATAPUMP_QUETAB_V

KUPC$DATAPUMP_QUETAB

SYSNTuqbWKWtJPc7gQMEKFx9cXA==

SYSNTuqbWKWtLPc7gQMEKFx9cXA==

SYSNTuqbWKWtNPc7gQMEKFx9cXA==

AQ$_KUPC$DATAPUMP_QUETAB_F

AQ$_KUPC$DATAPUMP_QUETAB

2.)recompilation error

We queried the UTL_RECOMP_ERRORS table and found

156977

09-MAR-12 10.08.35.

ORA-01403: no data found

ORA-01403: no data found.

Please suggest how to proceed.

Br

Anthony

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello Anthony,

even maybe not on Windows (I faced this on Unix), proceed with invalid objects as in : Note 1453935 - Invalid DataPump objects after Windows patch collection > 25

this is the leftover of some previous 10g patching. Once objects are recreated, recompilation will go ok.

Regards,

Igor