My Oracle Support Banner

Image upgrade failing during post upgrade steps with status "UPDATE STEP FAILED. NOT PROCEEDED" (Doc ID 2921042.1)

Last updated on JANUARY 17, 2023

Applies to:

Oracle Exadata Storage Server Software - Version 21.2.10.0.0 to 22.1.8.0.0
Information in this document applies to any platform.

Symptoms

ERROR: Expected status not found in /.computenode.post.marker aborting

2023-01-11 07:37:24 -0500 :ERROR : dbnodeupdate.sh running an update step on ***DB03
2023-01-11 07:38:18 -0500 :INFO : SUMMARY FOR ALL NODES:
2023-01-11 07:37:21 -0500 :ERROR : ***DB01 has state: UPDATE STEP FAILED. NOT PROCEEDED
2023-01-11 07:37:42 -0500 :ERROR : ***DB01 has state: UPDATE STEP FAILED. NOT PROCEEDED
2023-01-11 07:37:44 -0500 :ERROR : ***DB01 has state: UPDATE STEP FAILED. NOT PROCEEDED
2023-01-11 07:37:59 -0500 :ERROR : ***DB01 has state: UPDATE STEP FAILED. NOT PROCEEDED
2023-01-11 07:38:18 -0500 :FAILED : Initiate update on node(s).

As well we can see target version of rpms ,but the image version still stays at source version with success status

# imageinfo

Kernel version: 4.14.35-2047.514.5.1.2.el7uek.x86_64
Uptrack kernel version: 4.14.35-2047.516.2.el7uek.x86_64
Image kernel version: 4.14.35-2047.514.5.1.2.el7uek
Image version: 21.2.15.0.0.220816 <<<<<<<<<<<<<<<<<<<<<<<<<<21.2.15 (source)
Image activated: 2022-09-21 10:34:40 -0500
Image status: success
Node type: COMPUTE
System partition on device: /dev/mapper/VGExaDb-LVDbSys1

exadata-sun-computenode-minimum-21.2.19.0.0.221201-1.noarch <<<<<<<<<<<<<21.2.19 image rpms(Target)
exadata-oswatcher-21.2.19.0.0.221201-1.noarch
exadata-applyconfig-21.2.19.0.0.221201-1.noarch
exadata-firmware-compute-21.2.19.0.0.221201-1.noarch
exadata-validations-compute-21.2.19.0.0.221201-1.noarch
exadata-exacli-21.2.19.0.0.221201-1.noarch
exadata-dbmmgmt-21.2.19.0.0.221201-1.noarch
exadata-ibdiagtools-21.2.19.0.0.221201-1.noarch
exadata-kvmutils-21.2.19.0.0.221201-1.noarch
exadata-sun-computenode-21.2.19.0.0.221201-1.noarch
exadata-base-21.2.19.0.0.221201-1.noarch
exadata-binaries-21.2.19.0.0.221201-1.noarch
exadata-commonnode-21.2.19.0.0.221201-1.noarch
exadata-ipconf-21.2.19.0.0.221201-1.noarch

 

 

Changes

 

Exadata image upgrade on compute nodes

 

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
References


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