Backup & Recovery :: Oracle11gR2 Not Allow To Open Database After Complete Recovery?
Feb 24, 2012
My database is in NOARCHIVELOG mode.I took whole DB backup ( cold).Then just after half an hour I ran following script.
RMAN> RUN { RESTORE DATABASE;RECOVER DATABASE;alter database open;}
Starting restore at 24-FEB-12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=133 device type=DISK
channel ORA_DISK_1: starting datafile backup set restore
[code]...
Starting recover at 24-FEB-12
using channel ORA_DISK_1
starting media recovery archived log for thread 1 with sequence 2 is already on disk as file /u01/app/oracle/oradata/PROD/redo02.log
archived log file name=/u01/app/oracle/oradata/PROD/redo02.log thread=1 sequence=2
media recovery complete, elapsed time: 00:00:01
[code]...
Why do I need to specify an option at the first place?As my redo is intact, it is not incomplete recovery and, I do not want to generate new incarnation of my database.Why oracle simply not opening my database?
SQL> alter database mount; Database altered. SQL> alter database open resetlogs; alter database open resetlogs * ERROR at line 1: ORA-01139: RESETLOGS option only valid after an incomplete database recovery
i have found an issue regarding log archiving on dest1. yesterday one sequence number 76871 not archive to dest1.alert logfile content as follow. i configure standby and ship archive manually with window copy command. i need this archive to complete recovery on standby database.
Mon Oct 21 09:29:28 2013 ARC2: Completed archiving log# 3 seq# 76869 Mon Oct 21 09:39:28 2013 Thread 1 advanced to log sequence 76871 Current log# 2 seq# 76871 mem# 0: D:ORACLEORADATAORC1REDO02.LOG [code]....
what are the minimum files which are required to open the db ? take it as this
I have oracle installed in c drive. I have placed 3 datafile related to one tablespace say test: two in D and one in E. I have place 3 datafile related to tablespace say orcl : two in D and one in E.
my undo is in E scenario is that my E drive crashed . db is in no archive mode . no backup is there. to be more worst db shuts down abnormally. I want my db open with data of c drive and D drive.
We are trying to restore a database on the different server using RAM incremental level 0 and 1 backups. We have weekly Incremental level 0 backups along with incremental backups on daily basis. During recovery of Incremental level 0 backup, RMAN is expecting/looking for Incremental Level 0 backup of prior week as well. Is this the usual process for RMAN to look for prior level 0 backup though we need to restore from the current level 0 backup and roll forward by a week with subsequent Level 1 backup.?
We intend to restore from the Level 0 of 1/16 and roll forward with daily incrementals till 1/22. RMAN is expecting level 0 backupsets from 1/9 backup as well and keep failing since those backups are not available. quick inputs since we are in middle of recovery and trying to resolve if this is even doable.
I have problem on using "delete obsolete" in RMAN.
First, let describe my backup configuration.
1. Full backup every Monday (17-Oct, 10-Oct, 3-Oct, 26-Sep) 2. Incremental backup for other days 3. Enable autobackup of control file 4. Backup archive log every day 5. RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS 6. Execute "Delete obsolete" every day 7. control file is used instead of catalog
The results observed: 1. Backup of control files older than 30 days will be deleted 2. Backup of archive log files older than 30 days will be deleted. 3. Backup of datafiles older than ~14 days but before 30 days are also DELETED.
In my example, the backup of datafiles created at 26-Sep is deleted at 16-Oct.
I tried "restore database validate until time "sysdate-22"" at 17-Oct. And RMAN reported "datafile xx will be created automatically during restore operation". It seems that RMAN failed to do restoration up to 22 days ago. The retention policy I set seems not effective on datafile backups.
I checked view v$backup_set and the "Keep" is "No" and "Keep until" is empty.
The only thing I can think of, is the settings of "CONTROL_FILE_RECORD_KEEP_TIME". It is marked "7" in the Oracle, which is less than the retention. But I suppose this only causes the backup not deleted, but NOT be deleted earlier.
I run DLY cold backups including controlfile & archivelogs and keep 3 gens of backups and archivelogs to 3 days also. What is the correct procedure to restore back to an old cold backup. Database is backed up Mon,Tue,Wed on Thur we require to bring database back to Tuesday DLY security.
I have tried: startup mount restore database from tag 'DLYTUE' recover database
( this just rolls forward on all archive logs once it restores datafiles, not getting to point to alter database open resetlogs.)
Next tried to :
recover database archivelog tag 'DLYTUE' ( same outcome )
What is the correct rman procedure including should I remove old archive logs from working OS directory ? Also need to know once I restore back and open database to TUE security how do you tidy up the archive logs and dumps which are no longer require i.e. : weds..
I have read about using the set until time option but how to I get absolute time from when cold backup completed if this is the correct procedure.
I just switched my STBDY DB to a PRIMARY DB and I am ran the following:
RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
using target database control file instead of recovery catalog old RMAN configuration parameters: CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY; new RMAN configuration parameters: CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; new RMAN configuration parameters are successfully stored ORA-00245: control file backup operation failed
RMAN-08132: WARNING: cannot update recovery area reclaimable file list
RMAN> show all;
RMAN configuration parameters for database with db_unique_name ORARZULB are: CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS; CONFIGURE BACKUP OPTIMIZATION OFF; # default CONFIGURE DEFAULT DEVICE TYPE TO DISK; CONFIGURE CONTROLFILE AUTOBACKUP ON; [code]....
what causes this warning and how to get rid of it?
While connecting to target database from stand database. I am getting below error.
calhost dbs]$ sqlplus system/oracle@proddb
SQL*Plus: Release 10.2.0.1.0 - Production on Sat Jun 22 00:18:10 2013
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production With the Partitioning, OLAP and Data Mining options
SQL> exit Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production With the Partitioning, OLAP and Data Mining options [standdb@localhost dbs]$ rman target system/oracle@proddb auxiliary system/oracle@standdb
Recovery Manager: Release 10.2.0.1.0 - Production on Sat Jun 22 00:18:22 2013
Copyright (c) 1982, 2005, Oracle. All rights reserved.
i have read from documentation but getting some error.
in last
E:Documents and SettingsAdministrator>rman Recovery Manager: Release 11.2.0.2.0 - Production on Sun Sep 30 03:03:09 2012 Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved. RMAN> connect auxiliary sys/12 connected to auxiliary database: XE (not mounted) RMAN> RMAN> DUPLICATE DATABASE TO xe
[code]...
Backup-Based Duplication Without a Target and a Recovery Catalog Connection?
I have a doubt regarding the process the RMAN follows for restore and recovery of the database.
My Level 0 full backup completes on Saturdays at around 11 am after taking 8 hours (It starts at 3am).On Sunday, I ask RMAN to restore (on a different box) till Saturday 11:30 am.Then, after the restore is successful, I recover it till 11:45 am.
The recovery also goes fine and Iam able to clone to test box.
Till what time is the database restored? I assume its till 11 am since the L0 backup finishes at 11 am though I have asked it to restore till 11:30 am
During the recovery, ONLY the archives generated between Saturday 3 am and till the time i asked for recovery (Saturday 11:45 am ) are required. But, checking the recovery log file, i was surprised to see that RMAN has restored archive files starting from Friday 9:30 pm (Much before the time the Level 0 backup even started).
while opening my database i got this error i already increase my db_recovery_file_dest_size but still i got this error
E:oracleproduct10.2.0db_1BIN>SET ORACLE_SID=LIVEDB E:oracleproduct10.2.0db_1BIN>SQLPLUS SQL*Plus: Release 10.2.0.4.0 - Production on Thu Mar 22 11:14:47 2012 Copyright (c) 1982, 2007, Oracle. All Rights Reserved. Enter user-name: SYS AS SYSDBA Enter password: Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options
I was trying to backup my database via RMAN and I had deleted a datafile from the database while it was still in open mode.Since I can't return back to mount stage again,I tried to bring the tablespace pertaining to that datafile offline and then restore backup of the tablespace but it's falshing error during recovery.
When I try to restore entire database,it is not even able to restore.
I am trying to open the database bur gettinf following errors
ERROR at line 1: ORA-01194: file 1 needs more recovery to be consistent ORA-01110: data file 1: 'C:ORACLEPRODUCT10.2.0ORADATAORCLSYSTEM01.DBF'
SQL> shutdown ORA-01109: database not open Database dismounted. ORACLE instance shut down. SQL> startup mount; ORACLE instance started. Total System Global Area 289406976 bytes
1. My RAC (old RAC) had got a failures from one node, then there was only one existing node now.
2. I configured a RAC (new RAC) on 2 other servers, both of them (old-RAC and new-RAC) has got same OS version, platform and Oracle version release.
3. I took a full backup yesterday plus archivelog in the node of old-Rac, configure NFS in new-Rac to make the backup within remote-share NFS.
The only problem still now that I've restore/recovery/duplicated single instance, not Rac. So, may you guide me to do it?
Information:
Old-Rac & New-Rac: + Cluster 11g: CFS + Database: 2 nodes with same instance name (cbs1-cbs2) + Location for CRS_HOME and ORACLE_HOME: Same to be. + Location of archivelog: Same to be (+ARCHIVE)
I am trying to move my data files from one location to other as i ran out of space.
SQL> alter database rename file 'C:oracleproduct10.2.0oradataSPF433SPF433ADW_DATA.DBF' to 'D:OracleDatafilesSPF433SPF433ADW_DATA.DBF'; Database Altered
SQL> alter database rename file 'C:oracleproduct10.2.0oradataSPF433SPF433ADW_DATATEMP.DBF' to 'D:OracleDatafilesSPF433SPF433ADW_DATATEMP.DBF' Database Altered
Now when i am trying to run Alter Database open I get ORA-01113: file 5 needs media recovery error