ORA-00600[17114] Error Due To Memory Corruption That Comes From SQL Tuning Advisor
(Doc ID 1911334.1)
Last updated on JULY 24, 2024
Applies to:
Oracle Database Cloud Service - Version N/A and laterOracle Database - Enterprise Edition - Version 11.2.0.3 to 11.2.0.3 [Release 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
1. Follwing errors are seen in the alert.log:
Errors in file <diagnostic_dest>/diag/rdbms/<dbname>/<instname>/trace/<instname>_j003_6602.trc (incident=897028):
ORA-00600: internal error code, arguments: [17114], [0x2ADCC6B31FC0], [], [], [], [], [], [], [], [], [], []
Incident details in: <diagnostic_dest>/diag/rdbms/<dbname>/<instname>/incident/incdir_897028/<instname>_j003_6602_i897028.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Wed Jul 02 09:01:55 2014
Dumping diagnostic data in directory=[cdmp_20140702090155], requested by (instance=1, osid=6602 (J003)), summary=[incident=897028].
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x0] [PC:0x24DB073, kxhfSync()+255] [flags: 0x0, count: 1]
Errors in file <diagnostic_dest>/diag/rdbms/<dbname>/<instname>/trace/<instname>_j003_6602.trc (incident=897029):
ORA-07445: exception encountered: core dump [kxhfSync()+255] [SIGSEGV] [ADDR:0x0] [PC:0x24DB073] [Address not mapped to object] []
ORA-00600: internal error code, arguments: [17114], [0x2ADCC6B31FC0], [], [], [], [], [], [], [], [], [], []
Incident details in: <diagnostic_dest>/diag/rdbms/<dbname>/<instname>/incident/incdir_897029/<instname>_j003_6602_i897029.trc
Use ADRCI or Support Workbench to package the incident.
ORA-00600: internal error code, arguments: [17114], [0x2ADCC6B31FC0], [], [], [], [], [], [], [], [], [], []
Incident details in: <diagnostic_dest>/diag/rdbms/<dbname>/<instname>/incident/incdir_897028/<instname>_j003_6602_i897028.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Wed Jul 02 09:01:55 2014
Dumping diagnostic data in directory=[cdmp_20140702090155], requested by (instance=1, osid=6602 (J003)), summary=[incident=897028].
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x0] [PC:0x24DB073, kxhfSync()+255] [flags: 0x0, count: 1]
Errors in file <diagnostic_dest>/diag/rdbms/<dbname>/<instname>/trace/<instname>_j003_6602.trc (incident=897029):
ORA-07445: exception encountered: core dump [kxhfSync()+255] [SIGSEGV] [ADDR:0x0] [PC:0x24DB073] [Address not mapped to object] []
ORA-00600: internal error code, arguments: [17114], [0x2ADCC6B31FC0], [], [], [], [], [], [], [], [], [], []
Incident details in: <diagnostic_dest>/diag/rdbms/<dbname>/<instname>/incident/incdir_897029/<instname>_j003_6602_i897029.trc
Use ADRCI or Support Workbench to package the incident.
2. Call stack in trace file:
kghrcdepth kghrcappl kghfrempty_ex qesmmIPgaFreeCb ksu_dispatch_tac krr_thread_read krr_read_buffer krr_parse_redo kcra_scan_redo kcra_dump_redo
3. Trace files shows BAD MAGIC NUMBER:
EXTENT 29 addr=0x2adcc6b31ea0
Chunk 2adcc6b31eb0 sz= 136 perm "perm " alo=136
Chunk 2adcc6b31f38 sz= 136 BAD MAGIC NUMBER IN NEXT CHUNK (C0B38F0000000738) ------------------>Memory corruption
perm "perm " alo=136
.....
Bucket 5 size=1048
Chunk 2adcc6cb9e80 sz= 3824 free " "
Chunk 2adcc6b31fc0 sz= 1848 ERROR, BAD MAGIC NUMBER (C0B38F0000000738)
Chunk 2adcc6b31eb0 sz= 136 perm "perm " alo=136
Chunk 2adcc6b31f38 sz= 136 BAD MAGIC NUMBER IN NEXT CHUNK (C0B38F0000000738) ------------------>Memory corruption
perm "perm " alo=136
.....
Bucket 5 size=1048
Chunk 2adcc6cb9e80 sz= 3824 free " "
Chunk 2adcc6b31fc0 sz= 1848 ERROR, BAD MAGIC NUMBER (C0B38F0000000738)
4. The current SQL in trace file comes form SQL Tuning Advisor:
----- Current SQL Statement for this session (sql_id=85fy1sjzcvkn9) -----
/* SQL Analyze(1024,1) / select from <table_name>
...
...
/* SQL Analyze(1024,1) / select from <table_name>
...
...
Changes
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 |