Need to remove dbtools_jdk-1.8.0.192-1.el7.x86_64 rpm before Exadata image update to 22.1.10 (Doc ID 2951407.1)

Last updated on JUNE 30, 2023

Applies to:

Symptoms

Customer trying to update DOMU Exadata image to 22.1.10.  image update reported below error at the end

[1684449390][2023-05-18 19:07:23 -0400][INFO][0-0][./patchmgr][patchmgr_print_format_message][298]  <hostname> is ready to reboot.
[1684449390][2023-05-18 19:07:23 -0400][INFO][0-0][./patchmgr][patchmgr_print_format_message][298]  SUCCESS: DONE: dbnodeupdate.sh run
ning an update step on <hostname>
.
.
[1684449390][2023-05-18 19:14:35 -0400][INFO][0-0][./patchmgr][patchmgr_print_format_message][298]  Working: DO: Initiate completion s
tep from dbnodeupdate.sh on beta-qbznb2
[1684449390][2023-05-18 19:17:32 -0400][ERROR][0-0][./patchmgr][patchmgr_print_format_message][298]  There was an error during the com  >>>>>>
pletion step on <hostname>

Symptoms

+++++++++++

- exadata-dbmmgmt update failed with java dependency issues & image status marked as failed.
- dbserverd service was down
- jdk rpm was missing
- exadata-dbmmgmt rpm version was older 

// dbnodeupdate.log:

zzz - ./dbnodeupdate.sh called from hostname:/u01/dbnodeupdate.patchmgr

with arguments -g -P 100523231634 -q -s -a -S -u -l

p35129585_221000_Linux-x86-64.zip -t 22.1.10.0.0.230422 at 2023-05-10 23:35:33

 [1683761733][2023-05-10 23:35:44+0000][INFO][./dbnodeupdate.sh][InitLogfile][] # dbnodeupdate.sh script rel.  : 23.230418 started at (runid :100523231634)

 .

: :

.

 [1683761733][2023-05-10 23:48:59 +0000][CMD][./dbnodeupdate.sh][RemoveAllJDK][] [CMD: rpm -e --nodeps

 jdk1.8-1.8.0_361.x86_64] [CMD_STATUS: 0] [EXEC_TIME_IN_ms: 634][1683761733][2023-05-10 23:49:00

 +0000][INFO][./dbnodeupdate.sh][RemoveAllJDK][] Removed: jdk1.8-1.8.0_361.x86_64 >>>>>> system jdk removed

.

.

2023-05-10 23:49:42 +0000: Pre Installation steps in progress ... 2023-05-10 23:49:42 +0000: Trying to update from version

 22.1.7.0.0.230113 to version 22.1.10.0.0.230422!

Previous install dir /opt/oracle/dbserver_22.1.7.0.0.230113 exists

 Cannot shutdown current MS instance, exit. >>>>>>>>>>>>>>>>>>>>>

 error: %pre(exadata-dbmmgmt-22.1.10.0.0.230422-1.noarch) scriptlet  failed, exit status 1 >>>>>>>>>>>>>>>>>>>>>

 Error in PREIN scriptlet in rpm package

 exadata-dbmmgmt-22.1.10.0.0.230422-1.noarch >>>>>>>>>>>>>>>>>>>>>

 .

 Later there were validation failure since dbserverd service couldnt be started.

.

 // validations.log:

 .

 2023-05-11 00:02:06 +0000 vldrun.pl: Command line is  /opt/oracle.cellos/validations/bin/vldrun.pl -quiet -all

 2023-05-11 00:02:06 +0000 vldrun.pl: Run validation misceachboot - 2023-05-11  00:02:17 +0000 vldrun.pl: [FAILED]

2023-05-11 00:02:17 +0000 vldrun.pl: Check log in /var/log/cellos/validations/misceachboot.log

 // misceachboot.log:

 .

 [1683763324][2023-05-11 00:02:12 +0000][CMD][/opt/oracle.cellos/image_functions][image_functions_check_configured_services][] [CMD: systemctl is-active dbserverd.service] [CMD_STATUS: 3] [EXEC_TIME_IN_ms: 28]

 ----- START STDOUT -----

 failed

 ----- END STDOUT -----

 [1683763324][2023-05-11 00:02:12+0000][ERROR][0-0][/opt/oracle.cellos/image_functions][image_functions_check_c

 onfigured_services][] Validation check ERROR - NOT RUNNING for service: dbserverd

Changes

 Customer was trying update exadata image on DOMU to 22.1.10

Cause

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