Rman want really old logsequence for recover

Question

Hello,
Red Hat x86 - 5
Oracle 10.2.0.2
I have restored a database to a new host from tape, not a duplicate, but a controlfile restore, and then restore.
run
ALLOCATE CHANNEL ch0 TYPE 'SBT_TAPE' PARMS 'ENV=(NB_ORA_SERV=xxxxx, NB_ORA_CLIENT=xxx, NB_ORA_POLICY=xxx)';
ALLOCATE CHANNEL ch1 TYPE 'SBT_TAPE' PARMS 'ENV=(NB_ORA_SERV=xxxxx, NB_ORA_CLIENT=xxx, NB_ORA_POLICY=xxx)';
restore database CHECK READONLY;
RELEASE CHANNEL ch0;
RELEASE CHANNEL ch1;
}It works fine, and when i try to start recover with this command, the time stamp is after last backup, but not after last archived redo log is backed up (hence all redo logs is on tape)
run
ALLOCATE CHANNEL ch0 TYPE 'SBT_TAPE' PARMS 'ENV=(NB_ORA_SERV=xxxxx, NB_ORA_CLIENT=xxx, NB_ORA_POLICY=xxx)';
ALLOCATE CHANNEL ch1 TYPE 'SBT_TAPE' PARMS 'ENV=(NB_ORA_SERV=xxxxx, NB_ORA_CLIENT=xxx, NB_ORA_POLICY=xxx)';
set until time "to_date('June 22 2010 23:55:00','Mon DD YYYY HH24:MI:SS')";
RECOVER DATABASE;
RELEASE CHANNEL ch0;
RELEASE CHANNEL ch1;
}This should work fine, however he ask for some really old crappy log:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 06/28/2010 16:12:13
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 41538 lowscn 101774536598 found to restore
RMAN-06025: no backup of log thread 1 seq 41537 lowscn 101774528933 found to restore
RMAN-06025: no backup of log thread 1 seq 41536 lowscn 101774024733 found to restoreThis 415** logs are really old, probably 2-3 years, from some old datafile we dropped before i think (before my time)
I have tried to manually restore the logsequences i need, and it work fine, so netbackup and commands are fine, this one work:
run
ALLOCATE CHANNEL ch0 TYPE 'SBT_TAPE' PARMS 'ENV=(NB_ORA_SERV=xxxxx, NB_ORA_CLIENT=xxx, NB_ORA_POLICY=xxx)';
ALLOCATE CHANNEL ch1 TYPE 'SBT_TAPE' PARMS 'ENV=(NB_ORA_SERV=xxxxx, NB_ORA_CLIENT=xxx, NB_ORA_POLICY=xxx)';
set archivelog destination to '/flasharea2/flash_recovery_area/xxxx/';
restore archivelog from logseq 41871 until logseq 41875;
RELEASE CHANNEL ch0;
RELEASE CHANNEL ch1;
}So how can i know why he wants some old logsequences, and how can i identifiy to what this belong, and what can i do to stop this from happening?
Thanks for any help!

Answer 1

Chinar wrote:
This 415** logs are really old, probably 2-3 years, from some old datafile we dropped before i think (before my time)
How you dropped datafile? did you use offline drop? If yes thus reason is this.Hello, the one who dropped it does not work here anymore, but it seems like it was offline drop!
If find this in controlfile (backuped to trace):
-- Take files offline to match current control file.
ALTER DATABASE DATAFILE '/data2/oracle/xxx/data-file-name' OFFLINE DROP;How can i fix this? :(