No Oracle AI Database 26ai, o método oficialmente suportado para upgrade é o AutoUpgrade (ou Replay Upgrade), sendo que abordagens como upgrade manual via scripts não são mais recomendadas.
Neste artigo será demonstrado, passo a passo, o processo de upgrade de um ambiente:
- Oracle Database 19c;
- Arquitetura CDB/PDB (PDB já existente);
- Sistema operacional Oracle Linux 9.7;
- Upgrade para Oracle AI Database 26ai;
- Estratégia out-of-place;
Nesta estratégia (out-of-place) o oracle home de origem 19c permanece inalterado, reduzindo o risco operacional, possibilitando um rollback controlado.
É sempre importante antes de um processo de upgrade, garantir um backup do banco de dados, afim de garantir um ponto de restauração caso necessário.
1 - Download do AutoUdapgrade
É recomendável sempre baixar a versão mais recente do autoupgrade. Neste exemplo estarei criando a estrutura de diretórios e baixando a versão atualizada.
[oracle@oracle26ai u01]$ pwd /u01 [oracle@oracle26ai u01]$ mkdir autoupgrade [oracle@oracle26ai u01]$ cd autoupgrade/ [oracle@oracle26ai autoupgrade]$ mkdir logs [oracle@oracle26ai autoupgrade]$ mkdir keystore [oracle@oracle26ai autoupgrade]$ mkdir patches [oracle@oracle26ai autoupgrade]$ ls keystore logs patches [oracle@oracle26ai autoupgrade]$ pwd /u01/autoupgrade [oracle@oracle26ai autoupgrade]$ wget https://download.oracle.com/otn-pub/otn_software/autoupgrade.jar --2026-02-14 11:01:44-- https://download.oracle.com/otn-pub/otn_software/autoupgrade.jar Resolving download.oracle.com (download.oracle.com)... 2.20.224.113 Connecting to download.oracle.com (download.oracle.com)|2.20.224.113|:443... connected. HTTP request sent, awaiting response... 302 Moved Temporarily Location: https://edelivery.oracle.com/otn-pub/otn_software/autoupgrade.jar [following] --2026-02-14 11:01:44-- https://edelivery.oracle.com/otn-pub/otn_software/autoupgrade.jar Resolving edelivery.oracle.com (edelivery.oracle.com)... 23.61.118.226, 2600:1419:3e00:292::366, 2600:1419:3e00:28f::366 Connecting to edelivery.oracle.com (edelivery.oracle.com)|23.61.118.226|:443... connected. HTTP request sent, awaiting response... 302 Moved Temporarily Location: https://download.oracle.com/otn-pub/otn_software/autoupgrade.jar?AuthParam=1771253672_2cf593cf3c4975771895646568489d35 [following] --2026-02-14 11:01:44-- https://download.oracle.com/otn-pub/otn_software/autoupgrade.jar?AuthParam=1771253672_2cf593cf3c4975771895646568489d35 Connecting to download.oracle.com (download.oracle.com)|2.20.224.113|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 6960211 (6.6M) [application/x-jar] Saving to: ‘autoupgrade.jar’ autoupgrade.jar 100%[========================================================================================================================================>] 6.64M 25.0MB/s in 0.3s 2026-02-14 11:01:45 (25.0 MB/s) - ‘autoupgrade.jar’ saved [6960211/6960211] [oracle@oracle26ai autoupgrade]$ ls autoupgrade.jar keystore logs patches [oracle@oracle26ai autoupgrade]$
2 - Criação do Arquivo de Configuração
Para gerar o arquivo de configuração que será utilizado pelo autoupgrade, estarei usando o autoupgrade composer. O AutoUpgrade Composer, mantido por Marcus Vinicius (ViniciusDBA), é uma ferramenta web que simplifica a criação do arquivo de configuração do Oracle AutoUpgrade.
Ele reduz o risco operacional ao automatizar a geração do arquivo de configuração do AutoUpgrade, garantindo sintaxe correta e consistência entre parâmetros globais e específicos (source_home, target_home, log_dir, dbname). Em ambientes com múltiplos bancos ou estratégia out-of-place, essa padronização aumenta previsibilidade na fase ANALYZE e reduz falhas por erro manual.
Link oficial: https://viniciusdba.com.br/autoupgrade-composer/
Basta preencher os dados de origem e destino que o arquivo de configuração será gerado, conforme artigo do Marcus Vinicius.
No exemplo deste artigo o arquivo estou considerando que o produto 26ai já esteja instalado. Você pode usar o artigo NOME DO ARTIGO para instalar através do AutoUpgrade.
Arquivo dbupgrade.cfg gerado pelo AutoUpgrade Composer.
[root@oracle26ai autoupgrade]# cat upg_ora19c.cfg # Created by AutoUpgrade Composer # Upgrade, UpgType: regular global.global_log_dir=/u01/autoupgrade/logs upg1.sid=ora19c upg1.log_dir=/u01/autoupgrade/logs/ upg1.source_home=/u01/app/oracle/product/19.30/dbhome_1 upg1.target_home=/u01/app/oracle/product/23.26.1/dbhome_1 upg1.restoration=YES [root@oracle26ai autoupgrade]#
3 - Execução do Analyze
No processo de analyze o AutoUpgrade faz um “dry-run inteligente” que analisa o ambiente e aponta bloqueios/ações necessárias, sem alterar o banco de origem.
Comando: -mode analyze
[oracle@oracle26ai autoupgrade]$ java -jar autoupgrade.jar -config upg_ora19c.cfg -mode analyze AutoUpgrade 26.2.260205 launched with default internal options Processing config file ... +--------------------------------+ | Starting AutoUpgrade execution | +--------------------------------+ 1 CDB(s) plus 2 PDB(s) will be analyzed Type 'help' to list console commands upg> lsj -a 30 upg> +----+-------+---------+---------+-------+----------+-------+----------------------------+ |Job#|DB_NAME| STAGE|OPERATION| STATUS|START_TIME|UPDATED| MESSAGE| +----+-------+---------+---------+-------+----------+-------+----------------------------+ | 101| ora19c|PRECHECKS|EXECUTING|RUNNING| 15:46:20| 3s ago|Loading database information| +----+-------+---------+---------+-------+----------+-------+----------------------------+ Total jobs 1 The command lsj is running every 30 seconds. PRESS ENTER TO EXIT +----+-------+---------+---------+-------+----------+-------+----------------+ |Job#|DB_NAME| STAGE|OPERATION| STATUS|START_TIME|UPDATED| MESSAGE| +----+-------+---------+---------+-------+----------+-------+----------------+ | 101| ora19c|PRECHECKS|EXECUTING|RUNNING| 15:46:20| 0s ago|Executing Checks| +----+-------+---------+---------+-------+----------+-------+----------------+ Total jobs 1 The command lsj is running every 30 seconds. PRESS ENTER TO EXIT Job 101 completed ------------------- Final Summary -------------------- Number of databases [ 1 ] Jobs finished [1] Jobs failed [0] Please check the summary report at: /u01/autoupgrade/logs/cfgtoollogs/upgrade/auto/status/status.html /u01/autoupgrade/logs/cfgtoollogs/upgrade/auto/status/status.log
Finalizado o processo de analyze com sucesso. Podemos validar também o status nos logs gerados pelo processo.
[oracle@oracle26ai autoupgrade]$ cat /u01/autoupgrade/logs/cfgtoollogs/upgrade/auto/status/status.log ========================================== Autoupgrade Summary Report ========================================== [Date] Tue Feb 17 15:47:11 BRT 2026 [Number of Jobs] 1 ========================================== [Job ID] 101 ========================================== [DB Name] ora19c [Version Before Upgrade] 19.30.0.0.0 [Version After Upgrade] 23.26.1.0.0 ------------------------------------------ [Stage Name] PRECHECKS [Status] SUCCESS [Start Time] 2026-02-17 15:46:20 [Duration] 0:00:50 [Log Directory] /u01/autoupgrade/logs/ora19c/101/prechecks [Detail] /u01/autoupgrade/logs/ora19c/101/prechecks/ora19c_preupgrade.log Check passed and no manual intervention needed ------------------------------------------ [oracle@oracle26ai autoupgrade]$
4 - FIXUPS
A fase FIXUPS do Oracle AutoUpgrade executa correções identificadas na fase ANALYZE que podem ser aplicadas automaticamente antes do upgrade efetivo.
Tecnicamente, o AutoUpgrade:
- Ajusta parâmetros obsoletos ou depreciados
- Remove configurações incompatíveis com a versão alvo (26ai)
- Corrige inconsistências estruturais detectadas
- Ajusta componentes inválidos quando possível
- Executa ações preparatórias necessárias para evitar falhas no DEPLOY
- Aplica correções relacionadas a timezone, dictionary checks ou pré-requisitos internos
AutoUpgrade classifica cada item como:
- FIXUP automático (pode ser aplicado)
- FIXUP manual (exige intervenção do DBA)
- WARNING (não bloqueia, mas deve ser analisado)
A etapa de fixups não precisa ser executada separadamente uma vez que o processo de deploy executará a mesma.
Em ambientes produtivos é recomendado que a fase de prefixups seja executada antes do deploy porque:
- Reduz risco de falha no meio da janela de mudança
- Permite tratar pendências manuais com antecedência
- Dá maior previsibilidade ao processo
- Evita surpresas durante o upgrade real
A sequencia recomendada é sempre:
ANALYZE → FIXUPS → DEPLOY
[oracle@oracle26ai autoupgrade]$ java -jar autoupgrade.jar -config upg_ora19c.cfg -mode fixups AutoUpgrade 26.2.260205 launched with default internal options Processing config file ... +--------------------------------+ | Starting AutoUpgrade execution | +--------------------------------+ 1 CDB(s) plus 2 PDB(s) will be processed Type 'help' to list console commands upg> lsj -a 30 upg> +----+-------+---------+---------+-------+----------+-------+----------------+ |Job#|DB_NAME| STAGE|OPERATION| STATUS|START_TIME|UPDATED| MESSAGE| +----+-------+---------+---------+-------+----------+-------+----------------+ | 105| ora19c|PRECHECKS|EXECUTING|RUNNING| 11:17:09| 0s ago|Executing Checks| +----+-------+---------+---------+-------+----------+-------+----------------+ Total jobs 1 The command lsj is running every 30 seconds. PRESS ENTER TO EXIT +----+-------+---------+---------+-------+----------+-------+-------------------+ |Job#|DB_NAME| STAGE|OPERATION| STATUS|START_TIME|UPDATED| MESSAGE| +----+-------+---------+---------+-------+----------+-------+-------------------+ | 105| ora19c|PREFIXUPS|EXECUTING|RUNNING| 11:17:09| 0s ago|Re-Executing Checks| +----+-------+---------+---------+-------+----------+-------+-------------------+ Total jobs 1 The command lsj is running every 30 seconds. PRESS ENTER TO EXIT Job 105 completed ------------------- Final Summary -------------------- Number of databases [ 1 ] Jobs finished [1] Jobs failed [0] Please check the summary report at: /u01/autoupgrade/logs/cfgtoollogs/upgrade/auto/status/status.html /u01/autoupgrade/logs/cfgtoollogs/upgrade/auto/status/status.log
Podemos validar o log gerado status.log.
[oracle@oracle26ai autoupgrade]$ cat /u01/autoupgrade/logs/cfgtoollogs/upgrade/auto/status/status.log ========================================== Autoupgrade Summary Report ========================================== [Date] Wed Feb 18 11:18:16 BRT 2026 [Number of Jobs] 1 ========================================== [Job ID] 105 ========================================== [DB Name] ora19c [Version Before Upgrade] 19.30.0.0.0 [Version After Upgrade] 23.26.1.0.0 ------------------------------------------ [Stage Name] PRECHECKS [Status] SUCCESS [Start Time] 2026-02-18 11:17:10 [Duration] 0:00:33 [Log Directory] /u01/autoupgrade/logs/ora19c/105/prechecks [Detail] /u01/autoupgrade/logs/ora19c/105/prechecks/ora19c_preupgrade.log Check passed and no manual intervention needed ------------------------------------------ [Stage Name] PREFIXUPS [Status] SUCCESS [Start Time] 2026-02-18 11:17:43 [Duration] 0:00:32 [Log Directory] /u01/autoupgrade/logs/ora19c/105/prefixups [Detail] /u01/autoupgrade/logs/ora19c/105/prefixups/prefixups.html ------------------------------------------ [oracle@oracle26ai autoupgrade]$
5 - DEPLOY
O deploy é a fase em que o Oracle AutoUpgrade executa efetivamente o upgrade do banco para o Oracle AI Database 26ai. Este processo possui um total de 11 etapas (Setup, Guarantee Restore Point (GRP), Preupgrade, Prechecks, Prefixups, Drain, DB upgrade, Post checks, Postfixups, Postupgrade, and Sysupdates).
Para execução do deploy utilizar a opção -deploy.
[oracle@oracle26ai autoupgrade]$ java -jar autoupgrade.jar -config upg_ora19c.cfg -mode deploy AutoUpgrade 26.2.260205 launched with default internal options Processing config file ... +--------------------------------+ | Starting AutoUpgrade execution | +--------------------------------+ 1 CDB(s) plus 2 PDB(s) will be processed Type 'help' to list console commands upg> lsj -a 60 upg> +----+-------+-----+---------+-------+----------+-------+------------------------+ |Job#|DB_NAME|STAGE|OPERATION| STATUS|START_TIME|UPDATED| MESSAGE| +----+-------+-----+---------+-------+----------+-------+------------------------+ | 109| ora19c|DRAIN|EXECUTING|RUNNING| 15:19:15|20s ago|Disabling RAC if present| +----+-------+-----+---------+-------+----------+-------+------------------------+ Total jobs 1 The command lsj is running every 60 seconds. PRESS ENTER TO EXIT +----+-------+---------+---------+-------+----------+-------+-------+ |Job#|DB_NAME| STAGE|OPERATION| STATUS|START_TIME|UPDATED|MESSAGE| +----+-------+---------+---------+-------+----------+-------+-------+ | 109| ora19c|DBUPGRADE|EXECUTING|RUNNING| 15:19:15| 0s ago|Running| +----+-------+---------+---------+-------+----------+-------+-------+ Total jobs 1 The command lsj is running every 60 seconds. PRESS ENTER TO EXIT +----+-------+---------+---------+-------+----------+-------+-------------------+ |Job#|DB_NAME| STAGE|OPERATION| STATUS|START_TIME|UPDATED| MESSAGE| +----+-------+---------+---------+-------+----------+-------+-------------------+ | 109| ora19c|DBUPGRADE|EXECUTING|RUNNING| 15:19:15|32s ago|0%Upgraded CDB$ROOT| +----+-------+---------+---------+-------+----------+-------+-------------------+ Total jobs 1 The command lsj is running every 60 seconds. PRESS ENTER TO EXIT +----+-------+---------+---------+-------+----------+-------+--------------------+ |Job#|DB_NAME| STAGE|OPERATION| STATUS|START_TIME|UPDATED| MESSAGE| +----+-------+---------+---------+-------+----------+-------+--------------------+ | 109| ora19c|DBUPGRADE|EXECUTING|RUNNING| 15:19:15| 0s ago|96%Upgraded CDB$ROOT| +----+-------+---------+---------+-------+----------+-------+--------------------+ Total jobs 1 The command lsj is running every 60 seconds. PRESS ENTER TO EXIT +----+-------+---------+---------+-------+----------+-------+-------------------+ |Job#|DB_NAME| STAGE|OPERATION| STATUS|START_TIME|UPDATED| MESSAGE| +----+-------+---------+---------+-------+----------+-------+-------------------+ | 109| ora19c|DBUPGRADE|EXECUTING|RUNNING| 15:19:15|45s ago|0%Upgraded PDB$SEED| +----+-------+---------+---------+-------+----------+-------+-------------------+ Total jobs 1 The command lsj is running every 60 seconds. PRESS ENTER TO EXIT +----+-------+---------+---------+-------+----------+-------+---------------+ |Job#|DB_NAME| STAGE|OPERATION| STATUS|START_TIME|UPDATED| MESSAGE| +----+-------+---------+---------+-------+----------+-------+---------------+ | 109| ora19c|DBUPGRADE|EXECUTING|RUNNING| 15:19:15|44s ago|1%Upgraded PDB1| +----+-------+---------+---------+-------+----------+-------+---------------+ Total jobs 1 The command lsj is running every 60 seconds. PRESS ENTER TO EXIT +----+-------+---------+---------+-------+----------+-------+----------------+ |Job#|DB_NAME| STAGE|OPERATION| STATUS|START_TIME|UPDATED| MESSAGE| +----+-------+---------+---------+-------+----------+-------+----------------+ | 109| ora19c|DBUPGRADE|EXECUTING|RUNNING| 15:19:15|58s ago|76%Upgraded PDB1| +----+-------+---------+---------+-------+----------+-------+----------------+ Total jobs 1 The command lsj is running every 60 seconds. PRESS ENTER TO EXIT +----+-------+---------+---------+-------+----------+-------+--------------------+ |Job#|DB_NAME| STAGE|OPERATION| STATUS|START_TIME|UPDATED| MESSAGE| +----+-------+---------+---------+-------+----------+-------+--------------------+ | 109| ora19c|DBUPGRADE|EXECUTING|RUNNING| 15:19:15|13s ago|81%Upgraded PDB$SEED| +----+-------+---------+---------+-------+----------+-------+--------------------+ Total jobs 1 The command lsj is running every 60 seconds. PRESS ENTER TO EXIT +----+-------+---------+---------+-------+----------+-------+----------------+ |Job#|DB_NAME| STAGE|OPERATION| STATUS|START_TIME|UPDATED| MESSAGE| +----+-------+---------+---------+-------+----------+-------+----------------+ | 109| ora19c|DBUPGRADE|EXECUTING|RUNNING| 15:19:15|58s ago|81%Upgraded PDB1| +----+-------+---------+---------+-------+----------+-------+----------------+ Total jobs 1 The command lsj is running every 60 seconds. PRESS ENTER TO EXIT +----+-------+---------+---------+-------+----------+-------+--------------------+ |Job#|DB_NAME| STAGE|OPERATION| STATUS|START_TIME|UPDATED| MESSAGE| +----+-------+---------+---------+-------+----------+-------+--------------------+ | 109| ora19c|DBUPGRADE|EXECUTING|RUNNING| 15:19:15|12s ago|85%Upgraded PDB$SEED| +----+-------+---------+---------+-------+----------+-------+--------------------+ Total jobs 1 The command lsj is running every 60 seconds. PRESS ENTER TO EXIT +----+-------+----------+---------+-------+----------+-------+----------------+ |Job#|DB_NAME| STAGE|OPERATION| STATUS|START_TIME|UPDATED| MESSAGE| +----+-------+----------+---------+-------+----------+-------+----------------+ | 109| ora19c|POSTFIXUPS|EXECUTING|RUNNING| 15:19:15|12s ago|Executing fixups| +----+-------+----------+---------+-------+----------+-------+----------------+ Total jobs 1 The command lsj is running every 60 seconds. PRESS ENTER TO EXIT +----+-------+----------+---------+-------+----------+-------+----------------+ |Job#|DB_NAME| STAGE|OPERATION| STATUS|START_TIME|UPDATED| MESSAGE| +----+-------+----------+---------+-------+----------+-------+----------------+ | 109| ora19c|POSTFIXUPS|EXECUTING|RUNNING| 15:19:15|42s ago|Executing fixups| +----+-------+----------+---------+-------+----------+-------+----------------+ Total jobs 1 The command lsj is running every 60 seconds. PRESS ENTER TO EXIT +----+-------+----------+---------+-------+----------+-------+----------------------------------------+ |Job#|DB_NAME| STAGE|OPERATION| STATUS|START_TIME|UPDATED| MESSAGE| +----+-------+----------+---------+-------+----------+-------+----------------------------------------+ | 109| ora19c|SYSUPDATES|EXECUTING|RUNNING| 15:19:15|34s ago|RAC configurations have finished success| +----+-------+----------+---------+-------+----------+-------+----------------------------------------+ Total jobs 1 +----+-------+----------+---------+-------+----------+-------+----------------------------------------+ |Job#|DB_NAME| STAGE|OPERATION| STATUS|START_TIME|UPDATED| MESSAGE| +----+-------+----------+---------+-------+----------+-------+----------------------------------------+ | 109| ora19c|SYSUPDATES|EXECUTING|RUNNING| 15:19:15|65s ago|RAC configurations have finished success| +----+-------+----------+---------+-------+----------+-------+----------------------------------------+ Total jobs 1 The command lsj is running every 60 seconds. PRESS ENTER TO EXIT Job 109 completed ------------------- Final Summary -------------------- Number of databases [ 1 ] Jobs finished [1] Jobs failed [0] Jobs restored [0] Jobs pending [0] Please check the summary report at: /u01/autoupgrade/logs/cfgtoollogs/upgrade/auto/status/status.html /u01/autoupgrade/logs/cfgtoollogs/upgrade/auto/status/status.log [oracle@oracle26ai autoupgrade]$
Podemos consultar o Summary Report do job de upgrade executado pelo Oracle AutoUpgrade no modo deploy. Ele consolida todas as fases executadas no ciclo completo do upgrade do banco ora19c, incluindo tempos, diretórios de log e status final de cada etapa.
[root@oracle26ai ~]# cat /u01/autoupgrade/logs/cfgtoollogs/upgrade/auto/status/status.log ========================================== Autoupgrade Summary Report ========================================== [Date] Thu Feb 19 17:38:13 BRT 2026 [Number of Jobs] 1 ========================================== [Job ID] 109 ========================================== [DB Name] ora19c [Version Before Upgrade] 19.30.0.0.0 [Version After Upgrade] 23.26.1.0.0 ------------------------------------------ [Stage Name] PREUPGRADE [Status] SUCCESS [Start Time] 2026-02-19 15:19:15 [Duration] 0:00:00 [Log Directory] /u01/autoupgrade/logs/ora19c/109/preupgrade ------------------------------------------ [Stage Name] PRECHECKS [Status] SUCCESS [Start Time] 2026-02-19 15:19:15 [Duration] 0:00:36 [Log Directory] /u01/autoupgrade/logs/ora19c/109/prechecks [Detail] /u01/autoupgrade/logs/ora19c/109/prechecks/ora19c_preupgrade.log Check passed and no manual intervention needed ------------------------------------------ [Stage Name] PREFIXUPS [Status] SUCCESS [Start Time] 2026-02-19 15:19:51 [Duration] 0:00:32 [Log Directory] /u01/autoupgrade/logs/ora19c/109/prefixups [Detail] /u01/autoupgrade/logs/ora19c/109/prefixups/prefixups.html ------------------------------------------ [Stage Name] DRAIN [Status] SUCCESS [Start Time] 2026-02-19 15:20:24 [Duration] 0:03:39 [Log Directory] /u01/autoupgrade/logs/ora19c/109/drain ------------------------------------------ [Stage Name] DBUPGRADE [Status] SUCCESS [Start Time] 2026-02-19 15:24:04 [Duration] 1:55:34 [Log Directory] /u01/autoupgrade/logs/ora19c/109/dbupgrade ------------------------------------------ [Stage Name] POSTCHECKS [Status] SUCCESS [Start Time] 2026-02-19 17:19:41 [Duration] 0:00:07 [Log Directory] /u01/autoupgrade/logs/ora19c/109/postchecks [Detail] /u01/autoupgrade/logs/ora19c/109/postchecks/ora19c_postupgrade.log Check passed and no manual intervention needed ------------------------------------------ [Stage Name] POSTFIXUPS [Status] SUCCESS [Start Time] 2026-02-19 17:19:52 [Duration] 0:13:38 [Log Directory] /u01/autoupgrade/logs/ora19c/109/postfixups [Detail] /u01/autoupgrade/logs/ora19c/109/postfixups/postfixups.html ------------------------------------------ [Stage Name] POSTUPGRADE [Status] SUCCESS [Start Time] 2026-02-19 17:33:30 [Duration] 0:00:00 [Log Directory] /u01/autoupgrade/logs/ora19c/109/postupgrade ------------------------------------------ [Stage Name] SYSUPDATES [Status] SUCCESS [Start Time] 2026-02-19 17:33:31 [Duration] 0:04:41 [Log Directory] /u01/autoupgrade/logs/ora19c/109/sysupdates ------------------------------------------ Summary:/u01/autoupgrade/logs/ora19c/109/dbupgrade/upg_summary.log [root@oracle26ai ~]#
Alem do Summary Report temos o Upgrade Summary Log (upg_summary.log), que é o relatório detalhado do upgrade do dicionário, gerado durante a fase DBUPGRADE do Oracle AutoUpgrade. Ele é produzido pelo Post-Upgrade Status Tool (baseado no catctl/catcon) e mostra exatamente o que foi atualizado em cada container do CDB.
[root@oracle26ai ~]# cat /u01/autoupgrade/logs/ora19c/109/dbupgrade/upg_summary.log Oracle Database Release 23 Post-Upgrade Status Tool 02-19-2026 16:39:3 Container Database: ORA19C [CON_ID: 1 => CDB$ROOT] Component Current Full Elapsed Time Name Status Version HH:MM:SS Oracle Server UPGRADED 23.26.1.0.0 00:58:33 JServer JAVA Virtual Machine UPGRADED 23.26.1.0.0 00:07:39 Oracle XDK UPGRADED 23.26.1.0.0 00:01:30 Oracle Database Java Packages UPGRADED 23.26.1.0.0 00:00:37 OLAP Analytic Workspace UPGRADED 23.26.1.0.0 00:00:19 Oracle Label Security UPGRADED 23.26.1.0.0 00:00:27 Oracle Database Vault UPGRADED 23.26.1.0.0 00:03:02 Oracle Text UPGRADED 23.26.1.0.0 00:01:29 Oracle Workspace Manager UPGRADED 23.26.1.0.0 00:01:37 Oracle Real Application Clusters UPGRADED 23.26.1.0.0 00:00:00 Oracle XML Database UPGRADED 23.26.1.0.0 00:01:02 Spatial UPGRADED 23.26.1.0.0 00:04:18 Oracle OLAP API UPGRADED 23.26.1.0.0 00:00:13 Datapatch 00:00:09 Final Actions 00:00:23 Post Upgrade 00:00:13 Total Upgrade Time: 01:15:14 [CON_ID: 1 => CDB$ROOT * ] Asterisks denotes compilation time has been included during the upgrade process unless invoked from AutoUpgrade. Database time zone version is currently at 32. It is older than the latest time zone version data file 43 that is shipped in the target home. Time zone upgrade is recommended using the DBMS_DST package. Note that this message is printed before post upgrade fixups are run. To review if a time zone upgrade is needed, query the database before updating the time zone manually. Use "select version from v$timezone_file" to query current database timezone ver sion. Use "select dbms_dst.get_latest_timezone_version from dual" to query the latest timezone version in the target home. Oracle Database Release 23 Post-Upgrade Status Tool 02-19-2026 17:18:3 Container Database: ORA19C [CON_ID: 2 => PDB$SEED] Component Current Full Elapsed Time Name Status Version HH:MM:SS Oracle Server UPGRADED 23.26.1.0.0 00:16:26 JServer JAVA Virtual Machine UPGRADED 23.26.1.0.0 00:05:07 Oracle XDK UPGRADED 23.26.1.0.0 00:01:59 Oracle Database Java Packages UPGRADED 23.26.1.0.0 00:00:21 OLAP Analytic Workspace UPGRADED 23.26.1.0.0 00:00:14 Oracle Label Security UPGRADED 23.26.1.0.0 00:00:24 Oracle Database Vault UPGRADED 23.26.1.0.0 00:02:57 Oracle Text UPGRADED 23.26.1.0.0 00:01:09 Oracle Workspace Manager UPGRADED 23.26.1.0.0 00:01:21 Oracle Real Application Clusters UPGRADED 23.26.1.0.0 00:00:00 Oracle XML Database UPGRADED 23.26.1.0.0 00:00:55 Spatial UPGRADED 23.26.1.0.0 00:05:59 Oracle OLAP API UPGRADED 23.26.1.0.0 00:00:15 Datapatch 00:00:06 Final Actions 00:00:22 Post Upgrade 00:00:15 Total Upgrade Time: 00:32:18 [CON_ID: 2 => PDB$SEED * ] Asterisks denotes compilation time has been included during the upgrade process unless invoked from AutoUpgrade. Database time zone version is currently at 32. It is older than the latest time zone version data file 43 that is shipped in the target home. Time zone upgrade is recommended using the DBMS_DST package. Note that this message is printed before post upgrade fixups are run. To review if a time zone upgrade is needed, query the database before updating the time zone manually. Use "select version from v$timezone_file" to query current database timezone ver sion. Use "select dbms_dst.get_latest_timezone_version from dual" to query the latest timezone version in the target home. Oracle Database Release 23 Post-Upgrade Status Tool 02-19-2026 17:18:4 Container Database: ORA19C [CON_ID: 3 => PDB1] Component Current Full Elapsed Time Name Status Version HH:MM:SS Oracle Server UPGRADED 23.26.1.0.0 00:16:26 JServer JAVA Virtual Machine UPGRADED 23.26.1.0.0 00:05:07 Oracle XDK UPGRADED 23.26.1.0.0 00:01:59 Oracle Database Java Packages UPGRADED 23.26.1.0.0 00:00:21 OLAP Analytic Workspace UPGRADED 23.26.1.0.0 00:00:15 Oracle Label Security UPGRADED 23.26.1.0.0 00:00:24 Oracle Database Vault UPGRADED 23.26.1.0.0 00:02:57 Oracle Text UPGRADED 23.26.1.0.0 00:01:10 Oracle Workspace Manager UPGRADED 23.26.1.0.0 00:01:21 Oracle Real Application Clusters UPGRADED 23.26.1.0.0 00:00:00 Oracle XML Database UPGRADED 23.26.1.0.0 00:00:55 Spatial UPGRADED 23.26.1.0.0 00:05:59 Oracle OLAP API UPGRADED 23.26.1.0.0 00:00:15 Datapatch 00:00:09 Final Actions 00:00:32 Post Upgrade 00:00:15 Total Upgrade Time: 00:32:17 [CON_ID: 3 => PDB1] Database time zone version is currently at 32. It is older than the latest time zone version data file 43 that is shipped in the target home. Time zone upgrade is recommended using the DBMS_DST package. Note that this message is printed before post upgrade fixups are run. To review if a time zone upgrade is needed, query the database before updating the time zone manually. Use "select version from v$timezone_file" to query current database timezone ver sion. Use "select dbms_dst.get_latest_timezone_version from dual" to query the latest timezone version in the target home. Upgrade Times Sorted In Descending Order Total Upgrade Time: 01:15:14 [CON_ID: 1 => CDB$ROOT * ] Total Upgrade Time: 00:32:18 [CON_ID: 2 => PDB$SEED * ] Total Upgrade Time: 00:32:17 [CON_ID: 3 => PDB1] Grand Total Upgrade Time: [0d:1h:55m:34s] [root@oracle26ai ~]#
Fontes:
Comentários
Postar um comentário