Last updated on NOVEMBER 04, 2014
Applies to:Oracle Database - Enterprise Edition - Version 126.96.36.199 to 188.8.131.52 [Release 11.2]
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 "firstname.lastname@example.org (TNS V1-V3)" sessions, and "ps -ef| grep beq" shows many processes:
Process state dump shows similar like the following:
Call stack: ..read<-ntpfprd<-nsbasic_brc<-nsbrecv<-nioqrc..
O/S info: user: oracle, term: , ospid: 21686
machine: racnode1.us.oracle.com program: email@example.com (TNS V1-V3)
application name: firstname.lastname@example.org (TNS V1-V3), hash value=12120032
Current Wait Stack:
0: waiting for 'SQL*Net message from client'
driver id=0x62657100, #bytes=0x1, =0x0
wait_id=103 seq_num=106 snap_id=1
wait times: snap=21706 min 32 sec, exc=21706 min 32 sec, total=21706 min 32 sec
Eventually ORA-00020 will happen as oraagent.bin keeps making new connections without closing them:
Once it happens, other instance may fail to restart as no new connection can be made to the ORA-00020 instance:
ORA-03113: end-of-file on communication channel
Errors in file /u01/app/oracle/diag/asm/+asm/+ASM12/trace/+ASM12_lck0_9071.trc (incident=233838):
ORA-00600: internal error code, arguments: , , , , , , , , , , , 
Incident details in: /u01/app/oracle/diag/asm/+asm/+ASM12/incident/incdir_233838/+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  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)
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms