Remove Invalid OLAP Objects From SYS And OLAPSYS Schemas
Last updated on DECEMBER 11, 2017
Applies to:Oracle OLAP - Version 10.2.0.1 and later
Information in this document applies to any platform.
Checked for relevance on 14-Sep-2011.
The following scenarios may result in invalid objects in OLAPSYS and SYS / PUBLIC:
- Removing the OLAP option from an instance (with or without interruption / errors).
- Migration of an instance (for instance from 32bit to 64bit) with the OLAP option enabled.
- Creating a database instance in Standard Edition using a DBCA template other than 'CUSTOM'.
- Restoring a database, schema, or tablespace that includes OLAPSYS
- Any other operation that affects tablespaces related to the OLAPSYS schema.
- Migrating a database from 32 bit to 64 bit or vice versa
- Removing the OLAP option from an instance
- Creating an instance in Standard Edition using DBCA templates other than 'CUSTOM'
- Restoring a database, schema or tablespace that includes OLAPSYS.
- Any other configuration that introduces OLAP schema objects without OLAP being linked into the Oracle executable
If you are actively using the OLAP option you cannot simply reinstall the OLAP option on the 64 bit system since this would make the data managed by the OLAP option unuseable. Instead, the data needs to be migrated properly according to the information contained in
<Note 386990.1> DB CONVERSION: 32 bit -->64 Bit Broke OLAP OPTION
If you are not using the OLAP option, it is possible to remove the OLAP option manually and (if required) re-install it at a later time.
Refer to <Note 739032.1> How To Find Out If OLAP is Being Used And How To Remove OLAP
for details about the general process
This note explains how to remove the OLAP option and which invalid objects can be discarded.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms