11.2 compatible parameter setting
From: Daniel Fink <daniel.fink_at_optimaldba.com>
Date: Mon, 27 Dec 2010 14:21:02 +0000
Message-ID: <20101227142102.99459.qmail_at_optimaldba.com>
A client recently upgraded one of their databases from 10gR2 to 11gR2, but have left the compatible parameter to 10.2.0 in case they needed to downgrade. They will be bouncing the system in January and are looking to change the parameter to 11.2.<something>. The question they have (and I have) is what should that <something> be?
Date: Mon, 27 Dec 2010 14:21:02 +0000
Message-ID: <20101227142102.99459.qmail_at_optimaldba.com>
A client recently upgraded one of their databases from 10gR2 to 11gR2, but have left the compatible parameter to 10.2.0 in case they needed to downgrade. They will be bouncing the system in January and are looking to change the parameter to 11.2.<something>. The question they have (and I have) is what should that <something> be?
What is the appropriate setting for the COMPATIBLE parameter? Just the major release (11.2.0) or the patch set (11.2.0.1)? Are there any implications of setting it to a patch set instead of release? or vice versa? If they set it to 11.2.0 (current install is 11.2.0.1) and update to 11.2.0.2, would they have any issues backing out the patch if necessary?
-- http://www.freelists.org/webpage/oracle-lReceived on Mon Dec 27 2010 - 08:21:02 CST