Using dbed_analyzer

Effectively performing a parallel backup requires an understanding of which tablespaces reside on which disks. If two tablespaces reside on the same disk, for example, backing them up in parallel will not reduce their downtime.

The dbed_analyzer command provides tablespace-to-physical disk mapping information for all the datafiles in a specified tablespace, list of tablespaces, or an entire database. (In contrast, the vxstorage_stats command provides this information on a per-file basis only.) In addition, dbed_analyzer provides information about the amount of disk space they are using.

Prerequisites

• You must log in as the database administrator (typically, the user ID oracle).

Usage Notes

• The -o sort=tbs option provides the layout of the specified tablespaces on the physical disk as well as the amount of disk space they are using.
• The -o sort=disk option provides the name of the disks containing the specified tablespaces as well as the amount of disk space the tablespaces are using.
• The -f filename option specifies the name of a file containing a list of the tablespaces for which to obtain mapping information.
• The -t tablespace option specifies the name of a tablespace for which to obtain mapping information.
• If -f filename or -t tablespace is not specified then all the tablespaces in the database will be analyzed.
• For more information, see the dbed_analyzer(1M) online manual page.

Obtaining Storage Mapping Information for a List of Tablespaces

  To obtain storage mapping information sorted by tablespace

Use the dbed_analyzer command with the -f filename and -o sort=tbs options:

Example

Output similar to the following is displayed in the file tbsfile:

  To obtain storage mapping information sorted by disk

Use the dbed_analyzer command with the -f filename and -o sort=disk options:

Example

Output similar to the following is displayed in the file tbsfile: