My Oracle Support Banner

ExaCloud: exadbcpatch -list_patches fails with "ERROR: could not find the existing db version" (Doc ID 2711920.1)

Last updated on JANUARY 20, 2022

Applies to:

Oracle Exadata Storage Server Software - Version 12.1.2.4.0 and later
Information in this document applies to any platform.

Symptoms

+ -list_patches operation fails for the db=QA

# /var/opt/oracle/exapatch/exadbcpatchmulti -list_patches -oh=ed0xyz01vm01:/u02/app/oracle/product/11.2.0/dbhome_3/
INFO: cmd is: /var/opt/oracle/exapatch/exadbcpatch -list_patches -patch_homes=/u02/app/oracle/product/11.2.0/dbhome_3 -dbnames=QA
Starting EXADBCPATCH
Logfile is /var/opt/oracle/log/exadbcpatch/exadbcpatch_2020-07-01_14:58:30.452260353890.log
Config file is /var/opt/oracle/exapatch/exadbcpatch.cfg

INFO: dbversion detected : 11204
INFO: patching type : psu

INFO: images available for patching

INFO: patch_all_dbs is set to

Use of uninitialized value within %queries in concatenation (.) or string at /var/opt/oracle/exapatch/../perl_lib/DBAAS/db.pm line 1129.

ERROR: could not find the existing db version <<<<<<<<<<
....

Changes

 

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
Changes
Cause
Solution


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