AUTOMATICA Controlfile backup?

Similar Questions

• Unnecessary number of backup controlfile

  Dear Sir

  Here is my script to take a daily backup of my my prod system:

  {

  allocate channels ch1 device type sbt PARMS 'ENV =(NSR_SERVER=xxxxx)' =;

  backup data format "XXXX_ t_ %s %";

  cross-checking of backup;

  ARCHIVELOG backup all the format "XXXX_ t_ %s %";

  overlap archivelog all;

  backup current controlfile;

  }

  And out of all is:

  CONFIGURE CONTROLFILE AUTOBACKUP ON;
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F ';
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default

  But the problem is: when I took the backup with this script, I can see there are backup automatic the spfile and controlfile after each backup command. as after the backup of database compltes, it took a car controlfile bkp, after thn after archivelog backp... and so on... There are 4 backup controlfile who shouldn't be.

  Everyone guess why this is happening? My version of db is 11.1.0.6

  Kind regards

  My guess is that if you rearrange and rewrite your backup script, you'll see less automated backup controlfile.

  I guess you see a backup controlfile after your backup to the base, the second is after your backup archivelog, the third is when you save the controlfile explicitly and the fourth is taken automatically after backup current controlfile.

  Controlfile backups are performed whenever a backup folder is added.

  http://docs.Oracle.com/CD/E25054_01/backup.1111/e10642/rcmconfb.htm#autoId9

  If you are running your script as follows, I'd wait only autobackup controlfile is taken.

  {

  allocate channels ch1 device type sbt PARMS 'ENV =(NSR_SERVER=xxxxx)' =;

  backup data format "XXXX_ t_ %s %";

  ARCHIVELOG backup all the format "XXXX_ t_ %s %";

  cross-checking of backup;

  overlap archivelog all;

  }

• backup controlfile

  Hello world!
  
  I have a very dull question.
  
  My oracle is always full due to my controlfile record.
  
  I have to remove them, and I think that they are not buy useful, I'm not sure.
  
  I daily make a backup with this rman script:
  
  Run {}
  assign the channel c1 type disc format ' / oraclebck/backup_%d_set%s_piece%p_%T_%U';
  backup of database filesperset 1;
  backup current controlfile;
  backup ARCHIVELOG all delete them all entries;
  output channel c1;
  }
  
  
  which makes the controlfile backup in the backup piece, isn't?
  
  I have it configured in rman
  
  
  RMAN > show all.
  
  RMAN configuration parameters are:
  CONFIGURE REDUNDANCY 1 RETENTION STRATEGY; # by default
  CONFIGURE BACKUP OPTIMIZATION # by default
  SET UP DEFAULT DISK DEVICE TYPE; # by default
  CONFIGURE CONTROLFILE AUTOBACKUP ON;
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
  SET UP THE DEVICE TYPE DISK PARALLELISM 1; # by default
  CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
  CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
  CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT ' / backup/ora_df%t_s%s_s%p';
  CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
  CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / casa/oracle/product/9.2/dbs/snapcf_adaiasrv.f'; # by default
  
  Can I configure CONTROLFILE AUTOBACKUP off, since I make a backup of controlfile with rman?
  
  Thank you

  Controlfile autobackup can vary.
  or alternatively, you can change the location of the setting below
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default

  importance: -.
  RMAN can be configured to automatically back up the control file and the server settings file every time that metadata from database structure in control of changes in the file and each time a backup folder is added. Automatic backup RMAN can recover data even if the current control file, catalog and server parameter file are lost.
  Because the file name for the backup uses a well known format, RMAN can get without access to a repository and restore the server settings file. After you start the instance with the restored server settings file, RMAN can restore a backup control file. Once you mount the control file, the RMAN Repository is available and RMAN can restore the data files and find that the archived redo log.

• backup controlfile format

  Hello
  
  When I backup controlfile, rman generates two files:
  ctl_tnn17r1o and c-3169926800-20120120-00
  
  What is the reason for this?
  
  
  

  RMAN> backup current controlfile format '/rmanbackup/orcl/ctl_%u';
  
  Starting backup at 20-JAN-12
  using channel ORA_DISK_1
  using channel ORA_DISK_2
  using channel ORA_DISK_3
  channel ORA_DISK_1: starting full datafile backup set
  channel ORA_DISK_1: specifying datafile(s) in backup set
  including current control file in backup set
  channel ORA_DISK_1: starting piece 1 at 20-JAN-12
  channel ORA_DISK_1: finished piece 1 at 20-JAN-12
  piece handle=/rmanbackup/orcl/ctl_tnn17r1o tag=TAG20120120T101311 comment=NONE
  channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
  Finished backup at 20-JAN-12
  
  Starting Control File and SPFILE Autobackup at 20-JAN-12
  piece handle=/rmanbackup/orcl/c-3169926800-20120120-00 comment=NONE
  Finished Control File and SPFILE Autobackup at 20-JAN-12

  Yes, the reason is that you select "Controlfile Autobackup.

  You specify RMAN to do the backup of the controlfile in the format ' / rmanbackup/orcl/ctl_%u '. If you have found the 1st controlfile backup as ctl_tnn17r1o . Later, since you turn autobackup controlfile on, RMAN takes the automatic backup of the controlfile which is the 2nd file c-3169926800-20120120-00

  You can check if the controlfile autobackup is enabled or not by using:

  RMAN > show all.

  Handle: Ora_83
  Status level: Beginner
  Join date: November 8, 2009
  Messages total: 474
  Total Questions: 177 (114 pending)

  Why so many unanswered questions? If you do not have the answers in the right way, then ask them again in the same thread rather than leaving pending

  Published by: srp on 20 January 2012 10:39

• How to identify what trace file is your track of backup controlfile in udump

  I have a 10.2.0.3 database under unix.
  I want to configure a job to run a script every night to save the controlfile as text.
  as "alter database backup controlfile to trace."
  How my script can identify what trace file is the only one created just for backup controlfile and copy the file on a backup drive?
  
  Thank you very much!

  I thought that there

  change controlfile backup of database to trace in the "absolute path to a file where you want that control to plain text file";

  e.g. on Windows...

  ALTER database backup controlfile to trace as *'c:\temp\create_ORCL_control.sql'*.

  This way, you will know where your work will backup controlfile to trace

• 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

• The weekly backup failure

  Hello

  I am running an RMAN backup and daily backups to succeed, but I encounter a problem during the weekly backup.

  I am using recovery Director: Release 11.1.0.7.0

  Here is the script I'm running:

  Run {}

  SQL ' alter session set nls_date_format = "dd-mon-yyyy hh24:mi:ss";

  backup current controlfile;

  Home ' date/t ';

  Home ' time/t ';

  View all;

  outline report;

  cross-checking of backup;

  overlap archivelog all;

  duplication of copy of the controlfile;

  Home ' date/t ';

  Home ' time/t ';

  delete noprompt force backup expired;

  delete noprompt obsolete force;

  delete noprompt force expired archivelog all;

  delete noprompt force archivelog backupset all completed before ' sysdate-2';

  delete noprompt force complete database before backupset ' sysdate-7 ";

  Home ' date/t ';

  Home ' time/t ';

  retrieve the copy of the database with the tag "FULL";

  backup as backupset compressed incremental level 1 to retrieve copy with 'FULL' tag data include current controlfile;

  SQL 'alter system archive log current;

  SQL 'alter controlfile backup database to trace";

  ARCHIVELOG backup all the tag delete 'ARCHIVELOG' entry;

  Home ' date/t ';

  Home ' time/t ';

  }

  "exit";

  The question starts with the recover command.

  The errors I get:

  From back to January 27, 14

  using channel ORA_DISK_1

  using the ORA_DISK_2 channel

  channel ORA_DISK_1: from additional data file from the restore backup set

  channel ORA_DISK_1: specifying data file copies to recover

  retrieve the file number of the data copy = 00003 name = E:\FLASH_RECOVERY_AREA\NNVSDB\DATAFILE\O1_MF_UNDOTBS1_9CMHHTNM_ file. DBF

  retrieve the file number of the data copy 00005 name = E:\FLASH_RECOVERY_AREA\NNVSDB\DATAFILE\O1_MF_TS_NSA_D_9CMHHTNM_ = file. DBF

  retrieve the file number of the name 00006 = copy data file is E:\FLASH_RECOVERY_AREA\NNVSDB\DATAFILE\O1_MF_TS_NSA_D_9CMHY34C_. DBF

  retrieve the file number of the data copy = 00009 name = E:\FLASH_RECOVERY_AREA\NNVSDB\DATAFILE\O1_MF_TS_NSA_L_9CMHRGCG_ file. DBF

  channel ORA_DISK_1: backup E:\FLASH_RECOVERY_AREA\NNVSDB\BACKUPSET\2014_01_25\O1_MF_NNND1_TAG20140125T020010_9G72SC4V_ piece reading. BKP

  channel ORA_DISK_2: from additional data file from the restore backup set

  channel ORA_DISK_2: specifying data file copies to recover

  retrieve the file number of the data copy = 00001 name = E:\FLASH_RECOVERY_AREA\NNVSDB\DATAFILE\O1_MF_SYSTEM_9CMHY42C_ file. DBF

  retrieve the file number of the name 00002 = copy data file is E:\FLASH_RECOVERY_AREA\NNVSDB\DATAFILE\O1_MF_SYSAUX_9CMHYXN3_. DBF

  retrieve the file number of the data copy 00004 name = E:\FLASH_RECOVERY_AREA\NNVSDB\DATAFILE\O1_MF_USERS_9CMHZ2T6_ = file. DBF

  retrieve the file number of the data copy 00007 = E:\FLASH_RECOVERY_AREA\NNVSDB\DATAFILE\O1_MF_TS_NSA_I_9CMHRGCG_ name = file. DBF

  retrieve the file number of the data copy 00008 name = E:\FLASH_RECOVERY_AREA\NNVSDB\DATAFILE\O1_MF_TS_NSA_I_9CMHW21Q_ = file. DBF

  channel ORA_DISK_2: reading from the backup E:\FLASH_RECOVERY_AREA\NNVSDB\BACKUPSET\2014_01_25\O1_MF_NNND1_TAG20140125T020010_9G72SC3W_ piece. BKP

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

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

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

  RMAN-03002: failure of the command recover at 27/01/2014 05:09

  ORA-19870: error when restoring the backup E:\FLASH_RECOVERY_AREA\NNVSDB\BACKUPSET\2014_01_25\O1_MF_NNND1_TAG20140125T020010_9G72SC4V_ piece. BKP

  ORA-19625: error identifying file E:\FLASH_RECOVERY_AREA\NNVSDB\DATAFILE\O1_MF_UNDOTBS1_9CMHHTNM_. DBF

  ORA-27041: could not open the file

  04002 - OSD: could not open the file

  S/O-error: (OS 2) the system cannot find the file specified.

  What I am doing wrong?

  Thanks in advance.

  You use an incremental update strategy of backup.  This attempts to update the full backup on the disk.  The error here is that the data UNDOTBS1 file is NOT in the database backup on the disk (in the FLASH_RECOVERY_AREA).  Bottom line: all your backups are useless without this data file in the backup.

  See gradually "update backup" to http://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmbckba.htm#CHDEHBFF

  (Frankly, your script is a mixture of different configurations!)

  Hemant K Collette

• DG advice backup, backup the database ensures 11 GR 2

  Hello world

  I have a few problems with the way backups are installed in my DG Environment. I searched high and low and not really found an easy answer to how set up your backups DG.

  It is said this, another says that. So I ask here in the forum.

  What is the right way to safeguard a DG Environment? Some emissions of debates just do a normal backup on the standby only, another says that you must back up the controlfiles primary as well (this is where my problem begins)

  We have recently upgraded a DB 11 GR 1 material in GR 11, 2 and now the old system no longer works. The old plant was on standby and spfile backup + controlfile backup on the primary node. this moment fails with an invalid sequence of function calls ANU2614E to the Protection of data for Oracle (tape backup)

  This particular error occurs when I run a backup controlfile on the primary before the backup on the previous day. If I jump the backup controlfile on the primary, standby backup properly, including the controlfile + spfile.

  There is also an obsolete script delete running in each script (controlfile backup etc.), could also questions cause I guess. But it worked well in 11 GR 1 material.

  So I'm tender hand, trying to find the right way of backup, everyone says different.

  Sincerely

  Johnny

  What is the right way to safeguard a DG Environment?

  Support of primary or secondary is more correct than the other.

  You can use a backup made on the previous day in order to restore and recover a database and vice versa.

  Data files, control files and archive backups are interchangeable in a Data Guard environment.

  Where you backup should depend on the load. If the primary can handle the load without causing a problem with ALS then I would backup here.

  The main things I'd do with Data Guard RMAN are as follows:

  Select the block change tracking.

  Always use the auto backup.

  Always use an FIU.

  Keep Flashback Database.

  And always put this on the primary (CONFIGURE ARCHIVELOG DELETION POLICY to APPLIED on all THE previous DAY ;))

  Sequence ANU2614E invalid.

  Strange, if you use a third-party software with RMAN I could check this:

  RMAN fails ORA-19511 ANU2614E invalid sequence of function calls to the Protection of data for Oracle (Doc ID 1300134.1)

  Otherwise, I opened a support ticket as soon as POSSIBLE.

  Best regards

  mseberg

