restoration of the database

Similar Questions

• 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 with the restoration of the database

  Hello world

  I have a strange problem while restoring the database with rman. The problem is that the data are not restored at all.

  Let me show you what I do step by step:

  1. create the test table:

  $ sqlplus / as sysdba

  SQL * more: Production of release 11.2.0.1.0 Thu Apr 17 22:51:58 2014

  Copyright (c) 1982, 2009, Oracle.  All rights reserved.

  Connected to:

  Oracle Database 11 g Enterprise Edition Release 11.2.0.1.0 - 64 bit Production

  With partitioning, OLAP, Data Mining and Real Application Testing options

  SQL > create table test (ID);

  Table created.

  SQL > insert into values test (1);

  1 line of creation.

  SQL > commit;

  Validation complete.

  2. backup the current database:

  rman target $ /.

  Recovery Manager: release 11.2.0.1.0 - Production Fri Apr 17 22:56:44 2014

  Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

  connected to target database: ORACLE (DBID = 1672007929)

  RMAN > backup database;

  From 17 April 14 backup
  using the control file of the target instead of recovery catalog database
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: SID = 6 type of device = DISK
  channel ORA_DISK_1: starting full datafile from backup set
  channel ORA_DISK_1: specifying datafile (s) in the backup set
  Enter a number of file datafile = 00001 name=/u01/app/oracle/oradata/oracle/system01.dbf
  Enter a number of file datafile = name=/u01/app/oracle/oradata/oracle/sysaux01.dbf 00002
  Enter a number of file datafile = name=/u01/app/oracle/oradata/oracle/undotbs01.dbf 00003
  Enter a number of file datafile = 00005 name=/u01/app/oracle/oradata/oracle/example01.dbf
  Enter a number of file datafile = name=/u01/app/oracle/oradata/oracle/users01.dbf 00004
  channel ORA_DISK_1: from room 1 to 17 April 14
  channel ORA_DISK_1: finished piece 1 to 17 April 14
  piece handle=/u01/app/oracle/flash_recovery_area/ORACLE/backupset/2014_04_17/o1_mf_nnndf_TAG20140417T230734_9o1j980f_.bkp tag = TAG20140417T230734 comment = NONE
  channel ORA_DISK_1: complete set of backups, time: 00:00:57
  channel ORA_DISK_1: starting full datafile from backup set
  channel ORA_DISK_1: specifying datafile (s) in the backup set
  including the current control in the backup set file
  including current SPFILE in the backup set
  channel ORA_DISK_1: from room 1 to 17 April 14
  channel ORA_DISK_1: finished piece 1 to 17 April 14
  piece handle=/u01/app/oracle/flash_recovery_area/ORACLE/backupset/2014_04_17/o1_mf_ncsnf_TAG20140417T230734_9o1jc09s_.bkp tag = TAG20140417T230734 comment = NONE
  channel ORA_DISK_1: complete set of backups, time: 00:00:01
  Backup finished on 17 April 14

  3. change the data in the test table

  $ sqlplus / as sysdba

  SQL * more: Production of release 11.2.0.1.0 Thu Apr 17 23:10:16 2014

  Copyright (c) 1982, 2009, Oracle.  All rights reserved.

  
  Connected to:
  Oracle Database 11 g Enterprise Edition Release 11.2.0.1.0 - 64 bit Production
  With partitioning, OLAP, Data Mining and Real Application Testing options

  SQL > select * from test;

  ID
  ----------
  1

  SQL > update test set ID = 2;

  1 line update.

  SQL > commit;

  Validation complete.

  4. restore the database

  RMAN target /.

  Recovery Manager: release 11.2.0.1.0 - Production Fri Apr 17 23:11:15 2014

  Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

  connected to target database: ORACLE (DBID = 1672007929)

  RMAN > shutdown immediate;

  using the control file of the target instead of recovery catalog database

  database closed

  dismounted database

  Instance Oracle to close

  RMAN > bootable media.

  connected to the database target (not started)

  Oracle instance started

  mounted database

  Total System Global Area 835104768 bytes

  Bytes of size 2217952 fixed

  629147680 variable size bytes

  197132288 of database buffers bytes

  Redo buffers 6606848 bytes

  RMAN > restore database;

  From restoration to April 17, 14

  allocated channel: ORA_DISK_1

  channel ORA_DISK_1: SID = 156 type device = DISK

  channel ORA_DISK_1: from the restore backup set data file

  channel ORA_DISK_1: specifying datafile (s) to restore from backup set

  channel ORA_DISK_1: restore datafile 00001 to /u01/app/oracle/oradata/oracle/system01.dbf

  channel ORA_DISK_1: restore datafile 00002 to /u01/app/oracle/oradata/oracle/sysaux01.dbf

  channel ORA_DISK_1: restore datafile 00003 to /u01/app/oracle/oradata/oracle/undotbs01.dbf

  channel ORA_DISK_1: restore datafile 00004 in /u01/app/oracle/oradata/oracle/users01.dbf

  channel ORA_DISK_1: restore datafile 00005 to /u01/app/oracle/oradata/oracle/example01.dbf

  channel ORA_DISK_1: backup /u01/app/oracle/flash_recovery_area/ORACLE/backupset/2014_04_17/o1_mf_nnndf_TAG20140417T230734_9o1j980f_.bkp piece reading

  channel ORA_DISK_1: room handle=/u01/app/oracle/flash_recovery_area/ORACLE/backupset/2014_04_17/o1_mf_nnndf_TAG20140417T230734_9o1j980f_.bkp tag = TAG20140417T230734

  channel ORA_DISK_1: restored the backup part 1

  channel ORA_DISK_1: restore complete, duration: 00:00:55

  Restoration finished in 17 April 14

  RMAN > restore database;

  To go back to April 17, 14

  using channel ORA_DISK_1

  starting media recovery

  media recovery complete, duration: 00:00:03

  Finished recover at April 17, 14

  RMAN > sql 'alter database open;

  SQL statement: alter database open

  5. check if the data has been restored

  sqlplus / as sysdba

  SQL * more: Production of release 11.2.0.1.0 Thu Apr 17 23:14:39 2014

  Copyright (c) 1982, 2009, Oracle.  All rights reserved.

  
  Connected to:
  Oracle Database 11 g Enterprise Edition Release 11.2.0.1.0 - 64 bit Production
  With partitioning, OLAP, Data Mining and Real Application Testing options

  SQL > select * from test;

  ID
  ----------
  2

  Summary:

  Data has not changed. Provided the ID is 1, but after the success of data recovery is not restored (ID is always 2).

  Can someone help me? What I am doing wrong?

  Database is Oracle 11 g with archivelog active

  Ol6 2.6.39 Linux OS - 300.17.2.el6uek.x86_64

  RMAN > restore database;

  To go back to April 17, 14

  using channel ORA_DISK_1

  starting media recovery

  media recovery complete, duration: 00:00:03

  Finished recover at April 17, 14

  RMAN > sql 'alter database open;

  SQL statement: alter database open

  5. check if the data has been restored

  sqlplus / as sysdba

  SQL * more: Production of release 11.2.0.1.0 Thu Apr 17 23:14:39 2014

  Copyright (c) 1982, 2009, Oracle.  All rights reserved.

  Connected to:
  Oracle Database 11 g Enterprise Edition Release 11.2.0.1.0 - 64 bit Production
  With partitioning, OLAP, Data Mining and Real Application Testing options

  SQL > select * from test;

  ID
  ----------
  2

  Summary:

  Data has not changed. Provided the ID is 1, but after the success of data recovery is not restored (ID is always 2).

  Can someone help me? What I am doing wrong?

  Database is Oracle 11 g with archivelog active

  the recovery was successful, but achieved your goal.

  There are several options to reach your goal to recover your database to a particular State that is point in time.

  1 restore the file of control as noted above. you restore the control file must not be aware of the generated once archivelog that you update your table. IE backup controlfile prior you updatedyour table.

  2. do not apply archivelog all during recovery. You can use SNA, SEQUENCE, RESTORE POINT option of the recover command. This option requires that you open your database with resetlog.

  read: scene of Flashback and the database Point-in - time recovery

  After a restore successful your database (before the recover command), you can "alter database open read-only" to check and confirm the values in the table.

  HTH

  Tobi

