RMAN expired Backup

Similar Questions

• Cannot expire backups

  Hello world!!
  
  Unable to do a delete im expired backups
  
  RMAN > run {}
  2 > crosscheck backup;
  3 > overlaps with the copy;
  4 > overlap archivelog all;
  5 > delete noprompt expired backup;
  6 > delete expired noprompt copy;
  7 > delete noprompt expired archivelog all;
  8 > delete noprompt obsolete;
  9 > backup current controlfile;
  {10 >}
  
  iniciando completa del recuperaci¾n catsslogo resincronizaci¾n
  resincronizaci¾n completa terminada
  asignado channel: ORA_SBT_TAPE_1
  channel ORA_SBT_TAPE_1: sid = 457 devtype = SBT_TAPE
  channel ORA_SBT_TAPE_1: for Oracle Data Protection: version 5.4.1.0
  asignado channel: ORA_DISK_1
  channel ORA_DISK_1: sid = 461 devtype = DISK
  cruzada comprobaci¾n a parte of backup: is ha detectado are "EXPIRATION".
  Manager of parte of copia seguridad=D:\ORACLE\PRODUCT\10.2.0\DB10G\DATABASE\6MMD64LF_1_1 recid = 32812 marca = 752030385
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03009: fallo del comando overlap el canal ORA_SBT_TAPE_1 fr 17/05 / 2012 11:16:53
  ORA-27191: sbtinfo2 ha UN error return
  
  I realized that in this way D:\ORACLE\PRODUCT\10.2.0\DB10G\DATABASE\ I have a lot of files that I don't know what they are useful for, among them, the 6MMD64LF_1_1, with a similar format.
  
  I can remove them? They are the reason for unsuccessful expired backup?
  
  RMAN > show all.
  
  parssmetros of configuraci¾n of RMAN:
  CONFIGURE RETENTION POLICY TO RECOVERY OF 7-DAY WINDOW;
  CONFIGURE BACKUP OPTIMIZATION # by default
  CONFIGURE DEFAULT DEVICE TYPE TO 'DRIVE '.
  CONFIGURE CONTROLFILE AUTOBACKUP ON;
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F ';
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK to 'E:\Backup\PREDB\RMAN_INC0\backup_controlfile_%F ';
  SET UP THE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1 BACKUP BACKUPSET TYPE;
  SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
  CONFIGURE BACKUP COPIES OF DATA FILE FOR DEVICE TYPE SBT_TAPE TO 1; # by default
  CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
  CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE SBT_TAPE TO 1; # by default
  CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
  CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'ENV = (TDPO_OPTFILE = C:\Program Files\Tivoli\TSM\AgentOBA64\tdpo.opt)';
  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:\BACKUP\PREDB\RMAN_INC0\SNCFPREDB. ORA';
  
  Thank you

  RMAN-03009: fallo del comando overlap el canal ORA_SBT_TAPE_1 fr 17/05 / 2012 11:16:53
  ORA-27191: sbtinfo2 ha UN error return

  "CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'ENV = (TDPO_OPTFILE = C:\Program Files\Tivoli\TSM\AgentOBA64\tdpo.opt)';

  Is it purposely configured?
  See the thread
  https://forums.Oracle.com/forums/thread.jspa?MessageID=10337571�

• 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

• RMAN bypass backup can be taken from question?

  Hi all

  pretty simple question (I hope that ):

  I use the suite at the moment for example:

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

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

  run
  {

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

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

  
  

  cleaning etc release channels

  }

  PS: question side bonus points

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

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

  Thanks in advance.

  
  
  

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

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

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

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

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

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

• How to expire backup manually image via VDP

  Hello

  I want to expire backup manually image after successful backup, everyone knows?

  Thank you

  Walker

  Well, now I need to backup VMs, it will compare the data with the deleted data from deduplication, do you mean this?

  Yes. I mean that it will always use the deleted data for deduplication because the deletion to the user interface is as marking for deletion and is still not deleted in the destination of deduplication. As says, it is actually deleted only during the blackout window.

  You will also note that deduplication is not at the level of the image, but at the level of the blocks.

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

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

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

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

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

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

  This is a backup log:

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

  From backup 4 July 13

  allocated channel: ORA_DISK_1

  channel ORA_DISK_1: sid = 1043 devtype = DISK

  channel ORA_DISK_1: additional start-up compressed 1 datafile backupset

  channel ORA_DISK_1: specifying datafile (s) in backupset

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

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

  ...

  channel ORA_DISK_1: starting total, 1 to 4 July 13

  channel ORA_DISK_1: finished piece 1 to 4 July 13

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

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

  Backup finished on 4 July 13

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

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

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

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

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

  Hemant K Collette

