My Oracle Support Banner

Many Connections From oraagent.bin to ASM or Database Instance (Likely ORA-00020) (Doc ID 1287496.1)

Last updated on SEPTEMBER 20, 2022

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.


11gR2 Grid Infrastructure, observed many connections from oraagent.bin to ASM or database instance, v$session.program shows many "oraagent.bin@racnode1.<domain> (TNS V1-V3)" sessions, and "ps -ef| grep beq" shows many processes:

Once it happens, other instance may fail to restart as no new connection can be made to the ORA-00020 instance:

SQL> startup
ORA-03113: end-of-file on communication channel

Errors in file $TRACE/+ASM12_lck0_9071.trc  (incident=233838):
ORA-00600: internal error code, arguments: [1617], [30], [1], [], [], [], [], [], [], [], [], []
Incident details in: $INCIDENT/+ASM12_lck0_9071_i233838.trc
LCK0 (ospid: 9071): terminating the instance due to error 480

Trace shows call stack of: .. kgeasi ksbmsg ksbedcic_one_int ksbedcic_one kclabs ..

The ORA-00600 [1617] error will go away once the ORA-00020 instance is restarted (it could mean a restart of Grid Infrastructure  if OCR/VD is on ASM and ASM is getting ORA-00020)




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.