Problem recover database

From: Tommy Fallsen <tommyf_at_kongsberg.com>
Date: Tue, 7 Sep 2004 13:21:00 +0200
Message-ID: <chk5au$179$1@darkstar.kongsberg.com>

Hi

Got a problem with recovering a database, it errors with this message:

Recovery Manager: Release 9.2.0.5.0 - 64bit Production Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved. RMAN>
connected to target database: BAAN5 (DBID=2267994717) RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10>
using target database controlfile instead of recovery catalog allocated channel: tape1
channel tape1: sid=9 devtype=SBT_TAPE
channel tape1: NMO v4.1.0.0
sent command to channel: tape1
Starting recover at 06-SEP-04
channel tape1: starting incremental datafile backupset restore channel tape1: specifying datafile(s) to restore from backup set destination for restore of datafile 00001:
/export/oracledb/oradata/baan5/system01.dbf
destination for restore of datafile 00011:
/export/oracledb/oradata/baan5/C900IDX_01.dbf
released channel: tape1

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================

RMAN-03002: failure of recover command at 09/06/2004 14:47:48 ORA-19507: failed to retrieve sequential file, handle="backup_BAAN5_313_1_535594513.bck", parms="" ORA-27029: skgfrtrv: sbtrestore returned error ORA-19511: Error received from media manager layer, error text: nwora_open_restore: Could not locate the NWORA save file 'backup_BAAN5_313_1_53
5594513.bck' on server 'notodden'.
RMAN>
Recovery Manager complete.

baans05<173> sqlplus "/ as sysdba"
SQL*Plus: Release 9.2.0.5.0 - Production on Mon Sep 6 14:47:59 2004 Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

Connected to:
Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.5.0 - Production
SQL> select handle,status from v$backup_piece where handle like '%backup_BAAN5_313_1_535594513.bck%';
HANDLE

---

---

S
-
backup_BAAN5_313_1_535594513.bck
A
SQL> Is this error the cause of a bad backup or something else?

BANNER

---

Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production PL/SQL Release 9.2.0.5.0 - Production
CORE 9.2.0.6.0 Production
TNS for Solaris: Version 9.2.0.5.0 - Production NLSRTL Version 9.2.0.5.0 - Production

Second Problem: set until time='2004-09-04:00:00:00'; fails. Tried different variations found in the docs.
Does it matter alot where the set until time clause is in the script?

This is the script. Its restores from another oracle server. Making the test server the same as prod server.

ORACLE_SID=baan5
ORAENV_ASK=NO
. oraenv
ORAENV_ASK=YES
NLS_DATE_FORMAT='YYYY-MM-DD:HH24:MI:SS'
rman <<!
connect target
shutdown immediate
startup nomount
set dbid=2267994717;
run {
allocate channel tape1 type 'sbt_tape';
send
'NSR_ENV=(NSR_SERVER=notodden,NSR_CLIENT=baans04,NSR_GROUP=db_oracle9i_full) ';
set until time='2004-09-04:00:00:00';
restore controlfile from autobackup;
sql 'alter database mount';
restore database;
recover database;
sql 'alter database open resetlogs';
release channel tape1;
}
exit
!

It failes with this message:

executing command: SET until clause
released channel: tape1

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================

RMAN-03002: failure of set command at 09/07/2004 13:06:03 ORA-01507: database not mounted

RMAN> Recovery Manager complete.

Thanks

Tommy Fallsen Received on Tue Sep 07 2004 - 06:21:00 CDT