Friday, February 09, 2007

CRS Version

I notice that on a lot of forums the following is quite a common question
"How can I verify what version CRS is?".

The version of CRS can be higher than the version of database/ASM software. The commands to see the same are

crsctl query crs softwareversion
crsctl query crs activeversion

So although the difference between the two commands might be obvious I am not sure if this is documented anywhere. Also after upgrading from 10.2.0.1 to 10.2.0.2/10.2.0.3 the active version does not seem to change. This maybe due to bug 5278777 which should be fixed in the 10.2.0.4 patchset.

I upgraded a couple of clusters yesterday from 10.2.0.1 to 10.2.0.3 (without any issues per se) and this is what I see after the CRS upgrade.

elephant-> crsctl query crs softwareversion
CRS software version on node [elephant] is [10.2.0.3.0]
elephant-> crsctl query crs activeversion
CRS active version on the cluster is [10.2.0.1.0]

elephant-> cemutlo -w
2:1:

The cemutlo command is used by the EM agent to query CRS version.

Also a rolling upgrade of CRS causes the VIP to relocate to some other node and you have to manually relocate the same using crs_relocate. This is mentioned in the patchset readme though I am not sure how many customers actually read the section “Known Issues”.

8 comments:

sendivam said...

I upgraded a 6-node cluster from 10.2.0.1 to 10.2.0.2. While upgrading each cluster node, I was checking the software and active versions. Until you upgrade all nodes in a cluster, the active version will not be updated to the software version. When I patched all 6 nodes, I found the software and active versions point to the newly patched version.

Fairlie Rego said...

Thanks Sendivam.
In my case I have upgraded all the nodes in the cluster.

jason said...

cheers for posting the crsctl command to check. Running rhel4 U2 I found same behaviour as Sendivam going from 10.2.0.2 -> 10.2.0.3:

oracle@linuxrac1 ~]$ crsctl query crs softwareversion
CRS software version on node [linuxrac1] is [10.2.0.3.0]
[oracle@linuxrac1 ~]$ crsctl query crs activeversion
CRS active version on the cluster is [10.2.0.2.0]
after upgrading clusterware on 2nd node:
[oracle@linuxrac1 ~]$ crsctl query crs activeversion
CRS active version on the cluster is [10.2.0.3.0]

Indy said...

I upgraded 2-node RAC on Solaris 10 from 10.2.0.1 to 10.2.0.3 and it is showing the correct version

gcrdb1:"/export/home/oracle"> crsctl query crs softwareversion
CRS software version on node [gcrdb1] is [10.2.0.3.0]
gcrdb1:"/export/home/oracle"> crsctl query crs activeversion
CRS active version on the cluster is [10.2.0.3.0]

Anonymous said...

Hi Fairlie,

I have a 10.1.0.4 db and when i run this under CRS_HOME

[oracle@test bin]$ crsctl query crs softwareversion
Unexpected parameter: crs

[oracle@test bin]$ cemutlo -w
1:1:

is this command not active in previous releases?
Thanks,
Roshan

Anonymous said...

Works fine for me too. Patching CRS does not lead to any discrepancy in the version.

>crsctl query crs softwareversion
CRS software version on node [x303] is [10.2.0.3.0]
>crsctl query crs activeversion
CRS active version on the cluster is [10.2.0.3.0]

Analise said...

Good for people to know.

maclean said...

after patched all node from 10.2.0.1 to 10.2.0.4
[root@rh2 bin]# ./crsctl query crs softwareversion
CRS software version on node [rh2] is [10.2.0.4.0]
[root@rh2 bin]# ./crsctl query crs activeversion
CRS active version on the cluster is [10.2.0.1.0]
[root@rh2 bin]# ./crsctl query crs activeversion
CRS active version on the cluster is [10.2.0.4.0]