Backup controlfile by RMAN error

Similar Questions

• RMAN > recover DB with backup controlfile > RMAN-06025: no backup of...

  Oracle Database 10g Enterprise Edition Release 10.2.0.2.0
  on RHEL 5
  
  I am trying to execute the following commands to RMAN in a TEST instance and receive errors. I don't have the archive logs in the test OS instance (they were deleted manually... "I know it's a big mistake). Is there a way to always run 'restore database using backup controlfile until Cancel' successfully?
  
  Step 1:
  
  SQL > restore database using backup controlfile until cancel;
  ORA-00279: change 40600690589 September at 2010-04-18 19:38:24 to
  thread 1
  ORA-00289: suggestion: /u001/dbsvr/deverp1/arch_575406629_1_122104.arc
  ORA-00280: change 40600690589 thread 1 is in sequence #122104
  
  Specify the log: {< RET > = suggested |} Filename | AUTO | CANCEL}
  
  Auto
  
  ORA-00308: cannot open archived log
  ' / u001/dbsvr/deverp1/arch_575406629_1_122104.arc'
  ORA-27037: unable to get file status
  Linux-x86_64 error: 2: no such file or directory
  Additional information: 3
  
  
  ORA-01547: WARNING: RECOVER succeeded but OPEN RESETLOGS would get below error
  ORA-01194: file 1 needs a recovery more match
  ORA-01110: data file 1: '+ DATA2/prod/datafile/system.291.716736657 '.
  
  
  ==========================================================
  Step 2:
  
  rman target $ /.
  RMAN >
  run
  {
  allocate channel d1 type disk;
  define archivelog destination to ' / u001/dbsvr/deverp1 / ";
  restore the logseq 122104 than logseq 122204 thread 1 all archivelog;
  output channel d1;
  }
  
  allocated channel: d1
  channel d1: sid = 1971 devtype = DISK
  
  executing command: SET DESTINATION ARCHIVELOG
  
  From restoration to April 19, 10
  
  output channel: d1
  RMAN-00571:
  RMAN-00569:
  = FOLLOWS THE ERROR MESSAGE BATTERY =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the restore command at 19/04/2010 19:45:29
  RMAN-06026: some targets not found - abandonment of restoration
  RMAN-06025: no thread 1 122116 lowscn found 40607234921 seq log backup to restore
  RMAN-06025: no thread 1 122115 lowscn found 40606700559 seq log backup to restore
  
  RMAN >
  
  Published by: CipherDBA on April 19, 2010 18:43

  I see you are using ASM. In this case, I strongly suggest forgetting all about giving orders for recovery of any kind in SQL * more and make sure that you have completely mastered RMAN. RMAN is the only reliable tool that can be used to do anything in ASM. In general, it is a very bad idea to mix managed by users and managed by RMAN recovery mechanisms: you ask just for confusion all round!

  Also, I see someone suggesting 'Restoration until the 122114 seq archivelog', but it is false. If you run the syntax in this way, eventually you recovery until the end of the log 122113 and not enforce a 122114 again, that seems to exist. Numbers you put in an rman command "set until" are not exhaustive, so if you are missing journal 115, it's that you defined up to the number. You do not go around off delimbing a 1 or so just in case where, unless you plan to perform a recovery more incomplete than you can actually go out with.

  Overall, the most appropriate RMAN recovery command in this case would be, I would say:

  crosscheck archivelog all;
  crosscheck backup;
  run {
  set until logseq 122115;
  restore database;
  recover database;}
  

  More seriously: I have no idea why you are trying to recover with a bit of 'backup controlfile' in your syntax. It is only necessary if you have actually lost the original control file and have restored a backup. But since I don't see you do that ('Restore automatic backup controlfile' would be the usual thing to do with RMAN), then there is no need to specify that little bit of syntax in your orders. Now that you once asked Oracle to think he's working with a backup controlfile, however, all bets are off, so if I were you, in view of this is that a test system, I put things in a working state, and then start your recovery from scratch test. Just say 'using backup controlfile' If you actually are. If you simply mount the original controlfile that has not been lost by the disaster, so there no need to mention and the above commands should work properly.

• Backup Controlfile RMAN

  Hello

  If I configured the RMAN for using backup controlfile option:

  RMAN > configure controlfile autobackup on;

  I always have to do this:

  SQL ' ALTER DATABASE BACKUP CONTROLFILE TO "${CTRLBKP}" ";

  I have a script to backup RMAN (written by someone else) who issues the SQL above once the backup is complete.

  My understanding is that if the controlfile is automatically RMAN backup, there is no need to run the SQL above.

  Please notify.

  Hello

  no need to take backup using sql.

  You can also read this if you have the slightest doubt:configuration of RMAN environment

  HTH

• RMAN backup fails with the error

  Hi all
  
  Oracle 10.2.0.3
  Windows 2003 Server
  
  We take RMAN backup full every day. We are facing problems while taking backups.
  Please find the error message is recorded in the backup log.
  
  RMAN-03009: failure of the backup command on channel ch1 at 2009-09-07 23:17:05
  ORA-19502: write error on file '\\VN619. In. NAB.COM\ORACLE_BACKUP\DB\DB_DATA_GHKOM9K0_3_1_20090907 ", blockno 342401 (blocksize = 8192).
  ORA-27072: IO file error
  OSD-04008: WriteFile() failure, cannot write to the file
  S/O-error: (OS 64) the specified network name is no longer available.
  
  What is happening Alternatively, some days, the backup is successful. We thought that the problem of network and changed the way network access, but since a few days, it was ok, and even now, we are facing the same problem.
  
  I spoke with our network administrators, they said its not related to the network and there is no errors in the log of their network.
  
  
  If you please advice to slove this...
  
  TIA,

  RMAN works very well. This is your network connection. He sometimes works normal, sometimes doesn't

• RMAN errors

  I get below error while trying to restore the database. Please let me know where I made mistakes.

  RMAN > RUN

  2 > {}

  3 > STARTUP NOMOUNT

  4 > SET until TIME ' TO_DATE (31 July 14 09:24 ', "DD-MM-YY HH24:MI:SS");

  5 > restore controlfile to ' E:\EffTemp\RMAN_CONTROL. RMAN';

  6 > startup MOUNT;

  7 > RESTORE database;

  8 > RECOVER DATABASE;

  9 > ALTER DATABASE OPEN RESETLOGS;

  {10 >}

  connected to the database target (not started)

  Oracle instance started

  Total System Global Area 2622255104 bytes

  Bytes of size 2258072 fixed

  1946159976 variable size bytes

  654311424 of database buffers bytes

  Redo buffers 19525632 bytes

  executing command: SET until clause

  From restoration to the 31 July 14

  RMAN-00571: ===========================================================

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

  RMAN-00571: ===========================================================

  RMAN-03002: failure of the restore command to 31/07/2014 11:55:29

  ORA-01507: database not mounted

  Try this use of it, you must format the date type and then use set until:

  RMAN > RUN

  {

  SHUTDOWN IMMEDIATE;

  STARTUP NOMOUNT;

  RESTORE AUTOMATIC BACKUP CONTROLFILE;

  stop immediately;

  bootable media;

  SQL "alter session set NLS_DATE_FORMAT = 'My JJ YYYY HH24:MI:SS' ';"

  Up to THE TIME "November 19, 2018 21:30 ';"

  RESTORE THE DATABASE;

  RECOVER THE DATABASE;

  SHUTDOWN IMMEDIATE;

  BOOTABLE MEDIA;

  }

• Restore RMAN error

  Hello
  I restore 20 Apr 11 backup but it give the error below mention. Please notify
  
  rman bash-3 target. $ 00 /.
  THE VALUE OF DBID 3166051926
  RUN {}
  startup nomount
  allocate channel c1 type disk;
  allocate channel c2 type disk;
  
  Recovery Manager: Release 10.2.0.4.0 - Production Fri Apr 29 23:55:09 2011
  
  Copyright (c) 1982, 2007, Oracle. All rights reserved.
  
  allocated channel c3 type disk;
  CONTROLFILE AUTOBACKUP FORMAT SET
  FOR DEVICE TYPE DISK TO ' / oranfsbkup/lmsdb/backup/20APR11/%F';
  RESTORE AUTOMATIC BACKUP CONTROLFILE;
  change the editing of the database;
  restore the database;
  recover the database;
  output channel c1;
  output channel c2.
  output channel c3.
  ALTER database open resetlogs;
  } connected to the database target (not started)
  
  RMAN >
  executing command: SET DBID
  
  RMAN >
  
  Oracle instance started
  
  Total System Global Area 3221225472 bytes
  
  Bytes of size 2105952 fixed
  209718688 variable size bytes
  3003121664 of database buffers bytes
  Redo buffers 6279168 bytes
  
  using the control file of the target instead of recovery catalog database
  allocated channel: c1
  channel c1: sid = 153 devtype = DISK
  
  allocated channel: c2
  channel c2: sid = 152 devtype = DISK
  
  allocated channel: c3
  channel c3: sid = 150 devtype = DISK
  
  executing command: SET CONTROLFILE AUTOBACKUP FORMAT
  
  From restoration to the 29 April 11
  
  channel c1: looking for autobackup day: 20110429
  channel c1: looking for autobackup day: 20110428
  channel c1: looking for autobackup day: 20110427
  channel c1: looking for autobackup day: 20110426
  channel c1: looking for autobackup day: 20110425
  channel c1: looking for autobackup day: 20110424
  channel c1: looking for autobackup day: 20110423
  channel c1: found no autobackup in 7 days
  channel c2: looking for autobackup day: 20110429
  channel c2: looking for autobackup day: 20110428
  channel c2: looking for autobackup day: 20110427
  channel c2: looking for autobackup day: 20110426
  channel c2: looking for autobackup day: 20110425
  channel c2: looking for autobackup day: 20110424
  channel c2: looking for autobackup day: 20110423
  channel c2: found no autobackup in 7 days
  channel c3: looking for autobackup day: 20110429
  channel c3: looking for autobackup day: 20110428
  channel c3: looking for autobackup day: 20110427
  channel c3: looking for autobackup day: 20110426
  channel c3: looking for autobackup day: 20110425
  channel c3: looking for autobackup day: 20110424
  channel c3: looking for autobackup day: 20110423
  channel c3: found no autobackup in 7 days
  output channel: c1
  output channel: c2
  output channel: c3
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the restore command at 29/04/2011 23:55:22
  RMAN-06172: no autobackup couldn't find or handle specified is not a valid copy or a piece
  
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-00558: error occurred during parsing of order entry
  RMAN-01006: error scored during the analysis
  RMAN-02003: unrecognized character:
  
  RMAN > show all.
  
  RMAN configuration parameters are:
  CONFIGURE REDUNDANCY 1 RETENTION STRATEGY; # by default
  CONFIGURE BACKUP OPTIMIZATION # by default
  SET UP DEFAULT DISK DEVICE TYPE; # by default
  CONFIGURE CONTROLFILE AUTOBACKUP # by default
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
  SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
  CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
  CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
  CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
  CONFIGURE ENCRYPTION OF DATABASE # by default
  CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
  CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
  
  Thank you
  Merri

  See the example which has the command
  "RESTORE CONTROLFILE AUTOBACKUP MAXSEQ 100;

  to
  http://download.Oracle.com/docs/CD/B19306_01/backup.102/b14194/rcmsynta055.htm#sthref875

  The MAXSEQ 100 in this example is to instruct the Oracle to go as far as 100 days looking to save.
  (the value by default, as you have discovered, is 7 days).

  Hemant K Collette

• Cannot retrieve automatic backup controlfile

  Hallo! I am a newbie to oracle studying for certification in Database Administration OCP Oracle 10 g.
  During his studies, I proposed using the instructions below for the resumption of the controlfiles
  
  SQL > ALTER DATABASE BACKUP CONTROLFILE to TRACE;
  
  RMAN > CONFIGURE CONTROLFILE AUTOBACKUP ON;
  
  To see if I could pick up the controlfiles once lost, I deleted all instances of the controlfiles, and then I ran the statement that caused the errors below
  
  RMAN > restore controlfile autobackup.
  
  From restoration to October 23, 10
  using channel ORA_DISK_1
  
  field of recovery destination: / u01/app/oracle/flash_recovery_area
  name of database (or unique name of database) used for research: ORCL
  channel ORA_DISK_1: no record not found in the recovery area
  Autobackup search outside the recovery zone not tempted because DBID has not been set.
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the restore command at 2010-10-23 17:25:17
  RMAN-06172: no autobackup couldn't find or handle specified is not a valid copy or a piece
  
  How is that possible when I had already created the AutoSave?
  
  Please help me.
  
  Thank you.

  Here is the procedure.

  # controlfile recovering using RMAN and no FRA and nocatalog

  RMAN target /.
  Set the DBID = 1188930158
  startup nomount;
  Restore automatic backup controlfile;
  change the editing of the database;
  recover the database;
  ALTER database open resetlogs;

  Have you taken the RMAN backup after you configure controlfile autobackup

  RMAN > backup database archivelog;

  Concerning
  Asif Kabir

  Handle: * 4joey1 *.
  Status level: Beginner
  Join date: April 28, 2009
  Messages total: 63
  Total Questions: * 40 (34 pending) *.

  -brand your helpful post as correct/good and close all answered threads.

• Backup DB by RMAN

  Hi all
  I have a probem with backup of database by RMAN. I searched the internet, I tried everthing, but without result.
  
  It's my RMAN script:
  
  Run {}
  allocate channels ch1 type disk maxpiecesize = 1900 M;
  full backup of database noexclude
  format 'c:\oracle_backup\ovanet_datafile_20100719-14070425.bak '.
  tag 'my;
  }
  
  
  before script, I put these settings:
  
  Configure redundancy 7 retention strategy;
  configure backup optimization
  Configure the type of device parallelism disc 1;
  configure backup of data file for device 1 disc type.
  Configure snapshot controlfile name to "% ORACLE_BCK%\%ORACLE_SID%-snapcf.f";
  Configure controlfile autobackup on;
  Configure controlfile autobackup format for device type disk to "% ORACLE_BCK%\%ORACLE_SID%-controlfile_%F";
  
  Then and how I run the backup then RMAN throw this log:
  
  
  Recovery Manager: Release 10.2.0.1.0 - Production on Mon Jul 19 14:07:16 2010
  
  Copyright (c) 1982, 2005, Oracle. All rights reserved.
  
  connected to target database: OVANET (DBID = 263516168)
  
  RMAN > comprehensive database # backup controlfile and spfile
  2 > run {}
  3 > allocate channel ch1 type disk maxpiecesize = 1900M;
  4 > full backup of database noexclude
  5 > format 'c:\oracle_backup\ovanet_datafile_20100719-14070425.bak '.
  6 > tag "Lun."
  {7 >}
  8 > "exit";
  using the control file of the target instead of recovery catalog database
  allocated channel: ch1
  channel ch1: sid = 136 devtype = DISK
  
  From backup July 19, 10
  channel ch1: starting full datafile backupset
  channel ch1: specifying datafile (s) in backupset
  input datafile fno = 00001 name = C:\ORACLE_DATA\OVANET\SYSTEM01. DBF
  input datafile fno = 00003 name = C:\ORACLE_DATA\OVANET\SYSAUX01. DBF
  input datafile fno = name 00002 = C:\ORACLE_DATA\OVANET\UNDOTBS01. DBF
  input datafile fno = 00004 name = C:\ORACLE_DATA\OVANET\USERS01. DBF
  input datafile fno = 00005 name = C:\ORACLE_DATA\OVANET\BILLING. ORA
  channel ch1: starting piece 1 to July 19, 10
  channel ch1: finished piece 1 to July 19, 10
  piece handle=C:\ORACLE_BACKUP\OVANET_DATAFILE_20100719-14070425.BAK tag = MY comment = NONE
  channel ch1: complete set of backups, time: 00:01:06
  channel ch1: starting full datafile backupset
  channel ch1: specifying datafile (s) in backupset
  including the current control in backupset file
  including current SPFILE in backupset
  channel ch1: starting piece 1 to July 19, 10
  output channel: ch1
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03009: failure of the backup command on channel ch1 at 2010-07-19 14:08:26
  ORA-19504: cannot create the file 'C:\ORACLE_BACKUP\OVANET_DATAFILE_20100719-14070425.BAK '.
  ORA-27038: created file already exists
  OSD-04010: < create > option specified, the file already exists
  
  Complete recovery manager.
  
  
  Why could not create the file, created file already exists? Before starting the backup file doesn't NOT EXIST!
  
  During the treatment, backup in the folder file is created, but on the end RMAN deleted file.
  
  I'm really dying. Plese help.
  
  I'm sorry for my English, I'm the Czech Republic junior developer and ORACLE is not my jpb, but this what I should do.
  
  Thank you very much for everything.

  Hai,

  run {
  allocate channel ch1 type Disk maxpiecesize = 1900M;
  backup full database noexclude
  format 'c:\oracle_backup\ovanet_datafile_20100719-14070425.bak'
  tag 'Mon';
  } 
  

  Line - format ' c:\oracle_backup\ovanet_datafile_20100719-14070425.bak -causing error.
  Put the line in the format "c:\oracle_backup\ovanet_datafile_20100719-14070425_%U.bak".

  % You'll generate backupset unique name

  Kind regards
  Montagnier

• RMAN: Error trying to retrieve a data file

  Hi all.
  
  I have a problem: I accessed the EM today and I could see that a specific data file that has my DB is offline in the restoring state (must get it back). First, using the DB EM I selected the option to recover this file of data to a specific time in the past in my backups. But I can't get it back in any case, always I got this message:
  
  -------------------------------------------------------------------------------
  RMAN > run {}
  2 > restore datafile 5 until time ' to_date ('2009-05-12 15:33:16 ',' ' YYYY-MM-DD HH24:MI:SS). "
  {3 >}
  From restoration to 13 May 09
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: sid = 150 devtype = DISK
  output channel: ORA_DISK_1
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the restore command at 13/05/2009 12:33:58
  ORA-19554: error device allocation, type of device: SBT_TAPE device name:
  ORA-27211: unable to load the media management library
  
  
  RMAN > "exit";
  
  Complete recovery manager.
  -------------------------------------------------------------------------------
  
  Analyzing this message I see ORA-19554 tells me that the device type is defined s SBT_TAPE. But I didn't do my backups on tape. I did a disk and it is running OK every day without any problem. My DB is in ARCHIVELOG mode and I have an area called/app/oracle_recovery_area, and in this case, I store the archivelogs and made by RMAN backups. My RMAN parameters are those below:
  
  -------------------------------------------------------------------------------
  RMAN configuration parameters are:
  CONFIGURE THE RETENTION NONE POLICY;
  CONFIGURE BACKUP OPTIMIZATION
  SET UP DEFAULT DISK DEVICE TYPE;
  CONFIGURE CONTROLFILE AUTOBACKUP ON;
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT for DEVICE TYPE DISK TO ' / app/oracle_recovery_area/ORCL/backup/%F';
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO "%F" # by default
  SET UP THE DEVICE TYPE DISK BACKUP FOR PARALLELISM BACKUPSET TABLET 1 TYPE;
  SET UP THE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
  CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
  CONFIGURE BACKUP COPIES OF DATA FILE FOR DEVICE TYPE SBT_TAPE TO 1; # by default
  CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
  CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE SBT_TAPE TO 1; # by default
  CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT ' / app/oracle_recovery_area/ORCL/backup/%U' MAXPIECESIZE 2 G;
  CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' MAXPIECESIZE 2 G;
  CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
  CONFIGURE ENCRYPTION OF DATABASE # by default
  CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
  CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
  CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / app/oracle/product/10.2.0/db_1/dbs/snapcf_orcl.f'; # by default
  -------------------------------------------------------------------------------
  
  Could someone help me with the solution to recover this data file?
  Thank you very much.

  It's bug 4338664 , EM DBCONSOLE is DEFAULT to SBT_TAPE REGARDLESS OF RMAN SETTINGS.

  In an RMAN command line session number

  Configure CHANNEL device type 'SBT_TAPE' clear;

  Werner

• tape backup fail with RMAN-03002 RMAN-20201 and RMAN-06010

  Hello
  
  My level 0 backup failed over the weekend and I don't understand why. I know I have four data corruption with files, so I put the MAXCORRUPT to 5 for these specific files so the continuous backup to work. This script has completed successfully in the past, and the structure of the database has not changed since the last backup of level 0 has been taken using this script. Here's what I see in my log file that displays the RMAN script, I used to run the backup and the following error messages:
  
  Recovery Manager: Release 10.2.0.1.0 - Production on Sat Apr 18 00:05:24 2009
  
  RMAN > Connect target *.
  2 > run {}
  3 > allocate channel oem_sbt_backup1 type 'SBT_TAPE' format 'SDE_L0_ % %%U s_ t_ ";
  4 > allocate channel oem_sbt_backup2 type 'SBT_TAPE' format 'SDE_L0_ % %%U s_ t_ ";
  5 > the file VALUE of DATA MAXCORRUPT for 112,28,61,43 to 5;
  6 > database backup incremental level 0 filesperset 1;
  7 > archivelog backup all the format "%%U t_ SDE_ARCLOG_" remove entry;
  8 > delete noprompt obsolete recovery window 14 days device type 'SBT_TAPE ';
  9 > output channel oem_sbt_backup1;
  10 > output channel oem_sbt_backup2;
  11 > assign the channel oem_disk_backup1 type disc format ' / u01/app/oracle/controlfilebackups/cf_SDE_%t_%s_%U';
  12 > backup current controlfile;
  13 > output channel oem_disk_backup1;
  {14 >}
  15 >
  connected to target database: MYDATABASENAME (DBID = <>#)
  using the control file of the target instead of recovery catalog database
  
  allocated channel: oem_sbt_backup1
  channel oem_sbt_backup1: sid = 108 devtype = SBT_TAPE
  channel oem_sbt_backup1: NMO v5.0.0.0
  command sent on channel: oem_sbt_backup1
  
  allocated channel: oem_sbt_backup2
  channel oem_sbt_backup2: sid = 159 devtype = SBT_TAPE
  channel oem_sbt_backup2: NMO v5.0.0.0
  command sent on channel: oem_sbt_backup2
  
  executing command: SET MAX CORRUPT
  output channel: oem_sbt_backup1
  output channel: oem_sbt_backup2
  RMAN-00571: ======================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ======================================================
  RMAN-03002: failure of the command set to 18/04/2009 00:05:36
  RMAN-20201: datafile not found in the recovery catalog
  RMAN-06010: error while looking upward of datafile: 112

  DataFile 112 exist?

  See the notes 197932.1 on MOS.

• Database ALTER DATABASE RECOVER using backup controlfile with AUTO option

  Hello. I was recovering a database today and had a little blip.

  I have published the following:

  Database ALTER DATABASE RECOVER using backup controlfile

  I then chose the AUTO option, allowing Oracle to select all available log files so that it would recover to the last log found in the destination of archive

  However... has performed the following:

  ORA-00289: suggestion:
  /U03/Oracle/stk2proddata/archived_logs/arch1_242449_737547185.dbf
  ORA-00280: change 30031145558 thread 1 is in sequence #242449
  ORA-00278: log file
  ' / u03/oracle/stk2proddata/archived_logs/arch1_242448_737547185.dbf' is no longer
  necessary for this recovery

  
  ORA-00308: cannot open archived log
  ' / u03/oracle/stk2proddata/archived_logs/arch1_242449_737547185.dbf'
  ORA-27037: unable to get file status
  Linux-x86_64 error: 2: no such file or directory
  Additional information: 3

  Two messages above that I expected. However, I made then this:

  SQL > alter database open resetlogs;

  ALTER database open resetlogs

  *

  ERROR on line 1:

  ORA-01113: file 1 needs media recovery

  ORA-01110: data file 1: ' / u02/oracle/stk2proddata/system01.dbf'

  This is not what I expected. What I've done wrong? Should I once received the message "cannot open archived log", launched to CANCEL?

  I then recovered again, but used

  SQL > restore database using backup controlfile until cancel;

  ORA-00279: change 30031145558 generated at 30/04/2014 09:58:34 needed to
  thread 1
  ORA-00289: suggestion:
  /U03/Oracle/stk2proddata/archived_logs/arch1_242449_737547185.dbf
  ORA-00280: change 30031145558 thread 1 is in sequence #242449

  
  Specify the log: {< RET > = suggested |} Filename | AUTO | CANCEL}

  ORA-00279: change 30031157768 generated at 30/04/2014 10:06:07 needed to
  thread 1
  ORA-00289: suggestion:
  /U03/Oracle/stk2proddata/archived_logs/arch1_242450_737547185.dbf
  ORA-00280: change 30031157768 thread 1 is in sequence #242450
  ORA-00278: log file
  ' / u03/oracle/stk2proddata/archived_logs/arch1_242449_737547185.dbf' is no longer
  necessary for this recovery

  
  Specify the log: {< RET > = suggested |} Filename | AUTO | CANCEL}
  Cancel
  Cancelled media recovery.
  SQL > alter database open resetlogs;

  Database altered.

  No problem then here. Could someone please explain what I did wrong the first time and the second time right? Is this a problem with the car and using CANCEL?

  Thank you!

  DA

  11.2.0.2

  RHEL 5.5

  Bug: 4178579

• Backup controlfile to trace as 'c:\prod_ctl.txt '.

  Hi all

  11.2.0.1

  I review the output of the trace file, because I want to simulate or test this process.

  This file has two (2) sets of command. one (1) for online newspapers intact and one (1) to damage newspapers online.

  Issues related to the:

  1. What do you mean by damage, newspapers online. does that mean I lost all these redo files:

  LOGFILE

  GROUP 1 ' D:\APP\PROD\ORADATA\ORCL\REDO01. NEWSPAPER "SIZE 50 M 512 BLOCKSIZE,

  GROUP 2 ' D:\APP\PROD\ORADATA\ORCL\REDO02. NEWSPAPER "SIZE 50 M 512 BLOCKSIZE,

  GROUP 3 ' D:\APP\PROD\ORADATA\ORCL\REDO03. NEWSPAPER "SIZE 50 M BLOCKSIZE 512

  
  

  2. Why is that the two (2) are still set up orders? with the exception of the backup controlfile and open resetlogs?

  3. should I backup RMAN to perform this recovery statements?

  
  

  Thank you

  pK
  

  ========

  -Here's current system-scope REDO Log archiving related

  -parameters and can be included in the database initialization file.

  --

  -LOG_ARCHIVE_DEST = "

  -LOG_ARCHIVE_DUPLEX_DEST = "

  --

  --LOG_ARCHIVE_FORMAT=ARC%S_%R.%T

  --

  -DB_UNIQUE_NAME = "orcl".

  --

  -LOG_ARCHIVE_CONFIG =' SEND, RECEIVE, NODG_CONFIG'

  -LOG_ARCHIVE_MAX_PROCESSES = 4

  -STANDBY_FILE_MANAGEMENT = MANUAL

  --STANDBY_ARCHIVE_DEST=%ORACLE_HOME%\RDBMS

  -FAL_CLIENT = "

  -FAL_SERVER = "

  --

  -LOG_ARCHIVE_DEST_1 =' LOCATION = USE_DB_RECOVERY_FILE_DEST'

  -LOG_ARCHIVE_DEST_1 = "NODELAY MANDATORY NOREOPEN.

  -LOG_ARCHIVE_DEST_1 = 'NOAFFIRM ARCH ACCELERATE NOVERIFY SYNC'

  -LOG_ARCHIVE_DEST_1 = 'NOREGISTER NOALTERNATE NODEPENDENCY.

  -LOG_ARCHIVE_DEST_1 = 'NOMAX_FAILURE NOQUOTA_SIZE NOQUOTA_USED NODB_UNIQUE_NAME.

  -LOG_ARCHIVE_DEST_1 = 'VALID_FOR = (PRIMARY_ROLE, ONLINE_LOGFILES)'

  -LOG_ARCHIVE_DEST_STATE_1 = ENABLE

  --

  -Here are two sets of SQL statements, each of them creates a new

  -control file and use it to open the database. The first series opens

  -the database with the NORESETLOGS option and should be used only if

  -the current versions of all online newspapers are available. The second

  -together opens the database with the RESETLOGS option and should be used

  -If online newspapers are not available.

  -All appropriate declarations that can be copied from the trace to

  -a script file, edited as necessary and executed when there is a

  -need to re - create the control file.

  --

  -Set #1. NORESETLOGS case

  --

  -The following commands will create a new control file and use

  -to open the database.

  -The data used by the Recovery Manager will be lost.

  -Additional logs may be required for media recovery of offline

  -Use this option only if the current versions of all online newspapers are

  -available.

  -After mounting the controlfile created, the following SQL code

  -Statement will place the database in case

  -protection mode:

  -ALTER DATABASE BASE_DE_DONNEES ENSURES TOGETHER TO OPTIMIZE PERFORMANCE

  STARTUP NOMOUNT

  CREATE CONTROLFILE REUSE DATABASE "ORCL" NORESETLOGS NOARCHIVELOG

  MAXLOGFILES 16

  MAXLOGMEMBERS 3

  MAXDATAFILES 100

  MAXINSTANCES 8

  MAXLOGHISTORY 292

  LOGFILE

  GROUP 1 ' D:\APP\PROD\ORADATA\ORCL\REDO01. NEWSPAPER "SIZE 50 M 512 BLOCKSIZE,

  GROUP 2 ' D:\APP\PROD\ORADATA\ORCL\REDO02. NEWSPAPER "SIZE 50 M 512 BLOCKSIZE,

  GROUP 3 ' D:\APP\PROD\ORADATA\ORCL\REDO03. NEWSPAPER "SIZE 50 M BLOCKSIZE 512

  -STANDBY LOGFILE

  DATA FILE

  ' D:\APP\PROD\ORADATA\ORCL\SYSTEM01. DBF',.

  ' D:\APP\PROD\ORADATA\ORCL\SYSAUX01. DBF',.

  ' D:\APP\PROD\ORADATA\ORCL\UNDOTBS01. DBF',.

  ' D:\APP\PROD\ORADATA\ORCL\USERS01. DBF',.

  ' D:\APP\PROD\ORADATA\ORCL\EXAMPLE01. DBF'

  WE8MSWIN1252 CHARACTER SET

  ;

  -Orders to recreate the table of the incarnation

  -Under journal names MUST be replaced by names of existing files

  -disc. The log files from each branch can be used for

  -re - create the folders of the incarnation.

  -REGISTRY ALTER DATABASE LOG FILE ' D:\APP\PROD\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2013_12_26\O1_MF_1_1_%U_. ARC'.

  -REGISTRY ALTER DATABASE LOG FILE ' D:\APP\PROD\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2013_12_26\O1_MF_1_1_%U_. ARC'.

  -Recovery is required if any of the data files are restored backups.

  - or if the last shutdown was not normal or immediate.

  RECOVER THE DATABASE

  -Database can now be opened normally.

  ALTER DATABASE OPEN;

  -Commands to add tempfiles to temporary storage.

  -Online Tempfiles have complete space information.

  -Other tempfiles may require an adjustment.

  ALTER TABLESPACE TEMP ADD TEMPFILE ' D:\APP\PROD\ORADATA\ORCL\TEMP01. DBF'

  SIZE 20971520 REUSE AUTOEXTEND ON NEXT 655360 32767M MAXSIZE;

  -End of tempfile additions.

  --

  -Set #2. RESETLOGS case

  --

  -The following commands will create a new control file and use

  -to open the database.

  -The data used by the Recovery Manager will be lost.

  -The content of online newspapers will be lost and all backups

  -be invalidated. Use this option only if online newspapers are damaged.

  -After mounting the controlfile created, the following SQL code

  -Statement will place the database in case

  -protection mode:

  -ALTER DATABASE BASE_DE_DONNEES ENSURES TOGETHER TO OPTIMIZE PERFORMANCE

  STARTUP NOMOUNT

  CREATE CONTROLFILE REUSE DATABASE "ORCL" RESETLOGS NOARCHIVELOG

  MAXLOGFILES 16

  MAXLOGMEMBERS 3

  MAXDATAFILES 100

  MAXINSTANCES 8

  MAXLOGHISTORY 292

  LOGFILE

  GROUP 1 ' D:\APP\PROD\ORADATA\ORCL\REDO01. NEWSPAPER "SIZE 50 M 512 BLOCKSIZE,

  GROUP 2 ' D:\APP\PROD\ORADATA\ORCL\REDO02. NEWSPAPER "SIZE 50 M 512 BLOCKSIZE,

  GROUP 3 ' D:\APP\PROD\ORADATA\ORCL\REDO03. NEWSPAPER "SIZE 50 M BLOCKSIZE 512

  -STANDBY LOGFILE

  DATA FILE

  ' D:\APP\PROD\ORADATA\ORCL\SYSTEM01. DBF',.

  ' D:\APP\PROD\ORADATA\ORCL\SYSAUX01. DBF',.

  ' D:\APP\PROD\ORADATA\ORCL\UNDOTBS01. DBF',.

  ' D:\APP\PROD\ORADATA\ORCL\USERS01. DBF',.

  ' D:\APP\PROD\ORADATA\ORCL\EXAMPLE01. DBF'

  WE8MSWIN1252 CHARACTER SET

  ;

  -Orders to recreate the table of the incarnation

  -Under journal names MUST be replaced by names of existing files

  -disc. The log files from each branch can be used for

  -re - create the folders of the incarnation.

  -REGISTRY ALTER DATABASE LOG FILE ' D:\APP\PROD\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2013_12_26\O1_MF_1_1_%U_. ARC'.

  -REGISTRY ALTER DATABASE LOG FILE ' D:\APP\PROD\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2013_12_26\O1_MF_1_1_%U_. ARC'.

  -Recovery is required if any of the data files are restored backups.

  - or if the last shutdown was not normal or immediate.

  RECOVER DATABASE USING BACKUP CONTROLFILE

  -Database can now be opened to zero online newspapers.

  ALTER DATABASE OPEN RESETLOGS;

  -Commands to add tempfiles to temporary storage.

  -Online Tempfiles have complete space information.

  -Other tempfiles may require an adjustment.

  ALTER TABLESPACE TEMP ADD TEMPFILE ' D:\APP\PROD\ORADATA\ORCL\TEMP01. DBF'

  SIZE 20971520 REUSE AUTOEXTEND ON NEXT 655360 32767M MAXSIZE;

  -End of tempfile additions.

  --

  ===============,

  Hello

  According to the Oracle Documentation:

  RESETLOGS specify RESETLOGS if you want Oracle database to ignore the content of the files listed in the LOGFILE clause. These files do not have to exist. Each redo_log_file_spec in the LOGFILE clause must specify the SIZE parameter. The database assigns redo all online log file groups to thread 1 and enables this thread for public use by any instance. After using this clause, you must open the database by using the ALTER DATABASE statement RESETLOGS clause.

  NORESETLOGS NORESETLOGS to specify if you want the Oracle server to use all files in the LOGFILE clause as they were when the database was last open. These files must exist and must be the online redo logs rather that restore backups. The database reassigns log files groups redo the nets to which they were previously assigned and re-active threads as they authorized beforehand.

  With RESETLOGS you're going to have a new incarnation of the database and are used when you perform incomplete recovery when you do not have full recovery stack to perform a full restore.

  Do I need a backup RMAN to test this statement?

  No, 'must' use RMAN. You can perform a recovery by the managed user. Personally its always preferable to use RMAN, but if you aren't aware of the working RMAN you can go forward with the managed user.

  Kind regards

  Suntrupth

• RMAN ERROR - 06428

  I changed a db in archivelog noarchivelog mode because there was a problem with archivelog (no free space in the destination of recovery)

  The problem comes when trying to run backup script backup.

  RMAN-00571: ===========================================================

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

  RMAN-00571: ===========================================================

  RMAN-03002: failure to allocate command at 24/09/2013 14:55:54

  RMAN-06428: recovery catalog is not installed

  The problem comes when trying to run backup script backup.

  RMAN-00571: ===========================================================

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

  RMAN-00571: ===========================================================

  RMAN-03002: failure to allocate command at 24/09/2013 14:55:54

  RMAN-06428: recovery catalog is not installed

  Any idea?

  Hello

  Connect to the database as the owner of the catalog schema and issue this query:

  SELECT db_key, db_id FROM db WHERE db_id = 12345639687;

  DB_ID DB_KEY

  ---------- ----------

  12345639687 XXXXXXX

  Then, run the following package:

  SQL > execute dbms_rcvcat.unregisterdatabase (xxxxxxx, 12345639687);

  After that, you can save the database again.

  This my idea

  Thank you

• backup controlfile

  Hello world!
  
  I have a very dull question.
  
  My oracle is always full due to my controlfile record.
  
  I have to remove them, and I think that they are not buy useful, I'm not sure.
  
  I daily make a backup with this rman script:
  
  Run {}
  assign the channel c1 type disc format ' / oraclebck/backup_%d_set%s_piece%p_%T_%U';
  backup of database filesperset 1;
  backup current controlfile;
  backup ARCHIVELOG all delete them all entries;
  output channel c1;
  }
  
  
  which makes the controlfile backup in the backup piece, isn't?
  
  I have it configured in rman
  
  
  RMAN > show all.
  
  RMAN configuration parameters are:
  CONFIGURE REDUNDANCY 1 RETENTION STRATEGY; # by default
  CONFIGURE BACKUP OPTIMIZATION # by default
  SET UP DEFAULT DISK DEVICE TYPE; # by default
  CONFIGURE CONTROLFILE AUTOBACKUP ON;
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
  SET UP THE DEVICE TYPE DISK PARALLELISM 1; # by default
  CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
  CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
  CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT ' / backup/ora_df%t_s%s_s%p';
  CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
  CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / casa/oracle/product/9.2/dbs/snapcf_adaiasrv.f'; # by default
  
  Can I configure CONTROLFILE AUTOBACKUP off, since I make a backup of controlfile with rman?
  
  Thank you

  Controlfile autobackup can vary.
  or alternatively, you can change the location of the setting below
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default

  importance: -.
  RMAN can be configured to automatically back up the control file and the server settings file every time that metadata from database structure in control of changes in the file and each time a backup folder is added. Automatic backup RMAN can recover data even if the current control file, catalog and server parameter file are lost.
  Because the file name for the backup uses a well known format, RMAN can get without access to a repository and restore the server settings file. After you start the instance with the restored server settings file, RMAN can restore a backup control file. Once you mount the control file, the RMAN Repository is available and RMAN can restore the data files and find that the archived redo log.

