APPLIES TO:Oracle Database Backup 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
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 12.2.0.1 and later
Information in this document applies to any platform.
SYMPTOMSThe following errors occur in the alert log: ORA-03137 : [kpoal8Check-5] [0] [0x000000000] [0x000000000] [0] [0] [2080] []
2017-07-27T16:34:55.075221+03:00
Session (491,42000): Bad TTC Packet Detected: Inbound connection from client
Session (491,42000): Bad TTC Packet Detected: DB Logon User: <login>, Remote Machine: <machine_name>, Program: <program_name>, OS User: <os_user>
Session (491,42000): Bad TTC Packet Detected: Client IP Address: <IP address>
2017-07-27T16:34:56.506362+03:00
Errors in file <diagnostic_dest>/diag/rdbms/<dbname>/<instname>/trace/<instname>_ora_27281.trc (incident=128688):
ORA-03137: [kpoal8Check-5] [0] [0x000000000] [0x000000000] [0] [0] [2080] []
2017-07-27T16:34:56.508811+03:00
Session (491,42000): Bad TTC Packet Detected: Inbound connection from client
Session (491,42000): Bad TTC Packet Detected: DB Logon User: <login>, Remote Machine: <machine_name>, Program: <program_name>, OS User: <os_user>
Session (491,42000): Bad TTC Packet Detected: Client IP Address: <IP address>
Errors in file <diagnostic_dest>/diag/rdbms/<dbname>/<instname>/trace/<instname>_ora_27281.trc (incident=132001):
ORA-03137: [kpoal8Check-5] [0] [0x000000000] [0x000000000] [0] [0] [2080] []
Session (491,42000): Bad TTC Packet Detected: Inbound connection from client
Session (491,42000): Bad TTC Packet Detected: DB Logon User: <login>, Remote Machine: <machine_name>, Program: <program_name>, OS User: <os_user>
Session (491,42000): Bad TTC Packet Detected: Client IP Address: <IP address>
The Call Stack Trace in the associated incident trace file shows: opiierr <- kpoal8Check <- kpoal8 <- opiodr <- ttcpip <- opitsk <- opiino <- opiodr <- opidrv <- sou2o
CHANGESThe database was upgraded to 12.2 or higher. CAUSEThis issue is caused by the client version not being compatible with the RDBMS server version. Unlike previous versions, Oracle has added some strict checks starting 12.2.0.1 and client applications must comply with these checks. This issue was investigated in unpublished Bug 26092744 which was closed as Not a Bug.
SOLUTIONUpgrade the client to a compatible level.
|