[root@hellodba ~]# cat /tmp/autoupgrade_log/hellodba/100/prechecks/hellodb_preupgrade.log
[dbname]          [HELLODB]
==========================================
[container]          [HELLODB]
==========================================
[checkname]          AMD_EXISTS
[stage]              PRECHECKS
[fixup_available]    YES
[runfix]             YES
[severity]           WARNING
[rule]               Starting with Oracle Database 12c, the OLAP Catalog (OLAP AMD) is desupported and will be automatically marked as OPTION OFF during the database upgrade if present. Oracle recommends removing OLAP Catalog (OLAP AMD) before database upgrade.  This step can be manually performed before the upgrade to reduce downtime.
[broken rule]        The OLAP Catalog component, AMD, exists in the database.
[action]             Remove OLAP Catalog by running the 11.2.0.4.0 SQL script $ORACLE_HOME/olap/admin/catnoamd.sql script.
----------------------------------------------------

[checkname]          AWR_DBIDS_PRESENT
[stage]              POSTCHECKS
[fixup_available]    YES
[runfix]             YES
[severity]           WARNING
[rule]               Inactve AWR DBIDs should be updated after the upgrade completes.
[broken rule]        Inactive DBIDs were found in your Automatic Workload Repository (AWR).
[action]             To update the inactive DBIDs in AWR, run the script awrupd12.sql as SYSDBA.
----------------------------------------------------

[checkname]          DICTIONARY_STATS
[stage]              PRECHECKS
[fixup_available]    YES
[runfix]             YES
[severity]           RECOMMEND
[rule]               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.<br><br>For information on managing optimizer statistics, refer to the 11.2.0.4 Oracle Database Performance Tuning Guide.
[broken rule]        Dictionary statistics do not exist or are stale (not up-to-date).
[action]             Gather stale data dictionary statistics prior to database upgrade in off-peak time using:<br><br>  EXECUTE DBMS_STATS.GATHER_DICTIONARY_STATS;
----------------------------------------------------

[checkname]          EM_PRESENT
[stage]              PRECHECKS
[fixup_available]    YES
[runfix]             YES
[severity]           WARNING
[rule]               Starting with Oracle Database 12c, the local Enterprise Manager Database Control does not exist anymore. The repository will be removed from your database during the upgrade.  This step can be manually performed before the upgrade to reduce downtime.
[broken rule]        The database has an Enterprise Manager Database Control repository.
[action]             Remove the EM repository.<br><br>- Copy the $ORACLE_HOME/rdbms/admin/emremove.sql script from the target 19 ORACLE_HOME into the source 11.2.0.4.0 ORACLE_HOME.<br><br>Step 1: If database control is configured, stop EM Database Control, using the following command<br><br>  $> emctl stop dbconsole<br><br>Step 2: Connect to the database using the SYS account AS SYSDBA<br><br>  SET ECHO ON;<br>  SET SERVEROUTPUT ON;<br>  @emremove.sql<br><br>Without the set echo and serveroutput commands, you will not be able to follow the progress of the script.
----------------------------------------------------

[checkname]          EXF_RUL_EXISTS
[stage]              PRECHECKS
[fixup_available]    YES
[runfix]             YES
[severity]           INFO
[rule]               Starting with Oracle Database release 12.1, the Expression Filter (EXF) and Database Rules Manager (RUL) features are desupported, and are removed during the upgrade process.  This step can be manually performed before the upgrade to reduce downtime.
[broken rule]        Expression Filter (EXF) or Rules Manager (RUL) exist in the database.
[action]             Run $ORACLE_HOME/rdbms/admin/catnoexf.sql located in the new Oracle Database Oracle home to remove both EXF and RUL.
----------------------------------------------------

[checkname]          TRGOWNER_NO_ADMNDBTRG
[stage]              PRECHECKS
[fixup_available]    YES
[runfix]             YES
[severity]           RECOMMEND
[rule]               The creation of database triggers must be done by users granted with ADMINISTER DATABASE TRIGGER privilege. Privilege must have been granted directly.
[broken rule]        There is one or more database triggers whose owner does not have the right privilege on the database.
[action]             Directly grant ADMINISTER DATABASE TRIGGER privilege to the owner of the trigger or drop and re-create the trigger with a user that was granted directly with such. You can list those triggers using: SELECT OWNER, TRIGGER_NAME FROM DBA_TRIGGERS WHERE TRIM(BASE_OBJECT_TYPE)='DATABASE' AND OWNER NOT IN (SELECT GRANTEE FROM DBA_SYS_PRIVS WHERE PRIVILEGE='ADMINISTER DATABASE TRIGGER').
----------------------------------------------------

