在AutoUpgrade 19c第1部分中，我們以分析模式執(zhí)行AutoUpgrade，對(duì)數(shù)據(jù)庫執(zhí)行只讀檢查，并返回一個(gè)報(bào)告，其中突出顯示了數(shù)據(jù)庫升級(jí)中可能出現(xiàn)的任何警告或潛在錯(cuò)誤，并提供了一些建議。

在修復(fù)模式下執(zhí)行自動(dòng)升級(jí)時(shí)，它會(huì)執(zhí)行在分析模式下也會(huì)執(zhí)行的檢查，完成這些檢查后，自動(dòng)升級(jí)會(huì)在升級(jí)開始前執(zhí)行修復(fù)早期版本源數(shù)據(jù)庫所需的所有自動(dòng)修復(fù)任務(wù)。

請(qǐng)注意，在修復(fù)模式下運(yùn)行時(shí)，自動(dòng)升級(jí)不會(huì)創(chuàng)建還原點(diǎn)（這僅在升級(jí)模式下完成）–因此建議在修復(fù)模式下運(yùn)行自動(dòng)升級(jí)之前進(jìn)行備份或創(chuàng)建手動(dòng)GRP。

在prechecks文件夾中，將存在SID_checklist.cfg文件，該文件將包含要執(zhí)行的預(yù)檢查以及針對(duì)該預(yù)檢查存在相應(yīng)修復(fù)程序的文件。

dbname]          [DB1]
==========================================
[container]          [DB1]
==========================================
[checkname]          DICTIONARY_STATS
[stage]              PRECHECKS
[fixup_available]    YES
[runfix]             YES
[severity]           RECOMMEND
----------------------------------------------------

[checkname]          POST_DICTIONARY
[stage]              POSTCHECKS
[fixup_available]    YES
[runfix]             YES
[severity]           RECOMMEND
----------------------------------------------------

[checkname]          POST_FIXED_OBJECTS
[stage]              POSTCHECKS
[fixup_available]    YES
[runfix]             YES
[severity]           RECOMMEND
----------------------------------------------------

[checkname]          PRE_FIXED_OBJECTS
[stage]              PRECHECKS
[fixup_available]    YES
[runfix]             YES
[severity]           RECOMMEND
----------------------------------------------------

[checkname]          OLD_TIME_ZONES_EXIST
[stage]              POSTCHECKS
[fixup_available]    YES
[runfix]             YES
[severity]           WARNING
----------------------------------------------------

[checkname]          PARAMETER_MIN_VAL
[stage]              PRECHECKS
[fixup_available]    YES
[runfix]             YES
[severity]           WARNING
----------------------------------------------------

[checkname]          MANDATORY_UPGRADE_CHANGES
[stage]              PRECHECKS
[fixup_available]    YES
[runfix]             YES
[severity]           INFO
----------------------------------------------------

[checkname]          RMAN_RECOVERY_VERSION
[stage]              PRECHECKS
[fixup_available]    NO
[runfix]             N/A
[severity]           INFO
----------------------------------------------------

[checkname]          TABLESPACES_INFO
[stage]              PRECHECKS
[fixup_available]    NO
[runfix]             N/A
[severity]           INFO
----------------------------------------------------

在固定模式下執(zhí)行自動(dòng)升級(jí)

[oracle@host02 bin]$ $ORACLE_HOME/jdk/bin/java -jar /home/oracle/autoupgrade.jar -config /tmp/config.txt -mode fixups
Autoupgrade tool launched with default options
+--------------------------------+
| Starting AutoUpgrade execution |
+--------------------------------+
2 databases will be processed
Type 'help' to list console commands
upg> lsj
+----+-------+---------+---------+--------+--------------+--------+--------+---------------+
|Job#|DB_NAME|    STAGE|OPERATION|  STATUS|    START_TIME|END_TIME| UPDATED|        MESSAGE|
+----+-------+---------+---------+--------+--------------+--------+--------+---------------+
| 106|    DB1|PRECHECKS|PREPARING| RUNNING|19/06/10 18:37|     N/A|18:37:07|Loading DB info|
| 107|    DB2|    SETUP|PREPARING|FINISHED|19/06/10 18:37|     N/A|18:37:06|      Scheduled|
+----+-------+---------+---------+--------+--------------+--------+--------+---------------+
Total jobs 2

