Recovery of database

Hi...
My manager wants some data of 8th of aug-2010,but I have only this month backup dump. because I put the only one month backup redundancy.
Plz help me is there any method to find the data.plzzzzzz
Edited by: userjic on Sep 29, 2010 2:53 AM

Yes we have Flashback Recovery area....
Actually the problem is ...weekly we are exporting full backup of database,And only One month backup redundancy is we have in backup strategy.
I have only this month of backup... but my manager wants last month in between aug 8th to 16th date of data which I don't have a dump.
But not hole database restore..i need only may be nearly 300 records of data.
How can I recover it...
My be is it possible with log miner.

Similar Messages

Error while rman recovery of database

We are using rman recovery for database clone.
I am getting the following error,
restoring datafile 00442 to /d05/u10/oracle/ndevdata/applsysd06.dbf
channel dup1: reading from backup piece /db05/PROD_BACKUPS/inc0_dPROD_u1bku1pnr_t702605051_s15403_p1
ORA-19870: error reading backup piece /db05/PROD_BACKUPS/inc0_dPROD_u19ku1onq_t702604026_s15401_p1
ORA-19505: failed to identify file "/db05/PROD_BACKUPS/inc0_dPROD_u19ku1onq_t702604026_s15401_p1"
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options
Additional information: 3
ORA-19870: error reading backup piece /db05/PROD_BACKUPS/inc0_dPROD_u1aku1ou5_t702604229_s15402_p1
ORA-19505: failed to identify file "/db05/PROD_BACKUPS/inc0_dPROD_u1aku1ou5_t702604229_s15402_p1"
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options
Additional information: 3
ORA-19870: error reading backup piece /db05/PROD_BACKUPS/inc0_dPROD_u1bku1pnr_t702605051_s15403_p1
ORA-19505: failed to identify file "/db05/PROD_BACKUPS/inc0_dPROD_u1bku1pnr_t702605051_s15403_p1"
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options
Additional information: 3
failover to previous backup
How to resolve this?
Thanks,
Kavitha

hi;
Please follow:
Re: erros while clong a db
Also check:
http://kr.forums.oracle.com/forums/thread.jspa?threadID=546746
Re: rapid clone from RMAN backup
Regard
Helios

How to recovery the database from a complete backup

I have a 10.2.0.3 database with archive log enabled.
I do a cold backup of database every Sunday night.
I shutdown the database, copy all the database files, control files and redo logs to a backup disk.
Then the database started and running again.
I am trying to test my backup and make sure I can recovery the database to the most current stage using the Sunday backup and the archive logs.
for example: use the backup from 4/01/2012, recover the database to today 4/04/2012 9:00am.
What's the steps of doing this?
I tried to copy all the Sunday backup files to the correct location, start the database, the database is started successfully. However, I don't know how to apply the logs from since the Sunday backup upto now.
Thanks a lot!

hi,
rman is your friend to do backups, restores and recovers of database.
to do a full recover of database, for example to do a test on your current test database (no in crash):
rman time:
startup nomount;
restore controlfile;
alter database mount;
sql now
select archivelog_change#-1 from v$database;
then go back to rman and do the following :
RMAN> run{
2> set until scn xxxxxx;
3> restore database;
4> recover database;
5> alter database open resetlogs;
6> }
**where xxxxx is the result of your sql query
HTH
--edit:
forgot to told that You will need to set your ORACLE_HOME and ORACLE_SID env variables
Edited by: Me_101 on 04-abr-2012 8:41

Oracle RMAN recovery catalog database in a Primary and Standby mode

Hello All,
The customer wants the RMAN recovery catalog database to be highly available so that none of the RMAN database backup jobs are impacted at the time of taking the database backups. There are are 200+ databases running on OEL, RHEL and Windows. So we planned to host the recovery catalog database on Oracle Active DataGuard 11.2.0.1 Enterprise Edition on RedHat EL 5.8 version on two physical servers. The Primary Instance will be in one server in the Primary DC and the Standby Instance will be on another server in another DC. Also all the database datafiles are hosted in ASM Diskgroups on SAN (DATA, FRA, REDO, ARCH diskgroups).
Are there any specific RPM/patch/OS user custom/specific settings or configurations needed..?
Thanks in advance..
Regards,
Abhijit

"The customer wants the RMAN recovery catalog database to be highly available so that none of the RMAN database backup jobs are impacted at the time of taking the database backups"
Hi,
i think you can achieve HA for the catalog DB. (Rac and Asm should work fine)
There's no way (afaik) to use TAF with the rman backup. If you have a failure during a backup it simply fails.
There is no TAF in this situation.
Hope this helps.
Regs,
Drew

Config recovery catalog database

dear all.
i had read several documents about "create recovery catalog", but all of that start with statement
CREATE TABLESPACE
...and continue with CREATE USER, etc.
I want to create a NEW database for recovery catalog, this database what characteristics must to have ?? Anyone have a link or document where explain me how to create a database (only i need database creation) for recovery catalog.???
thanks
The version is ORacle 10gr2

hi,
the recovery catalog is just a normal database with a schema called rman or whatever you choose.
it should ideally be on a separate server to your target database. The RMAN database as with any other database should have multiplexed control files and redo files.
schema creation assumming windows O/S
-- Create tablepsace to hold repository
CREATE TABLESPACE "RMAN"
DATAFILE 'C:\ORACLE\ORADATA\W2K1\RMAN01.DBF' SIZE 6208K REUSE
AUTOEXTEND ON NEXT 64K MAXSIZE 32767M
EXTENT MANAGEMENT LOCAL
SEGMENT SPACE MANAGEMENT AUTO;
-- Create rman schema owner
CREATE USER rman IDENTIFIED BY rman
TEMPORARY TABLESPACE temp
DEFAULT TABLESPACE rman
QUOTA UNLIMITED ON rman;
GRANT connect, resource, recovery_catalog_owner TO rman;
then create the recovery catalog
C:>rman catalog=rman/rman@w2k1
Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to recovery catalog database
recovery catalog is not installed
RMAN> create catalog tablespace "RMAN";
recovery catalog created
RMAN> exit
Recovery Manager complete.
C:>
then register your database
C:>rman catalog=rman/rman@w2k1 target=sys/password@w2k2
Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: W2K2 (DBID=1371963417)
connected to recovery catalog database
RMAN> register database;
database registered in recovery catalog
starting full resync of recovery catalog
full resync complete
RMAN>
let us know how you get on.
rgds
alan

Query to identify the recovery catalog database name from target database

Hi,
How to get the recovery catalog database name from the registered target database?
i dont know my recovery catalog database for my target database.
I know we can use the query
select * from rc_database;
from recovery catalog database to know all the registered database with the recovery catalog but I want to know is there any way or query to identify the recovery catalog database name from target database to which the target database is registered
With Regards
Boobathi P

You can check the backup scripts which you use to backup your target database to get the catalog database name.
And check the corresponding connect string in TNSNAMES.ORA file or tnsping to get the server details of the catalog database.
Edited by: gopal on Apr 12, 2013 12:59 PM

Unable to recover database after rman recovery and database open resetlogs

