DBA Tips Archive for Oracle

Upgrading OCFS2 - 1.4

by Jeff Hunter, Sr. Database Administrator

Contents

1. Overview
2. Upgrade OCFS2
3. About the Author

Overview

This article describes the steps necessary to upgrade an installation of Oracle Cluster File System 2 (OCFS2) 1.4 on the Linux platform. More specifically, the OCFS2 kernel driver will be upgraded from version 1.4.2-1 to the latest release which at the time of this writing is 1.4.7-1.

In addition, the OCFS2 Tools and Console will be upgraded from version 1.4.2-1 to version 1.4.4-1.

For the purpose of this article, a single OCFS2 file system is configured on a two node Oracle RAC 10g environment to support a shared file system required by Oracle Clusterware (the Oracle cluster registry file and the voting disk). The following table describes the current OCFS2 file system:

Upgrade OCFS2

Upgrading from OCFS2 version 1.4.2-1 to 1.4.7-1 does not require any on-disk format change. At a minimum, only a simple kernel driver update is required in most situations which means the entire upgrade process could be performed in a rolling manner. While this would avoid a cluster-wide outage, a full outage was still scheduled for this upgrade since it was unknown if cleaning out any previous orphan files (using fsck.ocfs2) could be performed on a disk device that still had other cluster instances mounting it.

As mentioned earlier, the OCFS2 Console and OCFS Tools module will also be upgraded to the latest version along with the kernel driver.

Perform the following from all nodes in the Oracle RAC cluster.

• Bring Down all Oracle Database Services

[oracle@thing1 ~]$ srvctl stop database -d thingdb [oracle@thing1 ~]$ srvctl stop asm -n thing1 [oracle@thing1 ~]$ srvctl stop asm -n thing2 [oracle@thing1 ~]$ srvctl stop nodeapps -n thing1 [oracle@thing1 ~]$ srvctl stop nodeapps -n thing2

• Bring Down Oracle Clusterware – (all nodes)

[root@thing1 ~]# /u01/app/crs/bin/crsctl stop crs [root@thing2 ~]# /u01/app/crs/bin/crsctl stop crs

• Un-mount All OCFS2 Volumes – (all nodes)

[root@thing1 ~]# umount /u02 [root@thing2 ~]# umount /u02

• If Required, Remove any Orphaned Files – (all nodes)

Note: If orphaned files are detected and removed by fsck.ocfs2, run the fsck.ocfs2 command again to verify all orphaned files have been cleared out.

[root@thing1 ~]# /sbin/fsck.ocfs2 -fy /dev/iscsi/thingdbcrsvol1/part1 [root@thing2 ~]# /sbin/fsck.ocfs2 -fy /dev/iscsi/thingdbcrsvol1/part1

• Stop OCFS2 Services – (all nodes)

[root@thing1 ~]# /etc/init.d/o2cb offline ocfs2 [root@thing1 ~]# /etc/init.d/o2cb unload [root@thing2 ~]# /etc/init.d/o2cb offline ocfs2 [root@thing2 ~]# /etc/init.d/o2cb unload

• If Required, Update OCFS2 Console and Tools Module – (all nodes)

[root@thing1 ~]# rpm -Uhv ocfs2console-1.4.4-1.el5.i386.rpm ocfs2-tools-1.4.4-1.el5.i386.rpm [root@thing2 ~]# rpm -Uhv ocfs2console-1.4.4-1.el5.i386.rpm ocfs2-tools-1.4.4-1.el5.i386.rpm

Note: Updating the OCFS2 modules (above) will remove all old OCFS2 RPMs (version 1.4.2-1) and replace them with the newer OCFS2 RPMs (version 1.4.4-1):

[root@thing1 ~]# rpm -qa | egrep "ocfs2console|ocfs2-tools" ocfs2console-1.4.4-1.el5 ocfs2-tools-1.4.4-1.el5

• Update OCFS2 Kernel Module – (all nodes)

[root@thing1 ~]# rpm -Uhv ocfs2-2.6.18-164.el5-1.4.7-1.el5.i686.rpm [root@thing2 ~]# rpm -Uhv ocfs2-2.6.18-164.el5-1.4.7-1.el5.i686.rpm

Note: Updating the OCFS2 modules (above) will remove all old OCFS2 RPMs (version 1.4.2-1) and replace them with the newer OCFS2 RPMs (version 1.4.7-1):

[root@thing1 ~]# rpm -qa | grep ocfs2-2 ocfs2-2.6.18-164.el5-1.4.7-1.el5

• Ensure init Services ocfs2 and o2cb are Enabled – (all nodes)

[root@thing1 ~]# chkconfig --add o2cb [root@thing1 ~]# chkconfig --add ocfs2 [root@thing2 ~]# chkconfig --add o2cb [root@thing2 ~]# chkconfig --add ocfs2

• Check Whether the Services are Enabled – (all nodes)

[root@thing1 ~]# chkconfig --list o2cb o2cb 0:off 1:off 2:on 3:on 4:on 5:on 6:off [root@thing1 ~]# chkconfig --list ocfs2 ocfs2 0:off 1:off 2:on 3:on 4:on 5:on 6:off ---------------------------- [root@thing2 ~]# chkconfig --list o2cb o2cb 0:off 1:off 2:on 3:on 4:on 5:on 6:off [root@thing2 ~]# chkconfig --list ocfs2 ocfs2 0:off 1:off 2:on 3:on 4:on 5:on 6:off

• Update OCFS2 Cluster Timeouts – (all nodes)

The default cluster stack configuration file for o2cb from the initial OCFS2 installation (/etc/sysconfig/o2cb) will still exist and contain the same values after the upgrade. It is highly recommended, however, to run the o2cb init script using the "configure" option in order to set any additional timeout parameters that may have been introduced in the newer version of OCFS2.

[root@thing1 ~]# /etc/init.d/o2cb configure [root@thing2 ~]# /etc/init.d/o2cb configure

After the o2cb configuration process, the OCFS2 cluster stack will be started.

• Restart OCFS2 – (all nodes)

At this stage one could either reboot the nodes or simply restart the cluster and mount the volume(s).

Reboot All Oracle RAC Nodes – (Method 1)

[root@thing1 ~]# reboot [root@thing2 ~]# reboot

Restart OCFS2 Cluster / Mount Cluster Volumes – (Method 2)

Re-enable OCFS2 Services on All Nodes

Note: If you updated the OCFS cluster timeouts by running the command "/etc/init.d/o2cb configure" in the previous section, the o2cb and ocfs2 services will already be started, in which case, you are not required to run the following commands to start the OCFS2 cluster services.

[root@thing1 ~]# /etc/init.d/o2cb start [root@thing1 ~]# /etc/init.d/ocfs2 start [root@thing2 ~]# /etc/init.d/o2cb start [root@thing2 ~]# /etc/init.d/ocfs2 start

Re-mount OCFS2 Volumes

[root@thing1 ~]# mount /u02 [root@thing2 ~]# mount /u02

Bring Up Oracle Clusterware

[root@thing1 ~]# /u01/app/crs/bin/crsctl start crs [root@thing2 ~]# /u01/app/crs/bin/crsctl start crs

About the Author

Jeffrey Hunter is an Oracle Certified Professional, Java Development Certified Professional, Author, and an Oracle ACE. Jeff currently works as a Senior Database Administrator for The DBA Zone, Inc. located in Pittsburgh, Pennsylvania. His work includes advanced performance tuning, Java and PL/SQL programming, developing high availability solutions, capacity planning, database security, and physical / logical database design in a UNIX, Linux, and Windows server environment. Jeff's other interests include mathematical encryption theory, programming language processors (compilers and interpreters) in Java and C, LDAP, writing web-based database administration tools, and of course Linux. He has been a Sr. Database Administrator and Software Engineer for over 18 years and maintains his own website site at: http://www.iDevelopment.info. Jeff graduated from Stanislaus State University in Turlock, California, with a Bachelor's degree in Computer Science.