DB1

DB1

  • CheckName: PARAMETER_MIN_VAL
  • FixUp Available: YES
  • Severity: WARNING
  • Stage: PRECHECKS

Update NUMERIC INITIALIZATION PARAMETERS to meet estimated minimums. This action may be done now or when starting the database in upgrade mode using the 19 ORACLE HOME.

The database upgrade process requires certain initialization parameters to meet minimum values. The Oracle upgrade process itself has minimum values which may be higher and are marked with an asterisk. After upgrading, those asterisked parameter values may be reset if needed.

ParameterCurrentlyminimum
*sga_target8388608001002438656

  • CheckName: DICTIONARY_STATS
  • FixUp Available: YES
  • Severity: RECOMMEND
  • Stage: PRECHECKS

Gather stale data dictionary statistics prior to database upgrade in off-peak time using:

EXECUTE DBMS_STATS.GATHER_DICTIONARY_STATS;

Dictionary statistics help the Oracle optimizer find efficient SQL execution plans and are essential for proper upgrade timing. Oracle recommends gathering dictionary statistics in the last 24 hours before database upgrade.

For information on managing optimizer statistics, refer to the 12.2.0.1 Oracle Database SQL Tuning Guide.

Dictionary statistics do not exist or are stale (not up-to-date).

  • CheckName: PRE_FIXED_OBJECTS
  • FixUp Available: YES
  • Severity: RECOMMEND
  • Stage: PRECHECKS

Gather statistics on fixed objects prior the upgrade.

Gathering statistics on fixed objects, if none have been gathered yet, is recommended prior to upgrading.

For information on managing optimizer statistics, refer to the 12.2.0.1 Oracle Database SQL Tuning Guide.

None of the fixed object tables have had stats collected.

  • CheckName: MANDATORY_UPGRADE_CHANGES
  • FixUp Available: YES
  • Severity: INFO
  • Stage: PRECHECKS

Mandatory changes are applied automatically in the during_upgrade_pfile_dbname.ora file. Some of these changes maybe present in the after_upgrade_pfile_dbname.ora file. The during_upgrade_pfile_dbname.ora is used to start the database in upgrade mode. The after_upgrade_pfile_dbname.ora is used to start the database once the upgrade has completed successfully.

Mandatory changes are required to perform the upgrade. These changes are implemented in the during_ and after_upgrade_pfile_dbname.ora files.

Parameter
parallel_min_servers='0'
cluster_database='FALSE'
job_queue_processes='0'
parallel_max_servers='0'

  • CheckName: RMAN_RECOVERY_VERSION
  • FixUp Available: NO
  • Severity: INFO
  • Stage: PRECHECKS

Check the Oracle Backup and Recovery User's Guide for information on how to manage an RMAN recovery catalog schema.

It is good practice to have the catalog schema the same or higher version than the RMAN client version you are using.

If you are using a version of the recovery catalog schema that is older than that required by the RMAN client version, then you must upgrade the catalog schema.

  • CheckName: TABLESPACES_INFO
  • FixUp Available: NO
  • Severity: INFO
  • Stage: PRECHECKS

To help you keep track of your tablespace allocations, the following AUTOEXTEND tablespaces are expected to successfully EXTEND during the upgrade process.

Minimum tablespace sizes for upgrade are estimates.

Tablespace NameIn UseAllocatedAutoextend Size availableAvailableRequired size for UpgradeTo IncreaseMinimum Required for UpgradeAdd allocated for UpgradeFilename in TablespaceAutoextend onIs TempDBIs Locally Managedcontentstbs action
SYSTEM79580032735216327671150910110/u02/app/oracle/oradata/db1/system01.dbftruefalsetruePERMANENTNone
TEMP03233521648327671500150118/u02/app/oracle/oradata/db1/temp01.dbftruetruetrueTEMPORARYNone
UNDOTBS1657033482736327674020400330/u02/app/oracle/oradata/db1/undotbs01.dbftruefalsetrueUNDONone
SYSAUX443470330731363276747050030/u02/app/oracle/oradata/db1/sysaux01.dbftruefalsetruePERMANENTNone

  • CheckName: OLD_TIME_ZONES_EXIST
  • FixUp Available: YES
  • Severity: WARNING
  • Stage: POSTCHECKS

Upgrade the database time zone file using the DBMS_DST package.

Oracle recommends upgrading to the desired (latest) version of the time zone file. For more information, refer to "Upgrading the Time Zone File and Timestamp with Time Zone Data" in the 19 Oracle Database Globalization Support Guide.

The database is using time zone file version 26 and the target 19 release ships with time zone file version 32.

  • CheckName: POST_DICTIONARY
  • FixUp Available: YES
  • Severity: RECOMMEND
  • Stage: POSTCHECKS

Gather dictionary statistics after the upgrade using the command:

EXECUTE DBMS_STATS.GATHER_DICTIONARY_STATS;

Dictionary statistics provide essential information to the Oracle optimizer to help it find efficient SQL execution plans. After a database upgrade, statistics need to be re-gathered as there can now be tables that have significantly changed during the upgrade or new tables that do not have statistics gathered yet.

Oracle recommends gathering dictionary statistics after upgrade.

  • CheckName: POST_FIXED_OBJECTS
  • FixUp Available: YES
  • Severity: RECOMMEND
  • Stage: POSTCHECKS

Gather statistics on fixed objects after the upgrade and when there is a representative workload on the system using the command:

EXECUTE DBMS_STATS.GATHER_FIXED_OBJECTS_STATS;

Fixed object statistics provide essential information to the Oracle optimizer to help it find efficient SQL execution plans. Those statistics are specific to the Oracle Database release that generates them, and can be stale upon database upgrade.

For information on managing optimizer statistics, refer to the 12.2.0.1 Oracle Database SQL Tuning Guide.

This recommendation is given for all preupgrade runs.