On This Page:

Taking Database Dumps
BackUp and Archive Strategy
Tablespace

If an Oracle database is being used for the ServiceOptimizer instance then this page gives some tips on general housekeeping requirements.

Taking Database Dumps

When taking a database dump, use the following option on the command line:

COMPRESS=N

This avoids compressing objects which are split over multiple segments into a single segment, which, paradoxically, usually makes the disk file larger!

If taking a dump from a running system you must specify:

CONSISTENT=Y

BackUp and Archive Strategy

It is important that the ServiceScheduling database is backed up on a regular basis. The back up procedure should be carefully planned so as to ensure that business critical information is not lost in the event of a system failure. For a detailed description of the issues which need to be considered, refer to the Database Backup and Recovery section of the Oracle Server Administrator's Guide.

The recommended scheme to adopt is to perform a full database backup each day, and to run the database in ARCHIVELOG mode so that transaction logs are not overwritten.

Tablespace

By default, all of the tables and indexes are located within a single tablespace, which makes the task of backing up the tables relatively straightforward. Use of multiple tablespaces is not recommended.

Browser not supported