 |
|
| Computers Forum Index » Computer - Databases - Oracle (Server) » Ora-19906 when restoring user managed backup -... |
|
Page 1 of 1 |
|
| Author |
Message |
| gs... |
 Posted: Wed Sep 09, 2009 2:05 am |
|
|
|
Guest
|
I have a test database I often restore from an online user managed
backup (not rman), the procedure is simple:
shut test database down
copy files from last online backup on prod to test db locations, along
with any archived logs since backup
startup mount the test db, rebuild the controlfile renaming database and
new file locations etc.
recover database until cancel using backup controlfile, then apply redo
etc. cancel and open database with resetlogs, create a tempfile and I'm
good to go
Usually goes without a hitch, but for some reason after I hit enter to
have it apply the archived log it is looking for, I am getting:
===================================================================
ORA-00283: recovery session canceled due to errors
ORA-19906: recovery target incarnation changed during recovery
ORA-01112: media recovery not started
===================================================================
Looking up the 19906 error says its an rman incantation setting, but I
am not using rman at all for this, and I'm stumped why this is happening
now.
I even re-ran the online backup and recopied the files over, with no
success.
Any ideas what I'm missing here?
thanks |
|
|
| Back to top |
|
|
|
| GS... |
| Posted: Wed Sep 09, 2009 5:15 am |
|
|
|
Guest
|
| ps. database is 10.2.0.4 on windows 64 bit server. |
|
|
| Back to top |
|
|
|
| Hemant K Chitale... |
| Posted: Thu Sep 10, 2009 7:30 am |
|
|
|
Guest
|
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 |
|
|
| Back to top |
|
|
|
| gs... |
| Posted: Thu Sep 10, 2009 6:04 pm |
|
|
|
Guest
|
Hemant K Chitale wrote:
Quote: 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.. |
|
|
| Back to top |
|
|
|
| Hemant K Chitale... |
| Posted: Fri Sep 11, 2009 2:07 am |
|
|
|
Guest
|
Likely you had, inadvertently, done one recover and resetlogs already
and attempted another recover without re-restoring ? |
|
|
| Back to top |
|
|
|
| GS... |
| Posted: Fri Sep 11, 2009 7:04 pm |
|
|
|
Guest
|
Hemant K Chitale wrote:
Quote: Likely you had, inadvertently, done one recover and resetlogs already
and attempted another recover without re-restoring ?
nope - just to be sure that wasn't the case I re-ran the backup on the
prod database & switched logfiles, deleted all the data files from the
test database etc., basically started from scratch again - same result. |
|
|
| Back to top |
|
|
|
| gs... |
| Posted: Wed Sep 16, 2009 8:56 pm |
|
|
|
Guest
|
gs wrote:
Quote: 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... |
|
|
| Back to top |
|
|
|
| Ravi... |
| Posted: Mon Oct 05, 2009 8:00 pm |
|
|
|
Guest
|
On Sep 16, 12:56 pm, gs <g... at (no spam) gs.com> wrote:
Quote: 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. |
|
|
| Back to top |
|
|
|
| gs... |
| Posted: Wed Oct 14, 2009 5:47 pm |
|
|
|
Guest
|
Ravi wrote:
Quote: On Sep 16, 12:56 pm, gs <g... at (no spam) 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. |
|
|
| Back to top |
|
|
|
|
|
All times are GMT
The time now is Sat Dec 12, 2009 1:57 am
|
|