Yes it was… created with the rman duplicate command. You may be on to
something. Should be able to check that… the next time it is duplicated..
I will shutdown abort after duplicating.
The source has two tempfiles, but the duplicated database has one now
because the tablespace was dropped and recreated with one. However, the
trace controlfile for the duplicated database had one tempfile now because
that is how I recreated it. (I created a trace controlfile before
re-creating the temp tablespace).
The followup message, also in alert.log. ORA-01203: wrong incarnation of
this file - wrong creation SCN
If what you say is true, should not the source be in the same state? How
to check? That database shuts down once each month immediate without
issue.
Joel Patterson
Database Administrator
joel.patterson@xxxxxxxxxxx
x72546
904 727-2546
------------------------------
*From:* Niall Litchfield [mailto:niall.litchfield@xxxxxxxxx]
*Sent:* Tuesday, July 03, 2007 4:21 PM
*To:* Patterson, Joel
*Cc:* oracle-l@xxxxxxxxxxxxx
*Subject:* Re: Shutdown Abort
Was that database cloned from somewhere using RMAN? If so it's likely an
old tempfile that didn't really belong to the db.
cheers
Niall
On 7/2/07, *Joel.Patterson@xxxxxxxxxxx* <Joel.Patterson@xxxxxxxxxxx>
wrote:
Update FYI:
I just did a shutdown abort on 10.2.0.1 and got:
ORA-01187: cannot read from file 201 because it failed verification tests
.
Had to drop and re-create the TEMP tablespace… .
Joel Patterson
Database Administrator
joel.patterson@xxxxxxxxxxx
x72546
904 727-2546
--
Niall Litchfield
Oracle DBA
http://www.orawin.info