Hi all,
So I started facing this in a client environment. Here is the alert message:
Target name=db01cel08.xxx.com Message=ORA-00600: internal error code, arguments: [LinuxBlockIO::reap], [0x60000D502388], [], [], [], [], [], [], [], [], [], [] Event reported time=Dec 19, 2019 2:14:16 AM EDT
When checking on the cellserver I see this message:
[root@db01 ~]# ssh db01cel08 Last login: Thu Dec 19 04:45:13 2019 from db01.xxx.com [root@db01cel08 ~]# cellcli CellCLI: Release 12.1.2.3.5 - Production on Fri Dec 19 17:13:31 EDT 2019 Copyright (c) 2007, 2016, Oracle. All rights reserved. CellCLI> LIST ALERTHISTORY detail [...] name: 10 alertDescription: "ORA-07445: exception encountered: core dump [__intel_new_memset()+62] [11] [0x000000000] [] [] []" alertMessage: "ORA-07445: exception encountered: core dump [__intel_new_memset()+62] [11] [0x000000000] [] [] []" alertSequenceID: 10 alertShortName: ADR alertType: Stateless beginTime: 2019-12-19T02:00:04-04:00 endTime: examinedBy: notificationState: 1 sequenceBeginTime: 2019-12-19T02:00:04-04:00 severity: critical alertAction: "Errors in file /opt/oracle/cell/log/diag/asm/cell/SYS_112331_170406/trace/cellofltrc_19796_53.trc (incident=25). Diagnostic package is attached. It is also accessible at https://db01cel08.xxx.com/diagpack/download?name=db01cel08_2019_12_19T02_00_04_10.tar.bz2 It will be retained on the storage server for 7 days. If the diagnostic package has expired, then it can be re-created at https://db01cel08.xxx.com/diagpack" name: 11 alertDescription: "ORA-00600: internal error code, arguments: [LinuxBlockIO::reap], [0x60000D502388], [], [], [], [], [], [], [], [], [], []" alertMessage: "ORA-00600: internal error code, arguments: [LinuxBlockIO::reap], [0x60000D502388], [], [], [], [], [], [], [], [], [], []" alertSequenceID: 11 alertShortName: ADR alertType: Stateless beginTime: 2019-12-19T02:00:04-04:00 endTime: examinedBy: notificationState: 1 sequenceBeginTime: 2019-12-19T02:00:04-04:00 severity: critical alertAction: "Errors in file /opt/oracle/cell/log/diag/asm/cell/db01cel08/trace/svtrc_9174_12.trc (incident=25). Diagnostic package is attached. It is also accessible at https://db01cel08.xxxx.com/diagpack/download?name=jdb01cel08_2019_12_19T02_00_04_11.tar.bz2 It will be retained on the storage server for 7 days. If the diagnostic package has expired, then it can be re-created at https://db01cel08.xxx.com/diagpack" name: 12_1 alertDescription: "A SQL PLAN quarantine has been added" alertMessage: "A SQL PLAN quarantine has been added. As a result, Smart Scan is disabled for SQL statements with the quarantined SQL plan. Quarantine id : 21 Quarantine type : SQL PLAN Quarantine reason : Crash Quarantine Plan : SYSTEM Quarantine Mode : FULL_Quarantine DB Unique Name : XPTODB Incident id : 25 SQLID : 8j0az9sgxs5yh SQL Plan details : {SQL_PLAN_HASH_VALUE=281152830, PLAN_LINE_ID=9} In addition, the following disk region has been quarantined, and Smart Scan will be disabled for this region: Disk Region : {Grid Disk Name=Unknown, offset=186750337024, size=1M} " alertSequenceID: 12 alertShortName: Software alertType: Stateful beginTime: 2019-12-19T02:00:12-04:00 examinedBy: metricObjectName: QUARANTINE/21 notificationState: 1 sequenceBeginTime: 2019-12-19T02:00:12-04:00 severity: critical alertAction: "A SQL statement caused the Cell Server (CELLSRV) service on the cell to crash. A SQL PLAN quarantine has been created to prevent the same SQL statement from causing the same cell to crash. When possible, disable offload for the SQL statement or apply the RDBMS patch that fixes the crash, then remove the quarantine with the following CellCLI command: CellCLI> drop quarantine 21 All quarantines are automatically removed when a cell is patched or upgraded. For information about how to disable offload for the SQL statement, refer to the section about 'SQL Processing Offload' in Oracle Exadata Storage Server User's Guide. Diagnostic package is attached. It is also accessible at https://db01cel08.xxx.com/diagpack/download?name=db01cel08_2019_12_19T02_00_12_12_1.tar.bz2 It will be retained on the storage server for 7 days. If the diagnostic package has expired, then it can be re-created at https://db01cel08.xxx.com/diagpack" CellCLI>
After some research, we could match the situation to Bug 13245134 – Query may fail with errors ORA-27618, ORA-27603, ORA-27626 or ORA-00600[linuxblockio::reap_1] or ora-600 [cacheput::process_1]
It’s also described as per: Exadata/SuperCluster: 11.2 databases missing fix for the bug 13245134 may lead to cell service crash with ora-600 [linuxblockio::reap_1]/ora-600 [cacheput::process_1] or ORA-27626: Exadata error: 242/Smart scan issues on the RDBMS side
In order to resolve the crashes quickly, I applied the patch online with:
After applying, all got solved:
[oracle@db01 ~]$ /oracle/xptodb/product/11.2.0.4/OPatch/opatch lsinventory -OH $ORACLE_HOME | grep 13245134 Patch (online) 13245134: applied on Thu Dec 19 23:34:50 EST 2019 13245134 [oracle@db01 ~]$
Hope it helps!