Oracle Appliance Kit
 
Oracle Database Appliance
 

PLA-Support>Database Technology>Engineered Systems>Oracle Database Appliance>DB: ODA_EST
 
.Old GCS Categories>ST>Server>Engineered Systems>Oracle Database Appliance>Install
 
.Old GCS Categories>ST>Server>Engineered Systems>Oracle Database Appliance>Patching
 

In this document

Applies to:

Purpose

This document currently lists the Patches, Known issues and Workarounds for Oracle Database Appliance.

Scope

The contents of this document is specific to Oracle Database Appliance

Details

Terminology

Oracle Database Appliance patches and software consists the following components:

• ODA Bundle Patch
  Contains patches to the following components: OS, Component Firmware and Oracle Appliance Manager Modules, Grid Infrastructure, and RDBMS. 
• End-User GI/RDBMS Clone files
  Contains the latest Grid Infrastructure and RDBMS components, for deployment on an Oracle Database Appliance in the "shipped from factory" state, or an Oracle Database Appliance that has been re-imaged using the OS ISO Image.
• OS ISO Image
  Used to restore the OS to the "shipped from factory" state. Use only when necessary.

Latest Releases

Release History

Known Issues for 2.3.0.0.0

1. Issue: Unable to 'update -patch 2.3.0.0.0 --infra' prior to the deployment.  You will receive the following error:
   
   
   Failed to open /crs/install/crsconfig_params : No such file or directory at /opt/oracle/oak/lib/oakutilslib/oakutils.pm line 1338.
ERROR: Failed to apply the patch
   
   Workaround: Please complete the deployment first, and patch ‘--infra’ again.
2. Issue: Unable to delete all database homes. 
   Workaround:  Please create a new home before you delete the very last db homes on the system.  If you only have one home shown as below, please do not delete OraDb11203_home1, until you create a new database home first. 
   
   
   # oakcli show dbhomes

  Oracle Home Name      Oracle Home version                 Home Location
  OraDb11203_home1      11.2.0.3.3(13923374,13919095)       /u01/app/oracle/product/11.2.0.3/dbhome_1
3. Issue: Failed to create a database due to ora-12700.  There are few typos for nls_territory, database language, and database characterset.
   Workaround: Please contact Oracle support regarding how to manually correct lines in /opt/oracle/oak/pkgrepos/System/2.3.0.0.0/bin/genUpgradeConfig.pm
4. Issue: etc/init.d/dbconsole not updated when upgrading db successfully
   Workaround: Manually modify the dbconsole script in the init.d with the new home.
5. Issue: Unable to delete a database if it failed to start.
   Workaround: Manually start the database first.  Or if the database home only host this database, then delete the database home.
6. Issue: Running ipmitool or ipmiflash intermittently fails with "Failed to connect: Busy", i.e. oakcli validate, oakcli update -patch --verify.
   Workaround: Wait one-minute and retry.
7. Issue: Unable to Roll back to previous versions.
   Workaround: Roll back to previous versions is not supported.
8. Issue:   If you upgraded ODA from 2.2 to 2.3, if one of the nodes is powered down, and if you try to restart the clusterware on the remaining node; the clusterware won't come up successfully, until you power up the down node.  This does not happen on a fresh deployed ODA 2.3 system.  When one of the nodes is powered down, and on the other node no clusterware restart is attempted, the clusterware and instances will be  running without any issue.
   Workaround: This is a known issue. Please see the following Note for details:
   <Document 1486965.1> - Single Node ODA clusterware does not Startup Correctly if the Second Node is down.
9. Issue: When running on ODA version 2.3 with multiple Oracle Homes (11.2.0.2 & 11.2.0.3), installing additional products in an existing database home (For example, "Oracle Database 11g Examples"), causes 'okacli show dbhomes' and 'oakcli show version' commands to report errors.
   
   
   # oakcli show dbhomes
Bad index while coercing array into hash at /opt/oracle/oak/lib/oakutilslib/oakutils.pm line 2133.

# oakcli show version -detail
Reading the metadata. It takes a while...
Bad index while coercing array into hash at /opt/oracle/oak/lib/oakutilslib/oakutils.pm line 2133.
   
   Workaround: This is a known issue as reported as in bug 14511622. Please contact Oracle Support for a fix.
10. Issue: In the previous version, we set use_large_pages=TRUE.  For "new" deployment, we adapt the best practice to set use_large_pages=ONLY.  If you did not do the sizing properly based on Appendix C of the Getting Started Guide for Oracle Database Appliance; and your database has bigger SGA, you might receive the following similar messages in the alert log file.  We do not recommend you change back to "TRUE".  It's in your best interest that you receive the early warning that your database might run into memory issue and eventually it will affect the performance.  It's better not to create and start more 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

Known Issues for 2.2.0.0.0