I am running Oracle 10.2.0.5 on OpenSUSE 9. I have been trying to upgrade the database to 11g, through dbua. I was getting stuck at one point during the Oracle Server install and the upgrade failed and I was forced to restore the database to an earlier backup.
Below is the current place that I am stuck. As you can see I opened the database multiple times and reset the logs. Now I am afraid that my controlfile and redo log backups are out of sync and i can't get them back on track. Before when I actually got the database recovered RMAN would immediately throw:
RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row
RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows
OPA-00600: ORA-00600: internal error code, arguments: ...
The database would open with ALTER DATABASE RESETLOGS but any query on non-system tables would fail and throw:
ORA-04045: errors during recompilation/revalidation of LCRS_DEV1.FACILITY_REF
ORA-00600: internal error code, arguments: [17069], [0x1158ED180], [], [], [],
I hope I have not dug myself into too deep of a hole here.
Here is the trace from my most recent attempt.
RMAN> startup nomount;
connected to target database (not started)
Oracle instance started
Total System Global Area 3070230528 bytes
Fixed Size 2099424 bytes
Variable Size 301991712 bytes
Database Buffers 2751463424 bytes
Redo Buffers 14675968 bytes
RMAN> list incarnation of database;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 08/02/2011 15:49:04
ORA-01507: database not mounted
RMAN> restore controlfile from autobackup;
Starting restore at 02-AUG-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
recovery area destination: /opt/oracle/flash_recovery_area
database name (or database unique name) used for search: LCRSDEV
channel ORA_DISK_1: autobackup found in the recovery area
channel ORA_DISK_1: autobackup found: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
channel ORA_DISK_1: control file restore from autobackup complete
output filename=/opt/oracle/oradata/LCRSDEV/control01.ctl
output filename=/opt/oracle/oradata/LCRSDEV/control02.ctl
output filename=/opt/oracle/oradata/LCRSDEV/control03.ctl
Finished restore at 02-AUG-11
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN> list incarnation of database;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05
2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11
3 3 LCRSDEV 756543625 PARENT 92348137 18-JUL-11
4 4 LCRSDEV 756543625 PARENT 95654931 01-AUG-11
5 5 LCRSDEV 756543625 PARENT 95675699 01-AUG-11
6 6 LCRSDEV 756543625 PARENT 95676699 02-AUG-11
7 7 LCRSDEV 756543625 PARENT 95676700 02-AUG-11
8 8 LCRSDEV 756543625 CURRENT 95676701 02-AUG-11
RMAN> restore database until scn 95676700;
Starting restore at 02-AUG-11
Starting implicit crosscheck backup at 02-AUG-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
Crosschecked 6 objects
Finished implicit crosscheck backup at 02-AUG-11
Starting implicit crosscheck copy at 02-AUG-11
using channel ORA_DISK_1
Finished implicit crosscheck copy at 02-AUG-11
searching for all files in the recovery area
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 08/02/2011 15:52:04
RMAN-20208: UNTIL CHANGE is before RESETLOGS change
RMAN> restore database;
Starting restore at 02-AUG-11
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /opt/oracle/oradata/LCRSDEV/system01.dbf
restoring datafile 00002 to /opt/oracle/oradata/LCRSDEV/undotbs01.dbf
restoring datafile 00003 to /opt/oracle/oradata/LCRSDEV/sysaux01.dbf
restoring datafile 00004 to /opt/oracle/oradata/LCRSDEV/users01.dbf
restoring datafile 00005 to /opt/oracle/oradata/LCRSDEV/LCRS_TBS.dbf
channel ORA_DISK_1: reading from backup piece /opt/oracle/flash_recovery_area/LCRSDEV/backupset/2011_07_22/o1_mf_nnndf_TAG20110722T111922_72m8rc5x_.bkp
channel ORA_DISK_1: restored backup piece 1
piece handle=/opt/oracle/flash_recovery_area/LCRSDEV/backupset/2011_07_22/o1_mf_nnndf_TAG20110722T111922_72m8rc5x_.bkp tag=TAG20110722T111922
channel ORA_DISK_1: restore complete, elapsed time: 00:23:36
Finished restore at 02-AUG-11
RMAN> recover database until scn 95676700;
Starting recover at 02-AUG-11
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/02/2011 16:16:28
RMAN-20208: UNTIL CHANGE is before RESETLOGS change
RMAN> recover database;
Starting recover at 02-AUG-11
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 90 is already on disk as file /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_90_72ml85v3_.arc
archive log filename=/opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jr20qc_.arc thread=1 sequence=1
unable to find archive log
archive log thread=1 sequence=1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/02/2011 16:25:04
RMAN-06054: media recovery requesting unknown log: thread 1 seq 1 lowscn 95676701

