Unnecessary number of backup controlfile

Similar Questions

• New added file how to recover using backup controlfile

  Hi all

  From a complete backup direct (extra number 0) I cloned a new dev server database. The next day a new data file added in Live and I took a cumulative incremental backup in Live. Live and Dev server have not even mount point. While the restoration itself I gave the name of the new set for the control of data file to remap all the data files in the new location on the dev server. Now, I want to know how to get back with cumm incr backup when a new data added live file.

  Concerning

  Jennifer

  DBA CTS team

  I restored a backup of incr 0 in dev server with the set new name command. and after that I got the database with the archives transferred to live. and then I opened the database with reset logs... now the database is open... the next day I took differential bkp live to contain the new datafile... How can you apply that backup incr 1 cumm in my dev server.

  You must restart level 0, i.e.

  1. After the level 1 backup archivelogs
  2. backup controlfile
  3. have all the backups on the dev server (level 0, 1, archivelogs and controlfile)
  4. Restore controlfile (from #2)
  5. restore the backup of level 0 (with set newname, including the new data file)
  6. recover the database
  7. Open the database with the resetlogs option.

• Recovery using backup Controlfile...

  Hi all
  
  I have a little doubt about the recovery process...
  
  Suppose I took a cold backup (after immediate stop).
  After that, I started the database, made a newspaper change and delete the control file.
  
  In this case when I try to recover the database by using a backup controlfile (recover database using backup controlfile), I need to provide the name of the log file manually
  to ensure no loss of data during the recovery process.
  After that, I need start the database with the RESET LOGS.
  
  
  But my question is why the database will force you to RESETLOGS even if you haven't lost all the data or you haven't made an incomplete recovery.
  
  
  Thank you...

  >
  Suppose I took a cold backup (after immediate stop).
  After that, I started the database, made a newspaper change and delete the control file.

  In this case when I try to recover the database by using a backup controlfile (recover database using backup controlfile), I need to provide the name of the log file manually
  to ensure no loss of data during the recovery process.
  After that, I need start the database with the RESET LOGS.

  But my question is why the database will force you to RESETLOGS even if you haven't lost all the data or you haven't made an incomplete recovery.
  >
  It's the RESETLOGS forcing resynchronization of the control file.

  A control file "backup" is a copy and is supposed to be an older file so it needs to be synchronized with the redo log using RESETLOGS files.

  See the doc of SQL language
  http://docs.Oracle.com/CD/B28359_01/server.111/b28286/statements_1004.htm
  >
  RESETLOGS. NORESETLOGS clause determines if Oracle database resets the current sequence number to 1, archives logs not archived (including the active log) and eliminates any information redo that was not implemented during recovery, ensuring that it will never be applied. Oracle database using NORESETLOGS automatically except in the following specific situations, which require a framework for this clause:

  You must specify RESETLOGS:

  After completing the incomplete media recovery or media recovery using a backup control file

• Why cant the controlfile be synchronized, when you use the backup controlfile

  Hi all
  
  I understand a little... .to leave a DBA of my friends...
  
  you need a resetlog to synchronize the data file headers and the controlfiles
  
  (1) you need a resetlog when you perform incomplete recovery
  (2) you can complete recovery using a backup controlfile as long as you have all the necessary archived logs and online redo logs.
  (3) but not to do resetlog after 2), you must re-create the controlfile
  
  my questions are
  
  T1) are the next point above true?
  
  (* q2) why update slope the controlfile to oracle during recovery using backup controlfile? in this case, I do not need to recreate a controlfile, isn't?
  
  
  Rgds,
  Noob

  user12050668 wrote:
  Hi Alex and the guys,.

  Thanks for comfirming my questions.
  I wonder what...

  -resetlog was designed to synchronize the control and the data headers file isn't it?
  -When I get back, even if I am using backup controlfile, I'm actually synchronization data is not?

  Yes it's true. But also during resetlogs you get new redologs and PAPER SEQUENCE NUMBER will be 1 and the database will has new incarnation.

  so, the only reason why I need resetlog even if I finished syncing correctly to the point of failure, is simply because I am using a BACKUP controlfile?.

  Yes quite right.

• 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 controlfiles recovery

  Hello
  
  I'm practicing controlfile conecpts backup and restore. In a database, there are 3 controlfiles. I have a copy of database backup controlfile and archivelogs. I deleted a controlfile.
  
  There is no message in the alerts log. I get an error only when I have as long as DBA question certain points of view V$. I get a message that a controlfile does not exist, no file or directory etc. etc.
  
  The interesting thing I have noticed is that I get no error when querying V$ views already recorded sessions until I removed controlfile. I get error only when I connect to a new session and the query V$ views.
  
  
  
  Is there a way DBAs do we know if a controlfile has been deleted at the OS level other than this way? How DBAs usually knows a controlfile is missing?

  1.
  Instance crashes whenever there is an error in the reading or writing of control file. Reading and writing are not a continuous process. So after deletion, you have to wait a bit for the next operation. If you do not want to wait just trying to make the point of control, add/delete datafile or empty manually.

  2.
  RM command really does not remove the files. For fiscal purposes use shred or dd to put some of 0 and 1 in file. If the control file is not valid, its effect will be the same.

  3.
  The number of user sessions / is not serious.

  Bartek

• doubts in the database using backup controlfile recovery.

  Hi gurus,

  I have a doubt in database recovery using backup controlfile.

  I do not speak of "ORA-01207: file is newer than the control file - old control file.

  Here, any of our files archive / redo log have been lost and the problem of lack of update in the control file.

  So why open the database in resetlogs option, after recovering the database by using a backup controlfile. ?

  Thanks in advance

  Mahi

  In order to maintain the consistency of the data, the RCS should be the same in all the files of the controlfile & file REDO data current.

  By definition when you use 'backup controlfile' there a SNA expired in it.

  RESETLOG requires the RCS to 1 in order to get consistency across all files in the database.

  CREATE CONTROLFILE fills this new file with the most recent SNA that exist in the data files.

  It's just the way Oracle has been implemented.

• Can not find the trace file after "alter database backup controlfile to trace;" on the RDBMS 11.2.0.3

  Hello

  I use a database on RDBMS 11.2.0.3. Connected as sys and run

  SQL > alter database backup controlfile to trace;

  Database altered.

  view the USER_DUMP_DEST parameter.

  VALUE OF TYPE NAME

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

  user_dump_dest string D:\app\oracle\diag\rdbms\pears

  dev\pearsdev\trace

  Looking at the track record, there is no trace file? What am I missing?

  Thank you

  Mathias

  Confirm with:

  SQL > dir D:\APP\ORACLE\CONTROLFILE the host. TXT

• 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

• 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

• 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

• Recover using backup controlfile

  A binary restoration of the controlfile requires incomplete recovery of the database and a database open with resetlogs.
  
  But I understand why it is necessary to specify 'using backup controlfile' with the recover command - what is the difference. With the help of Oracle 11.2.
  
  Since Oracle 10 g, it is more necessary to back up the database after a database opened with resetlogs and the recovery process is able to recover a database to a previous, provided incarnation archivelogs are available. What is the history please?

  I just came across this old post of mine. Actually, I don't really remember what it was. However, I think the confusing part was simply that I didn't, that SQL * MORE and RMAN recovery is not the same.

  When you use SQLPLUS to recover the database "with the HELP of BACKUP CONTROLFILE' is necessary. Under RMAN is not necessary because it automatically determines a BACKUP CONTROLFILE. If the question was probably SQL vs RMAN database recovery.

• 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.

• ORA-01194 and ORA-00604 when using backup controlfile set #2

  Oracle 11.2.0.1 database version
  Enterprise Linux 5.4
  Database is in archivelog mode.
  
  I'm trying to recover a database according to a backup controlfile to trace #2. Create the controlfile works very well, but recover the database fails.
  
  From what I understand, the recovery fails because it cannot roll forward - 39 sequence is in the online missing redo log file. However, the database opens with the restlogs option and I understand that it should use the archivelogs in order to roll back. Since it is a new controlfile he does not know the archivelogs, but he does not accept to register or use archivelog files.
  
  The recovery as shown in set #2 doesn't seem to work as expected. Any ideas?
  
  Following errors:
  

  SQL>  CREATE CONTROLFILE REUSE DATABASE "RCAT" RESETLOGS  ARCHIVELOG etc.
  Control file created.
  
  Tyring to register on of the archivelogs does not work:
  SQL>  ALTER DATABASE REGISTER LOGFILE '/u02/fra/RCAT/archivelog/2010_09_19/o1_mf_1_33_69bfo5tx_.arc';
   ALTER DATABASE REGISTER LOGFILE '/u02/fra/RCAT/archivelog/2010_09_19/o1_mf_1_33_69bfo5tx_.arc'
  *
  ERROR at line 1:
  ORA-00604: error occurred at recursive SQL level
  
  
  Applying an existing archivelog during recovery does not work:
  
  SQL> recover database using backup controlfile until cancel
  Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
  /u02/fra/RCAT/archivelog/2010_09_19/o1_mf_1_33_69bfo5tx_.arc
  ORA-00310: archived log contains sequence 33; sequence 39 required
  ORA-00334: archived log:
  '/u02/fra/RCAT/archivelog/2010_09_19/o1_mf_1_33_69bfo5tx_.arc'
  
  
  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/RCAT/datafile/o1_mf_system_6959kz7l_.dbf'
  
  
  ls -l /u02/fra/RCAT/archivelog/2010_09_19:
  -rw-r----- 1 oracle dba 49313280 Sep 19 00:01 o1_mf_1_33_69bfo5tx_.arc
  -rw-r----- 1 oracle dba   312320 Sep 19 00:03 o1_mf_1_34_69bft63b_.arc
  -rw-r----- 1 oracle dba 20343808 Sep 19 02:10 o1_mf_1_35_69bo6y6j_.arc
  -rw-r----- 1 oracle dba    40960 Sep 19 02:12 o1_mf_1_36_69boc9t8_.arc
  -rw-r----- 1 oracle dba    20992 Sep 19 02:13 o1_mf_1_37_69bofng4_.arc
  -rw-r----- 1 oracle dba   794624 Sep 19 02:15 o1_mf_1_38_69bokwbf_.arc

  Thank you
  Markus

  Markus Waldorf wrote:
  I think that I am aware and do not suggest to use the hidden setting.

  What worries me is that the value #2 of the controlfile to trace the contours of the database backup can be recovered even with the lack of recovery online newspapers, but apparently this is not the case. What I also don't understand, is why he simply not restore using the information of the archivelogs. The database was not shut down properly, but isn't always the case when you lose again-online newspapers?

  Here is the text of the controlfile.sql

  -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.

  Published by: Markus Waldorf Sep 20, 2010 09:34

  You are right. But it is especially the case.perform, create the new database and will stop immediately (without demolition) and remove newspapers online OS level. And try to recover the database using backup controlfile until cancel or just recover database until cancel then enter Word Cancel and resetlogs option database open. It will work. Because it actually do not need any recovery operation. But your case you need to recover the database. You consider backup restore las and perform incomplete recovery. I think you can do the first test.