How To Remove or De-activate OLAP After Migrating From 9i To 10g or 11g
(Doc ID 467643.1)
Last updated on FEBRUARY 02, 2022
Applies to:
Oracle OLAP - Version 9.2.0.5 to 11.2.0.2 [Release 9.2 to 11.2]Information in this document applies to any platform.
Symptoms
NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the Oracle sample or bulit-in schema(s), Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.
- This note applies to both Oracle Database 10g as well as Oracle Database 11g. It describes a scenario that results from migrating from Oracle Database 9i to a higher-numbered version. Whenever it mentions "Oracle 10g" interpret it to say "Oracle 10g or 11g". This is not repeated throughout the note for clarity.
- After migrating an Oracle 9i Database to a Oracle 10g Standard Edition Database, the OLAP option of the migrated 10g environment is no longer operational and needs to be deactivated.
- Any scenario where all of the items below apply:
- an Oracle RDBMS 9i instance had been upgraded to a 10g instance
- the OLAP option was not upgraded properly (still showing 9.x version in the DBA registry)
- OLAP is no longer required in the 10g environment
- OLAP removal scripts are not available in the 10g environment
Changes
An Oracle Database version 9i (including OLAP) has been migrated to Oracle Database 10g.
After the migration, many objects are flagged as INVALID in the 10g environment, many of these objects belong to the OLAPSYS schema / owner.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |