数据库升级到19后，大量的 ORA-3137[kpoal8Check-5] 错误
更新时间： 2021-09-24 17:05
数据库从11G升级到19C后,报警日志中不停的报这个ORA-3137的错误，
如下：
。。。
ORA-03137: TC : [kpoal8Check-5] [0] [0x000000000] [0x000000000] [0] [0] [265512] []
Session (886,4908): Bad TTC Packet Detected: Inbound connection from DBID: (DESCRIPTION =(A GLOBAL_DB_NAME: (DESCRIPTION =(A
Session (886,4908): Bad TTC Packet Detected: DB Logon User: CHIS, Remote Machine: WORKGROUP\WIN-3UVLE0V53JO, Program: w3wp.exe, OS User: DRGs????
Session (886,4908): Bad TTC Packet Detected: Client IP Address: 192.168.10.10
。。。
Session (886,4908): Bad TTC Packet Detected: Inbound connection from DBID: (DESCRIPTION =(A GLOBAL_DB_NAME: (DESCRIPTION =(A
Session (886,4908): Bad TTC Packet Detected: DB Logon User: CHIS, Remote Machine: WORKGROUP\WIN-3UVLE0V53JO, Program: w3wp.exe, OS User: DRGs????
Session (886,4908): Bad TTC Packet Detected: Client IP Address: 192.168.10.10
。。。
TRACE文件中，包含：ksedst1,ksedst,dbkedDefDump,ksedmp,dbgexPhaseII,dbgexProcessError,dbgePostErrorKGE,dbkePostKGE_kgsf,kgeade,kgerelv,opiierr,kpoal8Check ,kpoal8,opiodr,ttcpip,opitsk,opiino,opiodr,opidrv,sou2o,opimai_real,ssthrdmain,main,libc_start_main
这个主要是客户端版本和数据库服务器版本不匹配导致的，有些客户端版本还是8I,9I，
解决办法：升级客户端到11.2.0.4以上版本即可.
参见官方文档：
ORA-3137[kpoal8Check-5] from Incompatible Client Version Connecting to a 12.2 Database (文档 ID 2296523.1)
In this Document
Symptoms
Changes
Cause
Solution
References
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.
SYMPTOMS
The 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
CHANGES
The database was upgraded to 12.2.
CAUSE
This issue is caused by the client version not being compatible with 12.2 RDBMS server version. Unlike previous versions, Oracle has added some strict checks in 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.
SOLUTION
Upgrade the client to a compatible level.
REFERENCES
Symptoms
Changes
Cause
Solution
References
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.
SYMPTOMS
The 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
CHANGES
The database was upgraded to 12.2.
CAUSE
This issue is caused by the client version not being compatible with 12.2 RDBMS server version. Unlike previous versions, Oracle has added some strict checks in 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.
SOLUTION
Upgrade the client to a compatible level.
REFERENCES
