Filter
Top Products
System Administrator’s Guide U42252-J-Z915-1-76
Installation and Configuration Configuration
4.3.2 Preparations
First make sure of the following:
If you have several database instances on one computer, the redolog
files of the various instances must have been created each in their
own separate directory.
As the next step you should draw up a backup schedule for your database. This
is a task for the database administrator. You will have to decide whether you
want the database being backed up as a whole or the backup being devided up
to several days of the week.
Please note that its is not possible to perform a recover until time if the
backup is divided up to several days.
However if you make a distributed backup, you must decide which
tablespaces should be saved on which day of the week. For example,
tablespaces in which extensive changes take place daily should be
backed up more frequently than tablespaces, which are almost always
accessed in read mode. In this way a faster recovery is possible in an
emergency. Tablespaces that are almost always accessed in read mode
can be backed up less frequently. A suitable backup schedule can allow
you to avoid full backups, which require lots of time and equipment, with-
out creating excessively long recovery times.
Establishing tablespace names
To provide an overview of the existing tablespaces and their sizes, a tool named
config.sh has been supplied as a basis for creating backup schedules. It provides
an overview of existing tablespaces, the associated database files and their
sizes. config.sh is located in the directory $NSR_INST/oracle/config.
Example:
The configuration tool is invoked with the command
sh> config.sh <ORACLE_SID>
The ORACLE_SID can be omitted if it has been set as a shell variable and
exported.
The following information is output, for example:
!
!