cancel
Showing results for 
Search instead for 
Did you mean: 

Can you guess ....RMAN?

file system
Frequent Advisor

Can you guess ....RMAN?

Hi experts.
can you tell me why the problem is going on.?

I have backuped up data for a few days.
and I have tested for recover database using RMAN.

here is the problem.
$ rman target /

Recovery Manager: Release 9.2.0.1.0 - 64bit Production

Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.

connected to target database: CHULHA (DBID=1490410073)

RMAN> report schema;

using target database controlfile instead of recovery catalog
RMAN-06139: WARNING: controlfile is not current for REPORT SCHEMA
Report of database schema
File K-bytes Tablespace RB segs Datafile Name
---- ---------- -------------------- ------- -------------------
1 819200 SYSTEM *** /data0/oradata/chulha/system01.dbf
2 2048000 UNDOTBS1 *** /data0/oradata/chulha/undotbs01.dbf
3 25600 USERS *** /data0/oradata/chulha/users_01.dbf
4 10240 TOOLS *** /data0/oradata/chulha/tools01.dbf
5 20480 CWMLITE *** /data0/oradata/chulha/cwmilte01.dbf
6 20480 DRSYS *** /data0/oradata/chulha/drsys.dbf
7 20480 ODM *** /data0/oradata/chulha/odm.dbf
8 20480 RBS *** /data0/oradata/chulha/rbs.dbf
9 20480 INDX *** /data0/oradata/chulha/indx01.dbf
10 143360 EXAMPLE *** /data0/oradata/chulha/example.dbf
11 4096000 TS_MARO_ETC *** /data1/oradata/chulha/ts_maro_etc01.dbf
12 4096000 TS_MARO_ETC *** /data1/oradata/chulha/ts_maro_etc02.dbf
13 4096000 TS_MARO_ETC *** /data1/oradata/chulha/ts_maro_etc03.dbf
14 4096000 TS_MARO_ETC *** /data1/oradata/chulha/ts_maro_etc04.dbf
15 3072000 TS_IDX_MARO_ETC *** /data1/oradata/chulha/ts_idx_maro01.dbf
16 3072000 TS_IDX_MARO_ETC *** /data1/oradata/chulha/ts_idx_maro02.dbf
17 1024000 TS_MARO_MARKET_ANAL *** /data1/oradata/chulha/ts_maro_market_anal01.dbf
18 1024000 TS_IDX_MARO_MARKET_ANAL *** /data1/oradata/chulha/ts_idx_maro_market_anal01.dbf
19 1024000 TS_IDX_SHAREINFO *** /data1/oradata/chulha/ts_idx_shareinfo01.dbf
20 4096000 TS_MARO_PAT *** /data2/oradata/chulha/ts_maro_pat01.dbf
21 4096000 TS_MARO_PAT *** /data2/oradata/chulha/ts_maro_pat02.dbf
22 4096000 TS_IDX_MARO_PAT *** /data2/oradata/chulha/ts_idx_maro_pat01.dbf
23 4096000 TS_IDX_MARO_PAT *** /data2/oradata/chulha/ts_idx_maro_pat02.dbf
24 4096000 TS_MARO_WO_REAL_PRICE *** /data3/oradata/chulha/ts_maro_wo_real_price01.dbf
25 4096000 TS_MARO_WO_REAL_PRICE *** /data2/oradata/chulha/ts_maro_wo_real_price02.dbf
26 4096000 TS_MARO_WO_REAL_PRICE *** /data2/oradata/chulha/ts_maro_wo_real_price03.dbf
27 4096000 TS_MARO_WO_REAL_PRICE *** /data2/oradata/chulha/ts_maro_wo_real_price04.dbf
28 4096000 TS_IDX_WO_REAL_PRICE *** /data4/oradata/chulha/ts_idx_wo_real_price01.dbf
29 4096000 TS_IDX_WO_REAL_PRICE *** /data4/oradata/chulha/ts_idx_wo_real_price02.dbf
30 4096000 TS_IDX_WO_REAL_PRICE *** /data4/oradata/chulha/ts_idx_wo_real_price03.dbf
31 4096000 TS_IDX_WO_REAL_PRICE *** /data4/oradata/chulha/ts_idx_wo_real_price04.dbf
32 4096000 TS_IDX_WO_REAL_PRICE *** /data4/oradata/chulha/ts_idx_wo_real_price05.dbf
33 4096000 TS_IDX_WO_REAL_PRICE *** /data4/oradata/chulha/ts_idx_wo_real_price06.dbf
34 4096000 TS_MARO_WO_DAILY_PRICE *** /data2/oradata/chulha/ts_maro_wo_daily_price01.dbf
35 4096000 TS_MARO_WO_DAILY_PRICE *** /data2/oradata/chulha/ts_maro_wo_daily_price02.dbf
36 4096000 TS_MARO_WO_DAILY_PRICE *** /data3/oradata/chulha/ts_maro_wo_daily_price03.dbf
37 4096000 TS_MARO_WO_DAILY_PRICE *** /data3/oradata/chulha/ts_maro_wo_daily_price04.dbf
38 4096000 TS_MARO_WO_DAILY_PRICE *** /data3/oradata/chulha/ts_maro_wo_daily_price05.dbf
39 4096000 TS_MARO_WO_DAILY_PRICE *** /data3/oradata/chulha/ts_maro_wo_daily_price06.dbf
40 4096000 TS_MARO_WO_DAILY_PRICE *** /data3/oradata/chulha/ts_maro_wo_daily_price07.dbf
41 4096000 TS_IDX_WO_DAILY_PRICE *** /data4/oradata/chulha/ts_idx_wo_daily_price01.dbf
42 4096000 TS_IDX_WO_DAILY_PRICE *** /data4/oradata/chulha/ts_idx_wo_daily_price02.dbf
43 4096000 TS_IDX_WO_DAILY_PRICE *** /data4/oradata/chulha/ts_idx_wo_daily_price03.dbf
44 1024000 TS_CHULHA *** /data1/oradata/chulha/ts_chulha01.dbf
45 4096000 TS_SHAREINFO *** /data1/oradata/chulha/ts_shareinfo01.dbf
46 2048000 TS_CLIMATE *** /data1/oradata/chulha/ts_climate01.dbf
47 2048000 TS_MARO_WO_REAL_PRICE *** /data3/oradata/chulha/ts_maro_wo_real_price05.dbf
48 921600 CATTBS *** /data5/rman/cattbs

