RE: Practice of using chopt to disable database options

From: Peter Sharman <pete.sharman_at_oracle.com>
Date: Tue, 12 Nov 2013 17:52:05 -0800 (PST)
Message-ID: <399dfa46-e928-4098-9e05-654fbc0d757f_at_default>

Sorry for being late to the party on this one, I've been travelling with the APAC OTN Tour and haven't had as much time for looking at email.  

Let me raise a caveat here.  

PLEASE do not do this without checking with Support first. There are times where Oracle uses functionality internally that you do not need to be licensed for, and disabling that functionality can cause major problems. As an example, behind the scenes we use partitioning in the Oracle database for the EM repository. If you remove that partitioning functionality EM will not be happy, as a customer I know here in Australia found out when they relinked the kernel without partitioning. If my understanding is correct, a similar thing will happen in Database 12c if you relink without XDB, which EM Express uses.  

Bottom line, just ask first. It won't hurt to ask, and it may save you a lot of work.  

Pete

Pete Sharman
Principal Product Manager
Enterprise Manager Product Suite
33 Benson Crescent CALWELL ACT 2905 AUSTRALIA

Phone: HYPERLINK "tel:+61262924095"+61262924095 | | Fax: HYPERLINK "fax:+61262925183"+61262925183 | | Mobile: +61414443449

---

"Controlling developers is like herding cats."

Kevin Loney, Oracle DBA Handbook  

"Oh no, it's not, it's much harder than that!"

Bruce Pihlamae, long term Oracle DBA

---

 

From: Justin Mungal [mailto:justin_at_n0de.ws] Sent: Tuesday, November 12, 2013 12:18 AM To: NJN_at_dst.dk
Cc: oracle-l_at_freelists.org
Subject: Re: Practice of using chopt to disable database options  

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 <HYPERLINK "mailto:NJN_at_dst.dk"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 Wed Nov 13 2013 - 02:52:05 CET