• RAC RAC CLONE OF RMAN cold backup

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

  Hello

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

  Use Rman cold backup

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

  Copy these to the remote host backup sets

  (2) clone of the database on the remote host

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

  RMAN > catalogue start with "";

  Restore controlfile

  RMAN > restore controlfile;

  RMAN > restore database;

  RMAN > restore database;

  On the success of the recovery

  RMAN > sql 'alter database open;

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

  Srvctl user to add resources

  Use: srvctl

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

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

  user11993454 wrote:
  Hello

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

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

  Thank you.

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

• EBS R11i Rman DB Backup error

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

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

• -Obsolete - RMAN expired

  Dear friends,
  
  I'm with RMAN to back up my database.
  
  That means backup obsolete and outdated?
  
  When they reach such a State?
  
  Please guide me.
  
  Thank you

  >
  A backup is obsolete when the REPORT OUTDATED or OBSOLETE REMOVE determines, based on the user-defined retention policy, it is not necessary for recovery. A backup is considered a backup expired only when RMAN performs an overlap and can not find the file. In short, obsolete means that a file is not necessary, whereas expired way, it is not found.
  >

  Please read about the RMAN backup retention policies: http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmcncpt.htm#BRADV99966.

• RMAN incremental backup

  Hi all

  I have a question, I am on RHEL-6 / Oracle 11 GR 2.

  After taking the backup of level 0 (RMAN), if I plan tale level1 backup then how oracle knows that they are the backup piece is considered a level 1 backup.

  I mean, that's how oracle knows that these are the blocks that had to be backeup.

  Kind regards.

  Please refer to the https://docs.oracle.com/cd/B19306_01/backup.102/b14192/bkup004.htm documentation

  Article: 4.4.1 Alogrithm incremental backup

  -Jonathan Rolland

