question of RMAN backup optimization

Hello

I met a related issue of RAM and would like to understand the answer:

Configuration of RMAN optimization a backup the value ONE. Which of the following commands will affect this setting?

one) backup Archivelog with ALL or AS options, b) backup Backupset ALL, c) backup Tablespace, d) Backup Database

I think that all of the above are affected by the backup optimization, however, only a, b and d seems correct, not c. I wonder why tablespace is not affected - it is not read-only, etc. ?

Any ideas? Thank you.

That is right. Please see the link to the doc,
http://download.Oracle.com/docs/CD/E11882_01/backup.112/e10642/rcmconfb.htm#BRADV113

HTH
Aman...

Tags: Database

Similar Questions

RMAN backup optimization CANCEL 11g
Hi all?

I tested 11g RMAN CANCEL backup optimization
1 I filled out by manipulation sql undo tablespace and not commit
2nd undo_ts backed up by RMAN (size 24 m)
3rd I made a commit
Then the tablespace undo supported again but the backup_size column has not changed (24 m)
Then I did some more manipulations and supported undo_ts again. This reduced time backup_size column. (11 m)
Then I rebooted db and saved to undo_ts again. Size of backup at this time became what I expected (600K)

The question is why did not reduce the size 11 g rman undo tablespace backups after validation?
According to 11 g cancel optimization to

...
SQL > select sum (bytes) of dba_free_space where nom_tablespace = 'UNDOTBS2 ';
SUM (BYTES)
13172736
SQL > start
because me 1.100000 loop
insert into testundo values (i);
end loop;
end;
/
2 3 4 5 6
PL/SQL procedure successfully completed.
SQL > SQL > update of testundo game
ID = 2 where id > 0;
2
Update testundo set
*
ERROR on line 1:
ORA-30036: unable to extend segment by 8 in undo tablespace "UNDOTBS2".
SQL > select sum (bytes) of dba_free_space where nom_tablespace = 'UNDOTBS2 ';
Sum (bytes)
RMAN > backup datafile 6;

RMAN > backup from the list of the 6 data file;

List of backup sets
===================

Time of accomplishment BS key Type LV size device Type elapsed time
10 full * 24.54M* DISK 00:00:04 June 10, 10
BP key: 10 location: AVAILABLE Tablet: NO Tag: TAG20100610T142437
Part name: /home/oracle/flash_recovery_area/11GR1/backupset/2010_06_10/o1_mf_nnndf_TAG20100610T142437_611ctr1f_.bkp
List of files of data backup set 10
Name of file LV Type cash SNA cash time
6 integer 577669 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf 10 June 10

SQL > commit;

Full validation.
RMAN > backup datafile format 6 "after commit.backup";

RMAN > backup from the list of the 6 data file;

List of backup sets
===================

Time of accomplishment BS key Type LV size device Type elapsed time
11 full * 24.54M* DISK 00:00:02 June 10, 10
BP key: 11 location: AVAILABLE Tablet: NO Tag: TAG20100610T142541
Item name: / home/oracle/product/11/Db_1/dbs/after commit.backup
List of files of data backup set 11
Name of file LV Type cash SNA cash time
6 integer 577705 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf 10 June 10

SQL > alter system archive log current;
Modified system.
SQL > commit;
Validation complete.
SQL > select count (*) in the testundo;
COUNT (*)
100000
SQL > delete from testundo;
100000 deleted rows.
SQL > commit;
Validation complete.
SQL > insert into testundo values (1);
1 line of creation.
SQL > commit;
Validation complete.
SQL > alter system flush buffer_cache;
Modified system.
RMAN > backup datafile 6;

RMAN > backup from the list of the 6 data file;

List of backup sets
===================

Time of accomplishment BS key Type LV size device Type elapsed time
13 full * 11.03M* DISK 00:00:01 June 10, 10
BP key: 13 status: AVAILABLE Tablet: NO Tag: TAG20100610T143359
Part name: /home/oracle/flash_recovery_area/11GR1/backupset/2010_06_10/o1_mf_nnndf_TAG20100610T143359_611dd8sz_.bkp
List of files to backup data value 13
Name of file LV Type cash SNA cash time
6 integer 578410 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf 10 June 10

RMAN >

SQL > shutdown immediate;
The database is closed.
The database is dismounted.
ORACLE instance stops.
SQL > startup
ORACLE instance started.

Total System Global Area 393375744 bytes
Bytes of size 1300156 fixed
352323908 variable size bytes
33554432 buffers of data bytes
Redo buffers 6197248 bytes
Mounted database.
Open database.
SQL >
RMAN > backup datafile 6;
RMAN > backup from the list of the 6 data file;

List of backup sets
===================

Time of accomplishment BS key Type LV size device Type elapsed time

Full 14 * DISK 00:00:02 600.00K* 10 June 10
BP key: 14 location: AVAILABLE Tablet: NO Tag: TAG20100610T152843
Part name: /home/oracle/flash_recovery_area/11GR1/backupset/2010_06_10/o1_mf_nnndf_TAG20100610T152843_611hlwmv_.bkp
List of defined backup data files 14
Name of file LV Type cash SNA cash time

6 integer 580347 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf 10 June 10

Thanks in advance
Turkel
Hi Turkel,
Space used to cancel is also linked to the undo retention implementation.
As it seems do you an update of test and perform backups on:
-14: 24:37 (-> 25 M)
-14: 25:41 (-> 25 M)
-14:33:59 (-> 11 M)
-15: 28:43 (-> 600 K)
The first two backups are probably still in the retention period to cancel the update.
The third backup shows a cancellation partly empty (is your setting 900?).
The last falls outside the period of retention for the update, resulting the small size of backup.
Kind regards
Tycho

Question of RMAN

Hi all
Could you get it someone please let me know what is the difference between incremental backup using rman and rman optimization. I searched a lot in the Oracle documentation but could not get it.
Kind regards
Michel

RMAN > backup optimization;

RMAN > backup optimization;

When you enable backup optimization, backup using rman command will skip backup of any file (datafile, archivelog or backup sets) if it has not changed or it is already saved. If your subsequent backup will save space.

