|
Oracle9i Application Server Release Notes
Release 2 (9.0.3) for AIX-Based Systems, hp HP-UX PA-RISC (64-bit), hp Tru64 UNIX, and Linux x86 Part No. B10227-11 |
|
|
|
|
Oracle9i Application Server Release Notes
Release 2 (9.0.3) for AIX-Based Systems, hp HP-UX PA-RISC (64-bit), hp Tru64 UNIX, and Linux x86 Part No. B10227-11 |
|
|
|
|
This chapter describes installation and migration issues and their workarounds associated with Oracle9iAS. It covers the following topics:
In addition to the issues documented in the Installation Guide., note the following preinstallation issues:
Section 3.1.1, "Setting the ORACLE_HOME Environment Variable on HP-UX"
Section 3.1.3, "Installing Oracle9iAS on IBM AIX-Based Systems"
Section 3.1.7, "Additional Preinstallation Steps for UnitedLinux"
Section 2.5.4.1 of the Installation Guide states that you must make sure the ORACLE_HOME environment variable points to an absolute path directory. This is true for IBM-AIX, Tru64 UNIX and Linux, however it is not a requirement for HP-UX.
Oracle recommends that you remove the /var/opt/oracle/emtab file from Tru64 systems before installing Oracle9iAS Release 2 (9.0.3).
If you do not remove the /var/opt/oracle/emtab file before installing Oracle9iAS Release 2 (9.0.3), certain Oracle9iAS Release 2 (9.0.3) products may be unusable after completing the installation.
If you are using IBM JDK 1.3.1 SR-3 , the /usr/java131/bin/java file may be hard linked to /usr/java131/jre/bin/java. Installing Oracle9iAS copies this link to the $ORACLE_HOME/jdk directory and causes Oracle specific JDK extensions to be ignored. To avoid this issue, enter the following commands before installing Oracle9iAS:
# cd /usr/java131/bin # mv java java.ORIG # ln -sf ../jre/bin/java ./java
The default JRE environment on RedHat may cause problems with the Oracle9iAS configuration assistants. Change the environment before installing Oracle9iAS.The IBMJava2-131 JRE is provided with RedHat AS 2.1 and, by default, the IBMJava2-131/bin directory is included in the value of the PATH environment variable. Remove any directory entries that contain references to IBMJava2-131 from the PATH environment variable. If the IBMJava2-131 JRE is required, restore the entries after completing the installation of Oracle9iAS.
Chapter 3 of the Installation Guide lists the requirements for installing Oracle9iAS. This section outlines the steps required to verify the hardware requirements:
To determine the physical RAM size, enter one of the following commands:
Table 3-1 Commands for Checking RAM
| Platform | Command |
|---|---|
| AIX | # /usr/sbin/lsattr -E -l sys0 -a realmem
|
| HP-UX | # /usr/sbin/dmesg | grep "Physical:"
|
| Linux | # grep MemTotal /proc/meminfo
|
| Tru64 UNIX | # /bin/vmstat -P | grep "Total Physical Memory"
|
If the size of the physical RAM installed in the system is less than the required size, you must install more memory before continuing.
To determine the size of the configured swap space, enter one of the following commands:
Table 3-2 Commands for Checking swap space
| Platform | Command |
|---|---|
| AIX | # /usr/sbin/lsps -a
|
| HP-UX | # /usr/sbin/swapinfo -a
|
| Linux | # grep SwapTotal /proc/meminfo
|
| Tru64 UNIX | # /sbin/swapon -s
|
If necessary, see your operating system documentation for information on how to configure additional swap space.
To determine the amount of disk space available in the /tmp directory, enter one of the following commands:
HP-UX:
# bdf /tmp
Other operating systems:
# df -k /tmp
To determine the amount of free disk space on the system, enter one of the following commands:
HP-UX:
# bdf
Other operating systems:
# df -k
Chapter 3 of the Installation Guide lists the requirements for installing Oracle9iAS. This section outlines the steps required to verify the software requirements:
To determine the operating system version, enter one of the following commands:
To determine the JDK version, enter one of the following commands:
On AIX, enter the following command to display information about the filesets and operating system patches:
# lslpp -h
On AIX, enter the following command to display APAR information:
# instfix -i
On HP-UX, enter the following command to display information about the installed software:
# /usr/sbin/swlist
On Linux, enter the following command to display information about the installed kernel:
# uname -r
On Linux, enter the following command to display information about the installed packages:
# rpm -qa
On Tru64 UNIX, enter the following command to display information about the installed software:
# /usr/sbin/setld -i | more
In addition to the requirements in Section 1.3.1, "UnitedLinux Requirements", perform the following steps before installing Oracle9iAS 9.0.3 on UnitedLinux:
Create the following sybolic links. These are required because some Oracle makefiles have hard coded paths to the /usr/bin/gcc directory.
prompt> ln -s /opt/gcc295/bin/gcc /usr/bin/gcc prompt> ln -s /opt/gcc295/bin/gcc /usr/bin/cc
Create the following symbolic link for the perl executable:
prompt> ln -sf /usr/bin/perl /usr/local/bin/perl
Verify that the hostname command returns the fully qualified hostname as shown below:
$ hostname hostname.domainname
If any Java packages are installed on the system, unset the Java environment variables, for example JAVA_HOME.
|
Note: If you are installing UnitedLinux on a clean system, Oracle recommends that you do not install the any of the Java packages supplied with the UnitedLinux distribution. |
Unset the Oracle related environment variables for the account used to install Oracle9iAS 9.0.3. For example, make sure that the .profile, .login file and /etc/profile.d files do not set the ORACLE_HOME, PATH and LD_LIBRARY_PATH environment variables with references to Oracle binaries or directories.
If the orarun package was installed on the system, complete the following steps as the oracle user to reset the environment:
Enter the following commands:
prompt> cd /etc/profile.d prompt> mv oracle.csh oracle.csh.bak prompt> mv oracle.sh oracle.sh.bak prompt> mv alljava.sh alljava.sh.bak prompt> mv alljava.csh alljava.csh.bak
Use any text editor to comment out the following line from the $HOME/.profile file:
. ./.oracle
Log out of the oracle user account.
Log into the oracle user account for the changes to take effect.
Make sure that the ports listed in Appendix A of the Installation Guide are available. Ports such as 1810 are required for Enterprise Manager and must be available. For some component, the Installer can assign free ports to the component from a range as documented in the Appendix. For example, the Oracle9iAS Web Cache Administration component requires three free ports in the port range from 4000 - 4030. If the correct number of ports in the appropriate range are not available for any component, errors will occur during installation.
To give the OSDBA group the MLOCK privilege:
As the root user, enter the following command:
# setprivgrp dba MLOCK
To ensure that the dba group retains the MLOCK privilege after the system reboots, create the /etc/privgroup file, if it does not exist on your system, and add the following line to it:
dba MLOCK RTPRIO RTSCHED
You cannot install Oracle9iAS in a clustered environment, that is, Oracle does not support installing Oracle9iAS in a clustered environment for AIX-Based Systems, hp-ux PA-RISC (64-bit), hp Tru64 UNIX, or Linux x86. The Operating System Requirements section of the Installation Guide incorrectly lists various clusterware requirements. This clusterware software is not required or supported.
This section describes the following installation issues:
Section 3.2.1, "Oracle9iAS 9.0.2.1 patch for HP-UX, IBM AIX, and Tru64 UNIX"
Section 3.2.4, "Using Oracle9iAS Infrastructure 9.0.2 with IBM AIX 5L"
Section 3.2.5, "Additional Steps for Installing on UnitedLinux"
Please check http://metalink.oracle.com for product availability dates of Oracle9iAS 9.0.2.1 core patch-set on HP-UX, Tru64 UNIX and IBM AIX. Oracle9iAS 9.0.2.1 core patch-set is required if Oracle9iAS Release 2 (9.0.3) and Oracle9iAS Release 2 (9.0.2) mid-tier or infrastructure instances will be installed on same node.
By default, the installer only installs the English language files for Oracle9i Application Server. To install all available languages, run the following command to launch the installer instead of runInstaller setup.exe:
prompt> mount_point/9ias_903disk1/runInstallerNLS
Oracle9iAS installation might report that you have insufficient swap space to proceed with the install, even if you actually have the required swap space.
As a workaround, unset the TMP environment variable and restart the install.
If you want to use Oracle9iAS Infrastructure 9.0.2, as described in Chapter 1 of the Oracle9iAS Installation Guide, on IBM AIX 5L:
Note that Oracle9iAS 9.0.2 is now available for IBM AIX 5L.
If you install Oracle9iAS 9.0.3 using Oracle9iAS 9.0.2.0.1 Infrastructure running on AIX 4.3.3, you will encounter problems while adding Oracle9iAS 9.0.3 J2EE instances to clusters. To fix this issue, install the patch located in the following patch directory on the Oracle9iAS 9.0.3 CD-ROM.
CD_Mount_Point/patch/2640377
To install the patch, follow the instructions in the README file located in the patch directory.
When installing Oracle9iAS 9.0.3 on UnitedLinux 1.0, an error is displayed during the relinking phase. Do not close the Installer window. Complete the following steps to resolve the error:
Open a new terminal window.
Edit the $ORACLE_HOME/lib/sysliblist file and add the following entry to the end of the line:
-lgcc -L/opt/gcc295/lib/gcc-lib/i486-suse-linux/2.95.3
Run the following command:
prompt> $ORACLE_HOME/bin/genclntsh
Click Retry in the Installer window. The installation will continue without displaying further errors.
Some tools are not supplied or supported with Oracle9iAS Release 2 (9.0.3) on IBM AIX 5L systems. This issue is described in bug no. 2656597.
Table 3-5 lists the files and describes the tools that are not installed on IBM AIX 5L systems:
Table 3-5 Unsupported Tools on IBM AIX 5L
| File | Description |
|---|---|
$ORACLE_HOME/bin/loadpsp
|
This tool loads PLSQL Server pages into an Oracle database. Since this file is not supplied with Oracle9iAS on AIX 5L, use the tool on another platform such as AIX 4.3. This tool will be made available soon as a fix for bug no. 2656597. Check for availability of this fix on http://metalink.oracle.com.
|
$ORACLE_HOME/bin/sqlplus
|
This is the SQL command line tool used to connect to Oracle databases for development and administration tasks. The absence of SQL*Plus does not affect Oracle9iAS functionality. Since this file is not supplied with Oracle9iAS on AIX 5L, use the tool on another platform such as AIX 4.3. This tool will be made available soon as a fix for bug no. 2656597. Check for availability of this fix on http://metalink.oracle.com.
|
$ORACLE_HOME/bin/xml
|
This is the XML parser for C/C++. Since this file is not supplied with Oracle9iAS on AIX 5L, use the tool on another platform such as AIX 4.3. This tool will be made available soon as a fix for bug no. 2656597. Check for availability of this fix on http://metalink.oracle.com.
|
$ORACLE_HOME/bin/xmlcfg
|
This is the XML class generator. Since this file is not supplied with Oracle9iAS on AIX 5L, use the tool on another platform such as AIX 4.3. This tool will be made available soon as a fix for bug no. 2656597. Check for availability of this fix on http://metalink.oracle.com.
|
See the latest Release Notes on the documentation section of OTN for availability of patches for bug no. 2656597:
http://otn.oracle.com/docs
This section covers the following postinstallation issue:
Oracle9iAS install does not configure JServ by default. As a workaround, configure JServe using the Oracle Enterprise Manager Console after installation. Oracle Management Server has a reporting servlet that runs within JServ. In order to access this reporting servlet, configure JServ from the Oracle Enterprise Manager Console.
Infrastructure installs do not have JServ listed as an installed component in ORACLE_HOME/config/ias.properties. Therefore, JServ is, by default, not configurable after installation.
To make JServ configurable in the infrastructure install, edit the ias.properties file from ORACLE_HOME/config directory as shown below.
Change the following existing line (to append JServ to Components entry) from:
Components=Apache,J2EE,WebCache,SSO,OID
to
Components=Apache,J2EE,WebCache,SSO,OID,JServ
In addition to the issues documented in the Installation Guide., note the following Silent and Non-Interactive Installation issues:
This section covers the following deinstallation issues:
If you have only one Oracle9iAS instance (9.0.2x or 9.0.3) on your machine, then that instance also contains the active Oracle Enterprise Manager. Deinstalling that instance also removes the active Oracle Enterprise Manager. This is the desired result, and it does not cause any problems because no other instance depends on that active Oracle Enterprise Manager.
If you have multiple Oracle9iAS instances (9.0.2x or 9.0.3) on a machine, then you have to be careful when you deinstall an instance because all the instances on the machine share the same active Oracle Enterprise Manager. You need to ensure that you do not deinstall an instance that contains the active Oracle Enterprise Manager.
When you install an Oracle9iAS 9.0.3 instance on a machine that already contains Oracle9iAS 9.0.2x instances, the installer automatically switches the active Oracle Enterprise Manager to the Oracle9iAS 9.0.3 instance.
Before you deinstall an instance on a machine that contains multiple Oracle9iAS instances:
Determine which Oracle9iAS instance contains the active Oracle Enterprise Manager.
Check the ACTIVE_EMD_HOME entry in the /var/opt/oracle/emtab file.
If the instance you want to deinstall contains the active Oracle Enterprise Manager, switch the active Oracle Enterprise Manager to a remaining instance.
If you have a remaining instance that is of Oracle9iAS 9.0.3, you must switch your active Oracle Enterprise Manager to that instance. Otherwise, you can switch to an instance that is of Oracle9iAS 9.0.2x.
prompt> ORACLE_HOME/bin/emctl switch home
This displays a dialog where you can select another Oracle9iAS instance that contains the active Oracle Enterprise Manager.
Deinstall the instance.
If you have 9.0.2 or 9.0.3 and Release 2 (9.0.4) instances on the same computer, and you want to deinstall a 9.0.2 or 9.0.3 instance, perform these steps:
Apply patch 3234681 to your 9.0.2 or 9.0.3 instances. You can download the patch from OracleMetaLink (http://metalink.oracle.com). This patch is valid for all UNIX platforms, however when searching for this patch, specify the platform as Solaris Operating System (SPARC 64-bit).
Stop all processes associated with the instance you want to deinstall.
Run the installer to deinstall the 9.0.2 or 9.0.3 instance. Make sure you run the installer for the 9.0.2 or 9.0.3 instance.
For 9.0.2 and 9.0.3 instances, the installer is located in the oui/install directory at the same level as the Oracle home directory. For example, if the 9.0.2 or 9.0.3 Oracle home is /opt/oracle/orahome902, then the installer would be /opt/oracle/oui/install/runInstaller.
If you have multiple 9.0.2 and/or 9.0.3 instances on the same computer, these instances share an Oracle Enterprise Manager. This is the "active Oracle Enterprise Manager". When you deinstall the instance that contains the active Oracle Enterprise Manager using the installer, the installer needs to switch the active Oracle Enterprise Manager to one of the remaining instances. If there is only one remaining instance, then the installer automatically makes it the active Oracle Enterprise Manager. If more than one instance remain, the installer prompts you to select the instance to contain the active Oracle Enterprise Manager.
Unlike 9.0.2 or 9.0.3 instances, Oracle9iAS Web Cache Release 2 (9.0.4) instances on the same computer do not share an Oracle Enterprise Manager. Each Release 2 (9.0.4) instance has its own Oracle Enterprise Manager.
Because Release 2 (9.0.4) instances do not share an Oracle Enterprise Manager, you must not select a Release 2 (9.0.4) instance to contain the active Oracle Enterprise Manager. You must select a 9.0.2 or 9.0.3 instance to contain the active Oracle Enterprise Manager.
If you select a Release 2 (9.0.4) instance, or if the installer automatically switches the active Oracle Enterprise Manager to a remaining instance that happens to be a Release 2 (9.0.4) instance, the installer overwrites files in the Release 2 (9.0.4) Oracle home with files from the 9.0.2 or 9.0.3 home. This causes Oracle Enterprise Manager to stop working.
The patch prevents the installer from automatically switching the active Oracle Enterprise Manager to a Release 2 (9.0.4) instance in the case where the only remaining instances are Release 2 (9.0.4) instances. It also prevents the installer from displaying Release 2 (9.0.4) instances in the list where you select the instance to contain the active Oracle Enterprise Manager.
If a Release 2 (9.0.4) instance becomes the active Oracle Enterprise Manager, Oracle Enterprise Manager will stop working.
To fix this, perform these steps in the Release 2 (9.0.4) Oracle home:
Shut down the Oracle Enterprise Manager Application Server Control.
prompt> emctl stop iasconsole
Rename the following files. Do not delete the files, because you might need them in step 5. You can rename them with an "active" suffix (for example, iasadmin.properties.active):
ORACLE_HOME/sysman/config/iasadmin.properties
ORACLE_HOME/sysman/emd/targets.xml
ORACLE_HOME/sysman/j2ee/config/jazn-data.xml
ORACLE_HOME/sysman/webapps/emd/WEB-INF/config/consoleConfig.xml
Copy the backup files for the files listed in the preceding step.
The backup files are in the same directory as the listed files. The names of the backup files are suffixed with a digit (for example, iasadmin.properties.1). Check the timestamp, or check the content, of the backup files to determine the most recent backup file.
Start the Oracle Enterprise Manager Application Server Control.
prompt> emctl start iasconsole
If you have remaining 9.0.2/9.0.3 instances on the computer, you need to designate one of them to contain the active Oracle Enterprise Manager.
Copy the files listed in step 2 (which you renamed with the active suffix) to the 9.0.2/9.0.3 instance's Oracle home. Rename them back to the original names (that is, remove the active suffix).
Edit /var/opt/oracle/emtab to set the DEFAULT property to refer to the new active Oracle Enterprise Manager.
This section covers the following reinstallation issue:
Oracle9iAS Release 2 (9.0.3) does not support reinstallation. After you successfully installed Oracle9iAS Release 2 (9.0.3) J2EE and Webcache, if you try to install the same product into the same home directory, the OC4J configuration tool fails. This is because the OC4J configuration tool does not handle the reinstallation appropriately.
This section covers the following migration issue.
After migrating from Oracle9iAS 1.0.2.2.2 or 9.0.2x to 9.0.3, the symbolic links used in httpd.conf or any other configuration files are not being migrated. This is because that the Oracle HTTP Server plug-in does not migrate the symbolic links to the corresponding Oracle Home directory.
Therefore, after migration, you must check the directives in the configuration files for symbolic links and point these symbolic links to the correct location.
This section covers the following known documentation issues for the Oracle9i Application Server Migrating to Oracle9iAS Release 2 (9.0.3) guide:
Section 3.8.1, "Oracle9i Application Server Migrating to Oracle9iAS Release 2 (9.0.3)"
Section 3.8.2, "Oracle9iAS Containers for J2EE User's Guide"
Section 3.8.3, "Documentation Errata for Installation Guide"
This section covers the following known documentation issues for the Oracle9i Application Server Migrating to Oracle9iAS Release 2 (9.0.3) guide:
This section describes incorrect chapter headings for the following chapters:
In Chapter 3 "Migrating Oracle9iAS Containers for J2EE (OC4J)" the headings shown on the chapter title page are:
OC4J Migration Candidates
The OC4J Configuration File Migration Process
Backup and Auditing Measures for OC4J Migration
It should read as follows:
OC4J Migration Candidates
OC4J Elements Not Migrated
The OC4J Configuration File Migration Process
Backup and Auditing Measures for OC4J Migration
In Chapter 4 "Migrating Oracle9iAS Web Cache" the headings shown on the chapter title page are:
Web Cache Migration Candidates for Migration from Release 1 (1.0.2.2.x)
The Web Cache Migration Process: Migrating from Release 1 (1.0.2.2.x)
The Web Cache Migration Process: Migrating from Release 2 (9.0.2)
The Web Cache Migration Process: Migrating from Release 2 (9.0.2)
The Web Cache Migration Process: Migrating from Release 1 (1.0.2.2.x)
Backup and Auditing Measures for Web Cache Migration
Completing the Web Cache Migration
It should read as follows:
Web Cache Migration Candidates for Migration from Release 1(1.0.2.2.x)
Web Cache Migration Candidates for Migration from Release 2 (9.0.2)
Web Cache Elements Not Migrated
The Web Cache Migration Process: Migrating from Release 2 (9.0.2)
The Web Cache Migration Process: Migrating from Release 1 (1.0.2.2.x)
Backup and Auditing Measures for Web Cache Migration
Completing the Web Cache Migration
In the table located in Chapter 4 "Migrating Oracle9iAS Web Cache" the table element for Site-to-server mappings shows:
Virtual Host, Listen
It should read as follows:
VirtualHost, Listen
Step 7 in Chapter 5, "Using the Oracle9iAS Migration Assistant" that starts as follows:
"Press Enter to accept the default password welcome, or type the password and press Enter."
is invalid
The text in the Architecture section of Chapter 9, "Oracle9iAS Clustering" in the Oracle9iAS Containers for J2EE User's Guide incorrectly refers to DCM as Dynamic Configuration Management. DCM refers to Distributed Configuration Management.
This section covers the following known documentation issues for the Oracle9i Application Server Installation Guide:
Table 2-7 incorrectly refers to Oracle9iAS Release 3 (9.0.3). The reference should read Oracle9iAS Release 2 (9.0.3).
Step 10 of Section 3.1 refers to the JDKHOME directory. The references should read JDK_HOME.
The Caution note in Section 5.1.2 refers to registry entries. This note can be safely ignored.
Step 8 of Section 5.1.2 requests you to reboot the system. This step can be safely ignored.
Table A-1 contains a duplicate entry for Oracle HTTP Server- SSL. Ignore the duplicate row of the table.
