Archive for 九月, 2009

hacmp 5.4.1 10gr2

星期四, 九月 24th, 2009

在AIX系统上安装ORACLE 10GR2 RAC时,如果HACMP版本是5.4.1的,那么在安装CRS时,将无法看到节点信息,如下图
aix
这是ORACLE的一个BUG,相关PATCH文档号:Patch 6718715
Oracle 10gR2 patchset 10.2.0.3, CRS bundled Patch 6160398 is required. In addition, rootpre.sh Patch 6718715 is required when using HACMP 5.4.1 with a fresh install of Oracle RAC clusterware or when upgrading from Oracle 10gR1 to Oracle 10gR2. This patch should be installed on all nodes before installing Oracle 10.2.0.1 software. Be sure to download the 10gR2 version of Patch 6718715.

建议在AIX 下使用HACMP时,参照文档:404474.1,可以少走一些弯路

RAC VIP ORA-12545

星期天, 九月 20th, 2009
最近在做一个RAC 实施时,发现客户应用连接RAC时,老是报ora-12545 因目标主机或对象不存在 连接失败,之前应用,因为我们使用的都是预连接,而且用的实际地址,所以没怎么遇到过,这次用的VIP,确总是报错,最后在METALINK364855.1
找到解决方法:
Symptoms
When we try to connect to a RAC service name we sometimes get redirected by the first node's listener to the public address/hostname of the second node instead of its VIP address. An ORA-12545 error may be generated if that public hostname is not configured in DNS.
 
We were expecting the connection to eventually be redirected to the VIP of the other node.
 
 
Cause
The Database on one RAC node remote registers with the wrong local IP address to the listener on the other RAC node (e.g. the public IP address instead of the wanted VIP address).
 
The PMON process handles database registration to the local and remote listeners. For remote listeners registration PMON will have to find out what is the IP address of the local system in order to present it to the remote listener as database contact address.
 
In the default Oracle configuration, for hosts which have more than one IP address configured on the network interfaces,  it is undefined which IP address will be selected for remote registration.
 
 
Solution
Modify the local_listener database parameter to point to the local VIP address. For the parameter value use either an alias name which contains in the DESCRIPTION field only the VIP address or use an explicit connection statement like the following:
alter system set LOCAL_LISTENER="(ADDRESS=(PROTOCOL=TCP)(HOST=<VIP_address>)(PORT=1521))" scope=both sid=
'instance_name';
记得一定要是双引号
 
 
Where "instance_name" is the unique instance name.   Issue this statement for all instances in the cluster. The LOCAL_LISTENER database parameter will give PMON a hint in respect of which IP address it should use for remote registration with other nodes
' listener(s).