LMD0 (ospid: 28789): terminating the instance due to error 482

opiodr aborting process unknown ospid (6272) as a result of ORA-609
Fri Jun 20 04:54:47 2014
Errors in file /u01/app/oracle/diag/rdbms/orcldr/orcldr1/trace/orcldr1_lmd0_28789.trc  (incident=182497):
ORA-00600: internal error code, arguments: [kjxcvr:!valblk], [0x255ECAC20], [3014670], [538947], [30], [18], [3], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/orcldr/orcldr1/incident/incdir_182497/orcldr1_lmd0_28789_i182497.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file /u01/app/oracle/diag/rdbms/orcldr/orcldr1/trace/orcldr1_lmd0_28789.trc:
ORA-00600: internal error code, arguments: [kjxcvr:!valblk], [0x255ECAC20], [3014670], [538947], [30], [18], [3], [], [], [], [], []
Fri Jun 20 04:54:49 2014
Dumping diagnostic data in directory=[cdmp_20140620045449], requested by (instance=1, osid=28789 (LMD0)), summary=[incident=182497].
Fri Jun 20 04:54:50 2014
Sweep [inc][182497]: completed
Sweep [inc2][182497]: completed
Errors in file /u01/app/oracle/diag/rdbms/orcldr/orcldr1/trace/orcldr1_lmd0_28789.trc:
ORA-00600: internal error code, arguments: [kjxcvr:!valblk], [0x255ECAC20], [3014670], [538947], [30], [18], [3], [], [], [], [], []
LMD0 (ospid: 28789): terminating the instance due to error 482
Fri Jun 20 04:54:53 2014
ORA-1092 : opitsk aborting process
***********************************************************************

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

VERSION INFORMATION:
TNS for Linux: Version 11.2.0.3.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.3.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.3.0 - Production
Time: 20-JUN-2014 04:53:52
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 (6265) as a result of ORA-609
Fri Jun 20 04:53:52 2014

***********************************************************************
  • The ORA-609 error is thrown when a client connection of any kind failed to complete or aborted the connection process before the connection/authentication process was complete.
  • Very often, this connection abort is due to a timeout.here timeout is 60 seconds, for make the internal db connection
  • Beginning with 10gR2, a default value for inbound connect timeout has been set at 60 seconds.
  • This time limit is often inadequate for the entire connection process to complete.
Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s