RMAN 'unrecoverable report '.

Similar Questions

• What is unrecoverable; report

  RMAN > unrecoverable report;
  
  Files report requiring a backup due to unrecoverable operations
  Type of file backup name required
  ---- ----------------------- -----------------------------------
  22 full or incremental /u02/proddata/a_txn_data01.dbf
  23 full or incremental /u02/proddata/a_txn_data02.dbf
  24 full or incremental /u02/proddata/a_txn_data03.dbf
  39 full or incremental /u02/proddata/a_txn_data04.dbf
  
  
  each time indicates this value after the rman full backup
  
  
  Why and what is the solution

  Hello

  What should be the database logging or NOLOGGING mode.

  Not to be confused with Operation FORESTIERE/NOLOGGING/ARCHIVELOG NOARCHIVELOG.

  A database may be in ARCHIVELOG mode and have Tables / Tablespaces using the NOLOGGING to allow unregistered operations.

  A non-logged operation can improve performance in some cases (heavy,...), but should be used with caution. If you need to recover a database in which there were a non documented DML, some blocks may be marked as corrupted.

  NOLOGGING mode must therefore be limited to Tables that you can re-create and reload easily. For example, the temporary Tables that does not store permanent data.

  Otherwise, avoid using the NOLOGGING mode in database Production.

  Please find attached a very interesting link on this topic:

  http://asktom.Oracle.com/pls/Apex/f?p=100:11:0:P11_QUESTION_ID:5280714813869

  Hope this helps.
  Best regards
  Jean Valentine

• Unrecoverable report

  Hi all
  
  After a day of my full database backup (DB in 11.2.0 in archive mode) unrecoverable report in rman list some data files having sunk some modification. It does not imply that changes can not be recovered as the operations are performed in nologging mode? If Yes, how can I identify these unrecoverable changes and get rid of them.
  I don't want my database into force logging it as production and that he could be an impact on performance. Please suggest how to deal with this situation.
  
  Thanks for your time.

  You should focus your search for problem to only the following object types.

  The logging_clause lets you specify whether creation of a database object will be logged in the redo log file (LOGGING) or not (NOLOGGING).
  
  You can specify the logging_clause in the following statements:
  
      *      CREATE TABLE and ALTER TABLE: for logging of the table, a table partition, a LOB segment, or the overflow segment of an index-organized table (see CREATE TABLE and ALTER TABLE).
      *      CREATE INDEX and ALTER INDEX: for logging of the index or an index partition (see CREATE INDEX and ALTER INDEX).
      *      CREATE MATERIALIZED VIEW and ALTER MATERIALIZED VIEW: for logging of the materialized view, one of its partitions, or a LOB segment (see CREATE MATERIALIZED VIEW and ALTER MATERIALIZED VIEW).
      *      CREATE MATERIALIZED VIEW LOG and ALTER MATERIALIZED VIEW LOG: for logging of the materialized view log or one of its partitions (see CREATE MATERIALIZED VIEW LOG and ALTER MATERIALIZED VIEW LOG).
      *      CREATE TABLESPACE and ALTER TABLESPACE: to set or modify the default logging characteristics for all objects created in the tablespace (see CREATE TABLESPACE and ALTER TABLESPACE).
  

  SQL> select LOGGING     , count(*) from dba_tablespaces group by LOGGING     ;
  
  LOGGING     COUNT(*)
  --------- ----------
  LOGGING         4
  NOLOGGING        2
  

  Published by: sb92075 on November 7, 2010 07:38