• RMAN automatically removes outdated backups?

  Hello

  1st:

  If I have the RMAN set 3 days retention policy (configire retention policy to recovery of 30-day window), RMAN would remove outdated backups automatically OR I have to explicitly issue the following command:

  RMAN > remove obsolete;

  
  

  2 : After that I have run the command above, is the backup 'physically' removed from storage OR is just RMAN deletes / purges his catalog/controlfile backup information?

  
  

  Best regards
  

  
  

  Hello

  1. you must use the button Delete obsolete; command to delete the backup

  2 backup will be deleted physically.

  You can also check this:8.3 deleting backups

  HTH

• RMAN backup using control as repository via networker file

  Hi guys,.
  
  I use the control as the rman repository file. Currently I have this backup running at 20:00 every night:
  
  backup format full filesperset 4 ' / Data_%d_%U/' (database);
  SQL 'alter system switch logfile;
  SQL 'alter system archive log current';
  overlap archivelog all;
  backup format '% s_ %%t p_ arch_' archivelog all;
  delete archivelog all completed before ' sysdate-3'; "
  
  And the log backup archive running from 07:00, 11:00, 16:00.
  
  
  Have a few queries:
  
  1. understand that with the above, backup control files will also be included as RMAN automatically includes the control file and the SPFILE in backups of data file 1.
  So in all cases when my control file is accidentally deleted from the server, I always can I restore from the backup right?
  I think I need set the db first as a control the file id is my deposit. If the control is absent, it can identify the control file for restore by setting db IDs?
  2. my automatic backup of control is set to off. What is the difference between the control file backup taken by autobackup compared to 1?
  understand controlfile autobackup is good because it will automatically backup if there is no change in the db (as new file created, etc.). Any other difference?
  3.
  Plateforme BACKUP CURRENT CONTROLFILE
  ❐ a control within a file backup by using the CONTROLFILE CURRENT INCLUDE of the BACKUP command
  What is the difference with this backup from controlfile backup to point 1 and 2?
  
  4. Finally, if my control + bow + datafiles, redo file is deleted by mistake at 18:00. I've restored the control taken to yesterday 20:00 file. The control file consisting only of 20:00 and before backup information, how to restore the rest of the newspapers arch taken by 07:00, 11:00, 16:00?
  
  
  
  Thank you

  Since you talk about networker, I presume that you are copying backups from disk to tape as a separate order of networker. Do not forget to include the controlfile record as well during the copy on tape!

  1. Yes, you can restore the controlfile and spfile from the backup. But you will need to manually determine what backup piece contains the backup controlfile and spfile. (In the scenario where you assume the controlfile is lost, you cannot issue a BACKUP LIST to identify the backuppieces, so you will have files from search logs to identify the backuppiece!)

  2. a controlfile autobackup will be created in db_recovery_file_dest using OMF. If you do not have it defined, the controlfile autobackup is epxected to go in $ORACLE_HOME/dbs - although the location of the actual target can be dependent on version and platform.

  3. a backup BACKUP CONTROLFILE creates a separate backupset and backuppiece for the controlfile. In OMF, it goes in the backup directory, not in the AutoSave directory.

  4. without a repository, if your archivelog backups are on the disc, you can catalog THEM (i.e. run 'CATALOGUE START WITH /disklocation' command) in the controlfile you restorted to the backup from 20:00. You cannot catalog backuppeices tape is advicable to use a repository when you back up directly to tape.

  Hemant K Collette

