I would set to 11.2.0.0.0 to be safe. The compatible setting is what would activate certain functionality as well. I know there are certain ASM features that are only enabled when the diskgroup compatibility is at or above 11.2.0. I don't know of any reason to be more specific than 11.2.0. Don. On Mon, Dec 27, 2010 at 10:12 AM, Taral Desai <taral.desai@xxxxxxxxx> wrote: > On my windows box i recently(new) install 11.2.0.2 and default compatible > setting are 11.2.0.0.0. Why one extra zero i don't know. > > > On Mon, Dec 27, 2010 at 8:21 AM, Daniel Fink > <daniel.fink@xxxxxxxxxxxxxx>wrote: > >> 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? >> -- >> //www.freelists.org/webpage/oracle-l >> >> >> > > > -- > Thanks & Regards, > Taral Desai > -- Don Seiler http://www.seiler.us