This discussion is archived
3 Replies Latest reply: Sep 14, 2012 5:28 AM by Srini Chavali-Oracle RSS

Oracle OLAP API invalid at upgrade to 11.2.0.3

Martin1 Newbie
Currently Being Moderated
Hi,
i upgraded a database on Win64 from 11.2.0.1 to 11.2.0.3 Patch 10.

The 'Pre-Upgrade Information Tool' said 'Oracle OLAP API [upgrade] INVALID' bevore the upgrade. The upgrade procedure didn't then do the upgrade of OLAP. Now several objects of OLAPSYS and the object CTXSYS.DRIOPT are invalid and can not be validated by compilation. What should i do now?

Many thanks in advance.

Regards,
Martin
  • 1. Re: Oracle OLAP API invalid at upgrade to 11.2.0.3
    Srini Chavali-Oracle Oracle ACE Director
    Currently Being Moderated
    Pl post OS details. It is best practice to fix all invalid issue before you perform the upgrade. Can you post the output of the pre-upgrade information tool ? http://docs.oracle.com/cd/E11882_01/server.112/e23633/upgrade.htm#CACHIDJD

    If OLAP is used in this database, you will have to restore the database from backups, fix the OLAP invalid, and perform the upgrade again.

    Oracle Olap API Invalid After Adding or Upgrading OLAP [ID 466363.1]
    How To Diagnose Components With NON VALID Status In DBA_REGISTRY After an Upgrade [ID 753041.1]

    HTH
    Srini
  • 2. Re: Oracle OLAP API invalid at upgrade to 11.2.0.3
    Martin1 Newbie
    Currently Being Moderated
    Hi Srini,

    thanks for your reply.

    Here the output of the 'Pre-Upgrade Information Tool':
    SQL> @ C:\oracle\product\11.2.0\dbhome_2\RDBMS\ADMIN\utlu112i.sql
    Oracle Database 11.2 Pre-Upgrade Information Tool 09-13-2012 13:46:40
    Script Version: 11.2.0.3.0 Build: 001
    .
    **********************************************************************
    Database:
    **********************************************************************
    --> name: LPT01
    --> version: 11.2.0.1.0
    --> compatible: 11.2.0.0.0
    --> blocksize: 8192
    --> platform: Microsoft Windows x86 64-bit
    --> timezone file: V11
    .
    **********************************************************************
    Tablespaces: [make adjustments in the current environment]
    **********************************************************************
    --> SYSTEM tablespace is adequate for the upgrade.
    .... minimum required size: 863 MB
    --> SYSAUX tablespace is adequate for the upgrade.
    .... minimum required size: 694 MB
    --> UNDOTBS1 tablespace is adequate for the upgrade.
    .... minimum required size: 400 MB
    --> TEMP 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]
    **********************************************************************
    -- No obsolete parameters found. No changes are required
    .

    **********************************************************************
    Components: [The following database components will be upgraded or installed]
    **********************************************************************
    --> Oracle Catalog Views [upgrade] VALID
    --> Oracle Packages and Types [upgrade] VALID
    --> JServer JAVA Virtual Machine [upgrade] VALID
    --> Oracle XDK for Java [upgrade] VALID
    --> Oracle Workspace Manager [upgrade] VALID
    --> OLAP Analytic Workspace [upgrade] VALID
    --> OLAP Catalog [upgrade] VALID
    --> EM Repository [upgrade] VALID
    --> Oracle Text [upgrade] VALID
    --> Oracle XML Database [upgrade] VALID
    --> Oracle Java Packages [upgrade] VALID
    --> Oracle interMedia [upgrade] VALID
    --> Spatial [upgrade] VALID
    --> Expression Filter [upgrade] VALID
    --> Rule Manager [upgrade] VALID
    --> Oracle Application Express [upgrade] VALID
    ... APEX will only be upgraded if the version of APEX in
    ... the target Oracle home is higher than the current one.
    --> Oracle OLAP API [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 11.2.0.1.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 PUBLIC has 19 INVALID objects.
    .... USER LPU_LINK has 1 INVALID objects.
    WARNING: --> Database contains schemas with objects dependent on DBMS_LDAP package.
    .... Refer to the 11g Upgrade Guide for instructions to configure Network ACLs.
    .... USER LPADM has dependent objects.
    .... USER APEX_040100 has dependent objects.
    .... USER LPU_APEX has dependent objects.
    .
    **********************************************************************
    Recommendations
    **********************************************************************
    Oracle recommends gathering dictionary statistics prior to
    upgrading the database.
    To gather dictionary statistics execute the following command
    while connected as SYSDBA:

    EXECUTE dbms_stats.gather_dictionary_stats;

    **********************************************************************
    Oracle recommends reviewing any defined events prior to upgrading.

    To view existing non-default events execute the following commands
    while connected AS SYSDBA:
    Events:
    SELECT (translate(value,chr(13)||chr(10),' ')) FROM sys.v$parameter2
    WHERE UPPER(name) ='EVENT' AND isdefault='FALSE'

    Trace Events:
    SELECT (translate(value,chr(13)||chr(10),' ')) from sys.v$parameter2
    WHERE UPPER(name) = '_TRACE_EVENTS' AND isdefault='FALSE'

    Changes will need to be made in the init.ora or spfile.

    **********************************************************************
    SQL> spool off

    We have the Enterprise Edition - therefore we can drop the OLAP objects.


    Additionally here the Output of DBA_REGISTRY:
    COMP_NAME VERSION STATUS
    ---------------------------------- ----------- ----------
    JServer JAVA Virtual Machine 11.2.0.3.0 VALID
    OLAP Analytic Workspace 11.2.0.1.0 OPTION OFF
    OLAP Catalog 11.2.0.1.0 OPTION OFF
    Oracle Application Express 4.1.0.00.32 VALID
    Oracle Database Catalog Views 11.2.0.3.0 VALID
    Oracle Database Java Packages 11.2.0.3.0 VALID
    Oracle Database Packages and Types 11.2.0.3.0 VALID
    Oracle Enterprise Manager 11.2.0.3.0 VALID
    Oracle Expression Filter 11.2.0.3.0 VALID
    Oracle Multimedia 11.2.0.3.0 VALID
    Oracle OLAP API 11.2.0.1.0 OPTION OFF
    Oracle Rules Manager 11.2.0.3.0 VALID
    Oracle Text 11.2.0.3.0 INVALID
    Oracle Workspace Manager 11.2.0.3.0 VALID
    Oracle XDK 11.2.0.3.0 VALID
    Oracle XML Database 11.2.0.3.0 VALID
    OWB 11.2.0.1.0 VALID
    Spatial 11.2.0.1.0 OPTION OFF

    Best Regars,
    Martin
  • 3. Re: Oracle OLAP API invalid at upgrade to 11.2.0.3
    Srini Chavali-Oracle Oracle ACE Director
    Currently Being Moderated
    If you do no use OLAP functionality (which sounds like the case since your source database had this option INVALID), then you can ignore these errors.

    HTH
    Srini

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points