[checkname]          POST_DICTIONARY
[stage]              POSTCHECKS
[fixup_available]    YES
[runfix]             YES
[severity]           RECOMMEND
[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.
[broken rule]        Oracle recommends gathering dictionary statistics after upgrade.
[action]             Gather dictionary statistics after the upgrade using the command:<br><br>  EXECUTE DBMS_STATS.GATHER_DICTIONARY_STATS;
----------------------------------------------------

[checkname]          POST_FIXED_OBJECTS
[stage]              POSTCHECKS
[fixup_available]    YES
[runfix]             YES
[severity]           RECOMMEND
[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.<br><br>For information on managing optimizer statistics, refer to the 11.2.0.4 Oracle Database Performance Tuning Guide.
[broken rule]        This recommendation is given for all preupgrade runs.
[action]             Gather statistics on fixed objects after the upgrade and when there is a representative workload on the system using the command:<br><br>  EXECUTE DBMS_STATS.GATHER_FIXED_OBJECTS_STATS;
----------------------------------------------------

[checkname]          PRE_FIXED_OBJECTS
[stage]              PRECHECKS
[fixup_available]    YES
[runfix]             YES
[severity]           RECOMMEND
[rule]               Gathering statistics on fixed objects, if none have been gathered yet, is recommended prior to upgrading.<br><br>For information on managing optimizer statistics, refer to the 11.2.0.4 Oracle Database Performance Tuning Guide.
[broken rule]        None of the fixed object tables have had stats collected.
[action]             Gather statistics on fixed objects prior the upgrade.
----------------------------------------------------

[checkname]          OLD_TIME_ZONES_EXIST
[stage]              POSTCHECKS
[fixup_available]    YES
[runfix]             YES
[severity]           WARNING
[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.
[broken rule]        The database is using time zone file version 14 and the target 19 release ships with time zone file version 32.
[action]             Upgrade the database time zone file using the DBMS_DST package.
----------------------------------------------------

[checkname]          MANDATORY_UPGRADE_CHANGES
[stage]              PRECHECKS
[fixup_available]    YES
[runfix]             YES
[severity]           INFO
[rule]               Mandatory changes are required to perform the upgrade.  These changes are implemented in the during_ and after_upgrade_pfile_dbname.ora files.
[broken rule]        [Parameter]
                     |parallel_min_servers='0'|
                     |cluster_database='FALSE'|
                     |job_queue_processes='0'|
                     |parallel_max_servers='0'|

[action]             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.
----------------------------------------------------

[checkname]          RMAN_RECOVERY_VERSION
[stage]              PRECHECKS
[fixup_available]    NO
[runfix]             N/A
[severity]           INFO
[rule]               It is good practice to have the catalog schema the same or higher version than the RMAN client version you are using.
[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.
[action]             Check the Oracle Backup and Recovery User's Guide for information on how to manage an RMAN recovery catalog schema.
----------------------------------------------------

[checkname]          TABLESPACES_INFO
[stage]              PRECHECKS
[fixup_available]    NO
[runfix]             N/A
[severity]           INFO
[rule]               Minimum tablespace sizes for upgrade are estimates.
[broken rule]        [Tablespace Name|In Use|Allocated|Autoextend Size available|Available|Required size for Upgrade|To Increase|Minimum Required for Upgrade|Add allocated for Upgrade|Filename in Tablespace|Autoextend on|Is TempDB|Is Locally Managed|contents|tbs action]
                     |SYSTEM|739|750|32786416|32767|447734|0|1177|427|/u01/app/oracle/oradata/hellodb/system01.dbf|true|false|true|PERMANENT|None|
                     |TEMP|0|29|33524720|32767|153600|0|150|121|/u01/app/oracle/oradata/hellodb/temp01.dbf|true|true|true|TEMPORARY|None|
                     |UNDOTBS1|13|75|33477616|32767|474518|0|401|326|/u01/app/oracle/oradata/hellodb/undotbs01.dbf|true|false|true|UNDO|None|
                     |SYSAUX|496|530|33011696|32767|264883|0|756|226|/u01/app/oracle/oradata/hellodb/sysaux01.dbf|true|false|true|PERMANENT|None|

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

[checkname]          DIR_SYMLINKS
[stage]              POSTCHECKS
[fixup_available]    NO
[runfix]             N/A
[severity]           WARNING
[rule]               Starting in Release 18c, symbolic links are not allowed in directory object path names used with BFILE data types, the UTL_FILE package, or external tables.
[broken rule]        Some directory object path names may currently contain symbolic links.
[action]             To identify directory objects with symbolic links in the path name, run $ORACLE_HOME/rdbms/admin/utldirsymlink.sql AS SYSDBA after upgrade. Recreate any directory objects listed, using path names that contain no symbolic links.
----------------------------------------------------

3.4、修复不满足的升级条件

SQL> @$ORACLE_HOME/olap/admin/catnoamd.sql

[oracle@hellodba ~]$ cp /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/emremove.sql /u01/app/oracle/product/11.2.0/dbhome_1/rdbms/admin
[oracle@hellodba ~]$ cd /u01/app/oracle/product/11.2.0/dbhome_1/rdbms/admin
[oracle@hellodba admin]$ sqlplus / as sysdba
SQL> @emremove.sql

SQL> EXECUTE DBMS_STATS.GATHER_DICTIONARY_STATS;

SQL> PURGE DBA_RECYCLEBIN;

[oracle@hellodba ~]$ java -jar /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/autoupgrade.jar -config /soft/sample_config.cfg -mode deploy
Autoupgrade tool launched with default options
+--------------------------------+
| Starting AutoUpgrade execution |
+--------------------------------+
1 databases will be processed
Enter some command, type 'help' or 'exit' to quit

upg> status
---------------- Config -------------------
User configuration file    [/soft/config.txt]
General logs location      [/tmp/autoupgrade_log/cfgtoollogs/upgrade/auto]
Mode                       [DEPLOY]
DB upg fatal errors        ORA-00600,ORA-07445
DB Post upgrade abort time [60] minutes
DB upg abort time          [1440] minutes
DB restore abort time      [120] minutes
DB drop GRP abort time     [3] minutes
------------------- Jobs -------------------
Total databases in configuration file [1]
Total Non-CDB being processed         [1]
Total CDB being processed             [0]
Jobs finished successfully            [0]
Jobs finished/aborted                 [0]
jobs in progress                      [1]
------------ Resources ----------------
Threads in use                        [27]
JVM used memory                       [60] MB
CPU in use                            [13%]
Processes in use                      [21]

upg> lsj    
+----+-------+---------+---------+-------+--------------+--------+--------+-------------+
|JOB#|DB NAME|    STAGE|OPERATION| STATUS|    START TIME|END TIME| UPDATED|      MESSAGE|
+----+-------+---------+---------+-------+--------------+--------+--------+-------------+
| 101|HELLODB|PREFIXUPS|EXECUTING|RUNNING|23/12/26 14:37|     N/A|14:37:38|Remaining 0/4|
+----+-------+---------+---------+-------+--------------+--------+--------+-------------+
    
upg> status -job 101
Progress
-----------------------------------
Start time:      23/12/26 14:37
Elapsed (min):   4
End time:        N/A
Last update:     2023-12-26T14:41:14.728
Stage:           DBUPGRADE
Operation:       EXECUTING
Status:          RUNNING
Pending stages:  4

Job Logs Locations
-----------------------------------
Logs Base:    /tmp/autoupgrade_log/hellodba
Job logs:     /tmp/autoupgrade_log/hellodba/101
Stage logs:   /tmp/autoupgrade_log/hellodba/101/dbupgrade
TimeZone:     /tmp/autoupgrade_log/hellodba/temp

Additional information
-----------------------------------
Details:
[Upgrading] is [19%] completed for [hellodb] 
                 +---------+-------------+
                 |CONTAINER|   PERCENTAGE|
                 +---------+-------------+
                 |  HELLODB|UPGRADE [19%]|
                 +---------+-------------+

Error Details:
None

[oracle@hellodba ~]$ cd /tmp/autoupgrade_log/cfgtoollogs/upgrade/auto
[oracle@hellodba auto]$ python -m SimpleHTTPServer 8000
// 浏览器访问
http://192.168.0.55:8000/state.html

[root@hellodba ~]# cat /tmp/autoupgrade_log/hellodba/101/dbupgrade_20231228_user.log
2023-12-28 10:30:04.539 INFO Analyzing HELLODB, 80 checks will run using 4 threads 
2023-12-28 10:30:10.907 INFO Guarantee Restore Point (GRP) successfully removed [HELLODB][AUTOUPGRADE_221145114461854_HELLODB] 
2023-12-28 10:30:11.009 INFO Guarantee Restore Point (GRP) successfully created [HELLODB][AUTOUPGRADE_221145114461854_HELLODB] 
2023-12-28 10:30:11.024 INFO Using /tmp/autoupgrade_log/hellodba/101/prechecks/hellodb_checklist.cfg as reference to determine the fixups which will be executed 
2023-12-28 10:30:38.643 INFO Analyzing HELLODB, 80 checks will run using 4 threads 
2023-12-28 10:31:04.322 INFO Total Number of upgrade phases is 108 
2023-12-28 10:31:04.325 INFO Begin Upgrade on Database [hellodb] 
2023-12-28 10:31:10.347 INFO [Upgrading] is [0%] completed for [hellodb] 
+---------+------------+
|CONTAINER|  PERCENTAGE|
+---------+------------+
|  HELLODB|UPGRADE [0%]|
+---------+------------+ 
2023-12-28 10:34:11.474 INFO [Upgrading] is [18%] completed for [hellodb] 
+---------+-------------+
|CONTAINER|   PERCENTAGE|
+---------+-------------+
|  HELLODB|UPGRADE [18%]|
+---------+-------------+ 
2023-12-28 10:37:12.557 INFO [Upgrading] is [37%] completed for [hellodb] 
+---------+-------------+
|CONTAINER|   PERCENTAGE|
+---------+-------------+
|  HELLODB|UPGRADE [37%]|
+---------+-------------+ 
2023-12-28 10:40:13.622 INFO [Upgrading] is [49%] completed for [hellodb] 
+---------+-------------+
|CONTAINER|   PERCENTAGE|
+---------+-------------+
|  HELLODB|UPGRADE [49%]|
+---------+-------------+ 
2023-12-28 10:43:14.672 INFO [Upgrading] is [61%] completed for [hellodb] 
+---------+-------------+
|CONTAINER|   PERCENTAGE|
+---------+-------------+
|  HELLODB|UPGRADE [61%]|
+---------+-------------+ 
2023-12-28 10:46:15.738 INFO [Upgrading] is [84%] completed for [hellodb] 
+---------+-------------+
|CONTAINER|   PERCENTAGE|
+---------+-------------+
|  HELLODB|UPGRADE [84%]|
+---------+-------------+ 
2023-12-28 10:49:22.802 INFO [Upgrading] is [95%] completed for [hellodb] 
+---------+-------------+
|CONTAINER|   PERCENTAGE|
+---------+-------------+
|  HELLODB|UPGRADE [95%]|
+---------+-------------+ 
2023-12-28 10:50:42.103 INFO SUCCESSFULLY UPGRADED [hellodb] 
2023-12-28 10:50:42.103 INFO End Upgrade on Database [hellodb] 
2023-12-28 10:50:53.156 INFO Begin Compiling Invalid Objects on Database [hellodb] 
2023-12-28 10:52:25.286 INFO [Compiling] is [0%] completed for [hellodb] objects remaining is [3058]
+---------+------------+
|CONTAINER|  PERCENTAGE|
+---------+------------+
|  HELLODB|COMPILE [0%]|
+---------+------------+ 
2023-12-28 10:55:13.312 INFO End Compiling Invalid Objects on Database [hellodb] 
2023-12-28 10:55:13.312 INFO SUCCESSFULLY COMPILED [hellodb] 
2023-12-28 10:55:15.365 INFO [Upgrading] is [100%] completed for [hellodb] 
+---------+-------------------------------+
|CONTAINER|                     PERCENTAGE|
+---------+-------------------------------+
|  HELLODB|SUCCESSFULLY UPGRADED [hellodb]|
+---------+-------------------------------+ 
2023-12-28 10:55:15.372 INFO Error opening file [/u01/app/oracle/product/19.0.0/dbhome_1/dbs/inithellodb.ora] for reading. 
2023-12-28 10:55:16.404 INFO Creating spfile completed with success 
2023-12-28 10:55:16.405 INFO SUCCESSFULLY UPGRADED [hellodb] 
2023-12-28 10:55:16.437 INFO hellodb Return status is SUCCESS 
2023-12-28 10:56:53.635 INFO Analyzing HELLODB, 6 checks will run using 4 threads 
2023-12-28 10:56:55.743 INFO Using /tmp/autoupgrade_log/hellodba/101/postchecks/hellodb_checklist.cfg as reference to determine the fixups which will be executed 
2023-12-28 11:01:19.781 INFO Analyzing HELLODB, 6 checks will run using 4 threads 

[oracle@hellodba auto]$ cat /tmp/autoupgrade_log/hellodba/101/dbupgrade/upg_summary.log

Oracle Database Release 19 Post-Upgrade Status Tool    12-28-2023 10:49:3
Database Name: HELLODB

Component                               Current         Full     Elapsed Time
Name                                    Status          Version  HH:MM:SS

Oracle Server                          UPGRADED      19.3.0.0.0  00:07:11
JServer JAVA Virtual Machine           UPGRADED      19.3.0.0.0  00:01:38
Oracle XDK                             UPGRADED      19.3.0.0.0  00:00:18
Oracle Database Java Packages          UPGRADED      19.3.0.0.0  00:00:06
OLAP Analytic Workspace                UPGRADED      19.3.0.0.0  00:00:05
Oracle Text                            UPGRADED      19.3.0.0.0  00:00:19
Oracle Workspace Manager               UPGRADED      19.3.0.0.0  00:00:25
Oracle Real Application Clusters     OPTION OFF      19.3.0.0.0  00:00:00
Oracle XML Database                    UPGRADED      19.3.0.0.0  00:01:32
Oracle Multimedia                      UPGRADED      19.3.0.0.0  00:00:30
Spatial                                UPGRADED      19.3.0.0.0  00:02:21
Oracle OLAP API                        UPGRADED      19.3.0.0.0  00:00:05
Datapatch                                                        00:01:36
Final Actions                                                    00:02:02
Post Upgrade                                                     00:00:12

Total Upgrade Time: 00:17:29

Database time zone version is 14. It is older than current release time
zone version 32. Time zone upgrade is needed using the DBMS_DST package.

Grand Total Upgrade Time:    [0d:0h:24m:26s]

SQL> select name from v$restore_point;
NAME
------------------------------------------
AUTOUPGRADE_221145114461854_HELLODB

SQL> drop restore point AUTOUPGRADE_221145114461854_HELLODB;

SQL> show parameter compatible;
NAME				     TYPE			       VALUE
----------------------------------------------------------------------------------
compatible			     string			       11.2.0.4.0
noncdb_compatible		     boolean			       FALSE

SQL> alter system set compatible = '19.0.0' scope=spfile;
SQL> shutdown immediate;
SQL> startup

SQL> show parameter compatible;
NAME				     TYPE			       VALUE
----------------------------------------------------------------------------------
compatible			     string			       19.0.0
noncdb_compatible		     boolean			       FALSE

SQL> SELECT USERNAME,ACCOUNT_STATUS FROM DBA_USERS WHERE USERNAME IN ('SYS','SYSTEM');
USERNAME							ACCOUNT_STATUS
---------------------------------------------------------------------------------------
SYSTEM								EXPIRED & LOCKED
SYS								LOCKED
SQL> UPDATE USER$ SET ASTATUS=0 WHERE NAME='SYS';
SQL> UPDATE USER$ SET ASTATUS=0 WHERE NAME='SYSTEM';
SQL> COMMIT;
SQL> alter system flush shared_pool;
SQL> SELECT USERNAME,ACCOUNT_STATUS FROM DBA_USERS WHERE USERNAME IN ('SYS','SYSTEM');
USERNAME							ACCOUNT_STATUS
---------------------------------------------------------------------------------------
SYSTEM								OPEN
SYS								OPEN
SQL> alter user system identified by Hello#123DBA;
SQL> alter user sys identified by Hello#123DBA;

[oracle@hellodba ~]$ cd $ORACLE_HOME/dbs
[oracle@hellodba dbs]$ mv orapwhellodb orapwhellodb_bak
[oracle@hellodba dbs]$ orapwd file=orapwhellodb entries=5
Enter password for SYS: Hello#123DBA

SQL> show parameter db_domain;
NAME				     TYPE			       VALUE
-----------------------------------------------------------------------------
db_domain			     string			       NULL

SQL> alter system reset db_domain scope=spfile;(重启生效)

[oracle@hellodba ~]$ rm -rf /u01/app/oracle/product/11.2.0/dbhome_1

[oracle@hellodba ~]$ sqlplus sys/Hello#123DBA@hellodb as sysdba

SQL*Plus: Release 19.0.0.0.0 - Production on Fri Dec 29 16:16:15 2023
Version 19.3.0.0.0

Copyright (c) 1982, 2019, Oracle.  All rights reserved.

Last Successful login time: Fri Dec 29 2023 16:16:08 +08:00

Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.3.0.0.0