19.10 Premigration Advisor Tool Log File Structure
The Premigration Advisor Tool produces a log file structure that includes job status and configuration files.
premigration Log File Base Path
The Premigration Advisor Tool log file path is set using the global
parameter premigration_log_dir
.
/cfgtoollogs/premigrate/auto
The automatic configuration tools log directory
(/cfgtoollogs/premigration/auto
) contains three trace log files
that provide specific information about each job that the premigration job manager
processes:
premigration.log
: Provides detailed logs of the job that identify any problems that occur during job runs.premigration_usr.log
: Job information, which is formatted to enhance readability.premigration_err.log
: A report of any unexpected exceptions that occur when the job runs.
If problems occur when jobs start or stop, then you can use information in these log files to determine the cause of problems.
/config_files
The config_files
directory contains Premigration Advisor Tool
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 premigration 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.
/####
( Job Number)
Individual job runs are placed in subdirectories identified by the run number, in
the format /####
, where
####
represents the job
run number. For example: 0004
. Job run number directories
contain the following log files:
premigration_err.log
: Reports any unexpected exceptions that occur while the job runs.premigrationYYYYMMDD.log
: premigration trace log file. Provides detailed logs of the job that identify any problems that occur during job runs. The variableYYYYMMDD
represents year, month, and day of the job.premigration_YYYYMMDD_user.log
: premigration job status file, which is formatted to enhance readability. The variableYYYYYYMMDD
represents year, month, and day of the job.
/premigration
The premigration directory (/premigration
) contains the following
files and log files:
prechecks_databasename.log
: Trace log file. This file provides detailed logs that can assist with identifying problems that occur during the preupgrade job stage. The variabledatabasename
is the name of the database checked.databasename_preupgrade.html
: HTML report on the database status. The variabledatabasename
is the name of the database checked.databasename_preupgrade.log
: Text report on the database status. The variabledatabasename
is the name of the database checked.
/premigration
The database premigration directory (/premigration
) contains all log
files associated with the database upgrade:
premigrationYYYYMMDDHHMISCdbname.log
: Log files for the source database, identified by the date on which the upgrade was run, and by the database name, indicating parallelism. Format:YYYY
: YearMM
: MonthDD
: DayHH
: HourMI
: MinuteSC
: Seconddbname
: Database name, wheredbname
is the database name.
-
premigrationYYYYMMDDHHMISCdbnameN.log
: log files for the source database, identified by the date on which the premigration checks were run.Format:
YYYY
: YearMM
: MonthDD
: DayHH
: HourMI
: MinuteSC
: SeconddbnameN
: Database name, wheredbname
is the database name, andN
indicates the parallelism: 0...3 for CDB ROOT, and Non-CDB databases, and 0...1 for PDBs.
/temp
Temporary premigration files (/temp
). This directory can contain
files such as the PFILE
used during an upgrade.
Parent topic: Cloud Premigration Advisor Tool