My Oracle Support Banner

Database Targets Aren't Monitored Properly (Doc ID 1560552.1)

Last updated on MARCH 08, 2017

Applies to:

Enterprise Manager for Oracle Database - Version to [Release 11.1]
Information in this document applies to any platform.


Customer is using OMS console to attempt to connect to database target. The db target has the SEC_USER_AUDIT_ACTION_BANNER and SEC_USER_UNAUTHORIZED_ACCESS_BANNER parameters set in the sqlnet.ora. Because these are set, the database is expecting a response to allow access. The OMS will not send a response and so the following errors are shown in the alert log for the db target:

Fatal NI connect error 12637, connecting to:

  TNS for Linux: Version - Production
  Oracle Bequeath NT Protocol Adapter for Linux: Version - Production
  TCP/IP NT Protocol Adapter for Linux: Version - Production
 Time: 04-FEB-2013 11:32:56
 Tracing not turned on.
 Tns error struct:
  ns main err code: 12637

TNS-12637: Packet receive failed
  ns secondary err code: 12532
  nt main err code: 0
  nt secondary err code: 0
  nt OS err code: 0
opiodr aborting process unknown ospid (24053) as a result of ORA-609


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.