How to Override Default Fixups

You can use the RUNFIX column entry to disable automated fixups, except in cases where disabling the fixup violates security or Oracle policy.

The default fixups that are part of the AutoUpgrade procedure are generated during the Analyze processing mode stage. You can modify the generated fixups list to disable automatic fixups, so that you can run your own fixups.

The sequence of steps is as follows:

Run the AutoUpgrade utility in Analyze mode
Open and edit the checklist.cfg file that is generated during Analyze mode, so that the fixups you want to do manually are disabled from running automatically.
In your AutoUpgrade configuration file, under your local parameters list for the job on which you want to suppress the automatic fixup, find the parameter sid.checklist, where sid is the system identifier (SID) of the database on which you want to suppress an automatic fixup. Edit the parameter to provide a path to the checklist.cfg file that you have edited.

Use the examples that follow to assist you with this procedure.

Note:

If the AutoUpgrade utility finds an error level database condition, and there is not a fixup available for it, or you have manually disabled the available fixup, then the AutoUpgrade job that contains the database with the error condition stops.

Example 3-6 Starting Up the AutoUpgrade Utility in Analyze Mode

java -jar autoupgrade.jar -config config.cfg –mode analyze

Example 3-7 Find and Edit checklist.cfg

The Analyze mode generates a fixup file with the file name checklist.cfg. Navigate to the file, where DATABASE_LOGS_DIR is the value set for the AutoUpgrade log_dir parameter of the database, job-id refers to the job identifier that the AutoUpgrade utility generates, and sid is the system identifier for the database on which you want to suppress automatic fixups:

DATABASE_LOGS_DIR/job-id/prechecks/sid_checklist.cfg

Open the checklist.cfg file with a text editor. The following is an example of the checklist.cfg file for the database with the SID DB11204:

[dbname]          [DB11204]
==========================================
[container]          [DB11204]
==========================================
[checkname]          AMD_EXISTS
[stage]              PRECHECKS
[fixup_available]    YES
[runfix]             YES
[severity]           WARNING
----------------------------------------------------

[checkname]          DEPEND_USR_TABLES
[stage]              POSTCHECKS
[fixup_available]    YES
[runfix]             YES
[severity]           WARNING
----------------------------------------------------

[checkname]          DICTIONARY_STATS
[stage]              PRECHECKS
[fixup_available]    YES
[runfix]             YES
[severity]           RECOMMEND
----------------------------------------------------

[checkname]          EM_PRESENT
[stage]              PRECHECKS
[fixup_available]    YES
[runfix]             YES
[severity]           WARNING
----------------------------------------------------
.
.
.

The file has a hierarchical structure. It starts with the database name, and the container name for which the entries of the checklist.cfg apply. The file contains a series of fixup checks that are applied automatically. For each entry, there are 5 relevant values parameters:

Parameter	Description
`[checkname]`	Name of the database check
`[stage]`	AutoUpgrade stage in which the check is performed. It can be either prechecks, or post checks.
`[fixup available]`	Availability of an automatic fixup. This parameter value is either `YES` (an automatic fixup is available), or `NO` (an automatic fixup is not available).
`runfix`	Run status for the fixup. This parameter takes one of two values: `YES`: Run the fixup. `NO`: Do not run the fixup.
`severity`	Class of severity of the issue that the automatic fixup addresses.

For each fixup that you want to perform manually, change the [runfix] parameter value from YES to NO.

Parent topic: Using AutoUpgrade for Oracle Database Upgrades