Oracle Database Release Notes

Oracle® Database

Release Notes

11g Release 2 (11.2) for HP-UX

E23561-06

December 2013

This document contains information that was not included in the platform-specific or

product-specific documentation for this release. This document supplements Oracle

Database Readme.

This document may be updated after it is released. To check for updates to this

document and to view other Oracle documentation, refer to the Documentation

section on the Oracle Technology Network (OTN) website:

http://www.oracle.com/technetwork/indexes/documentation/index.html

This document contains the following topics:

■ Certification Information

■ Latest Upgrade Information

■ Unsupported Products

■ Content Specific to Oracle Database 11g Release 2 (11.2.0.1)

■ Content Specific to Oracle Database 11g Release 2 (11.2.0.2)

■ Content Specific to Oracle Database 11g Release 2 (11.2.0.3)

■ Content Specific to Oracle Database 11g Release 2 (11.2.0.4)

■ Documentation Accessibility

1 Certification Information

The latest certification information for Oracle Database 11g Release 2 (11.2) is available

on My Oracle Support (formerly OracleMetaLink) at:

https://support.oracle.com

Bash Support

Bash is not supported on HP-UX Itanium.

2 Latest Upgrade Information

For late-breaking updates and best practices about preupgrade, postupgrade,

compatibility, and interoperability discussions, refer to Note 785351.1 on My Oracle

Support (formerly OracleMetaLink) that links to the "Oracle 11gR2 Upgrade

Companion" page.

https://support.oracle.com

3 Unsupported Products

A list of unavailable features and products is available in Section 2, "Features Not

Available or Restricted in This Release," in Oracle Database Readme.

In addition to the items listed in Section 2, "Features Not Available or Restricted in

This Release," in Oracle Database Readme, the following products or features are not

supported:

Database Smart Flash Cache Support

Database Smart Flash Cache is supported on Oracle Solaris and Oracle Linux only. For

release 11.2.0.1 on Oracle Linux, you must install the 8974084 patch.

Oracle Automatic Storage Management Cluster File System (Oracle ACFS) and Oracle Automatic

Storage Management Dynamic Volume Manager (Oracle ADVM) Support

Oracle ACFS and Oracle ADVM are not supported.

Oracle ODBC Driver Support

Oracle ODBC driver is not supported on HP-UX PA-RISC.

ASMLIB Support

ASMLIB is not supported on HP-UX.

4 Content Specific to Oracle Database 11g Release 2 (11.2.0.1)

The following content is specific to release 11.2.0.1:

■ Preinstallation Requirements for Release 11.2.0.1

■ Installation, Configuration, and Upgrade Issues for Release 11.2.0.1

■ Other Known Issues for Release 11.2.0.1

4.1 Preinstallation Requirements for Release 11.2.0.1

Refer to the installation guides for the preinstallation requirements.

4.2 Installation, Configuration, and Upgrade Issues for Release 11.2.0.1

Review the following sections for information about issues that affect Oracle Database

installation, configuration, and upgrade:

■ Oracle Automatic Storage Management Configuration Assistant Fails While

Installing Oracle Grid Infrastructure on a Standalone Server

4.2.1 Oracle Automatic Storage Management Configuration Assistant Fails While

Installing Oracle Grid Infrastructure on a Standalone Server

ASM_DISKSTRING

attribute is set to the default empty

string and if there is more

than one path to the disk, then Oracle Automatic Storage Management fails to detect

the disks while installing Oracle Grid Infrastructure on a standalone server. The

following error message appears:

ORA-15020: discovered duplicate ASM disk "HPISIHA_0000"

Workaround:

Use the command

srvctl modify asm -d

diskstring

to set the

ASM_DISKSTRING

attribute to a valid directory path. You may also change the permission on the

directory path of the devices in such a way that all the disks are accessed from the

same directory path.

This issue is tracked with Oracle bug 9117353.

4.3 Other Known Issues for Release 11.2.0.1

The following section contains information about issues related to Oracle Database 11g

and associated products:

■ Help Files Translation Issue for Spanish and French

■ Incorrect Reverse Ping Command from Oracle Management Service

■ Help Pages Fail to Load for Oracle Database Client (32-Bit)

■ SQL Developer Fails to Start

4.3.1 Help Files Translation Issue for Spanish and French

Oracle Universal Installer does not copy the translated help files to Oracle home

directory when you select the Spanish or French language.

Workaround:

On the Select Product Languages page, select both the Latin American Spanish and

Spanish to get the help files translated in Spanish; and select both the Canadian French

and French for the translated help files in French.

This issue is tracked with Oracle bug 9147106.

4.3.2 Incorrect Reverse Ping Command from Oracle Management Service

Oracle Management Service provides incorrect reverse ping command with Oracle

Enterprise Manager Database Control. The

emoms.properties

file shows:

emdrep.ping.pingCommand=/usr/sbin/ping <hostname>

Workaround:

Change the property in the

emoms.properties

file to:

emdrep.ping.pingCommand=/usr/sbin/ping <hostname> -n 3 -m 30

This issue is tracked with Oracle bug 9211800.

4.3.3 Help Pages Fail to Load for Oracle Database Client (32-Bit)

Oracle Universal Installer does not find the

clientinstaller_help.map

file and fails

to load the help pages for locales other than English.

Workaround:

Note: On all the computers using IPv6, you must specify

ping6

command (or an equivalent IPv6 command) instead of

ping

command.

Set

LANG=C

before running Oracle Universal Installer. This changes the installer locale

to English and the help content is available.

This issue is tracked with Oracle bug 9474214.

4.3.4 SQL Developer Fails to Start

After you install the Oracle Database, the SQL Developer might fail to start and the

following error message appears:

/bin/bash: bad interpreter: No such file or directory

Workaround:

Open the

sqldeveloper.sh

file in a text editor and change

#!/bin/bash

to the actual

location of Bash. For example:

#!/usr/local/bin/bash

This issue is tracked with Oracle bug 9335876.

5 Content Specific to Oracle Database 11g Release 2 (11.2.0.2)

The following content is specific to release 11.2.0.2:

■ Preinstallation Requirements for Release 11.2.0.2

■ Installation, Configuration, and Upgrade Issues for Release 11.2.0.2

■ Other Known Issues for Release 11.2.0.2

5.1 Preinstallation Requirements for Release 11.2.0.2

Refer to the installation guides for the preinstallation requirements.

5.2 Installation, Configuration, and Upgrade Issues for Release 11.2.0.2

Review the following sections for information about issues that affect Oracle Database

installation, configuration, and upgrade:

■ Relinking Fails on 32-Bit Client Installations

■ Logical Volume Manager Issue

■ Owner and Group Permissions Issue with Database Upgrade

■ Network Connection Issue Between Nodes in a Cluster

■ Performance Statistics Issue with Oracle Enterprise Manager Database Control

5.2.1 Relinking Fails on 32-Bit Client Installations

Relinking fails on 32-bit client installations because the relink script tries to load 64-bit

libraries.

Workaround:

After installation, manually remove the

-d64

flag from

JRE_MEMORY_OPTIONS

in the

$ORACLE_HOME/oui/oraparam.ini

file.

This issue is tracked with Oracle bug 10027801.

5.2.2 Logical Volume Manager Issue

Oracle Automatic Storage Management Configuration Assistant attempts to filter out

disks that are in use by the operating system’s logical volume manager (LVM). The

mechanism used to check the character device files from their default location,

