Catalog vs controlfile recovery... ID of the database

Similar Questions

• RMAN - Catalog and ControlFile Recovery

  I recorded rock database (same host) and Fatima databases (in another machine) in the RECOVERY CATALOG.
  
  I m sticking with Faure database backup using the recovery catalog
  
  
  
  RMAN >
  
  Complete recovery manager.
  ^ C
  H:\ > rman target sys/farooq@farooq catalog rman2/cat@rock
  
  Recovery Manager: Release 10.2.0.1.0 - Production on Mon Sep 8 14:41:17 2008
  
  Copyright (c) 1982, 2005, Oracle. All rights reserved.
  
  connected to target database: FAURE (DBID = 1820635189)
  connected to the recovery catalog database
  
  RMAN > register database;
  
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03009: failure of the register command to the default channel on 2008-09-08 14:41:37
  RMAN-20002: target database is already registered in the recovery catalog
  
  RMAN > outline report;
  
  Report of the database schema
  
  List of permanent data files
  ===========================
  Size (MB) Tablespace RB segs Datafile file name
  ---- -------- -------------------- ------- ------------------------
  1 YES D:\ORADATA\FAROOQ\SYSTEM01 480 SYSTEM. DBF
  2 35 UNDOTBS1 D:\ORADATA\FAROOQ\UNDOTBS01 YES. DBF
  SYSAUX 3 250 NO D:\ORADATA\FAROOQ\SYSAUX01. DBF
  4 5 USERS WITHOUT D:\ORADATA\FAROOQ\USERS01. DBF
  5 100 EXAMPLE NO D:\ORADATA\FAROOQ\EXAMPLE01. DBF
  
  RMAN > list backup;
  
  
  RMAN > backup as incremental compressed backupset of level 0 database more archivelog;
  
  
  From backup 08-SEP-08
  Current archived log
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of command thus backup archivelog at 2008-09-08 14:43:03
  RMAN-03014: implicit recovery catalog Resync failed
  RMAN-06004: error ORACLE recovery catalog database: RMAN-20020: incarnation of the database not defined
  
  RMAN > list incarnation of database;
  
  
  List of Incarnations of the database
  DB key Inc key STATE ID DB name DB reset reset time SNA
  ------- ------- -------- ---------------- --- ---------- ----------
  3641 3649 FAURE 1820635189 PARENT 534907 29 JULY 08
  FAURE 3641 3642 1820635189 CURRENT 695424 08-SEP-08
  
  RMAN > RESET DATABASE to incarnation 3642
  2 >.
  
  database restore the incarnation 3642
  
  RMAN > backup as incremental compressed backupset of level 0 database more archivelog;
  
  
  From backup 08-SEP-08
  Current archived log
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: sid = 142 devtype = DISK
  channel ORA_DISK_1: starting from backupset journal archive compressed
  channel ORA_DISK_1: specification of archive log backup set
  archive log entry thread = 1 sequence 1 recid = 4 = 664886867 stamp =
  archive log entry thread = 1 sequence 2 recid = 5 = 664888152 stamp =
  archive log entry thread = 1 sequence = recid 3 = 6 = 664888938 stamp
  archive log entry thread = 1 sequence 4 recid = 7 = 664889572 stamp =
  archive log entry thread = 1 sequence 5 recid = 8 = 664889658 stamp =
  archive log entry thread = 1 sequence 6 recid = 9 = 664891871 stamp =
  archive log entry thread = 1 sequence 7 recid = 10 = 664892590 stamp =
  archive log entry thread = 1 sequence 8 recid = 11 = 664900983 stamp =
  archive log entry thread = 1 sequence 9 recid = 12 = 664902190 stamp =
  channel ORA_DISK_1: from room 1 to 08 - SEP-08
  channel ORA_DISK_1: finished piece 1 to 08 - SEP-08
  piece handle = D:\ORADATA\FLASH_RECOVERY_AREA\FAROOQ\BACKUPSET\2008_09_08\O1_MF_ANNNN_TAG20080908T150314_4D9Y35PK_. Tag BKP = comment TAG20080908T150314 = NONE
  channel ORA_DISK_1: complete set of backups, time: 00:00:26
  channel ORA_DISK_1: starting from backupset journal archive compressed
  channel ORA_DISK_1: specification of archive log backup set
  archive log entry thread = 1 sequence 8 recid = 1 stamp = 664886398 =
  archive log entry thread = 1 sequence 9 recid = 2 = 664886399 stamp =
  archive log entry thread = 1 sequence 10 recid = 3 = 664886403 stamp =
  channel ORA_DISK_1: from room 1 to 08 - SEP-08
  channel ORA_DISK_1: finished piece 1 to 08 - SEP-08
  piece handle = D:\ORADATA\FLASH_RECOVERY_AREA\FAROOQ\BACKUPSET\2008_09_08\O1_MF_ANNNN_TAG20080908T150314_4D9Y407K_. Tag BKP = comment TAG20080908T150314 = NONE
  channel ORA_DISK_1: complete set of backups, time: 00:00:09
  Backup finished 08-SEP-08
  
  From backup 08-SEP-08
  using channel ORA_DISK_1
  channel ORA_DISK_1: additional start-up compressed 0 datafile backupset
  channel ORA_DISK_1: specifying datafile (s) in backupset
  input datafile fno = 00001 name = D:\ORADATA\FAROOQ\SYSTEM01. DBF
  input datafile fno = 00003 name = D:\ORADATA\FAROOQ\SYSAUX01. DBF
  input datafile fno = 00005 name = D:\ORADATA\FAROOQ\EXAMPLE01. DBF
  input datafile fno = name 00002 = D:\ORADATA\FAROOQ\UNDOTBS01. DBF
  input datafile fno = 00004 name = D:\ORADATA\FAROOQ\USERS01. DBF
  channel ORA_DISK_1: from room 1 to 08 - SEP-08
  channel ORA_DISK_1: finished piece 1 to 08 - SEP-08
  piece handle = D:\ORADATA\FLASH_RECOVERY_AREA\FAROOQ\BACKUPSET\2008_09_08\O1_MF_NNND0_TAG20080908T150351_4D9Y49WW_. Tag BKP = comment TAG20080908T150351 = NONE
  channel ORA_DISK_1: complete set of backups, time: 00:01:15
  Backup finished 08-SEP-08
  
  From backup 08-SEP-08
  Current archived log
  using channel ORA_DISK_1
  channel ORA_DISK_1: starting from backupset journal archive compressed
  channel ORA_DISK_1: specification of archive log backup set
  archive log entry thread = 1 sequence 10 recid = 13 = 664902308 stamp =
  channel ORA_DISK_1: from room 1 to 08 - SEP-08
  channel ORA_DISK_1: finished piece 1 to 08 - SEP-08
  piece handle = D:\ORADATA\FLASH_RECOVERY_AREA\FAROOQ\BACKUPSET\2008_09_08\O1_MF_ANNNN_TAG20080908T150512_4D9Y6T1D_. Tag BKP = comment TAG20080908T150512 = NONE
  channel ORA_DISK_1: complete set of backups, time: 00:00:02
  Backup finished 08-SEP-08
  
  From control file and SPFILE Autobackup 08-SEP-08
  piece handle = D:\ORACLE\RMAN_BACKUP\CTL_SP_BAK_C-1820635189-20080908-09 comment = NONE
  Control finished and Autobackup SPFILE file 08-SEP-08
  
  RMAN > list backup;
  
  
  Backup list
  ===============
  S LV TY Device Type delay #Pieces compressed #Copies Tag key
  ------- -- -- - ----------- --------------- ------- ------- ---------- ---
  4615 DISC 08-SEP-08 1 1 YES TAG20080908T150314
  4617 B 0 A DRIVE 08-SEP-08 1 1 YES TAG20080908T150351
  4650 DISC 08-SEP-08 1 1 YES TAG20080908T150512
  4670 HAS NO DISK 1 1 08 - SEP - 08 NO TAG20080908T150517
  
  RMAN >
  
  
  
  Now, I m conneting to Faure - target database and obtaining the same information from the control file backup.
  
  H:\ > rman target sys/farooq@farooq
  
  Recovery Manager: Release 10.2.0.1.0 - Production on Mon 8 Sep 15:05:38 2008
  
  Copyright (c) 1982, 2005, Oracle. All rights reserved.
  
  connected to target database: FAURE (DBID = 1820635189)
  
  RMAN > LIST BACKUP SUMMARY;
  
  using the control file of the target instead of recovery catalog database
  
  Backup list
  ===============
  S LV TY Device Type delay #Pieces compressed #Copies Tag key
  ------- -- -- - ----------- --------------- ------- ------- ---------- ---
  21. A DRIVE 08-SEP-08 1 1 YES TAG20080908T150314
  22. A DRIVE 08-SEP-08 1 1 YES TAG20080908T150314
  23 B 0 A DRIVE 08-SEP-08 1 1 YES TAG20080908T150351
  24. A DRIVE 08-SEP-08 1 1 YES TAG20080908T150512
  25 A NO DISK 1 1 08 - SEP - 08 NO TAG20080908T150517
  
  My question: why are the information stored in the database control file (Faure) target so that its stored in the recovery catalog?

  Hello

  By default, RMAN stored metadata in the file control, all the RMAN is first written to control the file and then catalog of recovery if leaves. For example, when rman creates a new backupset, you can view the information in the v$ backup_set and you can also view the same information of the recovery RC_BAKCUP_SET catalog views.
  So every change repository is stored in two places... Control file and optionally recovery_catalog

  The catalog of recovery of the RMAN Repository versions are stored in database tables and version control repository os file stored as files in with in the control file.

  -Pavan Kumar N

• How instance recovery and restart the database after SHUTDOWN ABORT?

  How instance recovery and restart the database after the database is closed by using the command "SHUTDOWN ABORT"?

  Recovery if instance Oracle background SMON instance failure process using or stop quitting or database starting strength. After shutdown abort you just restart the startup database, oracle will take care for instance recovery you need'nt to intervene for example recovery.

• Database controlfile recovery

  Scenario:
  
  -10 day old backup of database
  -From yesterday's archive logs
  
  Database crashed.
  
  I have now to restore the data files and create a new controlfile because the old 10 day controlfile is not picking up the new archiving logs information.
  
  
  SQL > startup nomount;
  ORACLE instance started.
  
  Total System Global Area 289406976 bytes
  Bytes of size 1248576 fixed
  113246912 variable size bytes
  167772160 of database buffers bytes
  Redo buffers 7139328 bytes
  SQL > alter database backup controlfile to trace;
  ALTER database backup controlfile to trace
  *+
  ERROR on line 1:
  ORA-01507: database not mounted
  
  SQL > alter the editing of the database;
  change the database editing
  *+
  ERROR on line 1:
  ORA-00205: error in the identification of control files, check the log of alerts for more information
  
  I can't go up because there is no controlfile and I can't backup controlfile to trace , because the database is not mounted.
  
  
  What to do now?

  VR;
  recover database using backup controlfile until cancel; Apply then all archive logs

  ALTER database open resetlogs;

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

• The database recovery

  Hi all

  EBS R12.2.4

  OEL6

  I play with the recovery of database > restore database using backup controlfile until cancel;

  but I encountered error:

  ORA-00279: change 5965308871319 September at 29/11/2015 10:49:20 needed to

  thread 1

  ORA-00289: suggestion: /home/ARCH/1_212_894234402.dbf

  ORA-00280: change 5965308871319 thread 1 is in sequence #212

  ORA-00278: log file ' / home/ARCH/1_211_894234402.dbf' is no longer necessary for this

  recovery

  ORA-00283: cool cancelled due to errors

  ORA-01244: datafile (s) without a name added to the control file by the media recovery

  ORA-01110: data file 42: ' / home/oraprod/PROD/data/a_txn_ind10.dbf'

  ORA-01112: media recovery not started

  SQL > shutdown immediate;

  ORA-01109: database is not open

  The database is dismounted.

  ORACLE instance stops.

  SQL > bootable media.

  ORACLE instance started.

  Total System Global Area 2137886720 bytes

  Bytes of size 2230072 fixed

  452987080 variable size bytes

  1660944384 of database buffers bytes

  Redo buffers 21725184 bytes

  Mounted database.

  SQL > restore database using backup controlfile until cancel;

  ORA-00283: cool cancelled due to errors

  ORA-01111: 42 data file name is unknown - rename it to the correct file

  ORA-01110: data file 42: ' / home/oraprod/PROD/11.2.0/dbs/UNNAMED00042'

  ORA-01157: cannot identify/lock data file of 42 - see DBWR trace file

  ORA-01111: 42 data file name is unknown - rename it to the correct file

  ORA-01110: data file 42: ' / home/oraprod/PROD/11.2.0/dbs/UNNAMED00042'

  SQL >

  Help, please...

  Thank you

  JC

  You cannot copy directly, but you can save only data file with rman "backup datafile 42. However, the RCS in the header of the data file would be different now, and you cannot recover.

  You said in one of the message that the file without a NAME no longer exists? You rename it using 'alter database rename file '?

  You can use:

  ALTER database create datafile 42 as ' / home/oraprod/PROD/data/a_txn_ind10.dbf';

  Then run:

  RECOVER THE DATABASE AUTOMATICALLY USING BACKUP CONTROLFILE UNTIL CANCEL

• How Controlfile SNA remain synchronized after moving the database with the cold backup

  Hello DBAs,

  I doubt that:

  Every time you pass a cold backup database. We create a new controlfile with new locations of data/redologs etc.

  And then we execute "create controlfile reuse...". noresetlogs...; "to create the controlfile.

  After that, we will open the database as > > alter database open;

  Now the question is:

  We are able to open the database without clause "resetlogs.

  Here, we create a new controlfile so SNA to controlfile will not be synchronized with the SCN of the datafile and redo the file.

  Please let me know how the new controlfiles' SNA is synchronized with the data file and redofile and wea are able to open the database without resetlogs clause.

  Oracle: 11.2.0.4

  OS: Linux

  If your cold backup also includes online redo logs, a RESETLOGS is not necessary.

  The controlfile is created if it does not have a SNA, it reads the data file headers the YVERT database. For a cold backup, all the headers of data file are consistent.  (This is also the reason why a RECOVERY is not required).

  Hemant K Collette

• problem in the recovery of the database!

  Hi all
  
  I created a new database and wanted to restore the backup to a different database in it, I created the required tablespaces and began the restoration of RMAN backup by
  
  Run {}
  allocate channel 'dev_0' type 'sbt_tape '.
  parms 'ENV = (OB2BARTYPE = Oracle8, OB2APPNAME = orcl OB2BARLIST = DAILY_HISDBS01_ORACLE-DB_ONLINE_5W, OB2BARHOSTNAME = hisdbs01.kfmc.med)';
  Restore controlfile from "c-1179279249-20090511-02';
  change the editing of the database;
  free the channel "dev_0;
  }
  
  The obtained controlfile restored successfully, then I tried to restore and recover the database
  
  Run {}
  allocate channel 'dev_0' type 'sbt_tape '.
  parms 'ENV = (OB2BARTYPE = Oracle8, central = OB2APPNAME, OB2BARLIST = DAILY_HISDBS01_ORACLE-DB_ONLINE_5W, OB2BARHOSTNAME = hisdbs01.kfmc.med)';
  restore the database;
  recover the database;
  free the channel "dev_0;
  }
  
  The restoration was successful, but when I tried to open the database with the resetlogs option
  
  SQL > alter database open resetlogs;
  ALTER database open resetlogs
  *
  ERROR on line 1:
  ORA-01194: file 1 needs a recovery more match
  ORA-01110: data file 1: '+ DATADG/orcl/datafile/system.295.686609187 '.
  SQL > restore database using backup controlfile until cancel;
  
  ORA-00279: change 1136286903 September at 2009-05-11 02:08:22 for thread1
  ORA-00289: suggestion: */arch/archivelog/1_8493_651861624.dbf*
  ORA-00280: change 1136286903 thread 1 is in sequence #8493
  
  Specify the log: {< RET > = suggested |} Filename | AUTO | CANCEL}
  Cancel
  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: '+ DATADG/orcl/datafile/system.295.686609187 '.
  ORA-01112: media recovery not started
  
  The recovery process is looking for */arch/archivelog/1_8493_651861624.dbf* this archivelog, but this archivelog file is not present at this location, the restore process should have restored all archivelogs as well, in fact any archivelogs didn't get restored, how can I recover the database without newspapers archivelog? It is not possible at all.
  
  Please tell me how can I do the database work?

  Have you tried to restore the Archivelogs through RMAN manually, using "RESTORE ARCHIVELOG FROM TIME ="datestring "?

  See if RMAN can detect the ArchiveLogs tape.

