Placement of Voting disk and OCR Files in Oracle RAC 10g and 11gR1 [ID 293819.1]

Placement of Voting disk and OCR Files in Oracle RAC 10g and 11gR1 [ID 293819.1]

Modified 27-OCT-2010Type BULLETINStatus PUBLISHED

In this Document
Purpose
Scope and Application
Placement of Voting disk and OCR Files in Oracle RAC 10g and 11gR1
Linux–
AIX –
HP–
Solaris–
Tru64 –
References

Applies to:

Oracle Server - Enterprise Edition - Version: 10.1.0.5 to 11.1.0.7 - Release: 10.1 to 11.1
Information in this document applies to any platform.
OCR, Vote disk, clusterware

Purpose

In Oracle Clusterware 10g and 11g, there are two important cluster files, the Oracle Cluster Repository
(OCR) and the Voting Disk. Due to the nature of these files, they must be placed on shared devices; either
on cluster filesystems, NFS or shared raw devices.

The aim of this document is to provide a clear and concise method to create the OCR and voting disk on
raw devices using native OS utilities; i.e, without the need of extra licensable cluster software tools. The
intent of the document is to augment the platform specific documentation for Clusterware.

This document will focus on Oracle Clusterware 10g and 11g Release 1. Oracle Clusterware 11gR2
provides the capability to store the cluster files in ASM. Please check the Oracle documentation, Oracle®
Database 2 Day + Real Application Clusters Guide 11g Release 2, for 11g Release 2 installation
instructions.

Scope and Application

The procedures will be presented for the following operating systems:

o Linux
o AIX
o HP-UX
o Solaris
o Tru64

Placement of Voting disk and OCR Files in Oracle RAC 10g and 11gR1

Please also reference: Document ID 428681.1 OCR / Vote disk Maintenance Operations (ADD/REMOVE/REPLACE/MOVE), including moving from RAW Devices to Block Devices

Linux–

Prior to installing Oracle CRS, the raw devices that will house the OCR and voting disk files, must be
defined and initialized using the following procedure. Note, this procedure is applicable for RH/OEL 4 and
above as well as SUSE 9 and above. Additionally, this section does not describe how to setup Linux
multipathing, if multipathing is employed, then use the appropriate the multipath device name in place of
the devices listed below

1. Determine which disk devices will be used store the OCR and voting disk file.

2. Execute cat /proc/partitions command on all nodes to verify that the selected devices are available on nodes of the cluster.

3. Run fdisk command to create and label 280 MB partition for each the OCR and voting disk you plan on deploying.

4. Re-run cat /proc/partitions to verify that the partitions are available.

$ cat /proc/partitions
8 33 32098 sdc1 1023842 0 2047682 528080 1023708 0 2047416
681320 0 0
8 65 2048256 sde1 23151853 0 557694461 15652280 3991671 0
122778038 100


In our example, the /dev/sdc1 and /dev/sde1 will be used for OCR and for voting disk; respectively.

5. Initialize the devices using dd.
OCR disk device

dd if=/dev/zero of=/dev/sdc1 bs=125829120 count=1


Voting disk

dd if=/dev/zero of=/dev/sde1 bs=20971520 count=1



6. For each raw device that you specified in the rawdevices file, enter commands similar to the
following to set the owner, group, and permissions on the device file. The root.sh script will to
reset to the appropriate permissions.
OCR

chown root:dba /dev/sdc1
chmod 0640 /dev/sdc1


Voting disk

chown oracle:dba /dev/sde1
chmod 0660 /dev/sde1



7. When installing Oracle CRS, OUI will request the location of the OCR and voting disk. List the appropriate disk names as requested.
For more details see:
http://download.oracle.com/docs/cd/B28359_01/rac.111/b28252/toc.htm

AIX –

Prior to installing Oracle CRS, the raw devices that will house the OCR and voting disk files, must be
defined and initialized using the following procedure. Note this procedure uses raw partitions for these
files and not shared-concurrent logical volumes. The latter requires HACMP.

1. Determine which disk device will be used store the OCR file and voting disk. In our example, the /dev/rhdisk1 and /dev/hdisk2 will be used for the OCR and voting disk; respectively. Make sure that the devices chosen have PVIDs on them.

/usr/sbin/lspv


If no PVID exists, then alter the disk(s)

/usr/sbin/chdev –l hdiskn –a pv=yes


Note, the disk and its PVID must be visible and consistent between nodes. If the device name associated with the PVID for a disk that you want to use is different on any node, you must create a new device file for the disk on each of the nodes using a common unused name. In this case, create a dummy disk; e.g., hdisk99 using the mknod command on both the nodes with the minor and major number of the actual disk being used for OCR or voting disk. This will ensure the disk name is the same across all the nodes.

2. To allow concurrent IO access to this disk device and prevent the device driver from
locking the hdisks with a reservation on open, a no reservation flag must be set. Use the following chdev command to disable this reservation.
All MPIO-capable (ESS, DS8000, DS6000 devices):

