Exadata X5-2 Hardware
 
Exalogic Elastic Cloud X5-2 Hardware
 
Big Data Appliance X5-2 Hardware
 
Oracle Database Appliance X5-2
 
Zero Data Loss Recovery Appliance X5 Hardware
 
Oracle Server X5-2
 
Oracle Server X5-2L
 
Oracle Advanced Support Gateway Server X5-2
 
Private Cloud Appliance X5-2 Hardware
 

PLA-Support>Sun Systems>x86>Server>SN-x86: Oracle Server X5
 

In this Document

Symptoms

Changes

Cause

Solution

References

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: FABs are available to Internals and Partners

Applies to:

Symptoms

There is the potential to see early life 8-slot Disk Backplane (DBP) failures which can affect the long-term reliability of the product.

Impact

Systems may see a DBP failure due to this issue. The most common indicator is none of the installed devices (SSD/HDD) in the 8-slot DBP have DC power.

Changes

Systems that have been stored (un-powered) for extended periods of time (several months or more) may be more likely to see a DBP failure than systems which were shipped, received and powered on in a shorter period of time.

Note 1: This issue is specific to the 8-slot disk backplane, PN 7097205.

• This 8-slot disk backplane (DBP) is mainly used in X5-2 systems.
• The X5-2L can use this DBP, but normally uses the 12 slot DBP (PN 7069337 or 7311541), which is not affected.
• SPARC systems using this 8-slot DBP are not affected.

Note 2: This issue is specific to the following system serial number ranges:

Standalone Systems

• X5-2/X5-2L systems where the first 4 digits (date code) of the system serial number are earlier than 1546 are impacted by this issue.
• The first 2 digits of the serial number is the build year
(15 = 2015) and the second 2 digits are the week (46 = week 46).
• Systems with the first 4 digits of the system serial number being 1546 or later did not ship with the spacer. No action is required.

Engineered Systems

• Engineered Systems which have a “rack” serial number where the numeric portion is less than AK00334200 are impacted.
• An example of a “good” rack serial number would be AK00334205.

Racks with a SN above AK00334200 did not ship with X5-2 servers with the spacer installed. No action is required.  No 8-slot X5-2L systems shipped in Engineered Systems.

Cause

Due to a chemical interaction between the polyurethane spacer and the DBP printed circuits, these circuits may degrade to a point of failure.

Solution

Target Completion Date: No time limit for this recommended action
FE Onsite Labor: 30 minutes (per strip)
Hot Swappable: No

Workaround

No workaround available - see Resolution section below.

Resolution

To increase the long term reliability of the 8-slot Disk Backplane, removal of the polyurethane spacer is recommended during the next service action where the system is taken down for service for any reason.  Use the DBP Strip Removal Process document listed in the below References section of this knowledge article.

There is no requirement to take a special outage just to remove the spacer.  For any DBP failures perform standard break-fix replacement actions.

If the polyurethane spacer is present, remove it during the DBP replacement process.  Document in SR Task that the 8-slot DBP polyurethane strip was removed.

Field Instructions

FE should not do strip replacement on systems not related to Task being worked.  SR owner should assign a separate task for tracking and direction on work to be done.  Removing strips on other systems not being addressed on current SR/Task needs to be discussed with customer first.  If the FE obtains permission to do more systems than the Serial on the current SR/Task, the FE should copy task, one per serial, for each system they remove strip on for tracking purposes.

Until further notice all replaced 8-slot Disk Backplanes (DBPs) with a serial number later than 1526 should be CPAS'd.

References

ECO: E0027876
DBP Strip Removal Process
Bug: 21916073 - X5-2/L disk backplanes 7097205 are missing all disks
Doc ID 2097145.1 (Internal Only FAB for Conditional FCO A0361-1

Contacts

Contributor: Mick.Tabor@Oracle.COM, Martin.Canoy@Oracle.COM
Responsible Engineer: Martin.Canoy@Oracle.COM
Responsible Manager: phil.refano@oracle.com

This solution has no attachment