Database Targets Aren't Monitored Properly
(Doc ID 1560552.1)
Last updated on FEBRUARY 20, 2019
Applies to:Enterprise Manager for Oracle Database - Version 184.108.40.206 to 220.127.116.11 [Release 11.1]
Information in this document applies to any platform.
Customer is using 18.104.22.168 OMS console to attempt to connect to 22.214.171.124 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 126.96.36.199.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 188.8.131.52.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 184.108.40.206.0 - 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