chdev -l hdisk1 –a reserve_policy=no_reserve
chdev -l hdisk2 –a reserve_policy=no_reserve


for EMC (Symettrix &Clariion), HDS, IBM DS4000, and non-MPIO capable
devices, perform the following:

chdev -l hdisk1 –a reserve_lock=no
chdev -l hdisk2 –a reserve_lock=no


3. Change the permissions and ownership on the two devices.
OCR disk device

chown root:dba /dev/rhdisk1
chmod 0640 /dev/rhdisk1


Voting disk

chown oracle:dba /dev/rhdisk2
chmod 0660 /dev/rhdisk2


When installing Oracle CRS, OUI will request the location of the OCR and voting disk. List the appropriate disk device paths as listed in Step 1.

HP–

Prior to installing Oracle CRS, the raw devices that will house the OCR and voting disk files, must be
defined and initialized using the following procedure. Note, the following procedures are only necessary if
the devices in question appear as different device names (SCSI paths). If the device names are same, then
skip to step 5.

1. Determine which disk will be used store the OCR and voting disk file.

2. Execute ioscan -fnC disk command on all nodes of cluster to obtain the hardware path and Instance number for the selected devices.

On node1:

ioscan -fnC disk


This will generate output similar to the following:

disk 46 255/255/0/2.2 sdisk CLAIMED DEVICE HSV100 HP
/dev/dsk/c12t2d2 /dev/rdsk/c12t2d2


On node2:

ioscan -fnC disk


This will generate output similar to the following (note the differing devices name and Instance numbers between the two nodes).

disk 47 255/255/0/2.2 sdisk CLAIMED DEVICE HSV100 HP
nb /dev/dsk/c14t2d2 /dev/rdsk/c14t2d2


3. Create new devices using the above same devices:

mksf -C disk -I 47 -H 255/255/0/2.2 /dev/dsk/c12t2d2


and for the raw device:

mksf -C disk -I 47 -H 255/255/0/2.2 -r /dev/rdsk/c12t2d2


4. Re-running ioscan -fnC disk, provides the following output:

disk 47 255/255/0/2.2 sdisk CLAIMED DEVICE HSV100 HP
/dev/dsk/c12t2d2 /dev/rdsk/c12t2d2
/dev/dsk/c14t2d2 /dev/rdsk/c14t2d2


5. Initialize the devices using dd.
OCR disk device

dd if=/dev/zero of=/dev/rdsk/c12t2d2 bs=125829120 count=1


Voting disk

dd if=/dev/zero of=/dev/rdsk/c14t2d2 bs=20971520 count=1


6. Change the permissions and ownership on the two devices.
OCR disk device

chown root:dba /dev/rdsk/c12t2d2
chmod 0640 /dev/rdsk/c12t2d2


Voting disk

chown oracle:dba /dev/rdsk/c14t2d2
chmod 0660 /dev/rdsk/c14t2d2


7. When installing Oracle CRS, the OUI will request the location of the OCR and voting disk. List the appropriate disk device paths as listed in Step 1.

Solaris–

Prior to installing Oracle CRS, raw devices that will house the OCR and voting disk files, must be defined
and initialized using the following procedure:

1. Determine which disk devices will be used store the OCR and voting disk file. Use the format command to list the devices, and select the appropriate device. Create 280 MB partitions for each OCR/Vote you plan on deploying. Note, the disk partition to be used must skip the first 1Mb to avoid overwriting the disk VTOC.

2. Make sure the other nodes can see those devices. If the other nodes see those devices at a different path, then common symbolic links or mknod command must be used to point to the same location.

3. Initialize the devices using dd.

dd if=/dev/zero of=/dev/rdsk/c3t4d12s6 bs=125829120 / count=1
dd if=/dev/zero of=/dev/rdsk/c3t4d15s6 bs=20971520 / count=1



4. Change the permissions and ownership on the two devices.
OCR disk device

chown root:dba /dev/rdsk/c3t4d12s6
chmod 0640 /dev/rdsk/c3t4d12s6


Voting disk

chown oracle:dba /dev/rdsk/c3t4d15s6
chmod 0660 /dev/rdsk/c3t4d15s6


5. When installing Oracle CRS, the OUI will request the location of the OCR and voting disk. List the appropriate disk names as requested.

Tru64 –

Prior to installing Oracle CRS, the directories that will house the OCR and voting disk files, must be
identified. Since HP TruCluster software is required for CRS/RAC installation, it is recommended that
TruCluster Cluster Filesystem (CFS) be implemented. CFS provides single-image view of devices;
therefore, the CRS files can be located on the cluster filesystem.

1. Determine the path and name of the OCR and voting disk. For example

/oradata1/crs/ocr.dat
/oradata1/crs/voting_disk



2. Change the permissions and ownership on the two devices.
OCR disk device

chown root:dba /oradata1/crs/ocr.dat
chmod 0640 /oradata1/crs/ocr.dat


