TAGS

Recent Posts

Archives

How to Fix “208 Days” Bug in Oracle Exalytics
Posted on March 10, 2014
Author: Suresh Vupputuri, Performance Architects

Have you ever gone on vacation only to come back and realize that you cannot access your Oracle Exalytics machine anymore? Your ILOM (Integrated Lights Out Manager) shows that system is up and your network team says that ports are open in the firewall…but it isn’t working?

It turns out that there is a bug in the system where the Oracle Exalytics Linux operating system may crash or become unresponsive after 208 continuous days of use.

To fix the issue you will have to restart your system. You can also refer to the following document on Oracle Support if you run into this issue: “Oracle Exalytics Stability and Performance Issues on Compute Nodes Running Linux After Uptime of More Than 208 Days (Doc ID 1579194.1).”

For your reference, the Oracle documentation states, “To avoid further occurrences of the 208 days issue; it is recommended that you pro-actively plan to reboot the server before 208 days of continuous up-time has been reached.  By doing this, you will avoid any unplanned server outages.”

If you want permanently fix this issue, you’ll need to apply Patch Set 4 (PS4).

If you have run into this issue or would like to chat more about Exalytics, please email communications@performancearchitects.com.

Author: Suresh Vupputuri, Performance Architects

 

Share
This post was posted in Technical and tagged 208 Days Bug , Exalytics , Oracle , Oracle Exalytics , Oracle Support , Suresh Vupputuri .
© Performance Architects, Inc. and Performance Architects Blog, 2006 - present. Unauthorized use and/or duplication of this material without express and written permission from this blog's author and/or owner is strictly prohibited. Excerpts and links may be used, provided that full and clear credit is given to Performance Architects, Inc. and Performance Architects Blog with appropriate and specific direction to the original content.

Leave a Reply

Your email address will not be published. Required fields are marked *