Repair / recover database that is unable to be attached

Hi,
I had some hardware problems on the database server where I'm working. After restarting the server, I can't attach any database to an SQL Instance. I'm not sure what to do because without being able to attach it, I can't dbcc it. Is there any SQL Server
native tool or command that can help? What options do I have? (error message when I try to attach is bellow).
Thank you
TITLE: Microsoft SQL Server Management Studio
Attach database failed for Server 'LT105996'. (Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.0.4064.0+((Katmai_SP2_GDR).110225-1353+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attach+database+Server&LinkId=20476
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Could not redo log record (585:2858:3), for transaction ID (0:480869), on page (1:302), database 'HYP_PLN' (database ID 9). Page: LSN = (422:770:2), type = 1. Log: OpCode = 4, context 2, PrevPageLSN: (585:2800:3). Restore from a backup of the database, or
repair the database.
During redoing of a logged operation in database 'HYP_PLN', an error occurred at log record ID (585:2858:3). Typically, the specific failure is previously logged as an error in the Windows Event Log service. Restore the database from a full backup, or repair
the database.
Could not open new database 'HYP_PLN'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 3456)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=3456&LinkId=20476
BUTTONS:
OK

Hello Samuel, Yes, there are many tools available in the market that claim to recover mdf content. I would like to recommend to a Microsoft Golden Satisfy Partner's Product
Stellar Phoenix SQL Recovery software. It shows the preview of corrupt database. To save the corrupt database, you will have to buy the software. All the related information is available @
http://www.stellarsqldatabaserecovery.com/
Read my blog (Blog)
Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you

Similar Messages

After a recover database, how can I find the time of the last transaction?

After doing a restore and recovery. Is there something in the data dictionary that I can query to find the time of the last applied transaction that took place during the recover process?
restore database ;
recover database ;
For example, if I restored from a full backup on 8/3/2008 with archive redologs, I know my last restored transaction is from sometime on that day, but I'd like a way to know the hour:minute:second of the last transaction included in the backup and redologs that was applied to my restore. Is that possible?
The recover database applies all available redo logs for that day, but I want to know if that includes transaction up to 6PM, or 11:50PM, etc?
Thanks,
Jason

If you did only a "recover database" that would have been a Complete Recovery to the last transaction -- ie the point when the database was shutdown.
For an Incomplete Recovery, you would have to note the Sequence#, SCN or Timestamp of the recovery point.

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

"recover database until cancel" asks for archive log file that do not exist

Hello,
Oracle Release : Oracle 10.2.0.2.0
Last week we performed, a restore and then an Oracle recovery using the recover database until cancel command. (we didn't use backup control files) .It worked fine and we able to restart the SAP instances. However, I still have questions about Oracle behaviour using this command.
First we restored, an online backup.
We tried to restart the database, but got ORA-01113,ORA-01110 errors :
sr3usr.data1 needed media recovery.
Then we performed the recovery :
According Oracel documentation, "recover database until cancel recovery" proceeds by prompting you with the suggested filenames of archived redo log files.
The probleme is it prompts for archive log file that do not exist.
As you can see below, it asked for SMAarch1_10420_610186861.dbf that has never been created. Therefore, I cancelled manually the recovery, and restarted the database. We never got the message "media recovery complete"
ORA-279 signalled during: ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10417_61018686
Fri Sep 7 14:09:45 2007
ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10418_610186861.dbf'
Fri Sep 7 14:09:45 2007
Media Recovery Log /oracle/SMA/oraarch/SMAarch1_10418_610186861.dbf
ORA-279 signalled during: ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10418_61018686
Fri Sep 7 14:10:03 2007
ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10419_610186861.dbf'
Fri Sep 7 14:10:03 2007
Media Recovery Log /oracle/SMA/oraarch/SMAarch1_10419_610186861.dbf
ORA-279 signalled during: ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10419_61018686
Fri Sep 7 14:10:13 2007
ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10420_610186861.dbf'
Fri Sep 7 14:10:13 2007
Media Recovery Log /oracle/SMA/oraarch/SMAarch1_10420_610186861.dbf
Errors with log /oracle/SMA/oraarch/SMAarch1_10420_610186861.dbf
ORA-308 signalled during: ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10420_61018686
Fri Sep 7 14:15:19 2007
ALTER DATABASE RECOVER CANCEL
Fri Sep 7 14:15:20 2007
ORA-1013 signalled during: ALTER DATABASE RECOVER CANCEL ...
Fri Sep 7 14:15:40 2007
Shutting down instance: further logons disabled
When restaring the database we could see that, a recovery of online redo log has been performed automatically, is it the normal behaviour of a recovery using "recover database until cancel" command ?
Started redo application at
Thread 1: logseq 10416, block 482
Fri Sep 7 14:24:55 2007
Recovery of Online Redo Log: Thread 1 Group 4 Seq 10416 Reading mem 0
Mem# 0 errs 0: /oracle/SMA/origlogB/log_g14m1.dbf
Mem# 1 errs 0: /oracle/SMA/mirrlogB/log_g14m2.dbf
Fri Sep 7 14:24:55 2007
Completed redo application
Fri Sep 7 14:24:55 2007
Completed crash recovery at
Thread 1: logseq 10416, block 525, scn 105140074
0 data blocks read, 0 data blocks written, 43 redo blocks read
Thank you very much for your help.
Frod.

Hi,
Let me answer your query.
=======================
Your question: While performing the recovery, is it possible to locate which online redolog is needed, and then to apply the changes in these logs
1.   When you have current controlfile and need complete data (no data loss),
      then do not go for until cancel recovery.
2.   Oracle will apply all the redologs (including current redolog) while recovery
     process is    on.
3. During the recovery you need to have all the redologs which are listed in the    view    V$RECOVERY_LOG and all the unarchived and current redolog. By querying V$RECOVERY_LOG you    can find out about the redologs required.
4. If the required sequence is not there in the archive destination, and if recovery process    asks for that sequence you can query V$LOG to see whether requested sequence is part of the    online redologs. If yes you can mention the path of the online redolog to complete the recovery.
Hope this information helps.
Regards,
Madhukar

Recover Database without backup

Hi Joel,
I have read most of your postings regarding database recovery, but still encounter problems.
The background is: Our NT server was crashed last weekend, due to harddisk failure. We are able to retrieve back all the datafile, control file, everything in tact. But after recovery, the OS fails to recognize the ORacle and require reinstallation. We don't know how to re-associate this new instance of Oracle with the old databases that we have created.
I did create a new DB in the new instance, copy back the datafiles, control files to replace it, and run the recreate control file command that you have suggested. At the very final step, when doing recovery, it shows this message:
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: 'D:\ORACLE\ORADATA\ELOS\SYSTEM01.DBF'
---tried to do a recovery as suggested:
SQL> recover automatic database;
ORA-00279: change 3329263 generated at 04/19/2004 12:00:26 needed for thread 1
ORA-00289: suggestion : D:\ORACLE\ORA90\RDBMS\ARC00061.001
ORA-00280: change 3329263 for thread 1 is in sequence #61
ORA-00278: log file 'D:\ORACLE\ORA90\RDBMS\ARC00061.001' no longer needed for
this recovery
ORA-00308: cannot open archived log 'D:\ORACLE\ORA90\RDBMS\ARC00061.001'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
---Tried a search on the machine, but failed to find such file.
How can I proceed from here?
Thanks and regards,
Suhandy

if the datafile does not contains tables that are needed for some application , or not belong to system,sysaux tablespace , offline datafile can be some solution.
To recover a datafile without backup you need alll the archives from the date that the datafile is created.
Please make a procedure for backup
A sample backup script can be founded http://mikegeorgiou.blogspot.com/2007/04/user-manage-backup-9i.html

Recover database with missing archivelog...

Oracle10gR2 RHEL 4
Hi,
I am having a problem. I'm trying to recover my database to an previous point in time but the archive logs that I need were accidentally removed. Is there anyway I can restore it to a previous point in time? None of the SCN's are working no matter how far I go back (note: I can created the database lastweek so it can't go further than that).
Thanks
RMAN> recover database until time "to_date('2008-04-08:17:47:00','YYYY-MM-DD:HH24:MI:SS')";
Starting recover at 14-APR-08
using channel ORA_DISK_1
starting media recovery
archive log thread 2 sequence 4 is already on disk as file +FLASH1/vmracdev/archivelog/2008_04_08/thread_2_seq_4.290.651538751
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 04/14/2008 16:11:11
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 9 lowscn 153309685 found to restore
RMAN> recover database until SCN 153330712;
Starting recover at 14-APR-08
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 04/14/2008 16:12:40
RMAN-06556: datafile 1 must be restored from backup older than scn 153330712
RMAN> recover database until SCN 153266607;
Starting recover at 14-APR-08
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 04/14/2008 16:15:01
RMAN-06556: datafile 1 must be restored from backup older than scn 153266607

Ok, I am trying that but I get the following error:
RMAN> recover database until SCN 153219977;
Starting recover at 17-APR-08
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 04/17/2008 13:33:00
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20208: UNTIL CHANGE is before RESETLOGS change
And this is the latest SCN I have.
Thanks

Recover database using RMAN

Hi, I hope someone can explain to me what happened with my recovery process. I am running Oracle 8i.
I dropped a tablespace on 11/22 @ 09:11. I first tried to do a full restore without restoring the control file (I was told that I should keep the current control file in order to apply any logs).
RMAN> run {
2> allocate channel d1 type disk;
3> set limit channel d1 kbytes 100000;
4> allocate channel d2 type disk;
5> set limit channel d2 kbytes 100000;
6> allocate channel d3 type disk;
7> set limit channel d3 kbytes 100000;
8> restore database;
9> alter database mount;
10> recover database;
11> alter database open resetlogs;
12> release channel d1;
13> release channel d2;
14> release channel d3;
15> }
I received the following error:
RMAN-03002: failure during compilation of command
RMAN-03013: command type: recover
RMAN-03006: non-retryable error occurred during execution of command: recover(1)
RMAN-07004: unhandled exception during command execution on channel default
RMAN-10035: exception raised in RPC: ORA-19654: must use backup controlfile to switch file incarnations
RMAN-10031: ORA-19654 occurred during call to DBMS_BACKUP_RESTORE.SWITCHTOCOPY
I could not open the database, next I did a point in time restore with the control file:
RMAN> run {
2> allocate channel d1 type disk;
3> set limit channel d1 kbytes 100000;
4> allocate channel d2 type disk;
5> set limit channel d2 kbytes 100000;
6> allocate channel d3 type disk;
7> set limit channel d3 kbytes 100000;
8> restore controlfile;
9> alter database mount;
10> set until time = '2004-11-22:09:00:00';
11> restore database;
12> recover database;
13> release channel d1;
14> release channel d2;
15> release channel d3;
16> }
I received the following error:
RMAN-03002: failure during compilation of command
RMAN-03013: command type: recover
RMAN-03002: failure during compilation of command
RMAN-03013: command type: recover(4)
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 8 scn 263762 found to restore
I could not open the database, I received the following error when I tried to open with resetlogs:
RMAN-06003 .....:ORA-01113 file 1 needs media recovery
'/d01/oradata/dr_cms/system01.dbf'
I was done for the day and the system was shutdown, including the AIX server. When I started everything this morning, I did an 'alter database open resetlogs' and the database opened and the tablespace that I dropped was back!!!
Does this make sense? Can anyone tell me what happened?!
Why should a reboot of the system cause the database to open?

No, you do not have to reboot the OS to get start the database. To know what exactly passed it was needed to see at the OS level the datafiles found in disk during the several intents you did for recover the database.
Joel PÃ©rez
http://www.oracle.com/technology/experts

Problem in recovering database

I Have Oracle Database 10g (10.2.0.1.0) on Windows Server 2003
I have taken full hot RMAN backup of database.
I have copied the backup files from flash recovery area.
I have one other Machine having windows server 2003 And Oracle 10g Same version. I have copied the backup files from first machine to Flash Recovery Area folder on second machine.
Now i am trying to restore the database of first machine to second machine.
1. I have created a new instance on second machice with same name as in fiirst machine.
2. I have created one ORA password file as well.
3. SET ORACLE_SID=<name of DB as it was in first machine>
4. RMAN TARGET sys/<password given in newly ORA pwd file>@<DB name> nocatalog
5. SET DBID=<dbid of old database>
6. STARTUP NOMOUNT FORCE
7. RESTORE SPFILE TO PFILE '<path of new pfile>' from '<path where backup files are there>';
8. CREATE UDUMP,BDUMP,CDUMP,PFILE,ORADATA FOLDERS where required;
9. SHUTDOWN IMMEDIATE;
10. STARTUP NOMOUNT PFILE='<path of newly created pfile>';
11 RESTORE CONTROLFILE FROM '<path of backup files>';
12. ALTER DATABASE MOUNT;
Everything work fine till here
Now my next step was
13. RESTORE DATABASE;
Then it gives error like:-
RMAN> restore database;
Starting restore at 20-NOV-08
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=375 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 11/20/2008 21:00:54
RMAN-06026: some targets not found - aborting 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
Firstly i copied backup files to flash recovery area, then i copied files to 'D:\oracle\product\10.2.0\db_1\database' as well. Because i have done it in 9i, in 9i i copied the backup files to this backup folder then while doing restore RMAN succesfully takes file from this folder & restores the database. but in 10g RMAN is not recognising the path of backup. How this problem can be solved? Or is this some different problem which i am not getting?
Waiting for reply..

Hi ORADBA,
Thanks for your response. Your solution worked. Actually there was a difference the Oracle installation on server from which i was taking backup is on E drive.
And the server on which i am trying to restore that database has Oracle installation files on D drive. That's why this confusion occurred.
But i have one query again. I am not able to recover my database fully.
Firstly i typed restore database command that worked. Thereafter i tried recover database command. that commant resulted in an error as given below. Than i typed command archive log list on SQL promt, from there i found the information of latest archive log. then i tried recover database until logseq 484 thread 1. That also didn't work. In the same situation i tried to open database i was able to open database using command alter database open resetlogs. I suppose i was not able to recover the database fully. Hi can i recover my database fully?
waiting for reply. Thanks in advance.
RMAN> recover database;
Starting recover at 24-NOV-08
using channel ORA_DISK_1
channel ORA_DISK_1: starting incremental datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
destination for restore of datafile 00001: E:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\SYSTEM01.DBF
destination for restore of datafile 00002: E:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\UNDOTBS01.DBF
destination for restore of datafile 00003: E:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\SYSAUX01.DBF
destination for restore of datafile 00004: E:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\USERS01.DBF
channel ORA_DISK_1: reading from backup piece E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\BACKUPSET\2008_11_20\O1
MFNNND1_BACKUP_TESTDB_L_1_4LB0PZXS_.BKP*
channel ORA_DISK_1: restored backup piece 1
piece handle=E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\BACKUPSET\2008_11_20\O1_MF_NNND1_BACKUP_TESTDB_L_1_4L
B0PZXS_.BKP tag=BACKUP_TESTDB_L_112008115509
channel ORA_DISK_1: restore complete, elapsed time: 00:00:15
starting media recovery
unable to find archive log
archive log thread=1 sequence=484
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 11/24/2008 19:47:07
RMAN-06054: media recovery requesting unknown log: thread 1 seq 484 lowscn 11013224
RMAN> recover database until logseq 484;
Starting recover at 24-NOV-08
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 11/24/2008 19:48:07
RMAN-06556: datafile 1 must be restored from backup older than scn 11009149
RMAN> recover database until logseq 484 thread 1;
Starting recover at 24-NOV-08
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 11/24/2008 19:48:20
RMAN-06556: datafile 1 must be restored from backup older than scn 11009149
RMAN> recover database until logseq 483 thread 1;
Starting recover at 24-NOV-08
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 11/24/2008 19:48:58
RMAN-06556: datafile 1 must be restored from backup older than scn 10973094
RMAN> recover database until logseq 482 thread 1;
Starting recover at 24-NOV-08
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 11/24/2008 19:49:06
RMAN-06556: datafile 1 must be restored from backup older than scn 10952975
RMAN> alter database open;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 11/24/2008 19:49:21
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
RMAN> alter database open resetlogs
*2> ;*
Edited by: user648257 on Nov 24, 2008 6:48 AM

Recover database

10.2.0.4
linux hp-aux
Hi all;
I need to recover a database to 12 days back
the restore was fine
restore database until tim 'SYSDATE -12';
But now I want to recover it, with no luck:
RMAN> recover database until time 'SYSDATE -12';
Starting recover at 28-MAR-10
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=537 devtype=DISK
starting media recovery
channel ORA_DISK_1: starting archive log restore to default destination
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=51996
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=51997
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=51998
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=51999
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=52000
channel ORA_DISK_1: reading from backup piece /backup/rman/cds/cds_rman_arch_ctl8had5_1_1
ORA-19870: error reading backup piece /backup/rman/cds/cds_rman_arch_ctl8had5_1_1
ORA-19504: failed to create file "/archivelog_51997_1_598154815.arc"
ORA-27040: file create error, unable to create file
Linux Error: 13: Permission denied
Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/u02/oradata/cds/system01.dbf'
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 03/28/2010 21:21:34
RMAN-20506: no backup of archivelog found
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 52000 lowscn 5982565411376 found to restore
RMAN-06025: no backup of log thread 1 seq 51999 lowscn 5982565308766 found to restore
RMAN-06025: no backup of log thread 1 seq 51998 lowscn 5982565168847 found to restore
RMAN-06025: no backup of log thread 1 seq 51997 lowscn 5982565030845 found to restore
RMAN-06025: no backup of log thread 1 seq 51996 lowscn 5982564789686 found to restore
then I try:
RMAN> recover database until sequence 52047;
Starting recover at 28-MAR-10
using channel ORA_DISK_1
starting media recovery
channel ORA_DISK_1: starting archive log restore to default destination
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=51996
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=51997
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=51998
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=51999
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=52000
channel ORA_DISK_1: reading from backup piece /backup/rman/cds/cds_rman_arch_ctl8had5_1_1
ORA-19870: error reading backup piece /backup/rman/cds/cds_rman_arch_ctl8had5_1_1
ORA-19504: failed to create file "/archivelog_51997_1_598154815.arc"
ORA-27040: file create error, unable to create file
Linux Error: 13: Permission denied
Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/u02/oradata/cds/system01.dbf'
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 03/28/2010 21:25:29
RMAN-20506: no backup of archivelog found
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 52000 lowscn 5982565411376 found to restore
RMAN-06025: no backup of log thread 1 seq 51999 lowscn 5982565308766 found to restore
RMAN-06025: no backup of log thread 1 seq 51998 lowscn 5982565168847 found to restore
RMAN-06025: no backup of log thread 1 seq 51997 lowscn 5982565030845 found to restore
RMAN-06025: no backup of log thread 1 seq 51996 lowscn 5982564789686 found to restore
again that same backupset, which is for the 14th of March, and I want to recover to the 15th!
Can i delete that backupset that is ginving me the problem, or is it something els??
please I need help

Hello,
Each time you got the following error:
ORA-27040: file create error, unable to create file
Linux Error: 13: Permission deniedDo you have the correct right on the directories ?
Hope this help.
Best regards,
Jean-Valentin

Recover database but don't have archive log file

Hi
I use old backup set in tape and restore all datafile completed but I cannot recover that show below errror in RMAN
RMAN> recover database;
Starting recover at 08-SEP-09
using channel ORA_DISK_1
starting media recovery
unable to find archive log
archive log thread=1 sequence=29166
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 09/08/2009 21:49:36
RMAN-06054: media recovery requesting unknown log: thread 1 seq 29166 lowscn 1648727512
But in backup set and include archive log already that don't have seq 29166 that have last seg is 29165 when I tyr recover in sqlplus that show below error
SQL> recover database using backup controlfile;
ORA-00279: change 1648727512 generated at 09/05/2009 00:02:07 needed for thread
1
ORA-00289: suggestion : /oradata/archive/hrprd/1_29166_671345511.arc
ORA-00280: change 1648727512 for thread 1 is in sequence #29166
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log
'/oradata/archive/hrprd/1_29166_671345511.arc'
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 3
And I tried to open with reset log that show below error
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: '/oradata/data/hrprd/system01.dbf'
How can I do to open database?
Taohiko.

taohiko wrote:
Hi Werner
I tried and show below error
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 1648727512 generated at 09/05/2009 00:02:07 needed for thread
1
ORA-00289: suggestion : /oradata/archive/hrprd/1_29166_671345511.arc
ORA-00280: change 1648727512 for thread 1 is in sequence #29166
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
CANCEL
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/oradata/data/hrprd/system01.dbf'
ORA-01112: media recovery not started
How to do next step?
TaohikoHi Taohiko
Have you made backup of all archived redo log files? If so, why this one was disappeared?
Have you applied all archived redo log files before that required archived redo log file?
Please try to recover the database using the following command:
RMAN> RESTORE DATABASE;
RMAN> RECOVER DATABASE UNTIL SEQUENCE 29166;
RMAN>ALTER DATABASE OPEN RESETLOGS;

Check / Repair iPhoto Database - choose which options?

Hi!
I have read several tips regarding the "Command+Option Click" on the iPhoto Icon and check / repair the iPhoto database. Can someone explain all the 6 options, I can choose in the dialog box?
#1 - Repair the iPhoto Library Database
Where will I see the results of this scan/repair? I have tried it but I didn't see any results (scan finished - no errors -or- xx errors corrected).
#2 - Rebuild the database from automatic backup?
What's that for an automatic backup? Is this the timemachine backup? or is it an iPhoto internal database backup?
#3 and #4 - Rebuild small/all tumbnails
What's the difference? Why should this be necessary?
#5 recover orphaned photos
Are orphaned photos photos, which does exist in the library, but has no thumbnail/event/...?
Or are these photos which has a thumbnail and are in an event, but the full image is missing?
#6 Repair iPhoto Library file permissions
I think, it is easy and recommended to always check this, or?
I have also read the tip "delete iPhoto's cache files, located in ....... caches/com.apple.iPhoto folder".
Are these files the thumbnails from option #3 or #4? or is this something different?
I actually don't have a problem, but iPhoto is extremely slow and I want to know, if everything is ok with the library.
BTW - iPhoto '11 is great! But unfortunately - slow..... (13" 2.53GHz MacBookPro, 4GB RAM bought November 2009 - is this too old for iPhoto 11?)
best regards
michael

#1 - Repair the iPhoto Library Database
iPhoto attempts to repair the database. There is no report.
#2 - Rebuild the database from automatic backup?
It's an internal iPhoto database back up.
#3 and #4 - Rebuild small/all tumbnails
Because some folks lose their thumbnails, some folks have thumbnails that don't match the photo.
#5 recover orphaned photos
iPhoto will examine the library folder for any photos that are not currently being displayed in Albums or Events in the iPhoto source list. It may find some, it may not.
#6 Repair iPhoto Library file permissions
No need to do this unless you have a permissions issue.
I have also read the tip "delete iPhoto's cache files, located in ....... caches/com.apple.iPhoto folder".
No this is a different cache.
Regards
TD

Aperture wont open and says "repairing library database" even when 100% complete it still wont open

my aperture won't open and says "repairing library database" even when it gets up to 100% complete it just suts there frozen and won't open to the aperture screen

How many Images? How much storage space does the Library occupy? Do you have plenty of free space on your system drive?
Ignore the progress bar — it's often stuck, and therefore unreliable.
Ignore Activity Monitor reporting Aperture "Not Responding". This is, imho, a bug Apple should have squashed years ago.
Repairing (or doing any operations an entire Library) a large Library can take hours or days. You did not report what you did to get past 79% — I'm going to guess you Force-quit Aperture. Force-quitting any database is always a bad idea and should only be done as a last resort. Each time you force quit, you are likely adding to your problem.
Restart the rebuild, and let it run, unmolested, for at least 40 hours. IME, at some point the progress bar with jump to 99%, then 100%, and then stay there for perhaps a few more hours, and then it finishes.
I have _never_ had a repair or a rebuild (I have not had to do many rebuilds) _not_ finish. One took about 82 hours, but it finished.
If your Library is small — say, fewer than 100,000 Images _and_ smaller than 100 GB — and you're seeing these very long rebuild times, you likely have an actual problem — but the only way I know to find out is to let the rebuild continue. (I don't store any but small video in Aperture, and very few of them, so my numbers may not correspond to Libraries that store videos.)
Did you notice any other problems before Aperture itself recommended rebuilding?
In short: let it run unmolested.

HT4790 My Mac OS Lion 10.7 FileVaulted HD does not boot, prohibitory sign, stop sign appears some minutes after boot starts. Disk Utility repair shows four error messages: Unable to bootstrap transaction group 2517: inconsistent crosscheck (the same with

My Mac OS Lion 10.7 FileVaulted HD does not boot, prohibitory sign, stop sign appears some minutes after boot starts. Disk Utility repair shows four error messages:
Unable to bootstrap transaction group 2517: inconsistent crosscheck
No valid commit checkpoint found
The volume xxxxxxxxxxxxxx(here it shows physical volume number) was found corrupt and can not be repaired.
Problems were encountered during repair of the partition map
Error: Storage system verify or repair failed.
(the same with 2518, 2519 and 2520 transaction group)
I suppose it is serious bug in Mac OS Lion managing FileVault and wonder what the help could be?

Most likely culprit is your Lacie drives which are notorious for flaky power supplies which cause just the sort of erratic behaviour that you describe. Have had similar issues myself. Lacie has been good about replacing my power converter-- twice. If you have seven of them, good luck finding the bad one or more. Like I said, the behaviour is erratic. Sometimes it'll work sometimes not. I can't comment on Samsung drives because I've never used them and have never heard anything about them. Same with Softraid. Why not just use Disk Utility. Sounds like you're ready for an external hardware raid. This will be much faster, much more reliable, and may even be cheaper than seven firewire drives. Check out G Tech, and Maxx Digital for starters.
Best of luck
Terry

What order are Archive logs restored in when RMAN recover database issued

Ok, you have a run block that has restored your level-0 RMAN backup.
Your base datafiles are down on disc.
You are about to start recovery to point in time, lets say until this morning at 07:00am.
run { set until time "TO_DATE('2010/06/08_07:00:00','YYYY/MM/DD_HH24:MI:SS')";
allocate channel d1 type disk;
allocate channel d2 type disk;
allocate channel d3 type disk;
allocate channel d4 type disk;
recover database;
So the above runs, it analyses the earlies SCN required for recovery, checks for incremental backups (none here), works out the archivelog range
required and starts to restore the archive logs. All as expected and works.
My question: Is there a particular order that RMAN will restore the archive logs and is the restore / recover process implemented as per the run block.
i.e Will all required archive logs based on the run block be restored and then the database recovered forward. Or is there something in RMAN that says restore these archive logs, ok now roll forwards, restore some more.
When we were doing this the order of the archive logs coming back seemed to be random but obviously constrained by the run block. Is this an area we need to tune to get recoveries faster for situations where incrementals are not available?
Any inputs on experience welcome. I am now drilling into the documentation for any references there.
Thanks

Hi there, thanks for the response I checked this and here are the numbers / time stamps on an example:
This is from interpreting the list backup of archivelog commands.
Backupset = 122672
==============
Archive log sequence 120688 low time: 25th May 15:53:07 next time: 25th May 15:57:54
Piece1 pieceNumber=123368 9th June 04:10:38 <-- catalogued by us.
Piece2 pieceNumber=122673 25th May 16:05:18 <-- Original backup on production.
Backupset = 122677
==============
Archive log sequence 120683 low time: 25th May 15:27:50 Next time 25th May 15:32:24 <-- lower sequence number restored after above.
Piece1 PieceNumber=123372 9th June 04:11:34 <-- Catalogued by us.
Piece2 PieceNumber=122678 25th May 16:08:45 <-- Orignial backup on Production.
So the above would show that if catalogue command you could influence the Piece numbering. Therefore the restore order if like you say piece number is the key. I will need to review production as to why they were backed up in different order completed on production. Would think they would use the backupset numbering and then piece within the set / availability.
Question: You mention archive logs are restored and applied and deleted in batches if the volume of archivelogs is large enough to be spread over multiple backup sets. What determines the batches in terms of size / number?
Thanks for inputs. Answers some questions.

Can I use RECOVER database command evenif there is no MEDIA FAILURE? [b]Urg

I need an urgent help from all the big guns out there?
My database is up and running, but still I want to recover the deletion of data that has been done on FRIDAY/SATURDAY/SUNDAY/MONDAY/TUESDAY/WEDNESDAY in other words I want the FRIDAY's state of the database.
Can I do it using the
"RECOVER DATABASE UNTIL TIME '2005-28-06-00:00:00' command?
Please guide me.
Thanks in advance

Hi,
i assume you running your database in archive log mode and using rman to accomplish you task.i would say that you can recover your database even if there is no media faliur occurs,no doubt you can use this.i think you want to recover your database to the fridays state prior to the table deletion,so you get the tables back in your database.so what's a problem execut following.
run {
SET UNTIL TIME "TO_DATE('apr 03 2005 01:17:13','MON DD YYYY HH24:MI:SS')";
restore database ;
recover database ;
asuume in this example that you want to recover your database up to date aprail 3 and prior to 01pm time.
change the code according to your requirement.
thanks.

Repair / recover database that is unable to be attached

Similar Messages

Maybe you are looking for