Incremental backups RMAN backup datafile only blocks changed since a previous backup specified. You can perform incremental backups of databases, individual storage spaces or data files.

"Please ignore": double Question: PROBLEM of BACKUP RMAN
Dear Sir.

I learned that the RMAN backup command shows if a backup happened to own or not to for example:

RMAN backup report
SESSION_KEY INPUT_TYPE STATUS START_TIME, END_TIME MINUTES
1079 FINISHED ARCHIVELOG 03/01/10 08:14 03/01/10 08:46 32.12
1072 DB FULL FAILURE 03/01/10 04:09 01/03/10 07:56 227.65

The rman backup command shows that there no full backup of the DB:

The new order of 10g that gives me this info is provided below:

Select SESSION_KEY, INPUT_TYPE, STATUS, to_char (START_TIME, ' dd/mm/yy HH24') START_TIME, to_char (END_TIME, ' dd/mm/yy HH24') END_TIME, round ((end_time-start_time) * 1440, 2) Minutes of SYS.v_$ RMAN_BACKUP_JOB_DETAILS order by session_key desc;

My alert doesnot log tell me there's an error during backup how to check my status of full DB backup as to why told you can't...

Kindly help

In addition I also have Oracle 9i DB but we do not have a simple command like the above in 10 g that gives me a situation report that says for DB Backup went well or not your help will be much appreciated

Concerning

Published by: user8764012 on January 3, 2010 13:29
Please change the subject here line "Please ignore".

I thank you, in the future, no announcement only once and only in a good group.

content managed rman backup crushing and selection procedure of the tape media

Hello Experts.
I have a question about the backupset rman tape media manage tape of the osb.
[ENV]
Exadata rman backup assistance OSB(version: 10.4.0.3.0) SL500 LTO5 4 Tape Drive with rman scripts and full backup is working well.
1 Appendix backup on OS crontab
-Each backup full day at 00:00 AM
2 rman view all:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
using the control file of the target instead of recovery catalog database
RMAN settings for database with db_unique_name TESTDW are:
CONFIGURE RETENTION POLICY TO 3 DAY RECOVERY WINDOW;
CONFIGURE BACKUP OPTIMIZATION # by default
CONFIGURE THE TYPE OF DEFAULT DEVICE TO 'SBT_TAPE ';
SET UP THE DEVICE TYPE 'SBT_TAPE' PARALLELISM 4 TYPE OF BACKUP BACKUPSET.
CONFIGURE CONTROLFILE AUTOBACKUP ON;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3 rman backup scirpts
Run {}
allocate channels c01 type 'sbt_tape' connect 'sys/manager@testdw1';
allocate channel c02 type 'sbt_tape' connect 'sys/manager@testdw2';
allocate channel c03 type 'sbt_tape' connect 'sys/manager@testdw1';
allocate channels c04 type 'sbt_tape' connect 'sys/manager@testdw2';
Backup section size 900g database;
output channel c01;
output channel c02;
output channel c03;
output channel c04;
}
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1st quarter > after several weeks and I run the command as "#obtool u admin Pei welcome1 lsvol-L lib1.
and are used in many media of rman backup band (about 50EA media, perhaps 46EA are full and 4EA are appendble)
So, I issue the command 'lsvol - a - c' and could not display expired on all media content.
Why OSB no has not select and replace the tape media despite the rman rman default retention policy (3days) all show the setting.
Why OSB does not have the expired status of rman content on tape media?
-> I need the rman (delete expired, delete obsolete etc...) command to share the summary status of OSB and rman rman?
Q2 > selection procedure for the tape media all backup rman
Suppose the total number of tape media is 5EA. (1,2,3,4,5) with an available tape LTO5 drive.
Status: 1 (full-rman content already expired), 2 (content integral-rman not expired), 3 (editable, remaining space), 4 (new media), 5 (currnet wring media)
If OSB burn now 5 and reach at the end of the Strip and possibly another media, media to be selected by the OSB?
Advanced thanks.

If I place the order obsolete in the rman script as 'delete type 'SBT_TAPE' noprompt obsolete device;' the results will be the same as your

the syntax because rman default setting (CONFIGURE RETENTION POLICY to RECOVERY WINDOW OF 3 DAYS ;) has already been fixed on the command "Show all", right? @)

Yes.

I use the catalog of recovery on a different database and backup script has catalog db connection string.

And if I only use controlfile instead of recovery catalog to save the backup information and put in place "control_file_record_keep_time" a default of 7 days to 365 days, "remove obsolete" command to remove several weeks backupset works well, is it not?

Possible problem are existing backups for several weeks if you left default control_file_record_keep_time. Change now will not help unless you catalog later manually all the old pieces not catalogued on tape backup.

After you clean up the situation and particularly to remove obsolete in your script, rman, you will never make problems with control_file_record_keep_time from this moment. By default will do just fine because it is larger than your window of recovery.

Kind regards

Mitja

Hot RMAN backup fails every time in R12.

Hi experts,
Please suggest me that I have to plan rman backup hot. I have "write" command to perform hot backup. When I take backup hot of 1st time the backup completed successfully. but when I run the same command resume backup for the second day. it is impossible to give space issue I havhot e calendar for daily use rman backup.
I had to take the backup hot daily and I want backup overwrite the backup file according to the daily backup.
Please suggest me what I need to make changes in the configuration of rman and the rman command.
OS - réhèl 5.6
Database - 11.1
EBS - r12.3
configuration of RMAN:
RMAN > show all.

Database with db_unique_name UAT RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY OF 7-DAY WINDOW;
CONFIGURE BACKUP OPTIMIZATION
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 BACKUP BACKUPSET TYPE; # by default
CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1;
CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1;
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT ' / d06/UAT/rman_hot_backup/Backup_daily%d_DB_%u_%s_%p';
CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
CONFIGURE ENCRYPTION OF DATABASE # by default
CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
CONFIGURE COMPRESSION ALGORITHM 'BZIP2 '; # by default
CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / d06/UAT/db/tech_st/11.1.0/dbs/snapcf_UAT.f'; # by default

