it is linux, but because of bugs we had to work with
[root@pk7db01 ~]# cat /etc/issue
Red Hat Enterprise Linux Server release 5.11 (Tikanga)
Kernel \r on an \m
[oracle@pk7db02 /home/oracle]$cat /etc/issue
Red Hat Enterprise Linux Server release 5.8 (Tikanga)
Kernel \r on an \m
seems to work fine, at least this week.
On 06/02/2015 05:05 PM, Hameed, Amir wrote:
We are running a four-node RAC (both Grid and RDBMS are 11.2.0.4) on Solaris 10 update 10. We need to upgrade our database and grid to 12c and that requires the OS to be at a minimum of Solaris 10 Update 11. What I would like to find out is that if we do a rolling OS upgrade where we upgrade one RAC node at a time from *Solaris10/Update10* to *Solaris10/Update11*, for how long can these RAC nodes stay out of synch in terms of the OS revision level? Is it possible to upgrade OS on one node every week and spread the entire process over four weeks? Oracle’s response was that the maximum these hosts can stay out of synch is 1-2 days but I would like to validate it from the list.
