Principios para ordenar las referencias bibliográficas

You can use the report command to produce one of the following types of reports:

■ report unrecoverable report_object_list device_type_list

■ report need backup need_backup_operand report_object_list device_type_list ■ report obsoletereport_obsolete_operand_list device_type_list

■ report schemaat_clause

Where:

report_object_list

Specifies the datafiles to be reported on. The report can include the entire database (optionally skipping certain tablespaces), a list of tablespaces, or a list of datafiles.

device_type_list

Can be used to limit the backup sets that will be considered when deciding whether or not a file is unrecoverable or is in need of a more recent backup. If specified, only backup sets residing on one of the

Generating Reports

specified device types will be considered. If not specified, all available backup sets will be considered. Datafile copies will always be consid- ered.

Reporting Unrecoverable Datafiles

You can use the report unrecoverable command to list all datafiles that are unrecoverable. A datafile is considered unrecoverable if an UNRECOVERABLE operation has been performed against an object residing in the datafile since the last backup of the datafile.

Note that the non-existence of any backup of a datafile is not sufficient reason to consider it unrecoverable. Such datafiles can be recovered through the use of the

create datafile command, provided that logs starting from when the file was created are still in existence.

Example: Datafiles Requiring a New Backup The following command lists all datafiles that cannot be completely recovered from the existing backups because redo may be missing:

report unrecoverable;

Reporting Datafiles that Need to be Backed Up

The report need backup command lists all datafiles that need a new backup. The report assumes that the most recent backup would be used in the event of a restore. Following are descriptions of need_backup operands:

incremental

An integer specifying a threshold number of incremental backups. If complete recovery of a datafile would require the application of more than this many incremental backups, then the datafile is considered in need of a new full backup. This assumes the most efficient strategy, which is to use the lowest level of incremental backup whenever there is a choice. This is the same strategy that would be used if the file were actually being recovered by the recover command. Note that files for which no backups exist will not appear in this list. They can be found by using the report need backup days command.

days

An integer specifying a threshold number of days of log files that will need application during recovery of this file. For online files, this is the number of days since the last full or incremental backup of a file. The time of day is not considered when calculating the age of a backup set (i.e. a backup taken anytime yesterday is 1 day old). If multiple copies of a backup set exist, the completion time of the original backup set is used. If the most recent backup of this file is older than this number of days, then the file is in need of a new backup.

If the target database controlfile is mounted and current, the following optimizations will be made to this report:

1. Files that are offline and whose most recent backup contains all changes to the file will not be included.

2. Files that were offline and are now online, and whose most recent backup contains all changes up to the offline time, will only be reported if they have been online for more than the specified number of days.

redundancy

An integer specifying the minimum level of redundancy considered necessary. redundancy 2 means that there must be at least 2 backups of each datafile for it for it to be considered not in need of a backup. Example: Datafiles That Need to be Backed Up The following command reports all datafiles in the database that would require the application of three or more incremental backups to be recovered to their current state:

report need backup incremental 3 database;

The following command reports all datafiles from tablespace “system” that haven’t had a backup (full or incremental) in 5 or more days:

report need backup days 5 tablespace system;

Reporting Obsolete Datafile Backups

You can use the report obsolete command to list backup sets and datafile copies that can be deleted because they are redundant.

Generating Reports

A backup is obsolete if it meets one of the following criteria:

■ It is a backup of a file which no longer exists, or did not exist at the specified until-time

■ n more recent backups of the same file exist and are available, where n is the

desired redundancy

■ It is from an orphan incarnation, if the orphan option is specified

Following are descriptions of report_obsolete operands: redundancy

An integer specifying the minimum level of redundancy considered necessary. If more than this many full backups or copies exist for a given datafile, then the remainder of the backups are obsolete. This must be non-zero. The default value is one.

orphan

Specifies that backups and copies that can never be used (because they belong to incarnations of the database that are not predecessors of the current incarnation), will be considered obsolete.

until-clause

If an until-clause is specified, then no backup will be considered obso- lete or redundant if it contains any changes beyond the specified time. This is useful if the database must be recoverable to a point in time ear- lier than the present time.

Reporting Datafiles at the Current Time

The report schemacommandlists the names of all datafiles and tablespaces at the specified point in time, or at the current time. A point in time may be specified as a time, an SCN, or a redo log.

The at_clause has the following structure: at time

A quoted string specifying the time. at scn

at logseqinteger thread integer

Integers that specify the log sequence number and thread number to consider. This is the time when the specified log and thread were first opened.