• The database recovery/restore failed with unexpected error 509

  Hello

  The database recovery/restore failed with unexpected error 509

  In the Event Viewer, I had this error SEVERAL times every second.  He goes absolutely crazy.

  I don't know what to do with it.

  I'm with Windows 8 Pro running on a very stable computer with 8gig of ram, plenty of hard drive space.  Each single drivers updated Windows Update.  Everything is really clean except this error in Event Viewer

  Svchost SRUJet (1624): database recovery/restore failed with unexpected-509 error.

  Task category: registration/recovery

  Esentutl /p /r tried / everything but nothing wrong was found with those

  Thanks for any help.

  Exactly the same problem, nothing Microsoft recommended was the cause, scannow and DISM commands are returned without error.

  So I went to the event viewer and scrolled down to find, when these errors began to occur. So I found a few entries initially saying things like: an attempt to move the file 'C:\Users\xxxxx\AppData\Local\TileDataLayer\Database\EDB.log' to 'C:\Users\xxxxxxxx\AppData\Local\TileDataLayer\Database\EDB00008.log' failed indicating system 183 (0x000000b7) error: "cannot create a file when that file already exists.

  Then, I went to C:\Users\xxxxx\AppData\Local\TileDataLayer\Database\ and removed the files listed (e.g., EDB00008.log).

  Bingo, the errors will stop immediately.

• A query need to check whether the database should any recovery media...

  Hello
  
  I'm at the stage of editing a database and still be opened.at this point no matter what query is available or in any other way is there to check whether the database should any recovery media or Instance recovery... ?
  
  My goal is before opening the database, I make sure it's compatible or incompatible, and any form of recovery is necessary.
  
  Thank you and best regards,
  Rameau
  
  Published by: ragu.dba.in on 6 March 2013 12:57 AM

  Hi Lila,

  Use these queries, YVERT should match... no fuzzy file, don't check for recovering files in v$ recover_file... spend sufficient archives & realize the audits before open reset-logs

  set line 900
  set pages 900
  set echo on
  alter session set nls_date_format='dd-mon-yyyy hh24:mi:ss';
  set numwidth 13
  col CHECKPOINT_CHANGE# for 9999999999999999
  col CHANGE# for 9999999999999999
  column error format a10
  column member format a60
  show parameter db_recover
  select * from v$recover_file;
  select file#, status from v$datafile;
  select file#, checkpoint_change#, checkpoint_time, error from v$datafile_header;
  select distinct status from v$backup;
  select distinct  checkpoint_change#  from v$datafile_header;
  select hxfil file_id, fhscn scn, fhthr thread, fhrba_seq sequence, fhsta status from x$kcvfh;
  select distinct fhscn from x$kcvfh;
  select hxfil file_id, fhtnm tablespace_name from x$kcvfh;
  ##### Fuzzy Check ####
  alter session set nls_date_format = 'DD-MON-YYYY HH24:MI:SS';
  set feedback on
  set heading on
  set pagesize 1000
  set linesize 175
  column checkpoint_change# format 999999999999999999999
  select status, checkpoint_change#, fuzzy,
  to_char(checkpoint_time, 'DD-MON-YYYY HH24:MI:SS') as checkpoint_time,
  count(*)
  from v$datafile_header
  group by status, checkpoint_change#, fuzzy, checkpoint_time
  order by status, checkpoint_change#, fuzzy, checkpoint_time;
  

  Thank you
  Ajay more
  http://www.moreajays.com

• The database Point-in-time recovery

  Hi, experts.
  I have an interesting question. For example, I have consistent backup, backup and archivelog next cintrolfile. I want to recover the database to a point in time or SCN in the middle of this newspaper. How to check, before you begin the recovery, that this point in time, or SNA will be compatible? How to find coherent whole SNA or SNA that will I can recover the database for?

  How to find coherent whole SNA or SNA that will I can recover the database for?

  Not sure if we give the same meaning to "compatible", but all the SNA are "compatible": see this AskTom thread, where you can read

  the system change number (SCN) is the clock of Oracle - whenever we are committed, the clock
  increments. The RCS has just marks a coherent point in time in the database.

