| Oracle® Database Appliance Release Notes Release 2.1 for Linux x86-64 Part Number E23730-11 |
|
| PDF · Mobi · ePub |
| Oracle® Database Appliance Release Notes Release 2.1 for Linux x86-64 Part Number E23730-11 |
|
| PDF · Mobi · ePub |
Release Notes
Release 2.1 for Linux x86-64
E23730-11
December 2011
This document may be updated after it is released. To check for updates to this document and to view other Oracle documentation, check the online Oracle Database Appliance documentation library at:
http://www.oracle.com/pls/topic/lookup?ctx=dba21
This document contains the following topics:
Instructions for downloading and installing patchset 2.1.0.1.0 are in Oracle Database Appliance Installation, Configuration and User's Guide. See the section, "Patching Oracle Database Appliance Software With Oracle Appliance Manager" in Chapter 3.
For additional information about patching Oracle Database Appliance, see Oracle Database Appliance Installation, Configuration and User's Guide, section, "Upgrading and Patching Oracle Database Appliance Servers" in Chapter 3.
Instructions for downloading the initial Oracle software to Oracle Database Appliance are in Oracle Database Appliance Installation, Configuration and User's Guide. See the section "Configuring the Oracle Database Appliance Image" in Chapter 1.
With patchset 2.1.0.1.0, a Directory Name Server is no longer required. If you do not use a DNS, then the addresses you provide are configured in the /etc/hosts file to provide IP name and address resolution.
The issues described in this section are the only known issues at this time.
Issue:
If a system reset is issued to a system controller instead of graceful shutdown and restart of a running OS, then there is a low probability that a false uncorrectable memory error will be logged. This issue is indicated by the system FAULT LED being lit, and by a memory uncorrectable error logged in the SEL logs and in the Oracle ILOM event logs. This UE error typically is associated with a CPU-1 DIMM.
When the system controller restarts, it stops at the BIOS splash screen indicating a memory UE DIMM failure. You must press the "F1" key to continue restarting Oracle Appliance. Due to this false error, the failing DIMM is then mapped out. The system controller then restarts successfully, but without the one memory DIMM.
Workaround:
Avoid the use of the Oracle ILOM command-line interface (CLI) command "reset /SYS" or the use of the Oracle ILOM web interface "Reset" operation in the Remote Control --> Remote Power Control tab to shut down a running operating system.
On a memory UE error, the BIOS splash screen requires user to press the F1 key to continue. When this is done, the system restarts without this one memory DIMM and operates correctly.
To correct this state, and bring the DIMM back online, clear the fault and power cycle the system controller.
To clear the fault, use one of the following methods:
In the Oracle ILOM CLI interface issue a the following command:
set /SYS/MB/Px/Dy / clear_fault_action=true
You are prompted if you are sure you want to clear. Answer "y"
In the ILOM web interface, go to System Information, and then Components. Filter on "faulted" in the list menu.
The failing DIMM is shown. Select the DIMM by clicking on the circle (radio button). Select the Actions list menu, and click Clear Faults.
Either of these two methods clears the failure and extinguishes the FAULT LED. To bring memory back on line, shut down and power cycle the system controller.
Issue:
If the system controller is reset during early POST (power-on self test) before video initialization, spurious DRAM faults are logged when the system restarts. These spurious faults result in the faulted DIMMs being disabled by BIOS. The memory associated with those DIMMs is then unavailable to the operating system.
To determine if a particular DIMM fault may be the result of this issue, examine the IPMI SEL to determine if a warm reset occurred before Video initialization. The example in the following text depicts a typical failure log where a "System Restart" event occurred prior to the "Video initialization" event. This results in the spurious Memory Uncorrectable Error being reported following the reset. The timestamp associated with the Memory Uncorrectable Error should match the timestamp of the DIMM fault.
5 | 08/09/2011 | 16:40:33 | System Boot Initiated | Initiated by warm reset | Asserted
>>>> 6 | 08/09/2011 | 16:40:33 | System Boot Initiated | System Restart | Asserted
7 | 08/09/2011 | 16:40:33 | System Firmware Progress | Memory initialization | Asserted
8 | 08/09/2011 | 16:40:34 | System Firmware Progress | Primary CPU initialization | Asserted
9 | 08/09/2011 | 16:41:42 | System Firmware Progress | Management controller initialization | Asserted
a | 08/09/2011 | 16:41:42 | System Firmware Progress | Secondary CPU Initialization | Asserted
>>>> b | 08/09/2011 | 16:41:42 | Memory | Uncorrectable Error | Asserted | OEM Data-2 0x00 OEM Data-3 0x04
c | 08/09/2011 | 16:41:54 | System Firmware Progress | Video initialization | Asserted
d | 08/09/2011 | 16:42:00 | System Firmware Progress | Keyboard controller initialization | Asserted
e | 08/09/2011 | 16:42:12 | System Firmware Progress | Option ROM initialization | Asserted
f | 08/09/2011 | 16:42:15 | System Firmware Progress | Option ROM initialization | Asserted
10 | 08/09/2011 | 16:42:18 | System Firmware Progress | Option ROM initialization | Asserted
11 | 08/09/2011 | 16:42:22 | System Firmware Progress | Option ROM initialization | Asserted
12 | 08/09/2011 | 16:42:27 | System Firmware Progress | System boot initiated | Asserted
Workaround:
Avoid resetting the system busing of the Oracle ILOM command-line interface (CLI) command "reset /SYS" or the Oracle ILOM web interface "Reset" operation in the Remote Power Control tab, located under the section Remote Control, before you restart the operating system.
If the system is reset during early POST and spurious DIMM faults are logged, then these faults should be cleared using the following Oracle ILOM CLI command:
set /SYS/MB/Px/Dy/ clear_fault_action=true
Where Px/Dy identifies the DIMM the fault was reported against.
After clearing the DIMM faults, the system should be power-cycled to ensure all the memory is brought back online.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle Database Appliance Release Notes, Release 2.1 for Linux x86-64
E23730-11
Copyright © 2011, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|