RAC instance, trying to recover UNDO datafile, RMAN gives RMAN-06054
Hello all,
This has been a troublesome instance..a quick bit of background. This was created awhile back by someone else, I inherited this 3 mode RAC clusterof instance1.
I'm exporting out of one database (10G) into this instance1 (11G). When I was about to start the import..I found this instance wouldn't start. Turned out no backup had been going on of this empty instance. I backed up the archive logs to tape to free up the FRA..and things fired up.
I began the import, and found a bunch of errors...basically tellling me that I couldn't access one of the undo tablespaces...datafile problems.
I went to look and saw:
SQL> select a.file_name, a.file_id, b.status, a.tablespace_name
2 from dba_data_files a, v$datafile b
3 where a.file_id = b.file#
4 order by a.file_name;
FILE_NAME FILE_ID STATUS TABLESPACE_NAME
+DATADG/instance1/datafile/sysaux.270.696702269 2 ONLINE SYSAUX
+DATADG/instance1/datafile/system.263.696702253 1 SYSTEM SYSTEM
+DATADG/instance1/datafile/undotbs1.257.696702279 3 ONLINE UNDOTBS1
+DATADG/instance1/datafile/undotbs2.266.696702305 4 ONLINE UNDOTBS2
+DATADG/instance1/datafile/undotbs3.269.696702313 5 RECOVER UNDOTBS3
+DATADG/instance1/datafile/users.268.696702321 6 ONLINE USERS
+DATADG/instance1/l_data_01_01 11 ONLINE L_DATA_01
+DATADG/instance1/s_data_01_01 7 ONLINE S_DATA_01
+DATADG/instance1/s_data_01_02 8 ONLINE S_DATA_01
+INDEXDG/instance1/l_index_01_01 12 ONLINE L_INDEX_01
+INDEXDG/instance1/s_index_01_01 9 ONLINE S_INDEX_01
FILE_NAME FILE_ID STATUS TABLESPACE_NAME
+INDEXDG/instance1/s_index_01_02 10 ONLINE S_INDEX_01
There is is, file #5.
So, I went into RMAN to try to restore/recover:
RMAN> restore datafile 5;
Starting restore at 06-APR-10
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: SID=222 instance=instance1 device type=SBT_TAPE
channel ORA_SBT_TAPE_1: NMO v4.5.0.0
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=222 instance=instance1 device type=DISK
creating datafile file number=5 name=+DATADG/instance1/datafile/undotbs3.269.696702313
restore not done; all files read only, offline, or already restored
Finished restore at 06-APR-10
RMAN> recover datafile 5;
Starting recover at 06-APR-10
using channel ORA_SBT_TAPE_1
using channel ORA_DISK_1
starting media recovery
RMAN-06560: WARNING: backup set with key 343546 will be read 2 times
available space of 8315779 kb needed to avoid reading the backup set multiple times
unable to find archived log
archived log thread=1 sequence=1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 04/06/2010 14:33:07
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 1 and starting SCN of 16016
This is all on ASM, and am a bit of a newb with that. I bascially have no data I'm worried about losing, I just need to get everything 'on the air' so I can import successfully, and let users on this instance. I've set up the backups in GRID now....so, it will be backed up on the future, but what is the quickest, most efficient way to get this UNDO tablespace datafile recovered?
Thank you,
cayenne
Hemant K Chitale wrote:
SET UNTIL SEQUENCE 27wouldn't work if the Recovery requires Sequence 1 and it is missing.
Hemant K ChitaleOops...meant to have start and set until both to "1"
However, I see what you mean. It seems I cannot find the file on tape.
Since the RAC instance hasn't yet had any data put into it, I'm thinking it might be best to just blow it away, and recreate everything.
Trouble is, I'm a bit new at RAC and ASM. I was thinking the best route might be to use DBCA to remove the database...? Would this not take care of removing all the datafiles from all the ASM instances on the RAC..as well as all the other directories, etc on all 3x nodes?
I've already used the dbca to create templates of this instance, so recreation shouldn't be too difficult (although it will be my first RAC creation)...
Thank you in advance for the advice so far,
cayenne
Similar Messages
-
Error when trying to recover datafile from standby database to primary
hi friends,
getting problem with restoring datafile from backupset taken on standby database to primary database.
os: windows server 2003
db: oracle 11gR1(11.1.0.6)
i've configured standby database on two different hosts.
host1 - primary (db_uinque_name= prod)
host2 - standby (db_uniue_name= prodsby)
I've configure both database with recovery catalog. I take backup on standby database. users' datafile of primary database has been lost.i'm trying to restore from the backupsets taken on standby database.
with the help of - http://download.oracle.com/docs/cd/B28359_01/server.111/b28294/rman.htm#BAJCEFEG
on primary
c:\>rman target sys/password catalog rcat/password
rman>list backup for db_unique_name prodsby;
display the backupsets
rman>restore datafile 4;
Starting restore at 06-NOV-08
starting full resync of recovery catalog
full resync complete
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=1051 device type=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 11/06/2008 12:12:18
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 4 found to restore
also use to tag to restore the datafile
rman>restore datafile 4 from tag='base0_prodsby';
Starting restore at 06-NOV-08
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 11/06/2008 11:27:21
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 4 found to restore
i'm getting above errors when try to restore the datafile.
when i issue the following command.
BACKUP AS COPY DATAFILE 4 AUXILIARY FORMAT 'C:\app\Administrator\oradata\prod\USERS01.DBF';
Starting backup at 06-NOV-08
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=1068 device type=DISK
channel ORA_DISK_1: starting datafile copy
input datafile file number=00004 name=C:\APP\ADMINISTRATOR\ORADATA\prod\USERS01.
DBF
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 11/06/2008 12:49:
15
ORA-17628: Oracle error 19505 returned by remote Oracle server
please friends, try to help me to solve the problem.
Thanks,
Vihanghi.
Its not necessary its a otherway around to recover datafile from this backupset and apply archivelogs to make datafile consistent.
yes, it ain't the right way to restore backup to primary location.
so how would i connect to standby database with primary and recovery catalog.
i need to connect to recovery catalog and primary site because i need to restore to primary location and recovery catalog contain all metadata and backupsets related information.
i also tried the following steps from oracle documentation.
Connect to the standby database as the target database:
CONNECT TARGET sys@standby
You are prompted for a password:
target database Password: password
Connect to the primary database as the auxiliary database:
CONNECT AUXILIARY sys@primary
You are prompted for a password:
target database Password: password
Back up the datafile on the standby host across the network to a location on the primary host. For example, suppose that /disk1/df2.dbf is the name of datafile 2 on the standby host. Suppose that /disk8/datafile2.dbf is the name of datafile 2 on the primary host. The following command would copy datafile 2 over the network to /disk9/df2copy.dbf:
BACKUP AS COPY DATAFILE 2 AUXILIARY FORMAT '/disk9/df2copy.dbf';
Starting backup at 06-NOV-08
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=1068 device type=DISK
channel ORA_DISK_1: starting datafile copy
input datafile file number=00004 name=C:\APP\ADMINISTRATOR\ORADATA\prod\USERS01.
DBF
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 11/06/2008 12:49:
15
ORA-17628: Oracle error 19505 returned by remote Oracle server
getting this error. -
How to diagnose and recover corrupted datafile?
DBMS: Oracle v.9.2.0.1.0
OS: MS Server 2003 R2 SP2 x86
Problem: Database begin to stop every few minutes. I start to check and found that one and the largest of two datafiles is probably corrupted. Now I have no idea how to repair that datafile.
Firstly, I look into the alert.log and see that^
Mon Jul 29 11:02:03 2013
SMON: enabling tx recovery
Mon Jul 29 11:02:03 2013
Database Characterset is CL8MSWIN1251
replication_dependency_tracking turned off (no async multimaster replication found)
Completed: alter database open
Mon Jul 29 11:02:42 2013
KCF: write/open error block=0x3c009f online=1
file=4 F:\ORACLE\ORADATA\ORCL\USERS_1.ORA
error=27069 txt: 'OSD-04026: Invalid parameter passed. (OS 3932319)'
Mon Jul 29 11:02:42 2013
Errors in file c:\oracle\admin\orcl\bdump\orcl_dbw0_3604.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
ORA-01114: IO error writing block to file 4 (block # 3932319)
ORA-01110: data file 4: 'F:\ORACLE\ORADATA\ORCL\USERS_1.ORA'
ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file
OSD-04026: Invalid parameter passed. (OS 3932319)
DBW0: terminating instance due to error 1242
Instance terminated by DBW0, pid = 3604
Dump file c:\oracle\admin\orcl\bdump\alert_orcl.log
So, I turned archivelog on and open database but it continue to stop when somebody calls to some DB objects.
Then, I check v$headers:
SQL> select file#, status, recover, fuzzy, tablespace_name, to_char(CHECKPOINT_CHANGE#), name from v$datafile_header;
FILE# STATUS REC FUZ TABLESPACE_NAME TO_CHAR(CHECKPOINT_CHANGE#) NAME
1 ONLINE NO YES SYSTEM 9679059694215 F:\ORACLE\ORADATA\ORCL\SYSTEM.ORA
2 ONLINE NO YES UNDO 9679059694215 F:\ORACLE\ORADATA\ORCL\UNDO.ORA
3 ONLINE NO YES USERS 9679059694215 F:\ORACLE\ORADATA\ORCL\USERS.ORA
4 OFFLINE YES YES USERS 9679059697551 F:\ORACLE\ORADATA\ORCL\USERS_1.ORA
For some reason, USERS in USERS_1.ORA is offline and marked as requiring recovery.
I tried to recover datafile, but get some errors:
SQL> recover datafile 'F:\ORACLE\ORADATA\ORCL\USERS_1.ORA';
ORA-00283: recovery session canceled due to errors
ORA-01115: IO error reading block from file 4 (block # 3932319)
ORA-01110: data file 4: 'F:\ORACLE\ORADATA\ORCL\USERS_1.ORA'
ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file
OSD-04026: Invalid parameter passed. (OS 3932319)
That have looking creepy for me.
I tries to verify datafile:
dbv file=F:\oracle\oradata\orcl\users_1.ora blocksize=16384 logfile=F:\oracle\oradata\orcl\dbvlog.txt
The result of verification was unexpectedly clean:
DBVERIFY: Release 9.2.0.1.0 - Production on Tue Jul 30 05:03:26 2013
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
DBVERIFY - Verification starting : FILE = F:\oracle\oradata\orcl\users_1.ora
DBVERIFY - Verification complete
Total Pages Examined : 3932320
Total Pages Processed (Data) : 94051
Total Pages Failing (Data) : 0
Total Pages Processed (Index): 19378
Total Pages Failing (Index): 0
Total Pages Processed (Other): 3753059
Total Pages Processed (Seg) : 0
Total Pages Failing (Seg) : 0
Total Pages Empty : 65832
Total Pages Marked Corrupt : 0
Total Pages Influx : 0
Now I have that offlined tablespace in the probably not corrupted datafile and no idea how to get DB into the normal state.
Upd: I did database validation by RMAN:
RMAN> BACKUP VALIDATE DATABASE;
Starting backup at 30-JUL-13
using target database controlfile instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=11 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current controlfile in backupset
input datafile fno=00004 name=F:\ORACLE\ORADATA\ORCL\USERS_1.ORA
input datafile fno=00002 name=F:\ORACLE\ORADATA\ORCL\UNDO.ORA
input datafile fno=00003 name=F:\ORACLE\ORADATA\ORCL\USERS.ORA
input datafile fno=00001 name=F:\ORACLE\ORADATA\ORCL\SYSTEM.ORA
channel ORA_DISK_1: backup set complete, elapsed time: 00:33:06
Finished backup at 30-JUL-13
That would been check my DB and put information of corrupted blocks to a V$DATABASE_BLOCK_CORRUPTION, but no! There's nothing:
SQL> select * from V$DATABASE_BLOCK_CORRUPTION;
no rows selected
Nevertheless, database doesn't open, until I switch bad datafile to offline^
SQL> alter database datafile 'F:\ORACLE\ORADATA\ORCL\USERS_1.ORA' online;
Database altered.
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-01113: file 4 needs media recovery
ORA-01110: data file 4: 'F:\ORACLE\ORADATA\ORCL\USERS_1.ORA'
Message was edited by: Llywelyn.yvDoes it diferents from below?
RMAN> BACKUP VALIDATE DATABASE;
Starting backup at 30-JUL-13
using target database controlfile instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=11 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current controlfile in backupset
input datafile fno=00004 name=F:\ORACLE\ORADATA\ORCL\USERS_1.ORA
input datafile fno=00002 name=F:\ORACLE\ORADATA\ORCL\UNDO.ORA
input datafile fno=00003 name=F:\ORACLE\ORADATA\ORCL\USERS.ORA
input datafile fno=00001 name=F:\ORACLE\ORADATA\ORCL\SYSTEM.ORA
channel ORA_DISK_1: backup set complete, elapsed time: 00:33:06
Finished backup at 30-JUL-13 -
ORA-01180: can not create datafile 1 during RMAN restore.
Hello,
I am trying to refresh one of our QA environments and I am getting this error message:
RMAN> run
2> {
3> allocate channel c1 device type disk;
4> allocate channel c2 device type disk;
5> restore database;
6> recover database;
7> }
allocated channel: c1
channel c1: SID=5 device type=DISK
allocated channel: c2
channel c2: SID=131 device type=DISK
Starting restore at 08-NOV-12
using channel ORA_DISK_1
creating datafile file number=1 name=+DATA1/alephpr/datafile/system.269.722874729
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 11/08/2012 16:27:40
ORA-01180: can not create datafile 1
ORA-01110: data file 1: '+DATA1/alephpr/datafile/system.269.722874729' I created a new database from scratch with the same name as is in Production, later on I will proceed to rename it to the right one. I started the steps for refreshing the PRD copy:
RMAN> shutdown immediate
using target database control file instead of recovery catalog
database dismounted
Oracle instance shut down
RMAN> startup nomount
connected to target database (not started)
Oracle instance started
Total System Global Area 534462464 bytes
Fixed Size 2228200 bytes
Variable Size 176160792 bytes
Database Buffers 348127232 bytes
Redo Buffers 7946240 bytes
RMAN> set dbid=3573460394
executing command: SET DBID
RMAN> restore controlfile from '/restorealeph/c-3573460394-20121106-01';
Starting restore at 08-NOV-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=130 device type=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:07
+output file name=+DATA1/alephpr/controlfile/current.260.798747585+
+output file name=+FLASH/alephpr/controlfile/current.276.798747585+
Finished restore at 08-NOV-12
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1Once the control file is restored, I need to crosscheck, delete expired and catalog the backups at the new server:
RMAN> crosscheck backup;
Crosschecked 48 objects
RMAN> delete noprompt expired backup;
Deleted 48 EXPIRED objects
RMAN> list backup summary;
specification does not match any backup in the repositoryI need now to catalog the backups we transferred from Prod into the QA server's directory /restorealeph:
RMAN> catalog start with '/restorealeph/';
searching for all files that match the pattern /restorealeph/
List of Files Unknown to the Database
=====================================
File Name: /restorealeph/9cnpm51u_1_1
File Name: /restorealeph/9enpm6lj_1_1
File Name: /restorealeph/c-3573460394-20121107-00
File Name: /restorealeph/c-3573460394-20121107-01
File Name: /restorealeph/c-3573460394-20121106-01
Do you really want to catalog the above files (enter YES or NO)? YES
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /restorealeph/9cnpm51u_1_1
File Name: /restorealeph/9enpm6lj_1_1
File Name: /restorealeph/c-3573460394-20121107-00
File Name: /restorealeph/c-3573460394-20121107-01
File Name: /restorealeph/c-3573460394-20121106-01
RMAN> list backup summary;
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
4097 B F A DISK 07-NOV-12 1 1 NO BACKUP_ALEPHPR.TUR_110712030000
4098 B A A DISK 07-NOV-12 1 1 NO BACKUP_ALEPHPR.TUR_110712030000
RMAN> list backup tag="BACKUP_ALEPHPR.TUR_110712030000";
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
4097 Full 178.04G DISK 00:00:00 07-NOV-12
BP Key: 4097 Status: AVAILABLE Compressed: NO Tag: BACKUP_ALEPHPR.TUR_110712030000
Piece Name: /restorealeph/9cnpm51u_1_1
List of Datafiles in backup set 4097
File LV Type Ckp SCN Ckp Time Name
1 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/system.269.722874729
2 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/sysaux.266.722874731
3 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/undotbs1.289.722874727
4 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/undotbs2.257.722874727
5 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/users.298.722874731
6 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/audit.299.723372305
7 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/case_datos.260.723372307
8 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/case_indices.261.723372307
9 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/data_hist.262.723372309
10 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/data_l.264.723372319
11 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/data_long.265.723372349
12 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/data_md.270.723372355
13 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/data_sm.271.723372369
14 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/data_xl.272.723372375
15 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/index_l.273.723372401
16 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/index_md.274.723372427
17 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/index_sm.275.723372455
18 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/index_xl.276.723372473
19 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/tools.278.723372501
26 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/data_sm.300.736088959
27 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/dev_disco_ptm5_meta.301.746385117
28 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/dev_disco_pstore.302.746385119
29 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/dev_disco_ptm5_cache.304.746385121
30 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/undotbs1.305.796391931
31 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/undotbs2.306.796392185
BS Key Size Device Type Elapsed Time Completion Time
4098 16.89G DISK 00:00:00 07-NOV-12
BP Key: 4098 Status: AVAILABLE Compressed: NO Tag: BACKUP_ALEPHPR.TUR_110712030000
Piece Name: /restorealeph/9enpm6lj_1_1
List of Archived Logs in backup set 4098
Thrd Seq Low SCN Low Time Next SCN Next Time
1 35722 6919870864350 06-NOV-12 6919871887697 06-NOV-12
1 35723 6919871887697 06-NOV-12 6919872372211 06-NOV-12
1 35724 6919872372211 06-NOV-12 6919872410158 06-NOV-12
1 35725 6919872410158 06-NOV-12 6919872447301 06-NOV-12
1 35726 6919872447301 06-NOV-12 6919872503332 06-NOV-12
1 35727 6919872503332 06-NOV-12 6919872551564 06-NOV-12
1 35728 6919872551564 06-NOV-12 6919872603881 06-NOV-12
1 35729 6919872603881 06-NOV-12 6919872655942 06-NOV-12
1 35730 6919872655942 06-NOV-12 6919872698722 06-NOV-12
1 35731 6919872698722 06-NOV-12 6919872741655 06-NOV-12
1 35732 6919872741655 06-NOV-12 6919872782284 06-NOV-12
1 35733 6919872782284 06-NOV-12 6919872872302 06-NOV-12
1 35734 6919872872302 06-NOV-12 6919872910206 06-NOV-12
1 35735 6919872910206 06-NOV-12 6919872945577 06-NOV-12
1 35736 6919872945577 06-NOV-12 6919872980056 06-NOV-12
1 35737 6919872980056 06-NOV-12 6919873013411 06-NOV-12
1 35738 6919873013411 06-NOV-12 6919873050761 06-NOV-12
1 35739 6919873050761 06-NOV-12 6919873084996 06-NOV-12
1 35740 6919873084996 06-NOV-12 6919873122049 06-NOV-12
1 35741 6919873122049 06-NOV-12 6919873521767 06-NOV-12
1 35742 6919873521767 06-NOV-12 6919873952773 06-NOV-12
1 35743 6919873952773 06-NOV-12 6919874258549 06-NOV-12
1 35744 6919874258549 06-NOV-12 6919874472213 06-NOV-12
1 35745 6919874472213 06-NOV-12 6919874744856 06-NOV-12
1 35746 6919874744856 06-NOV-12 6919875113086 06-NOV-12
1 35747 6919875113086 06-NOV-12 6919875733337 06-NOV-12
1 35748 6919875733337 06-NOV-12 6919876139061 06-NOV-12
1 35749 6919876139061 06-NOV-12 6919876707162 06-NOV-12
1 35750 6919876707162 06-NOV-12 6919877706313 06-NOV-12
1 35751 6919877706313 06-NOV-12 6919877919039 06-NOV-12
1 35752 6919877919039 06-NOV-12 6919878024429 06-NOV-12
1 35753 6919878024429 06-NOV-12 6919878107673 06-NOV-12
1 35754 6919878107673 06-NOV-12 6919878258511 06-NOV-12
1 35755 6919878258511 06-NOV-12 6919878308336 06-NOV-12
1 35756 6919878308336 06-NOV-12 6919878424419 06-NOV-12
1 35757 6919878424419 06-NOV-12 6919878488485 06-NOV-12
1 35758 6919878488485 06-NOV-12 6919878827092 06-NOV-12
1 35759 6919878827092 06-NOV-12 6919879350098 07-NOV-12
1 35760 6919879350098 07-NOV-12 6919879675556 07-NOV-12
2 35949 6919870864360 06-NOV-12 6919871494640 06-NOV-12
2 35950 6919871494640 06-NOV-12 6919871887487 06-NOV-12
2 35951 6919871887487 06-NOV-12 6919872410655 06-NOV-12
2 35952 6919872410655 06-NOV-12 6919872552468 06-NOV-12
2 35953 6919872552468 06-NOV-12 6919872698940 06-NOV-12
2 35954 6919872698940 06-NOV-12 6919872872690 06-NOV-12
2 35955 6919872872690 06-NOV-12 6919872980371 06-NOV-12
2 35956 6919872980371 06-NOV-12 6919873085902 06-NOV-12
2 35957 6919873085902 06-NOV-12 6919873569082 06-NOV-12
2 35958 6919873569082 06-NOV-12 6919873949096 06-NOV-12
2 35959 6919873949096 06-NOV-12 6919874404640 06-NOV-12
2 35960 6919874404640 06-NOV-12 6919875011814 06-NOV-12
2 35961 6919875011814 06-NOV-12 6919875631429 06-NOV-12
2 35962 6919875631429 06-NOV-12 6919876324885 06-NOV-12
2 35963 6919876324885 06-NOV-12 6919876363526 06-NOV-12
2 35964 6919876363526 06-NOV-12 6919876748508 06-NOV-12
2 35965 6919876748508 06-NOV-12 6919877741784 06-NOV-12
2 35966 6919877741784 06-NOV-12 6919878108943 06-NOV-12
2 35967 6919878108943 06-NOV-12 6919878424477 06-NOV-12
2 35968 6919878424477 06-NOV-12 6919879012111 06-NOV-12
2 35969 6919879012111 06-NOV-12 6919879260589 07-NOV-12
2 35970 6919879260589 07-NOV-12 6919879350086 07-NOV-12
2 35971 6919879350086 07-NOV-12 6919879464935 07-NOV-12
2 35972 6919879464935 07-NOV-12 6919879548399 07-NOV-12
2 35973 6919879548399 07-NOV-12 6919879675564 07-NOV-12
RMAN> list incarnation;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 ALEPHPR 3573460394 PARENT 1 13-MAY-10
2 2 ALEPHPR 3573460394 PARENT 2229467 28-JUN-10
3 3 ALEPHPR 3573460394 CURRENT 6918261828355 26-SEP-12The ASM structure is created...
ASMCMD> lsdg
State Type Rebal Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files Name
MOUNTED EXTERN N 512 4096 1048576 509282 507421 0 507421 0 N DATA1/
MOUNTED EXTERN N 512 4096 1048576 50641 42850 0 42850 0 N FLASH/
ASMCMD> cd DATA1/ALEPHPR/DATAFILE
ASMCMD> pwd
+DATA1/ALEPHPR/DATAFILEBoth source and target databases are 11.2.0.2 PSU 6 running on Linux x64. I cannot use RMAN Duplicate since there is no visibility among different environments (PROD - QA in this case).
Any idea?
Thanks
Martin
Edited by: martin.morono on Nov 8, 2012 11:19 AM
Edited by: martin.morono on Nov 8, 2012 11:49 AMThanks Levi,
I slightly modified your script to recatalog the backup pieces since they are note stored at the same location in PR and QA.
No luck. The error message is different but the result is the same... it keeps failing.
RMAN> run {
2> allocate channel c1 device type disk;
3> allocate channel c2 device type disk;
4> restore controlfile from '/restorealeph/c-3573460394-20121107-01';
5> startup mount;
6> catalog start with '/restorealeph/';
7> restore database from tag 'BACKUP_ALEPHPR.TUR_110712030000';
8> }
allocated channel: c1
channel c1: SID=191 device type=DISK
allocated channel: c2
channel c2: SID=131 device type=DISK
Starting restore at 09 NOV 2012 13:11:09
channel c2: skipped, AUTOBACKUP already found
channel c1: restoring control file
channel c1: restore complete, elapsed time: 00:00:15
output file name=+DATA1/alephpr/controlfile/current.260.798747585
output file name=+FLASH/alephpr/controlfile/current.276.798747585
Finished restore at 09 NOV 2012 13:11:24
database is already started
database mounted
Starting implicit crosscheck backup at 09 NOV 2012 13:11:31
Crosschecked 52 objects
Finished implicit crosscheck backup at 09 NOV 2012 13:11:39
Starting implicit crosscheck copy at 09 NOV 2012 13:11:39
Crosschecked 2 objects
Finished implicit crosscheck copy at 09 NOV 2012 13:11:40
searching for all files in the recovery area
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_2_seq_1.279.795017193
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_2_seq_34950.273.795014469
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_1.281.795017413
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_2.283.795017519
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_3.290.795018411
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_4.291.795018559
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_5.292.795018707
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_6.293.795018811
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_7.294.795018899
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_8.295.795020509
File Name: +flash/ALEPHPR/CONTROLFILE/Current.268.798725123
searching for all files that match the pattern /restorealeph/
List of Files Unknown to the Database
=====================================
File Name: /restorealeph/9cnpm51u_1_1
File Name: /restorealeph/9enpm6lj_1_1
File Name: /restorealeph/c-3573460394-20121107-00
File Name: /restorealeph/c-3573460394-20121107-01
File Name: /restorealeph/c-3573460394-20121106-01
Do you really want to catalog the above files (enter YES or NO)? YEs
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /restorealeph/9cnpm51u_1_1
File Name: /restorealeph/9enpm6lj_1_1
File Name: /restorealeph/c-3573460394-20121107-00
File Name: /restorealeph/c-3573460394-20121107-01
File Name: /restorealeph/c-3573460394-20121106-01
Starting restore at 09 NOV 2012 13:11:48
released channel: c1
released channel: c2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 11/09/2012 13:11:48
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 31 found to restore
RMAN-06023: no backup or copy of datafile 30 found to restore
RMAN-06023: no backup or copy of datafile 29 found to restore
RMAN-06023: no backup or copy of datafile 28 found to restore
RMAN-06023: no backup or copy of datafile 27 found to restore
RMAN-06023: no backup or copy of datafile 26 found to restore
RMAN-06023: no backup or copy of datafile 19 found to restore
RMAN-06023: no backup or copy of datafile 18 found to restore
RMAN-06023: no backup or copy of datafile 17 found to restore
RMAN-06023: no backup or copy of datafile 16 found to restore
RMAN-06023: no backup or copy of datafile 15 found to restore
RMAN-06023: no backup or copy of datafile 14 found to restore
RMAN-06023: no backup or copy of datafile 13 found to restore
RMAN-06023: no backup or copy of datafile 12 found to restore
RMAN-06023: no backup or copy of datafile 11 found to restore
RMAN-06023: no backup or copy of datafile 10 found to restore
RMAN-06023: no backup or copy of datafile 9 found to restore
RMAN-06023: no backup or copy of datafile 8 found to restore
RMAN-06023: no backup or copy of datafile 7 found to restore
RMAN-06023: no backup or copy of datafile 6 found to restore
RMAN-06023: no backup or copy of datafile 5 found to restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
RMAN>Just in case, I re-run this script including the crosscheck backup and the delete noprompt expired backups before restoring an the error messages were the same.
THanks again for your help.
Regards.
Martin
Edited by: martin.morono on Nov 9, 2012 7:21 AM -
Completeness of Prerequisites for Recovering Tables for PDBs from RMAN Backups
Could you verify the completeness of following prerequisities on pag. 441 of the "Backup and Recovery User's Guide 12c Release 1 (12.1) E17630-14"
Prerequisites for Recovering Tables and Table Partitions from RMAN Backups
■ The target database must be in read-write mode.
■ The target database must be in ARCHIVELOG mode.
■ You must have RMAN backups of the tables or table partitions as they existed at the point in time to which you want recover these objects.
■ To recover single table partitions, the COMPATIBLE initialization parameter for target database must be set to 11.1.0 or higher.
According to my test Database administrator workshop: How to recover a table in a pluggable database from a backup
those prerequisities are valid for CDBs or non-CBDs, but if you want to recover tables or table partitions in PDBs a different prerequisite is needed.
Indeed if you have a backup of only the pluggable database including the missing table (the third prerequisite above), but you don't have any backup of the container database the command...
recover table ... of pluggable database ... until scn ... auxiliary destination ...
will fail with the following errors:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 02/12/2014 12:22:18
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
So to recover table in PDBs you must have also the RMAN backups of the CDB or in the opposite way it's not sufficient to have only the backups of the pluggable database, because during the creation of the auxiliary database the SYS, SYSAUX and the UNDO tablespace are required.
Regards,
MarcoVHi,
Before dropping a DB we had taken an RMAN backup.I hope you were in mount mode.
Will RMAN automatically recognize the FORMAT of the backup piece and restore ?No it won't.
First you have to restore a controlfile in nomount mode with:
restore controlfile from '/u04/backup/rmanbkp /02mo9fnc_1_1';
and do alter database mount.
Than you have to run "catalog start with '/u04/backup/rmanbkp'; " so the instance now knows where to find the pieces.
Now you can run a restore database command.
Than open the database with resetlogs.
Regards,
Tycho -
Undo tablespace recovery from RMAN backup
Hi,
Lets's assume we have RMAN backup and archivelog backups, and now
my undo tablespace's disk crashed ,how can i recover?
Can i recover while database is up?
Thanks,
Kumar.to recover UNDO tablespace from RMAN backup you must shutdown the database and start it in the MOUNT state to recover the missing files as follows
rman target /
RUN
STARTUP MOUNT;
ALLOCATE CHANNEL ch3 TYPE Disk;
RESTORE datafile 'c:\u01\prod3\undo01.dbf';
RECOVER datafile 'c:\u01\prod3\undo01.dbf';
ALTER DATABASE OPEN;
RELEASE CHANNEL ch3;
hope this will help you -
Steps to Recover OFFLINE datafile
Dear Guru's,
DB_VERSION-10.2.0.4
OS_VERSION-WINDOWS 2003 SERVER
I have noticed a datafile is offline from v$recover_file
15:05:08 prod >@db
NAME OPEN_MODE LOG_MODE HOST_NAME
PROD READ WRITE ARCHIVELOG PRODHOST
Elapsed: 00:00:00.51
15:05:10 prod >select * from v$recover_file;
FILE# ONLINE ONLINE_ ERROR CHANGE# TIME
20 OFFLINE OFFLINE 1160523233 19-JAN-12
Elapsed: 00:00:00.06
15:05:10 prod >select * from v$backup;
FILE# STATUS CHANGE# TIME
1 NOT ACTIVE 151722179 07-JUL-09
2 NOT ACTIVE 151722231 07-JUL-09
3 NOT ACTIVE 151722144 07-JUL-09
4 NOT ACTIVE 151722408 07-JUL-09
5 NOT ACTIVE 151721658 07-JUL-09
6 NOT ACTIVE 151721658 07-JUL-09
7 NOT ACTIVE 151721893 07-JUL-09
8 NOT ACTIVE 151721893 07-JUL-09
9 NOT ACTIVE 151721893 07-JUL-09
10 NOT ACTIVE 151721893 07-JUL-09
11 NOT ACTIVE 151721893 07-JUL-09
12 NOT ACTIVE 151721658 07-JUL-09
13 NOT ACTIVE 151721658 07-JUL-09
14 NOT ACTIVE 151721658 07-JUL-09
15 NOT ACTIVE 151721781 07-JUL-09
16 NOT ACTIVE 151721781 07-JUL-09
17 NOT ACTIVE 151721781 07-JUL-09
18 NOT ACTIVE 151721781 07-JUL-09
19 NOT ACTIVE 151721781 07-JUL-09
21 NOT ACTIVE 151721611 07-JUL-09
22 NOT ACTIVE 151722063 07-JUL-09
23 NOT ACTIVE 0
24 NOT ACTIVE 0
25 NOT ACTIVE 0
24 rows selected.
Elapsed: 00:00:00.17
15:05:10 prod >select max(sequence#) from v$archived_log;
MAX(SEQUENCE#)
30804Also because of which my export backup log showing following message :
. . exporting table XDF
EXP-00056: ORACLE error 376 encountered
ORA-00376: file 20 cannot be read at this time
ORA-01110: data file 20: 'E:\PROD\DATA\RMAN01.DBF'Kindly suggest your views in order to perform recovery.
Edited by: user12000301 on Feb 2, 2012 1:51 AMHi,
Tried to recover data file 20 of tablespace RMAN
RMAN> recover tablespace 'RMAN';
Starting recover at 02-FEB-12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=192 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=191 devtype=DISK
starting media recovery
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 02/02/2012 16:29:09
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 29881 lowscn 1162657672 found to restore
RMAN-06025: no backup of log thread 1 seq 29880 lowscn 1162614694 found to restore
RMAN-06102: no channel to restore a backup or copy of log thread 1 seq 29879 lowscn 1162613529
RMAN-06102: no channel to restore a backup or copy of log thread 1 seq 29878 lowscn 1162607230Also
SQL> recover datafile 20;
ORA-00279: change 1160523233 generated at 01/19/2012 11:53:51 needed for thread 1
ORA-00289: suggestion : E:\ARCHIVES\PROD_1_29777_717158136.LOG
ORA-00280: change 1160523233 for thread 1 is in sequence #29777
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
auto
ORA-00308: cannot open archived log 'E:\ARCHIVES\PROD_1_29777_717158136.LOG'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-00308: cannot open archived log 'E:\ARCHIVES\PROD_1_29777_717158136.LOG'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.The required archive is of 20-Jan-2012.Since the retention policy of the Primary is of 5 days,the archive is no longer available on the disk.
I have also tired to find the archive on DR server's but it has deleted.
The backup regularly goes onto the tape.
Also this tablespace i.e. RMAN is not critical for us as we are no longer using catalog.
Kindly suggest your views on the same.
Thanks in advance. -
Block corruption in UNDO datafile
Hi,
I am getting block corruption problem related to undo datafile on my pre production db.
Alert log says:
Tue Jun 24 17:59:38 2008
Errors in file /oracle/admin/CBOPROD/bdump/cboprod_pmon_2596886.trc:
ORA-01578: ORACLE data block corrupted (file # 2, block # 121)
ORA-01110: data file 2: '/oracle/oradata/CBOPROD/undotbs01.dbf'
Tue Jun 24 17:59:38 2008
Errors in file /oracle/admin/CBOPROD/bdump/cboprod_pmon_2596886.trc:
ORA-01578: ORACLE data block corrupted (file # 2, block # 137)
ORA-01110: data file 2: '/oracle/oradata/CBOPROD/undotbs01.dbf'
Tue Jun 24 17:59:38 2008
Errors in file /oracle/admin/CBOPROD/bdump/cboprod_pmon_2596886.trc:
ORA-01578: ORACLE data block corrupted (file # 2, block # 57)
ORA-01110: data file 2: '/oracle/oradata/CBOPROD/undotbs01.dbf'
Tue Jun 24 17:59:38 2008
Errors in file /oracle/admin/CBOPROD/bdump/cboprod_pmon_2596886.trc:
ORA-01578: ORACLE data block corrupted (file # 2, block # 25)
ORA-01110: data file 2: '/oracle/oradata/CBOPROD/undotbs01.dbf'
Tue Jun 24 17:59:38 2008
Errors in file /oracle/admin/CBOPROD/bdump/cboprod_pmon_2596886.trc:
ORA-01578: ORACLE data block corrupted (file # 2, block # 105)
ORA-01110: data file 2: '/oracle/oradata/CBOPROD/undotbs01.dbf'
Tue Jun 24 17:59:38 2008
Errors in file /oracle/admin/CBOPROD/bdump/cboprod_pmon_2596886.trc:
ORA-01578: ORACLE data block corrupted (file # 2, block # 73)
ORA-01110: data file 2: '/oracle/oradata/CBOPROD/undotbs01.dbf'
Tue Jun 24 17:59:38 2008This issue happend while loading the data into db. I am more worried about data rather than availability as we took a good time move production data.
I have the cold backup of last night using RMAN (at mount stage) and my db is running in Archive log mode.
Please suggest to how to approach in current scnario.
OS: AIX 5.3
Oracle: 10.2.0.3.0
Thanks for your time
BhupinderBhupinder,
The problem here it is your undo tablespace, and you are getting this error, because Oracle is hitting these blocks to use them.
You could try to create a new undo tablespace, but this measure is a bit strange, as obviously you can change the undo tablespace only without current transactions. If you can change the undo tablespace why recover the inactive undo tablespace?
I would probably try to change the undo tablespace, and if that fails there really is no other solution than at least restore the entire undo tablespace. Likely undo is disabled in mount stage so this should work.
Hth
Sybrand Bakker
Senior Oracle DBA -
Trying to recover an standby database
- Oracle 10.2.0.4 Standard Edition
- O/S: Windows Server 2003
- Phisically Standby
We have primary and a standby database. My standby database was synchronized through copying archive redo logs from Primary to Standby. They were copied every 15 min to standby server and then they were recovered from there. Because a lot of archive logs were missed for ever, now my standby database is not synchronized with my primary.
In order to recover my Standby, one week ago I followed these instructions:
Step 1: On the standby database check the current scn.
STDBY> select current_scn from v$database;
CURRENT_SCN
2527075174
Step 2: On the primary database create the needed incremental backup from the above SCN
C:\Documents and Settings\frego>rman target /
run {
allocate channel c1 type disk;
BACKUP INCREMENTAL FROM SCN 2527075174 DATABASE
format '\\srvbackup\archiveslogs-35\arch\incr_bkp_%U';
Step 3: Cancel managed recovery at the standby database
STDBY>alter database recover managed standby database cancel;
Media recovery complete.
Copied the backup files to standby server to "D:\arch\" folder.
Step 4: Catalog the Incremental Backup Files at the Standby Database
D:\arch> rman target /
RMAN> CATALOG START WITH 'D:\arch\';
Step 5: Apply the Incremental Backup to the Standby Database
RMAN> RECOVER DATABASE NOREDO;
Step 6: Put the standby database back to managed recovery mode.
STDBY>> recover managed standby database disconnect;
Media recovery complete.
Step 7: On the primary create new standby controlfile
PRIM>alter database create standby controlfile as 'C:\incr_bkp\standby01.ctl';
System altered.
Step 8: At Standby .. Replace standby controlfile at all location as shown by controle_files parameter.
Copy the standby control file to the standby site. Shutdown the standby database and replace the stanby controlfiles and restart the >standby database in managed recovery mode...
Problem was that there were new datafiles created in primary that didn't exist in standby. I had to created them manually on standby:
ALTER DATABASE CREATE DATAFILE 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB3.ORA' AS 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB3.ORA';
ALTER DATABASE CREATE DATAFILE 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB4.ORA' AS 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB4.ORA';
ALTER DATABASE CREATE DATAFILE 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BKP.ORA' AS 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BKP.ORA';
ALTER DATABASE CREATE DATAFILE 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB5.ORA' AS 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB5.ORA';
ALTER DATABASE CREATE DATAFILE 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB_A.ORA' AS 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB_A.ORA';
ALTER DATABASE CREATE DATAFILE 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB_B.ORA' AS 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB_B.ORA';
ALTER DATABASE CREATE DATAFILE 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB_C.ORA' AS 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB_C.ORA';
ALTER DATABASE CREATE DATAFILE 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB_D.ORA' AS 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB_D.ORA';
ALTER DATABASE CREATE DATAFILE 'D:\ORADATA\PROD\OPEXT\DATAFILES_IDX\PADRONIDX17.ORA' AS 'D:\ORADATA\PROD\OPEXT\DATAFILES_IDX\PADRONIDX17.ORA';
Also, I tried this commands:
On Standby:
RMAN> SHUTDOWN;
RMAN> STARTUP NOMOUNT;
RMAN> RESTORE STANDBY CONTROLFILE FROM 'D:\arch\standby01.ctl';
RMAN> SHUTDOWN;
RMAN> STARTUP MOUNT;
STDB> ALTER DATABASE CLEAR LOGFILE GROUP 1;
STDB> ALTER DATABASE CLEAR LOGFILE GROUP 2;
STDB> ALTER DATABASE CLEAR LOGFILE GROUP 3;
STDB> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT;
Database altered.
SQL> alter database open read only;
alter database open read only
ERROR at line 1:
ORA-01154: database busy. Open, close, mount, and dismount not allowed now
SQL> recover managed standby database cancel;
Media recovery complete.
SQL> alter database open read only;
alter database open read only
ERROR at line 1:
ORA-16004: backup database requires recovery
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: 'D:\ORADATA\PROD\OPEXT\SYSTEM01.DBF'My Questions:
- What is missing in order to open standby database?
- Can I again generate rman incremental backups on Primary (from SCN 2527075174), copy them to Standby and start recovery again? Would it generate duplicate records on tables?
- Should I generate new rman incremental backup pieces on Primary (from last SCN of Standby), copy them to standby and apply there?
Remember that my Primary is growing every day and those rman backup pieces and standby01.ctl, that are copied on my standby server, are from one week ago.
Thanks
Edited by: user521219 on 22-jun-2012 9:31user521219 wrote:
Should I restart and mount my standby database again?
If I apply Step 3 now:
STB> alter database recover managed standby database cancel;
ERROR at line 1:
ORA-16136: Managed Standby Recovery not activeRefer the above mentioned link. First restore controlfile & then perform recovery on standby database.
>
user521219
Newbie
Handle: user521219
Status Level: Newbie
Registered: Jul 20, 2006
Total Posts: 48
Total Questions: 29 (23 unresolved)
>
Consider closing your threads and keep the forum clean.
Edited by: CKPT on Jun 22, 2012 10:43 PM -
Please assist I have lost undo datafile
Hi ,please advice me ,the filesystem that contantain undo datafile is lost while the database is was down for OS maintenance,now when I have to start database I found that undo datafile is lost and they can't even see it from OS side,how can I start the database.
P. Forstmann wrote:
If you didn't shutdown your database cleanly and you have no backup for undo tablespace then there is no documented way to restart your database instance and you should contact Oracle Support.Yes,that is right,if database was not cleanly shutdown(with abort option) then actually in next instance startup will need recover and its instance recovery(must be perform).But performing instance recovery need undo tablespace,actually this is lost ,so with simple operations you can not open database.Of course the best way is report Oracle Support.However you can implement hidden parameter to opening database(_offline_rollback_segments).I do not recommend this way,just can try this.Before doing this you have to full backup database. -
Rconfig: converting a single instance to RAC instance
Hi,
I am trying to use the "rconfig" utility to convert a single instance to a RAC instance in an existing RAC cluster.
I have modified the .xml file, and am trying to run the conversion from the 1st node in the 2 node cluster (where the single instance resides).
The only error message i seem to be getting is below:
<Response>
<Result code="1" >
Operation Failed
</Result>
<ErrorDetails>
ORCL_DATA_ORCLCLN The specified diskgroup is not mounted.
</ErrorDetails>
</Response>
</Convert>
</ConvertToRAC></RConfig>
Now I dont really understand why I would be getting that message as the instance is up and running and ASM disk group is mounted on node1 at the time i run the rconfig command, though its not clear to me if I also need to somehow mount the ASM disk group on the second node prior to running the rconfig command??
node1:
bash-3.00$ asmcmd -p
ASMCMD [+] > lsdg
State Type Rebal Unbal Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Name
MOUNTED EXTERN N N 512 4096 1048576 10181 7442 0 7442 0 ORCL_DATA_ORCLCLN/
node2:
ASMCMD [+] > lsdg
State Type Rebal Unbal Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Name
I have attached the output of the alert log during the rconfig conversion of the target database, but it all looks pretty standard to me (keep in mind i am an oracle novice!).
alert.log
Completed: ALTER DATABASE OPEN
Thu Jul 23 13:51:55 2009
Shutting down instance (abort)
License high water mark = 2
Instance terminated by USER, pid = 15030
Thu Jul 23 13:51:57 2009
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Interface type 1 e1000g1 10.128.113.0 configured from OCR for use as a cluster interconnect
Interface type 1 e1000g0 10.128.113.0 configured from OCR for use as a public interface
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_1 parameter default value as /u01/app/oracle/product/10.2.0/db_1/dbs/arch
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.2.0.
System parameters with non-default values:
processes = 150
__shared_pool_size = 121634816
__large_pool_size = 4194304
__java_pool_size = 4194304
__streams_pool_size = 0
sga_target = 440401920
control_files = +ORCL_DATA_ORCLCLN/control01.ctl
db_block_size = 8192
__db_cache_size = 306184192
compatible = 10.2.0.2.0
log_archive_format = %t_%s_%r.dbf
db_file_multiblock_read_count= 16
cluster_database = FALSE
cluster_database_instances= 1
db_recovery_file_dest_size= 2147483648
norecovery_through_resetlogs= TRUE
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain = netapp.com
job_queue_processes = 10
background_dump_dest = /u01/app/oracle/admin/orcldb/bdump/ORCLCLN
user_dump_dest = /u01/app/oracle/admin/orcldb/udump/ORCLCLN
core_dump_dest = /u01/app/oracle/admin/orcldb/cdump/ORCLCLN
db_name = ORCLCLN
open_cursors = 300
pga_aggregate_target = 145752064
Cluster communication is configured to use the following interface(s) for this instance
10.128.113.200
Thu Jul 23 13:51:59 2009
cluster interconnect IPC version:Oracle UDP/IP (generic)
IPC Vendor 1 proto 2
PMON started with pid=2, OS id=15085
DIAG started with pid=3, OS id=15091
PSP0 started with pid=4, OS id=15094
LMON started with pid=5, OS id=15097
LMD0 started with pid=6, OS id=15102
MMAN started with pid=7, OS id=15112
DBW0 started with pid=8, OS id=15114
LGWR started with pid=9, OS id=15116
CKPT started with pid=10, OS id=15125
SMON started with pid=11, OS id=15128
RECO started with pid=12, OS id=15130
CJQ0 started with pid=13, OS id=15134
MMON started with pid=14, OS id=15143
MMNL started with pid=15, OS id=15146
Thu Jul 23 13:52:03 2009
lmon registered with NM - instance id 1 (internal mem no 0)
Thu Jul 23 13:52:04 2009
Reconfiguration started (old inc 0, new inc 2)
List of nodes:
0
Global Resource Directory frozen
* allocate domain 0, invalid = TRUE
Communication channels reestablished
Master broadcasted resource hash value bitmaps
Non-local Process blocks cleaned out
Resources and enqueues cleaned out
Resources remastered 0
Set master node info
Submitted all remote-enqueue requests
Dwn-cvts replayed, VALBLKs dubious
All grantable enqueues granted
Post SMON to start 1st pass IR
Submitted all GCS remote-cache requests
Post SMON to start 1st pass IR
Reconfiguration complete
Thu Jul 23 13:52:04 2009
ALTER DATABASE MOUNT
Thu Jul 23 13:52:04 2009
Starting background process ASMB
ASMB started with pid=17, OS id=15157
Starting background process RBAL
RBAL started with pid=18, OS id=15169
Thu Jul 23 13:52:09 2009
SUCCESS: diskgroup ORCL_DATA_ORCLCLN was mounted
Thu Jul 23 13:52:13 2009
Setting recovery target incarnation to 2
Thu Jul 23 13:52:13 2009
Successful mount of redo thread 1, with mount id 4437636
Thu Jul 23 13:52:13 2009
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Thu Jul 23 13:52:14 2009
ALTER DATABASE OPEN
Thu Jul 23 13:52:14 2009
Beginning crash recovery of 1 threads
Thu Jul 23 13:52:14 2009
Started redo scan
Thu Jul 23 13:52:14 2009
Completed redo scan
105 redo blocks read, 32 data blocks need recovery
Thu Jul 23 13:52:14 2009
Started redo application at
Thread 1: logseq 2, block 929
Thu Jul 23 13:52:15 2009
Recovery of Online Redo Log: Thread 1 Group 2 Seq 2 Reading mem 0
Mem# 0 errs 0: +ORCL_DATA_ORCLCLN/redo_2_1.log
Mem# 1 errs 0: +ORCL_DATA_ORCLCLN/redo_2_0.log
Thu Jul 23 13:52:15 2009
Completed redo application
Thu Jul 23 13:52:15 2009
Completed crash recovery at
Thread 1: logseq 2, block 1034, scn 613579
32 data blocks read, 25 data blocks written, 105 redo blocks read
Thu Jul 23 13:52:15 2009
Thread 1 advanced to log sequence 3
Thread 1 opened at log sequence 3
Current log# 1 seq# 3 mem# 0: +ORCL_DATA_ORCLCLN/redo_1_1.log
Current log# 1 seq# 3 mem# 1: +ORCL_DATA_ORCLCLN/redo_1_0.log
Successful open of redo thread 1
Thu Jul 23 13:52:15 2009
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Thu Jul 23 13:52:15 2009
SMON: enabling cache recovery
Thu Jul 23 13:52:17 2009
Successfully onlined Undo Tablespace 1.
Thu Jul 23 13:52:17 2009
SMON: enabling tx recovery
Thu Jul 23 13:52:17 2009
Database Characterset is WE8ISO8859P1
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=21, OS id=15328
Thu Jul 23 13:52:23 2009
Completed: ALTER DATABASE OPEN
Any help would be greatly appreciated!!!!Ok,
So I managed to get the disk group mounted on the second node, and re-ran the rconfig process.
I got a little further, but encountered another error which is displayed below:
-bash-3.00$ rconfig racconv.xml
<?xml version="1.0" ?>
<RConfig>
<ConvertToRAC>
<Convert>
<Response>
<Result code="1" >
Operation Failed
</Result>
<ErrorDetails>
/u01/app/oracle/product/10.2.0/db_1/dbs Data File is not shared across all nodes in the cluster
</ErrorDetails>
</Response>
</Convert>
</ConvertToRAC></RConfig>
I am not using a shared oracle home, each node in the cluster has its own oracle installation residing on local disk. Is a shared oracle home a pre-requisite for usin rconfig?
I have provided the .xml file I am using below:
-bash-3.00$ cat racconv.xml
<?xml version="1.0" encoding="UTF-8"?>
<n:RConfig xmlns:n="http://www.oracle.com/rconfig"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.oracle.com/rconfig">
<n:ConvertToRAC>
<!-- Verify does a precheck to ensure all pre-requisites are met, before the conversion is attempted. Allowable values are: YES|NO|ONLY -->
<n:Convert verify="YES">
<!--Specify current OracleHome of non-rac database for SourceDBHome -->
<n:SourceDBHome>/u01/app/oracle/product/10.2.0/db_1</n:SourceDBHome>
<!--Specify OracleHome where the rac database should be configured. It can be same as SourceDBHome -->
<n:TargetDBHome>/u01/app/oracle/product/10.2.0/db_1</n:TargetDBHome>
<!--Specify SID of non-rac database and credential. User with sysdba role is required to perform conversion -->
<n:SourceDBInfo SID="ORCLCLN">
<n:Credentials>
<n:User>oracle</n:User>
<n:Password>password</n:Password>
<n:Role>sysdba</n:Role>
</n:Credentials>
</n:SourceDBInfo>
<!--ASMInfo element is required only if the current non-rac database uses ASM Storage -->
<n:ASMInfo SID="+ASM1">
<n:Credentials>
<n:User>oracle</n:User>
<n:Password>password</n:Password>
<n:Role>sysdba</n:Role>
</n:Credentials>
</n:ASMInfo>
<!--Specify the list of nodes that should have rac instances running. LocalNode should be the first node in this nodelist. -->
<n:NodeList>
<n:Node name="sol002"/>
<n:Node name="sol003"/>
</n:NodeList>
<!--Specify prefix for rac instances. It can be same as the instance name for non-rac database or different. The instance number will be attached to this prefix. -->
<n:InstancePrefix>ORCLCLN</n:InstancePrefix>
<!--Specify port for the listener to be configured for rac database.If port="", alistener existing on localhost will be used for rac database.The listener will be extended to all nodes in the nodelist -->
<n:Listener port=""/>
<!--Specify the type of storage to be used by rac database. Allowable values are CFS|ASM. The non-rac database should have same storage type. -->
<n:SharedStorage type="ASM">
<!--Specify Database Area Location to be configured for rac database.If this field is left empty, current storage will be used for rac database. For CFS, this field will have directory path. -->
<n:TargetDatabaseArea></n:TargetDatabaseArea>
<!--Specify Flash Recovery Area to be configured for rac database. If this field is left empty, current recovery area of non-rac database will be configured for rac database. If current database is not using recovery Area, the resulting rac database will not have a recovery area. -->
<n:TargetFlashRecoveryArea></n:TargetFlashRecoveryArea>
</n:SharedStorage>
</n:Convert>
</n:ConvertToRAC>
</n:RConfig> -
Mapping PROD RAC Disk Groups to Three RAC Instances on SIngle TEST Server ?
Hi,
None of the books or papers describe one critical design. Assuming we are using EMC's BCV volume's or HDS's ShadowImage Software, we need the following.
Server 1-
- Production has 2 node RAC with 3 DG's under ASM, PROD_DATA, PROD_FLASH and PROD_ARCHIVE - Each are 64GB, each has one RAW device externally managed, Servers are PROD1 and PROD2
Server 2-
- Test, Conv, Dev are three RAC instances on RAC instances, on TEST1 and
TEST2 Server
Now we have 9 DG;s under ASM control , ASM1, ASM2
- TEST_DATA, TEST_FLASH, TEST_ARCHIVE
- DEV_DATA, DEV_FLASH, DEV_ARCHIVE
- CONV_DATA, CONV_FLASH, CONV_ARCHIVE
Now Issue is this - CLONING
- We BCV clones from PROD to TEST or PROD to CONV or PROD to DEV
- When the RAW files are SYNC from PROD, the ASM disk header gets to migrate as well, so the ASM DG names we have in TEST do not match what came from PROD, for simplicity
PROD_DATA cloned over RAW divice that MAPS to TEST_DATA
and the others as well. Now ASM DG we have for test is TEST_DATA afterthe clone the RAW header is PROD_DATA, there is a mismatch, for us to fix that we change our DG names for test to PROD_DATA etc and fix the control file.
Now what do we do for DEV and CONV? Same things will happen to those BCV volumes as well after block level copy is done...
If all these instances were on seperate boxes we could have fixed the issue or lived with same DG names as PROD...
We do not want to move database from ASM to FS and then to ASM or do ASM to ASM RMAN duplication, we want to do BCV or HDS shadow copy..If we did we could have same DG names in test server and have 3 times more storage than PROD and do all things manually without BCV or HDS's shadowclone..
How do we handle this situation? Please suggest... ASM dg rename is not fixed, that could have helpes until 11g R2...
I am not able to see any paper on this... I read the ASM book as well no such discussion.do not really understand all your config but here is what i can tell you
imho the solution is to copy the datafile (not the disks/raw devices) from one diskgroup to the other ; and indeed best way to do it is to use RMAN
note that in 11g, ASMCMD implements the cp command , so it is more easy.
It enables you to copy files between ASM disk groups on local instances to and from remote instances. The file copy cannot be between remote instances. The local ASM instance must be either the source or the target of the operation. You can also use this command to copy files from ASM disk groups to the operating system. -
Why it automatically recover current redo log in RMAN command window?
Firstly, I restore controlfile and datafiles from a backupset.
Then when I recover database in RMAN command window like below:
RMAN> recover database;
Starting recover at 15-AUG-13
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
starting media recovery
archive log thread 1 sequence 9 is already on disk as file /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_9_90sd0slz_.arc
archive log thread 1 sequence 10 is already on disk as file
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_10_90sd0tsb_.arc
archive log thread 1 sequence 11 is already on disk as file
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_11_90sd110b_.arc
archive log thread 1 sequence 12 is already on disk as file
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_12_90sd2ksr_.arc
archive log thread 1 sequence 13 is already on disk as file
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_13_90sd2mc6_.arc
archive log thread 1 sequence 14 is already on disk as file
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_14_90sd2qrm_.arc
archive log thread 1 sequence 15 is already on disk as file
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_15_90sd2s0w_.arc
archive log thread 1 sequence 16 is already on disk as file /u01/app/oracle/oradata/lonion/redo03.log
archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_9_90sd0slz_.arc thread=1 sequence=9
archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_10_90sd0tsb_.arc thread=1 sequence=10
archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_11_90sd110b_.arc thread=1 sequence=11
archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_12_90sd2ksr_.arc thread=1 sequence=12
archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_13_90sd2mc6_.arc thread=1 sequence=13
archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_14_90sd2qrm_.arc thread=1 sequence=14
archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_15_90sd2s0w_.arc thread=1 sequence=15
archive log filename=/u01/app/oracle/oradata/lonion/redo03.log thread=1 sequence=16
media recovery complete, elapsed time: 00:00:04
Finished recover at 15-AUG-13
RMAN>
But, when I recover database in SQL*Plus command window like below:
[oracle@lonion ~]$ uniread sqlplus /nolog
[uniread] Loaded history (2178 lines)
SQL*Plus: Release 10.2.0.1.0 - Production on Thu Aug 15 19:25:38 2013
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> conn /as sysdba
Connected.
SQL>
SQL> recover database;
ORA-00283: recovery session canceled due to errors
ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
SQL> recover database using backup controlfile;
ORA-00279: change 2147842454 generated at 08/15/2013 18:34:28 needed for thread
1
ORA-00289: suggestion :
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_9_%u_.a
rc
ORA-00280: change 2147842454 for thread 1 is in sequence #9
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
auto
ORA-00279: change 2147842651 generated at 08/15/2013 18:40:25 needed for thread
1
ORA-00289: suggestion :
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_10_%u_.
arc
ORA-00280: change 2147842651 for thread 1 is in sequence #10
ORA-00278: log file
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_9_90sd
0slz_.arc' no longer needed for this recovery
ORA-00279: change 2147842653 generated at 08/15/2013 18:40:26 needed for thread
1
ORA-00289: suggestion :
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_11_%u_.
arc
ORA-00280: change 2147842653 for thread 1 is in sequence #11
ORA-00278: log file
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_10_90s
d0tsb_.arc' no longer needed for this recovery
ORA-00279: change 2147842656 generated at 08/15/2013 18:40:32 needed for thread
1
ORA-00289: suggestion :
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_12_%u_.
arc
ORA-00280: change 2147842656 for thread 1 is in sequence #12
ORA-00278: log file
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_11_90s
d110b_.arc' no longer needed for this recovery
ORA-00279: change 2147842684 generated at 08/15/2013 18:41:21 needed for thread
1
ORA-00289: suggestion :
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_13_%u_.
arc
ORA-00280: change 2147842684 for thread 1 is in sequence #13
ORA-00278: log file
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_12_90s
d2ksr_.arc' no longer needed for this recovery
ORA-00279: change 2147842686 generated at 08/15/2013 18:41:23 needed for thread
1
ORA-00289: suggestion :
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_14_%u_.
arc
ORA-00280: change 2147842686 for thread 1 is in sequence #14
ORA-00278: log file
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_13_90s
d2mc6_.arc' no longer needed for this recovery
ORA-00279: change 2147842689 generated at 08/15/2013 18:41:27 needed for thread
1
ORA-00289: suggestion :
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_15_%u_.
arc
ORA-00280: change 2147842689 for thread 1 is in sequence #15
ORA-00278: log file
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_14_90s
d2qrm_.arc' no longer needed for this recovery
ORA-00279: change 2147842691 generated at 08/15/2013 18:41:28 needed for thread
1
ORA-00289: suggestion :
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_16_%u_.
arc
ORA-00280: change 2147842691 for thread 1 is in sequence #16
ORA-00278: log file
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_15_90s
g0or9_.arc' no longer needed for this recovery
ORA-00279: change 2147842986 generated at 08/15/2013 19:14:29 needed for thread
1
ORA-00289: suggestion :
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_17_%u_.
arc
ORA-00280: change 2147842986 for thread 1 is in sequence #17
ORA-00278: log file
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_16_90s
g0os5_.arc' no longer needed for this recovery
ORA-00308: cannot open archived log
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_17_%u_
.arc'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
SQL> recover database using backup controlfile;
ORA-00279: change 2147842986 generated at 08/15/2013 19:14:29 needed for thread
1
ORA-00289: suggestion :
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_17_%u_.
arc
ORA-00280: change 2147842986 for thread 1 is in sequence #17
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/u01/app/oracle/oradata/lonion/redo01.log ---- Yon see, proceeding this process, it can't automatically apply the current redo log.
Log applied.
Media recovery complete.
SQL>
Question Coming:
Now, my question is that 「Why it automatically recover current redo log in RMAN command window but not in SQL*Plus」?
BTW: Please pay attention to the red font.It also seems not work.
SQL> recover automatic database using backup controlfile;
ORA-00279: change 2148632889 generated at 09/26/2013 12:45:22 needed for thread
1
ORA-00289: suggestion :
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_.
arc
ORA-00280: change 2148632889 for thread 1 is in sequence #48
ORA-00278: log file
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_
.arc' no longer needed for this recovery
ORA-00308: cannot open archived log
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_
.arc'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
auto
ORA-00308: cannot open archived log
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_
.arc'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
ORA-00308: cannot open archived log
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_
.arc'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file
or directory
Additional information: 3
SQL>
It must specify the redo log.
SQL> recover database using backup controlfile;
ORA-00279: change 2148632889 generated at 09/26/2013 12:45:22 needed for thread
1
ORA-00289: suggestion :
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_.
arc
ORA-00280: change 2148632889 for thread 1 is in sequence #48
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/u01/app/oracle/oradata/lonion/redo02.log
Log applied.
Media recovery complete.
SQL> -
SMON ABOUT TO RECOVER UNDO SEGMENT s messages in alert log
Problem
======
There are lots of messages appearing in alert log of the following form:
SMON: about to recover undo segment %s
SMON: mark undo segment %s as available
Reason
======
When the recovery is going on after a abnormal shutdown. Cause These errors do not indicate rollback segment corruption. In oracle8i, this may becoz of problem with the "rollback_segments" parameter in the init.ora. where as in oracle9i, When the instance is shutdown, during the next startup instance recovery needs to take place.
In AUM we do not have any control over which undo segments will brought online after the instance startup.When SMON finds such offline undo segments with transactions needing recovery ,then it does what is intended to do recovery.
Solution
======
with oracle8i, we need to cross check rollback_segments" parameter in the init.ora
with oracle9i,
first note down segment from SMON: mark undo segment %s as available
sqlplus "/ as sysdba"
alter session set "_smu_debug_mode"=4;
alter rollback segment <offline segment name> online;
e.g. alter rollback segment "_SYSSMU11$" online;
Where 11 is the number that is appearing in the messages in the alert log.What's the point duplicate metalink doc here,
SMON: ABOUT TO RECOVER UNDO SEGMENT %s messages in alert log
Doc ID: Note:266159.1
besides it's violation of Oracle support service contract. -
Trying to recover metadata from a lost DB
Hi:
We lost a DB instance and cannot recover. Ops replaced the broken disks and restored datafiles from backup, but "recover datafile..." for a specific datafile fails with OAR-01113 (file 89 needs media recovery). It calls for a file called arch1_120544.dbf which it (and I) cannot find.
Anyway....
What I'd really like to do at this point is to salvage the metadata. Is there a way to do this without starting the instance? Can I drop the problem datafile (and if necessary, the associated tablespace) somehow and then start the instance without it/them?
Thanks!Nope, not yet...
SVRMGR> shutdown immediate;
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SVRMGR> startup open pfile = "/odb0/oracle_projects/devodb/initdevodb.ora";
ORACLE instance started.
Total System Global Area 604451812 bytes
Fixed Size 103396 bytes
Variable Size 111763456 bytes
Database Buffers 491520000 bytes
Redo Buffers 1064960 bytes
Database mounted.
ORA-01113: file 89 needs media recovery
ORA-01110: data file 89: '/odb24/devodb/indexes/devodb_imp_idx_huge.dbf'
SVRMGR> alter database datafile '/odb24/devodb/indexes/devodb_imp_idx_huge.dbf' offline;
alter database datafile '/odb24/devodb/indexes/devodb_imp_idx_huge.dbf' offline
ORA-01145: offline immediate disallowed unless media recovery enabled
SVRMGR>
Maybe you are looking for
-
Object does not match target type when raising an event from c# to VB6
I have a c# .net DLL that I use from a VB6 app. It exposes an event, and the VB6 app is sinking it. The VB6 app is receiving the event, as long as it is raised from the main thread of the .net DLL. I have an aync task being handled inside the DLL (de
-
How to go on creating activities in loop?
Hi! Lead record type has activities associated with it. if a new lead is created, automatically an initial activity should be created with certain details and assigned to a particular sales rep. this i can do with workflow. this is fine. Now i want t
-
I recently had to get a new hard drive and didnt have back up files. How do I sync my iopd up without losing all my music?
-
Premier Elements 11 .vob Import?
Can Premier Elements 11 import .vob files? (I dub home movie VHSs to DVDs w/a Samsung DVD-VR375 DVD & VCR machine.) When I copy my DVD to my hard drive on my computer, I can play my files just fine. But when I want to edit my video to get rid of so
-
Error Message: E_LIC_ALREADY_FULFILLED_RESULTS
Is anyone familiar with such an error message?