Patch Manager (patchmgr utility ) To Update Database (Compute) Node Fails With Error 'to release' does not match found release (Doc ID 2246002.1)

Last updated on APRIL 10, 2017

Applies to:

Oracle Exadata Storage Server Software - Version 12.1.2.4.0 to 12.2.1.1.1 [Release 12.1 to 12.2]
Information in this document applies to any platform.

Symptoms

Patch Manager (patchmgr utility ) to update database ( compute ) node fails with error below 

 

ERROR

=============

ERROR: Given 'to release' (12.2.1.2.0.170131) does not match found  release (12.2.1.1.0.170126.2), exiting

 

Make a note , release above is an example.

 

Changes

 With Jan 2017 , the Database Node ( Compute Node ) gets patched using Patch Manager (patchmgr utility) UNLIKE dbnodeupdate.sh that we have been using in the past.

 Syntax Expected in example below is

=============

./patchmgr -dbnodes dbs_group -upgrade -log_dir auto -target_version 12.1.2.3.4.170111 -yum_repo http://my-yum-repo/yum/EngineeredSystems/exadata/dbserver/12.1.2.3.4/base/x86_64/

 

However if you do NOT provide the Target Version here then it fails with an error.

 

ERROR

===============

ERROR: Given 'to release' (12.2.1.2.0.170131) does not match found release (12.2.1.1.0.170126.2), exiting

 

 

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms