Applies to:Exadata Database Machine X2-8
Oracle Exadata Storage Server Software - Version 184.108.40.206.1 to 220.127.116.11.2 [Release 11.2]
The 8-socket database servers of Exadata X2-8 systems running Exadata software releases older than 18.104.22.168.0 may experience issues if they have been continuously up for more than 208 days due to Linux Bug 14258279.
These issue can be avoided by upgrading to Exadata release 22.214.171.124.0 or later, or rebooting the servers before they reach 208 days of continuous uptime.
Exadata X2-8 database servers running Unbreakable Enterprise Kernel for Oracle Linux 2.6.32-100.23.1 that have been continuously up for more than 208 days are susceptible to this problem. Unbreakable Enterprise Kernel for Oracle Linux 2.6.32-100.23.1 is the Linux kernel provided with Exadata releases 126.96.36.199.0 through 188.8.131.52.2, inclusive. Uptime may be determined by the uptime(1) command.
Exadata X2-8 database servers running Unbreakable Enterprise Kernel for Oracle Linux 2.6.32-300.7.2 (provided with Exadata 184.108.40.206.0) or later are notaffected.
Exadata X2-2, V2, and V1 database servers are not affected.
Exadata Storage Servers are not affected.
One or more of the following issues may occur on or after 208 days of continuous uptime:
- Kernel panic
- Task scheduler unfairness
- CPU soft lockup error, especially when showing invalid time stamp and/or time calculation. The following is an example message reported to the system console with invalid time stamp and/or time calculation:
There are two possible courses of action:
- Upgrade to Exadata 220.127.116.11.0 or later (Recommended).
- Reboot database servers before uptime reaches 208 days.
1. Upgrade to Exadata 18.104.22.168.0 or later (Recommended)
The recommended action is to upgrade to Exadata release 22.214.171.124.0 or later. Exadata 126.96.36.199.0 and later contain a UEK version with a fix to this bug.
Refer to Document 888828.1 for the most recent Exadata release.
2. Reboot database servers before uptime reaches 208 days
If you cannot upgrade to Exadata 188.8.131.52.0 or later, then to avoid issues associated with Bug 14258279 on your current Exadata release, restart database servers before uptime reaches 208 days.
Follow the procedure below to reboot database servers in a rolling fashion.
Reboot Database Servers in Rolling Fashion
Rebooting database servers in rolling fashion allows application service(s) to potentially be available on and automatically failed over to 1 or more other database servers as 1 database server is restarted. For more information on making an application highly available using Oracle Clusterware and Transparent Application Failover please refer to the following:
- Making applications highly available using Oracle Clusterware
- Configuring Transparent Application Failover
Repeat the following procedure serially on each database server.
1. Ensure Cluster Ready Services (CRS) autostart is enabled so that CRS will automatically start when the database server is rebooted.
If autostart is not enabled and the desired behavior is to automatically start when the system is started, enable autostart with the following command:
2. Shutdown CRS by running the following command:
If any resources are still running after issuing the above command, then reissue the command using the force “-f” option:
3. Once all resources have stopped reboot the database server using the shutdown(8) command:
4. After the database server has restarted, check status of resources.
This Linux bug is fixed in Unbreakable Enterprise Kernel versions supplied with Exadata 184.108.40.206.0 and later.
Refer to Document 888828.1 for information on how to obtain Exadata releases.
10-Jul-2012 review ready