查看Exadata的版本

可以通过imagehistory和imageinfo2个命令查看Exadata的dbserver和cellnode的版本, 例如：   DBSERVER: [root@db01 ~]# imagehistory Version : 11.2.2.4.2.111221 Image activation date : 2012-08-09 15:08:29 -0400 Imaging mode : fresh Imaging status : success Version : 11.2.3.1.1.120607 Image activation date : 2012-08-14 19:16:01 -0400 Imaging mode : patch Imaging status : success [root@db01 ~]# imageinfo Kernel version: 2.6.18-274.18.1.0.1.el5 #1 SMP Thu Feb 9 19:07:16 EST 2012 x86_64 Image version: 11.2.3.1.1.120607 Image activated: 2012-08-14 19:16:01 -0400 Image status: success System partition on device: /dev/mapper/VGExaDb-LVDbSys1 [root@cel01 ~]# imagehistory Version : 11.2.2.4.2.111221 Image activation date : 2012-08-09 15:36:25 -0400 Imaging mode : fresh Imaging status : success Version : 11.2.3.1.1.120607 Image activation date : 2012-08-13 18:00:09 -0400 Imaging mode : out of partition upgrade Imaging status : success [root@cel01 ~]# imageinfo Kernel version: 2.6.18-274.18.1.0.1.el5 #1 SMP Thu Feb 9 19:07:16 EST 2012 x86_64 Cell version: OSS_11.2.3.1.1_LINUX.X64_120607 Cell rpm version: cell-11.2.3.1.1_LINUX.X64_120607-1 Active image version: 11.2.3.1.1.120607 Active image activated: 2012-08-13 18:00:09 -0400 Active image status: success Active system partition on device: /dev/md6 Active software partition on device: /dev/md8 In partition rollback: Impossible Cell boot usb partition: /dev/sdm1 Cell boot usb version: 11.2.3.1.1.120607 Inactive image version: 11.2.2.4.2.111221 Inactive image activated: 2012-08-09 15:36:25 -0400 Inactive image status: success Inactive system partition on device: /dev/md5 Inactive software partition on device: /dev/md7 Boot area has rollback archive for the version: 11.2.2.4.2.111221 Rollback to the inactive partitions: Possible       Exadata上的DB版本诊断，还可以参考下面的脚本：    

{ case `uname` in \
Linux ) ILOM="/usr/bin/ipmitool sunoem cli" ;; \
SunOS ) ILOM="/opt/ipmitool/bin/ipmitool sunoem cli" ;; \
esac ; ImageInfo="/opt/oracle.cellos/imageinfo" ; \
uname -srm ; head -1 /etc/*release ; uptime | cut -d, -f1 ; \
$ILOM "show /SP system_description system_identifier" | grep = ; \
$ImageInfo -activated -node -status -ver | grep -v ^$ ; \
} | tee /tmp/ExaInfo.log

Next, as oracle, run: 
$GRID_HOME/OPatch/opatch lsinv -all -oh $GRID_HOME | tee /tmp/OPatchInv.log
$ORACLE_HOME/OPatch/opatch lsinv -all | tee -a /tmp/OPatchInv.log

    Linux 2.6.18-274.18.1.0.1.el5 x86_64 ==> /etc/enterprise-release <== Enterprise Linux Enterprise Linux Server release 5.7 (Carthage) ==> /etc/oracle-release <== Oracle Linux Server release 5.7 ==> /etc/redhat-release <== Red Hat Enterprise Linux Server release 5.7 (Tikanga) 00:45:26 up 16 days system_description = SUN FIRE X4270 M2 SERVER, ILOM v3.0.16.10, r65138 system_identifier = Exadata Database Machine X2-2 AK00012260 Active image version: 11.2.3.1.1.120607 Active image activated: 2012-08-13 18:00:09 -0400 Active image status: success Active node type: STORAGE Inactive image version: 11.2.2.4.2.111221 Inactive image activated: 2012-08-09 15:36:25 -0400 Inactive image status: success Inactive node type: STORAGE