Practice of using chopt to disable database options
From: Niels Jespersen <NJN_at_dst.dk>
Date: Mon, 11 Nov 2013 13:08:49 +0000
Message-ID: <3967181ED595B445B1E39718204FD4BD13D30CC3_at_SRVEXC5.dst.local>
Hello all
Date: Mon, 11 Nov 2013 13:08:49 +0000
Message-ID: <3967181ED595B445B1E39718204FD4BD13D30CC3_at_SRVEXC5.dst.local>
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-lReceived on Mon Nov 11 2013 - 14:08:49 CET
