dbconsole
process needs to be running on the server. The dbconsole process is automatically started after installation.dbconsole
process from the command line:ORACLE_HOME/bin
directory.dbconsole
process:dbconsole
process:dbconsole
process as a service.dbconsole
as a service:Oracle
. The dbconsole
service is listed as OracleDBConsole
ORACLE_SID
, where ORACLE_SID
is your SID. The status of this process is listed in the Status column, either Started or Stopped.postupgrade_fixups.sql
script for Non-CDB to Non-CDB upgrades. ORA_DBA
group. Oracle recommends that you install the new release Oracle Database binaries on the server. Refer to the Oracle Database installation guide for Windows to complete that procedure. preupgrade.log
). If there are preupgrade_fixups.sql
scripts that you must run, then run them. In this example, we show manual fixes for the following errors: em_present
). amd_exists
). trgowner_no_admndbtrg
). mv_refresh
). apex_upgrade_msg
) preupgrade_fixups.sql
scripts. oracle1
, which is a member of the ORA_DBA group. C:apporacleproduct11.2.0dbhome_1
oracle2
, which is a member of the ORA_DBA group. C:apporacle1product19dbhome_1
java -jar %ORACLE_HOME19%rdbmsadminpreupgrade.jar
. %ORACLE_BASE%
. preupgrade.log
is generated in the following path: C:apporacle2cfgtoollogsorcl11preupgradepreupgrade.log
. preupgrade_fixups.sql
log file provides you with instructions to remove Oracle Enterprise Manager manually (em_present
): preupgrade_fixups.sql
log file provides you with instructions to remove the OLAP catalog manually (amd_exists
): preupgrade_fixups.sql
log file provides you with instructions to gather directory statistics (dictionary_stats
). preupgrade_fixups.sql
log file provides you with instructions to grant the ADMINISTER DATABASE TRIGGER privilege (trgowner_no_admndbtrg
): preupgrade_fixups.sql
log file provides you with instructions to refresh materialized views (mv_refresh
): preupgrade_fixups.sql
log file recommends to you that you can upgrade Oracle Application Express (apex_upgrade_msg
). Running this upgrade can reduce the downtime required for the Oracle Database upgrades. The log file provides you with information about how to complete that upgrade:tnsnames.ora
, listener.ora
, password files, wallets, and other similar files to the new Oracle home. LocalSystem
. If you are using a virtual account, then services run using the Windows virtual accounts, with names derived from the service name. If the Oracle Database 19c binaries owner is a virtual account, then you must add that virtual account to the group ORA_Homename_SVCAACCTS
, instead of adding the Oracle Home User. dbupgrade
. The shell script calls the Parallel Upgrade Utility (catctl.pl
), so that you can run the upgrade as a command. This example shows the upgrade of Oracle Database from release 11.2.0.4 to release 19c. The upgrade time for your system can vary from the results in this example. postupgrade_fixups.sql
script for Non-CDB to Non-CDB upgrades. postupgrade_fixups.sql
script that you generated with the Pre-Upgrade Information Tool in the earlier release Oracle home before starting the upgrade: postupgrade_fixup.sql
script could not complete three fixes. so you are instructed to carry out manual fixups. This outcome is normal. To carry out the manual fixups, look at the log file, preupgrade.log
. It contains instructions and script information for how to run manual fixup scripts. These fixup scripts are generated for you by the postupgrade_fixups.sql
script. Follow the instructions provided in the log file to fix the issues.