18:41 实时获得最耗CPU资源的SQL语句 (2874 Bytes) » DBA@Taobao

在Oracle性能诊断和日常监控中，最耗CPU的语句通常也是我们最需要关心的语句。所以在Oracle10g的awr中，将cpu time和elapsed time最高的语句加入到了报表，并且放到了SQL语句部分的前两位。那么在平时的监控中，也可以通过shell脚本实时捕获系统中CPU耗用最多的进程中正在执行的SQL，以更加有效和及时的诊断和发现问题。

首先写一个根据spid来或者其SQL的脚本get_by_spid.sql

#!/bin/ksh
# creator:NinGoo
# function: get sql statement by spid
# parameter: spid
# useage: get_by_spid.sh spid

sqlplus -S /nolog <<EOF
connect / as sysdba;
col SERIAL# format 999999
col sid format 99999
col username format a10
col machine format a12
col program format a32
col sql_text format a81
set lines 1000
set pages 1000
set verify off
col sql_hash_value new_value hash_value head hash_value
select sid,serial#,username,program,sql_hash_value,
to_char(logon_time,'yyyy/mm/dd hh24:mi:ss') as login_time
from v\$session
where paddr in ( select addr from v\$process where spid=$1);

select sql_text
from v\$sqltext_with_newlines
where hash_value = &hash_value
order by piece;
exit;
EOF

然后再在另外一个shell脚本topsql.sh中获得系统中CPU耗用最多的oracle server process的spid，循环调用第一个脚本获得SQL

#!/bin/ksh
# creator:NinGoo
# function: get top cpu sql
# parameter: N
# useage: topsql.sh N

