Precautions for installing or upgrading to Oracle 11.2.0.3 on AIX

For details, see:
Oracle Database Release Notes
11g Release 2 (11.2) for ibm aix on POWER Systems (64-Bit)
Part Number E23560-03
1. 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:
Monitoring Issue with Oracle Enterprise Manager Database Control
ORA-00600 Error During Database Upgrade
Warning Message While Downloading Software Updates for Oracle Database Client
Role Permissions Issue with Oracle ASM Configuration Assistant, SQL * Plus, X Terminal
Cluster Verification Utility Issue in Checking Network Parameters
Oracle Notification Service Issue After Shared Oracle RAC Database Upgrade
Automatic SSH Configuration Issue
Cluster Verification Utility Check Fails on AIX 6.1 and Later
2. Monitoring Issue with Oracle Enterprise Manager Database Control
Monitoring in memory access mode is not supported for databases.
This issue is tracked with an Oracle bug 6498439.
3. ORA-00600 Error During Database Upgrade
When you upgrade from Oracle9i Database Release 2 to Oracle Database 11g Release 2, the database upgrade fails with the following error:
ORA-00600: internal error code, arguments: [ktsxaff1]
Workaround:
Set _ affinity_on = false in the SPFILE of Oracle Database Release 9.2 before you upgrade.
This issue is tracked with an Oracle bug 6615695.
4. Warning Message While Downloading Software Updates for Oracle Database Client
After specifying the oraparam. ini file, when you run the Oracle Universal Installer to download software updates for Oracle Database Client, the following warning message may appear:
WARNING: User specified paramFile:/local_dir/oraparam. ini CLUSTER_NODES = {} not found
Workaround:
Ignore the warning message.
This issue is tracked with an Oracle bug 12690717.
5. Role Permissions Issue with Oracle ASM Configuration Assistant, SQL * Plus, X Terminal
Ensure that the oracle_devmgmt role is set before running administrative tools, such as, Oracle ASM Configuration Assistant and SQL * Plus, for management of Oracle Automatic IC Storage Management Cluster File System and Oracle Automatic IC Storage Management Dynamic Volume Manager. also, when entering a new X terminal (or using the associated commands, such as uxterm and aixterm ), the oracle_devmgmt role necessary for the administration of Oracle Automatic Storage Management Cluster File System and Oracle Automatic Storage Management Dynamic Volume Manager is not properly set.
Workaround:
Run the following command before running adminstrative tools or after opening a new terminal:
$ Swrole oracle_devmgmt
Check that the swrole is set to oracle_devmgmtby running the following command:
$ Rolelist-e
6. Cluster Verification Utility Issue in Checking Network Parameters
During an Oracle RAC database installation, the Cluster Verification Utility may not check the network parameters (tcp_sendspace, tcp_recvspace, udp_sendspace, udp_recvspace, sb_max, rfc1323) correctly. this may happen as part of the prerequisite check or if you run the following command:
Cluvfy stage-pre crsinst
Workaround:
Establish a symlink/etc/no to/usr/sbin/no.
This issue is tracked with an Oracle bug 13077654.
7. Oracle Notification Service Issue After Shared Oracle RAC Database Upgrade
After you complete an upgrade from shared Oracle Clusterware Release 11.1 to shared Oracle Grid Infrastructure Release 11.2, you may encounter an error with Oracle Notification Service. the first node shows the Oracle Notification Service file, ora. ons, is offline.
Workaround:
Perform. the following steps:
Log in as the Oracle Grid Infrastructure installation owner.
Run the following commands to find the Oracle Notification Service processes on the nodes and stop them:
$ Ps-ef | grep "ons-d"
$ Kill-9 pid1 pid2
Change directory to bin in the Oracle Grid Infrastructure home, and enter the command crsctl start res ora. ons. for example, if the grid home is/u01/grid, then enter the following commands:
$ Chdir/u01/grid/bin
$./Crsctl start res ora. ons
This issue is tracked with an Oracle bug 9133235.
8. 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 installing ing SSH Manually on All Cluster Nodes" in Oracle Grid Infrastructure Installation Guide for ibm aix on POWER Systems.
This issue is tracked with an Oracle bug 9979216.
9. Cluster Verification Utility Check Fails on AIX 6.1 and Later
The prerequisite checker checks only for the AIX fix, IZ97457, regardless of the operating system TL version. The following are the correct Authorized Problem Analysis Reports (APARs) for the corresponding TL versions:
6100-03-use aix apar IZ89304
6100-04-use aix apar IZ89302
6100-05-use aix apar IZ89300
6100-06-use aix apar IZ89514
7100-00-use aix apar IZ89165
5300-11-use aix apar IZ98424
5300-12-use aix apar IZ98126
6100-04-use aix apar IZ97605
6100-05-use aix apar IZ97457
6100-06-use aix apar IZ96155
7100-00-use aix apar IZ97035
Note: before installation or upgrade, if the above requirements are not met, you must upgrade the operating system first. Otherwise, you will encounter some unsolved problems.
Workaround:
Before starting the Oracle Universal Installer, set the environment variable, IGNORE_PREADDNODE_CHECKS, to Y:
Export IGNORE_PREADDNODE_CHECKS = Y
This issue is tracked with an Oracle bug 13083120.
10. Other Known Issues for Release 11.2.0.3
The following section contains information about issues related to Oracle Database 11g and associated products:
Required Oracle Warehouse Builder Patches
Oracle Messaging Gateway Fails to Start on AIX 6.1 or Higher Systems
Oracle ACFS File Systems Go Into Offline State
Wallet Upload Issue with Oracle Wallet Manager
Oracle RAC and IBM Virtual I/O Servers on AIX
SQL Developer Release 1.5.5 Does Not Support JDK Version 1.5.x
Oracle Management Service Restart Fails Intermittently
11. Required Oracle Warehouse Builder Patches
If you plan to install Oracle Warehouse Builder, then after you install Oracle Database, but before you create the Oracle Warehouse Builder repository, you must complete the following procedure:
Download patch 12973504 from the My Oracle Support Web site.
Extract the contents to a directory, for example,/tmp/12973504.
Verify that the ORACLE_HOME environment variable is set to the 11.2.0.2 DB home.
Run the Opatch utility with the right parameters to proceed with the Oracle Warehouse Builder one-off installation:
Cd/tmp/12973504
Opatch apply
Navigate to $ ORACLE_HOME/owb/patches/bug12973504.
Run the script, fix_bug12973504.sh.
After you have edited the files, you can install Oracle Warehouse Builder.
This issue is tracked with an Oracle bug 11772716.
12. Oracle Messaging Gateway Fails to Start on AIX 6.1 or Higher Systems
When attempting to start the Oracle Messaging Gateway using the DBMS_MGWADM.STARTUP procedure, the job started by this procedure fails with following error:
ORA-32830: Result code-8 returned by Messaging Gateway agent
In the Oracle Messaging Gateway logs (located at $ ORACLE_HOME/mgw/log), you see messages similar to the following:
> 2010-06-18 10:16:01 mgw c-Bootstrap 0 LOG process-id = 2908272
Bootstrap program starting
> 2010-06-18 10:16:02 mgw c-Bootstrap 0 LOG process-id = 2908272
Failed to create Java VM: retCode =-4
> 2010-06-18 10:16:02 mgw jvm log
JVMJ9VM015W Initialization error for library j9gc23 (2): Failed to instantiate
Heap; 64 M requested
Problem Summary: Java Instantiation fails on systems running AIX 6.1 or higher, which leads to this issue. IBM is aware of this issue and is tracking this through Authorized Program Analysis Report (APAR) IZ55237. Contact IBM Support for specific patches for the AIX version and level running in your environment.
Workaround:
Modify the listener. ora file for the Messaging Gateway listener to implement MPROTECT_TXT = OFF. For example:
SID_LIST_LISTENER =
 