• is validate the restore of the databases fairly

  Hi guys
  
  Is it enough to perform this restore validate sufficient data to prove that the databases can be restored?
  
  Please tell me whether or not.
  
  Thank you

  Hi haggy_fleisch,

  Oracle documentation.

  RESTORATION... VALIDATE causes RMAN select existing backups that she would use to perform a RESTORE operation and scan them all to make sure that they are present and free of corruption.

  If this seems sufficient.

  There is an argument for actually performing a restore (or duplicate) so not only a scan is performed, but also a write to the disk in a way a little more tests.

  Kind regards

  Tycho

• Full restore of the database of RMAN cross-platform

  All the
  
  I have a database 10.2.0.3 on Solaris 10 OS.
  
  I did a full upward (level 0) this database using rman with auto save on. I'm trying to worl on a scenario where I could restore that backup on another linux machine. so I copied all the elements on the target linux server backup. go to a local installation of RDBMS (10.2.0.3) on the linux machine I'm trying to restore the database... but does not yet...
  
  When I deliver restore spfile or restore the control file a + < backup file name > +; the guest continues search in rear location that responded to the questionnaire didn't tell no piece found backup... Here are the encode stage, I'm...
  
  
  1. set up env on the linux server
  
  2 rman target /.
  
  (instance not started but rman to connect)
  
  3 set the DBID = + < ID DB data source running on Solaris > +.
  
  It run set dbid =
  
  4 startup nomount
  
  as the pfile/spfile file is not available in $ORACLE_HOME/dbs on a linux machine picks it up pfile by default however, but the instance stars no Assembly...
  
  5 restore spfile to ' / u01/app/oracle/product/10.2.0/rman_bkp/c-300009955'
  
  Here, he is not able to restore any thing.same is the case with the control file.
  
  Ideas please advice
  
  Sarat

  Sarat Chandra C wrote:
  Thanks for the referance. Now, I understand that I am not able to use the transportable database command to carry the entire db. However, there is a line in the 'Cross-Platform Database Transportable Restrictions' that says ++ 'main restricting cross-platform transportable database is that the platform of source and destination must share the same endian format. For example, while you can transport a database from Microsoft Windows to Linux for x 86 (the two little endian) or HP - UX, Aix (the two big endian), you may not carry a set of base HP_UX to Linux for x 86 using this feature. You can, however, create a new database on a destination manually, and necessary transport of tablespaces of the source database platform using cross-platform transportable tablespace as described in "Cross - Platform Tranportation Tablespace: CONVERT DATAFILE or TABLESPACE. » +

  I understand that if we are willing to carry each tablespace from Source to target individually, may then be able to replicate a transportable database. Fact the transportable tablespace have not all restrictions has obtained from the database of transport compared to the platform and Endian? Please specify.

  Also is there a matrix of support for thr transportable database and tablespaces which we could see?

  Kind regards!
  Sarat

  Sarat,

  The same restriction that is there for the transport of the whole base is quite real for the transportable tablespace as well if you go to the cross-platform. Endian must match across platforms that only you can do otherwise, as the database feature, you must convert the source file to the target-endian.

  If you look at the doc of reference order of unlocking Tablespace
  http://download.Oracle.com/docs/CD/B19306_01/backup.102/b14194/rcmsynta063.htm#RCMRF1919

  This restriction is documented here in addition to the other restrictions
  ,
  >
  Restrictions and antonyms

  Limitations on the creation of tablespace portable games described in the Oracle database administrator's Guide apply to transport backup storage spaces, with the exception of accountability read-only storage.

  TRANSPORT TABLESPACE does not format endian conversion. If the target platform has a different endian format, you must use the CONVERT RMAN command to perform the separate step of conversion of data files endian format portable overall.
  >

  HTH
  Aman...