RMAN> restore datafile 4;

Starting restore at 07-MAR-07

allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: sid=12 devtype=SBT_TAPE
channel ORA_SBT_TAPE_1: NMO v3.5.0.0
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=13 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=14 devtype=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: sid=15 devtype=DISK
allocated channel: ORA_DISK_4
channel ORA_DISK_4: sid=16 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 03/07/2007 12:32:48
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 4 found to restore

RMAN> list incarnation;


List of Database Incarnations
DB Key Inc Key DB Name DB ID CUR Reset SCN Reset Time
------- ------- -------- ---------------- --- ---------- ----------
1 1 CHULHA 1490410073 NO 1 08-AUG-06
2 2 CHULHA 1490410073 YES 3951162961 06-MAR-07

RMAN> reset database to incarnation 2;

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of reset command at 03/07/2007 12:35:32
RMAN-06002: command not allowed when not connected to a recovery catalog

RMAN> reset database;

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of reset command at 03/07/2007 12:35:39
RMAN-06002: command not allowed when not connected to a recovery catalog


and I run the command to ensuer the incarnation.
RMAN> list incarnation;
List of Database Incarnations
DB Key Inc Key DB Name DB ID CUR Reset SCN Reset Time
------- ------- -------- ---------------- --- ---------- ----------
1 1 CHULHA 1490410073 NO 1 08-AUG-06
2 2 CHULHA 1490410073 YES 3951162961 06-MAR-07

and I crosschecked datafile 4.
RMAN> crosscheck backup of datafile 4;

using channel ORA_SBT_TAPE_1
using channel ORA_DISK_1
using channel ORA_DISK_2
using channel ORA_DISK_3
using channel ORA_DISK_4
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=FULL_CHULHA_1tib4q8m recid=27 stamp=615672086
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=FULL_CHULHA_2jib7hpj recid=41 stamp=615761715
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=FULL_CHULHA_36ibkmo5 recid=57 stamp=616192774
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=3kibsejg_1_1 recid=71 stamp=616446577
Crosschecked 4 objects


RMAN> restore datafile 4;

Starting restore at 07-MAR-07

using channel ORA_SBT_TAPE_1
using channel ORA_DISK_1
using channel ORA_DISK_2
using channel ORA_DISK_3
using channel ORA_DISK_4
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 03/07/2007 13:30:50
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 4 found to restore

why is the problem.
?
5 REPLIES
Steven E. Protter
Exalted Contributor

Re: Can you guess ....RMAN?

Shalom,

It would appear one or both of the following is true:

1) The rman backup seqeuence is incomplete.
2) The path its trying to restore to does not exist or has incorrect permissions.

A good old fashioned down the database get a cold OS backkup avoides these issues.

Hopefully this is not a DR situation and you are merely testing.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Yogeeraj_1
Honored Contributor

Re: Can you guess ....RMAN?

hi,

could it be related to the control files?

if this is on a production instance, it will be preferable that you contact Oracle Support for faster resolution.

kind regards
yogeeraj
No person was ever honoured for what he received. Honour has been the reward for what he gave (clavin coolidge)
Eric Antunes
Honored Contributor

Re: Can you guess ....RMAN?

Hi,

The recomended action for RMAN-06139 is:

"Use a recovery catalog or mount a current controlfile."

So, if you used a recovery catalog database for the backup, this database must be OPEN. If you used this same database you want to recover as recovery catalog, I don't know how to help you...

Best Regards,

Eric
Each and every day is a good day to learn.
TwoProc
Honored Contributor

Re: Can you guess ....RMAN?

You're right SEP - it's exactly why I don't depend solely on RMAN backups - I do both. I've seen too many times that a recovery is started and can't finish. Just go and browse Metalink for issues and bug fixes/incompatibilities with RMAN. I love it when it works right, but it's a dragon when anything goes wrong. Being able to get cold backups and manually roll them forward - though slow - is reassuring.
We are the people our parents warned us about --Jimmy Buffett
Julio Yamawaki
Esteemed Contributor

Re: Can you guess ....RMAN?

Hi,

First, here is not the correct forum for questions like this, the correct place is on metalink.oracle.com.
Second, full backup is good for recovering a backup in a date in the past, for recovering UNTIL the last transaction, you MUST use online backup.
Well, a good test for RMAN:
1. Create a instance in archivelog mode
2. Make about 5 online backups including datafiles and archivelogs
3. Remove all datafiles and archivelogs - retain redologs and controlfiles
4. Restore the database from RMAN (try a complete recovery)

Regards,