While starting up my database i am getting this error.by mistake i had moved log files, and after some time again i inserted those log files again into same directory i am getting this error.
View 13 RepliesWhen i open the primary database in my dataguard env,it raise error?
SQL> alter database open;
alter database open
*
ERROR at line 1:
ORA-00314: log 1 of thread 1, expected sequence# 77 doesn't match 0
ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/oracl/redo01.log'
I am getting the below message in my alert log
System: AIX6.1 - Oracle 11r2
GROUP# THREAD# MEMBER ARCHIVED STATUS MB
1 1 +DATA01/mydb/redolog_group1_member1 NO INACTIVE 1536
1 1 +DATA01/mydb/redolog_group1_member2 NO INACTIVE 1536
2 1 +DATA01/mydb/redolog_group2_member2 NO CURRENT 1536
2 1 +DATA01/mydb/redolog_group2_member1 NO CURRENT 1536
3 1 +DATA01/mydb/redolog_group3_member2 NO INACTIVE 1536
3 1 +DATA01/mydb/redolog_group3_member1 NO INACTIVE 1536Tue Jul 10 18:37:48 2012
[code]....
Could an increase on the redo log file sizes solve this problem? Unfortunately I do not have a test platform, where I could have tested this.
While creating a controlfile while bringing the database up we are consistently getting the below error
ORA-01161: database name CCSPS in file header does not match given name of CCSP
ORA-01110: data file 312: '/aoq53/appl/oracle/ccsps/dtmcs01_07.dbf'
The controlfile creation script is as follows.
CREATE CONTROLFILE SET DATABASE "CCSPS" RESETLOGS NOARCHIVELOG
-- SET STANDBY TO MAXIMIZE PERFORMANCE
MAXLOGFILES 255
MAXLOGMEMBERS 2
MAXDATAFILES 1022
MAXINSTANCES 8
MAXLOGHISTORY 904
[code]....
our production database is not coming up due to this issue and we are on the verge of missing SLA.
ORA-16038: log 2 sequence# 284 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 2 thread 1: /redo02.log'
USER (ospid: 792): terminating the instance due to error 16038
Fri Nov 02 13:14:19 2012
System state dump requested by (instance=1, osid=792), summary=[abnormal instance termination].
Fri Nov 02 13:14:19 2012
ARC3 started with pid=23, OS id=822
Errors in file _ora_792.trc:
ORA-19815: WARNING: db_recovery_file_dest_size of 10240 bytes is 100.00% used, and has 0 remaining bytes available.
i perform logminer in os (window xp and oracle linux 6) both. all the operation are successfully completed but at last i found the same error in both os. the error is
SQL> create table myLogAnalysis
as
select * from v$logmnr_contents;
select * from v$logmnr_contents
*
ERROR at line 3:
ORA-00310: archived log contains sequence 12; sequence 9 required
ORA-00334: archived log:'/home/oracle/oracle/product/10.2.0/oradata/orcl/redo02.log'
Every command I issue in RMAN I get these errors:
RMAN-03002: failure of report command at 07/01/2012 12:33:40 ORA-01861: literal does not match format stringHow should I resolve it?
We are running 11.2.0.3.2.
In my catalog for the "source" database (rman target db), I have the backupsets for a full database backup ended at Feb. 7, 03:43:37. These are online backups. So, there are archived redo logs being generated while it runs and the following archived redo logs finished at Feb. 7, 04:00:24.
We duplicate databases all the time. So, this is not a new concept for us. The one thing that has changed is that we now back up to disk (using the flashback recovery area) and then later on, initiate a backup to tape. Prior to this go-live, we did all of our backups directly to tape. The catalog does not seem confused. It knows it needs to go to tape because it's beyond the retention for disk backups. The only problem is that it is going to the backup prior to the backupset I want, only for a couple of files.
In the past, when all went directly to tape, we would do a set until time 'Feb. 7, 03:43:37' and it would automatically restore the backupset that finished then and apply archived redo logs as necessary to make a consistent copy. Now, if I use the same model, it's going to a backup set from the prior date for 3 particular files. If I change the time to when the archived redo logs ended their backup, 04:00, it still goes back to the day before, but only for 2 files.
I can list a backup of each specific file and see that the file is in the backupset for which I expect RMAN to pull. How can I figure out a date/time to go back to if not using the method of reviewing the catalog entries and timestamps?
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.
Here is the details
[oracle@localhost dbs]$ export ORACLE_SID=stby
[oracle@localhost dbs]$ sqlplus '/as sysdba'
SQL*Plus: Release 10.2.0.1.0 - Production on Thu Oct 20 09:47:34 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to an idle instance.
SQL> !
[oracle@localhost dbs]$ pwd
/oraeng/app/oracle/product/10.2.0/dbs
[oracle@localhost dbs]$ exit
exit
[code].....
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.
understanding rman scn based Backup Algorithm .. In SCN based backup do rman generate backup from archivelogs ???
View 1 Replies View RelatedI have 2 seperate rman backup one backup is of only datafile ,spfile and controlfile which i am able to restore and recover without any problem say bkp1 taken at 10 am
other set of backup is of only archive log files of same day but later time than datafile backup say bkp2 taken at 8pm...if i restore and recover bkp1 and try to restore bkp2 it gives error datafile exist (possibly due to fact both backup have control file)
if i just restore bkp1 and try to restore bkp2 so that i can do one recover at time
it gives error datafile permission issue (possibly due to fact both backup have control file)
I want to restore database upto 8pm time how can i use both bkp1 and bkp2 to do it(restore datafiles and apply all archive logs on it)
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
My scenario is: database is in archivelog mode.
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 need to make my database to ARCHIVELOG mode when i try it it gives below following error
SQL> alter database archivelog;
alter database archivelog
*
ERROR at line 1:
ORA-00265: instance recovery required, cannot set ARCHIVELOG mode
I have a database in Archivelog mode and Flashback mode. I am trying to connect to RMAN. But am getting the error
SQL> select name,log_mode,flashback_on from v$database
2 /
NAME LOG_MODE FLA
--------- ------------ ---
ORCL ARCHIVELOG YES
SQL> show user
USER is "SYS"
SQL> host rman target /
[code]....
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?
I have recently patched my catalog home to 9208 from 9204; the target database is still on 9204 but now I cannot connect to the catalog database.
oracle@mogw:TES1:/u01/app/oracle/admin/TES1/bdump
rman rcvcat rman/rman@RMANDB
Recovery Manager: Release 9.2.0.4.0 - 64bit Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
[code]...
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.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database:
ORA-01031: insufficient privileges
how to duplicate it on oracle 11g xe windows 2003
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?
when i performed incomplete recovery i try to set until time but it shows RMAN-20207:until time or recovery window shoubld be before resetlogs.
View 3 Replies View RelatedBackgroud info:
host server crashed.
Database was not cleanly shutdown.
Database is not in archivelog mode.
Datafiles were saved.
My goal:I want to recover the database based on the available files.
My approach:
Install new database.
ALTER DATABASE BACKUP CONTROLFILE TO TRACE.
shutdown database.
Place available dbf files in the location for new database, replacing existing files.
edit trace file to create new controlfile. Script is:
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "newdatabase" RESETLOGS NOARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
[code]....
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?
REGISTER DATABASE;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of register command at 01/01/2012 11:02:40
RMAN-06428: recovery catalog is not installed
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).
why does RMAN require the old archive log files.
I have problem when i am trying to recover database
i am getting above error.
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
[code].....
I want to do the recovery of my database using the archive log files but one of the archive log in between is missing,
View 17 Replies View RelatedI 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.