Oracle RAC百问百答-01 RAC篇

RAC: Frequently Asked Questions (RAC FAQ) (文档 ID 220970.1)

1.在操作系统升级后，我是否需要重新链接Oracle Clusterware/Grid Infrastructure home？
1.Do I need to relink the Oracle Clusterware  Grid Infrastructure home after an OS upgrade?

2.如何将数据库实例配置为在12.1.0.1 Oracle Flex Cluster Leaf node节点上运行？
2.How can I configure database instances to run on 12.1.0.1 Oracle Flex Cluster Leaf nodes?

3.在为GigE互连配置NIC卡和交换机时，应在Oracle RAC中将其设置为全双工还是半双工？
3.When configuring the NIC cards and switch for a GigE Interconnect should it be set to FULL or Half duplex in Oracle RAC?

4.NAS存储供应商如何认证其针对Oracle RAC的存储解决方案？
4.How can a NAS storage vendor certify their storage solution for Oracle RAC ?

5.Oracle RAC互连是否支持Infiniband？
5.Is Infiniband supported for the Oracle RAC interconnect?

6.您建议互连使用哪种硬件组件？
6.What kind of HW components do you recommend for the interconnect?

7.我在哪里可以找到支持的解决方案列表，以确保每个平台的NIC可用性/冗余（用于互连）？
7.Where can I find a list of supported solutions to ensure NIC availability  redundancy (for the interconnect) per platform?

8.什么是缓存融合，它如何影响应用程序？
8.What is Cache Fusion and how does this affect applications?

9.我可以在单个Oracle RAC群集上运行多个群集数据库吗？
9.Can I run more than one clustered database on a single Oracle RAC cluster?

10.Oracle RAC数据库对SID有哪些限制？是否限制为5个字符？
10.What are the restrictions on the SID with an Oracle RAC database? Is it limited to 5 characters?

11.是否支持将Oracle Clusterware和Oracle RAC作为不同的用户安装？
11.Is it supported to install Oracle Clusterware and Oracle RAC as different users?

12.从单个实例转换（迁移）到Oracle RAC是否困难？
12.Is it difficult to transition (migrate) from Single Instance to Oracle RAC?

13.Oracle RAC正常运行是否需要rcp和/或rsh？
13.Is rcp and/or rsh required for normal Oracle RAC operation ?

14.Oracle Clusterware或Oracle Real Application群集是否支持异构平台？
14.Does Oracle Clusterware or Oracle Real Application Clusters support heterogeneous platforms?

15.Oracle Database 10g中OCFS和ASM之间的依赖关系是什么？
15.What are the dependencies between OCFS and ASM in Oracle Database 10g ?

16.为什么需要在安装了NFS的RAC二进制文件上设置NOAC属性？
16.Why does the NOAC attribute need to be set on NFS mounted RAC Binaries?

17.我的客户有一个带有Oracle RAC数据库的XA应用程序，我可以跨Oracle RAC实例进行负载平衡吗？
17.My customer has an XA Application with a Oracle RAC Database, can I do Load Balancing across the Oracle RAC instances?

18.对于Oracle Real Application Clusterware，您会向客户、Oracle Clusterware或供应商Clusterware（即HP Service Guard、HACMP、Sun Cluster、Veritas等）推荐什么？
18.What would you recommend to customer, Oracle Clusterware or Vendor Clusterware (I.E. HP Service Guard, HACMP,Sun Cluster, Veritas etc.) with Oracle Real Application Clusters?

19.所有节点上都必须有Oracle数据库吗？
19.Do we have to have Oracle Database on all nodes?

20.Oracle RAC需要什么软件？它有单独的安装CD要订购吗？
20.What software is necessary for Oracle RAC? Does it have a separate installation CD to order?

21.我已使用 alter system set parameter_name =.... scope=spfile.。spfile位于ASM存储上，数据库将不会启动。
21.I have changed my spfile with alter system set parameter_name =.... scope=spfile. The spfile is on ASM storage and the database will not start.

22.如何为Oracle RAC和Oracle Clusterware互连使用VLAN？
22.How to use VLANs for Oracle RAC and the Oracle Clusterware Interconnect?

23.标准版Oracle RAC支持哪些存储？
23.What storage is supported with Standard Edition Oracle RAC?

24.我可以在分布式事务处理环境中使用Oracle RAC吗？
24.Can I use Oracle RAC in a distributed transaction processing environment?

25.更改Oracle用户的uid或gid是否会影响Oracle Clusterware？
25.Does changing uid or gid of the Oracle User affect Oracle Clusterware?

26.我可以将iSCSI存储与Oracle RAC群集一起使用吗？
26.Can I use iSCSI storage with my Oracle RAC cluster?

27.当我们使用SE RAC时，能否在ASM磁盘和常规文件系统上指定存档日志的位置？
27.Can we designate the place of archive logs on both ASM disk and regular file system, when we use SE RAC?

28.将防病毒软件添加到我的RAC群集是个好主意吗？
28.Is it a good idea to add anti-virus software to my RAC cluster?

29.我想使用rconfig将单个实例转换为Oracle RAC，但我正在Oracle RAC中使用raw设备。rconfig是否支持RAW？
29.I want to use rconfig to convert a single instance to Oracle RAC but I am using raw devices in Oracle RAC. Does rconfig support RAW ?

30.我可以使用Oracle Clusterware、Oracle RAC和ASM版本的哪些组合？
30.What combinations of Oracle Clusterware, Oracle RAC and ASM versions can I use?

31.我有一个3节点的Oracle RAC。由于出现问题，其中一个节点必须完全重建。由于没有备份，从集群中删除第三个节点以便将其添加回的正确步骤是什么？
31.I had a 3 node Oracle RAC. One of the nodes had to be completely rebuilt as a result of a problem. As there are no backups, What is the proper procedure to remove the 3rd node from the cluster so it can be added back in?

32.当我们使用SE RAC时，是否可以使用RMAN命令直接将备份输出到常规文件系统（而不是闪存恢复区域）？
32.Can we output the backupset onto regular file system directly (not onto flash recovery area) using RMAN command, when we use SE RAC?

33.如何检查Interconnect上的网络问题？
33.How do I check for network problems on my interconect?

34.实施Oracle RAC需要多少NIC？
34.How many NICs do I need to implement Oracle RAC?

35.使用VLAN隔离网络，与公用网络共享同一交换机时，互连是否存在任何问题？
35.Are there any issues for the interconnect when sharing the same switch as the public network by using VLAN to separate the network?

36.在尝试安装10.2.0.1 Oracle Clusterware时，我无法在Solaris 10服务器上进行用户等价性检查。安装运行正常，没有问题。<<Message: Result: User equivalence check failed for user "oracle".>>
36.I could not get the user equivalence check to work on my Solaris 10 server when trying to install 10.2.0.1 Oracle Clusterware. The install ran fine without issue. << Message: Result: User equivalence check failed for user "oracle". >>

37.为什么netca总是创建侦听公共ip而不仅仅是VIP的侦听器？
37.Why does netca always creates the listener which listens to public ip and not VIP only?

38.我的客户是否可以使用Veritas代理在安装了SFRAC的Unix上管理其Oracle RAC数据库？
38.Can my customer use Veritas Agents to manage their Oracle RAC database on Unix with SFRAC installed?

39.第219页上的Veritas安装文档要求设置LD_LIBRARY_PATH_64。是否应删除此项？
39.The Veritas installation document on page 219 asks for setting LD_LIBRARY_PATH_64. Should I remove this?

40.是否可以使用Oracle RAC.11g运行Oracle RAC？
40.Can I run Oracle RAC 10g with Oracle RAC 11g?

41.RAC是否支持Sun逻辑域（LDOM）？
41.Are Sun Logical Domains (ldoms) supported with RAC?

42.迁移到Oracle RAC时，我应该注意哪些应用程序设计注意事项？
42.What Application Design considerations should I be aware of when moving to Oracle RAC?

43.是否应为仅Oracle Clusterware安装设置SCSI-3保留位？
43.Should the SCSI-3 reservation bit be set for our Oracle Clusterware only installation?

44.我们使用TDE加密数据。我们在节点1上创建一个钱包并复制到节点2和3。打开钱包，我们可以选择所有三个节点上的加密数据。现在，我们要重新输入主密钥。我们该怎么办？
44.We are using Transparent Data Encryption (TDE). We create a wallet on node 1 and copy to nodes 2 & 3. Open the wallet and we are able to select encrypted data on all three nodes..Now, we want to REKEY the MASTER KEY. What do we have to do?

45.我已经安装了11.2 Grid Infrastructure，现在我想安装Oracle数据库的早期版本（11.1或10.2），这是否受支持？
45.I have the 11.2 Grid Infrastructure installed and now I want to install an earlier version of Oracle Database (11.1 or 10.2), is this supported ?

46.在安装了11.2网格基础设施之后，10.2或11.1版本的DBCA出现错误？
46.I get an error with DBCA from 10.2 or 11.1 after I have installed the 11.2 Grid Infrastructure?