Voting disk

chown oracle:dba /oradata1/crs/voting_disk
chmod 0660 /oradata1/crs/voting_disk


3. When installing Oracle CRS, the OUI will request the location of the OCR and voting disk. List the appropriate disk device paths as listed in Step 1.

References

NOTE:428681.1 - OCR / Vote disk Maintenance Operations: (ADD/REMOVE/REPLACE/MOVE)

------------------------------------------------------------------------------

Blog http://blog.youkuaiyun.com/tianlesoftware

网上资源: http://tianlesoftware.download.youkuaiyun.com

相关视频:http://blog.youkuaiyun.com/tianlesoftware/archive/2009/11/27/4886500.aspx

DBA1 群:62697716(); DBA2 群:62697977()

DBA3 群:62697850 DBA 超级群:63306533;

聊天 群:40132017

--加群需要在备注说明Oracle表空间和数据文件的关系,否则拒绝申请

<think>嗯,用户遇到了Vivado在实现阶段报错的问题,具体是[Place 30-675],关于全局时钟IO引脚和BUFG对的次优布局。我需要先理解这个错误的含义和可能的原因。 首先,全局时钟资源在FPGA设计中非常重要,尤其是时钟信号需要低延迟和高稳定性。BUFG是全局时钟缓冲器,用于将时钟信号分配到全局时钟网络上。如果IO引脚和BUFG之间的布局不理想,可能会导致时序问题或时钟偏差。 根据引用[^1],这个错误通常是因为时钟信号路径不符合FPGA架构的最佳实践。可能的原因有几个:一是时钟输入引脚没有直接连接到BUFG,中间可能有其他逻辑;二是布局约束不足,导致工具无法正确放置;三是物理位置限制,比如BUFG和IO引脚之间的距离过远。 接下来,我需要考虑解决方案。首先检查代码中的时钟定义,确保时钟信号直接连接到BUFG,没有经过逻辑处理。例如在Verilog中,应该使用IBUFG和BUFG组合。然后,添加位置约束,将时钟引脚和BUFG放置在合适的位置,可能需要使用XDC约束文件来指定位置。另外,使用CLOCK_DEDICATED_ROUTE属性可以绕过某些检查,但需谨慎。最后,优化布局策略,比如在Vivado中启用更严格的时钟布局优化选项。 还需要注意,不同FPGA型号的架构可能不同,比如7系列和UltraScale+的BUFG位置可能影响布局策略。因此,用户需要根据具体器件调整约束。 用户可能需要进一步了解如何编写XDC约束,或者如何分析时钟路径。我应该建议他们检查代码中的时钟连接,添加正确的约束,并在必要时参考Xilinx文档或社区资源。如果问题持续,可能需要调整布局或考虑硬件限制。</think>### 全局时钟IO引脚与BUFG对次优布局的解决方案 在FPGA设计中,全局时钟资源(如BUFG)的布局直接影响时序性能和信号完整性。错误`[Place 30-675]`表明时钟输入引脚(如全局时钟IO)与对应的BUFG缓冲器之间的物理路径未达到最佳布局要求,可能导致时钟延迟或布线拥塞[^1]。以下是分步解决方案: --- #### **1. 检查时钟信号路径** - **问题定位**:确认时钟信号是否直接从全局时钟引脚(如`MRCC`或`SRCC`)连接到BUFG,避免中间插入逻辑(如LUT或寄存器)。 - **代码示例**: ```verilog // 正确方式:直接连接BUFG wire clk_ibufg; IBUFG clk_ibufg_inst (.I(clk_in), .O(clk_ibufg)); BUFG bufg_inst (.I(clk_ibufg), .O(clk_out)); ``` --- #### **2. 添加位置约束** - **约束文件(XDC)**:通过约束指定全局时钟引脚和BUFG的位置,确保布局工具优先满足物理邻近性。 ```tcl # 示例:锁定时钟引脚和BUFG位置 set_property PACKAGE_PIN F10 [get_ports clk_in] set_property CLOCK_DEDICATED_ROUTE TRUE [get_nets clk_ibufg] ``` --- #### **3. 绕过次优路径检查(谨慎使用)** - **属性覆盖**:若设计需求允许非标准时钟路径,可添加以下属性(需验证时序): ```tcl set_property CLOCK_DEDICATED_ROUTE FALSE [get_nets clk_ibufg] ``` --- #### **4. 优化布局策略** - **布局参数调整**:在Vivado中启用更高优化级别: ```tcl place_design -post_place_opt -unplace route_design -phys_opt ``` - **BUFG利用率监控**:避免过度使用BUFG资源,7系列FPGA通常支持32个BUFG,需合理分配。 --- #### **关键注意事项** - **架构差异**:UltraScale系列支持`BUFG_GT`,需区分与7系列的设计约束。 - **时钟域交叉**:跨时钟域信号需同步处理,避免因布局问题导致时序违例。 ---
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值