• What will do to include current controlfile in the database

  Hello
  
  When you try to create a copy of the database, it still manages not to copy the controlfile
  What does take to include current controlfile in the copy of the database to the %b format
  

  RMAN> backup as copy database format 'd:\backup\%b'
  2> ;
  
  Starting backup at 13-SEP-10
  using channel ORA_DISK_1
  channel ORA_DISK_1: starting datafile copy
  input datafile file number=00001 name=D:\ORACLE\ORADATA\ORCL\SYSTEM01.DBF
  output file name=D:\BACKUP\SYSTEM01.DBF tag=TAG20100913T204940 RECID=16 STAMP=729636617
  channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:45
  channel ORA_DISK_1: starting datafile copy
  input datafile file number=00003 name=D:\ORACLE\ORADATA\ORCL\UNDOTBS01.DBF
  output file name=D:\BACKUP\UNDOTBS01.DBF tag=TAG20100913T204940 RECID=17 STAMP=729636660
  channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:35
  channel ORA_DISK_1: starting datafile copy
  input datafile file number=00002 name=D:\ORACLE\ORADATA\ORCL\SYSAUX01.DBF
  output file name=D:\BACKUP\SYSAUX01.DBF tag=TAG20100913T204940 RECID=18 STAMP=729636692
  channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:35
  channel ORA_DISK_1: starting datafile copy
  *copying current *control file**
  RMAN-03009: failure of backup command on ORA_DISK_1 channel at 09/13/2010 20:51:36
  ORA-19715: invalid format b for generated name
  ORA-27302: failure occurred at: slgpn
  continuing other job steps, job failed will not be re-run
  channel ORA_DISK_1: starting datafile copy
  input datafile file number=00004 name=D:\ORACLE\ORADATA\ORCL\USERS01.DBF
  output file name=D:\BACKUP\USERS01.DBF tag=TAG20100913T204940 RECID=19 STAMP=729636697
  channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:01
  channel ORA_DISK_1: starting full datafile backup set
  channel ORA_DISK_1: specifying datafile(s) in backup set
  *including current SPFILE in backup set*
  channel ORA_DISK_1: starting piece 1 at 13-SEP-10
  RMAN-00571: ===========================================================
  RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
  RMAN-00571: ===========================================================
  RMAN-03009: failure of backup command on ORA_DISK_1 channel at 09/13/2010 20:51:38
  ORA-19715: invalid format b for generated name
  ORA-27302: failure occurred at: slgpn

  Published by: hrishy on 13 Sep, 2010 08:26

  Hello

  Try setting 'CONFIGURE CONTROLFILE AUTOBACKUP ON' - what makes your work

  -Pavan Kumar N

• With regard to the restoration of the database and recovery (DBPITR)

  Hello

  Today I have a level 0 backup (23/01/2015) and I want to restore and to recover the database up to yesterday (22/01/2015-21:00) by using the backup of level 0 of today.

  Is this possible? If so, please tell me how?

  Thanks in advance.

  Hello

  It is not possible to restore and to recover the database until yesterday with the backup of level 0 of today.

  Your flashback database is active? If it is active, then you can use flashback database.

  to check it out;

  Select flashback_on in the database of v$.

  Talip Hakan Öztürk

• problem reconfigure everything. in the replication after the database crash recovery

  Dear friends, I have little problem in replication,.
  I have 2 databases DB1 and DB2 configured as Multimaster replication and My DB1 is master def. Now my master got DB2 database crashed and replication topology displayed in red color.
  So I again created DB2 database. So I tried to bring this new DB2 replication again some of the operations being on my site of master def.
  So the problem is that I couldnot stop replication
  Can anyone suggest me how can I reconfigure again back in replication without removing the current group of rep
  
  I tried suspend replication by Lee. intervention but couldnot
  
  Start
  () dbms_repcat.suspend_master_activity
  gname = > 'REPMG');
  end;
  
  can someone solution
  Note:
  my database got crashed and I recreated the database and made available in the position while he was just before the crash

  Even if 'create you' repadmin and links from the database, there is no information about the configuration of replication (repgroup (s), repobjects etc.) in the database. Also, of course, the deferred transaction queue has no entry.

  You must configure replication scratch 'from '.