47.Oracle RAC的标准版本是什么？
47.What is Standard Edition Oracle RAC?

48.RAC互连是否支持巨型帧？
48.Are jumbo frames supported for the RAC interconnect?

49.SCAN是什么？
49.What is SCAN?

50.如何确定群集中的哪个节点是“主”节点？
50.How do I determine which node in the cluster is the "Master" node?

51.我可以让多个公共网络访问我的Oracle RAC吗？
51.Can I have multiple public networks accessing my Oracle RAC?

52.在哪里可以找到Oracle Database 11g Release 2的Oracle Clusterware二进制文件和ASM二进制文件？
52.Where do I find Oracle Clusterware binaries and ASM binaries with Oracle Database 11g Release 2?

53.我可以在同一群集中运行Oracle 9i RAC和Oracle RAC 10g吗？
53.Can I run Oracle 9i RAC and Oracle RAC 10g in the same cluster?

54.如果我的OCR和投票磁盘在ASM中，我可以关闭ASM实例吗？
54.If my OCR and Voting Disks are in ASM, can I shutdown the ASM instance?

55.Oracle是否支持Solaris容器中的Oracle RAC（又称Solaris区域）？
55.Does Oracle support Oracle RAC in Solaris containers (a.k.a. Solaris Zones)?

56.块设备是否支持OCR、Voting盘和ASM设备？
56.Are block devices supported for OCR, Voting Disks, and ASM devices?

57.是否需要在Oracle RAC 10g版本2中重新启用LMS流程？
57.Is there a need to renice LMS processes in Oracle RAC 10g Release 2?

58.启动Oracle RAC数据库时出现以下错误，我该怎么办？
WARNING: No cluster interconnect has been specified.
58.I get the following error starting my Oracle RAC database, what do I do?

使用Oracle Clusterware 10g和11.1，无法重新链接Oracle Clusterware二进制文件。
Using Oracle Clusterware 10g and 11.1, Oracle Clusterware binaries cannot be relinked.
但是，作为home一部分的客户端共享库可以重新链接，在大多数情况下不需要重新链接它们。
However, the client shared libraries, which are part of the home can be relinked, in most cases there should not be a need to relink them.
查看743649.1文档获得更多信息。
See Document 743649.1 for more information.
使用Oracle Grid Infrastructure 11.2及更高版本，Grid home中的一些可执行文件可以而且应该在操作系统升级后重新链接。
Using Oracle Grid Infrastructure 11.2 and higher, there are some executables in the Grid home that can and should be relinked after an OS upgrade.
以下步骤描述了如何将OracleGrid Infrastructure重新链接到Clusters hom：
The following steps describe how to relink an Oracle Grid Infrastructure for Clusters home:

As root:
# cd Grid_home/crs/install
# perl rootcrs.pl -unlock

As the grid infrastructure for a cluster owner:
$ export ORACLE_HOME=Grid_home
$ Grid_home/bin/relink

As root again:
# cd Grid_home/crs/install
# perl rootcrs.pl -patch

Note:
If using Oracle Grid Infrastructure for Standalone Environments (Oracle Restart), see the Oracle
Documentation for more information: https://docs.oracle.com/database/121/LADBI/oraclerestart.htm#LADBI999
Note:
It is recommended to use the Perl version that comes along with your Grid Infrastructure Install i.e Grid_home/perl/bin/perl rootcrs.pl -patch.

Oracle 12c引入了一种称为Flex cluster的新群集拓扑，其中群集中的服务器可以承担特定的角色—集线器和叶。
Oracle 12c introduces a new cluster topology called Flex Cluster where servers in the cluster can assume the specific roles - HUB and LEAF.
在12.1.0.1版本中，只能为非数据库应用程序配置叶节点。
In the 12.1.0.1 release, the LEAF nodes can only be configured for non-database applications.
不支持在12.1.0.1 Flex群集叶节点上运行数据库实例。
Database instances are not supported to run on the 12.1.0.1 Flex Cluster LEAF nodes.
请参阅Oracle Clusterware下的12c Flex群集常见问题解答。
Please see the 12c Flex Cluster FAQ statement under Oracle Clusterware.

所有网络通信都必须使用全双工。半双工意味着一次只能发送或接收。
You must use Full Duplex for all network communication. Half Duplex means you can only either send OR receive at a time.
请注意，现代操作系统默认为全双工，除非交换机中存在某些电缆问题或配置错误。
Note that modern OS's default to Full Duplex unless there is some cable problem or some mis-configuration in the switch。

有关Oracle RAC技术矩阵（存储是其一部分）的详细信息，请参阅OTN上的此链接。
Please refer to this link on OTN for details on Oracle RAC Technologies Matrix (storage being part of it).
https://www.oracle.com/database/technologies/tech-generic-linux-new.html
支持以下NFS存储供应商：EMC、Fujitsu、HP、IBM、NetApp、Hitachi和Oracle（以前的SUN&Pillar）
Following NFS storage vendors are supported: EMC, Fujitsu, HP, IBM, NetApp, Hitachi, and Oracle (formerly SUN & Pillar)
NFS文件服务器不需要RAC认证。系统和存储供应商必须支持NFS文件服务器。
NFS file servers do not require RAC certification. The NFS file server must be supported by the system and storage vendors.
目前，仅支持NFS协议版本3（NFSv3）。
Currently, only NFS protocol version 3 (NFSv3) is supported.

是的，支持。
Yes, it is supported.

互连的一般建议是提供最高带宽的互连，以及给定平台可用的最低延迟协议。
The general recommendation for the interconnect is to provide the highest bandwidth interconnect, together with the lowest latency protocol that is available for a given platform.
您应该使用冗余的1千兆以太网，我们建议您为此或冗余互连使用功能使用HAIP。
You should use a redundant 1 Gigabit Ethernet and you should use Load Balancing Across, we recommend you use HAIP's for this or the Redundant Interconnect Usage Feature.
请记住，如果使用此功能，则必须为互连使用不同的子网。
Do remember that if you use this feature you must use different subnets for the Interconnect.

IBM AIX - available solutions:
Etherchannel (OS based)
HACMP based network failover solution
More information: Document 296856.1

HP HP/UX - available solutions:
APA - Auto Port Aggregation (OS based)
MC/Serviceguard based network failover solution
Combination of both solutions
More information: Document 296874.1 and Auto Port Aggregation (APA) Support Guide

Sun Solaris - available solutions:
Sun Trunking (OS based)
Sun IPMP (OS based)
Sun Cluster based network failover solution (clprivnet)
More information for Oracle RAC 10g and Oracle RAC 11g Release 1:
My Oracle Support Document 283107.1 - Configure IPMP for the Oracle VIP and IPMP introduction
My Oracle Support Document 368464.1 - How to Setup IPMP as Cluster Interconnect
More information for Oracle RAC 11g Release 2:
My Oracle Support Document 1069584.1 - Solaris IPMP and Trunking for the cluster interconnect in
Oracle Grid Infrastructure

Linux - available solutions:
Bonding
More information: Document 298891.1

Windows - available solutions:
Teaming
在Windows上，确保NIC可用性的协作解决方案通常是网卡驱动程序的一部分。
因此，它们取决于所使用的网卡。有关更多信息，请联系相应的硬件供应商。
On Windows teaming solutions to ensure NIC availability are usually part of the network card driver.
Thus, they depend on the network card used. Please, contact the respective hardware vendor for more information.

OS independent solution:
冗余互连使用可跨多个（最多四个）专用网络（也称为互连）实现负载平衡和高可用性。
Redundant Interconnect Usage enables load-balancing and high availability across multiple (up to four) private networks (also known as interconnects).

Oracle RAC 11g第2版修补程序集1（11.2.0.2）支持将冗余互连用作除Windows之外的所有平台的一项功能。
Oracle RAC 11g Release 2, Patch Set One (11.2.0.2) enables Redundant Interconnect Usage as a feature for all platforms, except Windows.
在使用Solaris群集的系统上，冗余互连使用将使用clprivnet。
On systems that use Solaris Cluster, Redundant Interconnect Usage will use clprivnet.

Cache Fusion是一种新的并行数据库体系结构，用于利用集群计算机实现所有类型应用程序的可伸缩性。
Cache Fusion is a new parallel database architecture for exploiting clustered computers to achieve scalability of all types of applications.
Cache Fusion是一种共享缓存体系结构，它使用目前群集系统上可用的高速低延迟互连来保持数据库缓存一致性。
Cache Fusion is a shared cache architecture that uses high speed low latency interconnects available today on clustered systems to maintain database cache coherency.
数据块需要跨节点进行互连。
Database blocks are shipped across the interconnect to the node where access to the data is needed.
这对系统的应用程序和用户来说是透明的。
This is accomplished transparently to the application and users of the system.
由于缓存融合最多使用3点协议，这意味着它很容易扩展到具有大量节点的集群。
As Cache Fusion uses at most a 3 point protocol, this means that it easily scales to clusters with a large numbers of nodes.
有关更多信息，请参阅缓存融合和全局缓存服务
For further information please refer to Cache Fusion and the Global Cache Service
Part Number A96597-01
http://docs.oracle.com/cd/B10501_01/rac.920/a96597/pslkgdtl.htm
有关更多信息，请访问：
Additional Information can be found at:
Document 139436.1 Understanding 9i Real Application Clusters Cache Fusion