if [ $# -eq 0 ]; then
echo "Usage: `basename $0` N"
exit 1
fi

topcpu=`ps auxw|grep LOCAL|sort -rn +2 |head -$1|awk '{print $2}'`
i=0

for spid in $topcpu
do
i=`expr $i + 1`
echo "\033[32;1m===============top $i cpu sql=============\033[0m"
. /home/oracle/worksh/get_by_spid.sh $spid
done

那么调用就很简单了，假如我们要看系统top 3的sql语句，只需要执行topsql.sh 3即可。当然，如果我们自己通过top/topas等工具已经获得spid了，那么只要执行get_by_spid.sh spid就能获得该进程正在执行的sql语句了。

Add Comments(0)

18:35 实时获得最耗CPU资源的SQL语句 (3436 Bytes) » NinGoo@Net

Author:NinGoo posted on NinGoo.net

在Oracle性能诊断和日常监控中，最耗CPU的语句通常也是我们最需要关心的语句。所以在Oracle10g的awr中，将cpu time和elapsed time最高的语句加入到了报表，并且放到了SQL语句部分的前两位。那么在平时的监控中，也可以通过shell脚本实时捕获系统中CPU耗用最多的进程中正在执行的SQL，以更加有效和及时的诊断和发现问题。

首先写一个根据spid来或者其SQL的脚本get_by_spid.sql

#!/bin/ksh
# creator:NinGoo
# function: get sql statement by spid
# parameter: spid
# useage: get_by_spid.sh spid

sqlplus -S /nolog < connect / as sysdba;
col SERIAL# format 999999
col sid format 99999
col username format a10
col machine format a12
col program format a32
col sql_text format a81
set lines 1000
set pages 1000
set verify off
col sql_hash_value new_value hash_value head hash_value
select sid,serial#,username,program,sql_hash_value,
to_char(logon_time,'yyyy/mm/dd hh24:mi:ss') as login_time
from v\$session
where paddr in ( select addr from v\$process where spid=$1);

select sql_text
from v\$sqltext_with_newlines
where hash_value = &hash_value
order by piece;
exit;
EOF

然后再在另外一个shell脚本topsql.sh中获得系统中CPU耗用最多的oracle server process的spid，循环调用第一个脚本获得SQL

#!/bin/ksh
# creator:NinGoo
# function: get top cpu sql
# parameter: N
# useage: topsql.sh N

if [ $# -eq 0 ]; then
echo “Usage: `basename $0` N”
exit 1
fi

topcpu=`ps auxw|grep LOCAL|sort -rn +2 |head -$1|awk ‘{print $2}’`
i=0

for spid in $topcpu
do
i=`expr $i + 1`
echo “\033[32;1m===============top $i cpu sql=============\033[0m”
. /home/oracle/worksh/get_by_spid.sh $spid
done

那么调用就很简单了，假如我们要看系统top 3的sql语句，只需要执行topsql.sh 3即可。当然，如果我们自己通过top/topas等工具已经获得spid了，那么只要执行get_by_spid.sh spid就能获得该进程正在执行的sql语句了。

Related Articles

Add Comments(0)

17:50 专业 (2906 Bytes) » Fenng's shared items in Google Reader

将近一个月的时间没有写任何的 blog, 最近自己的时间都花在了一些层出不穷的精彩的东西上:

这都是一些让像我这样的喜欢技术的人感到异常激动的伟大平台. 如果能够有更多的时间花在这些东西上, 并且关键在于, 在其中进行一种持续地积累的话, 就实在是很幸福的感觉. 想想看, 过去的几年时间里, 我都积累了一些什么呢? 那些积累下来的东西中, 有多少是自己真正喜欢的呢?

发现一件有趣的事情, 大部分的那些最热门的日本的动漫或者连续剧, 如果提炼其中的中心思想的话, 他们都是在说一件事情, "专业的人有好报, 不专业的人有恶报, 回头是岸". 于是, 或许在日本人的心目中, 所谓地道的方式就是只做一件事情, 并且把那件事情做得非常非常好甚至极端. 于是我们就会在动漫和连续剧中看到极其专业的围棋手, 篮球运动员, 营业员, 歌手, 同人漫画作者等等(你知道我在指的是哪些动漫和连续剧). 毫无疑问, 那意味着一种相当安分而满足的生活. 甚至可以用简单的快乐来形容. 而事实上, 我们目前所遇到的诸多问题, 难道不就是因为不专业而引起的么? 因为不专业, 我们无法彻底地相信别人, 因为不专业, 很多人经常性的一些做法恐怕只能用"不安分"来形容. 而这恐怕是一个负向循环, 因为很多人不专业, 于是这个环境不专业, 因为这个环境不专业, 于是很多人也就没有了变得专业的机会. 哈?

如果这是一个问题的话, 对我来说确实是一个问题, 那么我会用什么样的方式去解决呢? 任何的专业的道路开始于对于一种专业的选择, 而后在积累的过程中循环一些做法. 选择是一件困难的事情. 感谢我们国家的飞速发展, 使得生活在沿海城市的年轻的我们相对于父辈已经有了相当程度的自由. 于是这样的自由多少让我们有点彷徨. 至少对于我而言, 做出一个选择并不是容易的事情. 这个世界上有太多太多美好的东西, 而我对它们都有相当的兴趣. 成为一个程序高手或者是努力在未来成为国家地理杂志的摄影师或是成为一本畅销书的作者对我而言都有巨大的吸引力. 而尝试新东西的时候的兴奋感总是大于之后的恐惧.

[ read more on livid.cn ]

16:01 有趣的触发器事件 (566 Bytes) » yangtingkun

在查询触发器的视图时碰到了一个有趣的问题。通过一个SQL检查DBA_TRIGGERS中存在哪个触发事件：SQL> SELECT DISTINCT TRIGGERING_EVENT FROM DBA_TRIGGERS;TRIGGERING_EVENT------------------------------UPDATE OR DELETEDROPALTER OR RENAMEINSERT OR UPDATE OR DELETEINSERT OR UPDATEDELETEUPDATETRUNCATECREATEALTERCREATE OR ALTERINSERTSTARTUPDROP OR TRUNCATESHUTDOWN已选择15行。下面检查数据库中触发事件为SHUTDOWN的触发器有哪些：SQL> SELECT OWNER, TRIGGER_NAME 2 FROM DBA_TRIGGERS 3 WHERE TRIGGERING_EVENT = 'SHUTDOW...

15:37 OOXML approved by ISO: What next? (6494 Bytes) » Red Hat Magazine

Contributing author: Melanie Chernoff

Over the past year, the OOXML debate launched a worldwide discussion about what an open standard should be, how it impacts the technology industry, and why open standards are important.

Last week, OOXML–an XML format designed for Microsoft’s office suite–was approved as a standard by the International Organization for Standardization (ISO). In past articles^{1 2}, we have discussed problems with voting irregularities, the use of a fast-track process without adequate industry review, proprietary Microsoft technologies used without specification, and other problems. Now that OOXML has been approved despite these objections, let’s take a look at the standardization process and the impact that OOXML’s approval will have in the office suite space.

A credible process?

The OOXML debate has raised many concerns about the ISO standardization process, especially for fast-track standardization. Voting irregularities were reported in nearly one-quarter of the “P” countries that voted to approve OOXML. In a highly publicized statement, Norway requested to retract its vote. This compounds the issues raised in earlier rounds, such as new countries and technical committee members joining at the last minute in order to influence the vote, or incentives offered to Microsoft business partners to encourage them to vote for OOXML³.

Even without such irregularities, the ISO fast-track process was not designed allow adequate review of such a large and complex standard. Clearly, ISO needs to examine how such standards are approved, ensuring that they receive thorough and fair technical review, and that politics does not trump this review.

The fast-track review process used for OOXML required over a thousand technical issues be resolved very rapidly. It was simply not possible to adequately review these resolutions in time for the vote. Some of these issues clearly were not addressed well³.

Here’s one example: Microsoft’s date format incorrectly calculates leap year and days of the week for the year 1900, and cannot represent dates before 1900. Instead of fixing this problem, Microsoft added the standard ISO date and time types as another option. Thus, the same date can be on different weekdays depending on which date format is used to store it.

Life for open source after the vote

Microsoft still dominates the office software market. The European Union advised Microsoft to submit OOXML for standardization because it strongly favors open standards that allow it to safely preserve legacy documents and reduce vendor dependence. The adoption of OOXML as an ISO standard will help Microsoft overcome government procurement obstacles that it currently faces due to its proprietary formats.

However, the European Union has launched an investigation into Microsoft’s practices to influence the OOXML vote. It is not clear how this will impact European adoption of OOXML.

While open source advocates are understandably unhappy that OOXML was approved, the management and documentation of OOXML may have one positive side effect. Open source office software like Open Office or Abiword have long supported Microsoft’s proprietary binary formats, and the fact that these formats are now documented will make it easier to provide more complete support for them. And data in any XML format is easier to access and use in applications than proprietary formats.

However, there is still much work to be done. The OOXML standardization process has highlighted real weaknesses in the specification as well as in the ISO processes. We encourage the ISO to examine its procedures for standardizing software–especially the fast-track process–to ensure fairness, adequate technical review, interoperability, and compatibility.

That leaves, of course, the one big question: Now that there are two ISO standards for office document data, what does this means for ODF?

As the ODF Alliance said recently, “ODF will continue to be the document format of choice that best meets the needs of governments interested in ensuring access to their own information, now and in the future.”⁴

ODF is a simpler format that is easier to process, and less tied to legacy issues found in Microsoft office software. Open source office software is available for ODF formats. Red Hat, like many open source companies, will continue to support ODF and encourage governments to adopt ODF instead of OOXML.

¹ http://www.redhatmagazine.com/2008/03/24/iso-approval-a-good-process-gone-bad/
² http://www.redhatmagazine.com/2008/03/06/ooxml-why-the-debate/
³ For some further details, see http://www.odfalliance.org/resources/Oracle%20Technical%20Concerns%20DIS29500.pdf
⁴ http://www.odfalliance.org/blog/index.php/site/odf_alliance_statement_on_the_iso_vote_on_ooxml/

15:22 TPC-H Run on MySQL 5.1 and 6.0 (9338 Bytes) » MySQL Performance Blog

We were doing MySQL Performance evaluation on TPC-H queries for the client and they kindly allowed us to publish results which are very interesting.
This is obviously not audited TPC-H run, and it can’t be because we used MyISAM tables which are not ACID complaint. Plus we only measured Power to keep things simple.

We tested 10G and 100G data sets which was CPU bound and IO bound box on the Dell 2950 box w 16G of RAM which we used for testing. Even though box had 8 cores it is little use for MySQL as only one query is ran concurrently, same can be told about 8 hard drives which this box had.
MySQL Also was very slow running some queries so we changed scripts a bit to kill extremely long running queries to get results for others this means we can’t really get a valid TPC-H result from MySQL,though at least we get to see performance of individual queries.
We also packaged the toolset we used for benchmarks so you can repeat them if you like. It can be downloaded here

So let us first take a look at MySQL 5.1.23 vs 6.0.4 results for 10GB data set which “fits in memory”. The cut-off time for this test was 1 hour so query taking over 1 hour has NA. Times are given in seconds.
Ratio is MySQL 6.0 time divided by MySQL 5.1 time so if it is less than 1 MySQL 6.0 is faster if smaller than 1 slower:

Query	MySQL 5.0.23	MySQL 6.0.4	Ratio
Query1	370.50	372.16	1.00
Query2	724.63	623.68	0.86
Query3	328.25	354.62	1.08
Query4	7.95	8.08	1.02
Query5	154.36	161.65	1.05
Query6	29.35	38.51	1.31
Query7	322.04	331.05	1.03
Query8	469.31	457.18	0.97
Query9	123.75	121.33	0.98
Query10	343.37	341.23	0.99
Query11	2.32	2.34	1.01
Query12	28.68	38.61	1.35
Query13	46.00	47.84	1.04
Query14	8.83	8.23	0.93
Query15	21.50	23.61	1.10
Query16	55.48	61.42	1.11
Query17	9.00	9.33	1.04
Query18	N/A	1962.96	N/A
Query19	5.03	5.30	1.05
Query20	2.06	0.26	0.13
Query21	33.16	32.98	0.99
Query22	7.84	8.06	1.03

As you can see for 10G results there is only one query which does not complete within an hour in 5.1 and MySQL 6.0 can complete all queries within an hour.
We can also see MySQL 6.0 improving query 20 speed dramatically, the rest of the queries is however close and MySQL 6.0 is even significantly slower than 5.1 for
number of queries. Honestly I expected more from MySQL 6.0 optimizer improvements effort.

100GB Results are more interesting because this is database size for which you can find results published on TPC Web site. For example These Are results recently published for Microsoft SQL Server.
Of course this is much more powerful system but still you can get an idea - This system has geomean of 7.7 sec for Power test which is good order of magnitude better compared to MySQL results on 10G database.
TPC does discourage from comparing results against different database sizes so let’s see 100G data set results.
In this case we set cut-off time to 3 hours to give MySQL more time to complete the queries:

Query	MySQL 5.0.23	MySQL 6.0.4	Ratio
Query1	3784.45	3737.54	0.99
Query2	NA	NA	NA
Query3	NA	NA	NA
Query4	NA	NA	NA
Query5	NA	NA	NA
Query6	NA	NA	NA
Query7	4328.22	4533.62	1.05
Query8	8947.72	4122.62	0.46
Query9	NA	NA	NA
Query10	NA	NA	NA
Query11	2726.20	3395.02	1.25
Query12	NA	NA	NA
Query13	NA	NA	NA
Query14	2345.68	?	NA
Query15	NA	NA	NA
Query16	725.31	693.56	0.96
Query17	1895.55	NA	NA
Query18	NA	NA	NA
Query19	4896.27	4682.19	0.96
Query20	3117.45	1450.42	0.47
Query21	NA	NA	NA
Query22	108.56	100.72	0.93

As you can see on 100G data set MySQL 5.1 could only complete 10 out of 22 queries within 3hours run time allowed for each query and MySQL 6.0 has similar number of queries it can execute in reasonable time frame. There 2 queries (Query8 and Query20) which MySQL 6.0 does better but there is also Query11 in which significant regression is observed. Vadim has already Wrote about it in his MySQL 5.1 vs 6.0 in TPC-H Queries post

As a Summary: We can see MySQL capabilities to run complex analytics queries, in particular those presented in TPC-H benchmark are still subpar even with changes which are currently seen in MySQL 6.0 tree. There is a long way till Release and may be MySQL 6.0 performance will improve. Though considering a lot of talks about optimizer improvements in MySQL 6.0 I expected drastically better results.
Though may we should not be as surprised by these results - MySQL 6.0 still does not have hash or merge join which are frequently used for these kind of queries, and there is also no query parallelization which would allow MySQL to use CPUs and hard drives this system has more efficiently. Parallel query will be growing issue for MySQL because CPUs just continue to add more cores. Having 2 CPUs and being able to use only half of system CPU resources for query processing was not too bad, however with 16,32,64 cores it is just too bad.

Entry posted by peter | No comment

Add to: | | | |

15:22 TPC-H Run on MySQL 5.1 and 6.0 (9488 Bytes) » Fenng's shared items in Google Reader

We were doing MySQL Performance evaluation on TPC-H queries for the client and they kindly allowed us to publish results which are very interesting.
This is obviously not audited TPC-H run, and it can’t be because we used MyISAM tables which are not ACID complaint. Plus we only measured Power to keep things simple.

We tested 10G and 100G data sets which was CPU bound and IO bound box on the Dell 2950 box w 16G of RAM which we used for testing. Even though box had 8 cores it is little use for MySQL as only one query is ran concurrently, same can be told about 8 hard drives which this box had.
MySQL Also was very slow running some queries so we changed scripts a bit to kill extremely long running queries to get results for others this means we can’t really get a valid TPC-H result from MySQL,though at least we get to see performance of individual queries.
We also packaged the toolset we used for benchmarks so you can repeat them if you like. It can be downloaded here

So let us first take a look at MySQL 5.1.23 vs 6.0.4 results for 10GB data set which “fits in memory”. The cut-off time for this test was 1 hour so query taking over 1 hour has NA. Times are given in seconds.
Ratio is MySQL 6.0 time divided by MySQL 5.1 time so if it is less than 1 MySQL 6.0 is faster if smaller than 1 slower:

Query	MySQL 5.0.23	MySQL 6.0.4	Ratio
Query1	370.50	372.16	1.00
Query2	724.63	623.68	0.86
Query3	328.25	354.62	1.08
Query4	7.95	8.08	1.02
Query5	154.36	161.65	1.05
Query6	29.35	38.51	1.31
Query7	322.04	331.05	1.03
Query8	469.31	457.18	0.97
Query9	123.75	121.33	0.98
Query10	343.37	341.23	0.99
Query11	2.32	2.34	1.01
Query12	28.68	38.61	1.35
Query13	46.00	47.84	1.04
Query14	8.83	8.23	0.93
Query15	21.50	23.61	1.10
Query16	55.48	61.42	1.11
Query17	9.00	9.33	1.04
Query18	N/A	1962.96	N/A
Query19	5.03	5.30	1.05
Query20	2.06	0.26	0.13
Query21	33.16	32.98	0.99
Query22	7.84	8.06	1.03

As you can see for 10G results there is only one query which does not complete within an hour in 5.1 and MySQL 6.0 can complete all queries within an hour.
We can also see MySQL 6.0 improving query 20 speed dramatically, the rest of the queries is however close and MySQL 6.0 is even significantly slower than 5.1 for
number of queries. Honestly I expected more from MySQL 6.0 optimizer improvements effort.

100GB Results are more interesting because this is database size for which you can find results published on TPC Web site. For example These Are results recently published for Microsoft SQL Server.
Of course this is much more powerful system but still you can get an idea - This system has geomean of 7.7 sec for Power test which is good order of magnitude better compared to MySQL results on 10G database.
TPC does discourage from comparing results against different database sizes so let’s see 100G data set results.
In this case we set cut-off time to 3 hours to give MySQL more time to complete the queries:

Query	MySQL 5.0.23	MySQL 6.0.4	Ratio
Query1	3784.45	3737.54	0.99
Query2	NA	NA	NA
Query3	NA	NA	NA
Query4	NA	NA	NA
Query5	NA	NA	NA
Query6	NA	NA	NA
Query7	4328.22	4533.62	1.05
Query8	8947.72	4122.62	0.46
Query9	NA	NA	NA
Query10	NA	NA	NA
Query11	2726.20	3395.02	1.25
Query12	NA	NA	NA
Query13	NA	NA	NA
Query14	2345.68	?	NA
Query15	NA	NA	NA
Query16	725.31	693.56	0.96
Query17	1895.55	NA	NA
Query18	NA	NA	NA
Query19	4896.27	4682.19	0.96
Query20	3117.45	1450.42	0.47
Query21	NA	NA	NA
Query22	108.56	100.72	0.93

As you can see on 100G data set MySQL 5.1 could only complete 10 out of 22 queries within 3hours run time allowed for each query and MySQL 6.0 has similar number of queries it can execute in reasonable time frame. There 2 queries (Query8 and Query20) which MySQL 6.0 does better but there is also Query11 in which significant regression is observed. Vadim has already Wrote about it in his MySQL 5.1 vs 6.0 in TPC-H Queries post

As a Summary: We can see MySQL capabilities to run complex analytics queries, in particular those presented in TPC-H benchmark are still subpar even with changes which are currently seen in MySQL 6.0 tree. There is a long way till Release and may be MySQL 6.0 performance will improve. Though considering a lot of talks about optimizer improvements in MySQL 6.0 I expected drastically better results.
Though may we should not be as surprised by these results - MySQL 6.0 still does not have hash or merge join which are frequently used for these kind of queries, and there is also no query parallelization which would allow MySQL to use CPUs and hard drives this system has more efficiently. Parallel query will be growing issue for MySQL because CPUs just continue to add more cores. Having 2 CPUs and being able to use only half of system CPU resources for query processing was not too bad, however with 16,32,64 cores it is just too bad.

Entry posted by peter | No comment

Add to: | | | |

12:29 活在淘宝站内搜索的年代 (4277 Bytes) » Fenng's shared items in Google Reader

1、百度口头进军C2C市场的时候提出了一个重要的理由：市场上主要C2C交易平台超过40%的流量、淘宝30%的站外流量来自百度搜索。(下文所提“电子商务”基本不包括B2B)

2、我想象中的电子商务搜索应用场景有很多，“告诉我想买的东西在那个网店上有卖，基本情况是怎么样的”为最通用的应用描述。
“逛街的时候看到一个包包，随手在网上搜索一下，然后直接下单或者作为和卖家讨价还价的依据”；“看到朋友/别人在网上说买了一个我也喜欢的东西，马上去搜索一下哪里有卖的”；“突然想买一个东西，去网上搜索一下，看看详情和价格，然后决定要不要买。最后直接下单或者去熟悉的商场”；“打算买一个东西，去各家网店比较一下”，……

3、单说电子商务搜索这个服务，我更看好其在移动领域的应用。手机版淘宝上线后，这样的应用应该是非常普遍的。
像IVSOU.com这样，类似Like.com但不只是LIKE的创业项目貌似国内很少。“当你逛街的时候看到一个商品，用手机拍张照片传到网上，这个网站马上就可以通过图像识别告诉你：什么地方有卖同样/相似的商品，以及价格等详细信息”。这样的产品概念很具吸引力。

4、目前来看，似乎这些应用现在都去了两个地方：淘宝、百度。有网购经验的大多直接去淘宝，没有网购经验的人先去百度然后再去淘宝。

5、我们也并没有看到三大集团（阿里、百度、腾讯）或者其他企业专门去做，类似电子商务搜索的事情。究其原因：一家独大。
不少投资者几乎都回答了我同样的理由：我们也觉得这个市场会很有前景，但目前一家独大，看不到应用价值；虽然我们也同意市场会慢慢趋于平衡，但我们无法去押一个“期盼市场会平衡”的不可控项目。而且也没有看到什么企业可以拿出更好的商业模式。投资是押给“计算结果”的，不太可能押给“上天”。

6、国内现在的电子商务搜索几乎成了淘宝的站内搜索，一家独大确实很可怕。就像无论干什么都得和中移动打交道一样。
腾讯在IM上一家独大，但IM是一个基础服务，可以掐住对手脖子的玩意，所以对手无论如何也要闯进去。
但电子商务现阶段并非上网必须，电子商务搜索在现阶段也更无法被作为基础服务看待。ecshop、shopex等蚂蚁雄兵们却在急于宣传“淘宝2.0”，直接整合内容；集团大佬们不放心只做搜索“通道”，更想做“渠道”，不愿意把基础商家放在别人的地盘上，更不愿意眼睁睁的看着别人在赚“现金”。

7、从产品来讲，我一直认为淘宝目前有四个大不足：评价/信用体系、支付易用性（很多人在淘宝和支付宝之间跳来跳去，最后晕掉）、站外应用（特别是类搜索的）、社区应用。
关于站外应用，今天看到淘宝UED团队就IE8测试做了这样的尝试，很有意思。这个应用本身可能没什么，但值得很多做电子商务的人去思考，也许可以发现很好的“点子”。
.

ps：
1、我个人大胆估计：手机版淘宝90%以上的流量要经过“搜索”。谁有更准确的数据请指教。
2、前天在地铁上突然想到了一个针对淘宝的点子：首先让“网店”可以更加个性化相对“独立”，然后效仿英特尔给自己的卖家报销一定的广告费。

09:05 有趣的Firefox火狐浏览器3.0测试版背景图片 (3354 Bytes) » Fenng's shared items in Google Reader

　　近日，有很多网友都发现，正在紧张公测中的Firefox火狐3.0版浏览器的四个版本的背景图片，均已机器人，威风凛凛，煞是可爱，并且在Firefox 3 Beta 5中输入about:robots，会出现机器人“欢迎人类”的宣言，让我们一起欣赏一下吧！

Firefox火狐3.0版浏览器Beta 2版

Firefox火狐3.0版浏览器Beta 3版

Firefox火狐3.0版浏览器Beta 4版

Firefox火狐3.0版浏览器Beta 5版

在Firefox 3 Beta 5中输入about:robots，会出现机器人“欢迎人类”的宣言

发表者：Google（谷歌）研究员吴军

1. 二战的品牌

2. 黄金时代

3. 基因决定定理

4. 铱星计划

世界科技史上最了不起的、最可惜的、也许也是最失败的项目之一就是以摩托罗拉牵头的铱星计划。

为了夺得对世界移动通信市场的主动权，并实现在世界任何地方使用无线手机通信，以摩托罗拉为首的美国一些公司在政府的帮助下，于 1987 年提出的新一代卫星移动通信星座系统。我们知道，当今的移动通信最终要通过通信卫星来传输信息，为了保证在任何时候卫星能够收发信号，卫星必须保持和地球的相对位置不变。所有的同步通信卫星都必须挂在离地球三万多公里高的赤道上空。同时在地面建立很多卫星基站来联络手机和卫星。如果一个地方没有基站，比如沙哈拉沙漠里，那么手机就没有信号，无法使用。铱星计划和传统的同步通信卫星系统不同，新的设计是由 77 颗低卫星组成一个覆盖全球的卫星系统。每个卫星比同步通信卫星小得多，重量在 600-700 公斤左右，每颗卫星有三千多个信道，可以和手机直接通信（当然还要互相通信）。因此，它可以保证在地球任何地点实现移动通信。由于金属元素铱有 77 个电子，这项计划就被称为了铱星计划，虽然后来卫星的总数降到了 66 个。

这是一个非常宏伟而超前的计划，它最大的技术特点是通过卫星与卫星之间的传输来实现全球通信，相当于把地面蜂窝移动系统搬到了天上。从技术讲，铱星系统是相当了不起的，它采用星际链路。在极地，66 颗卫星要汇成一个点，又要避免碰撞，难道很高。从管理上讲，它又是一个完整的独立网，呼叫、计费等管理是独立于各个国家通信网的。（这种独立计费再后来给它的运营带来很大麻烦。）低轨道卫星与目前使用的同步轨道卫星通信系统比较有两大优势：首先，因为轨道低，只有几百公里，信息损耗小，这样才可能实现手机到卫星的直接通信。我们现在的任何手机都不可能和三万公里以外的同步卫星直接通信；第二，由于不需要专门的地面基站，可以在地球上任何地点进行通信。1991 年摩托罗拉公司联合了好几家投资公司，正式启动了“铱星计划”。1996 年，第一颗铱星上天；1998 年整个系统顺利投入商业运营。美国历史上最懂科技的副总统戈尔第一个使用铱卫系统进行了通话。此前，铱星公司已经上市了，铱星公司的股票在短短的一年内大涨了四倍。铱星系统被美国《大众科学》杂志评为年度全球最佳产品之一。铱星计划开始了个人卫星通信的新时代。

从技术角度看，铱星移动通信系统是非常成功的。这是真正的科技精品。我常常想，我们这些被称为高科技公司的互联网公司做到的东西和铱星系统相比，简直就像是玩具。铱星系统在研发中，有许多重大的技术发明。应该说整个铱星计划从确立、运筹和实施都是非常成功的。但是，在商业上，从投资的角度讲，它却是个彻头彻尾的失败。这个项目投资高达五六十亿美元，每年的维护费又是几亿美元。除了摩托罗拉等公司提供的投资和发行股票筹集的资金外，铱星公司还举借债三十亿美元的债务，每月光是利息就达几千万。为了支付高额的费用，铱星公司只能将手机的价钱订在五千美元一付，每分钟的通话费定在每分钟三美元。这样，铱星公司的用户群就大大减小。直到去年，它才有二十万用户，还不及苹果iPhone一个月发展的用户多。

铱星系统投入商业运行不到一年，1999 年 8 月 13 日铱星公司就向纽约联邦法院提出了破产保护。半年后的 2000 年 3 月 18 日，铱星公司正式破产。铱星成了美丽的流星。66 颗卫星在天上自己飞了几年，终于于 2001 年被一家私募基金公司（Private Equity）以两千五百万美元的低价买下。不到铱星整个投资是六十亿美元的 1% 。作为一个与摩托罗拉无关的私营公司，铱星居然起死回生，去年实现近三亿美元的营业额和五千万的利润。（注：这里的利润是按美国会计结算方式计算出来的，盈利并不代表现金流是正数。）

铱星计划是通信史上一个流星，一个美丽的故事（A Beautiful Story）。摩托罗拉公司很聪明地利用其技术优势吸引了全世界的眼球。该计划一出炉就引起世人的广泛注目，也赢得了风险投资家的青睐。摩托罗拉为此自己拿出了十亿美元，同时钓鱼似的从投资公司有拿到近五十亿美元，从而大大降低了自己的风险。但是，在商业运作上，摩托罗拉做得很不成功。首先，市场分析现在看来就有问题，成本过高导致用户数量不可能达不到预计的盈利所必需的规模。而成本过高的原因又是技术选择的失误造成的。摩托罗拉长期以来都是一个了不起的技术公司，它长于技术，但是过分相信技术的作用。铱星计划在技术上是无与伦比的，但是，过于超前市场的技术不仅导致成本过高，而且维护费用也是巨大的。另外，引入风投本身的弊端在项目的后期凸显出来，那就是投资者为了收回投资，过早将铱星系统投入商用，当时这个系统通话的可靠性和清晰度很差，数据传输速率也仅有 2.4Kps ，因此除了打电话没法做任何事，这使得潜在的用户大失所望。概况来讲，就是铱星计划太超前了，它开业的前两个季度，在全球只有一万个用户，而当初市场的分析去乐观地预计，仅在中国就能有这个数的十倍。在后期商业运作上。铱星公司问题很多，最终导致银行停止贷款、部分股东撤回投资，并导致公司在股市上停盘的致命打击。

06:11 今天我生日收每人一张卡片 (837 Bytes) » 玉面飞龙的BLOG

今天又是我生日，又朝奔三迈进了一步。收到不少朋友的恭贺短信和电话，意外。父母奶奶弟弟也慰问我，互道思念。下午在公司还收到女朋友送的20朵玫瑰，还好是送者买单；头一次别人送花给我，还是玫瑰；同事还以为是我买给别人的，本打算将花送给各位同事的，但要给每个人准备插花的花瓶，会浪费很多一次性纸杯的，作罢。晚上大餐红烧排骨+长寿面，美味。后来女友竟然还准备了蛋糕，油腻的那种，没有觉得好吃，不过还吹了提示我年龄”27″形状的蜡烛。有人唱歌祝我年年有今日。蛋糕前许了愿来年争取买几个房子。在CPI上涨就是混也很压力的今天，还真是感到幸福感了——幸福要记的细致点。

02:39 牌运不佳 (1434 Bytes) » blue_prince

上周末和这周二接连打了两次牌。没想到两次都是惨败，是打牌以来输得最惨的两次。打杭州这边流行的双扣，这两次都是第一把就双扣别人，结果后面就一直输下去，看来打牌是不能赢头把的。上个周末还坚持着一小段时间，这周二输得可就惨了。牌抓得好吧，别人抓得更好，手上好几幅炸弹，炸都炸死你；牌抓得不好吧，人家的牌还是比你好，硬生生地把你堵死。有一盘居然有一个人抓了2幅6张牌的炸弹，另外一个人抓了1幅6张牌的炸弹，加上被双扣，一把就输了6个。还有人抓7张牌炸弹的，有人抓4个鬼的，从-3到-23只用了5把，NNGX。输了点小钱，哈哈。本来打牌有个原则是坚决不赌钱，后面被gytyl拉下水，赌了点小钱，发现赌点小钱挺好玩的。小赌怡情啊！NinGoo也是打牌从不赌钱的，不过现在也被我拉下水了，哈哈，不过这小子一赌钱基本上都是小输或者平。

02:34 Oracle 9i 的生命周期支持策略 (3428 Bytes) » Oracle Life

©作者：eygle 发布在 eygle.com

有朋友问Oracle9i的支持周期，很多人说到今年Oracle9i将不再支持，其实这并不确切。

Oracle的支持周期由三部分组成：

1.从产品发布为期5年的标准支持服务期-Premier support
2.随后为期3年的延展支持服务期---------extended support
3.接下来进入持久支持服务期--------------sustaining support

下图是Oracle产品支持策略划分：

不过根据不同的周期划分，Oracle的支持费用将会不同，在延展服务器内，第一年将会加收10%的费用提供支持，第二年加收20%的费用提供支持，第三年也是加收20%的费用提供支持。
不过Oracle已经决定对9i第一年延展期免收额外费用：

Extended Support fee waived for period August 1, 2007 to July 31, 2008.
Access to Fixes and Critical Patch Updates (CPUs) during the first year of Extended Support at no additional cost.
Patch set 9.2.0.8 will be the last patch set available for Oracle9i Database Release 9.2.
Effective August 1, 2007 all CPUs and Fixes will be created against the 9.2.0.8 code line.

第一年的延展期将于2008年7月31日结束。

下图是Oracle数据库主要版本的支持周期：

关于 Oracle Lifetime Support Policy 策略，可以参考Oracle的官方站点：
http://www.oracle.com/support/lifetime-support-policy.html

-The End-

相关文章|Related Articles

评论数量(0)|Add Comments

本文网址：http://www.eygle.com/archives/2008/04/oracle9i_lifetime_support_policy.html

02:30 HACMP 认证学习系列，第 3 部分：安装和配置（2） (103 Bytes) » developerWorks : AIX 专区的文章，教程

在本文中，我们将介绍 HACMP 在定义、配置节点以及配置节点之间连接的内容。

02:30 HACMP 认证学习系列，第 2 部分：计划与设计 (237 Bytes) » developerWorks : AIX 专区的文章，教程

在规划和设计高可用性集群时，必须遵守所有的客户需求。您应该充分了解硬件和网络配置，以及将要实现高可用性的应用程序。您还应该能够控制应用程序在故障情况下的行为。

02:30 HACMP 5.x 完全手册，第 2 部分：配置 (340 Bytes) » developerWorks : AIX 专区的文章，教程

本系列文章的作者通过自己长期的实际项目工作经历，总结出了他对于 HACMP 设计实施的经验。本系列会分为 4 部分，会向您详细地介绍实施 HACMP 过程中会经历的各个过程，如设计，配置，安装，测试等。本文为第 2 部分，会向您介绍 HAMCP 的具体配置过程。

02:15 夏令时与Oracle PatchSet 10.2.0.4 (2156 Bytes) » DBA@Taobao

Author:江枫 posted on Taobao.com

Oracle10.2.0.4发布有一段时间了，在Metailink上搜索Patch Number：6810189，即可获得下载，目前已经发布了Linux X86/Linux X86_64/windows(32)三个版本，据说Solaris版本也已经发布，但是到今天Metalink上还是没有看到。

10.2.0.4中包含了DSTv4(Daylight Saving Time，也就是所谓的夏令时)的更新，所以如果你原有的系统中有使用Time Zone相关数据类型的（主要是TIMESTAMP WITH LOCAL TIME ZONE (TSLTZ)和TIMESTAMP WITH TIME ZONE (TSTZ)两种），升级之前需要检查系统的DST版本，然后做出相应的处理。

执行以下SQL，看数据库中是否使用了受影响的数据类型：

select c.owner || '.' || c.table_name || '(' || c.column_name || ') -' || c.data_type || ' ' col
from dba_tab_cols c, dba_objects o
where c.data_type like '%TIME ZONE'
   and c.owner=o.owner
   and c.table_name = o.object_name
   and o.object_type = 'TABLE'
order by col
/

如果没有，恭喜你，不用管啥DST了。如果有记录，那么根据现有的DST和Oracle版本的不同，需要做不同的处理。具体请参考Metalink(Note:553812.1)

如果是10g，可以通过如下SQL查询目前的DST版本：

select * from v$timezone_file;

如果是9i，是没有视图可以直接查的，Metalink上提供了一个utltzver.sql的脚本可以查询。

关于夏令时和Oracle，还可以参考Fenng的文章。

Add Comments(0)

02:13 夏令时与Oracle PatchSet 10.2.0.4 (2937 Bytes) » NinGoo@Net

Author:NinGoo posted on NinGoo.net

Oracle10.2.0.4发布有一段时间了，在Metailink上搜索Patch Number：6810189，即可获得下载，目前已经发布了Linux X86/Linux X86_64/windows(32)三个版本，据说Solaris版本也已经发布，但是到今天Metalink上还是没有看到。

10.2.0.4中包含了DSTv4(Daylight Saving Time，也就是所谓的夏令时)的更新，所以如果你原有的系统中有使用Time Zone相关数据类型的（主要是TIMESTAMP WITH LOCAL TIME ZONE (TSLTZ)和TIMESTAMP WITH TIME ZONE (TSTZ)两种），升级之前需要检查系统的DST版本，然后做出相应的处理。

执行以下SQL，看数据库中是否使用了受影响的数据类型：

select c.owner || ‘.’ || c.table_name || ‘(’ || c.column_name || ‘) -’ || c.data_type || ‘ ‘ col
from dba_tab_cols c, dba_objects o
where c.data_type like ‘%TIME ZONE’
and c.owner=o.owner
and c.table_name = o.object_name
and o.object_type = ‘TABLE’
order by col
/

如果没有，恭喜你，不用管啥DST了。如果有记录，那么根据现有的DST和Oracle版本的不同，需要做不同的处理。具体请参考Metalink(Note:553812.1)

如果是10g，可以通过如下SQL查询目前的DST版本：

select * from v$timezone_file;

如果是9i，是没有视图可以直接查的，Metalink上提供了一个utltzver.sql的脚本可以查询。

关于夏令时和Oracle，还可以参考Fenng的文章。

Related Articles

Add Comments(0)

01:39 隽。男人 (3057 Bytes) » Fenng's shared items in Google Reader

圈内最了解我的人应该是隽辰。
虽然我们不在一个城市，真正的直接交流也并不多。06年中我们认识，忘记因为什么。没见过，只在网上很少的交流。只感觉这个人很博学。

07年元旦我结婚，大雪，隽辰从南京赶来。俊秀的小生，内敛。
结婚的时候很忙，给他安排一个不咋地的酒店后就去忙我自己的了。头天中午吃饭，我们一帮北方男人用大杯干白酒，隽辰不能喝但坚持陪着，没有掉队。那个时候我知道了，这个南方人，硬汉。
第三天隽辰陪我们全家去逛天安门。回来後我妈说“那个小伙子很漂亮，很懂事”，老爸说“我对你唯一放心的就是你总有一帮对你很好的朋友”

07年3月，我突发奇想，要建一个草根团队，为交流也为体现草根的力量和价值。第一个邀请的是隽辰。他爽快的答应，并主持博客的建立和服器务等所有“技术”问题。这个南方人，有理想。很实干。

08春节后，我们开始准备UCDChina新的网站。我的想法总是很多，一天三变，要求也很苛刻。时间上还不停的挤。隽辰总是适应的很快，可以迅速的调整，不折不扣。
有人说棋友的最高境界是不用棋盘，可以互相清楚对方怎么想怎么走，局面是什么。隽辰给我的感觉就是这样。只要简单的说想法，他就很清楚我的意思。
隽辰说“白鸦是个苛刻的懒人”。就算是一个字体的大小，往往都指着他去调。

认识两年，我们真正只见过五次。隽辰来过北京三次，我去过南京两次。每次都是匆匆而来，匆匆而走。现实的交流很少，更多是网上的沟通。我说我又想干什么，他说可以怎么做。

隽辰很会生活，把自己安排的很充实。喜欢摄影，每个月都要出去一趟。坚持锻炼。上次去南京，隽辰说我太宅，应该多锻炼，找找互联网之外的乐趣。可他的眼睛没我好。
前天隽辰说他的眼睛有些不适，每天要用3种眼药水滴十几次。我们在北京都替他担心。

隽辰对于设计和产品的理解远胜于我。但他很少直接表达，更注重实干。我比他强的似乎只是经常会跳出来奇怪的想法，几箩筐加几箩筐，他总是可以让我尽情的表达完想法然后替我分析。

我曾经说，如果我创业一定不能少了隽辰。
虽然我不像佩服洪波一样佩服隽辰。但，男人对男人的欣赏，很可怕。

01:03 豆瓣寻人8：UI设计师 (1025 Bytes) » Fenng's shared items in Google Reader

工作职责：
-负责豆瓣和九点的用户界面设计
-根据产品需求与技术配合，高质量完成产品的视觉设计工作
-优化结合用户体验及完善设计流程

职位要求：
-大学本科或以上学历，人机交互、工业设计、视觉设计、计算机相关专业
-熟练运用Photoshop，Illustrator，Fireworks，Dreamwaver，Flash等常用设计软件，并具有在此基础上快速掌握和使用新软件的能力（请在简历中附带近期作品）
-熟悉Css、Html等网络技术
-拥有优秀的视觉设计能力，并且在web界面设计方面有成熟的作品
-认真细致，善于创新，对视觉设计、色彩有敏锐的观察力及分析能力

工作地点位于北京。有兴趣或者问题请email至 team(a)douban.com。请注明“UI”。

欢迎转载。谢谢！

00:51 10.2 RAC安装之clusterware (12578 Bytes) » Alibaba DBA Team

安装了下10.2的rac,在安装clusterware的过程中出现了一系列问题,零散的记录了下

系统环境：
4台刀片主机(linux AS 4.4) + 牛叉存储
RAC + ASM

网络环境配置(每台主机双网卡，只需要配置public,private两个IP，VIP由vipca去虚拟，不需要配置)：
#RAC network configure
10.0.38.160       hack1
10.0.38.170       hack1-vip
192.168.0.1       hack1-priv

10.0.38.162       hack2
10.0.38.172       hack2-vip
192.168.0.2       hack2-priv

10.0.38.164       hack3
10.0.38.174       hack3-vip
192.168.0.3       hack3-priv

10.0.38.166       hack4
10.0.38.176       hack4-vip
192.168.0.4       hack4-priv
磁盘用途：
votedisk -> /dev/raw/raw1 -> /dev/sdb1
ocrdisk -> /dev/raw/raw2 -> /dev/sdc1
disk1 -> /dev/raw/raw3 -> /dev/sdd1
disk2 -> /dev/raw/raw4 -> /dev/sde1

/etc/sysctl.conf添加如下内容：
kernel.shmall = 2097152
kernel.shmmax = 2147483648
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
fs.file-max = 65536
net.ipv4.ip_local_port_range = 1024 65000
net.core.rmem_default = 262144
net.core.rmem_max = 262144
net.core.wmem_default = 262144
net.core.wmem_max = 262144

系统包要求（更高）：
binutils-2.15.92.0.2-10.EL4
binutils-2.15.92.0.2-13.0.0.0.2.x86_64
compat-db-4.1.25-9
control-center-2.8.0-12
gcc-3.4.3-9.EL4
gcc-c++-3.4.3-9.EL4
glibc-2.3.4-2
glibc-common-2.3.4-2
gnome-libs-1.4.1.2.90-44.1
libstdc++-3.4.3-9.EL4
libstdc++-devel-3.4.3-9.EL4
make-3.80-5
pdksh-5.2.14-30
–部署目录
mkdir -p /opt/oracle/admin
mkdir -p /opt/oracle/products/10.2.0/db
mkdir -p /opt/oracle/products/crs
mkdir -p /opt/oracle/oraInventory
mkdir -p /opt/oracle/oradata/asmrac
mkdir -p /home/oracle
–编辑/etc/oraInst.loc,指定oraInventory目录和group
inventory_loc=/opt/oracle/oraInventory
inst_group=oinstall

–创建oracle帐户
/usr/sbin/groupadd oinstall
/usr/sbin/groupadd dba
/usr/sbin/groupadd oper
/usr/sbin/useradd -u 200 -g oinstall -G dba,oper oracle

chown -Rf oracle.dba /home/oracle
chown -Rf oracle.dba /opt/oracle

–配置ssh
su - oracle
mkdir ~/.ssh
chmod 700 ~/.ssh
/usr/bin/ssh-keygen -t rsa
/usr/bin/ssh-keygen -t dsa
touch ~/.ssh/authorized_keys
cd ~/.ssh

ssh hack1 cat /home/oracle/.ssh/id_rsa.pub >> authorized_keys
ssh hack2 cat /home/oracle/.ssh/id_rsa.pub >> authorized_keys
ssh hack3 cat /home/oracle/.ssh/id_rsa.pub >> authorized_keys
ssh hack4 cat /home/oracle/.ssh/id_rsa.pub >> authorized_keys

ssh hack1 cat /home/oracle/.ssh/id_dsa.pub >> authorized_keys
ssh hack2 cat /home/oracle/.ssh/id_dsa.pub >> authorized_keys
ssh hack3 cat /home/oracle/.ssh/id_dsa.pub >> authorized_keys
ssh hack4 cat /home/oracle/.ssh/id_dsa.pub >> authorized_keys

scp authorized_keys oracle@hack2:/home/oracle/.ssh/
scp authorized_keys oracle@hack3:/home/oracle/.ssh/
scp authorized_keys oracle@hack4:/home/oracle/.ssh/

–配置oracle用户环境
# .bash_profile

# Get the aliases and functions
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi

# User specific environment and startup programs

PATH=$PATH:$HOME/bin
ORACLE_BASE=/opt/oracle
ORACLE_SID=asmrac4
ORACLE_HOME=$ORACLE_BASE/products/10.2.0/db
CRS_HOME=$ORACLE_BASE/products/crs
ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data
PATH=$PATH:$ORACLE_HOME/bin:$ORACLE_HOME/oracm/bin
LD_LIBRARY_PATH=${LD_LIBRARY_PATH:+$LD_LIBRARY_PATH:}$ORACLE_HOME/lib:$ORACLE_HOME/ctx/lib:$ORACLE_HOME/oracm/lib
CLASSPATH=$ORACLE_HOME/JRE:$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib:$ORACLE_HOME/network/jlib

export ORACLE_BASE ORACLE_HOME ORA_NLS33 ORACLE_SID PATH LD_LIBRARY_PATH CLASSPATH TNS_ADMIN CRS_HOME

# ORACLE_TERM=xterm; export ORACLE_TERM
NLS_LANG=AMERICAN_AMERICA.US7ASCII; export NLS_LANG
alias sql=”sqlplus /nolog”
export SQLPATH=~/admin/sql:/$ORACLE_HOME/sqlplus/admin

export PATH
unset USERNAME

–部署供享磁盘，建立link
fdisk /dev/sdb /dev/sdc /dev/sdd /dev/sde

raw /dev/raw/raw1 /dev/sdb1
raw /dev/raw/raw2 /dev/sdc1
raw /dev/raw/raw3 /dev/sdd1
raw /dev/raw/raw4 /dev/sde1

chown -Rf oracle.dba /dev/sdb1
chown -Rf oracle.dba /dev/sdc1
chown -Rf oracle.dba /dev/sdd1
chown -Rf oracle.dba /dev/sde1
chown -Rf oracle.dba /dev/raw/raw1
chown -Rf oracle.dba /dev/raw/raw2
chown -Rf oracle.dba /dev/raw/raw3
chown -Rf oracle.dba /dev/raw/raw4

cd /opt/oracle/oradata/asmrac
ln -s /dev/raw/raw1 votedisk
ln -s /dev/raw/raw2 ocrdisk
ln -s /dev/raw/raw3 disk1
ln -s /dev/raw/raw4 disk2
–安装ASM工具和lib库
rpm -ivh oracleasm-support-2.0.3-1.x86_64.rpm
rpm -ivh oracleasm-2.6.9-42.ELsmp-2.0.3-1.x86_64.rpm
rpm -ivh oracleasmlib-2.0.2-1.x86_64.rpm

[root@hack3 oracle]# /etc/init.d/oracleasm configure
Configuring the Oracle ASM library driver.

This will configure the on-boot properties of the Oracle ASM library
driver. The following questions will determine whether the driver is
loaded on boot and what permissions it will have. The current values
will be shown in brackets (’[]’). Hitting <ENTER> without typing an
answer will keep that current value. Ctrl-C will abort.

Default user to own the driver interface []:
Default group to own the driver interface []:
Start Oracle ASM library driver on boot (y/n) [n]: y
Fix permissions of Oracle ASM disks on boot (y/n) [y]:
Writing Oracle ASM library driver configuration:           [ OK ]
Creating /dev/oracleasm mount point:                       [ OK ]
Loading module “oracleasm”:                                [ OK ]
Mounting ASMlib driver filesystem:                         [ OK ]
Scanning system for ASM disks:                             [ OK ]
作好上面的准备工作后，就开始安装clusterware了，把软件上传到一台服务器解压，
他基本是在一台安装，编译好，再scp到其他接点的,安装完后，需要运行root.sh，这个步骤最容易出错
下面列了下运行情况和遇到的错误解决

[root@hack3 install]# /opt/oracle/products/crs/root.sh
WARNING: directory ‘/opt/oracle/products’ is not owned by root
WARNING: directory ‘/opt/oracle’ is not owned by root
Checking to see if Oracle CRS stack is already configured
/etc/oracle does not exist. Creating it now.

Setting the permissions on OCR backup directory
Setting up NS directories
Oracle Cluster Registry configuration upgraded successfully
WARNING: directory ‘/opt/oracle/products’ is not owned by root
WARNING: directory ‘/opt/oracle’ is not owned by root
Successfully accumulated necessary OCR keys.
Using ports: CSS=49895 CRS=49896 EVMC=49898 and EVMR=49897.
node <nodenumber>: <nodename> <private interconnect name> <hostname>
node 1: hack3 hack3-priv hack3
node 2: hack4 hack4-priv hack4
Creating OCR keys for user ‘root’, privgrp ‘root’..
Operation successful.
Now formatting voting device: /opt/oracle/oradata/asmrac/votedisk
   Format of 1 voting devices complete.
Startup will be queued to init within 90 seconds.
Adding daemons to inittab
Expecting the CRS daemons to be up within 600 seconds.
CSS is active on these nodes.
        hack3
CSS is inactive on these nodes.
        hack4
Local node checking complete.
Run root.sh on remaining nodes to start CRS daemons.

[root@hack4 lib32]# /opt/oracle/products/crs/root.sh
WARNING: directory ‘/opt/oracle/products’ is not owned by root
WARNING: directory ‘/opt/oracle’ is not owned by root
Checking to see if Oracle CRS stack is already configured
/etc/oracle does not exist. Creating it now.

Setting the permissions on OCR backup directory
Setting up NS directories
Oracle Cluster Registry configuration upgraded successfully
WARNING: directory ‘/opt/oracle/products’ is not owned by root
WARNING: directory ‘/opt/oracle’ is not owned by root
clscfg: EXISTING configuration version 3 detected.
clscfg: version 3 is 10G Release 2.
Successfully accumulated necessary OCR keys.
Using ports: CSS=49895 CRS=49896 EVMC=49898 and EVMR=49897.
node <nodenumber>: <nodename> <private interconnect name> <hostname>
node 1: hack3 hack3-priv hack3
node 2: hack4 hack4-priv hack4
clscfg: Arguments check out successfully.

NO KEYS WERE WRITTEN. Supply -force parameter to override.
-force is destructive and will destroy any previous cluster
configuration.
Oracle Cluster Registry for cluster has already been initialized
Startup will be queued to init within 90 seconds.
Adding daemons to inittab
Expecting the CRS daemons to be up within 600 seconds.
CSS is active on these nodes.
hack3
hack4
CSS is active on all nodes.
Waiting for the Oracle CRSD and EVMD to start
Oracle CRS stack installed and running under init(1M)
Running vipca(silent) for configuring nodeapps
The given interface(s), “eth0″ is not public. Public interfaces should be used to configure virtual IPs.

–root.sh错误解决
1.直接出现Failed to upgrade Oracle Cluster Registry configuration，观察$CRS_HOME/logs/{node}/alert*日志，
发现有not set 0等字样
解决：不要直接使用共享lun，如/dev/sdb,一定要fdisk分区

2.rootconfig: line 815 Segmentation fault
解决：是gcc和g++有问题
1. cd /usr/bin
2. mv gcc gcc.script
3. mv g++ g++.script
4. ln -s gcc32 gcc
5. ln -s g++32 g++

3.运行完root.sh后，不能启动vipca，总是出错
PRKH-1010 : Unable to communicate with CRS services.
[PRKH-1000 : Unable to load the SRVM HAS shared library
[PRKN-1008 : Unable to load the shared library “srvmhas10″
解决：参考metalink Note:342750.1
在64bit linux上缺少32位的glibc-devel包，导致有些库文件链接出错，从$CRS_HOME/install 下的make log里面可以看到
错误信息
我这边下了
glibc-common-2.3.4-2.39.i386.rpm
glibc-2.3.4-2.39.i386.rpm
glibc-headers-2.3.4-2.39.i386.rpm
glibc-devel-2.3.4-2.39.i386.rpm
安装的时候注意顺序
4.如何清理安装失败的CRS
$CRS_HOME/install/rootdeinstall.sh
$CRS_HOME/install/rootdelete.sh
ps -ef | grep crs
kill <crs pid>
ps -ef | grep evm
kill <evm pid>
ps -ef | grep css
kill <css pid>

dd if=/dev/zero of=/opt/oracle/oradata/asmrac/votedisk bs=8192 count=2560
dd if=/dev/zero of=/opt/oracle/oradata/asmrac/ocrdisk bs=8192 count=12800

干掉CRS_HOME目录下的所有东西
rm -rf /var/tmp/.oracle
rm -rf /tmp/.oracle
rm -rf /etc/oracle
rm -rf /opt/oracle/oraInventory/*
rm -rf /opt/oracle/products/crs/*
到此clusterware安装完毕，可以再直接安装oracle数据库软件，这个比较顺利，就不多说了

00:21 安装Perl DBI模块 (1482 Bytes) » NinGoo@Net

Author:NinGoo posted on NinGoo.net

打算熟悉下perl，自然主要用于数据库管理和监控方面的，所以需要连接数据库。Perl连接数据库可以通过DBI或者DBD模块，Linux上默认安装的Perl是没有该模块的。可以从CPAN下载DBI模块进行安装。

安装过程很简单，下载解压：

gzip -d DBI-1.604.tar.gz
tar xvf DBI-1.604.tar

然后进入DBI-1.604目录，执行：

perl Makefile.PL
make
make test
make install

以下脚本可以用来检测系统中已经安装的Perl模块：

#!/usr/bin/perl
use ExtUtils::Installed;

my $inst = ExtUtils::Installed->new();
print join “\n”,$inst->modules();

安装完DBI后执行该脚本的结果如下：

# ./perl-module.pl
DBI
Perl

DBI的文档可以通过perldoc查看：

#perldoc DBI

Related Articles

Add Comments(0)

23:58 IE8与淘宝的亲密接触 - 新特性，新的用户体验 » Fenng's shared items in Google Reader