/dev/rdisk/*

, may fail if the Oracle

grid

user does not have read permissions on the

corresponding block device. In rare cases, that failure can result in Automatic Storage

Management Configuration Assistant creating an Oracle ASM disk group on top of an

existing LVM volume group, corrupting the LVM content.

Workaround:

On servers where the system administrator has explicitly granted read/write access to

any

/dev/rdisk/*

files for use by Oracle ASM, enable read permissions on the

corresponding block device. The ownership of the block device need not be changed.

For example, if disk11 is available to Oracle ASM, a listing of the device files for that

disk usually shows the following:

$ ls -l /dev/*disk/disk11

brw-r----- 1 bin sys 5 0x000001 Apr 21 2009 /dev/disk/disk11

crw-rw---- 1 grid oinstall 132 0x00001c Apr 21 2009 /dev/rdisk/disk11

As the

root

user, enable read access to the block device with the following command:

chmod a+r /dev/disk/disk11

This results in:

$ ls –l /dev/*disk/disk11

brw-r--r-- 1 bin sys 5 0x000001 Apr 21 2009 /dev/disk/disk11

crw-rw---- 1 grid oinstall 132 0x000001 Apr 21 2009 /dev/rdisk/disk11

This issue is tracked with Oracle bug 9956769.

5.2.3 Owner and Group Permissions Issue with Database Upgrade

When you upgrade from Oracle Database release 10.

or 11.1 to 11.2 release using the

Oracle ASM discovery path,

/dev/rdsk/*

as default, ensure that the corresponding

/dev/rdisk*

disks use the same owners and group permissions as the legacy device

special file,

/dev/rdsk/*

disks. Otherwise, the database may fail to start.

Run the following command to map the legacy device special file disks and persistent

device special file disks:

ioscan -m dsf

Based on the mapping result, change the permissions in the corresponding persistent

device special file disks.

This issue is tracked with Oracle bug 10148343.

Note: There is no risk of this failure if the character device files

referenced by Oracle ASM have been created in an alternate location.

For example:

/gridbase/asmdisks

5.2.4 Network Connection Issue Between Nodes in a Cluster

When installing Oracle Grid Infrastructure for a Cluster, the

root.sh

script fails on the

second node with the following errors in the

ocssd.log

CSSD][105]clssnmLocalJoinEvent: takeover aborted due to cluster member node found

on disk

CRS-5818:Aborted command 'start for resource: ora.cssd 1 1' for resource

'ora.cssd'

Solution:

Servers with the latest 10 Gigabit Ethernet adapter require revision B.11.31.1009.01 or

later of the 10GigEthr-02 software bundle.

Run

swlist 10GigEthr-02

command to identify the current version on your HP

server. If it is older than the above mentioned version, then enter 10GigEthr-02 in the

Search field and download the latest software from the HP site:

https://h20392.www2.hp.com/portal/swdepot/index.do

This issue is tracked with Oracle bug 10175794.

5.2.5 Performance Statistics Issue with Oracle Enterprise Manager Database Control

The summary chart on the Oracle Enterprise Manager Cluster Performance page does

not show any data.

Workaround:

Perform the following steps:

1. Stop Oracle Enterprise Manager Database Control.

2. Add the following to the properties file,

$ORACLE_HOME/host_

dbuniquename/sysman/config/emoms.properties

oracle.sysman.db.rac.useRemoteCollection=false

3. Restart the Oracle Enterprise Manager Database Control.

This issue is tracked with Oracle bug 10129539.

5.3 Other Known Issues for Release 11.2.0.2

The following section contains information about issues related to Oracle Database 11g

and associated products:

■ SQL Developer Fails to Start

5.3.1 SQL Developer Fails to Start

After you install the Oracle Database, the SQL Developer might fail to start and the

following error message appears:

/bin/bash: bad interpreter: No such file or directory

Workaround:

Open the

sqldeveloper.sh

file in a text editor and change

#!/bin/bash

to the actual

location of Bash. For example:

#!/usr/local/bin/bash

This issue is tracked with Oracle bug 9335876.

6 Content Specific to Oracle Database 11g Release 2 (11.2.0.3)

The following content is specific to release 11.2.0.3:

■ Preinstallation Requirements for Release 11.2.0.3

■ Installation, Configuration, and Upgrade Issues for Release 11.2.0.3

■ Other Known Issues for Release 11.2.0.3

6.1 Preinstallation Requirements for Release 11.2.0.3

Refer to the installation guides for the preinstallation requirements.

6.2 Installation, Configuration, and Upgrade Issues for Release 11.2.0.3

Review the following sections for information about issues that affect Oracle Database

installation, configuration, and upgrade:

■ SEMMNU Kernel Parameter Issue During Oracle Grid Infrastructure Installation

■ Oracle Grid Infrastructure Upgrade Fails with Oracle ASM Upgrade

■ Permission Issues with Oracle Cluster Registry

■ Fixup Script Does Not Set maxssiz_64bit Kernel Parameter

■ Fixup Script Does Not Set shmmni and shmseg Kernel Parameters

■ OC4J Error After Upgrading Oracle Grid Infrastructure to 11.2.0.3 Release

■ Automatic SSH Configuration Issue for HP-UX

■ Network Connection Issue Between Nodes in a Cluster

6.2.1 SEMMNU Kernel Parameter Issue During Oracle Grid Infrastructure Installation

During an Oracle Grid Infrastructure installation, if you are prompted to run the

runfixup.sh

script to adjust the value of the

SEMMNU

kernel parameter, you might see

the following error message:

NOTE: The requested changes could not be applied to the currently

running system, for the following reasons:

- The tunable 'semmnu' cannot be changed without a reboot.

* The requested changes have been saved, and will take effect at

next boot.

Workaround:

Set the value of

SEMMNU

to an appropriate value before installation, or ignore the error

message and continue the installation. After the installation completes, restart the

server to implement the kernel parameter change.

This issue is tracked with Oracle bug 12811986.

6.2.2 Oracle Grid Infrastructure Upgrade Fails with Oracle ASM Upgrade

When attempting to upgrade to Oracle Grid Infrastructure 11.2.0.2 or 11.2.0.3 from

Oracle ASM from version 11.1.0.7, if you choose to upgrade Oracle ASM during the

Oracle Grid Infrastructure upgrade and the Oracle ASM 11.1.0.7 installation is owned

by a different user than the Oracle Clusterware installation, the upgrade fails.

Workaround:

Change the working path to the new Grid Infrastructure home created by the upgrade

attempt.

Run the following command to manually upgrade the Oracle ASM installation:

Grid_home_for_11_2/bin/asmca

This issue is tracked with Oracle bug 12741662.

6.2.3 Permission Issues with Oracle Cluster Registry

When the Cluster Verification Utility performs the OCR Integrity check, the

sharedness check might fail due to the user not having the permission to access the

device used for the Oracle Cluster Registry. The error might look similar to the

following:

PRVF-4172 : Check of OCR device "device_used_for_OCR" for sharedness

failed Could not find the storage

Workaround:

Check the permissions of the device identified in the error message,

device_used_for_

OCR

. While logged in as the

root

user, grant the user permission to access the device.

This issue is tracked with Oracle bug 10064738.

6.2.4 Fixup Script Does Not Set maxssiz_64bit Kernel Parameter

The

fixup.sh

script does not set the kernel parameter,

maxssiz_64bit

, to a minimum

value required for the successful database installation.

Workaround:

Run the following command as the

root

user to tune the parameter:

# /usr/sbin/kctune maxssiz_64bit=1073741824

This issue is tracked with Oracle bug 12746701.

6.2.5 Fixup Script Does Not Set shmmni and shmseg Kernel Parameters

The

fixup.sh

script does not set the kernel parameters,

shmmni

and

shmseg

, to a

minimum value required for the successful database installation.

Workaround:

Run the following commands as the

root

user to tune the parameters:

# /usr/sbin/kctune shmmni=4096

# /usr/sbin/kctune shmseg=512

This issue is tracked with Oracle bug 12739313.

6.2.6 OC4J Error After Upgrading Oracle Grid Infrastructure to 11.2.0.3 Release

OC4J may remain enabled causing an error after you upgrade Oracle Grid

Infrastructure to 11.2.0.3 release. The

rootupgrade.sh

log file shows the following

error message:

PRKO-2116: OC4J is already enabled.

Workaround:

Use the following procedure to disable and stop the OC4J resource:

1. While the Oracle Clusterware stack is running, enter the following command:

$ srvctl config oc4j

If the output of this command shows that OC4J is enabled, then enter the

following command to disable OC4J:

$ srvctl disable oc4j

2. Run the following command to check if OC4J is running:

$ srvctl status oc4j

3. If the output of the command in the earlier step shows that OC4J is running, then

stop OC4J as follows:

$ srvctl stop oc4j

4. Confirm that the OC4J resource is no longer running by entering the following

command:

$ srvctl status oc4j

This issue is tracked with Oracle bug 12845598.

6.2.7 Automatic SSH Configuration Issue for HP-UX

Automatic SSH configuration is not available at the time of this release due to an issue

with the installer.

Workaround:

Perform manual SSH configuration as described in section "D.1 Configuring SSH

Manually on All Cluster Nodes" in Oracle Grid Infrastructure Installation Guide for

HP-UX.

This issue is tracked with Oracle bug 9979216.

6.2.8 Network Connection Issue Between Nodes in a Cluster

When installing Oracle Grid Infrastructure for a Cluster, the

root.sh

script fails on the

second node with the following errors in the

ocssd.log

CSSD][105]clssnmLocalJoinEvent: takeover aborted due to cluster member node found

on disk

CRS-5818:Aborted command 'start for resource: ora.cssd 1 1' for resource

'ora.cssd'

Solution:

Servers with the latest 10 Gigabit Ethernet adapter require revision B.11.31.1009.01 or

later of the 10GigEthr-02 software bundle.

Run

swlist 10GigEthr-02

command to identify the current version on your HP

server. If it is older than the above mentioned version, then enter 10GigEthr-02 in the

Search field and download the latest software from the HP site:

https://h20392.www2.hp.com/portal/swdepot/index.do

This issue is tracked with Oracle bug 10175794.

6.3 Other Known Issues for Release 11.2.0.3

No known issues at this time.

7 Content Specific to Oracle Database 11g Release 2 (11.2.0.4)

The following content is specific to release 11.2.0.4:

■ Preinstallation Requirements for Release 11.2.0.4

■ Installation, Configuration, and Upgrade Issues for Release 11.2.0.4

■ Other Known Issues for Release 11.2.0.4

7.1 Preinstallation Requirements for Release 11.2.0.4

Refer to the installation guides for the preinstallation requirements.

7.2 Installation, Configuration, and Upgrade Issues for Release 11.2.0.4

Review the following sections for information about issues that affect Oracle Database

installation, configuration, and upgrade:

■ Automatic SSH Configuration Issue

■ Oracle Grid Infrastructure Upgrade Fails with Oracle ASM Upgrade

■ Permission Issues with Oracle Cluster Registry

■ Network Connection Issue Between Nodes in a Cluster

■ Prerequisite Check for Memory Fails While Installing a Database Client (32-Bit)

7.2.1 Automatic SSH Configuration Issue

Automatic SSH configuration is not available at the time of this release due to an issue

with the installer.

Workaround:

Perform manual SSH configuration as described in section "D.1 Configuring SSH

Manually on All Cluster Nodes" in Oracle Grid Infrastructure Installation Guide for

HP-UX.

This issue is tracked with Oracle bug 9979216.

7.2.2 Oracle Grid Infrastructure Upgrade Fails with Oracle ASM Upgrade

When attempting to upgrade to Oracle Grid Infrastructure 11.2.0.2, 11.2.0.3, or 11.2.0.4

from Oracle ASM from version 11.1.0.7, if you choose to upgrade Oracle ASM during

the Oracle Grid Infrastructure upgrade and the Oracle ASM 11.1.0.7 installation is

owned by a different user than the Oracle Clusterware installation, the upgrade fails.

Workaround:

Change the working path to the new Grid Infrastructure home created by the upgrade

attempt.

Run the following command to manually upgrade the Oracle ASM installation:

Grid_home_for_11_2/bin/asmca

This issue is tracked with Oracle bug 12741662.

7.2.3 Permission Issues with Oracle Cluster Registry

When the Cluster Verification Utility performs the OCR Integrity check, the

sharedness check might fail due to the user not having the permission to access the

device used for the Oracle Cluster Registry. The error might look similar to the

following:

PRVF-4172 : Check of OCR device "device_used_for_OCR" for sharedness

failed Could not find the storage

Workaround:

Check the permissions of the device identified in the error message,

device_used_for_

OCR

. While logged in as the

root

user, grant the user permission to access the device.

This issue is tracked with Oracle bug 10064738.

7.2.4 Network Connection Issue Between Nodes in a Cluster

When installing Oracle Grid Infrastructure for a Cluster, the

root.sh

script fails on the

second node with the following errors in the

ocssd.log

CSSD][105]clssnmLocalJoinEvent: takeover aborted due to cluster member node found

on disk

CRS-5818:Aborted command 'start for resource: ora.cssd 1 1' for resource

'ora.cssd'

Solution:

Servers with the latest 10 Gigabit Ethernet adapter require revision B.11.31.1009.01 or

later of the 10GigEthr-02 software bundle.

Run

swlist 10GigEthr-02

command to identify the current version on your HP

server. If it is older than the above mentioned version, then enter 10GigEthr-02 in the

Search field and download the latest software from the HP site:

https://h20392.www2.hp.com/portal/swdepot/index.do

This issue is tracked with Oracle bug 10175794.

7.2.5 Prerequisite Check for Memory Fails While Installing a Database Client (32-Bit)

When installing a database client (32-bit), the memory requirement check fails with the

following error:

PRVF-07562: Sufficient available memory is not available on node "{0}" [Required

available memory = {1}]

Workaround:

None

This issue is tracked with Oracle bug 17552672.

7.3 Other Known Issues for Release 11.2.0.4

The following section contains information about issues related to Oracle Database 11g

and associated products:

■ Listener Fails to Start After a Second Database Installation

7.3.1 Listener Fails to Start After a Second Database Installation

When a database is installed the second time on a system, the Network Configuration

Assistant fails to start the listener.

Workaround:

Use any one of the following workarounds:

■ Skip the Network Configuration Assistant and proceed with the installation.

■ Edit the

ORACLE_HOME2/network/admin/listener.ora

file and change the port

value to a non-conflicting value.

■ Run the following command to start the listener:

ORACLE_HOME2/bin/lsnrctl start listener

This issue is tracked with Oracle bug 17580585.

8 Documentation Accessibility

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

Access to Oracle Support

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

visit

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs

if you are hearing

impaired.

Oracle Database Release Notes, 11g Release 2 (11.2) for HP-UX

E23561-06

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 END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware,

and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition

Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs,

including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license

terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

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.