..experience – 第 18 页

sqlnet文件格式导致侦听无法启动

2009-09-04 4条评论

今天凌晨接到某省的一个电话，数据库进行MC service guard的切换，但是切换过去后，发现侦听无法启动，启动时侦听报错信息为：

oracle@ha_dc02:/oracle/app/oracle/product/9.2.0/network/admin > lsnrctl start

LSNRCTL for HPUX: Version 9.2.0.6.0 - Production on 04-SEP-2009 01:46:07

Copyright (c) 1991, 2002, Oracle Corporation.  All rights reserved.

Starting /oracle/app/oracle/product/9.2.0/bin/tnslsnr: please wait...

TNSLSNR for HPUX: Version 9.2.0.6.0 - Production
System parameter file is /oracle/app/oracle/product/9.2.0/network/admin/listener.ora
Log messages written to /oracle/app/oracle/product/9.2.0/network/log/listener.log
Error listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.203.41.11)(PORT=1521)))
TNS-12532: TNS:invalid argument
 TNS-12560: TNS:protocol adapter error
  TNS-00502: Invalid argument


Listener failed to start. See the error message(s) above...

oracle@ha_dc02:/oracle/app/oracle/product/9.2.0/network/admin >

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

oracle@ha_dc02:/oracle/app/oracle/product/9.2.0/network/admin > lsnrctl start

LSNRCTL for HPUX: Version 9.2.0.6.0 - Production on 04-SEP-2009 01:46:07

Starting /oracle/app/oracle/product/9.2.0/bin/tnslsnr: please wait...

TNSLSNR for HPUX: Version 9.2.0.6.0 - Production

System parameter file is /oracle/app/oracle/product/9.2.0/network/admin/listener.ora

Log messages written to /oracle/app/oracle/product/9.2.0/network/log/listener.log

Error listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.203.41.11)(PORT=1521)))

TNS-12532: TNS:invalid argument

TNS-12560: TNS:protocol adapter error

TNS-00502: Invalid argument

Listener failed to start. See the error message(s) above...

oracle@ha_dc02:/oracle/app/oracle/product/9.2.0/network/admin >

检查配置，网络，都没有问题，浮动IP也是启动在10.203.41.11上，但是侦听就是起不来，检查 […]

..experience, Working case

用crs实现single instance的HA

2009-08-06 6条评论

数据库的高可用方案我们通常采用的是双机热备模式，一个机器跑主机，另一个机器进行standby。当发生故障的时候，故障机上的数据库被切换到备机，在备机上起浮动IP和数据库，对应用来讲是透明的，只是发生了短暂的切换。目前行业中常用的高可用软件如HP的Service Guard、IBM的HACMP，价格都 […]

..experience, Working case

启动lnsr需要写tmp权限

2009-07-29 6条评论

今天凌晨被叫醒起来，某省的数据库db01坏了一个cpu，由于有HA架构的保护，切换到了db02，但是在db02上却无法启动侦听，以下是报错信息：

oracle@gz_dc02:/oracle/app/oracle/admin/gzmisc/bdump > lsnrctl start

LSNRCTL for HPUX: Version 9.2.0.6.0 - Production on 29-JUL-2009 03:53:16

Copyright (c) 1991, 2002, Oracle Corporation.  All rights reserved.

Starting /oracle/app/oracle/product/9.2.0/bin/tnslsnr: please wait...

TNSLSNR for HPUX: Version 9.2.0.6.0 - Production
System parameter file is /oracle/app/oracle/product/9.2.0/network/admin/listener.ora
Log messages written to /oracle/app/oracle/product/9.2.0/network/log/listener.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.203.104.11)(PORT=1521)))
Error listening on: (ADDRESS=(PROTOCOL=ipc)(PARTIAL=yes)(QUEUESIZE=1))
No longer listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.203.104.11)(PORT=1521)))
TNS-12541: TNS:no listener
 TNS-12560: TNS:protocol adapter error
  TNS-00511: No listener
   HPUX Error: 2: No such file or directory

Listener failed to start. See the error message(s) above...

oracle@gz_dc02:/oracle/app/oracle/admin/gzmisc/bdump >

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

oracle@gz_dc02:/oracle/app/oracle/admin/gzmisc/bdump > lsnrctl start

LSNRCTL for HPUX: Version 9.2.0.6.0 - Production on 29-JUL-2009 03:53:16

Starting /oracle/app/oracle/product/9.2.0/bin/tnslsnr: please wait...

TNSLSNR for HPUX: Version 9.2.0.6.0 - Production

System parameter file is /oracle/app/oracle/product/9.2.0/network/admin/listener.ora

Log messages written to /oracle/app/oracle/product/9.2.0/network/log/listener.log

Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.203.104.11)(PORT=1521)))

Error listening on: (ADDRESS=(PROTOCOL=ipc)(PARTIAL=yes)(QUEUESIZE=1))

No longer listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.203.104.11)(PORT=1521)))

TNS-12541: TNS:no listener

TNS-12560: TNS:protocol adapter error

TNS-00511: No listener

HPUX Error: 2: No such file or directory

Listener failed to start. See the error message(s) above...

oracle@gz_dc02:/oracle/app/oracle/admin/gzmisc/bdump >

看报错很奇怪：Error listening on: (ADDRESS=(PROTOCO […]

..experience, Working case

设置侦听IP鉴权一段时间后侦听挂死

2009-07-24 一条评论

某省的数据库时不时的发生侦听挂死的现象。我们来看看具体的情况：当出现侦听挂死的时候，sqlplus登录会出现如下报错：

$ sqlplus user/pwd@tnsnames

SQL*Plus: Release 9.2.0.6.0 - Production on Sun Jun 28 11:43:32 2009

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.


ERROR:
ORA-12535: TNS:operation timed out
$

1

2

3

4

5

6

7

8

9

10

$ sqlplus user/pwd@tnsnames

SQL*Plus: Release 9.2.0.6.0 - Production on Sun Jun 28 11:43:32 2009

ERROR:

ORA-12535: TNS:operation timed out

$

而此时，可以看到listener.log中的内容为： [crayon-664332af9f87923196370 […]

..experience, Working case

ntp服务的安装

2009-07-04 3条评论

在rac环境中，会要求几个节点之间的时间差不能超时。一般如果超过30秒，节点很可能会重启。我们需要配置一个ntp时钟服务器，来给rac的各个节点进行时间同步。在这里，我们以windows机器（192.168.1.189）做ntp server，以2台虚拟机上的rac节点（192.168.1.131 […]

..experience, Working case

安腾平台的legato的lib link

2009-06-29 2条评论

某省新上安腾平台的oracle，备份软件是legato，首先在安腾的机器上安装了networker.pkg和nmo.pkg，配置好client后，发现备份失败。查/nsr/applogs/msglog.log发现：

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of allocate command on t1 channel at 06/29/2009 11:55:45
ORA-19554: error allocating device, device type: SBT_TAPE, device name: 
ORA-27211: Failed to load Media Management Library
Additional information: 25

1

2

3

4

5

6

7

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03009: failure of allocate command on t1 channel at 06/29/2009 11:55:45

ORA-19554: error allocating device, device type: SBT_TAPE, device name:

ORA-27211: Failed to load Media Management Library

Additional information: 25

对于这个报错，我已 […]

..experience, Working case

rac安装报错和修复小结

2009-06-27 2条评论

一、rac安装步骤主要分以下几步： 1、安装操作系统。 2、配置时间同步，如ntp 3、创建oracle用户和配置rsa和dsa 4、配置hosts文件 5、配置hangcheck-timer 6、配置共享存储（ocr和voting disk） 7、安装clusterware（crs） 8、配置as […]

..experience, Working case

swap空间不够导致连接侦听失败

2009-06-16 3条评论

早上4点多就被叫起来，说某现网的数据库侦听挂了。数据库连不上去，报以下的错误：

$ sqlplus user/pwd@sid

SQL*Plus: Release 9.2.0.6.0 - Production on Fri Jun 12 04:58:05 2009

Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.

ERROR:
ORA-12500: TNS:listener failed to start a dedicated server process

1

2

3

4

5

6

7

8

$ sqlplus user/pwd@sid

SQL*Plus: Release 9.2.0.6.0 - Production on Fri Jun 12 04:58:05 2009

ERROR:

ORA-12500: TNS:listener failed to start a dedicated server process

登录后检查数据库的侦听进程还在，检查lsnrctl status的状态也是正常。检查侦听的log发现，有大量连接拒连： [crayon-664332af […]

..experience, Working case

修改hosts后，rac通讯失败

2009-06-15 没有评论

今天收到个告警某省的一个数据库的一个节点down了，重启后，只能到started状态，数据库无法open，登录上去后，看到alertlog中：

Mon Jun 15 15:38:28 2009
Errors in file /oracle/app/oracle/admin/fjmisc/udump/fjmisc2_ora_26950.trc:
ORA-00603: ORACLE server session terminated by fatal error
ORA-27504: IPC error creating OSD context
ORA-27300: OS system dependent operation:gethostbyname failed with status: 3
ORA-27301: OS failure message: No such process
ORA-27302: failure occurred at: sskgxpmyip2
ORA-27303: additional information: nodename FJ_DB02
 Mon Jun 15 15:41:19 2009
Errors in file /oracle/app/oracle/admin/fjmisc/udump/fjmisc2_ora_27062.trc:
ORA-00603: ORACLE server session terminated by fatal error
ORA-27504: IPC error creating OSD context
ORA-27300: OS system dependent operation:gethostbyname failed with status: 3
ORA-27301: OS failure message: No such process
ORA-27302: failure occurred at: sskgxpmyip2
ORA-27303: additional information: nodename FJ_DB02
Mon Jun 15 15:42:37 2009
Errors in file /oracle/app/oracle/admin/fjmisc/udump/fjmisc2_ora_27147.trc:
ORA-00603: ORACLE server session terminated by fatal error
ORA-27504: IPC error creating OSD context
ORA-27300: OS system dependent operation:gethostbyname failed with status: 3
ORA-27301: OS failure message: No such process
ORA-27302: failure occurred at: sskgxpmyip2
ORA-27303: additional information: nodename FJ_DB02
 Mon Jun 15 15:46:19 2009
Errors in file /oracle/app/oracle/admin/fjmisc/udump/fjmisc2_ora_27362.trc:
ORA-00603: ORACLE server session terminated by fatal error
ORA-27504: IPC error creating OSD context

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

Mon Jun 15 15:38:28 2009

Errors in file /oracle/app/oracle/admin/fjmisc/udump/fjmisc2_ora_26950.trc:

ORA-00603: ORACLE server session terminated by fatal error

ORA-27504: IPC error creating OSD context

ORA-27300: OS system dependent operation:gethostbyname failed with status: 3

ORA-27301: OS failure message: No such process

ORA-27302: failure occurred at: sskgxpmyip2

ORA-27303: additional information: nodename FJ_DB02

Mon Jun 15 15:41:19 2009

Errors in file /oracle/app/oracle/admin/fjmisc/udump/fjmisc2_ora_27062.trc:

ORA-00603: ORACLE server session terminated by fatal error

ORA-27504: IPC error creating OSD context

ORA-27300: OS system dependent operation:gethostbyname failed with status: 3

ORA-27301: OS failure message: No such process

ORA-27302: failure occurred at: sskgxpmyip2

ORA-27303: additional information: nodename FJ_DB02

Mon Jun 15 15:42:37 2009

Errors in file /oracle/app/oracle/admin/fjmisc/udump/fjmisc2_ora_27147.trc:

ORA-00603: ORACLE server session terminated by fatal error

ORA-27504: IPC error creating OSD context

ORA-27300: OS system dependent operation:gethostbyname failed with status: 3

ORA-27301: OS failure message: No such process

ORA-27302: failure occurred at: sskgxpmyip2

ORA-27303: additional information: nodename FJ_DB02

Mon Jun 15 15:46:19 2009

Errors in file /oracle/app/oracle/admin/fjmisc/udump/fjmisc2_ora_27362.trc:

ORA-00603: ORACLE server session terminated by fatal error

ORA-27504: IPC error creating OSD context

当时第一个反映是gethostbyname failed 应该是主机名解析有问题了。但是p […]

..experience, Working case

主机安全加固导致dp分发客户端失败

2009-06-14 没有评论

今年的315晚会，曝光了某省移动的一些违规操作后，移动集团公司对各地分公司都进行了安全检查。在进行一系列的安全加固操作后，我们发现，还是有部分之前很顺利的操作会受到影响。问题的起因是这样的，某省的备份软件是HP的DP。DP能对数据库进行备份，也能对文件系统进行备份（这样的功能，我想一般的备份软件都 […]

..experience, Working case

用hanganalyze解决row cache lock

2009-05-20 3条评论

今天某省的一位同事来说，在执行一个split分区的脚本时长时间没有响应。登录上去查看，手工执行了split脚本，发现确实会hang住：

SQL> l
  1  ALTER TABLE A_PDA_SP_STAT SPLIT PARTITION P_MAX AT (20090609)
  2   INTO (PARTITION P_20090608 TABLESPACE TS_DATA_A
  3*  , PARTITION P_MAX TABLESPACE TS_DATA_A)
SQL>

1

2

3

4

5

SQL> l

1 ALTER TABLE A_PDA_SP_STAT SPLIT PARTITION P_MAX AT (20090609)

2 INTO (PARTITION P_20090608 TABLESPACE TS_DATA_A

3* , PARTITION P_MAX TABLESPACE TS_DATA_A)

SQL>

检查该session的等待事件：

EVENT                                  P1         P2         P3
------------------------------ ---------- ---------- ----------
row cache lock                          8          0          5

1

2

3

EVENT P1 P2 P3

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

row cache lock 8 0 5

[…]

..experience, Working case

rman备份发现坏块之后的处理

2009-04-20 8条评论

今天收到某省的备份发生失败的告警：

……
四月 16 16:30:19 ur_bak01: NetWorker savegroup: (alert) urmdborafull completed, total 2 client(s), 0 Hostname(s) Unresolved, 1 Failed, 1 Succeeded. (ur_mdb01 Failed)
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on t2 channel at 03/20/2009 13:49:09
ORA-19566: exceeded limit of 0 corrupt blocks for file /dev/vg_mdb02/rdata_2g_050
ORA-000060: Deadlock detected. More info in file /oracle/app/oracle/admin/uradt/udump/uradt_ora_3035.trc.
***
Corrupt block relative dba: 0x1a43d4e3 (file 105, block 251107)
Fractured block found during backing up datafile
Data in bad block -
 type: 0 format: 0 rdba: 0x00000000
 last change scn: 0x0000.00000000 seq: 0x0 flg: 0x00
 consistency value in tail: 0x00000000
 check value in block header: 0x0, block checksum disabled
 spare1: 0x0, spare2: 0x0, spare3: 0x0
***
Reread of blocknum=251107, file=/dev/vg_mdb02/rdata_2g_050. found same corrupt data
Thu Apr 16 16:31:04 2009
……

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

……

四月 16 16:30:19 ur_bak01: NetWorker savegroup: (alert) urmdborafull completed, total 2 client(s), 0 Hostname(s) Unresolved, 1 Failed, 1 Succeeded. (ur_mdb01 Failed)

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03009: failure of backup command on t2 channel at 03/20/2009 13:49:09

ORA-19566: exceeded limit of 0 corrupt blocks for file /dev/vg_mdb02/rdata_2g_050

ORA-000060: Deadlock detected. More info in file /oracle/app/oracle/admin/uradt/udump/uradt_ora_3035.trc.

***

Corrupt block relative dba: 0x1a43d4e3 (file 105, block 251107)

Fractured block found during backing up datafile

Data in bad block -

type: 0 format: 0 rdba: 0x00000000

last change scn: 0x0000.00000000 seq: 0x0 flg: 0x00

consistency value in tail: 0x00000000

check value in block header: 0x0, block checksum disabled

spare1: 0x0, spare2: 0x0, spare3: 0x0

***

Reread of blocknum=251107, file=/dev/vg_mdb02/rdata_2g_050. found same corrupt data

Thu Apr 16 16:31:04 2009

……

用dbv检查发现有至少有45个坏块：

[oracle@ur_mdb01 /oracle$]dbv file=/dev/vg_mdb02/rdata_2g_050 BLOCKSIZE=8192

DBVERIFY: Release 9.2.0.6.0 - Production on Mon Apr 20 09:55:07 2009

Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.

DBVERIFY - Verification starting : FILE = /dev/vg_mdb02/rdata_2g_050
Page 251107 is influx - most likely media corrupt
***
Corrupt block relative dba: 0x1a43d4e3 (file 105, block 251107)
Fractured block found during dbv: 
Data in bad block -
 type: 0 format: 0 rdba: 0x00000000
 last change scn: 0x0000.00000000 seq: 0x0 flg: 0x00
 consistency value in tail: 0x00000000
 check value in block header: 0x0, block checksum disabled
 spare1: 0x0, spare2: 0x0, spare3: 0x0
***

Page 251108 is marked corrupt
***
Corrupt block relative dba: 0x1a43d4e4 (file 105, block 251108)
Bad header found during dbv: 
Data in bad block -
 type: 181 format: 6 rdba: 0x00000000
 last change scn: 0x0000.00000000 seq: 0x0 flg: 0x00
 consistency value in tail: 0x00000000
 check value in block header: 0x0, block checksum disabled
 spare1: 0x7, spare2: 0xc, spare3: 0x0
***

……

Corrupt block relative dba: 0x1a43d56f (file 105, block 251247)
Bad header found during dbv: 
Data in bad block -
 type: 65 format: 5 rdba: 0x527002c2
 last change scn: 0x3131.02063033 seq: 0x30 flg: 0x31
 consistency value in tail: 0x3635032d
 check value in block header: 0x180, block checksum disabled
 spare1: 0x50, spare2: 0x72, spare3: 0x430
***



DBVERIFY - Verification complete

Total Pages Examined         : 262016
Total Pages Processed (Data) : 60240
Total Pages Failing   (Data) : 0
Total Pages Processed (Index): 0
Total Pages Failing   (Index): 0
Total Pages Processed (Other): 568
Total Pages Processed (Seg)  : 0
Total Pages Failing   (Seg)  : 0
Total Pages Empty            : 201163
Total Pages Marked Corrupt   : 45
Total Pages Influx           : 11
Highest block SCN            : 10816042273 (2.2226107681)

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

[oracle@ur_mdb01 /oracle$]dbv file=/dev/vg_mdb02/rdata_2g_050 BLOCKSIZE=8192

DBVERIFY: Release 9.2.0.6.0 - Production on Mon Apr 20 09:55:07 2009

DBVERIFY - Verification starting : FILE = /dev/vg_mdb02/rdata_2g_050

Page 251107 is influx - most likely media corrupt

***

Corrupt block relative dba: 0x1a43d4e3 (file 105, block 251107)

Fractured block found during dbv:

Data in bad block -

type: 0 format: 0 rdba: 0x00000000

last change scn: 0x0000.00000000 seq: 0x0 flg: 0x00

consistency value in tail: 0x00000000

check value in block header: 0x0, block checksum disabled

spare1: 0x0, spare2: 0x0, spare3: 0x0

***

Page 251108 is marked corrupt

***

Corrupt block relative dba: 0x1a43d4e4 (file 105, block 251108)

Bad header found during dbv:

Data in bad block -

type: 181 format: 6 rdba: 0x00000000

last change scn: 0x0000.00000000 seq: 0x0 flg: 0x00

consistency value in tail: 0x00000000

check value in block header: 0x0, block checksum disabled

spare1: 0x7, spare2: 0xc, spare3: 0x0

***

……

Corrupt block relative dba: 0x1a43d56f (file 105, block 251247)

Bad header found during dbv:

Data in bad block -

type: 65 format: 5 rdba: 0x527002c2

last change scn: 0x3131.02063033 seq: 0x30 flg: 0x31

consistency value in tail: 0x3635032d

check value in block header: 0x180, block checksum disabled

spare1: 0x50, spare2: 0x72, spare3: 0x430

***

DBVERIFY - Verification complete

Total Pages Examined : 262016

Total Pages Processed (Data) : 60240

Total Pages Failing (Data) : 0

Total Pages Processed (Index): 0

Total Pages Failing (Index): 0

Total Pages Processed (Other): 568

Total Pages Processed (Seg) : 0

Total Pages Failing (Seg) : 0

Total Pages Empty : 201163

Total Pages Marked Corrupt : 45

Total Pages Influx : 11

Highest block SCN : 10816042273 (2.2226107681)

经检查，发现这些坏块上没有任何数据对象： [crayon-664332afa766546044 […]