ODA Restore Node Command: 'odacli restore-node -g' Hung While Upgrading ODA To 19.22 From 19.20 Shows Running >90-Minutes
(Doc ID 3030617.1)
Last updated on JULY 26, 2024
Applies to:
Oracle Database Appliance Software - Version 19.22.0.0.0 ODA and laterInformation in this document applies to any platform.
Symptoms
On : Oracle Database Appliance X8-2HA
Environment
-------------------------------------
Platform: Linux x86-64
OS Ver: Oracle Linux 8
Ver: Oracle Database Appliance X8-2HA 19.22
Problem Summary
-------------------------------------
stuck "odacli restore-node -g" while upgrading ODA to 19.22 from 19.20 , running >90 minutes
Problem Description
-------------------------------------
Issue with "odacli restore-node -g" while upgrading ODA to 19.22 from 19.20.
The job is stuck with following message repeated in dcs-agent.log
2024-06-22 19:06:46,550 DEBUG [backgroundjob-zookeeper-pool-7-thread-1] [] c.o.d.a.s.DcsJobMonitor: OLD STATE : org.jobrunr.jobs.states.EnqueuedState@6f3d2563
2024-06-22 19:06:46,550 DEBUG [backgroundjob-zookeeper-pool-7-thread-1] [] c.o.d.a.s.DcsJobMonitor: NEW STATE : org.jobrunr.jobs.states.ProcessingState@6b02bc5c
2024-06-22 19:06:46,550 DEBUG [backgroundjob-zookeeper-pool-7-thread-1] [] c.o.d.a.s.DcsJobMonitor: Scheduled job status : JOB PROCESSING
2024-06-22 19:06:51,827 DEBUG [IlomMetadataDiscoverer] [] c.o.d.a.s.IlomMetadataDiscoverer: DBNode is not ready, will try to discover ilom later.
2024-06-22 19:06:51,828 DEBUG [IlomMetadataDiscoverer] [] c.o.d.a.s.i.BuildIlom: Succeeded in loading dbNodes from metadata store
2024-06-22 19:06:51,828 DEBUG [IlomMetadataDiscoverer] [] c.o.d.a.s.i.BuildIlom: ilom hasn't been persist to metadata store, will try to discover it later.
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 |