asked on

Errors in DB alert log file

Hi,
Oracle RDBMS version 11.2.0.3.0
O.S.: IBM/AIX

I have noticed many errors (hundreds) in DB alert log file like this:

Fatal NI connect error 12537, connecting to:
(LOCAL=NO)

VERSION INFORMATION:
TNS for IBM/AIX Version 11.2.0.3.0 - Production
TCP/IP NT Protocol Adapter for IBM/AIX Version 11.2.0.3.0 - Production
Time: 09-APR-2013
Tracing not turned on.
Tns error struct:
ns main err code: 12537

TNS-12537: TNS:connection closed
ns secondary err code: 12560
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
opiodr aborting process unknown ospid (878) as a result of ORA-609
Tue Apr 09 2013

***********************************************************************

Fatal NI connect error 12547, connecting to:
(LOCAL=NO)

VERSION INFORMATION:
TNS for IBM/AIX Version 11.2.0.3.0 - Production
TCP/IP NT Protocol Adapter for IBM/AIX Version 11.2.0.3.0 - Production
Time: 09-APR-2013
Tracing not turned on.
Tns error struct:
ns main err code: 12547

TNS-12547: TNS:lost contact
ns secondary err code: 12560
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
opiodr aborting process unknown ospid (937) as a result of ORA-609
Tue Apr 09 11:22:52 2013

At this specific error the output of the Trace file ORCL_ora_937.trc is:

Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /oracle/ORCL/119_69
System name: AIX
Node name: ORCL
Release: 1
Version: 7
Machine: 00A50345DC4
Instance name: ORCL
Redo thread mounted by this instance: 1
Oracle process number: 123
Unix process pid: 937, image: oracle@ORCL

*** 2013-04-09
*** CLIENT ID:() 2013-04-09
*** SERVICE NAME:() 2013-04-09
*** MODULE NAME:() 2013-04-09
*** ACTION NAME:() 2013-04-09

opiino: Attach failed due to ORA-12547

Below parameter processes/sessions

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
aq_tm_processes integer 1
db_writer_processes integer 1
gcs_server_processes integer 0
global_txn_processes integer 1
job_queue_processes integer 900
log_archive_max_processes integer 4
processes integer 400
java_max_sessionspace_size integer 0
java_soft_sessionspace_limit integer 0
license_max_sessions integer 0
license_sessions_warning integer 0
sessions integer 700
shared_server_sessions integer

Could someone tell me what these errors are due and what / where can I check to avoid them?

Thanks in advance!

slightwv (䄆 Netminder)

Check out:
http://ora-12547.ora-code.com/

I would probably contact Oracle Support on this one. They have the necessary tools to dig through the trace files and tell you what is happening.

ralph_rea

ASKER

Below my listener.ora:

ADMIN_RESTRICTIONS_LISTENER = on
LISTENER =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = IPC)
(KEY = ORCL.WORLD)
)
(ADDRESS=
(PROTOCOL = IPC)
(KEY = ORCL)
)
(ADDRESS =
(COMMUNITY = WORLD)
(PROTOCOL = TCP)
(HOST = ORCL)
(PORT = 1527)
)
)
STARTUP_WAIT_TIME_LISTENER = 0
CONNECT_TIMEOUT_LISTENER = 10
TRACE_LEVEL_LISTENER = OFF
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = ORCL)
(ORACLE_HOME = /oracle/ORCL/119_69)
)
)

CONNECT_TIMEOUT_LISTENER seems low, do you think that increasing the value can improve?

ASKER CERTIFIED SOLUTION

slightwv (䄆 Netminder)

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ralph_rea

ASKER

Here:
http://docs.oracle.com/cd/B28359_01/network.111/b28317/listener.htm

The parameter CONNECT_TIMEOUT is not present but is present INBOUND_CONNECT_TIMEOUT parameter.

Have you any idea?

slightwv (䄆 Netminder)

>>The parameter CONNECT_TIMEOUT is not present but is present INBOUND_CONNECT_TIMEOUT parameter.

I know. That's why I posted it.

>>Have you any idea?

I already gave my advice: Contact Oracle Support.

It might just be the client connection isn't being properly closed and this is 'normal' for the apps using the database.

The error code action from the link I posted above is:
Investigate partner application for abnormal termination. On an Interchange, this can happen if the machine is overloaded.

ralph_rea

ASKER

>>Based on the docs for INBOUND_CONNECT_TIMEOUT, it doesn't generate a ORA-12547

from docs NO but from Oracle support ID 1116960.1 seems yes.

slightwv (䄆 Netminder)

>>from docs NO but from Oracle support ID 1116960.1 seems yes

Well then, this might be the cause. Take the suggestion in the doc: Increase that parameter and see if the problem goes away or it reduces the number of occurences. If it only reduces the number of occurences, increase it again.

If the number doesn't decrease or go away, it wasn't the cause.

ralph_rea

ASKER

I tried with:
INBOUND_CONNECT_TIMEOUT=120 but I get the same alarm in alert log

I have noticed these parameters:
sga_max_size = 2G
sga_target = 0
pga_aggregate_target = 700M

Could be a problem the sga_target value to zero?

slightwv (䄆 Netminder)

>>INBOUND_CONNECT_TIMEOUT=120 but I get the same alarm in alert log

Then it likely isn't related?

>>Could be a problem the sga_target value to zero?

I don't think the issue is memory related. sga_target is just the size at startup.

I still suggest you work with Oracle Support on this one. I'm thinking it is realted to the apps connecting to the database and how they terminate/end the connections. That is just a gut feeling.