AutoUpgrade Fails With UPG-1400#UPGRADE FAILED on Windows (Doc ID 2921913.1)

Last updated on FEBRUARY 05, 2025

Applies to:

Oracle Database - Enterprise Edition - Version 18.0.0.0 and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Gen 2 Exadata Cloud at Customer - Version N/A and later
Information in this document applies to any platform.

Symptoms

Announcement
DBUA is officially desupported in Oracle 23ai. This is reflected in the Oracle documentation and AutoUpgrade MOS Note 2485457.1 along with a warning message to alert customers who execute DBUA or manual upgrade methods. AutoUpgrade is the official and only supported method of upgrade.
Note: DBUA for "RAC on Windows" is supported only for the short term until this functionality is available in AutoUpgrade.

Further information on how to use this Tool is documented in Note 2485457.1, Oracle 19c documentation and Oracle 23ai documentation.

To get latest version of AutoUpgrade Tool refer Note 2485457.1

Reference : AutoUprade Blog

Database upgrade using autoupgrade on Windows fails with the following error: UPG-1400#UPGRADE FAILED.
Specifying the SQLPATH environment variable and placing LOGIN.SQL does not solve the problem.

Example:
autoupgrade_<timestamp>.log shows :

oracle.upgrade.autoupgrade.utils.errors.AutoUpgException: AutoUpgException [UPG-1400#UPGRADE FAILED [<ORACLE_SID>]]

autoupgrade_err.log shows:

REASON: SP2-0310: unable to open file "LOGIN.SQL"