Re: ORA-00201 during startup

From: Abdellah DANY <abd.dany_at_gmail.com>
Date: Thu, 27 May 2021 11:11:09 +0100
Message-ID: <CAM7tOHMZ1_r4G24fKWuXzaJLJNu0QCwBEzfReGW-K7ygXqPtRg_at_mail.gmail.com>



Hi Mladen,

This is the first thing I tried but in vain. That is why I said it is odd how compatible parameter "propagated" so quickly to datafiles with just a simple startup..

Will do a test to confirm this and keep you updated.

Regards;

Le jeu. 27 mai 2021 à 03:05, Mladen Gogala <gogala.mladen_at_gmail.com> a écrit :

> Hi!
>
> You should try accessing 11.2.0.3 database from 11.2.0.3, reset the
> "compatible" parameter to 11.2.0.3 and all should be well. The only way to
> utilize 11.2.0.4 software would be to upgrade. As far as I am aware of,
> there is "dbua" utility in 11.2.0.4 home.
>
> Regards
> On 5/26/21 5:21 PM, Abdellah DANY wrote:
>
> Hi all,
>
> Recreating control file didn't help as well: ORA-01130: version
> 11.2.0.4.0 of datafile incompatible with version 11.2.0.3.0 ORACLE
> ORA-01110: datafile 1 : '/data/oracle/../datafile/system.dbf'
> This is odd how this propagated to datafiles.
>
> Since this is not a production environment and we haven't much time to try
> all the suggested solutions, we restore the latest available backup.
>
> _at_Mladen, this how this happened, we have two oracle homes (11.2.0.3 &
> 11.2.0.4) with 2 init files for the same instance name (everyone with the
> correct compatible parameter) and the server contains multiple database
> instances. Forgot to set the correct environment variables led to this.
>
> I will try to reproduce the problem in my home lab and try to figure out
> the easiest solution for this issue (upgrade, check file headers...)
>
> Thanks all for your help.
>
> Regards;
>
> Le mer. 26 mai 2021 à 20:20, Sayan Malakshinov <xt.and.r_at_gmail.com> a
> écrit :
>
>> Mladen,
>>
>> >Sayan, my understanding is that the situation is actually vice versa:
>>> database software is 11.2.0.3 and somebody has set compatible parameter to
>>> 11.2.0.4. Re-creating the control file or restoring from backup seem like
>>> the best options in that case.
>>
>>
>> Abdellah already confirmed my suspicions:
>>
>> > _at_Sayan, the database is 11.2.0.3 and was started with 11.2.0.4
>>> binaries with compatible=11.2.0.4 in the init file;
>>
>>
>> Moreover, as I said before, Oracle can't start with "compatible" higher
>> than current software version.
>> Simple test case:
>> Oracle version: 19.9:
>>
>> SQL> alter system set compatible='19.10.0' scope=spfile;
>>
>> System altered.
>>
>> SQL> shu immediate
>> Database closed.
>> Database dismounted.
>> ORACLE instance shut down.
>>
>> SQL> startup;
>>
>> *ORA-00401: the value for parameter compatible is not supported by this
>> release*
>>
>>
>> --
>> Best regards,
>> Sayan Malakshinov
>> Oracle performance tuning engineer
>> Oracle ACE Associate
>> http://orasql.org
>>
> --
> Mladen Gogala
> Database Consultant
> Tel: (347) 321-1217https://dbwhisperer.wordpress.com
>
>

--
http://www.freelists.org/webpage/oracle-l
Received on Thu May 27 2021 - 12:11:09 CEST

Original text of this message