Re: COMPATIBLE parameter.

When you say "binary indices" do you mean bitmap indexes as the rest of the sentence discusses? If so, your statement is incorrect. Bitmap indexes can be updated, but due to the nature of bitmap indexes an attempt to update or insert into a column that has a bitmap index defined on it will require the BITMAP to be locked, not the row. That's one of the reasons bitmap indexes are recommended for low update columns.

Going back to the original poster's question, the only issue really with changing COMPATIBLE is that if you use some of the new version's functionality, downgrading can be more complex. In this case, it's highly unlikely that you would need to downgrade to something lower than 7.3.2 (and you wouldn't be on a supported release if you did), so I wouldn't be too concerned about that.

HTH. Pete

Neil Cudd wrote:

> can't think of anything concerning the compatible setting, but your post
> reminded me of my attempt to introduce bitmap indices (I assume that's what
> we're talking about) and all went well until I discovered that binary
> indicies *cannot* be updated. So if you were doing any inserts (or updates
> to kejy fields) you will have to drop the index first and re-create after
>
> neil
>
> Ollie Kvalvaag wrote in message <38053c73.0_at_news.t-one.net>...
> >Hej all,
> >
> >I am running a Laboratory Information Management System on an Oracle
> 7.3.4.4
> >on NT 4.0 SP4.
> >
> >The COMPATABILTY parameter in init<sid>.ora is set to 7.3.0.0 , I want to
> >move it up to at least 7.3.2.0 to be able to implement binary indexes.
> >
> >Are there any concerns that I need to be aware of before changing this
> >parameter?
> >
> >Ola Espen Kvalvaag
> >--
> ><>{Ola Kvalvaag
> >
> >--
> ><>{
> >
> >
> >
> >
> >
> >

Received on Thu Oct 14 1999 - 11:00:55 CDT