Thanks for the reply Hemant. I have reset the database for the controlfile that I am using as backup and now I am not able to recover until the correct SCN. I am thinking that my recovery catalog is bad. If I mount with the current controlfile I have this list of incarnations:
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
*1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05*
*2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11*
*3 3 LCRSDEV 756543625 PARENT 92348137 18-JUL-11*
*4 4 LCRSDEV 756543625 PARENT 95654931 01-AUG-11*
*5 5 LCRSDEV 756543625 PARENT 95675699 01-AUG-11*
*6 6 LCRSDEV 756543625 PARENT 95676699 02-AUG-11*
*7 7 LCRSDEV 756543625 PARENT 95676700 02-AUG-11*
*8 8 LCRSDEV 756543625 PARENT 95676701 02-AUG-11*
*9 9 LCRSDEV 756543625 CURRENT 95676702 02-AUG-11*
However if I restore the controlfile to the earlier version I am getting the following output from the process:
RMAN> startup nomount;
connected to target database (not started)
Oracle instance started
Total System Global Area 3070230528 bytes
Fixed Size 2099424 bytes
Variable Size 301991712 bytes
Database Buffers 2751463424 bytes
Redo Buffers 14675968 bytes
RMAN> restore controlfile from '/opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_07_22/o1_mf_s_757164997_72m9rqw3_.bkp';
Starting restore at 03-AUG-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
output filename=/opt/oracle/oradata/LCRSDEV/control01.ctl
output filename=/opt/oracle/oradata/LCRSDEV/control02.ctl
output filename=/opt/oracle/oradata/LCRSDEV/control03.ctl
Finished restore at 03-AUG-11
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN> list incarnation of database;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05
2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11
3 3 LCRSDEV 756543625 CURRENT 92348137 18-JUL-11
RMAN> restore database until scn 92348137;
Starting restore at 03-AUG-11
Starting implicit crosscheck backup at 03-AUG-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
Crosschecked 1 objects
Finished implicit crosscheck backup at 03-AUG-11
Starting implicit crosscheck copy at 03-AUG-11
using channel ORA_DISK_1
Finished implicit crosscheck copy at 03-AUG-11
searching for all files in the recovery area
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_1_73g3hn6o_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_2_73g3hnxq_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_1_73g0rts6_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_134_72v9gv4s_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_138_72v9p4b4_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_120_72v8wwg0_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_121_72v8x5ty_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_131_72v9cnrv_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_139_72v9q5ok_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_137_72v9n4t5_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_136_72v9l88q_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_123_72v8ytm8_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_132_72v9dcxd_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_124_72v8zkg0_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_128_72v96qm1_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_135_72v9jqmx_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_129_72v98q3r_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_125_72v91g3b_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_118_72v8v8r4_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_127_72v9626w_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_130_72v9bqtb_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_141_72vncy6g_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_122_72v8ycd4_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_126_72v94cns_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_133_72v9fb17_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_140_72vn6wgo_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_119_72v8v9hf_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73j3wo01_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_2_73josgf1_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jr20qc_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_2_73jh223h_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73josflf_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jvqdqs_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_3_73josh91_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73j91rh9_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_91_72mqlnx9_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_111_72mrdr5m_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_96_72mqx958_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_114_72mrgsf9_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_94_72mqs6gj_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_102_72mr3893_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_99_72mr2h6c_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_104_72mr5hfm_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_109_72mrc83z_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_98_72mr080w_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_93_72mqq36m_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_97_72mqz0mm_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_116_72mrk268_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_101_72mr31yv_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_110_72mrddhg_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_95_72mqv3hp_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_105_72mr5vq4_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_115_72mrjd2s_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_106_72mr7hnt_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_100_72mr2qfc_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_112_72mrfc5j_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_107_72mr909t_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_103_72mr4pol_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_113_72mrfsb9_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_117_72mrl5mf_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_108_72mrb13l_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_90_72ml85v3_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_92_72mqnxz1_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_143_72y6ww71_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_144_72ybybps_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_142_72xt10j7_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_145_72yccy5z_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_01/o1_mf_s_758043324_73g3jfxx_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_01/o1_mf_s_758035850_73fw6vrc_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758133684_73jvr5px_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758127608_73jot9x0_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758109276_73j3xfom_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_07_22/o1_mf_s_757164997_72m9rqw3_.bkp
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 08/03/2011 12:53:19
RMAN-20208: UNTIL CHANGE is before RESETLOGS change
Edited by: K Doyle on Aug 3, 2011 10:22 AM

Exchange 2010 - Mail Database Recovery after Database Portability Applied

Background:
We had a city-wide power failure at Office A and as a result Exchange Server A (ES-A) was taken offline for an extended period of time. The last good backup of ES-A-DB was from the previous business day. The DR plan was enacted and the
ES-A mailbox database (ES-A-DB) was recovered to Exchange Server B (ES-B) as ES-B-DB2. Keeping in mind that a days worth of emails still reside on ES-A-DB.
Process:
I employed the database portability method when restoring the ES-A-DB to ES-B-DB2 at Office B. I rehomed the exchange users in active directory to now use ES-A-DB2. Users are working fine, activesync worked without issue. All is well.
I now face the situation where power has been restored to Office A and the server is available. I have NOT turned this server on yet as I am not sure what the net affect will be on ES-A and ES-A-DB.
The primary goal of the business is to recover the mail items from the missing day that was not backed up and recovered to ES-B-DB2. What would be the best way to do achieve this objective?
This is what I am thinking, though its all theoretical since I've never been in this situation.
- boot the Exchange Server with the network card disconnected
- Dismount ES-A-DB from ES-A
- Remove ES-A-DB from Exchange Org on ES-B
- Process logs and put the ES-A-DB in a Clean state
- mount as recovery database
- copy differential mail items to ES-B-DB2 mailboxes
Anyone have insight on this?
Thanks for your help in advance.

No need to dismount , remove from the org or boot the server w/o a NIC. The association between Exchange and the user is in AD and you already changed that when you set the new database with database portability.
I would just follow the instructions for restoring back to their current production mailboxes (DB2).
http://exchangeserverpro.com/restoring-mailbox-exchange-server-2013-recovery-database/
Try it with a sample mailbox or two and see how it handles the conflict resolution for duplicates.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Recovery of Database -- Restore from Cold Backup

Hi All
I was trying to understand the possible failures so as to enhance my recovery capabilities of Oracle database 10.2.0.4.
We take weekly hot back up of the database on every sunday including archive logs. Archive logs are also backed up when the log_archive_dest_1 disk space utilization grows beyond 80%. All the backup goes into an alterate disk made available on the host. The archive back up is triggered mostly twice a week, on one of the thursday/friday/Saturday depending on the redo generation in that week.
Imagine we have a failure on thursday leading me to restore the complete database from backup taken on the earlier sunday. I also realise there is 1 archive log from tuesday missing and its not backed up for sure. I restore from backup and try to recover. As all the archive logs are available since Sunday till the point of failure except for that one missing file from Tuesday, I want to recover the database until the point of failure although there is one log sequence missing in archive destination. how can I do that? Is it possible? Please advice.
I remember reading on net that recover database command can be hinted by an init parameter so as it does not check for sequece numbers and continue to apply archives (does not check sequence numbers) as they are available. But I am not able to recollect it exactly. while I was searching on net, I came to this forum hoping if some one knew it.
Let me know if you know how to go about this. Thanks in advance.
Sarat.

You cannot skip an archivelog (there is no init parameter to do so).
Think about this :
Imagine that there is one very long transaction. A transaction that deletes or updates 1 million records. With the redo logs being, say, 100MB each, the transaction spans multiple redo logs.
These redo logs are archived as, say, sequence #121 to 128.
Supposing that sequnece #123 is deleted by mistake.
Can you recover the database with sequence# 121, 122, 124-128 ? Can that transaction be consistent ?
OR think about this :
A redo log file is 99% full. A transaction for 1000 rows begins. All the redo entries for that transaction do not fit into that last 1%. The transaction spans into the next redo log file.
Can recovery be done with either of these missing ?
If you think through these scenarios, you will see that there will almost always be transactions spanning redo logs. That means, that you cannot skip redo logs during recovery.
Hemant K Chitale
http://hemantoracledba.blogspot.com

How to Perform Recovery in Database Control on tablespace?

Hi,
I am runnig 10gR2 on Windows XP SP 2.
I have taken backup of my nonsystem tablespace by using Database Control.
Now to test it I dropped tablespace.
Logged in as sys on Database Control:
Maintenance->Perform Recovery->
Object Level Recovery
Here in Object Type I choosed Tablespace from the dropdown
But what do I choose in Operation Type? There are three choises:
- Recover to current time or a previous point-in-time
- Restore tablespaces
- Recover from previously restored tablespaces
And as I said, I have taken backup of my whole tablespace...
Thanks