您可以在Oracle RAC群集中运行多个数据库，每个节点一个实例（不同的数据库在群集中具有不同的节点子集），或每个节点多个实例（所有数据库跨所有节点运行）或两者之间的某种组合。
You can run multiple databases in a Oracle RAC cluster, either one instance per node (w/ different databases having different subsets of nodes in a cluster), or multiple instances per node (all databases running across all nodes) or some combination in between.
在每个节点上运行多个实例确实会导致内存和资源碎片，但这与在单个实例环境中在单个节点上运行多个实例没有什么不同，后者非常常见。
Running multiple instances per node does cause memory and resource fragmentation, but this is no different from running multiple instances on a single node in a single instance environment which is quite common.
它确实提供了在节点上共享CPU的灵活性，但Oracle资源管理器目前不会限制一个节点上多个实例之间的资源。
It does provide the flexibility of being able to share CPU on the node, but the Oracle Resource Manager will not currently limit resources between multiple instances on one node.
您需要一个资源级别的OS管理器来执行此操作。
You will need to use an OS level resource manager to do this.

安装/配置工具将10g Release 1和早期版本中的SID前缀限制为5个字符，以便在ORACLE RAC环境中最多支持5+3=8个字符的ORACLE_SID。
The SID prefix in 10g Release 1 and prior versions was restricted to five characters by install/config tools so that an ORACLE_SID of upto max of 5+3=8 characters can be supported in an Oracle RAC environment.
在10g版本2中，SID前缀放宽为最多8个字符，有关更多信息，请参阅BUG 4024251。
The SID prefix is relaxed up to 8 characters in 10g Release 2, see Bug 4024251 for more information.
对于Oracle RAC 11g版本2，当实例启动时，系统将动态分配Oracle RAC中具有策略管理数据库的SID。
With Oracle RAC 11g Release 2, SIDs in Oracle RAC with Policy Managed database are dynamically allocated by the system when the instance starts.
这支持一个动态网格基础设施，它允许实例在集群中的任何服务器上启动。
This supports a dynamic grid infrastructure which allows the instance to start on any server in the cluster.

是的，Oracle Clusterware和Oracle RAC可以作为不同的用户安装。
Yes, Oracle Clusterware and Oracle RAC can be installed as different users.
Oracle Clusterware用户和Oracle RAC用户都必须将OINSTALL作为其主要组。
The Oracle Clusterware user and the Oracle RAC user must both have OINSTALL as their primary group.
每个数据库主目录都可以有一个具有不同用户名的不同OSDBA组。
Every Database home can have a different OSDBA group with a different username.

如果群集和群集软件不存在，则必须安装和配置这些组件。
If the cluster and the cluster software are not present, these components must be installed and configured.
必须使用Oracle Universal Installer添加Oracle RAC选项，这要求必须关闭现有数据库实例
The Oracle RAC option must be added using the Oracle Universal Installer, which necessitates the existing DB instance must be shut down.
数据库中的用户数据不需要更改。
There are no changes necessary on the user data within the database.
但是，自由列表和自由列表组的不足可能会导致多个实例争夺同一块时，表和索引的头块出现冲突。
However, a shortage of freelists and freelist groups can causecontention with header blocks of tables and indexes as multiple instances vie for the same block.
这可能会导致性能问题，并需要进行数据分区。然而，对这些变化的需求应该很少。
This may cause a performance problem and require data partitioning. However,the need for these changes should be rare.
建议：应用自动空间段管理自动执行这些更改。
Recommendation: apply automatic space segment management to perform these changes automatically.
自由空间管理将取代自由列表和自由列表组，效果更好。
The free space management will replace the freelists and freelist groups and is better.
对于每个实例，数据库需要一个重做线程和一个撤消表空间，这可以通过SQL命令或Enterprise Manager工具轻松添加。
The database requires one Redo thread and one Undo tablespace for each instance, which are easily added with SQL commands or with Enterprise Manager tools.
注意：对于Oracle RAC 11g Release 2，如果您使用的是Oracle托管文件（如ASM），则无需预先创建重做线程或撤消表空间。
NOTE: With Oracle RAC 11g Release 2, you do not neet to pre-create redo threads or undo tablespaces if you are using Oracle Managed Files (EG ASM).
数据文件需要移动到集群文件系统（CFS）中的任何一个，以便所有节点都可以访问它们。
Datafiles will need to be moved to either a clustered file system (CFS) so that all nodes can access them.
Oracle建议使用自动存储管理（ASM）。此外，控制文件中的MAXINSTANCES参数必须大于或等于您将在群集中启动的实例数。
Oracle recommends the use of Automatic Storage Management (ASM) Also, the MAXINSTANCES parameter in the control file must be greater than or equal to number of instances you will start in the cluster.
关更多详细信息，请参阅Oracle文档中的从单实例迁移到RAC。

