RMAN SBT_TAPE BACKUP FAILURE

Similar Questions

• Case of level 1 RMAN incremental backup failure...

  Hello

  I have a question. If the incremental level 1 RMAN backup fails, the next level 1 backup attempt will have backup all changes since the last backup of level 0 OR level 1 successful?

  Best regards

  Hello

  I have a question. If the incremental level 1 RMAN backup fails, the next level 1 backup attempt will have backup all changes since the last backup of level 0 OR level 1 successful?

  Check the dictionary BACKUP_SET V$ to confirm if the last backup has been affected by the data dictionary. If incremental backup failed is picked up then the last incremental backup will be required in the case of the next LEVEL 1 DIFFERENTIAL INCREMENTIELLE backup.

  But to be on the safe side, it is recommended that you take a LEVEL 01 CUMILATIVE INCREMENTAL backup of level 0 up to this day. For the recovery process can go through even if the previous backup is not valid.

  Thank you &

  Best regards

• RMAN: remove obsolete & sbt_tape backups?

  Hey;
  
  After several months of separation, I'm finally studying oracle backups. I try to get my database backups small test cleaned before trying again everywhere. I'm running into a bit of a snag, however:
  
  RMAN > list backup;
  
  
  Backup list
  ===============
  S LV TY Device Type delay #Pieces compressed #Copies Tag key
  ------- -- -- - ----------- --------------- ------- ------- ---------- ---
  5. A 10-AUG-09 SBT_TAPE 1 1 no TAG20090910T115704
  6. A 10-AUG-09 SBT_TAPE 1 1 no TAG20090910T115730
  13. A RECORD JULY 21 10 1 1 no TAG20100721T133933
  
  
  I want these two to 10-sep-09 backups go away. How they got there is a mystery because it is a small box of linux on intel. Is not a tape drive and never did; but this isn't the issue.
  
  I tried:
  
  RMAN > delete backup tag = "TAG20090910T115730";
  
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: sid = 139 devtype = DISK
  allocated channel: ORA_DISK_2
  channel ORA_DISK_2: sid = 129 devtype = DISK
  
  but the backup is still there because it uses a disk instead of a band channel channel.
  
  Can someone tell me how these two backups disappear?
  
  Thanks for your tips/advice/suggestions
  
  Doug O'Leary

  Allocate a fake tape channel and try again your deletion:

  RMAN> allocate channel for maintenance device type sbt
          parms 'SBT_LIBRARY=oracle.disksbt, ENV=(BACKUP_DIR=/tmp)';
  RMAN> delete obsolete;
  

• Problem with the archive log when you use RMAN for backup and restore (11g 2)

  Hello world
  Please help me solve this problem.
  I'm just beginner in Oracle Database (11 g 2). Today, I had a problem, I tried to back up and restore my db by RMAN. I delete all the files in /u01/app/oracle/oradata/orcl / * , then I restore them easily, but the point is I have a table, I can restore Hungarian, but cannot restore anything ranks in it (something wrong with step restore database). I'll tell the detail below.
  -First, I create a 'Day' with command table create table hr.day (varchar (20)) day. Then I backup complete by this:
  run{
allocate channel bkp device type DISK FORMAT '/u01/backup/DB_FULL_%d_%T_s%s_p%p' ;
backup as compressed backupset incremental level 0 tag 'DB_FULL' database include current controlfile;
backup as compressed backupset tag 'ARCL_BKP_FULL' archivelog all delete input;
crosscheck archivelog all;
crosscheck backup;
delete noprompt obsolete;
release channel bkp;
}
  

  
  D ' other hand, I have insert 'Monday' to table. then do an incremental backup by this:

  run{
allocate channel bkp device type DISK FORMAT '/u01/backup/DB_INC_%d_%T_s%s_p%p' ;
backup as compressed backupset incremental level 1 tag 'DB_INC' database include current controlfile;
backup as compressed backupset tag 'ARCL_BKP_INC' archivelog all delete input;
crosscheck archivelog all;
crosscheck backup;
delete noprompt obsolete;
release channel bkp;
}

  Repeat 7 times (Monday-> Saturday). And I got these files:

  [oracle@rac ~]$ ls -l /u01/backup/
total 400280
-rw-r----- 1 oracle oinstall  10158080 Jan 20 07:23 c-1428943247-20160120-01
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:04 c-1428943247-20160120-02
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:05 c-1428943247-20160120-03
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:06 c-1428943247-20160120-04
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:08 c-1428943247-20160120-05
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:08 c-1428943247-20160120-06
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:09 c-1428943247-20160120-07
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:32 c-1428943247-20160120-08
-rw-r----- 1 oracle oinstall 296337408 Jan 20 07:23 DB_FULL_ORCL_20160120_s89_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 07:23 DB_FULL_ORCL_20160120_s90_p1
-rw-r----- 1 oracle oinstall   2266624 Jan 20 07:23 DB_FULL_ORCL_20160120_s91_p1
-rw-r----- 1 oracle oinstall   4073984 Jan 20 07:23 DB_FULL_ORCL_20160120_s92_p1
-rw-r----- 1 oracle oinstall  11201536 Jan 20 07:23 DB_FULL_ORCL_20160120_s93_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:05 DB_INC_ORCL_20160120_s100_p1
-rw-r----- 1 oracle oinstall    146944 Jan 20 08:05 DB_INC_ORCL_20160120_s101_p1
-rw-r----- 1 oracle oinstall    884736 Jan 20 08:06 DB_INC_ORCL_20160120_s103_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:06 DB_INC_ORCL_20160120_s104_p1
-rw-r----- 1 oracle oinstall     82432 Jan 20 08:06 DB_INC_ORCL_20160120_s105_p1
-rw-r----- 1 oracle oinstall    294912 Jan 20 08:07 DB_INC_ORCL_20160120_s107_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:07 DB_INC_ORCL_20160120_s108_p1
-rw-r----- 1 oracle oinstall     18944 Jan 20 08:08 DB_INC_ORCL_20160120_s109_p1
-rw-r----- 1 oracle oinstall    155648 Jan 20 08:08 DB_INC_ORCL_20160120_s111_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:08 DB_INC_ORCL_20160120_s112_p1
-rw-r----- 1 oracle oinstall    131584 Jan 20 08:08 DB_INC_ORCL_20160120_s113_p1
-rw-r----- 1 oracle oinstall    647168 Jan 20 08:09 DB_INC_ORCL_20160120_s115_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:09 DB_INC_ORCL_20160120_s116_p1
-rw-r----- 1 oracle oinstall      8704 Jan 20 08:09 DB_INC_ORCL_20160120_s117_p1
-rw-r----- 1 oracle oinstall   2203648 Jan 20 08:04 DB_INC_ORCL_20160120_s95_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:04 DB_INC_ORCL_20160120_s96_p1
-rw-r----- 1 oracle oinstall   1899008 Jan 20 08:04 DB_INC_ORCL_20160120_s97_p1
-rw-r----- 1 oracle oinstall    327680 Jan 20 08:05 DB_INC_ORCL_20160120_s99_p1


  And
  RMAN> list backup summary;
List of Backups
===============
Key     TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
------- -- -- - ----------- --------------- ------- ------- ---------- ---
80      B  0  A DISK        20-JAN-16       1       1       YES        DB_FULL
81      B  0  A DISK        20-JAN-16       1       1       YES        DB_FULL
82      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL
83      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL
84      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL
85      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T072332
86      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
87      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
88      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
89      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080440
90      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
91      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
92      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
93      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080545
94      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
95      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
96      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
97      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080657
98      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
99      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
100     B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
101     B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080801
102     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
103     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
104     B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
105     B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080844
106     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
107     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
108     B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC

  My configuration of rman:
  RMAN> show all;
