Re: init.ora parm COMPATIBLE

Please understand what the compatible parameter does: it signifies what *data structures* are permissible, not what new features are allowed. With a compatible parameter set to 8.1... I can still do flashback in 9i -because flashback is a coding thing, and uses boring old rollback segments to make it work.

What I can't do is use Automatic Segment Space Management, because ASSM requires a bitmap to describe extent usage, and a bitmap to describe extent usage is a new data structure not seen before 9i.

So no, it's no surprise you can do "8i" things with an 8.0 compatible parameter if those 8i things are just programmatic magic, and not physically novel structures.

HJR "Marc Blum" <marc_at_marcblum.de> wrote in message news:0oavqu0a0inb7v91rpvanjcc8i63oqd6g7_at_4ax.com...
> On Thu, 17 Oct 2002 14:47:56 GMT, rainer.hirthammer_at_software-objects.com
(Rainer
> Hirthammer) wrote:
>
> >We run RDBMS 8.1.7 and have to force compatibility to version 8.0.5.
> >Is it sufficient to set the parameter 'compatible' at init.ora to
> >8.0.5?
> >
> >Tanks, Rainer
>
> Why do you have to force it?
>
> The only reason I can imagine is: To avoid programmers to use
8.1.x-features
> Recommendation: Develop a 8.0.x-Database!
>
> We had a 8.1.6 running with compatible=8.0.5. Funnily this one worked:
>
> CREATE VIEW v
> AS
> SELECT a
> FROM t
> ORDER BY a
> /
>
> which is only available from 8.1.5 on.
>
>
> Marc Blum
> mailto:marc_at_marcblum.de
> http://www.marcblum.de
Received on Fri Oct 18 2002 - 06:32:56 CDT