Image Version -Image History

Connect as a root on compute node:

[root@****~]# imagehistory
Version : 11.2.3.1.1.120607
Image activation date : 2012-08-14 17:18:32 -0700
Imaging mode : fresh
Imaging status : success

Version : 11.2.3.2.1.130302
Image activation date : 2013-09-26 21:12:46 -0500
Imaging mode : patch
Imaging status : success

Version : 11.2.3.3.1.140529.1
Image activation date : 2014-08-05 19:29:02 -0500
Imaging mode : patch
Imaging status : success

Version : 12.1.2.1.1.150316.2
Image activation date : 2015-05-03 09:23:54 -0500
Imaging mode : patch
Imaging status : success

Version : 12.1.2.3.1.160411
Image activation date : 2016-06-01 02:33:18 -0500
Imaging mode : patch
Imaging status : success

Version : 12.2.1.1.2.170714
Image activation date : 2017-11-07 11:51:09 -0600
Imaging mode : patch
Imaging status : success

[root@**** ~]# imageinfo

Kernel version: 4.1.12-61.47.1.el6uek.x86_64 #2 SMP Fri Jun 23 19:43:18 PDT 2017 x86_64 –>It is your kernel version.UEK4
Image kernel version: 4.1.12-61.47.1.el6uek
Image version: 12.2.1.1.2.170714
Image activated: 2017-11-07 11:51:09 -0600
Image status: success
System partition on device: /dev/mapper/VGExaDb-LVDbSys1


Image Version: 12.2.1.1.2.170714

This number consists of three components:

  1. Product version (e.g.12.2.1.1.2)
  2. Date code in YYMMDD format (e.g. 170714) –>Relase July 17th, 2017
  3. (optional) Oracle-internal build number (e.g. 2) –>We don’t have it

 

Leave a Reply

Your email address will not be published. Required fields are marked *