-The End-

一年了，文章数目虽然不多，质量也不咋地，但“看”和“看了再写”出自己的想法是完全不一样的感受，太多的东西可能自己很清楚很明白，但要写出来让别人一看就懂就难了，写博对我来说就起一个记录我学习和生活的过程，没想过PV，没想过订阅数，没有想过人气，只是经过一段时间之后再回过头来看这些，我会想，为什么当初我是那样考虑的，为什么当初我会那样做，这对我非常重要，这里就像一面镜子，我需要时刻参照、反省、改善，我认为这也应当算作财富吧。Blog空间明天就到期了，为了继续储蓄这笔财富，所以今天全额续费了，i hope just beginning！

-The End-

更多图片请稳步这里。
-The End-

遵义市位于贵州省北部，属云贵高原向四川盆地湖南丘陵地带过渡的东斜坡北段，处于省会贵阳市和重庆市之间，西北部与四川接旅游地图——点击可以放大壤，以北背靠重庆市，以南面对贵阳。是贵州的第二大城市，也是贵州北线旅游的中心，是国务院首批公布的全国24个历史文化名城之一。

遵义历史悠久，文化源远流长，到了近代，更以著名的遵义会议，奠定了它在中国革命历史上的重要地位。

遵义山川秀丽，风光独特，尤以山、水、林、洞为主要特色。这里有一个国家级风景名胜区和四个省级风景名胜区，近千处文物点。如被称为“西南古代雕刻艺术宝库”的杨粲墓、被誉为“生物活化石”的国家级桫椤自然保护区、“神州又一奇观”赤水十丈洞瀑布等，真可谓处处有佳境，步步有名胜。

此时，很想念家的温馨，想念LP和二个月的宝宝，希望一切顺利能早点回家。今晚又是一个不眠夜。

-The End-

[ID 403743.1]

Applies to:

Oracle Server – Enterprise Edition – Version: 10.2.0.1 to 11.1.0.7

This problem can occur on any platform.

Symptoms

This example is based on SUN Solaris platform, with IPMP configured for the public network. In this case, VIP failover takes almost 4 minutes to complete when both network cables of the public network are pulled from one node.

crsd.log shows:

2006-12-07 13:14:05.401: [ CRSAPP][4588] CheckResource error for ora.node1.vip error code = 1

2006-12-07 13:14:05.408: [ CRSRES][4588] In stateChanged, ora.node1.vip target is ONLINE

2006-12-07 13:14:05.409: [ CRSRES][4588] ora.node1.vip on node1 went OFFLINE unexpectedly

<<< detect network cable failure and VIP OFFLINE immediately

2006-12-07 13:14:05.410: [ CRSRES][4588] StopResource: setting CLI values

2006-12-07 13:14:05.420: [ CRSRES][4588] Attempting to stop `ora.node1.vip` on member `node1`

2006-12-07 13:14:06.651: [ CRSRES][4588] Stop of `ora.node1.vip` on member `node1` succeeded.

2006-12-07 13:14:06.652: [ CRSRES][4588] ora.node1.vip RESTART_COUNT=0 RESTART_ATTEMPTS=0

2006-12-07 13:14:06.667: [ CRSRES][4588] ora.node1.vip failed on node1 relocating.

2006-12-07 13:14:06.758: [ CRSRES][4588] StopResource: setting CLI values

2006-12-07 13:14:06.766: [ CRSRES][4588] Attempting to stop `ora.node1.LISTENER_NODE1.lsnr` on member `node1`

2006-12-07 13:17:41.399: [ CRSRES][4588] Stop of `ora.node1.LISTENER_NODE1.lsnr` on member `node1` succeeded.

<<< takes 3.5 minutes to stop listener

2006-12-07 13:17:41.402: Attempting to stop `ora.node1.ASM1.asm` on member `node1`

<<< stop dependant inst and ASM

2006-12-07 13:17:55.610: [ CRSRES][4588] Stop of `ora.node1.ASM1.asm` on member `node1` succeeded.

2006-12-07 13:17:55.661: [ CRSRES][4588] Attempting to start `ora.node1.vip` on member `node2`

2006-12-07 13:18:00.260: [ CRSRES][4588] Start of `ora.node1.vip` on member `node2` succeeded.

<<< now VIP failover complete after almost 4 mins

ora.node1.LISTENER_NODE1.lsnr.log shows:

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=node1vip)(PORT=1521)(IP=FIRST)))

TNS-12535: TNS:operation timed

2006-12-07 13:17:41.329: [ RACG][1] [23916][1][ora.node1.LISTENER_NODE1.lsnr]: out

TNS-12560: TNS:protocol adapter error

TNS-00505: Operation timed out

Solaris Error: 145: Connection timed out

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.1.10.100)(PORT=1521)(IP=FIRST)))

The command completed successfully

Client connection hang during this failover time.

Changes

This may be a new setup, or a setup that was migrated from an earlier release.

Cause

This problem is caused by the first address in the listener.ora configuration being an address that uses the TCP protocol.

In this circumstance, when a network cable is pulled, “lsnrctl stop” listener has to wait for TCP timeout before it can check next address. On the Solaris platform, TCP timeout is defined by tcp_ip_abort_cinterval with a default value of 180000 (3 minutes).   That is why shutting down listener almost took 3.5 minutes. (TCP timeout on other platforms may vary).  The error message “Solaris Error: 145: Connection timed out” in ora.node1.LISTENER_NODE1.lsnr.log also indicates it is waiting for tcp timeout.

The listener.ora in this scenario is defined as:

LISTENER_NODE1 =
 
(DESCRIPTION_LIST =
 
(DESCRIPTION =
 
(ADDRESS_LIST =
 
(ADDRESS = (PROTOCOL = TCP)(HOST = node1vip)(PORT = 1521)(IP = FIRST))
 
)
 
(ADDRESS_LIST =
 
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.1.10.100)(PORT = 1521)(IP = FIRST))
 
)
 
(ADDRESS_LIST =
 
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC))
 
)
 
)
 
)

Solution

To prevent this, move the IPC address to be the first address for the listener in the listener.ora, eg:

LISTENER_NODE1 =
 
(DESCRIPTION_LIST =
 
(DESCRIPTION =
 
(ADDRESS_LIST =
 
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC))
 
)
 
(ADDRESS_LIST =
 
(ADDRESS = (PROTOCOL = TCP)(HOST = node1vip)(PORT = 1521)(IP = FIRST))
 
)
 
(ADDRESS_LIST =
 
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.1.10.100)(PORT = 1521)(IP = FIRST))
 
)
 
)
 
)

When lsnrctl tries to stop the listener, it will now connect to the IPC address first, which is available during that time. It will not have to wait for tcp timeout.

After the above change, the VIP failover only takes 48 to 50 seconds to complete regardless of the tcp_ip_abort_cinterval setting.

Please note, listener.ora files newly created from 10.2.0.3 to 11.1.0.7 should have the IPC protocol as the first address in listener.ora in most cases.  However, if you have upgraded from a previous release, or manually modified/copied over a listener.ora from a previous install, you may not have the IPC protocol as the first address, regardless of your version. Manual modification is required to move IPC protocol to be the first address to avoid the problem described in this note.

BTW：梦想有多远的blog也有说明。

-The End-

1.09年大部分时间泡在Internet上，正因于此在网络上知道了很多牛人（排名不分先后 ）：eygle、rickyzhu、oracleblog、fenng、ningoo太多了就不依依写了。从这些牛人身上我收获了很多，也得到过很多帮助，这此对他们说声：“谢谢！”（即使他们不知道我）

2.09年俺也开博了，数了数一共73篇文章，虽然2/3写的是一些废话，但我相信只要坚持下去，总会等到有料的那一天。

3.6月份跳到现在的公司，开始大量接触小型机和企业级存储，感谢公司给了我这样的机会。

4.通过了Oracle 9i OCP和IBM 223考试 （记错了，OCP是08年考的）

5.太多牛人写了太多牛书，还只看了其中几本，这点还很需要加强。

6.换了工作之后，公司每周五下午都会去运动锻炼身体，像我们这种工作性质的人太需要锻炼了。

2010年，我不敢奢求太多，仅几点而已：

1.8月15日，静静等待宝宝（小名：果果，取自与老婆爱情的果实之意）呱呱落地来到这个充满爱的世界。

2.Oracle OCP升级考试（有可能的话OCM考试）和IBM 102考试（公司需要）

3.把买的牛人们写的书认真读完，再读一二本非技术类的书充实自己。

4.加强口语学习，争取能开口。

5.多多联系朋友。

6.最后一点，也是最重要的一点：我希望家人、朋友都能平平安安、健健康康、快快乐乐的生活每一天。

-The End-

EnterpriseDB的安装是我见过的RDBMS产品中安装最简单的，简单介绍for linux x86 platform的安装步骤。

1. 获得安装文件
2. # tar -zxvf pgplus-advsvr-linux-x86_830112.tar.gz
3. # setenforce Permissive
4. Graphical Installer:

# ./pgplus-advsvr-linux-x86_830112.bin

Command Line Installer:

# ./pgplus-advsvr-linux-x86_830112.bin -console

输入上面的命令之后剩下的工作就在对话中完成。

默认安装路径如下：

/opt/PostgresPlus/8.3R2AS

/opt/PostgresPlus/8.3R2AS/data

/opt/PostgresPlus/8.3R2AS/data/pg_xlog

5.# setenforce Enforcing

6.配置环境变量：安装完成之后，在每个用户的家目录下会有一个edb_83.env的文本文件，与$EDBHOME/dbserver/scripts/edb_83.env文件一样。

To load the environment for a single user:

#chown <username> /home/<username>/edb_83.env

#vi /home/<username>/.bash_profile

增加如下一行:

. /home/<username>/edb_83.env 注意. /之间有空格

To load the environment for all users:

#vi /etc/profile

增加如下一行:

. /etc/edb_83.env   注意. /之间有空格

我的实验环境：

[enterprisedb@postgres ~]$ edbplus

User: enterprisedb

Enter Password:

Connected to EnterpriseDB 8.3.0.112 (localhost:5444/edb) AS enterprisedb

EDB*Plus: Release 8.3 (Build 19)

Copyright (c) 2008-2009, EnterpriseDB Corporation.  All rights reserved.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

SQL>select * FROM v$version;
 
BANNER
 
--------------------------------------------------
 
Oracle DATABASE 10g Edition Release 10.2.0.1.0 - P
 
roduct IS similar
 
PL/SQL Release 10.2.0.1.0 - Production IS similar
 
CORE 10.2.0.1.0 Production IS similar
 
SQL>

更详细内容请参考官方文档。

-The End-

BTW:

需要PLSQL Developer 8.0.0.1483的朋友请稳步这里下载。

-The End-