Re: Compatibility Mode / JDBC

The alter database command should have a reset compatibility clause. Compatibility info is stored in any file header, which is why you simply can't change the compatible parameter.

Hth,

Sybrand Bakker, Oracle DBA

"Stefan Merath" <stefan_at_blue-orange.de> wrote in message news:39D9FD1E.CDC55F38_at_blue-orange.de...
> Hi,
>
> I am working with Oracle 8i. I tried to execute the following
> SQL-Command
>
> ALTER TABLE xyz DROP (abc);
>
> The result was the message that it must be running in the
> 8.1.0.0.0-Compatibility Mode or higher. OK, I changed the mode in the
> ini-File to 8.1.0, restarted the Database and executed the command to
> drop the column. So far...
>
> No I need to switch back to the former 8.0.5-compatibility-Mode because
> the JDBC-Driver (classes111.zip) seems to rquire the 8.0.5-Mode. But
> when I try this, it results in the Message, that the redo.log requires
> the Compatibility-Mode 8.1.0 now.
>
> What can I do? Is there JDBC-Driver which is newer? Or is there a
> possibility to clear those log-Files without loosing data?
>
> Thanx
>
> Stefan
>
> --
> let it flow ...
>
> ++++++++++++++++++++++++++++
> + Besuchen Sie uns +
> + auf der SYSTEMS 2000 +
> + in München 6.-10.11.2000 +
> + Halle B3 Stand 103/9 +
> ++++++++++++++++++++++++++++
>
> blue orange Internet GmbH
> Torstr. 109
> 10119 Berlin
> Tel: +49 30 440 10 361
> Funk: 0177 617 09 199
> Fax: +49 30 440 10 365
> Mail: mail_at_blue-orange.de
> Home: http://www.blue-orange.de
Received on Tue Oct 03 2000 - 12:37:03 CDT