| Oracle® Database Appliance Release Notes Release 2.6 for Linux x86-64 Part Number E23730-19 |
|
| PDF · Mobi · ePub |
Release Notes
Release 2.6 for Linux x86-64
E23730-19
May 2013
This document may be updated after the most recent version of the product is released. To check for updates to this document and to view other Oracle documentation, check the online Oracle Database Appliance documentation library:
http://www.oracle.com/pls/topic/lookup?ctx=dba21
This document contains the following topics:
For the latest software, announcements, alerts, knowledge documents, and problem-solution and troubleshooting documents, visit My Oracle Support Information Center: Oracle Database Appliance [ID 1417713.2]:
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1417713.2
My Oracle Support note 888888.1 is a dynamically updated document that contains patch downloads and the most current information about patches and known deployment issues. Access the note using the following URL:
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=888888.1
ODA Patch 2.6.0.0.0 Patch 16744915 (p16744915_26000_Linux-x86-64.zip)
Offers similar deployment and user experience for both Bare Metal and Virtualized platform on X3-2 and all earlier hardware
Support of OVM assemblies (*.ova files)
Support for http option for template import
SAP supported on Oracle Database Appliance and on Oracle Database Appliance X3-2 Bare Metal
ILOM version updated to 3.0.16.22.b r78329
Oracle Database Patch Set Update (PSU) 11.2.0.3.6 and 11.2.0.2.10
New offline Oracle Appliance Manager Configurator
New Oracle Appliance Manager commands and options:
oakcli restart oda_base: stop and restart ODA_BASE on the local node
oakcli start oda_base: start ODA_BASE on the local node
oakcli stop oda_base: stop ODA_BASE on the local node
You can deploy Oracle Database Appliance in a Virtualized or Non-virtualized (Bare Metal) configuration.
For Virtualized Configuration:
Patch 16186163: Oracle Database Appliance VM ISO Image (Dom0)
Patch 16186172: Oracle Database Appliance VM Template (ODA_BASE)
For Bare Metal (non-virtualized) configuration:
Patch 12999313: Oracle Database Appliance 2.6 Bare Metal ISO Image
Patch 16186172: Oracle Database Appliance 2.6 End User Bundle (GI+RDBMS)
End User 11.2.0.2.10 RDBMS Clone Patch 14349293
File Name: p14349293_26000_Linux-x86-64.zip
End User 11.2.0.3.6 RDBMS Clone Patch 14777276
File Name: p14777276_26000_Linux-x86-64.zip
Note:
When downloading patches for Oracle Database Appliance Release 2.6, ensure that you select Oracle Appliance Kit 2.6.0.0.0 in the Select a Release drop down list.Support for new Oracle Database Appliance X3-2 (hardware only).
Support for one additional storage expansion shelf (for a total of two storage shelves).
Provides choice of either a Bare Metal (BM) or a Virtualization Platform option for ODA X3-2 hardware.
This is the First version for ODA X3-2, therefore patching is not available.
For Bare Metal installation only, the following EndUserBundle clone file can be applied on ODA X3-2 nodes running versions 2.5.5.0.0:
p12978712_25500_Linux-x86-64.zip
For Virtualized Platform installation, apply the following files
p16186163_25500_Linux-x86-64.zip
p16186172_25500_Linux-x86-64.zip
using the step by step instructions documented in My Oracle Support Note https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=REFERENCE&id=1520579.1.
Starting with release 2.5, you can deploy Oracle Database Appliance in a Virtualized or Non-virtualized (Bare Metal) configuration.
Support for Oracle VM, Version 3.1.1
Efficient use of resources:
Few cores can be licensed for database
Remaining cores can support virtual domains for a variety of uses
Similar deployment and usage experience for both bare metal and virtual platforms
Based on Oracle VM 3.1.1 and supports all OS and templates support by Oracle VM
New Oracle VM oakcli commands
External Auto Service Request server support
Oracle Automatic Storage Management (Oracle ASM) Normal Redundancy Support for DATA and RECO disk groups: This feature is only available for new deployments. In the Oracle Database Appliance Manager GUI, you can select normal redundancy for your DATA and RECO disk groups when you select the Custom configuration option. Oracle continues to use HIGH redundancy for the REDO disk group.
Trace File Analyzer: This version adds a deployment step to install the new Trace File Analyzer feature.
The oakcli create command is enhanced as follows:
Currently, the supported versions for oakcli create dbhome –version version_number are 11.2.0.2.8 and 11.2.0.3.4.
All documentation in the Oracle Database Appliance library is current for Oracle Database Appliance 2.4.0.0.0. Some of the documents may refer to previous Oracle Database Appliance releases, but these documents are applicable to this most recent release.
For additional information about known issues for this patch, refer to My Oracle Support Note 888888.1. The following summarizes the known issues for release 2.4.0.0.0:
By default, Oracle installs Enterprise Manager DB Console for the database. For Grid Infrastructure patching, Oracle stops all DB Consoles. However, if you installed the Oracle Database Grid Control 12c agent, then it remains operational. If you have installed Oracle Database Grid Control 12c, then run the command emctl stop agent to stop the Oracle Database Enterprise Manager Agent before applying Grid Infrastructure patching. This avoids running into the issue – copy failed for crsctl.bin.
It is not necessary to run emctl stop dbconsole, because the patching process stops the console. Intermittently, some DB Console processes continue running, and Grid Infrastructure patching fails because a copy operation for crsctl.bin failed. If this happens, then ensure that the DB Console process is stopped before performing Grid Infrastructure patching.
After the infrastructure is updated, run dmidecode -t 1|egrep Serial Number|Version|Product Name|SKU Number on both nodes. If either node responds with a Not Available message, then reboot the node. This issue should be resolved in this release.
After the infrastructure updates, run fwupdate list controller | grep –v Intel on both nodes. If no information appears under FW Version for SAS LSI Logic 0x0072 Type Manufacturer Model controllers, then reboot the node. The firmware version should be 11.05.02.00. This issue should be resolved in this release.
In deployments for the version prior to Oracle Database Appliance 2.3, the parameter use_large_pages is set to TRUE. For new deployments, Oracle adopts the best practice of setting use_large_pages to ONLY. If you did not properly size your environment based on Appendix C of the Oracle Database Appliance Getting Started Guide and your database has a larger SGA, then you might see related messages in your alert log file. Oracle does not recommend that you revert the setting of use_large_pages to TRUE. Instead, Oracle recommends that you let the system notify you with the early warning that your database might run into memory issues; eventually this limitation will affect your system's performance. In this case, Oracle recommends that you avoid creating and starting additional databases.
****************** Huge Pages Information ***************** Huge Pages memory pool detected (total: 26000 free: 3729) Huge Pages allocation failed (free: 23694 required: 2049) Startup will fail as use_large_pages is set to "ONLY" *********************************************************
Or:
****************** Large Pages Information ***************** Parameter use_large_pages = ONLY Large Pages unused system wide = 23951 (47 GB) (alloc incr 128 MB) Large Pages configured system wide = 26000 (51 GB) Large Page size = 2048 KB ERROR: Failed to allocate shared global region with large pages, unix errno = 12. Aborting Instance startup. ORA-27137: unable to allocate Large Pages to create a shared memory segment ACTION: Total Shared Global Region size is 48 GB. Increase the number of unused large pages to at least 24580 (48 GB) to allocate 100% Shared Global Region with Large Pages. **********************************************************
Support for multiple Oracle homes for Oracle Database 11g Release 2 versions 11.2.0.2.5 and 11.2.0.3.3 as follows:
Ability to create multiple Oracle homes of the same database version or a different version.
For new database homes, Oracle supports 11.2.0.2.8 and 11.2.0.3.4.
You can create a database from an existing home. By default, when you create a database without providing the home information, Oracle creates a separate home for that database.
If you provide version information while creating the database, then Oracle creates a new database home with that particular version, and then creates the database in that home.
Please refer to Appendix C of the Oracle Database Appliance Getting Started Guide for information about Oracle Database Appliance sizing to determine how many Oracle RAC databases your environment can support.
The oakcli create command is enhanced as follows:
In addition to the oakcli upgrade command, there are some new oakcli commands included in this patch to support multiple databases and multiple database homes.
The minimum version to run oakcli create or oakcli delete is Oracle Database Appliance 2.3.0.0.0.
Run oakcli create commands to create new databases, or new database homes or new database configuration parameter files.
Oracle Database Appliance 2.3: currently the supported versions for oakcli create dbhome –version version_number are 11.2.0.2.7 and 11.2.0.3.3.
To create 11.2.0.2.8 homes, download the 11.2.0.2.8 database clone file from My Oracle Support, patch number 14349293 - p14349293_24000_Linux-x86-64.zip. To create 11.2.0.3.4 homes, download the 11.2.0.3.4 database clone file from My Oracle Support, patch # 14777276 - p14777276_24000_Linux-x86-64.zip. The command should be run on node 1.
See Also:
Enter theoakcli create -h command to see more details, or refer to Appendix D in the Oracle Database Appliance Getting Started GuideThe oakcli delete command is enhanced as follows:
You can use oakcli delete commands on node 1 to delete old unused databases and old, unused database homes.
See Also:
Enter theoakcli delete -h command to see more details, or refer to Appendix D in the Oracle Database Appliance Getting Started GuideThe Oracle Appliance Database configuration parameters are enhanced as follows:
Oracle uses a set of default parameters to create a database. You can use oakcli show db_config_parms –detail to display the database configuration parameter settings. To change these configuration parameter settings, create a configuration file using oakcli create db_config_params -conf conf_file_name on node 1, where conf_file_name is the name of the configuration file.
See Also:
Enter theoakcli show dbconfig_params -h command to see more details, or refer to Appendix D in the Oracle Database Appliance Getting Started GuideYou can now run the oakcli update –patch 2.4.0.0.0 --verify command as follows:
Before you run oakcli update –patch, you can verify the proposed patch version by running the oakcli update –patch 2.4.0.0.0 --verify command.
See Also:
Enter theoakcli update -patch 2.4.0.0.0 --verify command to see more details, or refer to Appendix D in the Oracle Database Appliance Getting Started GuideYou can now run the oakcli update –patch 2.4.0.0.0 -clean command as follows:
Run the oakcli update –patch 2.4.0.0.0 -clean command to delete all temporary files on the local node.
See Also:
Enter theoakcli update -patch 2.4.0.0.0 -clean command to see more details, or refer to Appendix D in the Oracle Database Appliance Getting Started GuideSupport for Oracle Database 11g Release 2 (11.2.0.3.2)
Support for Oracle Linux 5.8, including the Unbreakable Enterprise Kernel
Patching new features, including the following:
Support to patch Oracle Grid Infrastructure and Oracle Database homes separately
New oakcli command options (-infra, -verify)
Improved system diagnostics, including improved logging and patching information
Support for local applications running Oracle Database Appliance
You can deploy Oracle Database Appliance without using a DNS.
Oracle recommends that you use a DNS so that you can use the Single Client Access Name (SCAN) for client requests. If you deploy the appliance without a DNS, but later set up a DNS and configure the SCAN name and addresses on the DNS, then you must configure the SCAN listeners manually after installation.
See Also:
Oracle Clusterware Administration and Deployment Guide for information about configuring SCANsFor 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.6 for Linux x86-64
E23730-19
Copyright © 2011, 2013, 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.