RMAN >

##############################################################################################################

RMAN command that I used to make hot extra strength 0 cumulative backup.

RMAN > run
{
allocate channels c1 device type disk format ' / d06/UAT/rman_hot_backup/Daily_backup%d_DB_%u_%s_%p_%c';
allocate channel c2 device type disc format ' / d06/UAT/rman_hot_backup/Daily_backup%d_DB_%u_%s_%p_%c';
allocate channels c3 device type disk format ' / d06/UAT/rman_hot_backup/Daily_backup%d_DB_%u_%s_%p_%c';
allocate channel c4 device type disc format ' / d06/UAT/rman_hot_backup/Daily_backup%d_DB_%u_%s_%p_%c';
cumulative incremental database backup level 1 more archivelog;
output channel c1;
output channel c2.
output channel c3.
output channel c4.
}
If something bad in the configuration of rman and my order please suggest me to take the backup hot every day with success.

concerning
pritesh Rodriguez

Hi Pritesh, thanks for the update. You can mark this thread as answered if your questions have been answered. cordially Karan

can someone explain to me of retention of Rman and optimization policy on or off.

1. What is the meaning of retention policy redendency 1 or 2?
2 what is the meaning of the retention policy to retrieve the window?
3. What is the meaning of optimization and what happens in this case and vice versa?
4. If optimization is he going to consider read-only and offline table space?
5. If optimization off is going to be considered read-only and offline table space?
do not post any documents that I went through the box of documents that someone let me know in words simple or easy to understand for me... give me some examples of real time
Thank you for your time and patience. waiting for your answers...
Thanks and greetings
Pichon

Hi Abhishek,

(1) If you set the retention to redundancy 2 policy, RMAN will keep only two recent backup copies and it will mark the rest obsolete backup copies (which means no need for recovery)

(2) If you set the retention policy to retrieve the window at 5 days, no matter how much you take, backups RMAN will keep the last backup of 5 days. And the backups before the last 5 days will be marked as obsolete. So that the two retention policies are different, which serve different purposes. We use according to our requirement.

(3) optimization means determine the most effective way to carry out the instructions. When you turn on the backup optimization, all orders backup will skip backups of any file if it has not changed and she has already been saved on the allocated device type. A file can be any file dbf, archived redo log or a RMAN "backup set". If you turn off your backup optimization, all files are backup no question that has already been taken.

(4) if backup optimization is configured, RMAN ignores backups of data files offline and read-only if the most recent backups were made the or after the closest point in the recovery window

(5) if backup optimization is not configured, RMAN will have all the backups, including read-only and offline tablespaces.

Hope this helps!

Kind regards

Pradeep. V

Why are my RMAN backup files still around?

Environment:

Oracle 11.2.0.3 EE on Solaris 64 bit

