- 最后登录
- 2023-8-16
- 在线时间
- 1686 小时
- 威望
- 2135
- 金钱
- 50532
- 注册时间
- 2011-10-12
- 阅读权限
- 200
- 帖子
- 5207
- 精华
- 39
- 积分
- 2135
- UID
- 2
|
1#
发表于 2011-10-25 00:26:42
|
查看: 9139 |
回复: 0
文档 Installing CRS on Windows 2008 Fails When Checking OCFS and Orafence Driver's Signatures
- Applies to:
- Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 11.1.0.8 - Release: 10.2 to 11.1
- Microsoft Windows x64 (64-bit)
- Microsoft Windows Server 2008 x64 (AMD64/EM64T)
- Symptoms
- Installing Oracle 10g Clusterware on Windows 2008 64-Bit gives an error during the prerequisite checks that the Ocfs and Orafence Driver's signatures are expired on Win 2k8:
-
- Checking the InstallActions.log, you will also see the following warning:
- INFO: --------------------------------------------------------------------------------
- INFO: Checking CheckOcfsDriverValidity
- This is a pre-requisite check to ensure that ocfs and orafence driver's signatures are not expired.
- INFO: Commad used for VerifySignature.exe is C:\Users\haclu\AppData\Local\Temp\OraInstall2009-01-26_01-02-15AM\bin\win64\VerifySignature.exe C:\Users\haclu\AppData\Local\Temp\OraInstall2009-01-26_01-02-15AM\ext\jlib\ocfs.sys.w2k864
- INFO: output from binary executable is FALSE
- INFO: Check complete. The overall result of this check is: Failed <<<<
- INFO: --------------------------------------------------------------------------------
- --------------------------------------------------------------------------------
-
- INFO: Checking CheckOcfsDriverValidity
- This is a pre-requisite check to ensure that ocfs and orafence driver's signatures are not expired.
- INFO: Commad used for VerifySignature.exe is
- C:\Users\ADMINI~1\AppData\Local\Temp\2\
- OraInstall2009-01-20_01-07-17PM\bin\win64\VerifySignature.exe
- C:\Users\ADMINI~1\AppData\Local\Temp\2\OraInstall2009-01-20_01-07-17PM\
- ext\jlib\ocfs.sys.w2k864
- INFO: output from binary executable is FALSE
- INFO: Check complete. The overall result of this check is: Failed
- --------------------------------
- Changes
- Signatures expired for OCFS.SYS and Orafencedrv.sys as of Jan 16, 2009.
- Cause
- Microsoft has made driver signing mandatory for x64 platforms beginning with Windows 2008. The signatures for the Oracle-Provided drivers Ocfs.sys and Orafencedrv.sys expired as of Jan 16, 2009. Updated drivers with signatures extended to Jan 16, 2012 have been uploaded to Metalink under Patch 7320726.
-
- Note that this issue affects only 10g on x64 Windows 2008. Signatures are not mandatory for 32-Bit platforms, so this issue does not affect 32-Bit installations. In addition, 11g for x64 Windows 2008 is not affected, as the base release for 11g CRS for Windows 2008 already contains the updated drivers.
- Solution
- The preferred solution for avoiding this problem is to follow these steps:
-
- Step #1. Exit out of the installer
- Step #2. Download Patch 7320726 and unzip the updated drivers to a staging folder somewhere. For this example, we will use D:\driver_stage as the location where the drivers will be staged. Once extracted, the full path to the drivers will be:
- D:\driver_stage\7320726
- This directory should contain the following files:
- 01/16/2009 06:41 PM 579,112 ocfs.sys
- 01/16/2009 06:41 PM 16,424 orafencedrv.sys
- 01/16/2009 07:10 PM 1,026 Readme.txt
- Note: Before implementing Step #3, check that there are no other directories containing ocfs drivers in the PATH statement to ensure that the new drivers are picked up
-
- Step#3. Rename the driver files so that the installer will recognize them. Rename the files to:
- orafencedrv.sys.w2k8
- ocfs.sys.w2k864
- D:\driver_stage\7320726> rename orafencedrv.sys orafencedrv.sys.w2k8
- D:\driver_stage\7320726> rename ocfs.sys ocfs.sys.w2k864
- D:\driver_stage\7320726> dir
- 01/16/2009 06:41 PM 579,112 ocfs.sys.w2k864
- 01/16/2009 06:41 PM 16,424 orafencedrv.sys.w2k8
- 01/16/2009 07:10 PM 1,026 Readme.txt
- Use any other name file extension if w2k8 has already been used.
- Step#4. Start the installer again using the following syntax:
- setup.exe New_Driver_Loc=""
- oracle.has.cfs:s_newOcfspath="new_drive_location"
- oracle.has.crs:b_isWIN2k8="TRUE"
- oracle.has.crs:s_newOcfspath="new_drive_location"
- -ignoreSysprereqs
- So in this example, the exact syntax would be:
- setup.exe New_Driver_Loc="D:\driver_stage\7320726" oracle.has.crs:b_isWIN2k8="TRUE" oracle.has.crs:s_newOcfspath="D:\driver_stage\7320726" -ignoreSysprereqs
-
- If you have an existing 10gR2 clusterware installation on Windows 2008, that was installed prior to Jan 16, 2009 (i.e. prior to the driver expiration date) then the warning would not have displayed during the install. However, those drivers should still be updated following the steps below.
- After the installation is completed, download and apply Patch 7320726, which has updated drivers for ocfs.sys and orafencedrv.sys. To copy over the updated drivers, follow these steps:
- 1. Stop all Oracle Services
- 2. Navigate to the \windows\system32\driver directory and rename ocfs.sys and orafencedrv.sys, to back them up
- 3. Copy in the new orafencedrv.sys and ocfs.sys from the patch staging area
- 4. Reboot
- 5. Repeat the process on all nodes
- The fix for Patch 7320726 is also included in the 10.2.0.4 Windows Bundle Patch 19 and higher. Applying Bundle Patch 19 or higher to the CRS Home will update the OraFence driver and ocfs.sys to the latest signed driver versions. Please refer to note 161549.1 for the latest information on Windows bundle patches.
- Change Log
- [14-June-2011] - Changed syntax for "setup.exe New_Driver_Loc...." to be compiant with Oracleî Database Release Notes, 10g Release 2 (10.2) for Microsoft Windows (x64), Part Number B15680-17
- Also added a note that any file extension can be used when renaming the existing *.sys files.
- [5-March-2010] - This note originally incorrectly listed file extensions as .w2k864 instead of .w2k8 - this has been corrected.
- [28-Oct-2010] - Included 'Note:' between steps 2 and 3 to make sure no older ocfs drivers are pointed to from the PATH statement before proceeding
复制代码
|
|