RE: relink oracle after linux kernel upgrade
Date: Mon, 25 Aug 2008 17:58:23 -0400
Brandon mentioned the Oracle recommended solution (to relink), but, I just wanted to say, in addition to this, check your version of glibc. I'm right now doing a rolling upgrade of our 3-node RHEL4U6 cluster to bump glibc from glibc-2.3.4-2.39 to glibc-2.3.4-2.41. This is to address bug 6790001 which can cause: [ CSSD]2008-08-21 20:46:15.025  >ERROR: clssscExit: CSSD signal 11 in thread GMClientListener
Which causes the node to reboot.
Hope that helps,
Mark J. Bobak
Senior Database Administrator, System & Product Technologies ProQuest
789 E. Eisenhower, Parkway, P.O. Box 1346 Ann Arbor MI 48106-1346
+1.734.997.4059 or +1.800.521.0600 x 4059 mark.bobak_at_proquest.com
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Li Li Sent: Monday, August 25, 2008 4:36 PM
Subject: relink oracle after linux kernel upgrade
I am suggested by our vendor to upgrade from 2.6.9-55.0.12.ELlargesmp to 2.6.9-67.ELlargesmp, it's a 5-node 10.2.0.3 RAC on RHEL4U5 with different ORACLE_HOME for ASM and RDBMS. I googled around and some say to relink oracle after kernel upgrade, some say relink is not necessary.
Anybody has done this before? What is your take on this?
http://www.freelists.org/webpage/oracle-l Received on Mon Aug 25 2008 - 16:58:23 CDT