您的位置:首页 > 其它

dispatcher 'D000' encountered error getting listening address

2013-07-28 13:47 791 查看
一次闪回数据库操作实验中,在日志文件中出现以下错误:

found dead dispatcher 'D000', pid = (20, 86)

Sat Jul 27 03:22:22 2013

dispatcher 'D000' encountered error getting listening address

一、查找对应的错误记录文件:

[oracle@pc-centos /]$ cd $ORACLE_BASE/diag/rdbms/orcl/orcl/trace

[oracle@pc-centos trace]$ ls -rlt

......

-rw-r-----. 1 oracle oinstall 4392 Jul 27 03:22 orcl_d000_20094.trc

-rw-r-----. 1 oracle oinstall 232 Jul 27 03:22 orcl_d000_20097.trm

-rw-r-----. 1 oracle oinstall 4392 Jul 27 03:22 orcl_d000_20097.trc

[oracle@pc-centos trace]$ tail -f -n 100 orcl_d000_20097.trc

*** 2013-07-27 03:22:25.070

*** CLIENT ID:() 2013-07-27 03:22:25.070

*** SERVICE NAME:() 2013-07-27 03:22:25.070

*** MODULE NAME:() 2013-07-27 03:22:25.070

*** ACTION NAME:() 2013-07-27 03:22:25.070

network error encountered getting listening address:

NS Primary Error: TNS-12533: TNS:illegal ADDRESS parameters

NS Secondary Error: TNS-12560: TNS:protocol adapter error

NT Generic Error: TNS-00503: Illegal ADDRESS parameters

OPIRIP: Uncaught error 108. Error stack:

ORA-00108: failed to set up dispatcher to accept connection asynchronously

二、问题原因:

[root@pc-centos 2013_07_25]# hostname

pc-centos

[root@pc-centos 2013_07_25]# ping pc-centos

ping: unknown host pc-centos

[root@pc-centos 2013_07_25]# ifconfig

eth0 Link encap:Ethernet HWaddr 08:00:27:8A:6D:BA

inet addr:169.254.225.101 Bcast:169.254.225.255 Mask:255.255.255.0

inet6 addr: fe80::a00:27ff:fe8a:6dba/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:17673 errors:0 dropped:0 overruns:0 frame:0

TX packets:12939 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:1720163 (1.6 MiB) TX bytes:11525745 (10.9 MiB)

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING MTU:16436 Metric:1

RX packets:30136 errors:0 dropped:0 overruns:0 frame:0

TX packets:30136 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:1511250 (1.4 MiB) TX bytes:1511250 (1.4 MiB)

[root@pc-centos 2013_07_25]# ping 169.254.225.101

PING 169.254.225.101 (169.254.225.101) 56(84) bytes of data.

64 bytes from 169.254.225.101: icmp_seq=1 ttl=64 time=0.054 ms

64 bytes from 169.254.225.101: icmp_seq=2 ttl=64 time=0.042 ms

^C

--- 169.254.225.101 ping statistics ---

2 packets transmitted, 2 received, 0% packet loss, time 1981ms

rtt min/avg/max/mdev = 0.042/0.048/0.054/0.006 ms

原因:主机名不能被正常访问导致。

进行如下修改:

[root@pc-centos 2013_07_25]# vi /etc/hosts

127.0.0.1 localhost.localdomain localhost

169.254.225.101 pc-centos

HOSTNAME=pc-centos

[root@pc-centos 2013_07_25]# ping pc-centos

PING pc-centos (169.254.225.101) 56(84) bytes of data.

64 bytes from pc-centos (169.254.225.101): icmp_seq=1 ttl=64 time=0.024 ms

64 bytes from pc-centos (169.254.225.101): icmp_seq=2 ttl=64 time=0.035 ms

^C

--- pc-centos ping statistics ---

2 packets transmitted, 2 received, 0% packet loss, time 1742ms

rtt min/avg/max/mdev = 0.024/0.029/0.035/0.007 ms

三、重新启动ORACLE服务,观察d000进程

SQL> shutdown immediate;

Database closed.

Database dismounted.

ORACLE instance shut down.

SQL> startup;

ORACLE instance started.

Total System Global Area 451981312 bytes

Fixed Size 1337100 bytes

Variable Size 331352308 bytes

Database Buffers 113246208 bytes

Redo Buffers 6045696 bytes

Database mounted.

Database opened.

SQL> exit

Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

[oracle@pc-centos 2013_07_26]$ ps -ef | grep oracle

........

.......

oracle 20660 1 0 03:31 ? 00:00:00 ora_d000_orcl

...........

oracle 20732 9735 0 03:31 pts/2 00:00:00 ps -ef

oracle 20733 9735 0 03:31 pts/2 00:00:00 grep oracle

四、观察日志文件:

[oracle@pc-centos orcl]$ cd $ORACLE_BASE/diag/rdbms/orcl/orcl/trace

[oracle@pc-centos trace]$ tail -f -n 300 alert_orcl.log

Starting up:

Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options.

Using parameter settings in server-side spfile /u01/app/oracle/product/11.2.0/dbhome_1/dbs/spfileorcl.ora

System parameters with non-default values:

processes = 150

sga_max_size = 432M

large_pool_size = 52M

memory_target = 800M

control_files = "/u01/app/oracle/oradata/orcl/control01.ctl"

control_files = "/u01/app/oracle/oradata/orcl/control02.ctl"

