Move your mouse over this icon to show all screenshots.
You can also move your mouse over each individual icon to see only the screenshot
associated with it.
Configuring the Flash
Recovery Area and ARCHIVELOG Mode
The flash recovery area is a unified storage location for
all recovery related files and activities in an Oracle database. All files that
are needed to completely recover a database from a media failure are part of
the flash recovery area. The recovery related files that can be created in the
flash recovery area include: archived redo log files, control files, backups
created by Recovery Manager (RMAN), flashback logs, and the change tracking
file. Oracle recommends the change tracking file be created on the same disks
as the database files. In fact, if you set up OMF, and you issue the command
to enable change tracking, the file is automatically created in the directory
specified for the database files.
By allocating a storage location and unifying related recovery
files within a specific area, the Oracle database server relieves the database
administrator from having to manage the disk files created by these components.
When setting up a flash recovery area, you choose a directory,
file system or Automatic Storage Management disk group to hold the files, and
set a disk quota for the maximum space to be used for all files stored in the
flash recovery area. You must choose a location large enough to accommodate
the required disk quota. When the disk space limit is approached, the Oracle
server can delete nonessential files to make room for new files, subject to
the limitations of the RMAN retention policy.
The flash recovery area should be on a separate disk from
the working area, where active database files such as datafiles, control files,
online redo logs, and change tracking files used in incremental backups are
stored. Keeping the flash recovery area on the same disk as the working area
exposes you to loss of both your live database files and backups in the event
of a disk failure.
You can configure the flash recovery area and ARCHIVELOG mode
when you create the database. If you did not perform these tasks when you created
the database, follow the steps below to configure the flash recovery area and
ARCHIVELOG mode:
1.
At the operating system prompt, create a directory for
the flash recovery area. Execute the following commands:
cd $ORACLE_BASE
mkdir flash_rec_area
2.
Log in to Enterprise Manager Database Console by opening
your browser and specifying the SYS username and password as SYSDBA.
Click Login.
3.
Click Maintenance on your Oracle Database
Home page.
4.
Select Configure Recovery Settings in the Backup/Recovery
section. You can use the Configure Recovery Settings page to configure
the settings for the recovery utility, including the Flash Recovery Area.
5.
The Configure Recovery Settings page appears.
Scroll to the Flash Recovery Area section. Configure the flash
recovery area by entering the following values in the appropriate fields:
Flash Recovery Area Location: <directory you created
in step 1>
Flash Recovery Area Size: <required size for your flash recovery
area>
Scroll up to the top of the window.
6.
Check Archive Log Mode to configure ARCHIVELOG
mode for your database. Click Apply.
7.
A message confirming your changes is displayed. To complete
the configuration of ARCHIVELOG mode, the database instance must be shut
down. Click Yes to shut down the instance and restart it.
8.
The Restart Database:Specify Host and Target Database
Credentials page is displayed. Enter your host credentials and database
credentials. Click OK.
9.
The Restart Database:Confirmation page is displayed.
Click Yes to shutdown the instance and restart it.
10.
The Restart Database:Activity Information page
is displayed. Click Refresh to log in to Enterprise Manager Database
Control.
You can configure a number of settings and policies that determine
how backups are stored, which data is backed up, how backups perform, and how
long backups are
retained before being purged from the recovery area. You can also configure
features to improve backup performance.
1.
Click Maintenance on your Oracle Database Homepage.
2.
Select Configure Backup Settings in the Backup/Recovery
region.
3.
Scroll to the Host Credentials region on the Configure
Backup Settings page. Enter the operating system username and password.
Scroll up to the Disk Settings section.
4.
Accept the value of 1 in the Parallelism field
in the Disk Settings section on the Device page. The Disk Backup
Location field is set to null so that the flash recovery area will be
used for backups. Select Backup Set for Disk Backup Type. Click
Test Disk Backup.
5.
A message is displayed indicating the disk settings
backup test was successful. Now you will configure backup policy settings.
Click Policy to access the Policy page.
6.
Select Automatically backup the control file and
server parameter file (SPFILE) with every backup and database structural
change. Select Optimize the whole database backup by skipping unchanged
files such as read-only and offline datafiles that have been backed up.
Select Enable block change tracking for faster incremental backups.
Enter a file name for the Block Change Tracking file. Then scroll down
to the Retention Policy section.
7.
Select Retain backups that are necessary for a recovery
to any time within the specified number of days (point-in-time recovery)
and accept the default of 31 days. Click OK. You are returned to
the Maintenance page.
If you lose your database control file or SPFILE, Enterprise
Manager can restore them from backup, as long as you can provide the DB_UNIQUE_NAME
and DBID for your database.
Perform the steps below to determine the value of DB_UNIQUE_NAME:
1.
Click All Initialization Parameters in the Instance region
on the Administration page.
2.
The Current property page appears. Enter db_unique_name
in the Filter field and click Go.
3.
The resulting page displays a row with db_unique_name
in the Name column, and the db_unique_name
value for your database in the Value column.
Record this value so that you will have it should you need it in the
future for a recovery operation.
Perform the steps below to determine your DBID:
1.
Click Controlfiles in the Storage region
of the Administration page.
2.
The Controlfiles property page appears. Select
the Advanced property page.
3.
The Database ID field contains the DBID
value.
Record this value so that you will have it should you
need it in the future for a recovery operation.
You can backing up the entire contents of your database by
performing a whole database backup. Full backups of all datafiles are created.
The results may be stored as image copies or as backup sets, but in either case
the complete contents of all datafiles of the database are represented in the
backup, as well as the control file, archived redo log and server parameter
file. The database can be recovered completely with this set of files.
1.
Select Schedule Backup in the Backup/Recovery
region.
2.
The Schedule Backup: Strategy page appears. Select
Customized from the Backup Strategy drop-down menu. Select Whole
Database and enter the username and password in the Host Credentials
section if required. Click Next.
3.
The Schedule Backup: Options page appears. Select
Full Backup in the Backup Type section. Select Online Backup
in the Backup Mode section. Select Back up all archived logs on
disk in the Advanced section. Click Next.
4.
The Schedule Backup: Settings page appears. Select
Disk or Tape as appropriate. Click Next.
5.
The Schedule Backup: Schedule page appears. Accept
the default Job Name. Select Immediately to execute the job immediately
or enter a time to execute at a later time. Click Next.
6.
The Schedule Backup: Review page appears. Click
Submit Job.
7.
The Backup Submit Successful message is displayed.
Click OK.
Backing Up Your Database Using the Oracle-Suggested
Backup Strategy
The Oracle-suggested backup strategy is based on creating
an image copy of your database which is rolled forward using RMAN incremental
backups. Oracle Enterprise Manager schedules RMAN backups jobs. Follow the steps
below to set up your backup schedule:
1.
Select Schedule Backup in the Backup/Recovery
region.
2.
The Schedule Backup: Strategy page appears. Select
Oracle-suggested from the Backup Strategy drop-down menu. Select
Disk under Select your backup destination. Enter your operating
system username and password in the Host Credentials section. Click
Next .
3.
The Schedule Backup: Setup page appears. Review
the information and click Next.
4.
The Schedule Backup: Schedule page appears. Review
the information and adjust the start date and time as appropriate. Click
Next.
5.
The Schedule Backup: Review page appears. Review
the information and click Submit Job.
6.
The Status page appears with a message indicating
the job has been successfully submitted. You can click View Job
to access the job status page or click OK to complete the operation.
In this section you will recover a datafile through Enterprise
Manager.
1.
Select Perform Recovery in the Backup/Recovery
region.
2.
The Perform Recovery: Type page appears. Select
Whole Database from the Object Type drop-down menu in the Type
section. Select Recover to the current time or a previous point-in-time
as the Operation Type. Enter your operating system username and password
in the Host Credentials section. Click Next.
4.
The Recovery Wizard page is displayed indicating
that the instance will be shutdown and restarted. Click Refresh
to continue using the Recovery Wizard.
5.
Click Perform Recovery to recover your database.
6.
Enter your operating system username and password in
the Host Credentials region. Enter SYS
and the password for SYS
in the Database Credentials region. Click Continue.
7.
The Perform Recovery: Type page appears again.
The database is now in the mount state. Click Next.
8.
The Perform Recovery: Point-in-time page appears.
Select Recover to the current time. Click Next.
9.
The Perform Recovery: Rename page appears. Select
No. Restore the files to the default location if that is your choice
or select Yes. Restore the files to a new, common location and
enter the location. Click Next.
10.
The Perform Recovery: Review page appears. Review
the information and click Submit.
11.
You receive the "Operation succeeded" message.
Click OK.
You must enable row movement on a table in order to perform
a flashback table operation on the table. In this section you enable row movement
on the HR.EMPLOYEES table.
1.
Click Administration on your Oracle Database
Home page.
2.
The Administration property page appears. Select
Tables in the Schemasection.
3.
The Tables page appears. Select Table
from the Object Type drop-down menu. Enter HR in the Schema field
and REGIONS in the Object Name field. Click Go.
4.
The REGIONS
table is displayed in the Results section. Click Edit.
5.
The Edit Table page appears. Click the Options
tab.
6.
Select Yes from the Enable Row Movement
drop-down menu. Click Apply.
7.
You receive a message indicating your table has been
successfully modified. Select the Tables breadcrumb.
In this section you will use the flashback drop feature to
retrieve a table that has been dropped. For the purposes of this exercise, you
will create a new table, drop the table, and then recover it using flashback
drop.
Follow the steps below to create a new table and drop it:
1.
Enter HR
in the Schema Name field and REGIONS
or a part of the name in the Object Name field and click Go.
2.
Select Create Like from the Actions drop-down
menu. Click Go.
3.
The Create Table page appears. Enter REG_HIST
in the Name field. Deselect Not Null for the REGION_IDcolumn. Click Constraints.
4.
The Constraints page appears. Delete the constraints
on the table by selecting each and clicking delete. They are not
needed for this exercise.
5.
Click OK to create the REG_HIST
table.
6.
You receive a message indicating the table has been
created. Enter REG_HIST
in the Object Name field and click Go.
7.
The Tables page is displayed with the REG_HIST
table in the Results section. Click Delete to the delete the REG_HIST
table.
8.
Click Yes to confirm the deletion of the table.
9.
A message is displayed indicating the table has been
deleted. Click Go to attempt to retrieve the table.
10.
No object found is displayed in the results section.
To recover the table you just deleted, you will need to perform
a flashback drop. Perform the following:
1.
Click Recycle Bin.
2.
Enter HR
in the Schema Name field and click Go.
3.
Verify that
REG_HIST is selected and click Flashback Drop.
4.
The Perform Recovery Rename page appears. Click
Next.
5.
The Perform Recovery: Review page appears. Review
the information and click Submit.
6.
A confirmation message is displayed. Click OK.
7.
The table is no long in the recycle bin. Click the Tables
breadcrumb.
8.
The REG_HIST
table is now included in the tables list.
Managing backups consists of two tasks: managing the backups
themselves as they exist on disk or tape, and managing the record of backups
kept in the RMAN repository. In this section, you will perform backup maintenance
and update the RMAN repository. You perform the following tasks in this section:
You can use the Manage Current Backups
page to view the backups that are recorded in the RMAN repository. From this
page, you can perform the backup maintenance operations described throughout
this section.
1.
Click Manage Current Backups in the Backup/Recovery
region Maintenance property page.
2.
The Manage Current Backups page appears. The
Backup Sets property page displays the backup sets that are recorded
in the RMAN repository. Click the links in the Contents column to view
detailed information about the contents of a backup set.
3.
The Contents property page is displayed. Click
Manage Current Backups to return to the Manage Current Backups
property page.
4.
Click Image Copies to view the Image Copies
page.
5.
The Image Copies page appears displaying the
image copies that are recorded in the RMAN repository.
When you crosscheck a backup, RMAN verifies
that the information recorded in the repository is consistent with the physical
backup status. If it is not, the repository is updated to reflect the correct
status. You can crosscheck all of your backup files as follows:
1.
Click Manage Current Backups in the Backup/Recovery
region Maintenance property page.
2.
The Manage Current Backups page is displayed.
Click Crosscheck All at the top of the page to crosscheck all files
in the RMAN repository.
3.
The Crosscheck All: Specify Job Parameters page
is displayed. You can accept the defaults for the Job Name, Job Description,
Start time, and Repeat specifications or enter your own values. Click
Submit Job to submit the crosscheck job.
Bookmark