1. Issue: ASR registration failed during deployment Step 23
   Workaround:  Please refer "ASR Troubleshooting" section in MOS note 1427924.1.
   
   
   For configuring ASR post deployment,  refer "Configuring ASR post deploy" section in MOS note 1427924.1
2. Issue:  Unable to Roll back to previous versions
   Workaround : Roll back to previous versions is not supported.
3. Issue:  Subsequent Reboot after successful patching to 2.2.0.0.0 displays the warning message "kdump ramdisk not enough space to save a vmcore.”
   Workaround:  The message is a warning and can be ignored. 
                        Modify the /boot/grub/grub.conf file, specifically the crashkernel parameter in the boot line for kernel /vmlinuz-2.6.32-300.11.1.e15uek  from crashkernel=256M@16M to crashkernel=256M@64M.
4. Issue:  If the database names are in upper case, you will be unable to execute 'oakcli update -patch 2.2.0.0.0 --database <DB>' command.
   Workaround: Please refer to Note 1453154.1, to manually upgrade your databases.
                      /u01/app/oracle/product/11.2.0.3/dbhome_1/bin/dbua -silent -keepHiddenParams -dbName <DB>
5. Issue: After applying 2.2.0.0.0, the permissions on the 'oracle' executable are incorrect.
   Workaround: Change the permissions on the file as shown below
   
   As a 'root' user, please perform the following two steps:

# chmod 6751 /u01/app/oracle/product/11.2.0/dbhome_1/bin/oracle
# sh /u01/app/oracle/product/11.2.0/dbhome_1/root.sh


Known Issues for ODA 2.1.0.x.x only

1. Issue: If no public network is configured for ILOM, or if ILOM public network is configured under different subnet than the host public network, patching 2.1.0.3.0 will fail with an error message as shown below.
   
   
   
   INFO: Patching ILOM and BIOS...
   WARNING: IP address  172.32.17.210 unreachable
   INFO: Generated temporary ILOM user: iu_qtgqf
   
   
   Workaround: Use Keyboard Controller Style (KCS) interface to apply ILOM/BIOS patches as shown below.
   
   
   
   [root@odabox1 ~] cd /opt/oracle/oak/pkgrepos/thirdpartypkgs/Firmware/Ilom/SUN/541-4116-03/3.0.14.13.a_r70764/Base
[root@odabox1 Base]# ls
ILOM-3_0_14_13_a_r70764-Sun_Fire_X4370M2.pkg
[root@odabox1 Base]# ipmiflash -v write ILOM-3_0_14_13_a_r70764-Sun_Fire_X4370M2.pkg force script config delaybios warning=0

-- Wait 3-4 minutes to allow ILOM/SP to finish rebooting after patching and issue the following command:

[root@odabox1 Base]# ipmitool chassis power cycle
2. Issue: ASR registration failed during deployment Step 23
   Workaround:  Please refer "ASR Troubleshooting" section in MOS note 1427924.1.
   
   
   For configuring ASR post deployment,  refer "Configuring ASR post deploy" section in MOS note 1427924.1
3. Issue : Running ipmitool or ipmiflash intermittently fails with "Failed to connect: Busy"
   Once failed, there is one-minute timeout.
   Workaround: Wait for one minute and then retry the command.
4. Issue:  Re-deployment using cleandeploy.pl will fail to remove hidden filesleav
   Workaround: Manually remove files under '/opt/oracle/oak/conf/' subdirectory specifically files with the following pattern before attempting Deployment.
• .clustered,
• .configlock,
• .licensekey_tmp,
• .licensekey
5. Issue: The new Western Digital (WD) OS disks and Hitachi SAS Disks firmware will not be updated by this patch, instead a warning messages is reported to the console.
   Workaround : Ignore the warning message for now. The firmware will be updated in the next patch.
6. Issue:  Unable to Roll back to previous versions using the following
   
   • Roll back from 2.1.0.2.0 to 2.1.0.1.0 by running 'oakcli update -patch 2.1.0.1.0' command will receive "no need to patch" for all components.
     SUCCESS: <component(s)> is/are up to date, no need to patch.
     oak rpm will remain at 2.1.0.2.0_120111.1
   • Trying to roll back from 2.1.0.2.0 to 2.1.0.0.0 by running 'oakcli update -patch 2.1.0.0.0' will receive
     ERROR: Failed to run /opt/oracle/oak/pkgrepos/System/2.1.0.0.0/bin/pkg_install.pl --ver 2.1.0.0.0 --conf PatchImage.xml --install_args.
   Workaround : Roll back to previous versions is not supported.

Useful Links

• Oracle Appliance Manager Configurator http://www.oracle.com/technetwork/server-storage/engineered-systems/database-appliance/oracle-database-appliance-manager-1352946.zip
• Quick Start  http://docs.oracle.com/cd/E22693_01/doc.21/e26568.pdf
• <Document 1417713.1> - Information Center: Oracle Database Appliance

References

This solution has no attachment