Displaying the contents of the catalog is just as easy in OEM. Figure 12-6 shows results
equivalent to the list backup by backup command.
The list and report commands are covered in more detail later in this chapter.
Tablespace
After adding a tablespace to the database, performing an immediate backup of the tablespace will
shorten the time it will take to restore the tablespace later in the event of media failure. In addition,
you might back up an individual tablespace in a database that is too large to back up all at once;
again, creating a backupset or image copy of a tablespace at frequent intervals will reduce the
amount of redo that would need to be applied to an older backup of the tablespace in the event
FIGURE 12-5 Configure backup job with OEM
440 Oracle Database 11g DBA Handbook
of media failure. For example, in an environment with three large tablespaces??”USERS, USERS2,
and USERS3??”along with the default tablespaces SYSTEM and SYSAUX, you might back up the
SYSTEM and SYSAUX tablespaces on Sunday, USERS on Monday, USERS2 on Wednesday, and
USERS3 on Friday. Failures of any media containing datafiles from one of these tablespaces will
use a tablespace backup that is no more than a week old plus the intervening archived and online
redo log files for recovery.
In our next example, we??™re adding a tablespace to the dw database to support a new set of
star schemas:
SQL> create tablespace inet_star
2 datafile '+DATA' size 100m
3 autoextend on next 50m maxsize 500m;
Tablespace created.
Pages:
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682