• backup controlfile format

  Hello
  
  When I backup controlfile, rman generates two files:
  ctl_tnn17r1o and c-3169926800-20120120-00
  
  What is the reason for this?
  
  
  

  RMAN> backup current controlfile format '/rmanbackup/orcl/ctl_%u';
  
  Starting backup at 20-JAN-12
  using channel ORA_DISK_1
  using channel ORA_DISK_2
  using channel ORA_DISK_3
  channel ORA_DISK_1: starting full datafile backup set
  channel ORA_DISK_1: specifying datafile(s) in backup set
  including current control file in backup set
  channel ORA_DISK_1: starting piece 1 at 20-JAN-12
  channel ORA_DISK_1: finished piece 1 at 20-JAN-12
  piece handle=/rmanbackup/orcl/ctl_tnn17r1o tag=TAG20120120T101311 comment=NONE
  channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
  Finished backup at 20-JAN-12
  
  Starting Control File and SPFILE Autobackup at 20-JAN-12
  piece handle=/rmanbackup/orcl/c-3169926800-20120120-00 comment=NONE
  Finished Control File and SPFILE Autobackup at 20-JAN-12

  Yes, the reason is that you select "Controlfile Autobackup.

  You specify RMAN to do the backup of the controlfile in the format ' / rmanbackup/orcl/ctl_%u '. If you have found the 1st controlfile backup as ctl_tnn17r1o . Later, since you turn autobackup controlfile on, RMAN takes the automatic backup of the controlfile which is the 2nd file c-3169926800-20120120-00

  You can check if the controlfile autobackup is enabled or not by using:

  RMAN > show all.

  Handle: Ora_83
  Status level: Beginner
  Join date: November 8, 2009
  Messages total: 474
  Total Questions: 177 (114 pending)

  Why so many unanswered questions? If you do not have the answers in the right way, then ask them again in the same thread rather than leaving pending

  Published by: srp on 20 January 2012 10:39