• RMAN SBT_TAPE BACKUP FAILURE

  Hi all

  I met the following error when backing up the database. The device type is SBT_TAPE. We have replaced the tape media but still error persist.see journal of the errors below:

  RMAN-03009: failure of the backup command on channel t2 to 2015/12/29 07:10:49

  (ORA-19509: impossible de supprimer le fichier sequeIntial, gérer = «diqq0t84_1_1», parms="ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.opt)".

  ORA-27027: sbtremove2 returned error

  ORA-19511: error received from layer media manager, error text:

  ANS1355E Session (RC55) rejected: off server

  ORA-27191: sbtinfo2 returned the error

  Additional information: 3276

  ORA-19511: error received from layer media manager, error text:

  ORACLE recovery catalog database error: ORA-03113: end of file on communication channel

  Process ID: 13762638

  Session ID: 166 serial number: 18103

  Any ideas.

  Thank you.

  Hello

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

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

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

  RMAN-06004: the recovery catalog database ORACLE error: ORA-03113: end of file on communication channel

  Process ID: 7667754

  Session ID: 166 serial number: 18303

  ORACLE recovery catalog database error: ORA-03114: not connected to ORACLE

  Common causes of the error ORA-03114 include:

  • Process of Web server or headset does not work
  • Missing entry in the tnsnames.ora.
  • Network problems.
  • Problems with connection pooling (shared servers, MTS).

  Kind regards

  Katia V.

• 10g | RMAN | Daily backups in case files

  Hi guys

  RMAN > show all.

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

  RMAN configuration parameters are:

  CONFIGURE REDUNDANCY 3 RETENTION STRATEGY;

  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 'D:\oracle\rman\backup\%F ';

  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 the FORMAT of DISC TYPE CHANNEL DEVICE "D:\oracle\rman\backup\%U";

  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 ' D:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\SNCFSCT. ORA'; # by default

  RMAN >

  The foregoing describes RMAN configuration, I've done with the installation of 10g in my laptop for learning purposes. Now, how can I make sure that every day the backup is created in case files as below mentioned few

  D:\oracle\product\10.2.0\flash_recovery_area\SCT\BACKUPSET\2015_11_21

  D:\oracle\product\10.2.0\flash_recovery_area\SCT\BACKUPSET\2015_11_22

  D:\oracle\product\10.2.0\flash_recovery_area\SCT\BACKUPSET\2015_11_23

  D:\oracle\product\10.2.0\flash_recovery_area\SCT\BACKUPSET\2015_11_24

  My backups used to get created under individual records until I changed the type of RMAN channel with "CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'D:\oracle\rman\backup\%U';' "

  
  

  Please suggest.

  
  

  Thanks in advance

  rthampi wrote:

  Hi guys

  RMAN > show all.

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

  RMAN configuration parameters are:

  CONFIGURE REDUNDANCY 3 RETENTION STRATEGY;

  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 'D:\oracle\rman\backup\%F ';

  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 the FORMAT of DISC TYPE CHANNEL DEVICE "D:\oracle\rman\backup\%U";

  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 ' D:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\SNCFSCT. ORA'; # by default

  RMAN >

  The foregoing describes RMAN configuration, I've done with the installation of 10g in my laptop for learning purposes. Now, how can I make sure that every day the backup is created in case files as below mentioned few

  D:\oracle\product\10.2.0\flash_recovery_area\SCT\BACKUPSET\2015_11_21

  D:\oracle\product\10.2.0\flash_recovery_area\SCT\BACKUPSET\2015_11_22

  D:\oracle\product\10.2.0\flash_recovery_area\SCT\BACKUPSET\2015_11_23

  D:\oracle\product\10.2.0\flash_recovery_area\SCT\BACKUPSET\2015_11_24

  My backups to be created under individual records until I changed the type of RMAN channel with ' CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'D:\oracle\rman\backup\%U ';

  
  

  Please suggest.

  Thanks in advance

  These 'individual files' report to the FRA.  What you need to do is allow rman use the FIU, which it wants to do by default.  Then clear your default settings trying to name/place your backups differently.

• Export vs rman as backup strategy

  I just joined new company and owner oracle DBA confessed that they have never used in all of their many years as a DBA Oracle rman.  Currently, they have 7 days of files dmp to export for each prod database.  I started to create backups rman for each prod dB and I asked if we can stop exports altogether.  Holder s/n, says exports are still needed in case we need to restore a table or in the case where we need to refresh a development/test environment.  I submit that rman can do and I communicated that I never used exports in a special or as needed case either to move an oracle dB between different operating systems or incompatible versions.  All export their production databases every night?  I've been an Oracle DBA since 10g but I've always been the unique oracle DBA in the shops/companies that I worked.  It is the first time I had a DBA experienced to work with.  I'm surprised actually kind of which my colleague has never used rman being that they are so widely experienced.  Dig deeper, they say they have used the NetApp as their backup method and they try to get configured in my current company that tells me will make rman irrelevant.  What do you think?

  2983472 wrote:

  I just joined new company and owner oracle DBA confessed that they have never used in all of their many years as a DBA Oracle rman.  Currently, they have 7 days of files dmp to export for each prod database.  I started to create backups rman for each prod dB and I asked if we can stop exports altogether.  Holder s/n, says exports are still needed in case we need to restore a table or in the case where we need to refresh a development/test environment.  I submit that rman can do and I communicated that I never used exports in a special or as needed case either to move an oracle dB between different operating systems or incompatible versions.  All export their production databases every night?  I've been an Oracle DBA since 10g but I've always been the unique oracle DBA in the shops/companies that I worked.  It is the first time I had a DBA experienced to work with.  I'm surprised actually kind of which my colleague has never used rman being that they are so widely experienced.  Dig deeper, they say they have used the NetApp as their backup method and they try to get configured in my current company that tells me will make rman irrelevant.  What do you think?

  My, my, my.  Your recent history of the display, you seem to have a lot of questions with your new business.

  In this case, you are partially right.  It is unacceptable for this "very experienced" s/n do not use rman and see no need of it.  If his backup strategy should only take nightly exports, it has been lucky and lives on borrowed time.  If the database is corrupted or lost, these exports don't you a good few until what you create - from scratch - a database of work.  And even then, only, you will have a point in time as a recovery point.

  NetApp is concerned, that I've never used but I understand that it is simply wraps around rman.  Perhaps, this can be handy.  Until the disaster where you also get trashed NetApp configurations.  No, when it comes back up, and more important again, recovering from a disaster, I want to work closely with the oracle supplied and approved method.  The extra layers less potentially go wrong, the better.

  If they want to continue taking exports every night, he certainly won't do any harm, as long as they realize that is secondary to the required rman backups.  All my databases are backed up with rman.  Some but not all also have nightly exports.  It depends on the requirements.  There are some things for which having a practice of export is better than to rely solely on rman.

• ASM files using RMAN backupset backup system migration

  my script to backup daily as below

  backup in the format of compressed backupset "$BACKUP_DIR/db_%U" database

  backup current controlfile "$BACKUP_DIR/Cont_%U" format

  backup as backupset archivelog Tablet format all '$BACKUP_DIR/arch_%U ';

  It is possible to migrate the database ASM uses above backup backupset RMAN?

  because I restore the database is restored, the problem is when he try to recover it, unable to understand the archivelog and redlog files.

  Hello

  in fact, after I moved the pieces to another server and called with RMAN (including the archivelog files)

  1. When you have moved to another server, then at this stage - my hypothesis, you have restored the controlfile to fileystem and mounted

  2. as you said moved to another server, the parts are on file system or (ASM location - still the second server can see)? If your answer is no, when you catalog now, controfile must save it with the file system path but not ASM

  Note - If you're still see ASM path then. the migration of the ASM to no - asm (the steps are not correct) logically you went wrong and implementation/execution thrown.

  3. provide the plan and execution - what you did (while we can fix). To be honest, while on the move DB to non - asm, why you need first to recovery? Tell me about your backup procedure itself is gone bad.

  To be honest, you try to database host of ASM no - asm as backup in function (but no real process of moving).  Therefore, in spite of the use of rman backup in dual function duplication... you have implemented in the wrong approach.

  This is the reason why I have provided the link and examples to understand.

  Hope you understand now.

  -Pavan Kumar N