Copyright © 2001 Oracle Corporation. All Rights Reserved. |
|
| Oracle9i
Application Server Release Notes Addendum
Release 1 v(1.0.2.2) for AIX-Based Systems, Compaq Tru64 UNIX, HP 9000 Series HP-UX, Linux Intel, and Sun Solaris Intel Part Number A90463-03 |
|
Oracle is a registered trademark of Oracle Corporation.
Other names may be trademarks of their respective owners.
Copyright © 2001, Oracle Corporation.
Release
1 v(1.0.2.2)for AIX-Based
Systems, Compaq Tru64 UNIX, HP 9000 Series HP-UX, Linux Intel, and Sun
Solaris Intel
Use this addendum in conjunction with the Oracle9i
Application Server Release 1 v(1.0.2.2) Release Notes.
Oracle will periodically update this addendum as new information becomes available. The latest version can be found at the following website:
http://docs.oracle.com
The Oracle9i Application Server Release 1 v(1.0.2.2) Installation
Guide describes the process for installing Oracle9i Application
Server. This section provides additional information to help you successfully
complete the installation.
The Oracle9iAS Wireless Personalization Portal URL
on page F-8 is incorrect. To test if the Personalization Portal is working
properly, access the following URL:
http://<ias_host_name>.<domain>:<listener_port>/portal/Login.jsp
Ignore the section "Oracle9iAS Wireless Configuration
Parameters for Linux Intel" in Appendix F of the Oracle9i Application
Server Release 1 v(1.0.2.2) Installation Guide. Use the postinstallation
configuration instructions in the "Oracle9iASWireless Configuration
Parameters for AIX, HP, Tru64 and Solaris Intel" section to configure Oracle9iAS
Wireless on Linux Intel.
Instructions on page F-4 and page F-7 include configuring the jserv.conf file by adding the Oracle9iAS Wireless specific mount point. The following example ApJServGroupMount section was not included in the Oracle9i Application Server Release 1 v(1.0.2.2) Installation Guide:
# PTG Start ApJServGroupMount /ptg balance://group1/root # PTG End
The correct memory requirement listed in the Oracle9i
Application Server Release 1 v(1.0.2.2) Installation Guide should be
640 MB.
The following table lists the disk space requirements for
the corresponding UNIX platforms:
| Platform | Disk Space Requirement |
|---|---|
|
AIX |
6.5 GB |
|
HP |
6.0 GB |
|
Linux |
6.0 GB |
|
Tru64 |
6.5 GB |
|
Note: For the GNU LibC patch, go to: ftp://ftp.suse.com/pub/suse/i386/supplementary/commercia l/Oracle/glibc-7.2-jdk1.3.1/ |
http://www.blackdown.org
http://java.sun.com
In Appendix B, step 2 of the "Generate the Certificate Request" section, replace:
$ORACLE_HOME/Apache/open_ssl/bin
with:
$ORACLE_HOME/Apache/open_ssl/bin/openssl
There are three such occurrences.
The following sections correct and update the information
in the Oracle9i Application Server Release 1 v(1.0.2.2) Release Notes.
Section 1.5.5.1.19 in the Oracle9i Application Server
Release 1 v(1.0.2.2) Release Notes recommends using tcpatch
to fix damaged XML style sheets in large files.
Download this patch from the following website:
http://metalink.oracle.com
Section 1.6.1.2 in the Oracle9i Application Server Release
1 v(1.0.2.2) Release Notes has redundant information. Ignore the second/last
paragraph in this section.
In the Oracle9i Application Server Release 1 v(1.0.2.2)
Release Notes, the last subsection of note 1.5.1.23 "Response File
Variable Settings for Oracle9iAS Portal Silent Install" is obsolete.
The following sections describe pre-installation steps for
Oracle9i Application Server Enterprise Edition Installation on Linux
Intel.
Before starting the Oracle9i Application Server Enterprise Edition installation, create the following symbolic link if it does not already exist.
cd /usr/X11R6/lib ln -s libXm.so.2.1 libXm.so
Before starting the Oracle9i Application Server Enterprise
Edition installation, ensure that the /etc/oratab file exists.
The user must have write permission to the /etc/oratab file. When
the installation is 88% complete, Oracle Universal Installer will open
two xterm windows.
The first window will install the 80601 component. If the
/etc/oratab file does not exist or is not writable, then the oratab
dialog box will appear in the xterm window. Select OK in the oratab dialog
box to continue installing the 80601 component.
When the 80601 has finished installing, the second xterm
window will open. This window is for the installation of the 80630 component.
Select OK in the oratab dialog box. If the /etc/oratab file exists
and is writable, the two xterm windows will show the progress of the installations
and the oratab dialog box will not prompt the user for information.
|
Note: The character-based orainst utility is used to install the 80601 and 80630 components. This is because motif-based orainst utility is not available on Linux Intel. |
Ensure that the soft limit for the system parameter number
of open file descriptor for each user process (output of ulimit -n)
is set to a minimum of 8192. If this value is less than 8192, it might
affect the Discoverer configuration during installation. However, this
value might have to be increased depending on the system load.
If you are installing the Developer 6i component as part of Oracle9iAS Release 1 v(1.0.2.2), you must verify that the following symbolic links for system shared libraries are present:
/usr/lib/libXt.sl /usr/lib/libXt.3 /usr/lib/libX11.sl -> /usr/lib/libX11.3 /usr/lib/Motif2.1/libXm.sl -> /usr/lib/Motif2.1/libXm.4
If the shared library symbolic links are not present, you need to create them by using the root account and the following commands:
$ su root $ cd /usr/lib $ ln -s /usr/lib/libXt.3 libXt.sl $ ln -s /usr/lib/libX11.3 libX11.sl $ cd /usr/lib/Motif2.1 $ ln -s /usr/lib/Motif2.1/libXm.4 libXm.sl
If these shared library links are not present, you will get the following error while relinking Developer 6i products:
/usr/ccs/bin/ld: Can't find library for -lXm
If you notice this link problem after installation, create
the shared library softlinks. See the HP-UX
Developer 6i Troubleshooting section for how to relink the Developer
6i product after installation.
If you are installing the Developer 6i component as part of Oracle9iAS Release 1 v(1.0.2.2), you must verify that the following symbolic links for system shared libraries are present:
/usr/lib/libXt.sl /usr/lib/libXt.3 /usr/lib/libX11.sl -> /usr/lib/libX11.3 /usr/lib/Motif2.1/libXm.sl -> /usr/lib/Motif2.1/libXm.4
If the shared library symbolic links are not present, you need to create them by using the root account and the following commands:
$ su root $ cd /usr/lib $ ln -s /usr/lib/libXt.3 libXt.sl $ ln -s /usr/lib/libX11.3 libX11.sl $ cd /usr/lib/Motif2.1 $ ln -s /usr/lib/Motif2.1/libXm.4 libXm.sl
If these shared library links are not present, you will get the following error while relinking Developer 6i products:
/usr/ccs/bin/ld: Can't find library for -lXm
If you notice this link problem after installation, create
the shared library softlinks. See the HP-UX Developer
6i Troubleshooting section for how to relink the Developer 6i
product after installation.
Before using Oracle9i Application Server, read through
each item in this section to understand the restrictions and limitations
in this release. These known restrictions and limitations might require
additional steps.
After installation, publish the jsp demos using the following commands:
cd $ORACLE_HOME/jsp/demo unzip demo.zip make
iFS requires that you install Sun Microsystem JDK 1.3.1 for Linux on the system. For more information on installing JDK 1.3.1, go to the following URL:
http://java.sun.com/j2se/1.3/install-linux-sdk.html
When running ifsconfig, the system will prompt you
from the command line for the JDK 1.3.1 location. Enter the JDK1.3.1 install
location on the system to continue with ifsconfig.
For AIX, HP-UX, and Compaq Tru64, to access the Oracle Internet File System web interface through Oracle HTTP Server powered by Apache, after running ifsapachesetup, add the following line to the end of $ORACLE_HOME/Apache/Jserv/etc/jserv.conf and restart the Oracle HTTP Server:
ApJServGroupMount /ifs balance://group1/root
You should be able to access iFS web interface from:
http://<hostname>:<port number>/ifs/files
There are port conflicts between the mod_oprocmgr and the
Oracle Internet File System. The jserv.properties file, by default,
has JServ listening on port 8007 only. Oracle Internet File System uses
the jserv.properties file as part of setting up the Group Mount
(ApJServGroupMount). This creates a conflict with mod_oprocmgr, which is
also using port 8007.
To solve port conflicts, perform the following steps:
|
Note: The automated Oracle9i File System servlet configuration does not cater to the revised configuration mechanism in the High Availability feature. |
Perform the following post-configuration steps in addition to the steps mentioned in the Oracle Internet File System Release Notes:
$ ORACLE_HOME/Apache/Apache/bin/apachectl stop
$ ORACLE_HOME/Apache/Jserv/etc
$ ORACLE_HOME/Apache/Apache/bin/apachectl start
The following table describes the new features in Oracle9i
Application Server InterConnect, Version 4.1.
In Enterprise Edition installations that were migrated from
Release 1 (v.1.0.2.0) to (v.1.0.2.1), then to (v.1.0.2.2), the Oracle9i
Application Server Database Cache configuration tool, though not selected,
appears at the end of the installation, when no migration is required to
v.1.0.2.2.
Select Cancel to exit the configuration tool.
The following section contain issues on Forms and Reports.
For Forms and Reports, the latest version of jinitiator does
not get copied correctly during the Oracle9i Application Server
Migration installation process.
To copy the correct version of jinitiator, perform the following steps:
$ cd $ORACLE_HOME/6iserver/jinit/doc
$ chmod 755 jinit.exe
$ cp -p jinit-domestic.exe jinit.exe
The following sections contain Forms and Reports issues on
Linux Intel.
The Java Importer feature is available in Oracle9i Application Server Forms. It requires JDK 1.3.1. To enable this feature, perform the following steps:
<java_inst_dir>/jre/lib/i386: <java_inst_dir>/jre/lib/i386/hotspot: <java_inst_ dir>/jre/lib/i386/native_threads:$LD_LIBRARY_PATH
|
Note: The java_inst_dir variable defines the location where you installed JDK and JRE 1.3.1. |
The following error might occur when running the motif-based Forms/Reports executable:
Error while loading shared libraries: libXm.so.2.1: cannot open shared object file: No such file or directory
To solve this problem, add /usr/X11R6/lib into the LD_LIBRARY_PATH variable, using the following command:
export LD_LIBRARY_PATH=/usr/X11R6/lib:$LD_LIBRARY_PATH
Oracle Wallet Manager, shipped as part of Forms/Reports 6i,
does not work in Oracle9i Application Server Release 1 v(1.0.2.2)
for Linux Intel.
During the Oracle9i Application Server Enterprise Edition installation of the 80630 patch component, there is an intermittent bug that produces the following error:
This is a patch release to be installed with version 8.0.6.0.0 of RDBMS. You must install this patch in an ORACLE_HOME where version 8.0.6.0.0 is installed.
When this occurs, click OK from the dialog box so that the
installation will continue. The 80630 patch component will not be successfully
installed.
To install the 80630 patch component manually after the Oracle
Universal Installer installation is complete, refer to the instructions
provided in bug 1822270.
The following sections contain issues on Discoverer.
JServ fails when you use JDK1.1.8.04 on HP-UX and when you
use JDK 1.1.8 on AIX and Linux. This failure is due to the Visibroker wrapper.bin
parameter entry in the jserv.properties file.
Change the jserv.properties file from:
wrapper.bin.parameters=-mx256M -Dorg.omg.CORBA.ORBClass=com.visigenic.vbroker.orb.ORB -Dorg.omg.CORBA.ORBSingletonClass=com.visigenic.vbroker.orb.ORB
to:
wrapper.bin.parameters=-mx256M wrapper.bin.parameters=-Dorg.omg.CORBA.ORBClass=com.visigenic.vbroker \ .orb.ORB wrapper.bin.parameters=-Dorg.omg.CORBA.ORBSingletonClass=com.visigenic \ .vbroker.orb.ORB
Oracle9iAS Discover Server is currently not available
on Compaq Tru64 UNIX and Sun Solaris Intel. However, the Oracle HTTP Server
components of Oracle9iAS Discoverer Viewer and Oracle9iAS
Discoverer Plus (User Edition) are available for these platforms.
To install the Oracle HTTP Server components of Oracle9iAS
Discoverer Viewer and Oracle9iAS Discoverer Plus on Compaq Tru64
UNIX and Sun Solaris Intel, you must install at least the HTTP component
installation of Oracle9i Application Server on the host machines.
In addition, you must install Oracle9iAS Discoverer Server on NT.
The Oracle HTTP Server components for Oracle9iAS Discoverer
Viewer and Oracle9iAS Discoverer Plus are available as a patch.
To obtain the patch for Oracle9iAS Discoverer Viewer/User support
on Compaq Tru64 UNIX and Sun Solaris Intel, contact Oracle Support Services.
Instructions for installing the patch is in the README.TXT, provided
with the patch.
The following sections contain Oracle9iAS Portal issues.
While navigating within the Oracle9iAS Portal, the following intermittent error message might display:
Portlet could not be contacted
The patch for bug1811874 is mandatory for all the platforms.
Follow the installation instructions in the patch.
To run Oracle9iAS Portal in SSL with the IE browser:
#SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown
To enable JNI caching on AIX, insert following line in the <oracle-home>/Apache/Jserv/etc/jserv.properties file:
wrapper.bin.parameters=-Djava.library.path=<oracle-home>/lib
When installed, JNI Cache does not get enabled for Oracle9iAS Portal on HP-UX. To enable JNI Caching, perform the following steps:
<iAS Install Home>/lib/libwwjcache.sl
wrapper.env=SHLIB_PATH=<iAS Home>/lib wrapper.bin.parameters=-classic
The Oracle9iAS Portal online help does not get installed during the Oracle9i Application Server installation process. To install Oracle9iAS Portal online help, perform the following steps:
runimp.csh ../../bin/imp <portal_schema>/<portal_password> <database_hostname> <database_port> <database_sid> PORTAL_HELP <portal_schema> ../../portal30/doc/site/hlp30ca.dmp hlp30ca.dmp.log
$ cd $ORACLE_HOME/portal30/admin/plsql/wwu
@utlsbmrg.sql reuse database_user 0
When you install Oracle9iAS Portal, the configuration
assistant might report that the shared pool size or java pool size is insufficient.
This is because the assistant expects the pool size value to be in bytes.
To fix this problem, perform the following steps:
For example, if
SHARED_POOL_SIZE=100M
change it to:
SHARED_POOL_SIZE=100000000
Listener failures have been observed in multiple installs of Oracle9i Application Server Release 1 (v.1.0.2.2) on the same machine. The listener fails due to port conflicts (the port numbers are not getting bumped). The first installation functions correctly, but all subsequent installs fail. The error log contains messages similar to the following:
$ORACLE_HOME/Apache/Apache/logs/error_log ApacheJServ/1.1.2: Failed to bind to port(s) specified in /private/oracle/lizWorkarea/ias1022M6.2/Apache/Jserv/etc/jserv.propertie s. Please check /private/oracle/lizWorkarea/ias1022M6.2/Apache/Jserv/etc/jserv.propertie s and jserv.conf file, and make sure number of JServ process specified in jserv.conf is less than number of ports specified in /private/oracle/lizWorkarea/ias1022M6.2/Apache/Jserv/etc/jserv.propertie s.and the ports are not used by other processes. [Thu May 17 18:57:26 2001] [warn] OPM: EW process pdsun-qa17:0 (pid:14739) died, restarting. [Thu May 17 18:57:26 2001] [warn] OPM: ADM: process 14708 created server process 14747 (group group1, module JServ), and inserted in proctable as entry 0 $ORACLE_HOME/Apache/Jserv/logs/jserv.log ApacheJServ/1.1.2: Failed to bind to port(s) specified in /private/oracle/lizWorkarea/ias1022M6. 2/Apache/Jserv/etc/jserv.properties. Please check /private/oracle/lizWorkarea/ias1022M6.2/Apache/Jserv/etc/jserv.propertie s and jserv.conf file, and make sure number of JServ process specified in jserv.conf is less than number of ports specified in /private/oracl e/lizWorkarea/ias1022M6.2/Apache/Jserv/etc/jserv.properties. and the ports are not used by other processes.
To resolve this issue, edit the configuration files to (bump)
the port numbers.
The Oracle9i Application Server v1.0.2.2 Installation
Guide and Release Notes reference the use of JDK 1.1.8 and a special Portal
configuration on Linux (using a separate instance of the HTTP Server and
JDK 1.2.2).
Since the release of these documents, Oracle has certified
Oracle9iAS v1.0.2.2 with JDK 1.3.1 on SuSe Linux 7.1. Use of JDK
1.3.1 eliminates the need for a special Portal configuration. However,
the SuSe operating system must be patched to a glibc level of 2.2.2-53
and a kernel level of 2.4.4.
To change from JDK 1.1.8 to JDK 1.2.2, perform the following
steps, for the corresponding files:
The following documents (PDF files) are inaccessible from
the HP-UX documentation index. These documents are available on the CD-ROM.
| Document Name | Location |
|---|---|
|
Oracle9i Application Server Email Installation Guide |
/doc/A87551.pdf |
|
Oracle9i Application Server Unified Messaging Installation Guide |
/doc/A88738.pdf |
The Apache JServ log or the browser may report an "Out Of
Memory" condition. This condition is a result of insufficient JVM memory.
The JVM runs out of memory when the data handled by the JVM exceeds its
memory allocation pool.
To increase the maximum size of the memory allocation pool for a JVM, perform the following steps:
wrapper.bin.parameters=-mx<size>m [for jdk1.1.8] wrapper.bin.parameters=-Xmx<size>m [for jdk1.2.2 or jdk1.3.1 on Linux Intel]
where <size> quantifies the memory allocation
pool. The unit of measurement is megabyte.
The default value is 1 megabyte of memory. Oracle recommends
the use of 128 megabytes of memory.
For example, to set the value to 128 megabytes, add the following line:
wrapper.bin.parameters=-mx128m [for jdk1.1.8] wrapper.bin.parameters=-Xmx128m [for jdk1.2.2 or jdk1.3.1 on Linux Intel]
Include the following line in the <ORACLE_HOME/Apache/Jserv/etc/jserv.properties file:
wrapper.env=THREADS_FLAG=native
Oracle9iAS Web Cache cannot start in an Oracle Home
directory that begins with /ora. Do not use /ora at the
beginning of the Oracle Home directory.
To run JServ with JDK 1.3.1, add the following parameters:
wrapper.bin.parameters=-classic wrapper.bin.parameters=-Xms64m wrapper.bin.parameters=-Xmx128m
to the following files:
$ORACLE_HOME/Apache/Jserv/etc/jserv.properties $ORACLE_HOME/Apache/Jserv/etc/jservSoap.properties
|
Note: Only JDBC thin drivers are supported with the preceding configuration. |
When installing Oracle9i Application Server Enterprise
Edition, the Oracle9iAS Web Cache Configuration Assistant might
hang if there is an instance of Oracle9iAS Web Cache already running
on default ports. Bring down existingOracle9iAS Web Cache processes
before running a new installation.
If the Oracle9iAS Web Cache Configuration Assistant
hangs during installation, the workaround is to shut down the Oracle9iAS
Web Cache processes that are currently running. The Oracle9iAS Web
Cache Configuration Assistant will start as soon as old processes are shutdown.
Install Oracle9i Application Server Release 1 v(1.0.2.2)
with user's primary UNIX group to avoid causing Oracle9iAS Web Cache
Configuration Assistant to hang.
If Oracle9iAS Web Cache Configuration Assistant hangs, use the following steps to resolve the hanging issue:
$ORACLE_HOME/webcache/bin/webcachectl stop
Due to bug 1843175, Oracle9iAS Wireless does not support
OCI connections to the repository on Linux Intel. By default, Oracle9iAS
Wireless uses JDBC thin connections to the repository.
You must set JREHOME before starting the configuration tool
(imconfig) and the administration tools (imadm and imadml).
Set the JREHOME environment variable to the Blackdown JRE
1.1.8 location. The configuration tool and the administration tools are
certified with Blackdown JRE 1.1.8 only.
If there is a problem during the link phase of Developer (for example, where the Motif symbolic links are not present on the system), you need to do a post-installation relink of the Developer 6i Product. Do this by using the Developer 6i relink6i.sh script located under:
$ORACLE_HOME/6iserver/bin/relink6i.sh
To use the script for relinking, run the following command:
% cd $ORACLE_HOME/6iserver/bin % ./relink6i.sh
During relinking of Developer 6i, either using the relink6i.sh script or the installer, you might notice the following warning:
(Bundled) cc: warning 480: The +O2 option is available only with the C/ANSI C product; ignored.
You can ignore this warning. The optimization flag '+O2'
is only available when using /opt/ansic/bin/cc. If the ANSI C
compiler is present on your system, this warning can be resolved by changing
the PATH in the relink6i.sh script to use /opt/ansic/bin
instead of /usr/ccs/bin.
On IBM Power2 processors, the Apache startup problem can
be fixed by applying patch #1878400 from http://metalink.oracle.com.
|
Copyright © 2001 Oracle Corporation. All Rights Reserved. |
|