Shulou(Shulou.com)06/01 Report--

Environment:

Oracle 10.2.0.4, Red Hat Linux4.5 32bit

International Working Women's Day that day, a DB server died due to a hardware failure. Fix the restored DB to the new server through backup, and the hard disk will be full soon after the restored DB is enabled. Check the DB bdump directory to write a large number of trc files, and alert.log keeps reporting errors after open:

Fri Mar 9 04:19:59 2018

Dispatcher 'D000' encountered error getting listening address

Fri Mar 9 04:19:59 2018

Errors in file / u01/product/admin/umlaut/bdump/umlaut_ora_20942.trc:

ORA-07445: exception encountered: core dump [kslgetl () + 80] [SIGSEGV] [Address not mapped to object] [0x130] [] []

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

Fri Mar 9 04:20:02 2018

Found dead dispatcher 'D000mm, pid = (13,219)

Fri Mar 9 04:20:02 2018

Dispatcher 'D000' encountered error getting listening address

Fri Mar 9 04:20:02 2018

Errors in file / u01/product/admin/umlaut/bdump/umlaut_ora_20944.trc:

ORA-07445: exception encountered: core dump [kslgetl () + 80] [SIGSEGV] [Address not mapped to object] [0x130] [] []

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

....

Contents of trc file:

Oracle Database 10g Enterprise Edition Release 10.2.0.4.0-Production

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

ORACLE_HOME = / u01/product/oracle

System name: Linux

Node name: dthistory02

Release: 2.6.9-55.ELsmp

Version: # 1 SMP Fri Apr 20 17:03:35 EDT 2007

Machine: i686

Instance name: umlaut

Redo thread mounted by this instance: 1

Oracle process number: 13

Unix process pid: 18998, image: oracle@dthistory02 (D000)

Warning: keltnfy call to ldmInit failed with error 46

* * 2018-03-09 03 purl 42purl 51.581

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

Exception signal: 11 (SIGSEGV), code: 1 (Address not mapped to object), addr: 0x130, PC: [0x831f388, kslgetl () + 80]

Registers:

% eax: 0x00000000% ebx: 0x00000007% ecx: 0x00001768

% edx: 0x00003980% edi: 0x20098a44% esi: 0x00000000

% esp: 0xbffff188% ebp: 0xbffff194% eip: 0x0831f388

% efl: 0x00010246

Kslgetl () + 57 (0x831f371) jnz 0x831f5a2

Kslgetl () + 63 (0x831f377) mov 0xce77488% ESI

Kslgetl () + 69 (0x831f37d) mov 0xc (% edi),% ebx

Kslgetl () + 72 (0x831f380) movzw 0xc1e0d20 (,% ebx,2),% edx

> kslgetl () + 80 (0x831f388) test edx,0x130 (% esi)

Kslgetl () + 86 (0x831f38e) lea 0x9c (% esi),% eax

Kslgetl () + 92 (0x831f394) jnz 0x831f58c

Kslgetl () + 98 (0x831f39a) test ebx,%ebx

Kslgetl () + 100 (0x831f39c) jl 0x831f4e7

* * 2018-03-09 03 purl 42purl 51.583

Ksedmp: internal or fatal error

ORA-07445: exception encountered: core dump [kslgetl () + 80] [SIGSEGV] [Address not mapped to object] [0x130] [] []

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

Current SQL information unavailable-no session.

Check the MOS article: ORA-07445: [kslgetl () + 80] Followed by ORA-108: failed to set up dispatcher to accept connection asynchronously (ID 1298804.1) is basically the same as the error report. It is found that this problem is mainly related to hostname and hosts settings.

Check the configuration:

# hostname

Dthistory02

# cat / etc/hosts

10.10.10.191 dt history02 localhost

Sure enough, there is no error after modifying / etc/hosts (there is no need to restart DB). This problem is solved.

Attached: document ID 1298804.1

ORA-07445: [kslgetl () + 80] Followed by ORA-108: failed to set up dispatcher to accept connection asynchronously

APPLIES TO:Oracle Net Services-Version 11.1.0.7 and later

Information in this document applies to any platform.

SYMPTOMS

The following errors are seen in the trace file written by an ORA-7445 [kslgetl]:

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

Exception signal: 11 (SIGSEGV), code: 1 (Address not mapped to object), addr: 0x130, PC: [0x82f09dc, kslgetl () + 80]

The trace file indicates that there is no session:

Current SQL information unavailable-no session.

The Call Stack Trace in the ORA-7445 trace file contains a function list similar to:

Kslgetl

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.