• 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

• A new question on how to enable Flashback Database on the database pending?

  Best practical side says:
  
  Activate the Flashback Database on the database shall minimize downtime for logical corruption.
  
  I would like to know where to find the document or everybody already had experience in this topic?
  
  Also, I would like to know what is the best practice for backup/restore of the database of physical relief?
  
  Thanks in advance.

  Hello;

  Just an opinion, but I like the book 'Oracle Data Guard 11g Handbook' as the document and the answers to the second question.

  Chapter 12 covers the A to Z of RMAN with Data Guard.

  This book sold me since Flashback Flashback allows a former primary database to be reinstated after a failover with ongoing restoration operation (provided that enough newspaper flashback is available)

  My own experience is I tried a test failover without it and trash my primary test.

  I did a test of simple failover a few weeks ago, here are my notes.

  http://www.Visi.com/~mseberg/Data_Guard_Failover_Test_using_SQL.PDF

  Best regards

  mseberg

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

• Recover the database failed after restoration

  Dear people,

  We are trying to restore the RMAN backup on another Linux machine. We did this activity several times. The backup has been taken from a RAC instance and we are trying to restore to RAC. After the success of the restoration of the data files, while we publish "recover the database'; It ends with the following error messages:

  RMAN-00571, RMAN-00569
  RMAN-03002 recover command failed

  RMAN-11003 failure during parsing / execution of the sql statement: alter database recover if necessary until cancel using backup control file

  ORA-19801: DB_RECOVERY_FILE_DEST initialization parameter is not defined

  ORA-00280: change 123123213123213123 thread 1 is in sequence #10787

  Kind regards

  Ali

  ProDBA wrote:

  Dear people,

  We are trying to restore the RMAN backup on another Linux machine. We did this activity several times. The backup has been taken from a RAC instance and we are trying to restore to RAC. After the success of the restoration of the data files, while we publish "recover the database'; It ends with the following error messages:

  RMAN-00571, RMAN-00569
  RMAN-03002 recover command failed

  RMAN-11003 failure during parsing / execution of the sql statement: alter database recover if necessary until cancel using backup control file

  ORA-19801: DB_RECOVERY_FILE_DEST initialization parameter is not defined

  ORA-00280: change 123123213123213123 thread 1 is in sequence #10787

  Kind regards

  Ali

  1. as you have said several times, you performed the restore, then you have not yet checked the parameter above so defined or not?

  2. I hope that its very easy to understand ENGLISH characters

  3 try to correctly set the parameter and size, try again to display the error (since some changes for thread 1 is necessary (hopefully, you gave 123 repeatedly instead of posting of the number of real change in your message))

  -Pavan Kumar N

• can't understand why an extract of the database restore fails (missing archive logs)

  Dear,

  I'm completely back up my database ensures every night with following statement.

  full backup AS BACKUPSET COMPRESSED ORCL_FULL_STBY format database tag ' / oradata/archive/fast_recovery_area/%d_%T_%s_%p_FULL_STBY' more tag ORCL_FULL_STBY archivelog delete all entries;

  I wanted to check with 'restore... Preview' if my backup is good enough to restore the database from scratch.
  result = failed!
  Reason:
  "any backup log archived for thread 1 with sequence 65 and YVERT departure from 49020676 found to restore."

  I have read the documentation oracle and articles for days, but I did not understand that even though I take online backup yesterday if I want to restore my database today I still need archival newspapers last month?

  can you please review my analysis and tell me where I am doing wrong?

  for example a piece from my last backup;

  Time of accomplishment BS key Type LV size device Type elapsed time
  ------- ---- -- ---------- ----------- ------------ ---------------
  1008 full 199.25 M DISK 00:04:44 October 8, 15
  BP key: 1010 situation: AVAILABLE Tablet: YES Tag: ORCL_FULL_STBY
  Item name: / oradata/archive/fast_recovery_area/QIPDB1_20151008_1057_1_FULL_STBY
  List of defined backup data files 1008
  Name of file LV Type cash SNA cash time
  ---- -- ---- ---------- --------- ----
  50570723 full 1 8 October 15 /oradata/data/qipdb1/system01.dbf
  4 integer 50570723 8 October 15 /oradata/data/qipdb1/users01.dbf

  as you can see "Cash SNA" is 50570723 so tells me that my understanding if restore these backups I need archived newspapers on top of the YVERT.
  for me the best candidate is

  Time of accomplishment time BS key size Device Type
  ------- ---------- ----------- ------------ ---------------
  65,25 M 1004 00:01 DRIVE: 24 OCTOBER 8, 15
  BP key: 1006 situation: AVAILABLE Tablet: YES Tag: ORCL_FULL_STBY
  Part name: /oradata/archive/fast_recovery_area/QIPDB1_STBY/backupset/2015_10_08/o1_mf_annnn_ORCL_FULL_STBY_c1dkfw9k_.bkp

  List of newspapers archived in backup set 1004
  The next time that THRD Seq YVERT low low time next YVERT
  ---- ------- ---------- --------- ---------- ---------
  1 79 50310555 7 OCTOBER 15 50570723 8 OCTOBER 15
  
  BUT out of "restore...". Preview' RMAN stil tells me that

  any backup log archived for thread 1 with sequence 65 and YVERT departure from 49020676 found to restore
  any backup log archived for thread 1 with sequence 66 and YVERT departure from 49020693 found to restore
  any backup log archived for thread 1 with sequence 67 and YVERT departure from 49020696 found to restore
  any backup log archived for thread 1 with sequence 68 and YVERT departure from 49020761 found to restore
  any backup log archived for thread 1 with sequence 69 and YVERT departure from 49020836 found to restore
  any backup log archived for thread 1 with sequence 70 and YVERT departure from 49020919 found to restore
  any backup log archived for thread 1 with sequence 71 and YVERT departure from 49021021 found to restore
  any backup log archived for thread 1 with sequence 72 and YVERT departure from 49155291 found to restore
  any backup log archived for thread 1 with sequence 73 and YVERT departure from 49324912 found to restore
  any backup log archived for thread 1 with sequence 74 and YVERT departure from 49498102 found to restore

  When I look at V$ ARCHIVED_LOG I see seems indeed to these archived logs removed for cause of "more tag ORCL_FULL_STBY archivelog delete all entries ' that they have been deleetd after saving.
  and because of my retention policy and script; I remove the logs also archived backups that are more than 2 days.

  S SEQUENCE # FIRST_CHANGE # NEXT_CHANGE #.
  - ---------- ------------- ------------
  65 49020676 49020693 D
  A 49020693 OF 49020676 65
  D 68 49020761 49020836
  66 49020693 49020696 D
  67 49020696 49020761 D
  69 49020836 49020919 D
  70 49020919 49021021 D
  49155291 49021021 71 D
  72 49155291 49324912 D
  D 73 49324912 49498102
  74 49498102 49632131 D

  I still don't understand why rman complains of the archived logs that are for an older sequence (SNA) as my last backup
  because I was assuming that the concerned newspapers archived should have already applied to these files of data, right?

  My final goal is to deliver below for the case that we have lost everything.

  Run {}
  restore the database;
  recover the database;
  }

  Thanks in advance,
  Halit

  Hi guys,.

  I found the root cause and workaround

  RMAN-06025 - RMAN RESTORE DATABASE OVERVIEW to the backup site asks former newspaper (Doc ID 1599013.1)

  CAUSE Checkpoint_change# standby controlfile not refreshed properly.  BUG 15876029 - RESTORE PREVIEW ASKING OLD ARCHIVE LOG IN STANDBY DATABASE  Closed as DUPLICATE of  BUG 8740124 - CURRENT STANDBY REDO LOG GROUP SHOULD BE INCLUDED IN THE DATABASE BACKUP BY RMAN SOLUTION  1) Workaround is to recreate the standby controlfile.  OR  2) upgrade to 11.2.0.4 or above where Bug 8740124  is fixed  OR  3) check for availability of patch 8740124
  

