Re: Practice of using chopt to disable database options

From: Justin Mungal <justin_at_n0de.ws>
Date: Mon, 11 Nov 2013 07:17:50 -0600
Message-ID: <CAO9=aUxsNYWpH320KHLzsyRE7yU=-9LB9N9Rj6G0v2mYPxS1EA_at_mail.gmail.com>

I've only ever turned features on, such as when customers licensed new features but they weren't enabled at the binary level.

You can also use make, as chopt became available with 11.2 and is simpler. See *How to Check and Enable/Disable Oracle Binary Options (Doc ID 948061.1).*

You can surely turn off features as needed. I'm not sure how common it is but I personally see nothing wrong with doing so.

-Justin

On Mon, Nov 11, 2013 at 7:08 AM, Niels Jespersen <NJN_at_dst.dk> wrote:

> Hello all
>
>
>
> I’m wondering whether it is common practice to use the program chopt
> (resides in $ORACLE_HOME/bin) to disable certain non-licensed database
> options (11g onwards) (on 12c you can even disable partitioning) .
>
>
>
> The advantage being that disabled options cannot be inadvertently used
> (which may hit you license-wise later).
>
>
>
> The disadvantage being (I think) that patches applied will not be applied
> to disabled options, which when later enabled will leave your oracle-home
> partly patched, partly unpatched.
>
>
>
> We try to remember to do it immediately after install.
>
>
>
> What do you do?
>
>
>
> Regards Niels Jespersen
>
>
>
>
>

--
http://www.freelists.org/webpage/oracle-l

Received on Mon Nov 11 2013 - 14:17:50 CET