Good morning (at least it's morning here at the moment),

I have a test database that I have currently configured to do an incremental backup of level 0, every morning at about 03:00.

I also do one "archivelog backup all" every 4 hours during the day.

My archivelog deletion policy is "saved 2 times".

I put RMAN in place with a 8 day recovery window (ALL - see below).

I have multiple RMAN files dated 11 days ago.

Question: Why these files are still around?

RMAN> show all;

using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name APSMDMP2 are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 8 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 3;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE CHANNEL DEVICE TYPE DISK MAXPIECESIZE 5 G;
CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT   '/rman/APSMDMP2/APSMDMP2_%T_%t_%s_%p';
CONFIGURE CHANNEL 2 DEVICE TYPE DISK FORMAT   '/rman/APSMDMP2/APSMDMP2_%T_%t_%s_%p';
CONFIGURE CHANNEL 3 DEVICE TYPE DISK FORMAT   '/rman/APSMDMP2/APSMDMP2_%T_%t_%s_%p';
CONFIGURE MAXSETSIZE TO UNLIMITED;
CONFIGURE ENCRYPTION FOR DATABASE OFF;
CONFIGURE ENCRYPTION ALGORITHM 'AES128';
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE;
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO DISK;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11203/db_1/dbs/snapcf_APSMDMP2.f';

I have several entries in V$ ARCHIVED_LOG with a BACKUP_COUNT = 1 but they are all dated to 21 days ago and have DELETED status as shown here:

 SEQUENCE# ARC APPLIED   DEL S CTIME                         BACKUP_COUNT
---------- --- --------- --- - ----------------------------- ------------
      4625 YES NO        YES D 09-oct-2012 13:21:09                     1
      4626 YES NO        YES D 09-oct-2012 13:21:48                     1
      4627 YES NO        YES D 09-oct-2012 13:22:23                     1
      4628 YES NO        YES D 09-oct-2012 13:22:50                     1

I am able to see the content of the RMAN files, but I don't see anything that would cause them to not be removed during the RMAN runs. Here is an example of one of the files:

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ -------------------
6493    Incr 0  22.75G     DISK        01:35:54     2012-10-19:04:36:13
        BP Key: 6493   Status: AVAILABLE  Compressed: YES  Tag: FULL_DAILY
        Piece Name: /rman/APSMDMP2/APSMDMP2_20121019_797050819_6508_1
  List of Datafiles in backup set 6493
  File LV Type Ckp SCN    Ckp Time            Name
  ---- -- ---- ---------- ------------------- ----
  2    0  Incr 564035766  2012-10-19:03:00:19 /u05/oradata/APSMDMP2/sysaux01.dbf
  4    0  Incr 564035766  2012-10-19:03:00:19 /u05/oradata/APSMDMP2/users01.dbf
  5    0  Incr 564035766  2012-10-19:03:00:19 /u01/oradata/APSMDMP2/data_process_dt01_01.dbf
  9    0  Incr 564035766  2012-10-19:03:00:19 /u05/oradata/APSMDMP2/gmx_src_dt01_01.dbf
  10   0  Incr 564035766  2012-10-19:03:00:19 /u05/oradata/APSMDMP2/gmx_src_ix01_01.dbf
  12   0  Incr 564035766  2012-10-19:03:00:19 /u05/oradata/APSMDMP2/adm_data_ix01_01.dbf
  13   0  Incr 564035766  2012-10-19:03:00:19 /u05/oradata/APSMDMP2/patrol01_01.dbf
  16   0  Incr 564035766  2012-10-19:03:00:19 /u07/oradata/APSMDMP2/becosp_base_data_01.dbf
  18   0  Incr 564035766  2012-10-19:03:00:19 /u07/oradata/APSMDMP2/becosp_base_data_02.dbf
  27   0  Incr 564035766  2012-10-19:03:00:19 /u06/oradata/APSMDMP2/data_process_dt01_03.dbf
  30   0  Incr 564035766  2012-10-19:03:00:19 /u05/oradata/APSMDMP2/adm_data_dt01_02.dbf

I use the "DELETE NOPROMPT OBSOLETE' after each database and backup archivelog. Here is my command file 0 extra strength:

backup incremental level 0 cumulative database tag 'full_db';
backup archivelog all not backed up 2 times tag 'full_arch';
DELETE NOPROMPT OBSOLETE;

I know I can manually remove the files and everything with a resync OVERLAP but I was trying to understand why it happened in the first place.

Any suggestions are welcome.

Please let me know if you need more information.

Thank you very much!!

-gary

Hmm

Perhaps, I see your logic.

I post a thread as an editing tool that explains better than any I've seen.

Give him a look and see if the answer isn't here.

Best regards

mseberg

RAC RMAN backup

Hello

DB is 10.2.0.4 OS = BSG (CARS with 2 nodes BD01, db02). Here are the types of automated RMAN backups taken on db01.

-OCR
-Voting record
-Talespaces Snapshot
-Archivelog (hourly)
-Backup incremental level 0 (SUNDAY)
-backup incremental level 1 (Mon - Sat)
-Automatic backup of the control file and SPFILE (CONTROLFILE AUTOBACKUP ON)

Two big questions please. First of all, are these types of backups/backup are enough to RESTORE FULL speaking of RMAN backup on a RAC environment with 2 nodes? Otherwise please suggest what I need to backup?

Second, home backup location is /rman that I can see on db01 ONLY. This directory of /rman that I don't see on db02. My question is what db02 failure can I restore from directory /rman? or do I need to automate the backup also schedules on db02 separately?

[root@db01~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
                      3.9G  2.9G  814M  79% /
/dev/sda3             190M   34M  147M  19% /boot
tmpfs                  16G     0   16G   0% /dev/shm
/dev/mapper/VolGroup00-LogVol05
                      3.9G  137M  3.6G   4% /home
/dev/mapper/VolGroup00-LogVol03
                      3.9G  225M  3.5G   6% /tmp
/dev/mapper/VolGroup00-LogVol02
                      7.8G  3.7G  3.8G  50% /usr
/dev/mapper/VolGroup00-LogVol04
                      3.9G  379M  3.4G  11% /var
/dev/mapper/VolGroup00-ORACLE_BASE
                       12G  8.7G  2.6G  78% /oracle
10.10.28.140:/vol/px4cinconso
                       40G  1.4G   39G   4% /inconso_px
/dev/mapper/36001ec9000d5ea810000061349015d98
                      1.3T  551G  665G  46% /rman

[root@db02~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
                      3.9G  887M  2.9G  24% /
/dev/sda3             190M   34M  147M  19% /boot
tmpfs                  16G     0   16G   0% /dev/shm
/dev/mapper/VolGroup00-LogVol05
                      3.9G  137M  3.6G   4% /home
/dev/mapper/VolGroup00-LogVol03
                      3.9G  261M  3.5G   7% /tmp
/dev/mapper/VolGroup00-LogVol02
                      7.8G  3.7G  3.8G  50% /usr
/dev/mapper/VolGroup00-LogVol04
                      3.9G  355M  3.4G  10% /var
/dev/mapper/VolGroup00-ORACLE_BASE
                       12G  6.5G  4.8G  58% /oracle
10.10.28.140:/vol/px4cinconso
                       40G  1.4G   39G   4% /inconso_px

[oracle@db01~]$ rman target /

Recovery Manager: Release 10.2.0.5.0 - Production on Fri Feb 24 11:49:59 2012

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

connected to target database: F1 (DBID=1245145263)

RMAN> show all;

using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 28 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rman/f1/fullbackup/%F';
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/product/10.2.0/db/dbs/snapcf_f11.f'; # default

# Script for backup

level0 ()
run {
  allocate channel c1 type disk  maxpiecesize 2000M format '/rman/$ORACLE_SID/fullbackup/$ORACLE_SID-data-%U-%t';
  allocate channel c2 type disk  maxpiecesize 2000M format '/rman/$ORACLE_SID/archive/$ORACLE_SID-arch-%U-%t';
  backup incremental level 0 tag = weeklyfull database channel c1 
  plus archivelog tag = ARCH_$TODAY delete all input channel c2;
  release channel c1;
  release channel c2;
}

run {
  allocate channel c1 type disk;
  delete noprompt obsolete;
  release channel c1;
}

Bundle of thanks.

Kind regards

Published by: 910385 on February 24, 2012 03:00

Hi 910385,
The error on the node db02

ORA-19504: cannot create the file ' / rman/fp1/backup/c-1245145263-20120210-11.

is caused by your installation.
You have a /rman of mount point visible only on the node db01.
The controlfile autobackup setting triggers the creation of a backup of the controlfile:
-during the rman backup (this seems to work only on db01)
-in the case of a structural change in the database (eg. Adding a data file).
Sessions to make a structural change can be connected to one of your two instances, but the instance on db02 cannot create controlfile autobackup in /rman.
You must change the configuration and put the backup on a shared disk that is seen by the two systems.
Strangely, you have a shared file system:

10.10.28.140:/vol/px4cinconso 40G 1.4 G 39G 4% /inconso_px

Better would be to make a second for rman...
Kind regards
Tycho

CONFIGURATION BACKUP OPTIMIZATION;
Hi all

I have a doubt in RMAN - "CONFIGURATION BACKUP OPTIMIZATION ON;

Here it is the characteristics of this RMAN parameters

In order to safeguard the area of flash itself with RMAN recovery, you must set configuration backup optimization on IT.
Definition backup optimization on stop backups of read only tablespaces (RTO), whenever a backup is valid of the storage space exists in the RMAN catalog database.
If backup optimization is enabled, RMAN ignores backups of archived logs that have already been backed up on the allocated device.
I hope it's okay.

Here's my Question:

(D) I took a full backup and its valid, after a few minutes take another copy of the same database backup at this time here which should RAMN do this according to the highlighted above (* BOLD *) sentence.

my doubt is:

D2) I took the backup of repositories as below:

RMAN > backup tablespace system, applehut;
And this command brings me a valid backup in my local disk. After a minute, I wanted to take another tablespace, including the previous backup:

RMAN > backup system sysaux tablespace undotbs1, applehut;
This time also the RMAN is not omit tablespaces which already took a min before! Why this is happening, because according to the optimization strategy must omit the old right of tablespaces... I am right please clarify me if am wrong!

Please someone answer me...

Concerning
HAMEED

Published by: hamza on May 19, 2011 02:49
It will omit the tablespaces in offline mode only

OPTIMIZATION of the BACKUP of the databases is to Tablespaces that are READ only.
Do not test by setting a Tablespace Offline. Set the Tablespace READ ONLY to understand the functioning of the BACKUP OPTIMIZATION.

Hemant K Collette

Published by: Hemant K grapple on May 19, 2011 22:33

RMAN backups is missing...

Hi all.
I have a functional RMAN question...

Configuration of RMAN:_

RMAN> show all;

RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1; # default
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   '/u04/backup/vwood/vwood-arch-%s_%p_%Y%M%D.bkp';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/opt/oracle/product/9.2/dbs/snapcf_vwood.f'; # default

I am currently transfer our disk to tape backup strategy and have updated the entire test and archive backups with HP Server log file...
My current drive backups run with the command delete obsolete and for the last week or so that I was getting errors do not have an allocated channell interview. The tape drive is down for maintenance at the moment so I was ignorant to most...

Last night I noticed that they were not appearing in the output obsolete report more... I had 5 and one by one every hour, they stopped appearing, but they have not been removed...

_ The backup from 21:30

RMAN>
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type                 Key    Completion Time    Filename/Handle
-------------------- ------ ------------------ --------------------
Backup Set           670    Nov 20 2009 08:57:56
  Backup Piece       665    Nov 20 2009 08:57:56 rcworaprd-vwood-full<vwood_687:703414518:1>.dbf
Backup Set           671    Nov 20 2009 08:58:04
  Backup Piece       666    Nov 20 2009 08:58:04 rcworaprd-vwood-full<vwood_688:703414518:1>.dbf
Backup Set           672    Nov 20 2009 09:04:01
  Backup Piece       667    Nov 20 2009 09:04:01 rcworaprd-vwood-full<vwood_690:703414518:1>.dbf
Backup Set           673    Nov 20 2009 09:04:07
  Backup Piece       668    Nov 20 2009 09:04:07 rcworaprd-vwood-full<vwood_689:703414518:1>.dbf
Backup Set           674    Nov 20 2009 09:04:12
  Backup Piece       669    Nov 20 2009 09:04:12 rcworaprd-vwood-full<vwood_691:703415050:1>.dbf
Backup Set           675    Nov 20 2009 09:31:41
  Backup Piece       670    Nov 20 2009 09:31:41 /u04/backup/vwood/vwood-arch-692_1_20091120.bkp
Backup Set           676    Nov 20 2009 10:30:41
  Backup Piece       671    Nov 20 2009 10:30:41 /u04/backup/vwood/vwood-arch-693_1_20091120.bkp
Backup Set           677    Nov 20 2009 11:31:02
  Backup Piece       672    Nov 20 2009 11:31:02 /u04/backup/vwood/vwood-arch-694_1_20091120.bkp
Backup Set           678    Nov 20 2009 12:30:09
  Backup Piece       673    Nov 20 2009 12:30:09 /u04/backup/vwood/vwood-arch-695_1_20091120.bkp

_ The backup from 22:30

RMAN>
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type                 Key    Completion Time    Filename/Handle
-------------------- ------ ------------------ --------------------
Backup Set           671    Nov 20 2009 08:58:04
  Backup Piece       666    Nov 20 2009 08:58:04 rcworaprd-vwood-full<vwood_688:703414518:1>.dbf
Backup Set           672    Nov 20 2009 09:04:01
  Backup Piece       667    Nov 20 2009 09:04:01 rcworaprd-vwood-full<vwood_690:703414518:1>.dbf
Backup Set           673    Nov 20 2009 09:04:07
  Backup Piece       668    Nov 20 2009 09:04:07 rcworaprd-vwood-full<vwood_689:703414518:1>.dbf
Backup Set           674    Nov 20 2009 09:04:12
  Backup Piece       669    Nov 20 2009 09:04:12 rcworaprd-vwood-full<vwood_691:703415050:1>.dbf
Backup Set           675    Nov 20 2009 09:31:41
  Backup Piece       670    Nov 20 2009 09:31:41 /u04/backup/vwood/vwood-arch-692_1_20091120.bkp
Backup Set           676    Nov 20 2009 10:30:41
  Backup Piece       671    Nov 20 2009 10:30:41 /u04/backup/vwood/vwood-arch-693_1_20091120.bkp
Backup Set           677    Nov 20 2009 11:31:02
  Backup Piece       672    Nov 20 2009 11:31:02 /u04/backup/vwood/vwood-arch-694_1_20091120.bkp
Backup Set           678    Nov 20 2009 12:30:09
  Backup Piece       673    Nov 20 2009 12:30:09 /u04/backup/vwood/vwood-arch-695_1_20091120.bkp

23:30 backup:_

RMAN>
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type                 Key    Completion Time    Filename/Handle
-------------------- ------ ------------------ --------------------
Backup Set           672    Nov 20 2009 09:04:01
  Backup Piece       667    Nov 20 2009 09:04:01 rcworaprd-vwood-full<vwood_690:703414518:1>.dbf
Backup Set           673    Nov 20 2009 09:04:07
  Backup Piece       668    Nov 20 2009 09:04:07 rcworaprd-vwood-full<vwood_689:703414518:1>.dbf
Backup Set           674    Nov 20 2009 09:04:12
  Backup Piece       669    Nov 20 2009 09:04:12 rcworaprd-vwood-full<vwood_691:703415050:1>.dbf
Backup Set           675    Nov 20 2009 09:31:41
  Backup Piece       670    Nov 20 2009 09:31:41 /u04/backup/vwood/vwood-arch-692_1_20091120.bkp
Backup Set           676    Nov 20 2009 10:30:41
  Backup Piece       671    Nov 20 2009 10:30:41 /u04/backup/vwood/vwood-arch-693_1_20091120.bkp
Backup Set           677    Nov 20 2009 11:31:02
  Backup Piece       672    Nov 20 2009 11:31:02 /u04/backup/vwood/vwood-arch-694_1_20091120.bkp
Backup Set           678    Nov 20 2009 12:30:09
  Backup Piece       673    Nov 20 2009 12:30:09 /u04/backup/vwood/vwood-arch-695_1_20091120.bkp

And so on until they do show more...

At the end of each log, I get the error:

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 12/01/2009 23:30:22
RMAN-06091: no channel allocated for maintenance (of an appropriate type)

RMAN>

Recovery Manager complete.
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

I wonder why they no longer appear if they were not deleted...

They present as it is expired or obsolete...

I can not the tape drive to see if they are still on the tape or not that the player is still down for maintenance...
I was wondering what happens to them once they get this after 7 days... Is this a normal behavior RMAN?

Thanks to all the answers...

Jamie

Hi Jamie CC,.

Can you check what is actually located at:
/ u04/backup/vwood /.

Do you still have the file vwood-arch - 692_1_20091120.bkp?

If you do not use a catalog of recovery it could be information on backup items got years off the controlfile due to the control_file_record_keep_time parameter.

(see the control_file_record_keep_time parameter will tell you the setting).

Kind regards

Tycho

WITH THE HELP OF RMAN BACKUP CATALOG
Hello...

I INTEND TO TAKE THE "ORCL" DATABASE BACKUP USING THE CATALOGUE. FIRST, I CREATED A DATABASE USING DBCA NAMED "RMAN". NOW, IN THE FLASH RECOVERY AREA, I'LL HAVE TWO FOLDERS "ORCL" AND "RMAN".

MY QUESTION IS THAT... I HAVE USED WITH RMAN CATALOG AND TOOK THE GAME TO FULL DATABASE BACKUP AS BACKUP... BUT THE BACKUP SET WAS PLACED IN

E:\oracle\product\10.2.0\flash_recovery_area\ORCL\BACKUPSET\2009_07_29\O1_MF_NNNDF_FULLBACKUP_5703B10H_. BKP

I WANT TO KNOW WHEN I USE CATALOG RMAN DATABASE AS WHY IT IS IMPLEMENTED BACKUP ORCL...?
SO WHAT'S THE CHANCE OF CREATING A SEPARATE DATABASE "RMAN". ?
SEPARATE RMAN DATABSE IS JUST FOR CREAT CATALOG, THEN THE REGISTRY ORCL IN THIS CATALOG DATABASE?

THANKS FOR REPLYING...

I TOOK THE BACKUP AS BELOW...

............................................... RMAN DATABASE...

C:\Documents and Settings\Vortex > set oracle_sid = rman

C:\Documents and Settings\Vortex > sqlplus / as sysdba

SQL * more: Release 10.2.0.1.0 - Production on sea 29 Jul 11:31:20 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With partitioning, OLAP and Data Mining options

SQL > create user identified by human rman
* 2 default tablespace users *.
* 3 tablespace temporary temp *.
* 4 account unlock; *
Created by the user.

SQL > grant connect, resource, recovery_catalog_owner to rman;
Grant succeeded.

SQL > change the quota of rman to unlimited user on the users;
Modified user.

SQL > exit
Disconnected from the database to Oracle 10 g Enterprise Edition Release 10.2.0.1.0 - Production
With partitioning, OLAP and Data Mining options

C:\Documents and Settings\Vortex > rman@rman catalog rman

Recovery Manager: Release 10.2.0.1.0 - Production on sea Jul 29 11:33:08 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.

Catalog database recovery password:
connected to the recovery catalog database

RMAN > create catalog.
Recovery catalog created.

............................................... ORCL DATABASE...

Microsoft Windows XP [Version 5.1.2600]
Copyright (C) 1985-2001 Microsoft Corp.

C:\Documents and Settings\Vortex > set oracle_sid = orcl

C:\Documents and Settings\Vortex > rman@rman for catalog rman target /.

Recovery Manager: Release 10.2.0.1.0 - Production on sea Jul 29 11:37:10 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: ORCL (DBID = 1221198182)
Catalog database recovery password:
connected to the recovery catalog database

RMAN > register database;

registered in the recovery catalog database
from full resynchronization of the recovery catalog
full complete Resync

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 # by default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # 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 MAXSETSIZE TO UNLIMITED; # by default
CONFIGURE ENCRYPTION OF DATABASE # by default
CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' E:\ORACLE\PRODUCT\10.2.0\DB10G\DATABASE\SNCFORCL. ORA'; #

RMAN > CONFIGURE CONTROLFILE AUTOBACKUP ON;

new RMAN configuration settings:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration settings are stored successfully
from full resynchronization of the recovery catalog
full complete Resync

RMAN > outline report;

Report of the database schema

List of permanent data files

Size (MB) Tablespace RB segs Datafile file name

1 470 SYSTEM YES E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01. DBF
2 25 UNDOTBS1 E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\UNDOTBS01 YES. DBF
SYSAUX 3 230 NO E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSAUX01. DBF
4 5 USERS WITHOUT E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\USERS01. DBF

List of temporary files

File Size (MB) (MB) Maxsize Tempfile Tablespace name

1 E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\TEMP01 20 TEMP 32767. DBF

RMAN > run
* 2 > {allocate channel ch1 type disk; *}
* 3 > backup database tag = BACKUP; *
* 4 > release channel ch1. *
{* 5 >} *.

allocated channel: ch1
channel ch1: sid = 148 devtype = DISK

From backup 29 July 09
channel ch1: starting full datafile backupset
channel ch1: specifying datafile (s) in backupset
input datafile fno = 00001 name=E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01. DBF
input datafile fno = 00003 name=E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSAUX01. DBF
input datafile fno = name=E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\UNDOTBS01 00002. DBF
input datafile fno = 00004 name=E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\USERS01. DBF
channel ch1: starting piece 1 to 29 July 09
channel ch1: finished piece 1 to 29 July 09
room handle=E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2009_07_29\O1_MF_NNNDF_FULLBACKUP_570
3B10H_. Tag BKP = BACKUP comment = NONE
channel ch1: complete set of backups, time: 00:01:38
Backup finished in 29 July 09

From control file and SPFILE Autobackup 29 July 09
room handle=E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL\AUTOBACKUP\2009_07_29\O1_MF_S_693489105_5703F5L
K_. Comment BKP = NONE
File control finished and Autobackup SPFILE to 29 July 09
output channel: ch1.

RMAN >

Published by: Muhammad.Usman on July 28, 2009 23:01
You can also take your backups without a recovery catalog database. The additional advantage of using a database to catalog vs using the controlfile as repository (default average) target is essentially
>
RMAN automatically manages backup metadata in the database control file is saved. To protect and maintain metadata backup for long periods of time, the RMAN Repository is created in a separate database. This repository is generally referred to as a catalog of recovery. The benefits of using a catalog of recovery include:

*

Stores long-term backup information
*

Store the metadata for multiple databases
*

Restore a backup available on another system

Another reason to use a recovery catalog is the limited size of the target database control file. If the control file is too small to contain additional metadata from backup, then the existing backup information are crushed, making it difficult to restore and recover using these backups.
>

of http://download.oracle.com/docs/cd/B19306_01/server.102/b25159/configbp.htm#CHDBCHAC

Kind regards
Uwe

http://uhesse.WordPress.com

RMAN backup location must change and remove obsolete

Dear Experts,
I'm working on the following environment,
Operating system: Windows server 2012 R2
Oracle version: 11.2.0.1.0 release
Type of RMAN backup: Cumulative (preferred by the direction and I can't change it in differential backup)
My current situation,
I set up RMAN and H: drive for purposes of backup and G: for Archivelog.
Recently, my city was covered by the flood waters and the server works not for a week so that we delete obsolete level 0 does not work.
Currently there is not enough space to run a level 1 and level 0, while I should change the backup location.
My Question is,
(1) I need to change this location of drive H: to G: drive backup backup correctly without error not enough space.
(2) after having taken a level 1 and level 0, depending on my 1 redundancy, RMAN mechanism should delete obsolete backup disk without failure G: and H:.
Kindly help me how to get to my need. This will help me, thanks in advance

You can

1. replace the DB_RECOVERY_FILE_DEST G:

2 run backups

3. wait for the DELETE OBSOLETE delete obsolete backups of H:

and then

4. change the DB_RECOVERY_FILE_DEST return h as it was more early

In this way, you don't have to use the FORMAT or CHANNEL of CONFIGURE commands (I was referring to CONFIGURE CHANNEL, not ALLOCATE CHANNEL) to change the destination of the backup

Hemant K Collette

Waiting for redo log file missing when restore main database using RMAN backup that was taken on the database physical standby

Here's my question after tons of research and test without have the right solutions.
Target:
(1) I have a 12.1.0.2 database unique main enterprise 'testdb' as database instance running on the server "node1".
(2) I created physical standby database "stbydb" on the server "node2".
(3) DataGuard running on the mode of MaxAvailability (SYNC) with roll forward in real time 12 default c apply.
(4) primary database has 3 groups of one-man redo. (/oraredo/testdb/redo01.log redo02.log redo03.log)
(5) I've created 4 standby redo logfiles (/oraredo/testdb/stby01.log stby02.log stby03.log stby04.log)
(6) I do RMAN backup (database and archivelog) on the site of relief only.
(7) I want to use this backup for full restore of the database on the primary database.
He is a DR test to simulate the scenario that has lost every primary & Eve total servers.
Here is how to save, on the database pending:
(1) performance 'alter database recover managed standby database Cancel' to ensure that compatible data files
(2) RMAN > backup database;
(3) RMAN > backup archivelog all;
I got elements of backup and copied to primary db Server something like:
/Home/Oracle/backupset/o1_mf_nnndf_TAG20151002T133329_c0xq099p_.BKP (data files)
/Home/Oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.BKP (spfile & controlfile)
/Home/Oracle/backupset/o1_mf_annnn_TAG20151002T133357_c0xq15xf_.BKP (archivelogs)
So here's how to restore, on the main site:
I clean all the files (data files, controlfiles oder all gone).
(1) restore spfile from pfile
RMAN > startup nomount
RMAN > restore spfile from pfile ' / home/oracle/pfile.txt' to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';
(2) modify pfile to convert to db primary content. pFile shows below
*.audit_file_dest='/opt/Oracle/DB/admin/testdb/adump '
* .audit_trail = "db".
* full = '12.1.0.2.0'
*.control_files='/oradata/testdb/control01.ctl','/orafra/testdb/control02.ctl'
* .db_block_size = 8192
* .db_domain = "
*.db_file_name_convert='/testdb/','/testdb /'
* .db_name = "testdb".
* .db_recovery_file_dest ='/ orafra'
* .db_recovery_file_dest_size = 10737418240
* .db_unique_name = "testdb".
*.diagnostic_dest='/opt/Oracle/DB '
* .fal_server = "stbydb".
* .log_archive_config = 'dg_config = (testdb, stbydb)'
* .log_archive_dest_2 = "service = stbydb SYNC valid_for = (ONLINE_LOGFILE, PRIMARY_ROLE) db_unique_name = stbydb'"
* .log_archive_dest_state_2 = 'ENABLE '.
*.log_file_name_convert='/testdb/','/testdb /'
* .memory_target = 1800 m
* .open_cursors = 300
* runoff = 300
* .remote_login_passwordfile = "EXCLUSIVE."
* .standby_file_management = "AUTO".
* .undo_tablespace = "UNDOTBS1.
(3) restart db with updated file pfile
SQLPLUS > create spfile from pfile='/home/oracle/pfile.txt'
SQLPLUS > the judgment
SQLPLUS > startup nomount
(4) restore controlfile
RMAN > restore primary controlfile to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';
RMAN > change the editing of the database
(5) all elements of backup catalog
RMAN > catalog starts by ' / home/oracle/backupset / '.
(6) restore and recover the database
RMAN > restore database;
RMAN > recover database until the SNA XXXXXX; (this YVERT is the maximum in archivelog backups that extends beyond the scn of the backup of the data file)
(7) open resetlogs
RMAN > alter database open resetlogs;
Everything seems perfect, except one of the file log roll forward pending is not generated
SQL > select * from v$ standby_log;
ERROR:
ORA-00308: cannot open archived log ' / oraredo/testdb/stby01.log'
ORA-27037: unable to get file status
Linux-x86_64 error: 2: no such file or directory
Additional information: 3
no selected line
I intended to use the same backup to restore primary basic & helps record traffic and the downtime between them in the world of real output.
So I have exactly the same steps (except STANDBY restore CONTROLFILE and not recover after database restore) to restore the database pending.
And I got the same missing log file.
The problem is:
(1) complete alert.log filled with this error, not the concern here
(2) now repeat it in real time apply won't work since the Party shall LGWR shows always "WAITING_FOR_LOG."
(3) I can't delete and re-create this log file
Then I tried several and found:
The missing standby logfile was still 'ACTIVE' at present RMAN backup was made.
For example, on db standby, under Group #4 (stby01.log) would be lost after the restoration.
SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;
GROUP # SEQUENCE # USED STATUS
---------- ---------- ---------- ----------
4 19 ACTIVE 133632
5 0 0 UNASSIGNED
6 0 0 not ASSIGNED
7 0 0 UNASSIGNED
So until I take the backup, I tried on the primary database:
SQL > alter system set log_archive_dest_state_2 = delay;
This was the Group of standby_log side Eve #4 was released:
SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;
GROUP # SEQUENCE # USED STATUS
---------- ---------- ---------- ----------
4 0 0 UNASSIGNED
5 0 0 UNASSIGNED
6 0 0 not ASSIGNED
7 0 0 UNASSIGNED
Then, the backup has been restored correctly without missing standby logfile.
However, to change this primary database means break DataGuard protection when you perform the backup. It's not accept on the production environment.
Finally, my real questions come:
(1) what I do may not do on parameter change?
(2) I know I can re-create the control file to redo before delete and then recreate after. Is there any simple/fast to avoid the standby logfile lost or recreate the lost one?
I understand that there are a number of ways to circumvent this. Something to keep a copy of the log file waiting restoration progress and copy up one missing, etc, etc...
And yes I always have done no real-time applies "to the aid of archived logfile" but is also not accept mode of protection of production.
I just want proof that the design (which is displayed in a few oracle doc Doc ID 602299.1 is one of those) that backs up data backup works effectively and can be used to restore the two site. And it may be without spending more time to resume backups or put the load on the primary database to create the database before.
Your idea is very much appreciated.
Thank you!

Hello

1--> when I take via RMAN backup, RMAN does not redo log (ORL or SRL) file, so we cannot expect ORLs or SRL would be restored.

2nd--> when we opened the ORL database should be deleted and created

3rd--> Expecting, SRL should not be an issue.we should be able to do away with the fall.

DR sys@cdb01 SQL > select THREAD #, SEQUENCE #, GROUP #, STATUS from v$ standby_log;

THREAD # SEQUENCE # GROUP # STATUS

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

1 233 4 ACTIVE

1 238 5 ACTIVE

DR sys@cdb01 SQL > select * from v$ logfile;

GROUP # STATUS TYPE MEMBER IS_ CON_ID

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

3 /u03/cdb01/cdb01/redo03.log no. 0 online

/U03/cdb01/cdb01/redo02.log no. 0 2 online

1 /u03/cdb01/cdb01/redo01.log no. 0 online

4 /u03/cdb01/cdb01/stdredo01.log WATCH No. 0

/U03/cdb01/cdb01/stdredo02.log EVE 5 No. 0

DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

method: cannot access the /u03/cdb01/cdb01/stdredo01.log: no such file or directory

DR sys@cdb01 SQL >! ls - ltr /u03/cdb01/cdb01/stdredo02.log

-rw - r-. 1 oracle oinstall 52429312 17 Oct 15:32 /u03/cdb01/cdb01/stdredo02.log

DR sys@cdb01 SQL > alter database force claire logfile 4;

change the database group claire logfile 4

*

ERROR on line 1:

ORA-01156: recovery or current flashback may need access to files

DR sys@cdb01 SQL > alter database recover managed standby database cancel;

Database altered.

DR sys@cdb01 SQL > change the database group claire logfile 4;

Database altered.

DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

-rw - r-. 1 oracle oinstall 52429312 17 Oct 15:33 /u03/cdb01/cdb01/stdredo01.log

DR sys@cdb01 SQL >

If you do, you can recreate the controlfile without waiting for redo log entry...

If you still think it's something is not acceptable, you must have SR with support to analyze why he does not abandon SRL when controlfile_type is "underway".

Thank you

Backup Optimization doesn't work not as expected!

Hello
Oracle: 11.2.0.3
O / s: OEL 5.4 32-bit
Here's my configuration of RMAN
So even if backup optimization is enabled, why every time I take runs a command 'backup database', as always backup all data files.
This is a database of test on VM, kind of data aren't really change on all areas of storage.
Not sure why RMAN is not jump data files while performing the backup?
-Learner

OPTIMIZATION will only jump data files that have absolutely no change since the last backup - that is to say reading only datafiles.

Hemant K Collette

question of RMAN backup optimization

Similar Questions

Maybe you are looking for