• Restore the database to the fallback location

  Hi all

  9i

  RHEL5

  I'm doing to restore the database to the startup location.

  Copy the components of backup on the remote server (same directory).

  RMAN target / auxiliary sys/change_on_install@STANDBY

  
  

  Release of Recovery Manager: 9.0.1.1.0 - 64 bit Production

  (c) Copyright 2001 Oracle Corporation. All rights reserved.

  connected to target database: PROD (DBID = 3261937922)

  connected to the auxiliary database: PROD (not mounted)

  Run this command on the side of PROD or side Server backup server?

  He also mentioned @STANDBY, but it has not mentioned in the steps of the process to add the name of WATCH service in TNSNAMES.ora?

  Thank you very much

  JC

  Hello Jenna_c

  I suppose that you created a controlfile to standby to primary (SQL > alter database create standby controlfile as ' / tmp/stby.ctl '; in primary, then copy it to sleep)

  and you have been used for the standby instance nomount (with the settings standby.ora... file) and restore it from the last backup, if you have a backup tape of stb you can restore backup site, if you have a backup to disk, it must be accessible on the same path to the backup site. (NO RECOVERY)...

  Then you have an instance of State nomount standby:

  SQL > alter database base_de_donnees eve of Mount;

  Here, you can create the redologs Eve... it is not mandatory...

  SQL > alter database add standby logfile group 11 ('/ u01/apps/oracle/oradata/STANDBY_redo_11a.dbf',)

  u02/apps/Oracle/oradata/STANDBY_redo_11b.dbf') size 100 M;

  SQL > alter database add standby logfile Group 12 ('/ u01/apps/oracle/oradata/STANDBY_redo_12a.dbf',)

  u02/apps/Oracle/oradata/STANDBY_redo_12b.dbf') size 100 M;

  SQL > alter database add standby logfile Group 13 ('/ u01/apps/oracle/oradata/STANDBY_redo_13a.dbf',)

  u02/apps/Oracle/oradata/STANDBY_redo_13b.dbf') size 100 M;

  SQL > alter system set standby_file_management = auto; (throwing in the primary and standby)

  then, we put an instance ensures in recovery mode:

  SQL > change database recovery managed standby database disconnect from the session.

  in the primary, we check status of dest archive remotely.

  Select * from v$ archive_dest_status;

  sleep mode check us status of recovery:

  SQL > select process, status from v$ managed_standby;

  Kind regards.

• How to restore the database only with redolog, ctl and dbf files

  Hi friends,

  I had an oracle 11g database, but the server is down. So I just save only the DBF, CTL and REDOLOG files. But I couldn't save the file spfile and pwd.

  How to restore this database in the other server? How can I recreate the spfile?

  I hope someone can give me a hand.

  Thank you.

  Hello

  Thanks for all your advice.

  I try to recreate an environment equal to the original.

  I have install windows server 2003 and install the database from oracle 10.1 all default options.

  I create the directory D:\oracle\product\10.1.0\oradata\. Then I put the files (*.) CTL *. DBF, *. Log) in this directory.

  After this, I create a pfile file in: D:\oracle\product\10.1.0\db_1\database\init.ora with only the db_name and the control_file, the compatibility settings.

  Then open a CMD and create a service, set the ORACLE_SID and try to start the database:

  oradim-new - sid

  Set ORACLE_SID =

  sqlplus / as sysdba

  startup nomount pfile='D:\oracle\product\10.1.0\db_1\database\init.ora';

  change the editing of the database;

  ALTER database open;

  And, the open database

  After I install Oracle Sql Developer, and I can connect to instance and check the tables.

  But when I try to do an export of CMD, I get tracking errors:

  Export: Release 10.1.0.2.0 - Production on Jue 30 Abr 10:04:24 2015

  Copyright (c) 1982, 2004, Oracle.  All rights reserved.

  Contrase±a:

  Conectado has: Oracle Database 10 g Enterprise Edition Release 10.1.0.2.0 - product

  ion

  With partitioning, OLAP and Data Mining options

  Exportaci¾n made in el juego WE8MSWIN1252 character y el juego CARAC

  Teres AL16UTF16 NCHAR

  Exportando toda database...

  . exportando tablespace definiciones

  . exportando people

  . exportando usuario definiciones

  . exportando roles

  . exportando recursos costos

  . exportando rollback segmentos definiciones

  . exportando enlaces a the database

  . exportando sequence n·meros

  . exportando directorios alias

  . exportando espacios of numbers in context

  . exportando numbers of Ajas functions bibliotecas

  . exportando tipo p·blico sin¾nimos

  . exportando privado tipo sin¾nimos

  . exportando definiciones objetos types

  . exportando actions y objetos del sistema procedure

  . exportando actions y objetos procedure pre-sequence

  . exportando agrupamiento definiciones

  EXP-00056: is ha UN error 24324 ORACLE sown

  ORA-24324: Service Manager no inicializado

  EXP-00056: is ha UN error 24324 ORACLE sown

  ORA-24324: Service Manager no inicializado

  EXP-00056: is ha UN error 24324 ORACLE sown

  ORA-24324: Service Manager no inicializado

  EXP-00000: the exportaci¾n no ha terminado correctamente

  Someone knows this problem?

  Best regards.