For more detailed information, please see Migrating from single-instance to RAC in the Oracle Documentation.
对于Oracle Database 10g Release 2，$Oracle_HOME/bin/rconfig工具可用于将单实例数据库转换为RAC。
With Oracle Database 10g Release 2, $ORACLE_HOME/bin/rconfig tool can be used to convert Single instance database to RAC.
此工具接收xml输入文件并转换xml中提供信息的单实例数据库。
This tool takes in a xml input file and convert the Single Instance database whose information is provided in the xml.
在执行实际转换之前，可以在“verify only”模式下运行此工具。
You can run this tool in "verify only" mode prior to performing actual conversion.
这在Oracle RAC管理手册中有文档记录，可以在$Oracle_HOME/assistants/rconfig/sampleXMLs/ConvertToRAC.xml中找到示例xml。
This is documented in the Oracle RAC Admin book and a sample xml can be found $ORACLE_HOME/assistants/rconfig/sampleXMLs/ConvertToRAC.xml.
此工具仅支持使用群集文件系统或ASM的数据库。
This tool only supports databases using a clustered file system or ASM.
您不能将其用于原始设备。Grid Control 10g Release 2提供了一个易于使用的向导来执行此功能。
You cannot use it with raw devices. Grid Control 10g Release 2 provides a easy to use wizard to perform this function.
Oracle Enterprise Manager包括协助迁移的工作流(即迁移到ASM、创建备库、将备库转换为RAC等）迁移在Enterprise Manager Grid Control 10.2.0.5中自动进行。
Oracle Enterprise Manager includes workflows to assiste with migrations. (I.E. Migrating to ASM, Creating Standby, Converting Standby to RAC etc) The migration is automated in Enterprise Manager Grid Control 10.2.0.5.

正常Oracle RAC操作不需要"rcp"和“rsh”。
"rcp" and "rsh" are not required for normal Oracle RAC operation.
但是，在旧版本中，安装程序使用了“rsh”和“rcp”，因此应为Oracle RAC和修补程序集安装启用。
However in older versions ""rsh"" and ""rcp"" were used by the installer and therefore should to be enabled for Oracle RAC and patchset installation.
在以后的版本中，这些操作默认使用ssh。
In later releases, ssh is used by default for these operations.

Oracle Clusterware和Oracle Real Application群集不支持同一群集中的异构平台。
Oracle Clusterware and Oracle Real Application Clusters do not support heterogeneous platforms in the same cluster.
我们在同一集群中支持不同速度和大小的机器。
We do support machines of different speeds and size in the same cluster.
所有节点必须运行相同的操作系统（即，它们必须是二进制兼容的）。
All nodes must run the same operating system (I.E. they must be binary compatible).
在主动数据共享环境（如Oracle RAC）中，我们不支持具有不同芯片架构的机器。
In an active data-sharing environment, like Oracle RAC,we do not support machines having different chip architectures.

在Oracle RAC 10g环境中，自动存储管理（ASM）和Oracle群集文件系统（OCFS）之间没有依赖关系。
In an Oracle RAC 10g environment, there is no dependency between Automatic Storage Management (ASM) and Oracle Cluster File System (OCFS).
如果对数据库文件使用自动存储管理（ASM），则不需要OCFS。
OCFS is not required if you are using Automatic Storage Management (ASM) for database files.
对于ASM不处理的文件，您可以在Windows（Linux上的版本2）上使用OCFS—二进制文件（共享oracle home）、跟踪文件等。或者，您可以将这些文件放在本地文件系统上，即使考虑到多个位置，这样做并不方便。
You can use OCFS on Windows( Version 2 on Linux ) for files that ASM does not handle - binaries (shared oracle home), trace files, etc. Alternatively, you could place these files on local file systems even though it's not as convenient given the multiple locations.
Oracle建议对数据库文件使用ASM/ACFS
Oracle recommends using ASM/ACFS for your database files

noac属性是必需的，因为安装程序通过创建一个文件并检查该文件在远程节点上是否存在来确定共享性。
The noac attribute is required because the installer determines sharedness by creating a file and checking for that file’s existance on remote node.
如果未启用noac属性，则此测试将报错误并失败。这将混淆安装程序和opatch。
If the noac attribute is not enabled then this test will incorrectly fail. This will confuse installer and opatch.
默认$ORACLE_HOME/dbs中spfile的其他一些小问题肯定会受到影响。
Some other minor issues issues with spfile in the default $ORACLE_HOME/dbs will definitely be affected.

不，不是在传统的Oracle Net Services负载平衡中。
No, not in the traditional Oracle Net Services Load Balancing.
我们已经编写了一份文档，解释了针对9i、10g版本1和10g版本2的**最佳实践**。
We have written a document that explains the ** best practices for 9i, 10g Release 1 and 10g Release 2** .
随着Oracle Database 10g中服务的引入，生活变得更加轻松。要了解服务，请阅读《Oracle RAC管理和部署指南》。
With the introduction of Services in Oracle Database 10g, life gets easier. To understand services, read the Oracle RAC Admin and Deployment Guide.
使用Oracle RAC 11g，Oracle在Oracle RAC环境中为XA全局事务提供透明支持，该环境支持跨Oracle RAC实例使用Oracle Net Services进行负载平衡。
With Oracle RAC 11g, Oracle provides transparent support for XA global transactions in an Oracle RAC environment which supports load balancing with Oracle Net Services across Oracle RAC instances.

无论是否使用供应商Clusterware，您都将安装和使用Oracle Clusterware。
You will be installing and using Oracle Clusterware whether or not you use the Vendor Clusterware.
Oracle Clusterware提供了一个完整的群集解决方案，是Oracle RAC或自动存储管理（包括ACFS）所必需的。
Oracle Clusterware provides a complete clustering solution and is required for Oracle RAC or Automatic Storage Management (including ACFS).
供应商clusterware仅适用于Oracle 9i RAC。查看MyOracleSupport中的认证矩阵，了解认证供应商clusterware的详细信息。
Vendor clusterware is only required with Oracle 9i RAC. Check the certification matrix in MyOracleSupport for details of certified vendor clusterware.

用于集群数据库的集群中的每个节点通常都会加载数据库和Oracle RAC软件，但不会加载实际的数据文件（这些文件需要通过共享磁盘提供）。
Each node of a cluster that is being used for a clustered database will typically have the database and Oracle RAC software loaded on it, but not actual datafiles (these need to be available via shared disk).
例如，如果希望在4节点群集的2个节点上运行Oracle RAC，则需要在所有节点上安装clusterware，在2个节点上安装Oracle RAC，并且只需要在运行Oracle RAC数据库的两个节点上获得许可即可。
For example, if you wish to run Oracle RAC on 2 nodes of a 4-node cluster, you would need to install the clusterware on all nodes,Oracle RAC on 2 nodes and it would only need to be licensed on the two nodes running the Oracle RAC database.
请注意，使用群集文件系统或NAS存储可以提供一种不一定需要在所有节点上安装Oracle二进制文件的配置。
Note that using a clustered file system, or NAS storage can provide a configuration that does not necessarily require the Oracle binaries to be installed on all nodes.
对于Oracle RAC 11g Release 2，如果您使用的是策略管理的数据库，那么您应该可以在群集中的所有节点上访问Oracle RAC二进制文件。
With Oracle RAC 11g Release 2, if you are using policy managed databases, then you should have the Oracle RAC binaries accessible on all nodes in the cluster.

Oracle Real Application Clusters是Oracle数据库的一个选项，因此是Oracle数据库CD的一部分。

Oracle Real Application Clusters is an option of Oracle Database and therefore part of the Oracle Database CD.
对于Oracle 9i，Oracle 9i RAC是Oracle9i企业版的一部分。
With Oracle 9i, Oracle 9i RAC is part of Oracle9i Enterprise Edition.
如果您将9i EE安装到群集上，并且Oracle Universal Installer（OUI）能够识别该群集，则会为您提供安装RAC的选项。
If you install 9i EE onto a cluster, and the Oracle Universal Installer (OUI) recognizes the cluster, you will be provided the option of installing RAC.
在10g之前的版本中，大多数UNIX平台需要供应商提供的clusterware。
In versions prior to 10g, most UNIX platforms require a vendor supplied clusterware.
对于Intel平台（Linux和Windows），Oracle在Oracle9i Enterprise Edition版本中提供Clusterware软件。
For Intel platforms (Linux and Windows), Oracle provides the Clusterware software within the Oracle9i Enterprise Edition release.
对于Oracle Database 10g及更高版本，Oracle RAC是EE的一个选项，可作为SE的一部分提供。
With Oracle Database 10g and higher releases, Oracle RAC is an option of EE and available as part of SE.
Oracle在其自己的CD上为数据库CD包中包含的所有平台提供Oracle Clusterware。
Oracle provides Oracle Clusterware on its own CD for all platforms included in the database CD pack.
请查看认证矩阵（Note 184875.1）或与适当的平台供应商联系以了解更多信息。
Please check the certification matrix (Note 184875.1) or with the appropriate platform vendor for more information.
在Oracle Database 11g Release 2中，Oracle Clusterware和自动存储管理作为一组称为网格基础结构的二进制文件安装。
With Oracle Database 11g Release 2, Oracle Clusterware and Automatic Storage Management are installed as a single set of binaries called the Grid Infrastructure.
网格基础设施的介质位于单独的CD上或网格目录下。
The media for the grid infrastructure is on a separate CD or under the grid directory.
对于独立服务器，Automatic Storage Management和Oracle Restart作为独立服务器的网格基础结构安装在同一介质上。
For standalone servers, Automatic Storage Management and Oracle Restart are installed as the grid infrastructure for a standalone server which is installed from the same media.

如何恢复：
How to recover:
In $ORACLE_HOME/dbs
. oraenv <instance_name>
sqlplus "/ as sysdba"
startup nomount
create pfile='recoversp' from spfile
/
shutdown immediate
quit
现在编辑新创建的pfile，将参数更改为合理的值。
Now edit the newly created pfile to change the parameter to something sensible.
Then:
sqlplus "/ as sysdba"
startup pfile='recoversp' (or whatever you called it in step one).
create spfile='+<DGNAME>/<DBNAME>/spfile<DBNAME>.ora' from pfile='recoversp'
/
注意：spfile的名称是您原来的init（instance_name）
N.B.The name of the spfile is in your original init(instance_name).ora so adjust to suit
shutdown immediate
startup
quit

Oracle的一贯要求是在Oracle RAC群集中分离各种类型的通信。
It is Oracle's standing requirement to separate the various types of communication in an Oracle RAC cluster.
要求涉及以下通信分离：
This requirement addresses the following separation of communication:
Oracle RAC群集中的每个节点必须至少有一个公共网络。
Each node in an Oracle RAC cluster must have at least one public network.
Oracle RAC群集中的每个节点必须至少有一个专用网络，也称为“群集互连”。
Each node in an Oracle RAC cluster must have at least one private network, also referred to as "cluster interconnect".
如果使用基于网络的连接访问共享存储，则Oracle RAC群集中的每个节点必须至少有一个额外的网络接口。
Each node in an Oracle RAC cluster must have at least an additional network interface, if the shared storage is accessed using a network based connection.
集群互连网络分离可以通过使用独立的专用交换机（提供最高程度的网络隔离）或以太网交换机上定义的虚拟局域网（提供IP网络之间的广播域隔离）来实现。
Cluster interconnect network separation can be satisfied either by using standalone, dedicated switches, which provide the highest degree of network isolation, or Virtual Local Area Networks defined on the Ethernet switch, which provide broadcast domain isolation between IP networks. 
Oracle Clusterware互连部署完全支持VLAN。
VLANs are fully supported for Oracle Clusterware interconnect deployments.

分区允许以太网交换机使用VLAN：
Partitioning the Ethernet switch with VLANs allows for:
共享同一交换机进行私人和公共通信。
Sharing the same switch for private and public communication.
为多个群集的专用通信共享同一交换机。
Sharing the same switch for the private communication of more than one cluster.
共享同一交换机进行专用通信和共享存储访问。
Sharing the same switch for private communication and shared storage access.

应遵循以下最佳做法：
The following best practices should be followed:
群集互连VLAN必须位于非路由IP子网上。

The Cluster Interconnect VLAN must be on a non-routed IP subnet.
所有群集互连网络必须配置非路由IP。
All Cluster Interconnect networks must be configured with non-routed IPs.
服务器-服务器通信应通过互连VLAN通过交换机进行单跳。
The server-server communication should be single hop through the switch via the interconnect VLAN.
没有VLAN-VLAN通信。
There is no VLAN-VLAN communication.

Oracle建议维护子网到VLAN的1:1映射。
Oracle recommends maintaining a 1:1 mapping of subnet to VLAN.
最常见的VLAN部署维护子网到VLAN的1:1映射。
The most common VLAN deployments maintain a 1:1 mapping of subnet to VLAN.
强烈建议避免多子网映射到单个VLAN。
It is strongly recommended to avoid multi-subnet mapping to a single VLAN.
建议对已配置的VLAN交换机上的单个端口进行VLAN访问。
Best practice recommends a single access VLAN port configured on the switch for the cluster interconnect VLAN.
服务器端网络接口应该可以访问单个VLAN。
The server side network interface should have access to a single VLAN.

应配置共享交换机以降低生成树的成本
应遵循交换机供应商的最佳实践，以禁用或限制群集互连VLAN的生成树聚合成本。
The shared switch should be configured to mitigate the cost of Spanning Tree
The switch vendor’s best practices should be followed to either disable or limit the cost of Spanning Tree convergence for the cluster interconnect VLAN.

共享同一交换机以实现专用通信和共享存储访问
Sharing the same switch for private communication and shared storage access
如果基础网络基础设施支持数据中心桥接（DCB），则支持此配置，零数据包丢失，并且可以满足为应用程序定义的延迟和吞吐量。
This configuration is supported, if the underlying network infrastructure supports Data Center Bridging (DCB), zero packet loss and can satisfy the latency and throughput defined for the application.
这可能需要在共享交换机上施加服务质量（QoS），以优先考虑到存储器的基于网络的通信。
This may require imposing a Quality of Service (QoS) on the shared switch to prioritize network based communication to the storage.
经认证的配置支持以太网光纤通道（FCoE）融合网络。
Fiber Channel over Ethernet (FCoE) converged networks are supported for certified configurations.
有关更多详细信息，请参阅白皮书“Oracle RAC和Oracle Clusterware互连VLAN部署注意事项（PDF）”
For more details, Review the white paper "Oracle RAC and Oracle Clusterware Interconnect VLAN Deployment Considerations (PDF)"

根据许可文档，您必须将ASM用于带有SE Oracle RAC的所有数据库文件。
不支持CFS或NFS。
As per the licensing documentation, you must use ASM for all database files with SE Oracle RAC.
There is no support for CFS or NFS.
从Oracle Database 10g第2版许可文件：
From Oracle Database 10g Release 2 Licensing Doc:
Oracle标准版和Oracle Real Application Clusters（RAC）在群集服务器环境中与Oracle Real Application Clusters一起使用时，Oracle数据库标准版要求使用Oracle Clusterware。
Oracle Standard Edition and Oracle Real Application Clusters (RAC) When used with Oracle Real Application Clusters in a clustered server environment, Oracle Database Standard Edition requires the use of Oracle Clusterware.
不支持第三方群集软件管理解决方案。此外，必须使用自动存储管理（ASM）来管理所有与数据库相关的文件，包括数据文件、联机日志、归档日志、控制文件、SPF文件和闪存恢复区域。
Third-party clusterware management solutions are not supported. In addition, Automatic Storage Management (ASM) must be used to manage all database-related files, including datafiles, online logs, archive logs, control file, spfiles, and the flash recovery area.
不支持第三方卷管理器和文件系统。
Third-party volume managers and file systems are not supported for this purpose.

对。最佳实践是，在Oracle RAC数据库上运行的分布式事务的所有紧密耦合分支必须在同一实例上运行。
YES. Best practices is to have all tightly coupled branches of a distributed transaction running on an Oracle RAC database must run on the same instance.
在事务之间和服务之间，事务可以跨所有数据库实例进行负载平衡。
Between transactions and between services, transactions can be load balanced across all of the database instances.
在事务之间和服务之间，事务可以跨所有数据库实例进行负载平衡。
Prior to Oracle RAC 11g, you must use services to manage DTP environments.
通过定义服务的DTP属性，可以保证该服务在Oracle RAC数据库中一次在一个实例上运行。
By defining the DTP property of a service, the service is guaranteed to run on one instance at a time in an Oracle RAC database.
通过DTP服务执行的所有全局分布式事务都确保其紧密耦合的分支在单个Oracle RAC实例上运行。
All global distributed transactions performed through the DTP service are ensured to have their tightly-coupled branches running on a single Oracle RAC instance.
Oracle RAC 11g为Oracle RAC环境中的XA全局事务提供透明支持，您无需使用DTP服务。
Oracle RAC 11g provides transparent support for XA global transactions in an Oracle RAC environment and you do not need to use DTP services.

是的，更改UID/GID会影响Oracle Clusterware，因此不应这样做。
Yes, Changing UID/GID does affect Oracle Clusterware and should not be done.
在Oracle Clusterware home中和Oracle Clusterware home之外有许多文件，它们被分配到适当的组中以实现安全性和适当的访问。
There are a lot of files in the Oracle Clusterware home and outside of the Oracle Clusterware home that are chgrp'ed to the appropriate groups for security and appropriate access.
文件系统记录uid（而不是用户名），因此如果您交换名称，那么现在文件属于错误的组。
The filesystem records the uid (not the username), and so if you exchange the names, now the files are owned by the wrong group.

对于iSCSI，Oracle声明，作为块协议，此技术不需要对单实例数据库进行验证。
For iSCSI, Oracle has made the statement that, as a block protocol, this technology does not require validation for single instance database.
有许多早期采用iSCSI的客户运行Oracle9i和Oracle Database 10g。
There are many early adopter customers of iSCSI running Oracle9i and Oracle Database 10g.
至于Oracle RAC，Oracle已选择为10g平台验证iSCSI技术（而不是每个供应商的目标）-这已在Linux和Windows中完成。
As for Oracle RAC, Oracle has chosen to validate the iSCSI technology (not each vendor's targets) for the 10g platforms - this has been completed for Linux and Windows.
对于Windows，我们测试了多达4个节点—主机和存储设备支持的任何Windows iSCSI产品都受Oracle支持。
For Windows we have tested up to 4 nodes - Any Windows iSCSI products that are supported by the host and storage device are supported by Oracle.
我们不支持用于Windows的NAS设备，但是一些NAS设备（如NetApp）也可以将自己显示为iSCSI设备。
We don't support NAS devices for Windows, however some NAS devices (eg NetApp) can also present themselves as iSCSI devices.
如果是这种情况，则只要iSCSI设备供应商支持Windows作为启动器操作系统，客户就可以将此iSCSI设备与Windows一起使用。供应商特定信息将不会发布在证明上。
If this is the case then a customer can use this iSCSI device with Windows as long as the iSCSI device vendor supports Windows as an initiator OS. No vendor-specific information will be posted on Certify.

是，-客户可能希望为其SE RAC数据库创建备用数据库，因此可以将归档日志另外放置在ASM之外。
Yes, - customers may want to create a standby database for their SE RAC database so placing the archive logs additionally outside ASM is OK.

对于选择在其数据库服务器上运行防病毒（AV）软件的客户，他们应该知道，AV软件的本质是，随着大多数AV软件检查磁盘写入/读取，磁盘IO带宽略有减少。
For customers who choose to run anti-virus (AV) software on their database servers, they should be aware that the nature of AV software is that disk IO bandwidth is reduced slightly as most AV software checks disk writes/reads.
Also, as the AV software runs, it will use CPU cycles that would normally be consumed by other server processes (e.g your database instance).
因此，当不使用AV软件时，数据库将具有更快的性能。
As such, databases will have faster performance when not using AV software.
由于已知某些AV软件在扫描时会锁定文件，因此最好从常规AV扫描中排除Oracle数据文件/控制文件/日志文件
As some AV software is known to lock the files whilst it scans then it is a good idea to exclude the Oracle Datafiles/controlfiles/logfiles from a regular AV scan

不支持，rconfig只支持ASM和共享文件系统。
No. rconfig supports ASM and shared file system only.

有关详细的支持矩阵，请参见文件337737.1。基本上，Clusterware版本必须等于或高于ASM或RAC数据库版本。
See Document 337737.1 for a detailed support matrix. Basically the Clusterware version must be equal to or higher than the ASM or RAC Database version.
注意：对于Oracle Database 11g Release 2，您必须同时将Oracle Clusterware和ASM升级到11g Release 2。
Note: With Oracle Database 11g Release 2, You must upgrade Oracle Clusterware and ASM to 11g Release 2 at the same time.

按照有关删除节点的文档进行操作，但您可以跳过节点删除文档中需要在要删除的节点上运行的所有步骤，如步骤4、6和7（请参阅《Oracle RAC管理和部署指南》第10章）。
Follow the documentation for removing a node but you can skip all the steps in the node-removal doc that need to be run on the node being removed, like steps 4, 6 and 7 (See Chapter 10 of Oracle RAC Admin and Deployment Guide).
请确保使用srvctl和侦听器资源删除故障节点上配置的所有数据库实例，否则rootdeltenode.sh在删除nodeapps时会遇到问题。
Make sure that you remove any database instances that were configured on the failed node with srvctl, and listener resources also, otherwise rootdeltenode.sh will have trouble removing the nodeapps.
仅仅运行rootdeletenode.sh是不够的，因为您还需要更新安装程序清单，否则您将无法使用addNode.sh添加回节点。
Just running rootdeletenode.sh isn't really enough, because you need to update the installer inventory as well, otherwise you won't be able to add back the node using addNode.sh.
如果不删除实例和侦听器，则再次添加节点和实例时也会遇到问题。
And if you don't remove the instances and listeners you'll also have problems adding the node and instance back again.

是，-客户可能希望将其数据库备份到脱机存储，因此也支持此操作。
Yes, - customers might want to backup their database to offline storage so this is also supported.

1.确认两端所有接口上的所有互连链路的全双工设置正确。不要依赖自动协商。
1. Confirm that full duplex is set correctly for all interconnect links on all interfaces on both ends. Do not rely on auto negotiation.

2.ifconfig-a将指示冲突/错误/溢出和丢弃的数据包
2. ifconfig -a will give you an indication of collisions/errors/overuns and dropped packets

3.netstat-s将为您提供IP和UDP接收数据包丢弃、碎片和重组错误的列表。
3. netstat -s will give you a listing of receive packet discards, fragmentation and reassembly errors for IP and UDP.

4.正确设置udp缓冲区
4. Set the udp buffers correctly

5.检查您的布线
5. Check your cabling
注意：如果您发现RAC存在问题，RAC将使用UDP作为协议。Oracle Clusterware使用TCP/IP。
Note: If you are seeing issues with RAC, RAC uses UDP as the protocol. Oracle Clusterware uses TCP/IP.
查看说明<>了解有关网络问题的更多详细信息
Review Note <> for more details on Network issues

您至少需要2个NIC：外部（公共）、互连（专用）。
At minimum you need 2 Nics: external (public), interconnect (private).
当Oracle RAC的存储由基于以太网的网络（如NAS/nfs或iSCSI）提供时，您将需要第三个I/O接口，因此至少需要3个。
When storage for Oracle RAC is provided by Ethernet based networks (e.g. NAS/nfs or iSCSI), you will need a third interface for I/O so a minimum of 3.
任何其他因素都会导致负载下的性能和稳定性问题。
Anything else will cause performance and stability problems under load.
从HA的角度来看，您希望这些是冗余的，因此总共需要6个。
From an HA perspective, you want these to be redundant, thus needing a total of 6.

Oracle RAC和Oracle Clusterware部署最佳做法建议将互连部署在独立、物理上独立的专用交换机上。
Oracle RAC and Oracle Clusterware deployment best practices recommend that the interconnect be deployed on a stand-alone, physically separate, dedicated switch.
但是，许多客户已将这些独立交换机整合到更大的托管交换机中。
Many customers, however, have consolidated these stand-alone switches into larger managed switches.
这种整合的一个结果是将IP网络合并到一个由VLAN分割的共享交换机上。
A consequence of this consolidation is a merging of IP networks on a single shared switch, segmented by VLANs.
此类部署有一些相关的注意事项。
There are caveats associated with such deployments.
Oracle RAC缓存融合协议比非RAC Oracle数据库更严格地运行IP网络。
The Oracle RAC cache fusion protocol exercises the IP network more rigorously than non-RAC Oracle databases.
Oracle RAC/Oracle Clusterware互连IP网络的延迟和带宽要求以及可用性要求更符合高性能计算。
The latency and bandwidth requirements as well as availability requirements of the Oracle RAC  Oracle Clusterware interconnect IP network are more in-line with high performance computing.
在由VLAN分割的共享交换机上部署Oracle RAC/Oracle Clusterware互连可能会使互连链路在更大的IP网络拓扑中面临拥塞和不稳定性。
Deploying the Oracle RAC  Oracle Clusterware interconnect on a shared switch, segmented by a VLAN may expose the interconnect links to congestion and instability in the larger IP network topology.
如果在VLAN上部署互连，VLAN到不可路由子网的映射应为1:1，并且VLAN不应跨越多个VLAN（标记）或多个交换机。
If deploying the interconnect on a VLAN, there should be a 1:1 mapping of the VLAN to a non-routable subnet and the VLAN should not span multiple VLANs (tagged) or multiple switches.
此环境中的部署问题包括较大的IP网络拓扑发生变化时的生成树循环、可能导致数据包泛滥的不对称路由，以及缺乏对VLAN/端口的细粒度监控。
Deployment concerns in this environment include Spanning Tree loops when the larger IP network topology changes, Asymmetrical routing that may cause packet flooding, and lack of fine grained monitoring of the VLAN/port.

安装运行正常，没有问题。<< Message: Result: User equivalence check failed for user "oracle". >>
The install ran fine without issue. << Message: Result: User equivalence check failed for user "oracle". >>
Cluvfy和OUI试图在Solaris上的/usr/local/bin处找到SSH。解决方法是创建从/usr/bin/ssh到/usr/local/bin的软链接。
Cluvfy and the OUI tries to find SSH on Solaris at usr/local/bin. Workaround is to create a softlink from usr/bin/ssh to usr/local/bin.
Note:
安装（即使用OUI）和修补需要用户等效性。DBCA、NETCA和DBControl也要求用户等效。
User equivalence is required for installations (IE using OUI) and patching. DBCA, NETCA, and DBControl also require user equivalence.

这是与现有客户机的向后兼容性：考虑10G到10G服务器升级。
This is for backward compatibility with existing clients: consider pre-10g to 10g server upgrade.
如果我们将升级的侦听器设置为只在VIP上侦听，则未升级的客户端将无法再访问此侦听器。
If we made upgraded listener to only listen on VIP, then clients that didn't upgrade will not be able to reach this listener anymore.

有关使用RAC 10g支持SFRAC和Veritas代理的详细信息，请参阅文档397460.1 Oracle在Unix上使用Symantec SFRAC支持Oracle RAC 10g（也适用于Oracle RAC 11g）的策略，以及文档332257.1使用Oracle Clusterware和供应商Clusterware常见问题解答
For details on the support of SFRAC and Veritas Agents with RAC 10g, please see Document 397460.1 Oracle's Policy for Supporting Oracle RAC 10g (applies to Oracle RAC 11g too) with Symantec SFRAC on Unix and Document 332257.1 Using Oracle Clusterware with Vendor Clusterware FAQ

是的，您不需要为Oracle设置LD_LIBRARY_路径。
Yes You do not need to set LD_LIBRARY_PATH for Oracle.

对,Oracle Clusterware应始终在最高级别运行。
Yes. The Oracle Clusterware should always run at the highest level.
使用Oracle Clusterware 11g，您可以同时运行Oracle RAC 10g和Oracle RAC 11g数据库。
With Oracle Clusterware 11g, you can run both Oracle RAC 10g and Oracle RAC 11g databases.
如果将ASM用于存储，则可以使用Oracle Database 10g ASM或Oracle Database 11g ASM。但是，要获得11g功能，必须运行Oracle Database 11g ASM。
If you are using ASM for storage, you can use either Oracle Database 10g ASM or Oracle Database 11g ASM however to get the 11g features, you must be running Oracle Database 11g ASM.
建议使用Oracle Database 11g ASM。
It is recommended to use Oracle Database 11g ASM.
Note:
升级到11g版本2时，必须将Oracle Clusterware和Automatic Storage Management升级到11g版本2。这将支持Oracle Database 10g和Oracle Database 11g（RAC和单实例）。
When you upgrade to 11g Release 2, you must upgrade both Oracle Clusterware and Automatic Storage Management to 11g Release 2. This will support Oracle Database 10g and Oracle Database 11g (both RAC and single instance).
是的，您也可以在群集中运行Oracle 9i RAC。9i RAC要求除运行Oracle clusterware 11g外，还运行经Oracle 9i RAC认证的clusterware。
Yes, you can run Oracle 9i RAC in the cluster as well. 9i RAC requires the clusterware that is certified with Oracle 9i RAC to be running in addition to Oracle Clusterware 11g.

Oracle数据库（单实例和RAC）支持Sun逻辑域（LDOM）。
Sun Logical Domains (ldoms) are supported with Oracle Database (both single instance and RAC).
检查certify以获取最新版本的特定信息。
Check certify for the latest version specific information.

一般原则是，RAC基本上不需要不同的设计和编码实践，但执行或设计中的应用程序缺陷对RAC的影响更大。
The general principals are that fundamentally no different design and coding practices are required for RAC however application flaws in execution or design have a higher impact in RAC.
RAC中的性能和可伸缩性将对糟糕的计划或糟糕的模式设计更加敏感。序列化争用会降低应用程序的可伸缩性。
The performance and scalability in RAC will be more sensitive to bad plans or bad schema design. Serializing contention makes applications less scalable.
如果您的客户使用标准SQL和模式调优，则可以解决80%以上的性能问题
If your customer uses standard SQL and schema tuning, it solves > 80% of performance problems

他们应该寻找的一些可伸缩性陷阱是：
Some of the scalability pitfalls they should look for are:

*在一小组数据/索引块上序列化争用
* Serializing contention on a small set of data/index blocks
-->单调递增键
--> monotonically increasing key
-->频繁更新小型缓存表
--> frequent updates of small cached tables
-->没有自动段空间管理（ASSM）或自由列表组（FLG）的段
--> segment without automatic segment space management (ASSM) or Free List Group (FLG)

*全表扫描
*  Full table scans
-->在11g中优化完整扫描可以节省CPU和延迟
--> Optimization for full scans in 11g can save CPU and latency

*游标的频繁失效和解析
* Frequent invalidation and parsing of cursors
-->需要数据字典查找和同步
--> Requires data dictionary lookups and synchronizations

*并发DDL（例如 truncate/drop）

* Concurrent DDL ( e.g. truncate/drop )

Look for:
*具有正确增长特征的指数
* Indexes with right-growing characteristics
-->使用反向键索引
--> Use reverse key indexes
-->消除不需要的索引
--> Eliminate indexes which are not needed

*频繁更新和读取“小”表
* Frequent updated and reads of “small” tables
-->“小”=适合单个缓冲区缓存
--> “small”=fits into a single buffer cache
-->使用稀疏块（PCTFREE 99）减少序列化
--> Use Sparse blocks ( PCTFREE 99 ) to reduce serialization

*扫描大量数据的SQL
* SQL which scans large amount of data
-->并行化时可能更高效
--> Perhaps more efficient when parallelized
-->对于全局缓存，不需要进行全局同步的CPU读取
--> Direct reads do not need to be globally synchronized ( hence less CPU for global cache )

Oracle Clusterware和Oracle RAC都不需要使用SCSI-3持久组保留（PGR）。
Oracle Clusterware and Oracle RAC do not require neither use SCSI-3 Persistent Group Reservation (PGR).
在本机Oracle RAC堆栈（没有第三方或供应商群集，也没有Oracle Solaris群集）中，Oracle不需要SCSI-3 PGR，应在存储上禁用（对于堆栈中使用的磁盘/LUN）。
In a native Oracle RAC Stack (no third party or vendor cluster, neither Oracle Solaris Cluster) SCSI-3 PGR is not required by Oracle and should be disabled on the storage (for disks  LUNs used in the stack).
当使用第三方或供应商群集解决方案（如Symantec Veritas SFRAC）时，第三方群集解决方案可能要求在存储上启用SCSI-3 PGR，因为这些解决方案将使用SCSI-3 PGR作为其IO防护过程的一部分。通常，SCSI-3 PGR在阵列级别启用；
When using a third party or vendor cluster solution such as Symantec Veritas SFRAC, the third part cluster solution may require that SCSI-3 PGR is enabled on the storage, as those solutions will use SCSI-3 PGR as part of their IO fencing procedures. In general, SCSI-3 PGR is enabled at the array level;
例如，在EMC超级卷级别。
for example on EMC hypervolume level.

在节点1上重新设置密钥后，所有其他节点上的“alter system set wallet close”（更改系统设置钱包关闭）使用新的主密钥将钱包复制到所有其他节点上，“alter system set wallet open”（更改系统设置钱包打开）由“密码”标识；
After a re-key on node one, 'alter system set wallet close' on all other nodes, copy the wallet with the new master key to all other nodes, 'alter system set wallet open identified by "password";
在所有其他节点上，将（模糊化的）主密钥加载到节点的SGA中。
on all other nodes to load the (obfuscated) master key into node's SGA.

Yes 是的
但是，在尝试使用早期版本的Oracle数据库（即不是11.2）创建数据库之前，需要“锁定”群集中的节点。
however you need to "pin" the nodes in the cluster before trying to create a database using an earlier version of Oracle Database (IE not 11.2).
锁定节点的命令是crsctl pin css -n nodename。
The command to pin a node is crsctl pin css -n nodename.
您还应该为未发布的Bug 8288940应用补丁，以使DBCA在11.2集群中工作。
You should also apply the patch for unpublished Bug 8288940 to make DBCA work in an 11.2 cluster.

您需要将<Bug 8288940>的修补程序应用到您的数据库home，以便它能够识别从新的网格基础设施home运行的ASM。
You will need to apply the patch for <Bug 8288940> to your database home in order for it to recognize ASM running from the new grid infrastructure home.
还要确保已“固定”节点。
Also make sure you have "pinned" the nodes.
crsctl pin css -n nodename

从Oracle Database 10g开始，已购买Standard Edition的客户可以在Standard Edition（SE）的限制范围内使用Oracle RAC选项。
As of Oracle Database 10g, a customer who has purchased Standard Edition is allowed to use the Oracle RAC option within the limitations of Standard Edition(SE).
有关许可限制，请阅读Oracle数据库许可证文档。
For licensing restrictions you should read the Oracle Database License Doc.
在较高级别上，这意味着集群中最多可以有4个套接字，所有数据库文件都必须使用ASM。
从Oracle Database 11g第2版开始，ASM包括ACFS（群集文件系统）。
At a high level this means that you can have a max of 4 sockets in the cluster, you must use ASM for all database files.
As of Oracle Database 11g Release 2, ASM includes ACFS (a cluster file system).
ASM群集文件系统（ACFS）或本地操作系统文件系统必须用于存储所有非数据库文件，包括Oracle Home、应用程序和系统文件以及用户文件
ASM Cluster File System (ACFS) or a local OS file system must be used to store all non-database files including Oracle Home, Application and system files, and User files

NOTE:
不支持第三方群集软件和群集文件系统（ASM除外）。这包括OCFS和OCFS2。
3rd party clusterware and clustered file systems(other than ASM) are not supported. This includes OCFS and OCFS2.
以下是价目表中相应脚注中的文本（截至2010年1月，请查看价目表是否有任何变更）：
Here is the text from the appropriate footnote in the Price List (as of Jan2010, please check price list for any changes):
Oracle数据库标准版只能在最大容量为4个套接字的服务器上获得许可。
Oracle Database Standard Edition can only be licensed on servers that have a maximum capacity of 4 sockets.
如果由命名用户Plus授权，则至少有5个命名用户Plus许可证。
If licensing by Named User Plus, the minimum is 5 Named User Plus licenses.
Oracle Database Standard Edition与Oracle Real Application Clusters一起使用时，只能在一个服务器群集上获得许可，该群集最多支持4个套接字的最大总容量。
Oracle Database Standard Edition,when used with Oracle Real Application Clusters, may only be licensed on a single cluster of servers supporting up to a total maximum capacity of 4 sockets.
NOTE:
这意味着即使套接字为空，服务器容量也必须满足限制，因为它们计入容量。
This means that the server capacity must meet the restriction even if the sockets are empty, since they count towards capacity.

对,有关详细信息，请参阅文件341788.1集群互连和巨帧
Yes. For details see Document 341788.1 Cluster Interconnect and Jumbo Frames

单客户端访问名（SCAN）是一个单一名称，它允许客户端连接连接到Oracle群集中的任何数据库，而不依赖于该数据库（或服务）当前运行的群集中的哪个节点。
Single Client Access Name (SCAN) is a single name that allows client connections to connect to any database in an Oracle cluster independently of which node in the cluster the database (or service) is currently running.
The SCAN should be used in all client connection strings and does not change when you add/remove nodes from the cluster.
SCAN允许客户端使用EZConnect或此JDBC URL。
SCAN allows clients to use EZConnect or the this JDBC URL.
sqlplus system/<PASSWORD>@<SCANHOST>:<PORT>/<SERVICENAME>
jdbc:oracle:thin:@<SCANHOST>:<PORT>/<SERVICENAME>
SCAN定义为单个名称，解析为群集GNS或公司DNS中的3个IP地址。
SCAN is defined as a single name resolving to 3 IP addresses in either the cluster's GNS or your corporate DNS.
** Click here for more details on SCAN.

对于集群同步服务（CSS），可以通过搜索ORACLE_HOME/log/nodename/cssd/ocssd.log找到主服务器，其中ORACLE_HOME设置为网格基础设施主服务器
For the cluster synchronization service (CSS), the master can be found by searching ORACLE_HOME/log/nodename/cssd/ocssd.log where ORACLE_HOME is set to the Grid Infrastructure Home
对于Oracle RAC排队资源的主机，可以从v$ges_resource中进行选择。应该有一个主节点列。
For master of a enqueue resource with Oracle RAC, you can select from v$ges_resource. There should be a master_node column.

可以，您可以拥有多个网络。但是，使用Oracle RAC 10g和Oracle RAC 11g，群集只能使用VIP管理单个公共网络，并且数据库只能跨单个网络进行负载平衡。
Yes, you can have multiple networks however with Oracle RAC 10g and Oracle RAC 11g, the cluster can only manage a single public network with a VIP and the database can only load balance across a single network.
FAN只能在Oracle VIP的公共网络上工作。
FAN will only work on the public network with the Oracle VIPs.
Oracle RAC 11g版本2支持多个公用网络。您必须设置新的init.ora参数LISTENER_NETWORKS，以便用户在其网络中实现负载平衡。
Oracle RAC 11g Release 2 supports multiple public networks. You must set the new init.ora parameter LISTENER_NETWORKS so users are load balanced across their network.
服务与网络相连，因此与网络1连接的用户将使用与网络2不同的服务。每个网络都有自己的VIP。
Services are tied to networks so users connecting with network 1 will use a different service than network 2. Each network will have its own VIP.
有关更多信息，请参阅Oracle文档中的srvctl add reference 。
For more information refer to the srvctl add reference in the Oracle documentation.

使用Oracle Database 11g Release 2，Oracle Clusterware和自动存储管理（ASM）的二进制文件分布在一组称为网格基础结构的二进制文件中。
With Oracle Database 11g Release 2, the binaries for Oracle Clusterware and Automatic Storage Management (ASM) are distributed in a single set of binaries called the Grid infrastructure.
要安装网格基础设施，请转到11g Release 2介质上的网格目录并运行Oracle Universal Installer）。
To install grid infrastructure, go to the grid directory on your 11g Release 2 media and run the Oracle Universal Installer).
为集群选择网格基础结构。
Choose the Grid Infrastructure for a Cluster.
如果要在独立服务器上为Oracle数据库的单个实例安装ASM，请为独立服务器选择网格基础结构。此安装包括Oracle重新启动。
If you want to install ASM for a single instance of Oracle Database on a Standalone Server, choose the Grid Infrastructure for a Standalone Server. This installation includes Oracle Restart.

YES. 是的
但是，Oracle Clusterware（CRS）不支持Oracle 9i RAC数据库，因此您必须保留当前配置。
However Oracle Clusterware (CRS) will not support a Oracle 9i RAC database so you will have to leave the current configuration in place.
您可以将Oracle Clusterware和Oracle RAC 10g安装到不同Oracle home中的同一群集中。
You can install Oracle Clusterware and Oracle RAC 10g into the same cluster on different Oracle homes.
在Windows和Linux上，必须为9i数据库运行9i群集管理器，为10g数据库运行Oracle Clusterware。
On Windows and Linux, you must run the 9i Cluster Manager for the 9i Database and the Oracle Clusterware for the 10g Database.
安装Oracle Clusterware时，9i srvconfig文件将转换为OCR。Oracle 9i RAC和Oracle RAC 10g都将使用OCR。
When you install Oracle Clusterware, your 9i srvconfig file will be converted to the OCR. Both Oracle 9i RAC and Oracle RAC 10g will use the OCR.  
安装Oracle Clusterware后，请勿重新启动9i gsd。
Do not restart the 9i gsd after you have installed Oracle Clusterware.
默认情况下， Oracle Clusterware 11g Release 2将禁用GSD资源。
With Oracle Clusterware 11g Release 2, the GSD resource will be disabled by default.
只有在群集中运行Oracle 9i RAC时，才需要启用此资源。
You only need to enable this resource if you are running Oracle 9i RAC in the cluster.
请记住检查并确认哪些供应商clusterware可以与Oracle clusterware一起运行的详细信息。
Remember to check certify for details of what vendor clusterware can be run with Oracle Clusterware.
例如，在Solaris上，您的Oracle 9i RAC将使用Sun Cluster。
For example on Solaris, your Oracle 9i RAC will be using Sun Cluster.
您可以在运行Sun cluster和Oracle 9i RAC的同一群集中安装Oracle Clusterware和Oracle RAC 10g。
You can install Oracle Clusterware and Oracle RAC 10g in the same cluster that is running Sun Cluster and Oracle 9i RAC.

您必须在需要停止Oracle实例的节点上停止Oracle Clusterware堆栈。
You will have to stop the Oracle Clusterware stack on the node on which you need to stop the Oracle ASMinstance.
为此，请使用“crsctl stop cluster-n node_name”或“crsctl stop crs”。
Either use "crsctl stop cluster -n node_name" or "crsctl stop crs" for this purpose.

虽然支持全局容器已经有一段时间了，但在本地容器扩展到允许直接修改硬件之后，Oracle最近增加了对本地容器的支持。
While Global containers have been supported for a while, Oracle added support for local containers recently after the local containers were extended to allow direct hardware modification.
取消此限制允许Oracle Clusterware直接在硬件资源（如Oracle VIP的网络）上运行，从而使Oracle RAC能够在本地容器中运行。
Lifting this restriction allow Oracle Clusterware to operate on hardware resources such as the network for the Oracle VIP directly, enabling Oracle RAC to run in local containers.
More information about Solaris container support can be found in Oracle Certify.

块设备仅在Linux上受支持。
Block Devices are only supported on Linux.
在其他Unix平台上，directIO语义不适用于块设备（或者说没有实现）。
On other Unix platforms, the directIO semantics are not applicable (or rather not implemented) for block devices.


Note:
Oracle Database 12c计划取消对直接使用原始或块设备的支持。
The de-support for direct use of raw or block devices is scheduled for Oracle Database 12c.
Oracle Database 10g Oracle Universal Installer不支持块设备；Oracle Clusterware和ASM都可以。
The Oracle Database 10g Oracle Universal Installer does not support block devices; Oracle Clusterware and ASM do.
在Oracle RAC 11g第2版中，Oracle Universal Installer和配置助手不再支持原始或块设备。
With Oracle RAC 11g Release 2, the Oracle Universal Installer and the Configuration Assistants do not support raw or block devices anymore.
命令行界面仍然支持原始设备和块设备，因此可以在初始安装后移动Oracle Clusterware文件。
The Command Line Interfaces still support raw and block devices and hence the Oracle Clusterware files can be moved after the initial installation. 


Note:
Oracle database 12c不支持直接使用原始或块设备（用于数据库文件或Clusterware文件）。
Direct use of raw or block devices (for database files or Clusterware files) will be de-supported with Oracle Database 12c.
仍支持在Oracle ASM下使用原始或块设备。
Using raw or block devices under Oracle ASM will remain supported.

从10.2开始，默认情况下LMS进程应该在RT中运行，所以没有必要重新启动它们，否则会弄乱它们。
LMS processes should be running in RT by default since 10.2, so there's NO need to renice them, or otherwise mess with them.
Check with ps -efl:
0 S oracle 31191 1 0 75 0 - 270857 - 10:01 ? 00:00:00 ora_lmon_appsu01
0 S oracle 31193 1 5 75 0 - 271403 - 10:01 ? 00:00:07 ora_lmd0_appsu01
0 S oracle 31195 1 0 58 - - 271396 - 10:01 ? 00:00:00 ora_lms0_appsu01
0 S oracle 31199 1 0 58 - - 271396 - 10:01 ? 00:00:00 ora_lms1_appsu01


7th column, if it is 75 or 76 then this is Time Share, 58 is Real Time.


You can also use chrt to check:
LMS (Real Time):
$ chrt -p 31199
pid 31199's current scheduling policy: SCHED_RR
pid 31199's current scheduling priority: 1


LMD (Time Share)


$ chrt -p 31193
pid 31193's current scheduling policy: SCHED_OTHER
pid 31193's current scheduling priority: 0

58.I get the following error starting my Oracle RAC database, what do I do?
这仅仅意味着您既没有为数据库设置cluster_interconnects参数，也没有在OCR中找到任何群集互连规范，因此数据库会随机选择专用互连，并因此发出警告。
This simply means that you neither have a cluster_interconnects parameter set for the database, nor was there any cluster interconnect specification found in the OCR, so that the private interconnect is picked at random by the database, and hence the warning.
您可以在数据库的初始化文件（spfile/pfile）中设置cluster_interconnects参数以指定专用互连IP，也可以使用“oifcfg setif”（键入“oifcfg”以获取帮助）将的特定网络分类为群集互连网络。
You can either set the cluster_interconnects parameter in the initialization file (spfile / pfile) of the datbase to specify a private interconnect IP, OR you can use "oifcfg setif" (type "oifcfg" for help) to classify a certain network for as the cluster interconnect network.


$ oifcfg getif
eth0 <IP> global public
eth2 <IP> global cluster_interconnect
请注意，oifcfg允许您指定“本地”和“全局”设置。
Note that oifcfg enables you to specify "local" as well as "global" settings.
With Oracle Clusterware 10g Rel. 1 and Rel. 2 as well as Oracle Clusterware 11g Rel. 1, it is, however, only supported to use global settings.
如果要用于互连的硬件（网络接口）在集群中的所有节点上都不相同，则需要在硬件/OS级别相应地更改配置。
If the hardware (network interface) meant to be used for the interconnect is not the same on all nodes in the cluster, the configuration needs to be changed on the hardware / OS level accordingly.