AutoUpgrade Log File Base Path

The AutoUpgrade log file path is set using the global parameter autoupg_log_dir. By default, the global parameter has the following definition:

global.autoupgr_log_dir=/database/jobmgr

/cfgtoollogs/upgrade/auto

The automatic configuration tools log directory (/cfgtoollogs/upgrade/auto) contains specific information about each job that the AutoUpgrade job manager processes. You can use information in these directories to determine problems when jobs start or stop.

The AutoUpgrade utility maintains an AutoUpgrade log file for all AutoUpgrade jobs:

autoupgrade.log

The autoupgrade.log file contains two log files that provide further details about AutoUpgrade job starts and stops, which can assist you with debugging:

• user_autoupgrade.log: Job information, which is formatted to enhance readability.

• autoupgrade_err.log: A report of any unexpected exceptions that occur when the job runs.

/config_files

The config_files directory contains AutoUpgrade internal runtime configurations and global temporary files.

/status

The /status directory contains JSON job status files. It contains two directories:

• status.json: This directory contains the final job status of all jobs completed in the JSON file format.

• progress.json: This directory contains the progress of all jobs currently running in the JSON file format.

Each module in the directories contains a status file for the operation that it performed. The module takes the following format, where the prefix dbname is the database name, operation is the upgrade operation that was performed, and the suffix status is the completion status of that operation:

dbname_operation-name.status

The success or the failure of that operation is indicated by the suffix, which is either .success, indicating the successful performance of that operation, or .failure, indicating the failure of that operation. For example, the following module name indicates a successful run of the prechecks operation on the database sales:

sales_prechecks.success

The operation module name can be one of the following:

• preupgrade: The preupgrade stage, in which custom scripts can be run.

• prechecks: The upgrade checks completed before starting the upgrade.

• grp: Guaranteed restore point (using Oracle Flashback technology)

• prefixups: The preupgrade fixups run before starting the upgrade

• drain: The stage where existing jobs are completed or migrated before starting the upgrade.

• dbupgrade: The stage in which the upgrade takes place.

• postchecks: The stage in which postupgrade checks are run after the upgrade is completed.

• postfixups: The stage in which postupgrade fixups are run.

• postupgrade: The stage in which custom postupgrade scripts can be run.

Individual Job and Database Log File Directories

Each job started by the AutoUpgrade dispatcher is given a directory with that job identifier prefix. Inside that job directory, each database in the job is given a log directory in the path /database/logs/sid, where sid is the system identifier for the database. For example, where the job identified in the configuration file is sales1, and the database system identifier is sales, the log file for the database sales is in the following path:

sales.log_dir=/database/logs/sales1

The log directory contain all the relevant log files for all the tasks performed for that database. By default, a directory identified by SID is created under the /database/logs directory. Each database job can have a separate log directory, if you choose to set up your configuration file that way.