Re: increasing COMPATIBLE parameter

From: Sheehan, Jeremy <JEREMY.SHEEHAN_at_nexteraenergy.com>
Date: Tue, 24 Mar 2015 21:15:58 +0000
Message-ID: <93ed7f95-4aa2-49de-8148-191f04c97877_at_nee.com>



It's been modified in a test instance for a few weeks but I didn't change it. Someone else did and didn't document anything and they don't remember if anything else was done. This is a very vanilla db. No ASM, RAC.

Thanks!

Jeremy

Sent from a phone

From: Don Seiler <don_at_seiler.us>
Sent: Mar 24, 2015 4:55 PM
To: Sheehan, Jeremy
Cc: Oracle-L (oracle-l_at_freelists.org) Subject: Re: increasing COMPATIBLE parameter

This is an EXTERNAL email. Exercise caution. DO NOT open attachments or click links from unknown senders or unexpected email.


I would be sure to test application behavior on a test/staging database prior to doing this. But then again, that's solid advice for making any change in a database.

Sometimes behavior of various components can change with the compatible parameter. I've seen it in ASM diskgroup compatible changes, for what its worth.

Don.

On Tue, Mar 24, 2015 at 3:50 PM, Sheehan, Jeremy <JEREMY.SHEEHAN_at_nexteraenergy.com<mailto:JEREMY.SHEEHAN_at_nexteraenergy.com>> wrote: Hello,

I’m on 11.2.0.3 and am looking to update the COMPATIBLE parameter in a database from 10.2.0.4 to 11.2.0.3. I’ve searched pretty extensively (gone to page 3 of Google results and checked on MOS – 733987.1). Aside from taking a backup before making this change, are there any additional things I should look for or do after the change?

Please let me know! Thanks in advance.

Jeremy

--

Don Seiler
http://www.seiler.us

--

http://www.freelists.org/webpage/oracle-l Received on Tue Mar 24 2015 - 22:15:58 CET

Original text of this message