My Oracle Support Banner

ORA-600 [ipc_recreate_que_2] on Exadata with mlx4_core errors (Doc ID 2627212.1)

Last updated on MARCH 12, 2021

Applies to:

Oracle Database - Enterprise Edition - Version 18.4.0.0.0 to 19.2.0.0.0 [Release 18 to 19]
Information in this document applies to any platform.

Symptoms

18.4 version of database on Exadata hits internal error ORA-600 [ipc_recreate_que_2] but no crash was observed.

Instance alert log will have the below entries.

alert_<INST_NAME>.log
--------------------------
2019-12-19T02:23:44.160003+08:00
Errors in file $ADR_HOME/rdbms/<DB_NAME>/<INST_NAME>/trace/<INST_NAME>_j000_19915.trc (incident=2361113):
ORA-00600: internal error code, arguments: [ipc_recreate_que_2], [1], [1], [], [], [], [], [], [], [], [], []
Incident details in: $ADR_HOME/rdbms/<DB_NAME>/<INST_NAME>/incident/incdir_2361113/<INST_NAME>_j000_19915_i2361113.trc
2019-12-19T02:23:46.198220+08:00
*****************************************************************
An internal routine has requested a dump of selected redo.
This usually happens following a specific internal error, when
analysis of the redo logs will help Oracle Support with the
diagnosis.
It is recommended that you retain all the redo logs generated (by
all the instances) during the past 12 hours, in case additional
redo dumps are required to help with the diagnosis.
*****************************************************************
2019-12-19T02:23:49.551646+08:00
Errors in file $ADR_HOME/rdbms/<DB_NAME>/<INST_NAME>/trace/<INST_NAME>_j001_19917.trc (incident=2361121):
ORA-00600: internal error code, arguments: [ipc_recreate_que_2], [1], [1], [], [], [], [], [], [], [], [], []
Incident details in: $ADR_HOME/rdbms/<DB_NAME>/<INST_NAME>/incident/incdir_2361121/<INST_NAME>_j001_19917_i2361121.trc
2019-12-19T02:23:51.791360+08:00
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 $ADR_HOME/rdbms/<DB_NAME>/<INST_NAME>/trace/<INST_NAME>_j001_19917.trc (incident=2361122):
ORA-00600: internal error code, arguments: [600], [ORA-00600: internal error code, arguments: [ipc_recreate_que_2], [1], [1], [], [], [], [], [], [], [], [], []
], [], [], [], [], [], [], [], [], [], []
Incident details in: $ADR_HOME/rdbms/<DB_NAME>/<INST_NAME>/incident/incdir_2361122/<INST_NAME>_j001_19917_i2361122.trc
2019-12-19T02:23:52.032100+08:00
Dumping diagnostic data in directory=[cdmp_20191219022352], requested by (instance=2, osid=19917 (J001)), summary=[incident=2361121].
2019-12-19T02:23:53.696347+08:00
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.

 The call stack and incident context dump from the incident trace files are as follows.

<INST_NAME>_j000_19915_i2361113.trc
-----------------------------------------------
ORA-00600: internal error code, arguments: [ipc_recreate_que_2], [1], [1], [], [], [], [], [], [], [], [], []
:
----- Current SQL Statement for this session (sql_id=87gaftwrm2h68) -----
select o.owner#,o.name,o.namespace,o.remoteowner,o.linkname,o.subname from obj$ o where o.obj#=:1
:
:

 OS log from DomU does not have any error for the same period but Dom0 reports mlx4_core errors.

Dec 19 02:23:08 <NODE_NAME> kernel: [3376217.827496] mlx4_core 0000:3b:00.0: swiotlb buffer is full (sz: 262144 bytes)
Dec 19 02:23:08 <NODE_NAME> kernel: [3376217.827501] mlx4_core 0000:3b:00.0: swiotlb buffer is full
Dec 19 02:23:08 <NODE_NAME> kernel: [3376217.827514] mlx4_core 0000:3b:00.0: vhcr command:0xf00 slave:2 failed with error:0, status -12

 

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!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.