Oracle 9ias Backup Strategy

Oracle 9iAS Backup Strategy Guide

10/06/03

Here are some key facts about the 9iAS 9.0.2.0.1 platform that need to be setup prior to going into development or production (e.g. it is not recommended to just install from the 9iAS 9.0.2.0.1 CDs, and then begin development/production).

A) You should use the 9.0.2 EM Website as much as possible to edit any files as required. If you have to make manual changes to any files with a text editor for any reason with 9iAS 9.0.2 you must use the “dcmctl updateConfig” option.

Please see the 9iAS 9.0.2 Administrators Guide for more details on dcmctl command line usage.

After making any manual change to a configuration file (using a text editor), it is necessary to run an appropriate “dcmctl updateConfig” command to propagate the change to the configuration repository.

As an example, in the case where changes have only been made to “opmn.xml”, these changes can be propagated by running:

>dcmctl updateConfig –ct opmn

If you made changes to files for oc4j

>dcmctl updateConfig –ct oc4j

Or, just

>dcmctl updateConfig

When making manual changes to a configuration file via a text editor…If the above procedure is not followed, this can cause problems with your 9iAS repository for your Mid-tier and Infrastructure.

B) 9iAS does not do automatic backup of anything at this time. Even when using the 9.0.2 EM Website.

Therefore, if you are going to do anything significant to an 9iAS Mid-tier or Infrastructure, play it safe, and before an dcmctl updateConfig, resynchInstance, or any changes that are significant, use:

>dcmctl saveInstance –dir <directory>