[dbname] [hongkong]
==========================================
[container] [hongkong]
==========================================
[checkname] POST_DICTIONARY
[stage] POSTCHECKS
[fixup_available] YES
[runfix] YES
[severity] RECOMMEND
[action] Gather dictionary statistics after the upgrade using the command: EXECUTE DBMS_STATS.GATHER_DICTIONARY_STATS;
[broken rule] Oracle recommends gathering dictionary statistics after upgrade.
[rule] 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.
----------------------------------------------------
[checkname] POST_FIXED_OBJECTS
[stage] POSTCHECKS
[fixup_available] NO
[runfix] N/A
[severity] RECOMMEND
[action] 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;
[broken rule] Oracle recommends gathering fixed object statistics after upgrade. This recommendation is given for all preupgrade runs.
[rule] 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.
----------------------------------------------------
[checkname] OLD_TIME_ZONES_EXIST
[stage] POSTCHECKS
[fixup_available] YES
[runfix] YES
[severity] WARNING
[action] Upgrade the database time zone file using the DBMS_DST package.
[broken rule] The database is using time zone file version 26 and the target 19 release ships with time zone file version 32.
[rule] 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.
----------------------------------------------------
[checkname] RMAN_RECOVERY_VERSION
[stage] PRECHECKS
[fixup_available] NO
[runfix] N/A
[severity] INFO
[action] Check the Oracle Backup and Recovery User's Guide for information on how to manage an RMAN recovery catalog schema.
[broken rule] 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.
[rule] It is good practice to have the catalog schema the same or higher version than the RMAN client version you are using.
----------------------------------------------------
[checkname] TABLESPACES_INFO
[stage] PRECHECKS
[fixup_available] NO
[runfix] N/A
[severity] INFO
[action] To help you keep track of your tablespace allocations, the following AUTOEXTEND tablespaces are expected to successfully EXTEND during the upgrade process.
[broken rule] [Tablespace Name|Allocated|Minimum Required for Upgrade]
|SYSTEM|820 MB|960 MB|
|TEMP|32 MB|150 MB|
|UNDOTBS1|65 MB|400 MB|
|SYSAUX|470 MB|598 MB|
[rule] Minimum tablespace sizes for upgrade are estimates.
----------------------------------------------------
[checkname] INFORM_DROP_GRP
[stage] POSTCHECKS
[fixup_available] NO
[runfix] N/A
[severity] INFO
[action] Drop GRP at your convenience once you consider it is no longer needed. drop restore point AUTOUPGRADE_9212_HONGKONG122010;
[broken rule] None
[rule] The AutoUpgrade tool will not automatically drop a GRP unless you specify in the config file the parameter drop_grp_after_upgrade=YES.
----------------------------------------------------
[checkname] ORDIM_INFO_DESUPPORT
[stage] PRECHECKS
[fixup_available] NO
[runfix] N/A
[severity] INFO
[action] Follow the instructions in the Oracle Multimedia README.txt file in <19 ORACLE_HOME>/ord/im/admin/README.txt, or MOS note 2555923.1 to determine if Oracle Multimedia is being used. If Oracle Multimedia is being used, refer to MOS note 2347372.1 for suggestions on replacing Oracle Multimedia.
[broken rule] Oracle Multimedia component (ORDIM) is installed.
[rule] Starting in release 19c, Oracle Multimedia is desupported. Object types still exist, but methods and procedures will raise an exception. Refer to 19 Oracle Database Upgrade Guide, the Oracle Multimedia README.txt file in <19 ORACLE_HOME>/ord/im/admin/README.txt, or MOS note 2555923.1 for more information.
----------------------------------------------------
[checkname] TIMESTAMP_MISMATCH
[stage] POSTCHECKS
[fixup_available] YES
[runfix] YES
[severity] WARNING
[action] Recompile the objects with timestamp mismatch. Please refer to MOS note 781959.1 for more details.
[broken rule] There are objects whose timestamp are mismatched with its parent objects.
[rule] Timestamp of dependent objects must coincide with the timestamp of parent objects.
----------------------------------------------------
Thank you for giving your valuable time to read the above information.
If you want to be updated with all our articles send us the Invitation or Follow us:
Ramkumar’s LinkedIn: https://www.linkedin.com/in/ramkumardba/
LinkedIn Group: https://www.linkedin.com/in/ramkumar-m-0061a0204/
Facebook Page: https://www.facebook.com/Oracleagent-344577549964301
Ramkumar’s Twitter : https://twitter.com/ramkuma02877110
Ramkumar’s Telegram: https://t.me/oracleageant
Ramkumar’s Facebook: https://www.facebook.com/ramkumarram8