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
Last updated on APRIL 27, 2017
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 to 22.214.171.124 [Release 11.2]
Oracle SuperCluster Specific Software - Version 1.x to 2.x [Release 1.0 to 2.0]
Oracle Exadata Storage Server Software - Version 126.96.36.199.4 to 188.8.131.52.0 [Release 12.1 to 12.2]
Information in this document applies to any platform.
11.2 databases missing fix for the <bug 13245134> may cause the RDBMS to send incorrect payloads to the storage cells during the smart scan operation.
The outcome of the storage server receiving an invalid payload varies depending on Exadata storage server software version.
1. Storage software version <= 184.108.40.206.3
Cellsrv crash with ORA-600 [CachePut::Process_1] or ORA-00600 [linuxblockio::reap_1]
Exadata error: 242 indicate invalid payload error.
3. Storage software version >=220.127.116.11.5 or >=18.104.22.168.1
With the code improvements done in the <bug 25765869>, RDBMS will re-execute the query without the smart scan. This prevents the query failure.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms