Remove components from Oracle’s kernel with chopt

Remove

I’ve had an interesting discussion today. Somebody removed OLAP with chopt – and got issues afterwards. My guess: chopt will only remove the binary option and is meant to be used before a database got created. But if you use it afterwards you’ll have to make sure to remove the dictionary components as well.

A while back a blogged about chopt already:

Removing Options from the Oracle Database kernel in 12c

And there are some helpful Support Notes out there:

This applies especially to OLAP. When you remove it with chopt make sure you have removed all OLAP components from the database beforehand (AMD, APS, XOQ). Check COMP_ID in DBA_REGISTRY. And extra attention is required for CDBs as removing components afterwards from the dictionary may be not straight forward.

An interesting finding on the side for Oracle Database 12.2:

chopt can now remove the following options from the database kernel:
    olap
    oaa (Advanced Analytics - this is a new chopt option in 12.2)
    partitioning
    rat

–Mike

4 thoughts on “Remove components from Oracle’s kernel with chopt

  1. This applies especially to OLAP. When you remove it with chopt make sure you have removed all OLAP components from the database beforehand (AMD, APS, XOQ). Check COMP_ID in DBA_REGISTRY. And extra attention is required for CDBs as removing components afterwards from the dictionary may be not straight forward.

  2. Nope – chopt removes ONLY options from the kernel (aka binary) but never from the database itselves (aka DBA_REGISTRY).

    Cheers
    Mike

  3. Pingback: Removing Options from the Oracle Database kernel in 12c | Upgrade your Database - NOW!

Leave a Reply

Your email address will not be published. Required fields are marked *