Re: UPDATE - Ora-19906 when restoring user managed backup - stumped!
From: gs <gs_at_gs.com>
Date: Wed, 14 Oct 2009 13:47:59 GMT
Message-ID: <jEkBm.48054$Db2.8632_at_edtnps83>
Ravi wrote:
>> gs wrote:
>>> Hemant K Chitale wrote:
>>>> Check if you rebuilt the controlfile properly and that the newly
>>>> created controlfile IS in use for the Recovery, not an older
>>>> controlfile.
>>>> Hemant K Chitale
>>>> http://hemantoracledba.blogspot.com
>>> checked all that, all was ok, done this process many times, just this
>>> time I was getting error. Finally was able to apply redo and open
>>> database with resetlogs, but only after I set the database incarnation
>>> to 1 with and RMAN command. Not sure why this was necessary this
>>> particular time though. Opened an SR and uploaded alert logs etc.. from
>>> prod and test db's, will see if they come up with any useful info..
>> Oracles answer was when I try and recreate the controlfile with
>> resetlogs (or open database with resetlogs) a new incarnation is
>> created, and ends up being an orphan incarnation. Read more about it in
>> doc id 577820.1
>>
>> Setting db incarnation to 1 fixed the problem for me, but the note says
>> to recreate the controlfile to get around this error, which I did and
>> that alone did not work. In any case I am up and running now, still
>> puzzled as to why this never happened before though...- Hide quoted text -
>>
>> - Show quoted text -
Date: Wed, 14 Oct 2009 13:47:59 GMT
Message-ID: <jEkBm.48054$Db2.8632_at_edtnps83>
Ravi wrote:
> On Sep 16, 12:56 pm, gs <g..._at_gs.com> wrote:
>> gs wrote:
>>> Hemant K Chitale wrote:
>>>> Check if you rebuilt the controlfile properly and that the newly
>>>> created controlfile IS in use for the Recovery, not an older
>>>> controlfile.
>>>> Hemant K Chitale
>>>> http://hemantoracledba.blogspot.com
>>> checked all that, all was ok, done this process many times, just this
>>> time I was getting error. Finally was able to apply redo and open
>>> database with resetlogs, but only after I set the database incarnation
>>> to 1 with and RMAN command. Not sure why this was necessary this
>>> particular time though. Opened an SR and uploaded alert logs etc.. from
>>> prod and test db's, will see if they come up with any useful info..
>> Oracles answer was when I try and recreate the controlfile with
>> resetlogs (or open database with resetlogs) a new incarnation is
>> created, and ends up being an orphan incarnation. Read more about it in
>> doc id 577820.1
>>
>> Setting db incarnation to 1 fixed the problem for me, but the note says
>> to recreate the controlfile to get around this error, which I did and
>> that alone did not work. In any case I am up and running now, still
>> puzzled as to why this never happened before though...- Hide quoted text -
>>
>> - Show quoted text -
> > Did you happen to upgrade this database to 10g recently? Or has this > been at 10g for quite some time? I am just wondering if this is a 10g > behavior.
This was a database created as 10G, then data was imported from 9i, I never use the upgrade process, only exp/imp. Seems to be a 10G behaviour, I have never had this issue with 9i databases. Received on Wed Oct 14 2009 - 08:47:59 CDT