• Waiting for redo log file missing when restore main database using RMAN backup that was taken on the database physical standby

  Here's my question after tons of research and test without have the right solutions.

  Target:

  (1) I have a 12.1.0.2 database unique main enterprise 'testdb' as database instance running on the server "node1".

  (2) I created physical standby database "stbydb" on the server "node2".

  (3) DataGuard running on the mode of MaxAvailability (SYNC) with roll forward in real time 12 default c apply.

  (4) primary database has 3 groups of one-man redo. (/oraredo/testdb/redo01.log redo02.log redo03.log)

  (5) I've created 4 standby redo logfiles (/oraredo/testdb/stby01.log stby02.log stby03.log stby04.log)

  (6) I do RMAN backup (database and archivelog) on the site of relief only.

  (7) I want to use this backup for full restore of the database on the primary database.

  He is a DR test to simulate the scenario that has lost every primary & Eve total servers.

  Here is how to save, on the database pending:

  (1) performance 'alter database recover managed standby database Cancel' to ensure that compatible data files

  (2) RMAN > backup database;

  (3) RMAN > backup archivelog all;

  I got elements of backup and copied to primary db Server something like:

  /Home/Oracle/backupset/o1_mf_nnndf_TAG20151002T133329_c0xq099p_.BKP (data files)

  /Home/Oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.BKP (spfile & controlfile)

  /Home/Oracle/backupset/o1_mf_annnn_TAG20151002T133357_c0xq15xf_.BKP (archivelogs)

  So here's how to restore, on the main site:

  I clean all the files (data files, controlfiles oder all gone).

  (1) restore spfile from pfile

  RMAN > startup nomount

  RMAN > restore spfile from pfile ' / home/oracle/pfile.txt' to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';

  (2) modify pfile to convert to db primary content. pFile shows below

  *.audit_file_dest='/opt/Oracle/DB/admin/testdb/adump '

  * .audit_trail = "db".

  * full = '12.1.0.2.0'

  *.control_files='/oradata/testdb/control01.ctl','/orafra/testdb/control02.ctl'

  * .db_block_size = 8192

  * .db_domain = "

  *.db_file_name_convert='/testdb/','/testdb /'

  * .db_name = "testdb".

  * .db_recovery_file_dest ='/ orafra'

  * .db_recovery_file_dest_size = 10737418240

  * .db_unique_name = "testdb".

  *.diagnostic_dest='/opt/Oracle/DB '

  * .fal_server = "stbydb".

  * .log_archive_config = 'dg_config = (testdb, stbydb)'

  * .log_archive_dest_2 = "service = stbydb SYNC valid_for = (ONLINE_LOGFILE, PRIMARY_ROLE) db_unique_name = stbydb'"

  * .log_archive_dest_state_2 = 'ENABLE '.

  *.log_file_name_convert='/testdb/','/testdb /'

  * .memory_target = 1800 m

  * .open_cursors = 300

  * runoff = 300

  * .remote_login_passwordfile = "EXCLUSIVE."

  * .standby_file_management = "AUTO".

  * .undo_tablespace = "UNDOTBS1.

  (3) restart db with updated file pfile

  SQLPLUS > create spfile from pfile='/home/oracle/pfile.txt'

  SQLPLUS > the judgment

  SQLPLUS > startup nomount

  (4) restore controlfile

  RMAN > restore primary controlfile to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';

  RMAN > change the editing of the database

  (5) all elements of backup catalog

  RMAN > catalog starts by ' / home/oracle/backupset / '.

  (6) restore and recover the database

  RMAN > restore database;

  RMAN > recover database until the SNA XXXXXX; (this YVERT is the maximum in archivelog backups that extends beyond the scn of the backup of the data file)

  (7) open resetlogs

  RMAN > alter database open resetlogs;

  Everything seems perfect, except one of the file log roll forward pending is not generated

  SQL > select * from v$ standby_log;

  ERROR:

  ORA-00308: cannot open archived log ' / oraredo/testdb/stby01.log'

  ORA-27037: unable to get file status

  Linux-x86_64 error: 2: no such file or directory

  Additional information: 3

  no selected line

  I intended to use the same backup to restore primary basic & helps record traffic and the downtime between them in the world of real output.

  So I have exactly the same steps (except STANDBY restore CONTROLFILE and not recover after database restore) to restore the database pending.

  And I got the same missing log file.

  The problem is:

  (1) complete alert.log filled with this error, not the concern here

  (2) now repeat it in real time apply won't work since the Party shall LGWR shows always "WAITING_FOR_LOG."

  (3) I can't delete and re-create this log file

  Then I tried several and found:

  The missing standby logfile was still 'ACTIVE' at present RMAN backup was made.

  For example, on db standby, under Group #4 (stby01.log) would be lost after the restoration.

  SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;

  GROUP # SEQUENCE # USED STATUS

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

  4 19 ACTIVE 133632

  5 0 0 UNASSIGNED

  6 0 0 not ASSIGNED

  7 0 0 UNASSIGNED

  So until I take the backup, I tried on the primary database:

  SQL > alter system set log_archive_dest_state_2 = delay;

  This was the Group of standby_log side Eve #4 was released:

  SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;

  GROUP # SEQUENCE # USED STATUS

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

  4 0 0 UNASSIGNED

  5 0 0 UNASSIGNED

  6 0 0 not ASSIGNED

  7 0 0 UNASSIGNED

  Then, the backup has been restored correctly without missing standby logfile.

  However, to change this primary database means break DataGuard protection when you perform the backup. It's not accept on the production environment.

  Finally, my real questions come:

  (1) what I do may not do on parameter change?

  (2) I know I can re-create the control file to redo before delete and then recreate after. Is there any simple/fast to avoid the standby logfile lost or recreate the lost one?

  I understand that there are a number of ways to circumvent this. Something to keep a copy of the log file waiting restoration progress and copy up one missing, etc, etc...

  And yes I always have done no real-time applies "to the aid of archived logfile" but is also not accept mode of protection of production.

  I just want proof that the design (which is displayed in a few oracle doc Doc ID 602299.1 is one of those) that backs up data backup works effectively and can be used to restore the two site. And it may be without spending more time to resume backups or put the load on the primary database to create the database before.

  Your idea is very much appreciated.

  Thank you!

  Hello

  1--> when I take via RMAN backup, RMAN does not redo log (ORL or SRL) file, so we cannot expect ORLs or SRL would be restored.

  2nd--> when we opened the ORL database should be deleted and created

  3rd--> Expecting, SRL should not be an issue.we should be able to do away with the fall.

  DR sys@cdb01 SQL > select THREAD #, SEQUENCE #, GROUP #, STATUS from v$ standby_log;

  THREAD # SEQUENCE # GROUP # STATUS

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

  1 233 4 ACTIVE

  1 238 5 ACTIVE

  DR sys@cdb01 SQL > select * from v$ logfile;

  GROUP # STATUS TYPE MEMBER IS_ CON_ID

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

  3 /u03/cdb01/cdb01/redo03.log no. 0 online

  /U03/cdb01/cdb01/redo02.log no. 0 2 online

  1 /u03/cdb01/cdb01/redo01.log no. 0 online

  4 /u03/cdb01/cdb01/stdredo01.log WATCH No. 0

  /U03/cdb01/cdb01/stdredo02.log EVE 5 No. 0

  DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

  method: cannot access the /u03/cdb01/cdb01/stdredo01.log: no such file or directory

  DR sys@cdb01 SQL >! ls - ltr /u03/cdb01/cdb01/stdredo02.log

  -rw - r-. 1 oracle oinstall 52429312 17 Oct 15:32 /u03/cdb01/cdb01/stdredo02.log

  DR sys@cdb01 SQL > alter database force claire logfile 4;

  change the database group claire logfile 4

  *

  ERROR on line 1:

  ORA-01156: recovery or current flashback may need access to files

  DR sys@cdb01 SQL > alter database recover managed standby database cancel;

  Database altered.

  DR sys@cdb01 SQL > change the database group claire logfile 4;

  Database altered.

  DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

  -rw - r-. 1 oracle oinstall 52429312 17 Oct 15:33 /u03/cdb01/cdb01/stdredo01.log

  DR sys@cdb01 SQL >

  If you do, you can recreate the controlfile without waiting for redo log entry...

  If you still think it's something is not acceptable, you must have SR with support to analyze why he does not abandon SRL when controlfile_type is "underway".

  Thank you