Scribd
Upload
49 views

Lab-06-Using Optional Backup Features

Uploaded by

Arif Ahmad
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
49 views

Lab-06-Using Optional Backup Features

Uploaded by

Arif Ahmad
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

Oracle Internal & Oracle Academy Use Only

Practices for Lesson 6: Using


Optional Backup Features
Practices for Lesson 6: Overview

Overview
In this practice, you will use RMAN to create an archival backup.

Oracle Internal & Oracle Academy Use Only

Copyright © 2022, Oracle and/or its affiliates.

80 Practices for Lesson 6: Using Optional Backup Features


Practice 6-1: Creating an Archival Backup

Overview
In this practice, you create an archival backup, that is, a backup that is not under your normal
retention policies and it is not in your normal fast recovery area (FRA) destination. This KEEP
FOREVER database backup could be used for recovery if some of your later hands-on activities
were to require it. Archival backups can be created with an open or a mounted database.
You must use a recovery catalog to be able to create an archival backup of an OPEN database.
Without a recovery catalog, you must put the database in a MOUNTED state.

Timing Estimate
It should take approximately 20 minutes to complete this practice.

Oracle Internal & Oracle Academy Use Only


Tasks
1. Open a terminal window and log in to RMAN.
$ rman target "'/ as sysbackup'"
…
connected to target database: ORCLCDB (DBID=2778750799)

RMAN>
2. Shut down and then restart the database instance in MOUNT mode so you can create a
backup copy of the entire database in a mounted state.
RMAN> SHUTDOWN IMMEDIATE;

using target database control file instead of recovery catalog


database closed
database dismounted
Oracle instance shut down

RMAN> STARTUP MOUNT;

connected to target database (not started)


Oracle instance started
database mounted
…
RMAN>
3. Attempt to make an archival backup of your ORCLCDB database with the KEEP FOREVER
option.
RMAN> BACKUP AS COPY DATABASE KEEP FOREVER;
Starting backup at 2019-06-21:15:00:29

Copyright © 2022, Oracle and/or its affiliates.

Practices for Lesson 6: Using Optional Backup Features 81


allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=260 device type=DISK
RMAN-00571:
===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS
===============
RMAN-00571:
===========================================================
RMAN-03002: failure of backup command at 06/21/2019 15:00:30
RMAN-06522: KEEP FOREVER option is not supported without the
recovery catalog

RMAN>

Oracle Internal & Oracle Academy Use Only


Question: Why did the backup command fail?
Answer: It failed because a backup with the KEEP FOREVER option requires the use of a
recovery catalog. A recovery catalog is required when KEEP FOREVER is specified because
backup records will eventually age out of the control file.
4. Attempt to make an archival backup of your ORCLCDB database that will be kept for 365
days.
RMAN> BACKUP AS COPY DATABASE KEEP UNTIL TIME 'SYSDATE+365';

Starting backup at 2019-06-21:15:14:05

using channel ORA_DISK_1


backup will be obsolete on date 2020-06-20:15:14:05
archived logs required to recover from this backup will be
backed up
channel ORA_DISK_1: starting datafile copy
input datafile file number=00001
name=/u01/app/oracle/oradata/ORCLCDB/system01.dbf
RMAN-03009: failure of backup command on ORA_DISK_1 channel at
06/21/2019 15:14:05
ORA-19811: cannot have files in DB_RECOVERY_FILE_DEST with keep
attributes
continuing other job steps, job failed will not be re-run
…
RMAN-00571:
===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS
===============
RMAN-00571:
===========================================================
RMAN-03002: failure of backup command at 06/21/2019 15:14:07

Copyright © 2022, Oracle and/or its affiliates.

82 Practices for Lesson 6: Using Optional Backup Features


ORA-19811: cannot have files in DB_RECOVERY_FILE_DEST with keep
attributes

RMAN>
Question: Why did the backup command fail?
Answer: It failed because a backup with the KEEP option (an archival backup) cannot be
written to the Fast Recovery Area. Allowing this has the potential of causing the Fast
Recovery Area to quickly run out of space.
5. Create an archival backup with a FORMAT clause that will direct RMAN to create the backup
in the /home/oracle/backup directory and keep it for 365 days.
RMAN> BACKUP DATABASE FORMAT '/home/oracle/backup/%U' TAG
keep_db_tag KEEP UNTIL TIME 'SYSDATE+365';

Oracle Internal & Oracle Academy Use Only


Starting backup at 2019-06-21:15:39:34

using channel ORA_DISK_1


backup will be obsolete on date 2020-06-20:15:39:34
archived logs required to recover from this backup will be
backed up
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=/u01/app/oracle/oradata/ORCLCDB/system01.dbf
…
using channel ORA_DISK_1
backup will be obsolete on date 2020-06-20:15:40:12
archived logs will not be kept or backed up
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
channel ORA_DISK_1: starting piece 1 at 2019-06-21:15:40:13
channel ORA_DISK_1: finished piece 1 at 2019-06-21:15:40:14
piece handle=/home/oracle/backup/32u4lp6s_1_1 tag=KEEP_DB_TAG
comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 2019-06-21:15:40:14

RMAN>
6. Open the database.
RMAN> alter database open;
Statement processed

Copyright © 2022, Oracle and/or its affiliates.

Practices for Lesson 6: Using Optional Backup Features 83


RMAN>
7. Delete obsolete backups. Be sure to respond YES to the prompt. Note: You may not have
any obsolete backups.
RMAN> delete obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
-------------------- ------ ------------------ -----------------
---
Backup Set 38 2019-06-20:21:12:48

Oracle Internal & Oracle Academy Use Only


Backup Piece 38 2019-06-20:21:12:48
/u01/app/oracle/fast_recovery_area/ORCLCDB/autobackup/2019_06_20
/o1_mf_s_1011474768_gjqxpjsb_.bkp
Backup Set 39 2019-06-20:21:24:02
Backup Piece 39 2019-06-20:21:24:02
/u01/app/oracle/fast_recovery_area/ORCLCDB/autobackup/2019_06_20
/o1_mf_s_1011475441_gjqycl1b_.bkp

Do you really want to delete the above objects (enter YES or


NO)? YES
deleted backup piece
backup piece
handle=/u01/app/oracle/fast_recovery_area/ORCLCDB/autobackup/201
9_06_20/o1_mf_s_1011474768_gjqxpjsb_.bkp RECID=38
STAMP=1011474768
deleted backup piece
backup piece
handle=/u01/app/oracle/fast_recovery_area/ORCLCDB/autobackup/201
9_06_20/o1_mf_s_1011475441_gjqycl1b_.bkp RECID=39
STAMP=1011475442
Deleted 2 objects

RMAN>
8. Exit RMAN.
RMAN> exit
…
$
9. Close the terminal window.

Copyright © 2022, Oracle and/or its affiliates.

84 Practices for Lesson 6: Using Optional Backup Features

You might also like