Exadata Compute Node: Image activation date and status reporting blank post ESS upgrade to 19.3.7.0.0.200428 (Doc ID 2685340.1)

Last updated on JULY 27, 2020

Applies to:

Symptoms

+ Customer upgraded ESS image from 19.3.6.0.0.200317 to 19.3.7.0.0.200428 on Exadata compute node.

+ Post upgrade image status reported blank (neither Success nor failure). But, image version reflecting correctly target version to which upgrade was performed.

         ---------------

[root@node1 ~]# imageinfo

Kernel version: 4.14.35-1902.9.2.el7uek.x86_64 #2 SMP Mon Dec 23 13:39:16 PST 2019 x86_64
Image kernel version: 4.14.35-1902.301.1.el7uek
Image version: 19.3.7.0.0.200428
Image activated:
Image status:
Node type: COMPUTE
System partition on device: /dev/mapper/VGExaDb-LVDbSys1

---------------

+ At first attempt patchmgr failed. As per error stack

        ---------------

[INFO ] Collected dbnodeupdate diag in file: Diag_patchmgr_dbnode_upgrade_040620214337.tbz
-rw-r--r-- 1 root root 2587557 Jun 4 21:57 Diag_patchmgr_dbnode_upgrade_040620214337.tbz
2020-06-04 21:57:34 -0700 :ERROR : FAILED run of command:./patchmgr -dbnodes dbs_group -upgrade -log_dir auto -iso_repo /patch/193700/compute/p31028832_193000_Linux-x86-64.zip -log_dir auto -nomodify_at_prereq -rolling -target_version 19.3.7.0.0.200428 -smtp_from <Email-ID> -smtp_to <Email-ID>
2020-06-04 21:57:34 -0700 :INFO : Upgrade attempted on nodes in file dbs_group: [dbnode_name]
2020-06-04 21:57:34 -0700 :INFO : Current image version on dbnode(s) is:
2020-06-04 21:57:34 -0700 :INFO : <dbnode_name>: 19.3.7.0.0.200428
2020-06-04 21:57:34 -0700 :INFO : For details, check the following files in /patch/193700/compute/dbserver_patch_20.200422.2/log/<dbnode_name>_b2962f5a:
2020-06-04 21:57:34 -0700 :INFO : - <dbnode_name>_dbnodeupdate.log
2020-06-04 21:57:34 -0700 :INFO : - patchmgr.log
2020-06-04 21:57:34 -0700 :INFO : - patchmgr.trc
2020-06-04 21:57:34 -0700 :INFO : Exit status:1

---------------

+ Upgrade was reattempted and per patchmgr, it was successful:

--------
2020-06-04 22:04:38 -0700 :SUCCESS: Initiate update on node(s)
2020-06-04 22:04:38 -0700 :SUCCESS: Completed run of command: ./patchmgr -dbnodes dbs_group -upgrade -log_dir auto -iso_repo /patch/193700/compute/p31028832_193000_Linux-x86-64.zip -log_dir auto -nomodify_at_prereq -rolling -target_version 19.3.7.0.0.200428 -smtp_from <Email-ID>-smtp_to <Email-ID>
2020-06-04 22:04:38 -0700 :INFO : Upgrade attempted on nodes in file dbs_group: [dbnode_name]
2020-06-04 22:04:38 -0700 :INFO : Current image version on dbnode(s) is:
2020-06-04 22:04:38 -0700 :INFO : hpnplxekdb52: 19.3.7.0.0.200428
2020-06-04 22:04:38 -0700 :INFO : For details, check the following files in /patch/193700/compute/dbserver_patch_20.200422.2/log/<dbnode_name>_b2962f5a:
2020-06-04 22:04:39 -0700 :INFO : - <dbnode_name>_dbnodeupdate.log
2020-06-04 22:04:39 -0700 :INFO : - patchmgr.log
2020-06-04 22:04:39 -0700 :INFO : - patchmgr.trc
2020-06-04 22:04:39 -0700 :INFO : Exit status:0
----------

+ Validations have passed

---------------

root@node1 ~]# /opt/oracle.cellos/validations/bin/vldrun.pl -all
Logging started to /var/log/cellos/validations.log
Command line is /opt/oracle.cellos/validations/bin/vldrun.pl -all
Run validation ipmisettings - PASSED
Run validation misceachboot - PASSED
Run validation checkdeveachboot - PASSED
Run validation saveconfig - BACKGROUND RUN

---------------

Changes

 Exadata compute node ESS image upgraded from 19.3.6.0.0.200317 to 19.3.7.0.0.200428.

Cause

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