Hi Werner,
thanks again, but I still would like to perform backup of my tablespace.
Now I understood, that to drop a tablespace was an error. OK.
Next try:
Step 1:
CREATE TABLESPACE TEST_TS DATAFILE
'C:\ORACLE\ORADATA\ORCL\TEST_01.DBF' SIZE 1M AUTOEXTEND ON,
'C:\ORACLE\ORADATA\ORCL\TEST_02.DBF' SIZE 1M AUTOEXTEND ON;
Step 2:
CREATE TABLE TEST_TBL (
NAME VARCHAR2(10))
TABLESPACE TEST_TS;
Step 3:
INSERT INTO TEST_TBL VALUES('DB2');
Step 4:
COMMIT;
Step 5:
I have done backup of newly created tablespace TEST_TS via Database Control.
Step 6:
shutdown database;
Step 7:
I have manually renamed datafile TEST_01.DBF to TEST_01_.DBF
Step 8:
Now I have started database and have following entries in alert.log:
Errors in file c:\oracle\oracle\product\10.2.0\db_1\admin\orcl\bdump\orcl_dbw0_4124.trc:
ORA-01157: cannot identify/lock data file 6 - see DBWR trace file
ORA-01110: data file 6: 'C:\ORACLE\ORADATA\ORCL\TEST_01.DBF'
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-1157 signalled during: alter database open...
Which is correct. Oracle can not find the datafile I have renamed.
Step 9:
Now I thought I could be able to access Backup/Recovery Page in Database Control,
but all I can reach is 'Recovery Settings'
Do I need to go in open stage first to perfor recovery?
What needs to be done in Step 9? Do I have to drop my
ALTER DATABASE DATAFILE 'C:\ORACLE\ORADATA\ORCL\TEST_01.DBF' OFFLINE DROP;
alter database open;
Go to Database Control and try it out?
Thanks

Recovery of database with loss of archived logs

Hi,
I tried restoring the database using the standard practice, however, I am encountering errors. It looks like we are missing archive log files, but I am not sure. Could anyone provide more insight to this problem and how to recover the database?
Here are the steps we did.
SVRMGR> connect internal
Connected.
SVRMGR> startup
ORACLE instance started.
Total System Global Area 1117552144 bytes
Fixed Size 48656 bytes
Variable Size 291995648 bytes
Database Buffers 819200000 bytes
Redo Buffers 6307840 bytes
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SVRMGR> recover database using backup controlfile until cancel;
ORA-00279: change 663652622 generated at 02/13/02 06:20:02 needed for thread 1
ORA-00289: suggestion : /oraclesw8_redolog/ARCHIVE_CP/infr/infr_1_13598.dbf
ORA-00280: change 663652622 for thread 1 is in sequence #13598
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
Log applied.
ORA-00279: change 663654936 generated at 02/13/02 07:04:14 needed for thread 1
ORA-00289: suggestion : /oraclesw8_redolog/ARCHIVE_CP/infr/infr_1_13599.dbf
ORA-00280: change 663654936 for thread 1 is in sequence #13599
ORA-00278: log file '/oraclesw8_redolog/ARCHIVE_CP/infr/infr_1_13598.dbf' no longer needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
AUTO
ORA-00308: cannot open archived log '/oraclesw8_redolog/ARCHIVE_CP/infr/infr_1_13599.dbf'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01195: online backup of file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oraclesw8_data00/oradata/infr/infr_system_01.dbf'

Hi
It looks like you may have to manually apply the last redo log.
SVRMGR> SELECT member FROM v$log l, v$logfile f WHERE l.group# = f.group# AND l.status = 'CURRENT';
Note the path of this log file.
SVRMGR> Recover database until cancel
When you get the message that you mentioned -
Apply the log member from the select statement above. Give it
the full path as it appears on the select statement.
SVRMGR> Alter database open resetlogs;
The system should respond with "Statement processed".
Good Luck,
Bob

What is the steps for flash recovery of database

pls tell us what sre the steps for the flash recovery of the database.
how will we be do the auto recovery from flash recovery area......
rakesh

