Is log_file_name_convert in block running rman duplication.

Similar Questions

• DataGuard enviornment, rman duplication showed validation failed

  I have backup rman to backup site installation.
  DB version is GR 11, 2,
  version of the OS is redhat linux
  
  I did the rman duplication, here are some results:
  
  validation failed for the copy of the data file
  DataFile copy file name=+DAT/prd/datafile/system.324.792993247 RECID = 621 STAMP = 793373396
  validation failed for the copy of the data file
  DataFile copy file name=+DAT/prd/datafile/system.314.788073527 RECID = 483 STAMP = 792994113
  validation failed for the copy of the data file
  DataFile copy file name=+DAT/prd/datafile/system.323.786903909 RECID = 343 STAMP = 788102778
  validation failed for the copy of the data file
  DataFile copy file name=+DAT/prd/datafile/system.333.785989831 RECID = 206 STAMP = 786907706
  validation failed for the copy of the data file
  DataFile copy file name=+DAT/prd/datafile/system.347.785963645 RECID = 69 = 785990015 STAMP
  validation failed for the copy of the data file
  DataFile copy file name=+DAT/prd/datafile/sysaux.355.792993227 RECID = 622 STAMP = 793373396
  validation failed for the copy of the data file
  DataFile copy file name=+DAT/prd/datafile/sysaux.293.788073519 RECID = 484 STAMP = 792994113
  validation failed for the copy of the data file
  DataFile copy file name=+DAT/prd/datafile/sysaux.322.786903909 RECID = 344 STAMP = 788102779
  validation failed for the copy of the data file
  DataFile copy file name=+DAT/prd/datafile/sysaux.332.785989833 RECID = 207 STAMP = 786907706
  validation failed for the copy of the data file
  DataFile copy file name=+DAT/prd/datafile/sysaux.346.785963645 RECID = 70 = 785990015 STAMP
  validation failed for the copy of the data file
  DataFile copy file name=+DAT/prd/datafile/undotbs1.351.792993227 RECID = 623 STAMP = 793373396
  validation failed for the copy of the data file
  DataFile copy file name=+DAT/prd/datafile/undotbs1.361.788073413 RECID = 485 STAMP = 792994114
  validation failed for the copy of the data file
  DataFile copy file name=+DAT/prd/datafile/undotbs1.319.786903909 RECID = 345 STAMP = 788102779
  validation failed for the copy of the data file
  DataFile copy file name=+DAT/prd/datafile/undotbs1.258.785989851 RECID = 208 = 786907706 STAMP
  validation failed for the copy of the data file
  DataFile copy file name=+DAT/prd/datafile/undotbs1.345.785963645 RECID = STAMP 71 = 785990015
  validation failed for the copy of the data file
  DataFile copy file name=/oracle_backup/stage/arindex.341.785186191 RECID = 624 STAMP = 793373396
  validation failed for the copy of the data file
  DataFile copy file name=/oracle_backup/stage/arindex.319.713996145 RECID = 346 STAMP = 788102779
  validation failed for the copy of the data file
  DataFile copy file name=+DAT/prd/datafile/undotbs2.291.792993257 RECID = 625 STAMP = 793373396
  validation failed for the copy of the data file
  DataFile copy file name=+DAT/prd/datafile/undotbs2.315.788073545 RECID = 487 STAMP = 792994114
  validation failed for the copy of the data file
  DataFile copy file name=+DAT/prd/datafile/undotbs2.316.786903931 RECID = 347 STAMP = 788102779
  validation failed for the copy of the data file
  DataFile copy file name=+DAT/prd/datafile/undotbs2.348.785989855 RECID = 210 STAMP = 786907706
  validation failed for the copy of the data file
  DataFile copy file name=+DAT/prd/datafile/undotbs2.339.785963789 RECID = 73 = 785990015 STAMP
  validation failed for the copy of the data file
  DataFile copy file name=/oracle_backup/stage/arindex.429.785173115 RECID = 626 STAMP = 793373396
  validation failed for the copy of the data file
  DataFile copy file name=/oracle_backup/stage/arindex.274.713990673 RECID = 348 STAMP = 788102779
  validation failed for the copy of the data file
  DataFile copy file name=+DAT/prd/datafile/ggs_data.290.792993255 RECID = 627 STAMP = 793373397
  validation failed for the copy of the data file
  DataFile copy file name=+DAT/prd/datafile/ggs_data.294.788073529 RECID = 489 STAMP = 792994114
  validation failed for the copy of the data file
  DataFile copy file name=+DAT/prd/datafile/ggs_data.329.786903917 RECID = 349 STAMP = 788102779
  validation failed for the copy of the data file
  DataFile copy file name=+DAT/prd/datafile/ggs_data.257.785989847 RECID = 212 STAMP = 786907706
  validation failed for the copy of the data file
  DataFile copy file name=+DAT/prd/datafile/ggs_data.305.785981949 RECID = 75 = 785990015 STAMP
  validation failed for the copy of the data file
  DataFile copy file name=/oracle_backup/stage/arindex.407.785164105 RECID = 628 STAMP = 793373397
  validation failed for the copy of the data file
  DataFile copy file name=/oracle_backup/stage/arindex.273.713990667 RECID = 350 STAMP = 788102779
  validation failed for the copy of the data file
  DataFile copy file name=/oracle_backup/stage/arsystem.313.785209331 RECID = 629 STAMP = 793373397
  validation failed for the copy of the data file
  DataFile copy file name=/oracle_backup/stage/arsystem.360.770344487 RECID = 351 STAMP = 788102779
  validation failed for the copy of the data file
  DataFile copy file name=/oracle_backup/stage/arsystem.408.785164107 RECID = 630 STAMP = 793373397
  validation failed for the copy of the data file
  DataFile copy file name=/oracle_backup/stage/arsystem.359.770344385 RECID = 352 STAMP = 788102779
  validation failed for the copy of the data file
  DataFile copy file name=/oracle_backup/stage/arsystem.347.785193013 RECID = STAMP 631 = 793373397
  validation failed for the copy of the data file
  DataFile copy file name=/oracle_backup/stage/arsystem.358.770343541 RECID = 353 STAMP = 788102779
  validation failed for the copy of the data file
  DataFile copy file name=/oracle_backup/stage/arsystem.327.785199047 RECID = 632 STAMP = 793373397
  validation failed for the copy of the data file
  Copy file name=/oracle_backup/stage/arsystem.357.770343495 RECID DataFile = 354 STAMP = 788102779
  validation failed for the copy of the data file
  DataFile copy file name=/oracle_backup/stage/arsystem.309.785213677 RECID = 633 STAMP = 793373397
  validation failed for the copy of the data file
  DataFile copy file name=/oracle_backup/stage/arsystem.286.713990693 RECID = 355 STAMP = 788102780
  validation failed for the copy of the data file
  DataFile copy file name=/oracle_backup/stage/arsystem.317.785207493 RECID = 634 STAMP = 793373397
  validation failed for the copy of the data file
  DataFile copy file name=/oracle_backup/stage/arsystem.288.713990693 RECID = 356 STAMP = 788102780
  validation failed for the copy of the data file
  DataFile copy file name=/oracle_backup/stage/arsystem.316.785204659 RECID = 635 STAMP = 793373398
  validation failed for the copy of the data file
  
  How can I remove these entries from invalid rman? I can't overlap with success their.
  
  Thank you

  DataFile copy file name=/oracle_backup/stage/arsystem.288.713990693 RECID = 356 STAMP = 788102780
  validation failed for the copy of the data file
  DataFile copy file name=/oracle_backup/stage/arsystem.316.785204659 RECID = 635 STAMP = 793373398
  validation failed for the copy of the data file

  Have you tried below command?

  RMAN > CHANGE DATAFILECOPY '+ DAT/prd/datafile/undotbs2.339.785963789' UNCATALOG;

