ORACLE EXADATA升級—從11.2.3.1.0到11.2.3.3.0–（6）升級計算節點

Exadata計算節點的升級很簡單，先要在計算節點上關閉CRS和資料庫，並把CRS設定成為disable狀態，這樣在安裝過程中發生重啟，也不會去啟動叢集和資料庫。

[root@gxx2db01 tmp]dcli -g dbs_group -l root "/u01/app/11.2.0.3/grid/bin/crsctl stop crs -f" [root@gxx2db01 tmp]dcli -g dbs_group -l root "ps -ef | grep d.bin" [root@gxx2db01 tmp]dcli -g dbs_group -l root "/u01/app/11.2.0.3/grid/bin/crsctl disable crs"

在這裡我們需要使用工具DB Node Update Utility，也就是補丁16486998所提供的指令碼。詳細內容可以參考文件dbnodeupdate.sh: Exadata Database Server Patching using the DB Node Update Utility (文件 ID 1553103.1)。這篇文件有該指令碼很多的使用案例。我們使用的方式是ISO IMAGE的方式，還可以使用http的方式。升級之前最好先使用-v引數預檢測一把。還有一個注意的地方，如果你的solaris系統沒有被reclaim掉的話，執行該指令碼就會報錯。

整個升級過程如下所示：

[root@gxx2db02 u01]# ./dbnodeupdate.sh -u -l /u01/p17809253_112330_Linux-x86-64.zip ###########################################################################################################################

# Guidelines for using dbnodeupdate.sh (rel. 3.55): #

# - Prerequisites for usage: # 

# 1. Refer to dbnodeupdate.sh options. See MOS 1553103.1 # 

# 2. Use the latest release of dbnodeupdate.sh. See patch 16486998 #

# 3. Run the prereq check with the '-v' option. # 

# I.e.: ./dbnodeupdate.sh -u -l /u01/my-iso-repo.zip -v # 

# ./dbnodeupdate.sh -u -l  -v #  

# - Prerequisite dependency check failures can happen due to customization: # 

# - The prereq check detects dependency issues that need to be addressed prior to running a successful update. #

# - Customized rpm packages may fail the built-in dependency check and system updates cannot proceed until resolved. # 

# When upgrading from releases later than 11.2.2.4.2 to releases before 11.2.3.3.0: # 

# - Conflicting packages should be removed before proceeding the update. # 

# When upgrading to releases 11.2.3.3.0 or later: # 

# - When the 'exact' package dependency check fails 'minimum' package dependency check will be tried. # 

# - When the 'minimum' package dependency check also fails, # # the conflicting packages should be removed before proceeding. # 

# - As part of the prereq checks and as part of the update, a number of rpms will be removed. # 

# This removal is required to preserve Exadata functioning. This should not be confused with obsolete packages. #

# - See /var/log/cellos/packages_to_be_removed.txt for details on what packages will be removed. #

# - In case of any problem when filing an SR, upload the following: #

# - /var/log/cellos/dbnodeupdate.log #

# - /var/log/cellos/dbnodeupdate..diag #

# - where is the unique number of the failing run. #

# 

# ##########################################################################################################################

Continue ? [y/n] 

y 

 (*) 2014-09-06 21:53:28: Unzipping helpers (/u01/dbupdate-helpers.zip) to /opt/oracle.SupportTools/dbnodeupdate_helpers 

 (*) 2014-09-06 21:53:28: Initializing logfile /var/log/cellos/dbnodeupdate.log 

 (*) 2014-09-06 21:53:28: Collecting system configuration details. This may take a while... 

 (*) 2014-09-06 21:53:41: Validating system details for known issues and best practices. This may take a while... 

 (*) 2014-09-06 21:53:41: Checking free space in /u01/iso.stage.060914215326 

 (*) 2014-09-06 21:53:41: Unzipping /u01/p17809253_112330_Linux-x86-64.zip to /u01/iso.stage.060914215326, this may take a while 

 (*) 2014-09-06 21:54:00: Original /etc/yum.conf moved to /etc/yum.conf.060914215326, generating new yum.conf 

 (*) 2014-09-06 21:54:00: Generating Exadata repository file /etc/yum.repos.d/Exadata-computenode.repo

Warning: Network routing configuration requires change before updating database server. See MOS 1306154.1

Continue ? [y/n] 

y 

 (*) 2014-09-06 21:54:17: Validating the specified source location. 

 (*) 2014-09-06 21:54:18: Cleaning up the yum cache. 

 (*) 2014-09-06 21:54:18: Preparing update for releases 11.2.3.3.0 and later 

 (*) 2014-09-06 21:54:28: Performing yum package dependency check for 'exact' dependencies. This may take a while... 

 (*) 2014-09-06 21:54:32: 'Exact'package dependency check succeeded.

 (*) 2014-09-06 21:54:32: 'Minimum' package dependency check succeeded.

 Active Image version : 11.2.3.1.0.120304

 Active Kernel version : 2.6.18-274.18.1.0.1.el5

 Active LVM Name : /dev/mapper/VGExaDb-LVDbSys1 

 Inactive Image version : n/a 

 Inactive LVM Name : /dev/mapper/VGExaDb-LVDbSys2

 Current user id : root

 Action : upgrade

 Upgrading to : 11.2.3.3.0.131014.1 (to exadata-sun-computenode-exact)

 Baseurl : file:///var/www/html/yum/unknown/EXADATA/dbserver/060914215326/x86_64/ (iso)

 Iso file : /u01/iso.stage.060914215326/repoimage.iso

 Create a backup : Yes

 Shutdown stack : No (Currently stack is down)

 Hotspare exists : Yes, but will NOT be reclaimed as part of this update)

                 : Raid reconstruction to add the hotspare to be done later when required

 RPM exclusion list : Not in use (add rpms to /etc/exadata/yum/exclusion.lst and restart dbnodeupdate.sh)

 RPM obsolete list : /etc/exadata/yum/obsolete.lst (lists rpms to be removed by the update)

                   : RPM obsolete list is extracted from exadata-sun-computenode-11.2.3.3.0.131014.1-1.x86_64.rpm

 Exact dependencies : No conflicts

 Minimum dependencies : No conflicts

 Logfile : /var/log/cellos/dbnodeupdate.log (runid: 060914215326)

 Diagfile : /var/log/cellos/dbnodeupdate.060914215326.diag

 Server model : SUN FIRE X4170 M2 SERVER

 dbnodeupdate.sh rel. : 3.55 (always check MOS 1553103.1 for the latest release of dbnodeupdate)

 Note : After upgrading and rebooting run './dbnodeupdate.sh -c' to finish post steps.

 The following known issues will be checked for and automatically corrected by dbnodeupdate.sh:

 (*) - Issue 1.7 - Updating database servers with customized partitions may remove partitions already in use

 (*) - Issue - 11.2.3.3.0 and 12.1.1.1.0 require disabling SDP APM settings. See MOS 1623834.1 

 (*) - Issue - Incorrect validation name for ExaWatcher in /etc/cron.daily/cellos stops ExaWatcher

 (*) - Issue - tls_checkpeer and tls_crlcheck mis-configured in /etc/ldap.conf The following known issues will be checked for but require manual follow-up:

 (*) - Issue - Database Server upgrades may hit network routing issues after the upgrade 

 (*) - Issue - Yum rolling update requires fix for 11768055 when Grid Infrastructure is below 11.2.0.2 BP12

 (*) - Updates from releases earlier than 11.2.3.3.0 may hang during reboot. See MOS 1620826.1 for more details Continue ? [y/n] y

 (*) 2014-09-06 21:54:57: Verifying GI and DB's are shutdown

 (*) 2014-09-06 21:54:59: Collecting console history for diag purposes 

 (*) 2014-09-06 21:55:15: Unmount of /boot successful

 (*) 2014-09-06 21:55:15: Check for /dev/sda1 successful

 (*) 2014-09-06 21:55:15: Mount of /boot successful

 (*) 2014-09-06 21:55:15: Disabling stack from starting

 (*) 2014-09-06 21:55:15: Performing filesystem backup to /dev/mapper/VGExaDb-LVDbSys2. Avg. 30 minutes (maximum 120) depends per environment.....

 (*) 2014-09-06 21:59:26: Backup successful 

 (*) 2014-09-06 21:59:26: OSWatcher stopped successful 

 (*) 2014-09-06 21:59:27: Validating the specified source location. 

 (*) 2014-09-06 21:59:28: Cleaning up the yum cache. 

 (*) 2014-09-06 21:59:28: Preparing update for releases 11.2.3.3.0 and later

 (*) 2014-09-06 21:59:32: Performing yum update. Node is expected to reboot when finished.

 (*) 2014-09-06 22:01:56: Waiting for post rpm script to finish. Sleeping another 60 seconds (60 / 900) Remote broadcast message (Sat Sep 6 22:02:02 2014): Exadata post install steps started. It may take up to 5 minutes. 

 (*) 2014-09-06 22:02:56: Waiting for post rpm script to finish. Sleeping another 60 seconds (120 / 900)

 Remote broadcast message (Sat Sep 6 22:03:15 2014):

 Exadata post install steps completed with success

 It may take up to 5 minutes.

 (*) 2014-09-06 22:02:56: Waiting for post rpm script to finish. Sleeping another 60 seconds (120 / 900)

 Remote broadcast message (Sat Sep 6 22:03:15 2014):

 Exadata post install steps completed with success

整個Update需要40-50分鐘，系統會重啟幾次。在這中間可以觀察到系統重啟後，能ping通，但是ssh是不通的，然後要等待最後一次自動重啟之後才能SSH連上。這期間最好不要著急。

    （本文轉自“新炬網路”官網技術分享欄目）