• RMAN SCRIPT TO CLEAR THE BACKUP ITEMS MORE THAN 2 DAYS...

  Hello
  
  I take a full backup of the DB using RMAN script. The script is as below:
  
  grc_backup
  {allocate channel ch1 type disc format ' / home/oragrc/GRCbkup/rman_bkp/data/%T_%c_%s_%f';}
  backup database;
  SQL ' ALTER SYSTEM
  ARCHIVE LOG CURRENT ';
  change archivelog than any overlap;
  ARCHIVELOG backup all the format ' / home/oragrc/GRCbkup/rman_bkp/Archive/%T_al_%U.bck';
  current backup controlfile as ' / home/oragrc/GRCbkup/rman_bkp/%T_cf_%U.bck';
  }
  
  
  This script is supposed to run on a daily basis via an OS script.
  
  The problem is on a daily basis after the backup that I have to delete the backups more than 2 days. For this I use an OS script that finds the backups more than 2 days to find the command and deletes it. This script also removes the archivelogs over 2 days.
  
  I just know that it is not advisable to delete RMAN backups and archived logs OS command when using RMAN.
  
  I figured out the following script, I have changed the script and instance names are different please find below
  
  CONFIGURE REDUNDANCY 2 RETENTION STRATEGY;
  Configure type disk parallelism 1 backup compressed backupset device type;
  
  run
  {
  allocate channel d1 type disk;
  backup filesperset 5 ' format / u06/backup/EBSDEV/EBSDEV_data_t%t_s%s_p%p' database;
  SQL 'alter system archive log current';
  format of backup filesperset 20 ' / u06/backup/EBSDV3/EBSDV3_arch_t%t_s%s_p%p' all entered archivelog delete;
  backup format ' / u06/backup/EBSDEV/EBSDEV_control%U' current controlfile;
  backup spfile format ' / u06/backup/EBSDEV/EBSDEV_spfile_%U';
  SQL 'alter controlfile backup trace database as "/tmp/control.trc" re-use";
  
  OVERLAP BACKUPSET;
  DELETE NOPROMPT OBSOLETE;
  DELETE THE EXPIRED NOPROMPT BACKUP;
  }
  list summary backupset;
  "exit";
  
  Can someone suggest me this AM I correct...

  Yes.

  Note: The OVERLAP should be OVERLAPPING BACKUP.

  Hemant K Collette

• full backup

  Hello
  I have create this shell script for rman for Oracle version 8i for full backup (database + controlfile archivelog):

  rman nocatalog <<EOF >> $LOG 2>&1
  connect target sys/password@sid
  run {
  allocate channel c1 type disk format '/backup_full/backup%d_DB_%u_%s_%p';
  backup database;
   sql 'alter system archive log current';
  backup format 'backup%d_CL_%u_%s_%p' current controlfile;
  backup format 'backup%d_AR_%u_%s_%p' archivelog all delete input;
  release channel c1;
      }

  Now I need rman script to Oracle 10.2.0.5 for full backup (database + controlfile archivelog).
  
  Is this right? Should I change?
  
  
  Thanks in advance!

  RAF Royal wrote:
  I have create this shell script:

  MY_PATH="/backup_rman_full/"
  export MY_PATH
  
  rman nocatalog <> $LOG 2>&1
  connect target
  run {
  allocate channel c1 type disk format '${MY_PATH}back%d_%u_%s_%p';
  backup database;
  sql 'alter system archive log current';
  backup format '${MY_PATH}back%d_C_%u_%s_%p' current controlfile;
  backup format '${MY_PATH}back%d_A_%u_%s_%p' archivelog all delete input;
  release channel c1;
  }
  exit
  EOF
  

  Is to correct the syntax?

  Hello

  Your script above looks perfect with the exception of '$LOG' which is not defined. But I prefer to add ORACLE_HOME and ORACLE_SID in your script and also change the format specifier "%u" "%U" while RMAN generates the uniqueness in the backup files. Here's the updated script for you.

  ORACLE_HOME=
  export ORACLE_HOME
  ORACLE_SID=
  export ORACLE_SID
  MY_PATH="/backup_rman_full/"
  export MY_PATH
  
  rman nocatalog <
  

  Think of your son of fence by providing appropriate points if you think they have been answered. Please clean the forum.

• timestamp of backup

  Hello
  
  If I have no logs for rman backup, is there way to get this information from controlfile?
  
  I use below command, but it does show what time datafile, archivelog backup finished or what time controlfile backup finished?
  How can I retrieve this information?
  
  
  Export NLS_DATE_FORMAT = 'DD-MON-YYYY HH24:MI:SS.
  CONTENTS LIST BACKUP;

  Select
  SESSION_KEY, INPUT_TYPE, STATUS,
  TO_CHAR (START_TIME, "mm/dd/yy HH24 '") start_time,
  TO_CHAR (END_TIME, "mm/dd/yy HH24 '") end_time.
  Round ((end_time-start_time) * 1440, 2) "Minutes."
  v $ RMAN_BACKUP_JOB_DETAILS
  order by desc session_key;

  Concerning
  Asif Kabir