• I use TDE tablespace encriptación and backup is performed (no encriptación rman). I get the error message when you try to restore the database

  I use TDE tablespace encriptación and backup is performed (no encriptación rman). I deleted the database and try to restore the backup. I get the error when you try to restore the database with rman restore database.

  ORA-19870: error when restoring backup piece + FRA_DG, oratst, backupset, 2015_03_2

  ORA-19913: could not decrypt the backup

  ORA-28365: portfolio is not open

  About what I know, you should be able to RESTORE the data, but no RECOVERY without portfolio being opened.

  Check the value of the variable environment - ORACLE_UNQNAME

  It has everything first a correct value and try to open the wallet.

  HTH,

  Pradeep

• Restore the database to 10.2.0.1 (should I restore old saved oraInventory)?

  Hello everyone;

  Hello!  Hello all;

  If the upgrade process fails, should I restore old oraInventory directory?

  Already I have saved $ORACLE_HOME, oraInventory and consistent copy of the data files, controlfiles and redo log files.

  
  

  I restored $ORACLE_HOME and consistent copy of the data files, controlfiles and redo log files.

  Once again, should I restore (old oraInventory saved) directory?

  
  

  Thanks in advance...
  

  
  

  
  

  There are two parts to your upgrade-

  1. install the 10.2.0.4 patch on top of the binary 10.2.0.1 - you must save $ORACLE_HOME and oraInventory directories before applying the patch - if the binary upgrade fails for any reason, you can restore the ORACLE_HOME and oraInventory to backups and re-apply the binary 10.2.0.4.

  2 If the above step is successful, then you must update the database using DBUA. Yet once, before you begin the upgrade, you back up the database. If there are problems during this part, you simply restore the database from backup and re-run the upgrade.

  You can certainly use two separate houses if you wish. In this case, the first step would be to clone the 10.2.0.1 existing HOUSES a new 10.2.0.1 see HOME - cloning an Oracle Home

  Once completed the clone, and then use the two steps above on the newly created HOUSE

  HTH
  Srini

• The amendments are not expected to be replaced by "restore database; recover the database; » ?

  Hello

  I just have to experience.

  I create a test table and some inserted rows. The I took a full backup of the database more archivelog. Then I insert more than a few lines in the test table. Then the database to stop and he started in the State of EDITING.

  Then RMAN, I made the following two commands after connection to this database as target database:

  RMAN > restore database;

  RMAN > restore database;

  After the success of the recovery operation, I opened the database. Then, I questioned the test table. I expected to see only the rows that have been inserted before the last full backup, but I can see all rows that were inserted into the table of this test. I am little confused - I thought that "restore and recover" a full backup will overwrite the existing State of the database. I expect that the State of data (database) will be exactly the same as it was at the full backup.

  Now I think I got a bad concept, but could someone please clarify this?

  Best regards

  Since you did not specify a point in time recovery Oracle used the rman backup files including archivelogs and redo to roll forward to the top in its last consistent state.

  Do not know what you were doing to the database before you did the recovery, but if you were to try again but to delete all data files, file archivelog and repeat then try recover again you would only see then the first set of rows.