(SID_LIST =
(SID_DESC =
(SID_NAME = mgwextproc)
 
(ENVS = "LIBPATH = [ORACLE_HOME]/jdk/jre/bin: [ORACLE_HOME]/jdk/jre/bin/classic:
[ORACLE_HOME]/lib, MPROTECT_TXT = OFF ")
(ORACLE_HOME = [ORACLE_HOME])
(PROGRAM = extproc ))
)
)
This issue is tracked with an Oracle bug 12842870.
13. Oracle ACFS File Systems Go Into Offline State
Under heavy load, resulting in operating system paging, Oracle ACFS file systems may go into an offline state.
Workaround:
Request a one-off patch for release 11.2.0.3.
Note:
After installing the patch, unmount each Oracle ACFS file system and run the following command (from one node only) on each ACFS file system:
Fsck-y-o a/dev/asm/volume_name
Then, remount the Oracle ACFS file system.
This issue is tracked with an Oracle bug 13255295.
14. Wallet Upload Issue with Oracle Wallet Manager
Oracle Wallet Manager fails to upload wallet to Oracle Internet Directory server, giving the following error message:
Exception while initialization: java. security. NoSuchAlgorithmException:
Algorithm SunX509 not available
Workaround:
None
This issue is tracked with an Oracle bug 10144879.
15. Oracle RAC and IBM Virtual I/O Servers on AIX
If you use Virtual I/O (VIO) Servers with Oracle RAC, then there are special concerns for ensuring highly available interconnect networks. refer to My Oracle Support note 1356461.1, which is available at the following URL:
Https://support.oracle.com/
16. SQL Developer Release 1.5.5 Does Not Support JDK Version 1.5.x
The dialogs to create and edit objects in SQL Developer release 1.5.5 fail to open as JDK version 1.5.x is not supported.
Workaround:
Use any one of the following workarounds:
Upload the JDK to version 1.6.
Enter the SQL statement on the SQL Worksheet.
Use SQL Developer from a client desktop (non-AIX ).
Use the sqlplus command to start SQL * Plus.
This issue is tracked with an Oracle bug 9195473.
17. Oracle Management Service Restart Fails Intermittently
Oracle Management Service restart fails intermittently as Oracle Enterprise Manager Database Control fails to start with the following error message:
The socket name is already in use.
 
Workaround:
If Oracle Enterprise Manager Database Control does not shut down successfully, then manually stop the process.
This issue is tracked with an Oracle bug 9118229.

For more information about Oracle, see Oracle topics page http://www.bkjia.com/topicnews.aspx? Tid = 12