• RMAN duplication and expiration of the directives on the environment of data warehouse

  Operating systems: Windows Server 2008
  DB: Oracle 11 g 2
  
  Are there guidelines how often one should do a RMAN duplication and assign an expiration on archivelogs for data warehouse environments?
  It me appears once a day would be enough for overlapping in a data warehouse environment which is updated nightly. Expiration, I don't expect less than 1 week.
  See you soon!

  I agree with damorgan

  See the links for the best practices below.

  http://www.Oracle.com/technetwork/database/features/availability/311394-132335.PDF
  https://blogs.Oracle.com/Datawarehousing/entry/data_warehouse_in_archivelog_m

  Hope this helps,

  Concerning
  http://www.oracleracepxert.com
  Understand the power of the Oracle RMAN
  http://www.oracleracexpert.com/2011/10/understand-power-of-Oracle-RMAN.html
  Duplication of data base RAC with RMAN
  http://www.oracleracexpert.com/2009/12/duplicate-RAC-database-using-RMAN.html

• Only the unused blocks backup RMAN as well?

  DB version: 11.2.0.4

  OS: RHEL 6.6

  If I remember correctly, RMAN backs up only used blocks. I created a tablespace of 20 GB, as shown below. When I backed up, the backup piece is only 4MB in size, as shown below.

  SQL > create tablespace TEST_TS3 datafile '+ DATA_DG' size 20 G

  autoextend on

  MaxSize 32767 m

  Local extended management

  single 4 M size

  Auto segment space management;

  Created tablespace.

  SQL >

  SQL > select tablespace_name, bytes/1024/1024 of dba_Data_Files where nom_tablespace = 'TEST_TS3 ';

  BYTES/1024/1024 NOM_TABLESPACE

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

  TEST_TS3 20480

  Backup tablespace TEST_TS3 that is not used by all segments (empty)

  RMAN > backup tablespace TEST_TS3 format='/u05/RMAN_BKP/TBS_%U_%T.rmbk' tag = TEST_TS3_BKP;

  From 18 February 16 backup

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

  allocated channel: ORA_DISK_1

  channel ORA_DISK_1: SID = 4941 instance = HMAGPRD2 = DISK device type

  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 = name=+DATA_DG/hmagprd2/datafile/test_ts3.413.904152141 00144

  channel ORA_DISK_1: starting piece 1-18 February 16

  channel ORA_DISK_1: finished piece 1-18 February 16

  piece handle=/u05/RMAN_BKP/TBS_03qu8hg2_1_1_20160218.rmbk tag = TEST_TS3_BKP comment = NONE

  channel ORA_DISK_1: complete set of backups, time: 00:00:01

  Backup finished on 18 February 16

  $

  $ ls - lh /u05/RMAN_BKP/TBS_03qu8hg2_1_1_20160218.rmbk

  -rw - r - 1 oracle oinstall 4.1 M 18 Feb 17:29 /u05/RMAN_BKP/TBS_03qu8hg2_1_1_20160218.rmbk

  But in the world of real output, size of the RMAN backups seems to be much higher.

  The following production DB is 27.5 terabytes in size as evidenced by the physical layer (DBA_DATA_FILES. Column of BYTES)

  SQL > select sum(bytes/1024/1024/1024) bytesGB from dba_Data_Files;

  BYTESGB

  ----------

  27885.3252

  But at the level of the logic layer, the used space is only 16.5 TB as evidenced by DBA_EXTENTS. BYTES column

  SQL > select sum(bytes/1024/1024/1024) bytesGB from dba_extents.

  BYTESGB

  ----------

  16621.316

  But the size of RMAN backup came to 20 terabytes , become almost 4TB that space consumed at the level of the logical layer (DBA_EXTENTS. BYTES).

  Why is this?

  RMAN jump blocks that have never been used. If a block has been used in the past, it will be included in the same backup if currently is not used:

  https://docs.Oracle.com/CD/B28359_01/backup.111/b28270/rcmcncpt.htm

  Compression for backup sets

  When you back up the data files of backup sets, RMAN can use unused block compression to skip blocks of data file. RMAN always ignores blocks that have never been used. Under certain conditions, which are listed in the BACKUP AS BACKUPSET entry in reference Oracle database backup and recovery, RMAN also ignores the blocks that are not currently used. Data file backup sets are generally smaller than copies of data file and take less time to write. Compression of the unused block is fundamental to how RMAN writes files of data in backup items and cannot be disabled.

• Active RMAN duplication problem

  Experts,
  
  I am trying to set up a standby database single-server to a primary database RAC, using configurations of data Gaurad. In this process, I finished all the configurations, and I was about to run the RMAN script to duplicate primary DB on Standby DB.
  
  When I turn off the RMAN script, he throws under the errors:
  
  ince the backup to December 5, 11
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: SID = instance 901 = iam1 = DISK device type
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of Db in dual at 05/12/2011 15:31:42
  RMAN-05501: abandonment of duplicate target database
  RMAN-03015: an error has occurred in the script stored memory Script
  RMAN-03009: failure of the backup command on the channel ORA_DISK_1 at 05/12/2011 15:31:42
  ORA-17629: unable to connect to the remote database server
  ORA-17627: ORA-01031: insufficient privileges
  ORA-17629: unable to connect to the remote database server
  
  Additional information:
  
  
  
  --------------------------------------------------------------------------------
  
  -Password is correctly copied the main database and the RAC rescue.
  -Capable to connect to DB primary waiting for database via sqlplus tool.
  -Telnet is conversely works very well.
  -All the pings work correctly.
  
  Please let me know if you have any suggestions. Happy to provide further information if necessary.
  
  Thank you

  Make sure that you should not use the password file that is located under /dbs. There is a folder called "database", where a password file must have been already generated at installation time. Simply copy the file to the same location on the standby node. I hope it should work now.

• Crontab cannot run RMAN

  Hello
  10 g R2 on AIX 6.1, I put in the crontab, execution of myscript. But it returns the following error:

  myscript.sh[8]: rman:  not found

  And I in myscript:
  

  rman catalog rman/**@rep target / LOG=file.log << EOF
  run
  {
          allocate channel t1 type disk;
          .........
  }
  exit
  EOF

  Thanks for help.

  Hello

  I always put it at the beginning of my scripts:

  export ORACLE_SID=ORCL
  export ORAENV_ASK=NO
  . oraenv
  

  This command sets the variables right for you.

  Respect,

  -wiZ

• RMAN Duplication failed on another host

  Hi, I use oracle 10.2.0.4 on solaris 5.10 to duplicate the database of 1 host 2 host. I had tried that before and it was successful, except that the first time I had tried with a smaller database.
  
  Here's the code I ran host 1 and the error message below. Any help would be greatly appreciated:
  

  RMAN> run{
  2> allocate auxiliary channel aux1 device type disk;
  3> allocate auxiliary channel aux2 device type disk;
  4> allocate auxiliary channel aux3 device type disk;
  allocate auxiliary channel aux4 device type disk;
  5> allocate auxiliary channel aux5 device type disk;
  6> 7> allocate auxiliary channel aux6 device type disk;
  duplicate target database to UNOLTSVT;8> }
  
  allocated channel: aux1
  channel aux1: sid=1995 devtype=DISK
  
  allocated channel: aux2
  channel aux2: sid=999 devtype=DISK
  
  allocated channel: aux3
  channel aux3: sid=1994 devtype=DISK
  
  allocated channel: aux4
  channel aux4: sid=998 devtype=DISK
  
  allocated channel: aux5
  channel aux5: sid=2997 devtype=DISK
  
  allocated channel: aux6
  channel aux6: sid=3992 devtype=DISK
  
  Starting Duplicate Db at 07-FEB-11
  
  contents of Memory Script:
  {
     set until scn  1413162899;
     set newname for datafile  1 to
   "/databases/da001/UNOLTSVT/system01.dbf";
     set newname for datafile  2 to
   "/databases/da001/UNOLTSVT/undotbs01.dbf";
     set newname for datafile  3 to
   "/databases/da001/UNOLTSVT/sysaux01.dbf";
     set newname for datafile  4 to
   "/databases/da001/UNOLTSVT/users01.dbf";
     set newname for datafile  5 to
   "/databases/da001/UNOLTSVT/tools01.dbf";
     set newname for datafile  6 to
   "/databases/da001/UNOLTSVT/siebel_data01.dbf";
     set newname for datafile  7 to
   "/index/ix001/UNOLTSVT/siebel_index01.dbf";
     set newname for datafile  8 to
   "/databases/da001/UNOLTSVT/sbl_data_md01.dbf";
     set newname for datafile  9 to
   "/databases/da001/UNOLTSVT/sbl_data_lg01.dbf";
     set newname for datafile  10 to
   "/databases/da001/UNOLTSVT/sbl_data_xl01.dbf";
     set newname for datafile  11 to
   "/databases/da001/UNOLTSVT/sbl_data_xl02.dbf";
     set newname for datafile  12 to
   "/databases/da001/UNOLTSVT/sbl_data_xl03.dbf";
     set newname for datafile  13 to
   "/index/ix001/UNOLTSVT/sbl_idx_md01.dbf";
     set newname for datafile  14 to
   "/index/ix001/UNOLTSVT/sbl_idx_lg01.dbf";
     set newname for datafile  15 to
   "/index/ix001/UNOLTSVT/sbl_idx_xl01.dbf";
     set newname for datafile  16 to
   "/databases/da001/UNOLTSVT/genuser01.dbf";
     set newname for datafile  17 to
   "/index/ix001/UNOLTSVT/siebel_index02.dbf";
     set newname for datafile  18 to
   "/index/ix001/UNOLTSVT/sbl_idx_md02.dbf";
     set newname for datafile  19 to
   "/index/ix001/UNOLTSVT/sbl_idx_xl02.dbf";
     set newname for datafile  20 to
   "/index/ix001/UNOLTSVT/sbl_idx_lg02.dbf";
     set newname for datafile  21 to
   "/databases/da001/UNOLTSVT/siebel_data02.dbf";
     set newname for datafile  22 to
   "/databases/da001/UNOLTSVT/sbl_data_lg02.dbf";
     set newname for datafile  23 to
   "/databases/da001/UNOLTSVT/sbl_data_xl04.dbf";
     set newname for datafile  24 to
   "/index/ix001/UNOLTSVT/sbl_idx_lg03.dbf";
     set newname for datafile  25 to
   "/index/ix001/UNOLTSVT/sbl_idx_xl03.dbf";
     set newname for datafile  26 to
   "/index/ix001/UNOLTSVT/sbl_idx_xl04.dbf";
     set newname for datafile  27 to
   "/index/ix001/UNOLTSVT/sbl_idx_xl05.dbf";
     set newname for datafile  28 to
   "/index/ix001/UNOLTSVT/sbl_idx_xl06.dbf";
     set newname for datafile  29 to
   "/index/ix001/UNOLTSVT/sbl_idx_lg04.dbf";
     set newname for datafile  30 to
   "/index/ix001/UNOLTSVT/sbl_idx_md03.dbf";
     set newname for datafile  31 to
   "/index/ix001/UNOLTSVT/siebel_index03.dbf";
     restore
     check readonly
     clone database
     ;
  }
  executing Memory Script
  
  executing command: SET until clause
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  Starting restore at 07-FEB-11
  
  channel aux1: starting datafile backupset restore
  channel aux1: specifying datafile(s) to restore from backup set
  restoring datafile 00018 to /index/ix001/UNOLTSVT/sbl_idx_md02.dbf
  restoring datafile 00027 to /index/ix001/UNOLTSVT/sbl_idx_xl05.dbf
  channel aux1: reading from backup piece /archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyj52mr_.bkp
  channel aux2: starting datafile backupset restore
  channel aux2: specifying datafile(s) to restore from backup set
  restoring datafile 00023 to /databases/da001/UNOLTSVT/sbl_data_xl04.dbf
  restoring datafile 00024 to /index/ix001/UNOLTSVT/sbl_idx_lg03.dbf
  restoring datafile 00025 to /index/ix001/UNOLTSVT/sbl_idx_xl03.dbf
  restoring datafile 00026 to /index/ix001/UNOLTSVT/sbl_idx_xl04.dbf
  restoring datafile 00030 to /index/ix001/UNOLTSVT/sbl_idx_md03.dbf
  restoring datafile 00031 to /index/ix001/UNOLTSVT/siebel_index03.dbf
  channel aux2: reading from backup piece /archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyj52n3_.bkp
  channel aux3: starting datafile backupset restore
  channel aux3: specifying datafile(s) to restore from backup set
  restoring datafile 00008 to /databases/da001/UNOLTSVT/sbl_data_md01.dbf
  restoring datafile 00013 to /index/ix001/UNOLTSVT/sbl_idx_md01.dbf
  restoring datafile 00015 to /index/ix001/UNOLTSVT/sbl_idx_xl01.dbf
  restoring datafile 00019 to /index/ix001/UNOLTSVT/sbl_idx_xl02.dbf
  channel aux3: reading from backup piece /archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyj52qf_.bkp
  channel aux4: starting datafile backupset restore
  channel aux4: specifying datafile(s) to restore from backup set
  restoring datafile 00028 to /index/ix001/UNOLTSVT/sbl_idx_xl06.dbf
  restoring datafile 00029 to /index/ix001/UNOLTSVT/sbl_idx_lg04.dbf
  channel aux4: reading from backup piece /archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyk4tct_.bkp
  channel aux5: starting datafile backupset restore
  channel aux5: specifying datafile(s) to restore from backup set
  restoring datafile 00009 to /databases/da001/UNOLTSVT/sbl_data_lg01.dbf
  channel aux5: reading from backup piece /archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyknmt9_.bkp
  channel aux6: starting datafile backupset restore
  channel aux6: specifying datafile(s) to restore from backup set
  restoring datafile 00002 to /databases/da001/UNOLTSVT/undotbs01.dbf
  restoring datafile 00003 to /databases/da001/UNOLTSVT/sysaux01.dbf
  restoring datafile 00005 to /databases/da001/UNOLTSVT/tools01.dbf
  restoring datafile 00011 to /databases/da001/UNOLTSVT/sbl_data_xl02.dbf
  restoring datafile 00016 to /databases/da001/UNOLTSVT/genuser01.dbf
  restoring datafile 00020 to /index/ix001/UNOLTSVT/sbl_idx_lg02.dbf
  channel aux6: reading from backup piece /archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyj52mx_.bkp
  channel aux5: restored backup piece 1
  piece handle=/archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyknmt9_.bkp tag=MON_114501
  channel aux5: restore complete, elapsed time: 00:15:16
  channel aux5: starting datafile backupset restore
  channel aux5: specifying datafile(s) to restore from backup set
  restoring datafile 00001 to /databases/da001/UNOLTSVT/system01.dbf
  restoring datafile 00004 to /databases/da001/UNOLTSVT/users01.dbf
  restoring datafile 00006 to /databases/da001/UNOLTSVT/siebel_data01.dbf
  restoring datafile 00010 to /databases/da001/UNOLTSVT/sbl_data_xl01.dbf
  restoring datafile 00014 to /index/ix001/UNOLTSVT/sbl_idx_lg01.dbf
  restoring datafile 00022 to /databases/da001/UNOLTSVT/sbl_data_lg02.dbf
  channel aux5: reading from backup piece /archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyj52b2_.bkp
  channel aux1: restored backup piece 1
  piece handle=/archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyj52mr_.bkp tag=MON_114501
  channel aux1: restore complete, elapsed time: 00:19:42
  channel aux1: starting datafile backupset restore
  channel aux1: specifying datafile(s) to restore from backup set
  restoring datafile 00007 to /index/ix001/UNOLTSVT/siebel_index01.dbf
  restoring datafile 00012 to /databases/da001/UNOLTSVT/sbl_data_xl03.dbf
  restoring datafile 00017 to /index/ix001/UNOLTSVT/siebel_index02.dbf
  restoring datafile 00021 to /databases/da001/UNOLTSVT/siebel_data02.dbf
  channel aux1: reading from backup piece /archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyj52b7_.bkp
  channel aux4: restored backup piece 1
  piece handle=/archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyk4tct_.bkp tag=MON_114501
  channel aux4: restore complete, elapsed time: 00:19:45
  channel aux2: restored backup piece 1
  piece handle=/archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyj52n3_.bkp tag=MON_114501
  channel aux2: restore complete, elapsed time: 00:28:01
  channel aux3: restored backup piece 1
  piece handle=/archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyj52qf_.bkp tag=MON_114501
  channel aux3: restore complete, elapsed time: 00:42:37
  channel aux6: restored backup piece 1
  piece handle=/archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyj52mx_.bkp tag=MON_114501
  channel aux6: restore complete, elapsed time: 00:47:42
  channel aux5: restored backup piece 1
  piece handle=/archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyj52b2_.bkp tag=MON_114501
  channel aux5: restore complete, elapsed time: 00:56:02
  ORA-19870: error reading backup piece /archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyj52b7_.bkp
  ORA-19502: write error on file "/index/ix001/UNOLTSVT/siebel_index01.dbf", blockno 2365601 (blocksize=8192)
  ORA-27063: number of bytes read/written is incorrect
  SVR4 Error: 28: No space left on device
  Additional information: -1
  Additional information: 131072
  Outer dbms_backup_restore.restoreCancel() failed
  failover to previous backup
  
  channel aux1: reading from backup piece /scratch/bu002/UNTPUAT2/backupset/2011_02_05/UNTPUAT2_34_1_1
  *ORA-19870: error reading backup piece /scratch/bu002/UNTPUAT2/backupset/2011_02_05/UNTPUAT2_34_1_1*
  *ORA-19505: failed to identify file "/scratch/bu002/UNTPUAT2/backupset/2011_02_05/UNTPUAT2_34_1_1"*
  *ORA-27037: unable to obtain file status*
  *SVR4 Error: 2: No such file or directory*
  Additional information: 3
  failover to previous backup
  
  released channel: aux1
  released channel: aux2
  released channel: aux3
  released channel: aux4
  released channel: aux5
  released channel: aux6
  RMAN-00571: ===========================================================
  RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
  RMAN-00571: ===========================================================
  RMAN-03002: failure of Duplicate Db command at 02/07/2011 16:58:11
  RMAN-03015: error occurred in stored script Memory Script
  RMAN-06026: some targets not found - aborting restore
  RMAN-06100: no channel to restore a backup or copy of datafile 17
  RMAN-06100: no channel to restore a backup or copy of datafile 12
  RMAN-06100: no channel to restore a backup or copy of datafile 7
  
  RMAN>

  fuzzydba wrote:
  Hi Alex,

  The file it is trying to restore is approximately 22 GB and the drive carrier has about 34 GB of free space, as shown below:

  [oracle@siedbauq01] /archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07 [UNOLTSVT]>df -h /index/*
  Filesystem             size   used  avail capacity  Mounted on
  /dev/md/dsk/d36        197G   161G    34G    83%    /index/ix001
  

  Please notify.

  As says this problem with the free space above the oracle. Thus, to increase the free space and try again. See above the first error, this indicates that it is error of space.

• VMWare Fusion pro 7.1.1 - blocking running yosemite as a guest problem

  Hi all

  I have a Yosemite pro running (mid-2014, 16 GB of ram video card w / discrete) MacBook. When I run a guest of yosemite, the video is very lag, and the virtual machine is generally not very handy.

  The guest has 4 cores, 4 GB ram, 256 MB of video memory (using the discrete card for 3D applications only) and implements the latest vmware tools 'material' and vmware. I disabled the sound and bluetooth.

  Is that what I can do to improve performance?

  Thank you!

  Yes.  Please check this blog for the manual workaround and a program called "BeamOff" that will provide relief without manual effort.  https://derflounder.WordPress.com/2014/12/13/improving-Yosemite-VM-performance-in-VMware-Fusion/

  I am not the author, and cannot vouch for the port version, however.  I downloaded the source, reviewed and updated on mine, just to be sure.  But it will fix the problem that you are experiencing.  (You need to run the application in the prompt, if it isn't obvious!)

  -Joe

• RMAN DUPLICATION

  Hello
  in 10g R2, if OVERLAP is issued, can it be seen (caterpillars) somewhere?
  
  How can I check if a command of OVERLAP is given?
  Thank you.

  Read

  http://download.Oracle.com/docs/CD/B19306_01/backup.102/b14192/maint002.htm

• RMAN has no damaged block

  Oracle 11.2.0.4 64-bit in archivelog mode

  He is a 2nd block corrupted on SYSAUX. First time can be read ORA-19566: exceeded the limit of 3 corrupt blocks...

  The first time was SYSAUX 69262 and 69263 blocks

  This time was 100424.

  The following found on alert.log

  Incorrect header found during the backup of the data file

  Bad block data:

  type: 1 format: 2 rdba: 0x000024c8

  last change the SNA: following 0x808c.00000104: 0 x 95 flg: 0xe3

  spare1: 0 x 0 spare2: 0 x 0 spare3: 0x80

  consistency in tail value: 0x3bd40201

  check the value in the block header: 0x887a

  disabled block checksum

  Review of blocknum is 100424, file = < location > \SYSAUX01. DBF. found the same corrupted data

  Review of blocknum = 100424, file == < location > \SYSAUX01. DBF. found the same corrupted data

  Review of blocknum = 100424, file == < location > \SYSAUX01. DBF. found the same corrupted data

  Review of blocknum = 100424, file == < location > \SYSAUX01. DBF. found the same corrupted data

  Review of blocknum = 100424, file == < location > \SYSAUX01. DBF. found the same corrupted data

  My Sep 15 18:36:38 2015

  Running the Checker found 1 new failures of persistent data

  I read Doc-ID 472231.1 et Doc-ID 199933.1 as suggested on Block of fracture found during the backup of the data file and Oracle 11 g: block Corruption SYSAUX file

  Do not be applied to my case.

  While I was able to retrieve the blocks with RMAN; My concern is now the long term effects and what is the cause? Also, trying to find a more permanent solution and not to block recovery every 2 weeks.

  Advisor? What should I look for?

  Thank you

  If it is Windows 2008 chances are that you have probably not ASM. Good luck to pick up a few Oracle then

  I would certainly come from SAs for some assistance, they should be able to spot something at a lower level / side storage, have an audit of the PDF file & run the dbv and validate.

• RMAN, auxiliary db and blocked listener?

  Hey;
  
  I am to the point of trying the rman duplication in my study of backup/restore and I ran into a bit of a problem with oracle net.
  
  Oracle 10g, 10.2.0.1.0, under oracle redhat linux.
  
  I know rman requires a dedicated server, so I'm in netmgr and tried to create a.
  
  The listener.ora file has not changed and shows:
  
  LISTENER =
  (DESCRIPTION_LIST =
  (DESCRIPTION =
  (ADDRESS = (PROTOCOL = CIP)(KEY = EXTPROC1))
  )
  (DESCRIPTION =
  (ADDRESS = (PROTOCOL = TCP)(HOST = ocidb1.olearycomputers.com) (PORT = 1521))
  )
  )
  
  The tnsnames.ora file now has a section for oci3 (auxiliary, hope to be cloned db) as follows:
  
  OCI3 =
  (DESCRIPTION =
  (ADDRESS_LIST =
  (ADDRESS = (PROTOCOL = TCP)(HOST = ocidb1.olearycomputers.com) (PORT = 1521))
  )
  (CONNECT_DATA =
  (SERVER = DEDICATED)
  (SERVICE_NAME = oci3)
  )
  )
  
  
  And who exactly resembles the entrance to oci1 with the exception of the service_name.
  
  I reload, restart the listener, then "startup nomount" oci3.
  
  RMAN target / catalog rcat/${mypwd}@oci2
  
  shows a good connection to the source and the catalog, then:
  
  RMAN > Connect auxiliary sys/${mypwd}@oci3
  
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-04006: auxiliary database error: ORA-12528: TNS:listener: all appropriate instances are blocking new connections
  
  Headset shows the connection as blocked oci3:
  
  $ lsnrctl status
  [[snip]]
  Service 'oci3' has 1 instance (s).
  Instance 'oci3', LOCKED status, has 1 operation for this service...
  Service 'oci3_XPT' has 1 instance (s).
  Instance 'oci3', LOCKED status, has 1 operation for this service...
  The command completed successfully
  
  Can someone indicate on what I am to spoil? Net Oracle was my next field of study; However, what little I know, and, more importantly, from what I read, it looks like it's supposed to work
  
  Thanks for all the tips/advice/suggestions.
  
  
  Doug

  Dear dkoleary,

  BLOCKED instance means that the auxiliary instance in the phase nomount. If you mount the database or open it, you can connect via the entry of ID of the Oracle (sqlplus @ oracle_sid).

  You can use the following command on the auxiliary instance, where the primary is defined in the tnsnames.ora.

  # RMAN TARGET SYS/PASSWORD@PRIMARY AUXILIARY /
  

  Hope that helps.

  Ogan

• How to run the rman output files, which are more days of retention

  I use for my rman backup tasks.

  I have format my output files of rman to a specific path, instead of the fast recovery area.

  Also, I spend below command in RMAN

  RMAN > CONFIGURE RETENTION POLICY to RECOVERY OF 7-DAY WINDOW;

  And the "control_file_record_keep_time" parameter is also set to 7.

  I've been running rman for 8 days. Everything seems good. But I find several rman output files are more than 7 days.

  So, I just want to know how to handle the rman output, which is longer than 7 days files?

  In fact, I assumed that these older files should be obsolete files, but rman is not to declare that they are obsolete.

  So how do now?

  user8710670 wrote:

  I use for my rman backup tasks.

  I have format my output files of rman to a specific path, instead of the fast recovery area.

  Also, I spend below command in RMAN

  RMAN > CONFIGURE RETENTION POLICY TO RECOVERY OF 7-DAY WINDOW;

  And the "control_file_record_keep_time" parameter is also set to 7.

  I've been running rman for 8 days. Everything seems good. But I find several rman output files are more than 7 days.

  So, I just want to know how to handle the rman output, which is longer than 7 days files?

  In fact, I assumed that these older files should be obsolete files, but rman is not to declare that they are obsolete.

  So how do now?

  Windows 7 day average recovery rman will protect everything necessary for the recovery to any point in time in the last 7 days.  In fact, in the last 604800 seconds.  The same will mean that he need the files OLDER than that.  Simply because a backupset is older that your recovery window does NOT as yet, it is obsolete.  Any recovery begins with the last FULL or INCREMENTAL backup ZERO before the recovery point.  And it does not matter how old the backup is, it will be obsolete.  Suppose you take a level 0 backup, 1 January and for the rest of the year taking nothing but level 1 and backup archivelog.  31 December than and only the full backup will still not be obsolete, even though he is a year old.

  ============================================================================

  removal of the obsolescence of RMAN

  Day 1 - level 0

  Day 2 - level 1

  Day 3 - level 1

  Day 4 - level 1

  Day 5 - level 1

  Day 6 - level 1

  Day 7 - level 1

  Day 8 - level 0

  Day 9 - level 1

  Day 10 - level 1

  Day 11 - level 1

  Day 12 - level 1

  Day 13 - level 1

  Day 14 - level 1

  On day 14, your window of 7 days is up to date 7.  A recovery to date must begin by restoring the backup of level 0 of the day 1. So it may be outdated.  Some level 1 between 1 and 6 days backups might be obsolete, depending on if they are incremental or cumulative, and it also happens with archivelogs.

  If you have access to MOS, you can review the notes 462978.1 and 463875.1.

  ============================================================================

• syntax of log_file_name_convert in the case of several members to redo

  Dear Oracle guru,
  I'm doing a script rman duplication.
  on the target db I redo 3 groups each have 2 members on the different directory path. On les(different machine), the logs under/U01 will pass to the /ora1
  and / U02 will move to the /ora2
  
  
  /U01/oradata/prod/redo01.log
  /U02/oradata/prod/redo01b.log
  
  /U01/oradata/prod/redo02.log
  /U02/oradata/prod/redo02b.log
  
  
  /U01/oradata/prod/redo03.log
  /U02/oradata/prod/redo03b.log
  
  
  I know
  DB_FILE_NAME_CONVERT = ' / u01/oradata/prod / "," / ora1/oradata / to the /.
  
  What should be the proper syntax for log_file_name_convert
  
  I am looking for site to oracle but they just be listed in case 1 example
  
  log_file_name_convert = (< source_db_path >, < target_db_path >)
  
  should I use
  log_file_name_convert = ' / u01/oradata/prod / "," / ora1/oradata / to the / "," / u02/oradata/prod / "," / ora2/oradata / to the /.
  
  
  Thanks for your time...

  No, you cannot use log_file_name_convert in an RMAN execution block.

  But you have not :)

  Just put the conversion in the pfile/spfile file, start the auxiliary database in nomount mode and duplicate the database. Your conversion rules for log files are correct. You can collect both the logfile group members in directory a target on the side of the auxiliary.

  And Yes, you will get the same number of log files on Test as the Prod.

  HTH

  Joerg

• RMAN - list backup command

  Oracle 10.2.0.4
  
  I assigned a band unit that has a drawn backupset of another data base and trying to backup from the list. Am I missing syntax here?
  
  RMAN > run
  2 > {allocate channel sbt type ch01
  3 > format = '% d_data_set % s_piece % p_ T_ %U '.
  4 > PARMS 'ENV=(TDPO_OPTFILE=/a0167/oracle/tivoli/ndk8oasu181.opt) ';
  5 > list backup;
  
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-00558: error occurred during parsing of order entry
  RMAN-01009: syntax error: found 'list': expected an of: "{assign, modify, save, beginline, blockrecover, catalog, edit, copy, convert, duplication, configure, duplicate, debug, delete, run, endinline, flashback, host, mount, open, plsql, recover, release, replicate, report, restoration, resync,}, together, setlimit, sql, switch, start, stop, send, display, transport, post.
  RMAN-01007: column 1 row 5 file: entry standard
  
  
  Thank you!!

  Hi, you can not use "backup list" command in block execution (run {}). You can only use it outside block 'run '.

• RMAN duplicate for standby the active database and the missing data files

  We have a car of 2 node ASM 11 GR 2 and 11.1 of database and a standby with ASM also. Our database is relatively low (300 GB)

  and in one recent event the day before was such a departure from the primary that we decided to "repopulate" the data using duplicate RMAN.

  I deleted the data files of the previous day and followed the Oracle documentation to duplicate a database. In the waiting

  I created a static listener and a pfile containing only the essential information (db_unique_name). I started the day before with nomount using the 'empty' pfile.

  I run RMAN, connected to the target and ancillary catalogues and run this command:

  run {
  allocate channel prmy1 type disk;
  allocate channel prmy2 type disk;
  allocate channel prmy3 type disk;
  allocate channel prmy4 type disk;
  allocate channel prmy5 type disk;
  allocate auxiliary channel stby1 type disk;
  duplicate target database for standby from active database nofilenamecheck;
  }
  

  RMAN duplication completed without errors, so I started the rescue database and got

  an error saying that datafile XXX is missing. I checked XXX datafile at the primary level

  and it is in a DISCONNECTED state. In the standby database the same data file is in the online state.

  So I think the problem is that during the duplication, RMAN (as documentation States) does not work

  Copy the files of data in offline mode, but the standby control file seem to think that these data files

  are online and should be present.

  Can someone please help me solve this problem? From my understanding, I could just copy the missing persons

  data files (there are many however) and in the standby go offline, but I don't think it's

  the right solution, edit this file for control of the standby? I would add another option

  in the RMAN script?

  Take the data file in offline mode on the site of the previous day.

  I don't think that two COPIES try to manage separately offline files.

  Hemant K Collette