upg> status 
---------------- Config -------------------
User configuration file    [/tmp/config.txt]
General logs location      [/u02/app/oracle/autoupgrade        # Top level logging directory (Required)/cfgtoollogs/upgrade/auto]
Mode                       [FIXUPS]
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 [2]
Total Non-CDB being processed         [2]
Total CDB being processed             [0]
Jobs finished successfully            [0]
Jobs finished/aborted                 [0]
jobs in progress                      [2]
------------ Resources ----------------
Threads in use                        [19]
JVM used memory                       [26] MB
CPU in use                            [13%]
Processes in use                      [19]

upg> tasks
+---+--------------+-------------+
| ID|          NAME|         Job#|
+---+--------------+-------------+
|  1|          main|      WAITING|
| 30|      jobs_mon|      WAITING|
| 31|       console|     RUNNABLE|
| 32|  queue_reader|      WAITING|
| 33|         cmd-0|      WAITING|
| 44| job_manager-0|      WAITING|
| 47|    event_loop|TIMED_WAITING|
| 48|    bqueue-106|      WAITING|
| 49|    checks-106|      WAITING|
| 50|rep_checks-106|TIMED_WAITING|
|104|    db1-puic-0|      WAITING|
|105|    db1-puic-1|      WAITING|
|169|      quickSQL|     RUNNABLE|
|171|      quickSQL|     RUNNABLE|

+---+--------------+-------------+
upg> lsj
+----+-------+---------+---------+--------+--------------+--------+--------+---------+
|Job#|DB_NAME|    STAGE|OPERATION|  STATUS|    START_TIME|END_TIME| UPDATED|  MESSAGE|
+----+-------+---------+---------+--------+--------------+--------+--------+---------+
| 106|    DB1|PREFIXUPS|EXECUTING| RUNNING|19/06/10 18:37|     N/A|18:37:34|         |
| 107|    DB2|    SETUP|PREPARING|FINISHED|19/06/10 18:37|     N/A|18:37:06|Scheduled|
+----+-------+---------+---------+--------+--------------+--------+--------+---------+
Total jobs 2

upg> lsj
+----+-------+---------+---------+--------+--------------+--------+--------+-------------+
|Job#|DB_NAME|    STAGE|OPERATION|  STATUS|    START_TIME|END_TIME| UPDATED|      MESSAGE|
+----+-------+---------+---------+--------+--------------+--------+--------+-------------+
| 106|    DB1|PREFIXUPS|EXECUTING| RUNNING|19/06/10 18:37|     N/A|18:37:42|Remaining 5/5|
| 107|    DB2|    SETUP|PREPARING|FINISHED|19/06/10 18:37|     N/A|18:37:06|    Scheduled|
+----+-------+---------+---------+--------+--------------+--------+--------+-------------+
Total jobs 2

upg> lsj
+----+-------+---------+---------+--------+--------------+--------+--------+-------------+
|Job#|DB_NAME|    STAGE|OPERATION|  STATUS|    START_TIME|END_TIME| UPDATED|      MESSAGE|
+----+-------+---------+---------+--------+--------------+--------+--------+-------------+
| 106|    DB1|PREFIXUPS|EXECUTING| RUNNING|19/06/10 18:37|     N/A|18:37:42|Remaining 5/5|
| 107|    DB2|    SETUP|PREPARING|FINISHED|19/06/10 18:37|     N/A|18:37:06|    Scheduled|
+----+-------+---------+---------+--------+--------------+--------+--------+-------------+
Total jobs 2

upg> Job 106 completed
Job 107 completed
------------------- Final Summary --------------------
Number of databases            [ 2 ]

Jobs finished successfully     [2]
Jobs failed                    [0]
Jobs pending                   [0]
------------- JOBS FINISHED SUCCESSFULLY -------------
Job 106 FOR DB1
Job 107 FOR DB2

[oracle@host02 bin]$ 

如果我們查詢最后一個(gè)u分析的列，我們可以看到數(shù)據(jù)字典統(tǒng)計(jì)是最新的，并且是由執(zhí)行的自動(dòng)升級(jí)修復(fù)作業(yè)收集的。

SQL> select max(last_analyzed) from dba_tables where owner='SYS'
  2  and table_name='ACCESS$';

MAX(LAST_
---------
10-JUN-19


SQL> prompt 'Statistics for Fixed Objects'
select NVL(TO_CHAR(last_analyzed, 'YYYY-Mon-DD'), 'NO STATS') last_analyzed, COUNT(*) fixed_objects
FROM dba_tab_statistics
WHERE object_type = 'FIXED TABLE'
GROUP BY TO_CHAR(last_analyzed, 'YYYY-Mon-DD')
ORDER BY 1 DESC;

SQL> 'Statistics for Fixed Objects'
 
LAST_ANALYZED FIXED_OBJECTS
------------- -------------
NO STATS 152
2019-Jun-10       1137