RMAN configuration parameters for database with db_unique_name ORCL are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u01/backup/%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   '/u01/backup/backup_df%t_s%s_s%p';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome/dbs/snapcf_orcl.f'; # default

  - Thirdly, i removed all file in /u01/app/oracle/oradata/orcl/*. then restore control file from the newest backup control file (saturday backup) + restore database. Seem nothing's wrong here.
RMAN> restore controlfile from '/u01/backup/c-1428943247-20160120-08';
Starting restore at 20-JAN-16
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=18 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=20 device type=DISK
channel ORA_DISK_2: skipped, AUTOBACKUP already found
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:09
output file name=/u01/app/oracle/oradata/orcl/control01.ctl
output file name=/u01/app/oracle/flash_recovery_area/orcl/control02.ctl
Finished restore at 20-JAN-16

RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
released channel: ORA_DISK_2

RMAN> restore database;
Starting restore at 20-JAN-16
Starting implicit crosscheck backup at 20-JAN-16
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=20 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=18 device type=DISK
Crosschecked 29 objects
Finished implicit crosscheck backup at 20-JAN-16

Starting implicit crosscheck copy at 20-JAN-16
using channel ORA_DISK_1
using channel ORA_DISK_2
Finished implicit crosscheck copy at 20-JAN-16

searching for all files in the recovery area
cataloging files...
no files cataloged

using channel ORA_DISK_1
using channel ORA_DISK_2

channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to /u01/app/oracle/oradata/orcl/system01.dbf
channel ORA_DISK_1: restoring datafile 00002 to /u01/app/oracle/oradata/orcl/sysaux01.dbf
channel ORA_DISK_1: restoring datafile 00003 to /u01/app/oracle/oradata/orcl/undotbs01.dbf
channel ORA_DISK_1: restoring datafile 00004 to /u01/app/oracle/oradata/orcl/users01.dbf
channel ORA_DISK_1: restoring datafile 00005 to /u01/app/oracle/oradata/orcl/example01.dbf
channel ORA_DISK_1: reading from backup piece /u01/backup/DB_FULL_ORCL_20160120_s89_p1
channel ORA_DISK_1: piece handle=/u01/backup/DB_FULL_ORCL_20160120_s89_p1 tag=DB_FULL
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:15
Finished restore at 20-JAN-16


  -Fourth, the problem here, I got the database;
.. .every oky until this line...
starting media recovery

channel ORA_DISK_1: starting archived log restore to default destination
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=15
channel ORA_DISK_1: reading from backup piece /u01/backup/DB_INC_ORCL_20160120_s117_p1
channel ORA_DISK_1: piece handle=/u01/backup/DB_INC_ORCL_20160120_s117_p1 tag=ARCL_BKP_INC
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
archived log file name=/u01/app/oracle/flash_recovery_area/ORCL/archivelog/2016_01_20/o1_mf_1_15_c9xsyx9k_.arc thread=1 sequence=15
unable to find archived log
archived log thread=1 sequence=1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/20/2016 08:50:22
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 1 and starting SCN of 1205841

The error said that it is impossible to find the archived log thread = 1 sequence = 1. Then I check it with this command always there (oh, I'm wrong?)
RMAN> list backup of archivelog all;
List of Backup Sets
===================
BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
82      2.16M      DISK        00:00:00     20-JAN-16     
        BP Key: 82   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_FULL
        Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s91_p1

  List of Archived Logs in backup set 82
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
1    1       1154833    20-JAN-16 1177422    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
83      3.88M      DISK        00:00:00     20-JAN-16     
        BP Key: 83   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_FULL
        Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s92_p1

  List of Archived Logs in backup set 83
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
1    1       1162729    20-JAN-16 1188784    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
84      10.68M     DISK        00:00:01     20-JAN-16     
        BP Key: 84   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_FULL
        Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s93_p1

  List of Archived Logs in backup set 84
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    2       1177422    20-JAN-16 1201833    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
88      1.81M      DISK        00:00:01     20-JAN-16     
        BP Key: 88   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s97_p1

  List of Archived Logs in backup set 88
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    3       1201833    20-JAN-16 1204844    20-JAN-16
  1    4       1204844    20-JAN-16 1204893    20-JAN-16
  1    5       1204893    20-JAN-16 1204958    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
92      143.00K    DISK        00:00:00     20-JAN-16     
        BP Key: 92   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s101_p1

  List of Archived Logs in backup set 92
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    6       1204958    20-JAN-16 1205034    20-JAN-16
  1    7       1205034    20-JAN-16 1205253    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
96      80.00K     DISK        00:00:00     20-JAN-16     
        BP Key: 96   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s105_p1

  List of Archived Logs in backup set 96
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    8       1205253    20-JAN-16 1205354    20-JAN-16
  1    9       1205354    20-JAN-16 1205433    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
100     18.00K     DISK        00:00:00     20-JAN-16     
        BP Key: 100   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s109_p1

  List of Archived Logs in backup set 100
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    10      1205433    20-JAN-16 1205519    20-JAN-16
  1    11      1205519    20-JAN-16 1205559    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
104     128.00K    DISK        00:00:00     20-JAN-16     
        BP Key: 104   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s113_p1

  List of Archived Logs in backup set 104
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    12      1205559    20-JAN-16 1205624    20-JAN-16
  1    13      1205624    20-JAN-16 1205739    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
108     8.00K      DISK        00:00:00     20-JAN-16     
        BP Key: 108   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s117_p1

  List of Archived Logs in backup set 108
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    14      1205739    20-JAN-16 1205796    20-JAN-16
  1    15      1205796    20-JAN-16 1205840    20-JAN-16

  
If i ignore it and open the database, just my table in full backup come back but rows was not restored. I'm sure the problem is my archive log backup but i don't know how to solve it. Plz help me.

  Sorry for a long post.


  > 1 and from the 1205841 SNA sequence

  The SCN that indicates Oracle is above the range of SNA that you have in the ArchiveLog backups for sequence 1 to 15 (15 sequence ends at 1205840).

  The message

  channel ORA_DISK_1: restoring archives Journal

  Archives journal thread = 1 sequence = 15

  channel ORA_DISK_1: backup/u01/backup/DB_INC_ORCL_20160120_s117_p1 piece reading

  channel ORA_DISK_1: piece handle = / u01/backup/DB_INC_ORCL_20160120_s117_p1 tag = ARCL_BKP_INC

  indicates that he has restored the sequence up to 15

  You can check the log file alert database instance for messages on the fact of recovery.

  He is now asking sequence #1 it seems you did a RESETLOGS after sequence #15.

  Note: If you have NOT issued a COMMIT after the line is INSERTED in the table 'Day', the recovery of the database will have no * transactions * to retrieve.  An uncomitted transaction is cancelled.

  Hemant K Collette

• EBS R11i Rman DB Backup error

  Hi friends,
  
  AIX 5 L platform
  
  I'm my R11i EBS with RMAN database backup, but I got error.
  
  rman target $ /.
  
  Release of Recovery Manager: 9.2.0.6.0 - 64 bit Production
  
  Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
  
  connected to target database: TEST (DBID = 1969797320)
  
  RMAN > backup database;
  
  From backup 10 December 08
  using controlfile target instead of recovery catalog database
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: sid = 39 devtype = DISK
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the backup to 2008-12-10 15:17:06 command
  [ORA-00600: internal error code, arguments: [525], [0x70000001137DD50], [5], [cache library], [5], [0x700000000025BF0], [device information]]
  ORA-27041: could not open the file
  IBM AIX RISC System/6000 error: 25: not a typewriter
  Additional information: 16
  
  RMAN > exit
  
  This file is opening here RMAN > ORA-27041: could not open the file
  
  
  Thank you very much

  Please refer to the Note: 262997.1 - ORA-600 [525] / [510] and ORA-27041 when running RMAN backup on IBM AIX platform
  https://metalink2.Oracle.com/MetaLink/PLSQL/ml2_documents.showDocument?p_database_id=not&P_ID=262997.1

• backup failure "access denied 0x80070005.

  I meet a backup failure error ' access denied 0 x 8007005 "whenever I try to save my computer.  I use Vista Home Premium.  Suggestions for solution on how to fix this problem

  Make sure that you are logged on as administrator.

  Don't forget to check the antivirus product issues and security as a 3rd party firewall (Comodo, on the one hand, a
  has been known to cause this problem.

  It is a very difficult to solve.

  Products of security/antivirus/antispyware are a known cause, so you can turn them off like
  as the test (and that sometimes not really totally removes their influence).

  How to restore the security settings the default settings?
  http://support.Microsoft.com/kb/313222

  It is usually a permissions problem:

  Please check this link and those that he sites.

  Work your way through my 3 posts here.
  http://social.answers.Microsoft.com/forums/en-us/vistasecurity/thread/200f5140-c2dd-48a5-8CDB-0d8c82ade3cf

  I hope this helps.

  Rob - bicycle - Mark Twain said it is good.

• RMAN bypass backup can be taken from question?

  Hi all

  pretty simple question (I hope that ):

  I use the suite at the moment for example:

  run
  {
  Backup CONFIGURATION DEVICE TYPE DISK PARALLELISM 2 to compressed backupset;
  TIME 01:00 PARTIAL minimize THE time data BACKUP FILESPERSET 1;
  }

  But I was wondering if there is some way to this running as a backup script planned to restart backup, if it does not (due to problems of space file etc.)

  run
  {

  Configure the disk channel CH1 device type format ' / alternate/path/for_backup/%d_DB_%M%D%Y_%p_%s_%U';
  Configure the disk channel CH2 device type format ' / alternate/path/for_backup/%d_DB_%M%D%Y_%p_%s_%U';

  
  TIME 01:00 PARTIAL minimize THE time of BACKUP data NOT BACKED UP SINCE TIME ' SYSDATE - 1' fileperset 1;    < < < I know it won't work like that but y at - it another way to accomplish this? (work around to restart the backup time and the option to reduce time?)
  

  
  

  cleaning etc release channels

  }

  PS: question side bonus points

  who can tell me more about the loss of speed MB/S compared to the rate of compression: low/medium/high?

  I hope that there are some brilliant minds out there willing to help!

  Thanks in advance.

  
  
  

  The themes you mention seem to be covered in the Advanced documentation of RMAN:

  http://docs.Oracle.com/CD/E11882_01/backup.112/e10642/rcmbckad.htm#BRADV89540

  I don't know if anyone can really give you an opinion about which compression will have the best size vs time full report. But the next test by using a simple vanilla ORCL database shows the result of the compression of 'low '. It was done on sub Oracle 11 GR 2 one running a VirtualBox VM. As you can see there is a reduction of the large size of the backupset, which however has taken so long to complete as to the 'no' compression.

  RMAN> CONFIGURE COMPRESSION ALGORITHM clear;
  
  RMAN> backup database;
  RMAN> list backup;
  
  BS Key  Type LV Size       Device Type Elapsed Time Completion Time
  ------- ---- -- ---------- ----------- ------------ ---------------
  40      Full    1.20G      DISK        00:00:08     22-JUN-15
          BP Key: 40   Status: AVAILABLE  Compressed: NO  Tag: TAG20150622T123329
  
  RMAN> CONFIGURE COMPRESSION ALGORITHM 'LOW';
  RMAN> backup as compressed backupset database;
  RMAN> list backup;
  
  BS Key  Type LV Size       Device Type Elapsed Time Completion Time
  ------- ---- -- ---------- ----------- ------------ ---------------
  44      Full    400.38M    DISK        00:00:08     22-JUN-15
          BP Key: 44   Status: AVAILABLE  Compressed: YES  Tag: TAG20150622T123811
  

  Why did you write that I know that it won't work like that? According to the example below, I don't see the problem. As you can see on the 2nd run of the backup command, it ignores the data files that he has previously treated.

  RMAN> BACKUP DURATION 1:00 PARTIAL MINIMIZE TIME database NOT BACKED UP SINCE TIME 'SYSDATE -1' FILESPERSET 1;
  
  Starting backup at 22-JUN-15
  using channel ORA_DISK_1
  channel ORA_DISK_1: starting full datafile backup set
  channel ORA_DISK_1: specifying datafile(s) in backup set
  input datafile file number=00001 name=+DATA/orcl1/datafile/system.256.862871041
  channel ORA_DISK_1: starting piece 1 at 22-JUN-15
  channel ORA_DISK_1: finished piece 1 at 22-JUN-15
  piece handle=+DATA/orcl1/backupset/2015_06_22/nnndf0_tag20150622t121929_0.283.883052369 tag=TAG20150622T121929 comment=NONE
  channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
  channel ORA_DISK_1: starting full datafile backup set
  channel ORA_DISK_1: specifying datafile(s) in backup set
  input datafile file number=00005 name=+DATA/orcl1/datafile/example.269.862871121
  channel ORA_DISK_1: starting piece 1 at 22-JUN-15
  channel ORA_DISK_1: finished piece 1 at 22-JUN-15
  piece handle=+DATA/orcl1/backupset/2015_06_22/nnndf0_tag20150622t121929_0.275.883052373 tag=TAG20150622T121929 comment=NONE
  ...etc...
  
  RMAN> delete backupset 29,30,34;
  
  RMAN> BACKUP DURATION 1:00 PARTIAL MINIMIZE TIME database NOT BACKED UP SINCE TIME 'SYSDATE -1' FILESPERSET 1;
  
  Starting backup at 22-JUN-15
  using channel ORA_DISK_1
  skipping datafile 2; already backed up on 22-JUN-15
  skipping datafile 3; already backed up on 22-JUN-15
  skipping datafile 4; already backed up on 22-JUN-15
  channel ORA_DISK_1: starting full datafile backup set
  channel ORA_DISK_1: specifying datafile(s) in backup set
  input datafile file number=00001 name=+DATA/orcl1/datafile/system.256.862871041
  channel ORA_DISK_1: starting piece 1 at 22-JUN-15
  channel ORA_DISK_1: finished piece 1 at 22-JUN-15
  piece handle=+DATA/orcl1/backupset/2015_06_22/nnndf0_tag20150622t122021_0.308.883052421 tag=TAG20150622T122021 comment=NONE
  ...etc...
  

• LEVEL 0 BACKUP FAILURE AFTER CHANGE HARD DRIVE

  Hello

  Yesterday I took the backup of level 0 from the new hdd(H:), mais il a échoué.) Please find more information,

  OS - Windows server 2012 (Live)

  VERSION - 11.2.0.1.0

  SERVER - server production

  Previously I configured 2 TB external Hdd in G: drive and set db_recovery_file_dest 2000 GB and backup location also the same hard drive size. Log Archive also only set according to G: drive location

  Since last three it is smoothly and taken the backup and the status of yesterday as hdd(G:) sur le point de remplir et il n'y est pas d'espace pour contenir le prochain niveau 0.)

  Now, according to those elders advice and I decided to take the only above mentioned archive disk G: log and mount the new hard drive in drive H: and Changed to the H: drive db_recovery_file_dest as below,

  H:\RMAN\AWSPROCESS\BACKUP and I did nothing with the parameter db_recovery_file_dest_size, it is intact, that the way in which it has been defined depending on the hard disk existing (g) 2000 GB (I learned that I changed my backup location, so this new HARD drive will automatically consider
  

  My goal is that enough backup RMAN based on Hdd (H :) new and I started yesterday and obtained backup failed with only 155 GB of backup in the new hdd(H:), si le niveau 0 prises avec succès, alors il pourrait être autour de 400 Go.))

  How to take my level 0 success based on newly mount Hdd (H :). What I did wrong and what to do more to achieve my successful backup.

  Please guide me.

  If you simply replace the disk, RMAN will always have the previous saved backups. RMAN does not automatically adjust its records because you free up space on the side of the BONE. You must do an overlap RMAN to synchronize your catalog or the RMAN command file and delete the records expired in your RMAN Repository in order to relaim the space on your FRA.

  http://docs.Oracle.com/CD/E11882_01/backup.112/e10642/rcmmaint.htm#BRADV89615

• RMAN incremental backup continue to make backups "complete"?

  Hello, I am new to RMAN. I used only the full backup by RMAN, and it was OK. Now, due to lack of disk space, I decided to make incremental backups.

  I put 'to recovey retention policy window of 3 days; then made a new backup (by MS) job, looks like:

  $rman_script = ' backup database cumulative device type disk tag '% TAG' extra strength 1;

  backup disc tag '% TAG' type device archivelog all not saved delete all entries;

  But, always visible, size of the backup is the same all the time as a full backup? Where is my mistake?

  This is a backup log:

  RMAN > database backup incremental level 1 cumulative device type disk tag "BACKUP_DB10_00002_070413021501".

  From backup 4 July 13

  allocated channel: ORA_DISK_1

  channel ORA_DISK_1: sid = 1043 devtype = DISK

  channel ORA_DISK_1: additional start-up compressed 1 datafile backupset

  channel ORA_DISK_1: specifying datafile (s) in backupset

  input datafile fno = name=/database/app/oracle/oradata/db/tablespace1.dbf 00007

  input datafile fno = name=/database/app/oracle/oradata/db/tablespace2.dbf 00002

  ...

  channel ORA_DISK_1: starting total, 1 to 4 July 13

  channel ORA_DISK_1: finished piece 1 to 4 July 13

  piece handle=/backup/oracle/flash_recovery_area/db/backupset/2013_07_04/o1_mf_nnnd1_BACKUP_DB10_00002_0_8x9d45f5_.bkp tag = BACKUP_DB10_00002_070413021501 comment = NONE

  channel ORA_DISK_1: complete set of backups, time: 00:41:15

  Backup finished on 4 July 13

  > database backup incremental level 1 cumulative device type disk tag "BACKUP_DB10_00002_070413021501".

  There is a Note of support Oracle ' size of level 1 or level 1 cumulative backup greater than level 0 backups [ID 1534691.1].

  which applies if you use the DUNGEON and change the tag.

  I note that you change the tag every day, but do not use the clause to KEEP this note should not apply.

  Why not explicitly run EXTRA STRENGTH 0 backup once and then monitor subsequent LEVEL 1 backups?

  Hemant K Collette

• RAC RAC CLONE OF RMAN cold backup

  Hi all
  
  I need your help in my Oracle RAC 11.2.0.2 to remote host environment cloning. Here's the disc structure
  
  DGVOT (disc ASM holding OCR and voting disk group)
  DGDATA (disk group ASM containing data files)
  DGFRA (disk group ASM files for fast recovery)
  
  Remote host is on a different location so cannot use duplicate RMAN with auxiliary channel.
  Have the luxury of downtime so I wanted to take coherent RMAN (Cold Backup)
  
  SAME structure of the disc is available on remote hosts.
  
  11.2.0.2 CLusterware (IG) over the oracle binaries are already installed.
  
  Can any body tell me the steps to
  (1) how to take cold backup on the disk so that I can tar and copy to the remote host
  (2) clone of the database on the remote host
  (3) how do I add the listener for the database and other resources of this databasee clusterware.
  
  in fact, it's my first clone CARS, so I'm well aware of the steps in detail.
  
  
  I went though a lot of notes metalink but nobody fits my needs. your tips will help me a lot
  
  Kind regards

  Hello

  (1) how to take cold backup on disk so that I can tar and copy to the remote host.

  Use Rman cold backup

  At the stage of the mountain run
  RMAN > backup database archivelog format '%U /dbp ";
  RMAN > backup controlfile current format "%U /ctl";

  Copy these to the remote host backup sets

  (2) clone of the database on the remote host

  Create groups of similar ASM disk as source
  create pfile/spifile, starting in nomount mode instance
  backup set from catalog

  RMAN > catalogue start with "";

  Restore controlfile

  RMAN > restore controlfile;

  RMAN > restore database;

  RMAN > restore database;

  On the success of the recovery

  RMAN > sql 'alter database open;

  (3) how do I add the listener for the database and other resources of this databasee clusterware.

  Srvctl user to add resources

  Use: srvctl

• Roll forward standby with RMAN incremental backup when used DG broker

  Hello
  
  I'm about to use the process defined in the note: steps to roll forward a database ensures the RMAN incremental backup using during primaries and Eve are in the file [836986.1 ID] ASM system. I'm on 11.1.0.7.
  
  However, it does not mention the DataGuard broker.
  Did someone played this process when you use the broker.
  The broker he manages properly?
  Does it matter if the broker is upwards or downwards during the physical recovery of standby or replacement of control file?
  Should the broker configuration be re-created?
  
  Thank you.

  user11993454 wrote:
  Hello

  I'm about to use the process defined in the note: steps to roll forward a database ensures the RMAN incremental backup using during primaries and Eve are in the file [836986.1 ID] ASM system. I'm on 11.1.0.7.

  However, it does not mention the DataGuard broker.
  Did someone played this process when you use the broker.
  The broker he manages properly?
  Does it matter if the broker is upwards or downwards during the physical recovery of standby or replacement of control file?
  Should the broker configuration be re-created?

  Thank you.

  (1) disable the broker
  (2) perform the Roll forard SNA.
  (3) select the broker

• Resume failure RMAN incremental backup to disk 0 cold

  Linux x 86-64 10.2.0.4
  
  I take an incremental backup of 0 to disk in a database that is mounted. I'm backup the database on an NFS volume. I lost the NFS mounting. Is it possible to take a backup where it stopped at? He complains "ORA-27038: created file already exists" if I restart it. RMAN can easily return to a restore. I don't have time to redo everything all again. The database is greater than 10 TB. The target is not upward. Is there something else I could do?

  If you have lost the NFS mounting, has not lost what had been saved to this mount? So, don't you create a fresh backup of all the files again?

  How are you "restart" backup? If you issue a fresh BACKUP DATABASE, it must create a new backup, with new backupsets - I hope the backuppiece (i.e. the name of the file) is unique and/or the file with the same name is not existing on the target.

  Hemant K Collette

• RMAN SBT_TAPE error

  When I am trying to delete obsolete backups I get this error.
  
  ....
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03009: failure to allocate command on ch1 channel at 08/11/2007 15:21:08
  ORA-19554: error device allocation, type of device: SBT_TAPE device name:
  ORA-27211: unable to load the media management library
  ...
  
  need help!
  
  Thank you

  You can do it

   configure device type 'SBT_TAPE' clear 
  

  SS

• Backup failure

  Hello

  I'm having some problems with backups using enterprise manager.

  I run a full backup of database and it seems that everything is running, but fails at the last second. Copies of datafile everywhere but the mistakes in trying to identify the newspaper archive, this is the error I get:

  Backup finished at 2 October 15

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

  using channel ORA_DISK_1

  channel ORA_DISK_1: finished piece 1 at 2 October 15

  piece handle = \\IST_BACKUP_02\WINDOWS\L7QIN5UV_1_1 = EBS BACKUP_100215025659 = NONE comment tag

  ORA-27041: could not open the file

  ORA-19625: error identification of file C:\APP\ADMINISTRATOR\PRODUCT\11.2.0\ARCH\ARC0000113207_0812454378.0001

  RMAN-06059: expected found archived newspaper, loss of archived newspaper compromised recoverability

  RMAN-03002: failure of the backup command to the 02/10/2015 15:29:43

  RMAN-00571: ===========================================================

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

  RMAN-00571: ===========================================================

  04002 - OSD: could not open the file

  channel oem_backup_disk1: specifying datafile (s) in the backup set

  channel oem_backup_disk1: starting full datafile from backup set

  From 2 October 15 backup

  Anyone can help or point me in the right direction?

  See you soon

  Hello

  It seems by the above you have a completely out of the box on Windows installation? It puts your archivelogs in the ORACLE_HOME, probably not a good idea. Ideally on a separate file system.

  Have a control of the same place, looks like someone may have deleted the log file and advised against Oracle, oracle to think it is there, but is not.

  Check your log_archive_dest and your db_recovery_file_dest settings see where will the archivelogs.

  Also run an overlap for the archivelog (C:\APP\ADMINISTRATOR\PRODUCT\11.2.0\ARCH\) to say Oracle, what are the archivelogs and what archivelogs are missing.

  rman target / nocatalog
  crosscheck archivelog all;
  

  If you have the archivelog saved to another location and want to include in the backup, restore, and run:

  rman target / nocatalog
  catalog start with "C:\APP\ADMINISTRATOR\PRODUCT\11.2.0\ARCH"
  

  to save it with the database.

  Otherwise, make sure that you run a few journal archiving under tension, and then kick off the full backup & backup archivelog again.

  Good read point - RMAN is unimportant for belt and braces work s/n: http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmcncpt.htm#BRADV002

• Oracle 12 c with RMAN database backup

  Hi All-

  I started back to the top of one of my PDB using utility RMAN following the instructions on the link below.

  http://www.Oracle.com/WebFolder/technetwork/tutorials/OBE/DB/12C/R1/PDB/pdb_pitr/pdb_pitr.html

  --Connect to Oracle RMAN.
  rman> Connect target /
  --Set the Oracle RMAN backup device type and backup file location.
  rman> configure channel device type disk format '/stage/db_backup_files/cdb1/%U';
  --Turn on automatic backup of control files.
  rman> configure controlfile autobackup on;
  --Back up the database and archive logs.
  rman>backup database plus archivelog;
  rman> exit
  

  Back to the top has been done successfully, but when I started with the recovery process he gave me error reporting collection.

  Run {set until what SNA = 2263440; restore database connectable to pdb2; retrieve auxiliary destination of the pluggable database pdb2 = "/ stage/db_backup_files/cdb1 '; alter connectable database to pdb2 ;} open resetlogs}

  This is the track to RMAN

  Recovery Manager: release 12.1.0.2.0 - Production on sat 22 Aug 12:22:44 2015

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

  RMAN > Connect target /.

  connected to target database: RELIABLE (DBID = 1028507357)

  RMAN > run {}

  2 > ALTER DATABASE connectable to MultiPlay NARROW;

  3 > set up what SNA = 14899894;

  4 > restore database pluggable MultiPlay;

  5 > restore database pluggable MultiPlay;

  6 > alter database connectable to MultiPlay open resetlogs;

  {7 >}

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

  Statement processed

  executing command: SET until clause

  From restoration to 22 August 15

  allocated channel: ORA_DISK_1

  channel ORA_DISK_1: SID = 22 type of 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 00035 to E:\APP\ORADATA\RELIABLE\MULTIPLAY\SYSTEM01. DBF

  channel ORA_DISK_1: restore datafile 00036 to E:\APP\ORADATA\RELIABLE\MULTIPLAY\SYSAUX01. DBF

  channel ORA_DISK_1: restore datafile 00037 to E:\APP\ORADATA\RELIABLE\MULTIPLAY\MULTIPLAY_USERS01. DBF

  channel ORA_DISK_1: backup E:\APP\RECOVERY_AREA\RELIABLE\40A433F530464F3BBF2E7C0B1553ECE8\BACKUPSET\2015_08_22\O1_MF_NNNDF_TAG20150 piece reading

  822T115328_BXJ5C182_. BKP

  channel ORA_DISK_1: piece handle = E:\APP\RECOVERY_AREA\RELIABLE\40A433F530464F3BBF2E7C0B1553ECE8\BACKUPSET\2015_08_22\O1_MF_NNNDF_TAG20150822T115328_BX

  J5C182_. Tag BKP = TAG20150822T115328

  channel ORA_DISK_1: restored the backup part 1

  channel ORA_DISK_1: restore complete, duration: 00:01:05

  Restoration finished in 22 August 15

  From pick up to August 22, 15

  using channel ORA_DISK_1

  RMAN-05026: WARNING: following tablespaces set applies to the Point in time specified assuming

  List of tablespaces should have UNDO segments

  SYSTEM tablespace

  Tablespace UNDOTBS1

  Creation of automatic instance with SID = "zbnt."

  RMAN-00571: ===========================================================

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

  RMAN-00571: ===========================================================

  RMAN-03002: failure of the command recover at 22/08/2015 12:24:56

  ORA-19852: error creating services for the instance auxiliary zbnt (error 0)

  ORA-27302: failure occurred:

  ORA-27303: additional information: could not start the instance

  Thank you

  Siradji

  Just a wild guess

  You do not use this script in a command as Administrator window

  Therefore, you won't be able to create any service.

  I also have a question: your only troubleshooting activity consisted of hitting CTRL + C and CTRL-V, is not it?

  It's so boring to most of the people here do not even TRY to solve their own problems.

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

  Sybrand Bakker

  Senior Oracle DBA