See
[url http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14220/backrec.htm#sthref2379]Flashback Concepts
[url http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_9011.htm#sthref6870]Flashback Database
[url http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_9012.htm#sthref6882]Flashback Table

Recovery the database

Hi,
I have 2 DBs primary and standby, and i did a full back up on Saturday for the primary DB, and now i am doing recovery for the DB in the standby ( rebuild the standby DB), everything is went smooth but not i have this error which i dont know if it is good or bad
ORA-00279: change 6555156022 generated at 07/14/2008 12:35:16 needed for thread
1
ORA-00289: suggestion :
/data/oradata/xxxx/archive/xxxx_1_8766_657631822.arc
ORA-00280: change 6555156022 for thread 1 is in sequence #8766
ORA-00278: log file
'/data/oradata/xxxx/archive/xxxx_1_8765_657631822.arc' no longer needed
for this recovery
should i become worry or not, and if should i should become worry, what should i do?
byw, it is stilling running right now
my DB is oracle 10.1.0.5.0
OS is linux
Thank you

Always post your query in lower case.
Look at the metalink Note: 419137.1 -- Restoring Database Using rman On a Different Node with Different Backup and Database Directory Strutures
With best regards
Shan

Litigation Hold, Single Item Recovery, & Mailbox Database Deleted Items Retention

Hello
I'm looking for a simple explanation of how the three features mentioned in the subject line interact and affect one another.
Specifically, I'm after the answer to the following question:
If a users mailbox has litigation hold enabled, and the mailbox database it lives on has a deleted items retention value of 365 days, does that users "Recoverable Items" get deleted after 365 days, or does litigation hold, as I supspect bypass the retention
value?
If Single Item Recovery is enabled for said user as well, and added to the scenario above - how does this affect the retention of the deleted items?
I cannot find a definitive article that describes mailbox database deleted items retention, litigation hold and single item recovery and their behaviours when used together.
Regards
Matt
Matt

Hello again,
Just wanted to open this thread up again, and gain some further clarification, specifically on the behaviour of items in "Recoverable Items\ Deletions" folder.
In the following scenario how will items be processed:
-SingleItemRecoveryEnabled -True
-LitigationHoldEnabled - True
-UseDatabaseRetentionDefaults -True
-Items in the Deletions folder have passed the retention value date as specified on the database.
Given the parameters above, when the I run the Managed Folder Assistant against a mailbox, I'm expecting to see the items in the Deletions folder move, and be placed in Purges folder.
This is not happening however, items are only removed from the Deletions folder when LitigationHold is disabled. Then, items bypass the Purges folder altogether and are removed from the mailbox/database altogether.
I referred to the article below for clarification:
http://blogs.technet.com/b/exchange/archive/2009/09/25/3408389.aspx#_Short-Term_Preservation_of
"...the message was not purged from the mailbox store. Instead the message was moved from the Recoverable
Items\Deletions folder to the Recoverable Items\Purges folder. All store hard-deleted items end up in this folder when single item recovery is enabled. The Recoverable Items\Purges folder is not visible to the end user, meaning that they do not see data retained
in this folder in the Recover Deleted Items tool.
When the message deletion timestamp has exceeded the deleted item retention window, Records Management will purge the item."
Can anyone assist in explaining the behaviour I'm observing?
I'm in a transition period where by our organisation has been journalling all
email to an Online service since 2008 and this service will continue to be used solely as our archiving and compliance mechanism.
Since Exchange 2010 was adopted by the company around 18 months ago, the previous mail administrator had litigation hold enabled on all mailboxes
from the outset, so I'm in the position now where by I have two retention methods running side by side.
Long story short, the online archiving will be used moving forward and litigation hold will be disabled within Exchange.
What I want to do is transition from long term data
preservation inside Exchange, to short term preservation - hence the reason for now enabling SIR.
Currently I have mailboxes with 10's of GB's of mail sat in the "Recoverable Items\Deletions" folder, and very little, if anything in some
cases, in the respective "Purges" folder.....
Can anyone advise on a "correct" procedure for making this transition?
Regards
Matt
Matt

Recovery catalog database

Hi members,
Can we create the recovery catalon on the same server as standby database? I personally don't think so, but your opinions will be appreciated. Is a separate server necessary for R.C. database?
Thanks.

abctoz wrote:
Hi members,
Can we create the recovery catalon on the same server as standby database? I personally don't think so, but your opinions will be appreciated. Is a separate server necessary for R.C. database?
Thanks.Not really 'mandatory" but "advisable", yes very much! It surely is just a schema and not really a full blown database but its still better to have it on other machine from that which stores teh target db.
HTH
Aman....

Recovery of database

Similar Messages

Maybe you are looking for