• How can I recover a data file if it drop without backup!

  Dear friends,
  
  I have a request.
  
  In oracle database 10g, I created a database of test name 'medium '. I created a tablespace "support_ts" here.
  In my absent mind, I deleted the data file that is associated with "support_ts" physically. Logically the tablespace information is in the database, but physically the data file is deleted.
  
  'SUPPORT' database has no backup (export and rman), also the database is in noarchivelog mode.
  
  Now, is it possible to recover or do I focely delete the tablespace for database information? While, in the next database startup search information tablespace "support_ts"?

  Hello

  Recover the data file is not possible without the backup of the data file.

  You can re-create the control file and the startup of the database.

  Steps to recrete the control file.

  1. change controlfile backup of database to trace in the "";
  2. open the control file and remove the entry from tablespace and datafile support partly noreset newspapers.
  3. connect sys as sysdba
  4 cancel immediately / closed stop
  5 startup nomount
  6. paste balls noreset controlfile content
  7. After you have created the mount controlfile and open the database.

  Kind regards
  Prasanna

• Scheduled rman backup does not work, it works if performed manually

  Hi all
  
  I set up the automated DB Backup with rman via a cron job. The work begins, but the backup occurs do not. What I am doing wrong?
  
  Here is my configuration:
  
  Database: Oracle10g Express Edition
  OS: Oracle Linux
  
  * The backup should start every Friday @ 00:30
  
  crontab entry:
  
  30 00 * 5 /home/oracle/dba/scripts/rman_backup_db.sh > /home/oracle/dba/scripts/rman_backup_db.log
  
  The rman_backup_db.sh content:
  
  RMAN target / cmdfile=/home/oracle/dba/scripts/rman_backup_db.par log=/home/oracle/dba/logs/db_backup.log
  
  The rman_backup_db.par content:
  
  #
  
  Run {}
  allocate channel oem_backup_disk1 type disk;
  allocate channel oem_backup_disk2 type disk;
  allocate channel oem_backup_disk3 type disk;
  allocate channel oem_backup_disk4 type disk;
  allocate channel oem_backup_disk5 type disk;
  allocate channel oem_backup_disk6 type disk;
  allocate channel oem_backup_disk7 type disk;
  allocate channel oem_backup_disk8 type disk;
  noexclude backup power as the tag "online_bkp" COPY database include current controlfile;
  backup as COPY all backup archivelog do not delete all of the entries;
  output channel oem_backup_disk1;
  output channel oem_backup_disk2;
  output channel oem_backup_disk3;
  output channel oem_backup_disk4;
  output channel oem_backup_disk5;
  output channel oem_backup_disk6;
  output channel oem_backup_disk7;
  output channel oem_backup_disk8;
  }
  allocate channel for maintenance of type disk;
  OVERLAP DATAFILECOPY ALL;
  delete noprompt obsolete device type disk;
  output channel;
  
  # End of command RMAN script
  
  * There is no entry on the safeguarding of this morning
  /Home/oracle/dba/logs/db_backup.log content
  
  [oracle@olinux ~] $ /home/oracle/dba/scripts/rman_backup_db.log more
  [oracle@olinux ~] $ ls-l /home/oracle/dba/scripts/rman_backup_db.log
  -rw - r - r - 1 oracle oracle 0 August 27, 00:30 /home/oracle/dba/scripts/rman_backup_db.log
  [oracle@olinux ~] $
  
  If I run the /home/oracle/dba/scripts/rman_backup_db.sh manually, it works fine...
  
  Thank you for your time,
  
  Daniel

  Environment for cron tasks settings will not be addressed, you need to set your environment in the case against the .sh script will not be able to find programs. If you added the $ORACLE_HOME shell script call to your .profile, the same needs to be done in the script, i.e. for bourne or bash shells, there must be a space between the point and the .sh call note...

    .  /usr/lib/oracle/xe/app/oracle/product/10.2.0/client/bin/oracle_env.sh
    
  

  http://download.Oracle.com/docs/CD/B25329_01/doc/install.102/b25144/TOC.htm#CIHHJEHF in section 4.3 "defining the Oracle Database XE Server Environment Variables"