ORA-00600:[kjdrisRMnovalid:!creating_pt] in Database alert log after changing MTU size for private interface
(Doc ID 2389759.1)
Last updated on SEPTEMBER 16, 2021
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 and laterOracle Database Exadata 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
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Database alert.log
ORA-00600: internal error code, arguments: [kjdrisRMnovalid:!creating_pt], [1188], [1188], [], [], [], [], [], [], [], [], []
Incident details in: $INCIDENT/incdir_614021/<instancename>1_lms1_7071_i614021.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 $TRACE/<instancename>1_lmon_22616.trc:
ORA-27300: OS system dependent operation:config_check failed with status: 0
ORA-27301: OS failure message: Error 0
ORA-27302: failure occurred at: skgxpvalpid
ORA-27303: additional information: Remote port MTU does not match local MTU. [local: 8192, remote: 1500] (169.254.xx.94)
KSXP IPC protocol is incompatible with instance 2
Error Stack: ORA-600[kjdrisRMnovalid:!creating_pt]
Main Stack:
kjdrisRMnovalid <- kjdrvalidRMno <- kjmvalidate <- kjmpbmsg <- kjmsm <- ksbrdp <- opirip
<- opidrv <- sou2o <- opimai_real <- ssthrdmain <- main
Changes
MTU size for private interconnect changed to 8192 from 1500 to overcome ORA-00600: internal error code, arguments: [kjctr_pbmsg:badbmsg2] error.
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |