I have recently installed a oracle 11g r2 standard edition in aix 6.1.database is on archive log but archived log is generated in daily different folder named after date on system.
i want to generate all archive log in only one folder.
Backup entire database, without archived logs, while the database is open for user activity and also This backup should be the base for an incremental backup strategy.
View 10 Replies View RelatedI ran the Full database backup as,
RUN {ALLOCATE CHANNEL CH0 TYPE 'sbt_tape';
BACKUP DATABASE FORCE PLUS ARCHIVELOG FORCE NOT BACKED UP DELETE INPUT;
RELEASE CHANNEL CH0;
}
Then I ran the restore, it failed with Quote:RMAN-06054: media recovery requesting unknown archived log....
When I backup archivelogs and choose to delete the input, it does not delete the multiplexed copy, but the specific file being backed up.So, ideally it should find it in Flah Area or at least in the backed up pieces which are there with it.Still why is it failing?
Also, in recovery, it is deleting the archived log after applying, RMAN does this if we use recover... delete archivelog command.I am using only RECOVER, still in output I can see RMAN deleting the log after it has applied it. WHY?
How to manage your archived log?
View 9 Replies View RelatedORA-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 ran into the message RMAN-08138: WARNING: archived log not deleted - must create more backups during a backup. From what I understand this is caused when logs are removed that are needed for recovery.
rman target / nocatalog <<EOT
CONFIGURE CHANNEL DEVICE TYPE DISK clear ;
CONFIGURE CHANNEL DEVICE TYPE TAPE clear ;
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' clear ;
CONFIGURE RETENTION POLICY TO recovery window of 14 days;
CONFIGURE BACKUP OPTIMIZATION OFF;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
[code].....
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'
Opening the database with manually copied oracle data folders and files. Due to my server crashed we were forced to format the system. In that my friend by mistake copied the oracle folder (All data files, redo log files) manually instead of taking a backup in a procedural manner. Now we need to restore all the data. Would it be possible to restore the data with copied data file. If so how?
View 10 Replies View RelatedI've got a legacy SAP system with oracle 8i on Tru64. No changes at all are made but for legal reasons we have to keep it up and running.
we currently do a full backup monthly by shutting down oracle and doing a backup of all the files to tape and that takes around 12 hours.
If I stop doing the full backup and I only backup the control file and the archived redo log files every month and I had to restore the full database years from now, would I be able to restore the database using the last full monthly backup and use the latest control file and archived redo log files?
Assuming you have a 9i database . where you have it enabled in archive mode , yet constantly deleting the archived redo logs , due to space constraints .
Will you be able to perform a full level 0 backup , and the following incremental backups , in the absence of the archived redo logs ? And are these incremental backups enough to recover the database or particular data files , to the point of the backup itself at least ?
Backup your entire database, without archived logs, while the database is open for user activity. This backup should be the base for an incremental backup strategy
View 1 Replies View RelatedURL....I'm practicing for the OCP test and one of the questions is that there is a backup from yesterday and the last archived logs are from the day before yesterday not mentioned if it's cold or hot backup.
If its a cold backup - cant we recover it? is it a must to have the archived redo logs also when recovering a cold backup? That sounds not logical since those logs are made only for a hot backup. URL.....
I couldn't take backup of the RAC database archivelog.
RMAN> BACKUP VALIDATE DATABASE ARCHIVELOG ALL;
Starting backup at 24-MAR-13
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=+DG1/kvxcprd/datafile/system.260.777756857
input datafile fno=00003 name=+DG1/kvxcprd/datafile/sysaux.268.777756857
input datafile fno=00002 name=+DG1/kvxcprd/datafile/undotbs1.263.777756857
input datafile fno=00005 name=+DG1/kvxcprd/datafile/undotbs2.264.777756983
input datafile fno=00004 name=+DG1/kvxcprd/datafile/users.267.777756857
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:25
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=2 sequence=17 recid=26 stamp=810915691
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/24/2013 14:37:11
ORA-19599: block number 1985 is corrupt in archived log +FG/kvxcprd/archivelog/2013_03_24/thread_2_seq_17.269.810915689
RMAN> backup archivelog all;
Starting backup at 24-MAR-13
current log archived
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 03/24/2013 14:39:52
ORA-19563: header validation failed for file
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