control_files = "/u01/app/oracle/oradata/orcl/control03.ctl"

db_block_size = 8192

db_writer_processes = 2

compatible = "11.2.0.0.0"

db_files = 200

db_recovery_file_dest = "/u01/app/oracle/flash_recovery_area"

db_recovery_file_dest_size= 10G

fast_start_mttr_target = 900

undo_tablespace = "UNDOTBS1"

O7_DICTIONARY_ACCESSIBILITY= FALSE

remote_login_passwordfile= "EXCLUSIVE"

db_domain = ""

dispatchers = "(PROTOCOL=TCP) (SERVICE=orclXDB)"

local_listener = "(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.56.101)))"

audit_file_dest = "/u01/app/oracle/admin/orcl/adump"

audit_trail = "DB"

db_name = "orcl"

open_cursors = 300

os_authent_prefix = ""

pga_aggregate_target = 268M

optimizer_capture_sql_plan_baselines= TRUE

diagnostic_dest = "/u01/app/oracle"

Sat Jul 27 03:31:13 2013

PMON started with pid=2, OS id=20626

Sat Jul 27 03:31:13 2013

VKTM started with pid=3, OS id=20628

VKTM running at (100ms) precision

Sat Jul 27 03:31:13 2013

GEN0 started with pid=4, OS id=20632

Sat Jul 27 03:31:13 2013

DIAG started with pid=5, OS id=20634

Sat Jul 27 03:31:13 2013

DBRM started with pid=6, OS id=20636

Sat Jul 27 03:31:13 2013

PSP0 started with pid=7, OS id=20638

Sat Jul 27 03:31:13 2013

DIA0 started with pid=8, OS id=20640

Sat Jul 27 03:31:13 2013

MMAN started with pid=9, OS id=20642

Sat Jul 27 03:31:13 2013

DBW0 started with pid=10, OS id=20644

Sat Jul 27 03:31:13 2013

DBW1 started with pid=11, OS id=20646

Sat Jul 27 03:31:13 2013

LGWR started with pid=12, OS id=20648

Sat Jul 27 03:31:13 2013

CKPT started with pid=13, OS id=20650

Sat Jul 27 03:31:13 2013

SMON started with pid=14, OS id=20652

Sat Jul 27 03:31:13 2013

RECO started with pid=15, OS id=20654

Sat Jul 27 03:31:13 2013

MMON started with pid=16, OS id=20656

starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...

Sat Jul 27 03:31:13 2013

MMNL started with pid=17, OS id=20658

starting up 1 shared server(s) ...

ORACLE_BASE from environment = /u01/app/oracle

Sat Jul 27 03:31:14 2013

ALTER DATABASE MOUNT

Successful mount of redo thread 1, with mount id 1349632258

Allocated 3981204 bytes in shared pool for flashback generation buffer

Starting background process RVWR

Sat Jul 27 03:31:18 2013

RVWR started with pid=21, OS id=20694

Database mounted in Exclusive Mode

Lost write protection disabled

Completed: ALTER DATABASE MOUNT

Sat Jul 27 03:31:18 2013

ALTER DATABASE OPEN

Block change tracking file is current.

LGWR: STARTING ARCH PROCESSES

Sat Jul 27 03:31:18 2013

ARC0 started with pid=22, OS id=20697

ARC0: Archival started

LGWR: STARTING ARCH PROCESSES COMPLETE

ARC0: STARTING ARCH PROCESSES

Sat Jul 27 03:31:19 2013

ARC1 started with pid=23, OS id=20699

Sat Jul 27 03:31:19 2013

ARC2 started with pid=24, OS id=20701

ARC1: Archival started

ARC2: Archival started

ARC1: Becoming the 'no FAL' ARCH

ARC1: Becoming the 'no SRL' ARCH

ARC2: Becoming the heartbeat ARCH

Sat Jul 27 03:31:19 2013

ARC3 started with pid=25, OS id=20703

Thread 1 opened at log sequence 1

Current log# 1 seq# 1 mem# 0: /u01/app/oracle/oradata/orcl/redo01.log

Successful open of redo thread 1

Starting background process CTWR

Sat Jul 27 03:31:19 2013

CTWR started with pid=26, OS id=20705

Block change tracking service is active.

SMON: enabling cache recovery

Successfully onlined Undo Tablespace 2.

Verifying file header compatibility for 11g tablespace encryption..

Verifying 11g file header compatibility for tablespace encryption completed

SMON: enabling tx recovery

Database Characterset is WE8MSWIN1252

No Resource Manager plan active

replication_dependency_tracking turned off (no async multimaster replication found)

Starting background process QMNC

Sat Jul 27 03:31:20 2013

QMNC started with pid=27, OS id=20707

Completed: ALTER DATABASE OPEN

Sat Jul 27 03:31:20 2013

db_recovery_file_dest_size of 10240 MB is 22.36% used. This is a

user-specified limit on the amount of space that will be used by this

database for recovery-related files, and does not reflect the amount of

space available in the underlying filesystem or ASM diskgroup.

ARC3: Archival started

ARC0: STARTING ARCH PROCESSES COMPLETE

Starting background process CJQ0

Sat Jul 27 03:31:22 2013

CJQ0 started with pid=28, OS id=20721

已无相关报错信息
内容来自用户分享和网络整理,不保证内容的准确性,如有侵权内容,可联系管理员处理 点击这里给我发消息
标签: 
相关文章推荐