• extract from catalog rman backup report sorted by host name

  Hi all

  I have a catalog database.

  I have a lot of database running on multiple servers.

  I need to extract the backup report of database catalog sorted by host name.

  Please share all the reporting scripts you have.

  Here is the script that I have to extract the backup report

  Col in the shape of "TIME_SINCE_LAST_BACKUP (HOURS) topic TIME 99999.99

  Col BACKUP_SIZE column titled "BACKUP_SIZE (GB)"

  Neck backup for a12

  Course DURATION col ' BACKUP | DURATION | (MIN) "form 999.99

  TIME of col position "TIME_SINCE | LAST_BACKUP | (H) ' train 99999.99.

  col BACKUP_SIZE column headers "BACKUP_SIZE column | (GB) »

  SELECT A.DB_NAME

  , A.OBJECT_TYPE 'BACKUP '.

  (, TO_CHAR(A.START_TIME,'dd/mon/yyyy hh24:mi:ss') START_TIME

  (, TO_CHAR(A.END_TIME,'dd/mon/yyyy hh24:mi:ss') END_TIME

  , ROUND ((A.END_TIME - A. (START_TIME) * 24 * 60, 2) DURATION

  , ROUND ((SYSDATE - A. (END_TIME) * 24: 2) TIMES

  ROUND (OUTPUT_BYTES/1024/1024/1024,2) BACKUP_SIZE COLUMN

  OF rman. RC_RMAN_STATUS, A.

  (SELECT DB_NAME, OBJECT_TYPE

  MAX (END_TIME) END_TIME

  OF rman. RC_RMAN_STATUS

  WHERE

  OBJECT_TYPE IN ('FULL DB","DB INCR")

  AND

  STATUS like '% COMPLETE '.

  AND

  OPERATION ("BACKUP", "BACKUP COPYROLLFORWARD")

  DB_NAME, OBJECT_TYPE) B

  WHERE A.OBJECT_TYPE IN ('FULL DB", 'DB INCR', 'ARCHIVELOG')

  AND

  STATUS like '% COMPLETE '.

  AND

  OPERATION ("BACKUP", "BACKUP COPYROLLFORWARD")

  AND

  A.DB_NAME = B.DB_NAME

  AND

  A.END_TIME = B.END_TIME

  AND A.OBJECT_TYPE = B.OBJECT_TYPE and

  A.end_time > sysdate - 1.5

  ORDER BY 2,1 desc;

  Hello

  I think you need to create your own table and add the entry for the server name, database and DBID and then use this table in your query with join column DBID.

  HTH

• report unrecoverable_change # and unrecoverable rman

  I run a test db oracle 11 GR 2 on windows server 2008.
  
  I'm under oracle proposed the strategy of backup for my backup operation.
  
  So every night I run incremental backup and apply the previous additional costs associated with copies of the image.
  
  I'm confused on why when I run a query like
  
  Select the case number, name, unrecoverable_change #, unrecoverable_time from v$ datafile
  
  I have at least one or two files of data which unrecoverable_change # and unrecoverable_time value is not 0.
  
  If the operation was in nologging or not, since I have a why, incremental backup is the value preceding not 0?
  
  However when I run in rman,
  unrecoverable report;
  
  RMAN does not indicate anything. So what is the difference b/w rman unrecoverable and v$ datafile?
  
  can someone help me understand the correct concept of unrecoverable_change #?
  
  Thank you.

  Yes, it's true. At least with Oracle XE as show in the following test case:

  SQL> select name, unrecoverable_change#, unrecoverable_time from v$datafile where file#=1;
  
  NAME
  --------------------------------------------------------------------------------
  
  UNRECOVERABLE_CHANGE# UNRECOVER
  --------------------- ---------
  C:\ORACLEXE\ORADATA\XE\SYSTEM.DBF
                      0
  
  SQL> select name, unrecoverable_change# UC, unrecoverable_time UT from v$datafile where file#=1;
  
  NAME
  --------------------------------------------------------------------------------
  
          UC UT
  ---------- ---------
  C:\ORACLEXE\ORADATA\XE\SYSTEM.DBF
           0
  
  SQL> desc t;
  ERROR:
  ORA-04043: object t does not exist
  
  SQL> create table t(x int) nologging;
  
  Table created.
  
  SQL> insert /*+ APPEND */ into t select object_id from dba_objects;
  
  12616 rows created.
  
  SQL> commit;
  
  Commit complete.
  
  SQL> select name, unrecoverable_change# UC, unrecoverable_time UT from v$datafile where file#=1;
  
  NAME
  --------------------------------------------------------------------------------
  
          UC UT
  ---------- ---------
  C:\ORACLEXE\ORADATA\XE\SYSTEM.DBF
     2004176 16-SEP-10
  
  SQL> exit
  Disconnected from Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
  
  C:\>rman target /
  
  Recovery Manager: Release 10.2.0.1.0 - Production on Thu Sep 16 20:59:51 2010
  
  Copyright (c) 1982, 2005, Oracle.  All rights reserved.
  
  connected to target database: XE (DBID=2607125346)
  
  RMAN> report unrecoverable;
  
  using target database control file instead of recovery catalog
  Report of files that need backup due to unrecoverable operations
  File Type of Backup Required Name
  ---- ----------------------- -----------------------------------
  1    full or incremental     C:\ORACLEXE\ORADATA\XE\SYSTEM.DBF
  
  RMAN> backup incremental level 1 datafile 1;
  
  Starting backup at 16-SEP-10
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: sid=25 devtype=DISK
  channel ORA_DISK_1: starting incremental level 1 datafile backupset
  channel ORA_DISK_1: specifying datafile(s) in backupset
  input datafile fno=00001 name=C:\ORACLEXE\ORADATA\XE\SYSTEM.DBF
  channel ORA_DISK_1: starting piece 1 at 16-SEP-10
  channel ORA_DISK_1: finished piece 1 at 16-SEP-10
  piece handle=C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\BACKUPSET\2010_09_16\
  O1_MF_NNND1_TAG20100916T210031_694TBHLT_.BKP tag=TAG20100916T210031 comment=NONE
  
  channel ORA_DISK_1: backup set complete, elapsed time: 00:00:15
  channel ORA_DISK_1: starting incremental level 1 datafile backupset
  channel ORA_DISK_1: specifying datafile(s) in backupset
  including current control file in backupset
  including current SPFILE in backupset
  channel ORA_DISK_1: starting piece 1 at 16-SEP-10
  channel ORA_DISK_1: finished piece 1 at 16-SEP-10
  piece handle=C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\BACKUPSET\2010_09_16\
  O1_MF_NCSN1_TAG20100916T210031_694TC04T_.BKP tag=TAG20100916T210031 comment=NONE
  
  channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
  Finished backup at 16-SEP-10
  
  RMAN> report unrecoverable;
  
  Report of files that need backup due to unrecoverable operations
  File Type of Backup Required Name
  ---- ----------------------- -----------------------------------
  
  RMAN>
  

  And you still have:

  C:\>sqlplus / as sysdba
  
  SQL*Plus: Release 10.2.0.1.0 - Production on Thu Sep 16 21:08:27 2010
  
  Copyright (c) 1982, 2005, Oracle.  All rights reserved.
  
  Connected to:
  Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
  
  SQL> select name, unrecoverable_change# UC, unrecoverable_time UT from v$datafile where file#=1;
  
  NAME
  --------------------------------------------------------------------------------
  
          UC UT
  ---------- ---------
  C:\ORACLEXE\ORADATA\XE\SYSTEM.DBF
     2004176 16-SEP-10
  

  Edited by: P. Forstmann on 16 September. 2010 21:07

• Fatal or not?

  2-node RAC on 11.2.0.3.5 on Solaris Sparc 11.1

  When I run this query:

  SQL > select file #, unrecoverable_time, unrecoverable_change # from v$ datafile where unrecoverable_time is not null;

  FILE # UNRECOVER UNRECOVERABLE_CHANGE #.

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

  5-10 NOVEMBER 12 1774222

  94 10 NOVEMBER 12 15263028

  106 10 NOVEMBER 12 15262676

  240 10 NOVEMBER 12 15258111

  244 10 NOVEMBER 12 15259701

  250 10 NOVEMBER 12 15262273

  254 10 NOVEMBER 12 15260190

  256 10 NOVEMBER 12 15261471

  291 10 NOVEMBER 12 1776582

  318 10 NOVEMBER 12 15256886

  349 10 NOVEMBER 12 15261876

  351 10 NOVEMBER 12 15260644

  12 selected lines.

  ... It tells me that there are 12 data files that are unrecoverable. It's something the utility raccheck takes over and gives me a "failure" for recovery of file data accordingly.

  But the database logging mode force (lit on June this year). Then, when I check with RMAN:

  RMAN > unrecoverable report;

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

  Files report requiring a backup due to unrecoverable operations

  Type of file backup name required

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

  RMAN >

  ... I thought that nothing is unrecoverable, that's what I initially planned.

  Is that what I can do to remove the data from dba_data_files so that the utility raccheck choke on it every time? Or is there a real problem that raccheck is picking up that RMAN ignores?

  I think you are badly understand the meaning of these columns DATAFILE V$. Documentation:

  Unrecoverable change last number makes this data file. If the database is in ARCHIVELOG mode, then this column is updated when a fatal operation is finished. If the database is not in ARCHIVELOG mode, this column does not get updated.

  Timestamp of the last fatal change. This column is updated only if the database is in ARCHIVELOG mode.

  As you can see on 10 November 2012 there are transactions for these data files which are sunk, probably because of NOLOGGING. It will be a problem only if you want to restore a backup of 2012 and recover data to this particular SCN files. These columns display the LAST RCS of the LAST IMPOSSIBLE operation performed on these data files. You would be able to recover them at any time after November 10, 2012.

  RMAN does not report this because it takes into account your current backups. RMAN is you say that everything is OK to be restored to any point in time on your retention (time based or based redudancy) policy. For example, if you did a NOLOGGING INSERT it would show on RMAN, but it goes away after you take a full backup of the data file after the nologging operation.

  Concerning

• Report unrecoverable rman

  Hello

  I just ran the report unrecoverable on rman (unrecoverable database report) and discovered that there are unrecoverable data files.

  As has been suggested by some forums on the internet, I made a query involving: v$ segment_statistics ss and by limiting to statistic_name = 'direct written physical' and using the unrecoverable_change # on v$ datafile.

  The items returned by the query are essentially business segments, BUT the table space, the table and the lob segment have RECORD = 'YES '. This is where I started to get confused...

  So is my question, possible to say that the objects are loaded for the unrecoverable data file? And if so, except by checking the attributes of the RECORD, that I have to take care of other things (I can exclude the column from the table and lob have been changed on this day/today ' hui)?

  Thank you for your help.

  Best

  Martin

  So, do you have a reported fatal list everyday, even after fresh backups?

  This would mean that these operations are performed every day.

  One option is to set the FORCE_LOGGING at the database level.

  Hemant K Collette

• RMAN: we have a window of recovery of 130 days defined and we use a catalog of recovery, but report need backup doesn't report anything.

  Our first backup was made on April 28, 2015. Some how report need backup don't recount everything that needs to be backed up. Please let me know why it is like that.

  Hello

  When you run rman phrase 'report need backup '?. just after completing a backup complete (including the arch files)?

  If you made a backup today,"report needed backup; ' returns 0.

  I tested in oracle 10 and oracle 11, with the default of 60 days and archivelog retention policy backup every 3 hours.

  * "report need backup 300 recovery window days."

  Returns the value 0.

  * "list backupset summary"

  return values of 60 days so far.

  I reproduced with and without connecting to the catalog.

  Please read the old note:

  How does the REPORT the WINDOW to RETRIEVE NEED BACKUP? (Doc ID 301704.1)

  This is for oracle 9i, but I think you can always apply on oracle 11g

• RMAN how to handle simple full backups every day with the archivelogs

  
  

  
  

  Hello

  My use of Oracle DB is about 200 GB on a file system 1 TB from a NetApp file server. (i.e. 20% currently use)

  I'm not so attracted to use the RMAN catalog for the love of simplicity.

  Also, I have an affinity to run a full backup "Instant NetApp" every day, without running all the incremental backups.

  My snapshots of NetApp have a framework for the retention of 7 days.

  I think to implement a RMAN full backup script that includes the following to run every night:

  Run {}

  delete archivelog all;                    (to clean up the archive logs that are accumulated for each day)

  backup database;                          (for a full backup every night)

  }

  This will be a good idea?

  Will this coverage to back up all that I could restore if there is a problem.

  
  

  Part of the great mystery for me is on the restoration of the data that is generated during the execution of the "backup database" command in the RMAN.

  Any advice would be appreciated.

  Thank you!

  -Steve

  If you perform the backup in this order, you will get in big trouble.

  It is preferable to run the backup as follows:

  (1) the following parameters, you have to do only once:

  configure backup optimization

  Configure retention policy to recovery of 7-day window;

  Configure controlfile autobackup on;

  (2) backup every day:

  backup database more entered archivelog delete;

  delete noprompt obsolete;

  unrecoverable report;

  RMAN automatically takes care of cleaning the old backups<7 days="" and="" saved="">

  Concerning

  Patrick

• RMAN backup

  Hi all

  11.2.0.1

  Should I issue the command RMAN OBSOLETE REPORT, before that I can DELETE OBSOLETE backups?

  Is DELETE BACKUP EXPIRES, identical to REMOVE of BACKUPSET EXPIRES?

  Thank you

  zxy

  CONFIGURE RETENTION POLICY TO 1 DAY RECOVERY WINDOW;

  Then run crosscheck backup;

  remove obsolete;

  and back to the desired value

• RMAN switch problem.

  Hi guys, I use a CAR with 2 nodes, Oracle Database 10 g Enterprise Edition Release 10.2.0.5.0 with Linux [a test environment].
  I train in RMAN situations... I was using the comand of switch.
  I did this:
  

  RUN {
  BACKUP DATAFILE 77;
  SQL 'ALTER TABLESPACE NOVO_TBS OFFLINE';
  SET NEWNAME FOR DATAFILE 77 TO '/u01/backup/rman/teste/dfile77_novotbs.abc'
  RESTORE DATAFILE 77;
  SWITCH DATAFILE 77;
  RECOVER DATAFILE 77;
  SQL 'ALTER TABLESPACE NOVO_TBS ONLINE'
  }

  It worked, the data file left ASM to the file system.
  I've done some DML statements in the segments of this data file, and it worked as expected.
  
  Later, another person tried to do a select dba_tablespaces and got this error:
  ORA-01157: cannot identify/lock data file 77 - see DBWR trace file
  ORA-01110: data file 77: ' / u01/backup/rman/teste/dfile77_novotbs.abc'
  
  Then, I tried in my machine and it is so.
  I know that I could put this data file offline and kept operating normally or even upgrade the data file to ASM [works].
  
  But I want to test it on the file system.
  
  I checked it on the rman:
  

  rman target /
  report schema;

  List of permanent data files
  ===========================
  Size (MB) Tablespace RB segs Datafile file name
  75 10 BRUNO * +DATA/atrac/datafile/bruno.335.780773973
  77 100 NOVO_TBS * /u01/backup/rman/teste/dfile77_novotbs.abc
  78 1000 SYSTEM * +DATA/atrac/datafile/system.338.783883557
  
  Anyone know the reason?
  
  Thanks in advance.
  
  Best regards.
  
  Published by: BSalesRashid on 12/14/2012 11:52

  Hi Bruno.
  Forget the semaphores and file descriptors for now.
  I suppose that when you move the file to the ASM files/u01 system you can only see on Atrac1 or Atrac2 but not on both (Please also check the timstamp of the file).
  RAC to your data files on the cluster file systems so that both instances can read and update files.
  Kind regards
  Tycho

• Error during the registration of RMAN from the primary to the catalog database

  Hi all
  
  Here we have an environment with db1 (db_unique_name) 10g dataguard as primary and db2 (db_unique_name) Physics of the standby database. Also, we have configured a schema on a third computer as a database of catalog using following steps.
  
  The measures taken in the catalog database (appsdb):
  
  SQL > create tablespace rmancatlog_tbs datafile ' / u01/app/oracle/oradata/NEW/rman_catalog.dbf' size 500M autoextend extent management local segment space management auto;
  
  SQL > create user rman identified by oracle
  2 default tablespace rmancatlog_tbs
  3 unlimited quota on rmancatlog_tbs
  4;
  
  SQL > GRANT connect, resource, recovery_catalog_owner to rman;
  
  RMAN > create catalog.
  Recovery catalog created
  
  AMT added entries of catalog in primary and standby database. Then the primary database, we have tried to register for the catalog database. It shows that it registers. But all queries later rman throws the error. Here are the steps and the error:
  
  [oracle@db1 ~] $ rman target sys/oracle catalog rman/oracle@appsdb
  Recovery Manager: release 10.2.0.3.0 - Production on Mon Aug 13 21:39:32 2012
  Copyright (c) 1982, 2005, Oracle. All rights reserved.
  connected to target database: NIOS (DBID = 1589015669)
  connected to the recovery catalog database
  
  RMAN > register database;
  registered in the recovery catalog database
  
  RMAN > outline report;
  Report of the database schema
  List of permanent data files
  ===========================
  Size (MB) Tablespace RB segs Datafile file name
  ----
  -------------------- ------------------------
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of command report to the 08/10/2012 06:16:06
  [RMAN-00600: internal error, arguments [8201] [] [] []]
  
  Can anyone help on this error?
  Thanks in advance.

  Hello;

  Then, you have to re-create the controlfile to the target database. (Not funny)

  I like to use the method of trace file myself.

  How to recreate a Controlfile [ID 735106.1]

  Best regards

  mseberg

• RMAN throwing errors during backup Tablespace - RMAN-06004 and RMAN-06019

  Hi all.
  
  
  Please, help me difficulty trail of the error message I get when trying to backup to a tablespace that is newly added in the database. I'm with RMAN as a method of recovery.
  
  Tablespace name: test
  Version of DB: Oracle 10g R1.
  OS: Red Hat Linux 5
  
  
  
  
  RMAN > outline report;
  
  Report of the database schema
  
  List of permanent data files
  ===========================
  Size (MB) Tablespace RB segs Datafile file name
  ---- -------- -------------------- ------- ------------------------
  1 490 SYSTEM YES /u01/app/oracle/oradata/qrcl/system01.dbf
  2 25 UNDOTBS1 /u01/app/oracle/oradata/qrcl/undotbs01.dbf YES
  SYSAUX 3 270 NO /u01/app/oracle/oradata/qrcl/sysaux01.dbf
  4 23 USERS NO /u01/app/oracle/oradata/qrcl/users01.dbf
  5 40 TEST NO /u01/app/test01.dbf
  
  List of temporary files
  =======================
  File Size (MB) (MB) Maxsize Tempfile Tablespace name
  ---- -------- -------------------- ----------- --------------------
  1 20 TEMP /u01/app/oracle/oradata/qrcl/temp01.dbf 32767
  
  RMAN >
  
  
  
  
  
  RMAN > backup tablespace 'test '.
  
  From 22 August 12 backup
  using channel ORA_DISK_1
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the backup command to 22/08/2012 11:57:13
  RMAN-06004: error ORACLE recovery catalog database: RMAN-20202: tablespace not found in the recovery catalog
  RMAN-06019: could not translate tablespace name 'test '.
  
  RMAN > restore tablespace test;
  
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-00558: error occurred during parsing of order entry
  RMAN-01009: syntax error: found 'test': expected an a: 'double-quoted-string, identifier, single-quoted-string '.
  RMAN-01007: in the file column 20 line 1: entry standard
  
  
  
  I tried to update the catalog server but still no luck:
  
  RMAN > RESYNC CATALOG;
  
  from full resynchronization of the recovery catalog
  full complete Resync
  
  
  Please help.
  
  
  
  
  Thank you
  Prashant Dixit

  Prashant;

  I took the time to demonstrate using a tablespace that was NOT a reserved word in the hope that you would see how bad idea using a reserved word is.

  A tablespace is a logical structure and it can be almost any other name.

  Why create this problem yourself when there are simple alternatives?

  Time is the most precious thing in my life and I don't know that it's in yours also.

  Please consider using another name of the tablespace.

  ALTER TABLESPACE TEST RENAME OTEST;

  There is no sense, make things more complex, then they already are.

  If this is really not an option then:

  RMAN> backup tablespace "TEST";
  
  Starting backup at 22-AUG-12
  starting full resync of recovery catalog
  full resync complete
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: SID=88 device type=DISK
  channel ORA_DISK_1: starting full datafile backup set
  channel ORA_DISK_1: specifying datafile(s) in backup set
  input datafile file number=00008 name=/u01/oradata/RECOVER2/test05.dbf
  channel ORA_DISK_1: starting piece 1 at 22-AUG-12
  channel ORA_DISK_1: finished piece 1 at 22-AUG-12
  piece handle=/u01/app/oracle/flash_recovery_area/RECOVER2/backupset/2012_08_22/o1_mf_nnndf_TAG20120822T152734_83bj5pt3_.bkp tag=TAG20120822T152734 comment=NONE
  channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
  Finished backup at 22-AUG-12
  
  Starting Control File and SPFILE Autobackup at 22-AUG-12
  piece handle=/u01/app/oracle/flash_recovery_area/RECOVER2/autobackup/2012_08_22/o1_mf_s_791998056_83bj5rpq_.bkp comment=NONE
  Finished Control File and SPFILE Autobackup at 22-AUG-12
  

  Best regards

  mseberg

  Published by: mseberg on August 22, 2012 15:27

• RMAN cloning to another server

  using 10 gr 1 on windows xp
  I have two dbs
  prod db and db test
  backup database more archivelog prod DB
  create pfile from spfile
  remote access connection password file = exclusive lock
  copied file password
  copy all these files to test site
  created the directory for the data control, redo, fra, cdump, bdump, udump
  changed all sites on pfile
  oradim to create an instance
  Restore controlfile from "'
  This has created 3 control files in the location specified by the modified pfile file that was mentioned during the startup nomount (startup nomount pfile = ")
  change the editing of the database;
  catalog all backup items
  * rman > run {*}
  the value of newname for datafile 1 to "
  *}*
  I did it for all data files
  in editing mode, I have changed the location of the redo log by using alter database files rename file 'oldpath' to the 'new path ';
  I also used db_file_name_convert since
  RMAN > outline report;
  shows more former locations of the data files
  :
  :
  RMAN > restore database;
  gives me
  RMAN > restore database;
  
  From restoration to August 2, 12
  using controlfile target instead of recovery catalog database
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: sid = 160 devtype = DISK
  
  channel ORA_DISK_1: from datafile backupset restoration
  channel ORA_DISK_1: specifying datafile (s) to restore from backup set
  restoring datafile 00001 to E:\ORACLE\PRODUCT\10.1.0\ORADATA\LIBRARY\SYSTEM01. DBF
  restoring datafile 00002 to E:\ORACLE\PRODUCT\10.1.0\ORADATA\LIBRARY\UNDOTBS01. DBF
  restoring datafile 00003 to E:\ORACLE\PRODUCT\10.1.0\ORADATA\LIBRARY\SYSAUX01. DBF
  restoring datafile 00004 to E:\ORACLE\PRODUCT\10.1.0\ORADATA\LIBRARY\USERS01. DBF
  restoring datafile 00005 to E:\ORACLE\PRODUCT\10.1.0\ORADATA\LIBRARY\EXAMPLE01. DBF
  restoring datafile 00006 to E:\ORACLE\PRODUCT\10.1.0\ORADATA\LIBRARY\LIBRARY. DBF
  restoring datafile 00007 to E:\ORACLE\PRODUCT\10.1.0\ORADATA\LIBRARY\LIBRARY2. DBF
  ORA-19624: operation failed, try again possible
  ORA-19504: cannot create the file 'E:\ORACLE\PRODUCT\10.1.0\ORADATA\LIBRARY\LIBRARY2. DBF. "
  ORA-27040: create file error, cannot create the file
  04002 - OSD: could not open the file
  S/O-error: (OS 3) the system cannot find the path specified.
  switch to the previous backup
  
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the restore command to 08-02-2012 09:25:46
  RMAN-06026: some targets not found - abandonment of restoration
  RMAN-06023: no backup or copy of datafile 6 to restore
  RMAN-06023: no backup or copy of datafile 5 found to restore
  RMAN-06023: no backup or copy of the file 4 found to restore
  RMAN-06023: no backup or copy of datafile 3 found to restore
  RMAN-06023: no backup or copy of datafile 2 found to restore
  RMAN-06023: no backup or copy of datafile 1 found to restore
  :
  :
  Help, please
  where I'm going wrong
  Thanks in advance
  
  Edited by: 946207 August 2, 2012 11:34

  DB_FILE_NAME_CONVERT is used RMAN DUPLICATE and pending database.

  You must use the VALUE of NEWNAME if you do a RESTORE RMAN.

  Hemant K Collette

• RMAN-06056 and the data file does not exist

  Hello
  
  I'm working on Oracle 9i Database (9.2.0.8.0) on AIX 5.2 and we try to run a full backup of RMAN, but it seems to be failing with an error as follows;
  
  From backup to 27-SEPT.-10
  using the ORA_SBT_TAPE_1 channel
  using the ORA_SBT_TAPE_2 channel
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the backup to 27/09/2010 01:33:17 command
  RMAN-06056: could not access datafile 23
  
  I checked the v $ datafile and it shows that it is in a State of recovery.
  
  Select the State, file No., name from v$ datafile
  where status <>'in LINE '.
  order by 1
  
  RECOVER /u06/oradata/test_sys/data/msg_log06.dbf 23
  
  The file does not exist at the level of the BONE and the RMAN, it shows as;
  
  RMAN > resync catalog
  + 2 >. +
  
  from full resynchronization of the recovery catalog
  full complete Resync
  
  RMAN > outline report;
  
  Report of the database schema
  K - bytes Tablespace RB segs Datafile file name
  ---- ---------- -------------------- ------- -------------------
  819200 + 1 SYSTEM YES /u011/oradata/test_sys/data/system01.dbf+
  
  + 23 0 MSG_LOG NOT /u06/oradata/test_sys/data/msg_log06.dbf+
  
  The associated tablespace cannot be just deleted given that some other files of dependent data. The RMAN script has also been changed
  
  change archivelog than any overlap;
  backup database more archivelog entry remove
  Skip inaccessible;
  
  But the backup fails again, please advice.
  
  Concerning

  Run

  LIST OF BACKUP OF THE FILE 23

  to see if you have previous backups. If you have a backup of the data file, you can then
  Put the offline data file
  RESTORE the data file
  RECOVER the data file.

  If you want to 'ignore' this test taking it Offline datafile
  ALTER DATABASE DATAFILE OFFLINE 23

  then use "SKIP OFFLINE" in your RMAN BACKUP DATABASE command.

  Hemant K Collette