My Oracle Support Banner

Fleet : UDPATE_DB AutoUpgrade Fails With Error "status.json File doesn't exist" On Performing Upgrade from 19C to 21C (Doc ID 3003843.1)

Last updated on APRIL 16, 2025

Applies to:

Enterprise Manager for Oracle Database - Version 13.5.0.0.0 and later
Information in this document applies to any platform.

Symptoms

In Enterprise Manager Cloud Control using Fleet Maintenance, when performing the following UDPATE_DB using autoupgrade for databases 19C to 21C fails with below error.

Command Snippet:

$ emcli db_software_maintenance -performOperation -name="Update DB" -purpose=UPDATE_DB -target_type=oracle_database -target_list="<target_name>" -normal_credential="ORACLE:SYSMAN" -privilege_credential="ROOT:SYSMAN"

JobStep Log : UPGRDAE_DATABASE_PRECHECKS:

Autoupgrade command:
/agent_13.5.0.0.0/oracle_common/jdk/jre/bin/java -jar /scratch/aime1/fleetworkdir/13717990759295/autoupgrade.jar -config
/scratch/aime1/fleetworkdir/13717990759295/autoConfig.cfg -mode ANALYZE -noconsole
/scratch/obase/cfgtoollogs/autoupgrade/t1b0045/cfgtoollogs/upgrade/auto/status/status.json File doesn't exist to validate the result

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.