Oracle9i Application Server Release Notes Release 2 (9.0.2) for AIX-Based Systems, Compaq Tru64 UNIX, HP 9000 Series HP-UX, and Linux Intel Part Number A96168-01 |
|
This chapter describes installation and migration issues and their workarounds. Topics include:
This section covers these installation issues:
If you are installing more than one Oracle9i Application Server instance on a single computer, then you must perform all of the installations as the same operating system user.
When installing, avoid selecting an ORACLE_HOME
directory that is a symbolic link to another directory. If you do this, the following errors may occur when running the configuration tools:
java.lang.SecurityException: access denied
oracle.ias.repository.schema.SchemaException: access denied
As a workaround, install into a directory that is not a symbolic link.
Oracle9iAS supports multiple infrastructure installations and multiple metadata repositories. You must install the additional infrastructure instances before installing any Oracle9iAS mid-tier installation types. The installer prompts you to select a metadata repository only if it detects more than one repository.
When installing Oracle9iAS against an existing Oracle9iAS Infrastructure, ensure that the following infrastructure components are running:
If you are installing an Oracle9iAS Infrastructure component, then ensure that its dependencies are running before starting the installation process. For example, before installing Oracle9iAS Single Sign-On, start Oracle9iAS Metadata Repository, Oracle Internet Directory, and Oracle HTTP Server.
If Oracle HTTP Server is not running on the Infrastructure, then you might get the following error message when you try to use the Infrastructure during installation:
An error occured while attempting to verify your host and port. Please verify your host and port values and that you can connect to this host, or enter new values. User Output Stringlist is: <infra_host>:<port>. Return value from SSORunning function is INVALID.
If your computer does not have enough space in the Oracle home directory to create the database files required by the Oracle9iAS Metadata Repository, then you will be prompted to select another location to install them.
If you are using Oracle9iAS Metadata Repository, edit the init.ora
file to remove the following entry:
_optim_peek_user_binds=FALSE
Multiple Oracle9iAS Portal & Wireless installations pointing to a single Portal instance in the metadata repository would override the existing entries. Entries related to Web Cache would get overwritten in the Portal instance each time you run the mid-tier installation.
As a workaround, disable Web Cache for Portal in all the Oracle9iAS instances with the following procedure:
Note that each time you install the mid-tier, you drop and recreate the Portal users from Oracle Internet Directory. The password for the Portal lightweight user is the mid-tier instance name from the most recent installation.
During the installation process, when the component configuration screen appears, if you select to install Wireless, ensure that Portal is also selected. The configuration tool for Wireless requires Portal to work.
If the Oracle9iAS Infrastructure Configuration Assistant fails to register Oracle9iAS Single Sign-On Server /mod_osso
during installation, Oracle HTTP Server will not start. There are two options to correct this problem.
ORACLE_HOME
/Apache/Apache/conf/httpd.conf
. Add a #
character in front of the line to comment out the line.
# include ORACLE_HOME/Apache/Apache/conf/httpd.conf/mod_osso.conf
Note that you should use Oracle Enterprise Manager to edit the file.
SSOregistrar
tool to generate a valid osso.conf
file.
If SSOregistrar
returns a non-zero status or throws an exception indicating some errors occurred, then you should not use mod_osso
. To disable mod_osso
, comment the line that includes mod_osso
by adding a #
character in front of the line, as shown in the first option.
When the Oracle9iAS installer initially registers mod_osso
with the Oracle9iAS Single Sign-On Server, it passes the registration URLs containing the port number of the Oracle HTTP Server, instead of the port number of Web Cache. Because the installer passes the incorrect port number, it bypasses Web Cache.
For mod_osso
to work correctly, manually re-register mod_osso
using URLs that have the Web Cache port.
For detailed information on how changes in hostname and port affect Oracle9iAS, and, specifically, how mod_osso
and Oracle9iAS Single Sign-On Server may be affected, see Chapter 7, "Component Configuration Dependencies" in Oracle9i Application Server Administrator's Guide.
During installation, if the Reports Configuration Assistant fails and give the following message:
Process destroyed exception (in the installer configuration palette)
then perform the following steps:
ORACLE_HOME/portal/admin/plsql/wwd/rwaddpag.sql
This creates the Reports portlet.
Alternatively, you can create a tnsnames
entry and execute the script as Portal user with the Portal user password obtained from the Oracle Internet Directory, as described in Step 1.
This section covers the following post-installation issues:
The Installation Guide states that Oracle9i Application Server patches must applied to the metadata repository as a mandatory postinstallation task. These patches are available on the Patch CD-ROM in the Oracle9i Application Server CD Pack.
The installation sets the DISPLAY
variable in opmn.xml
to localhost:0
by default. If your machine is not equipped with a graphics card, you need to set the variable in opmn.xml
to point to a virtual frame buffer such as X Virtual Frame Buffer (XVFB) or Virtual Network Computing (VNC). Refer to Chapter 3 of the Oracle9i Application Server Installation Guide for instructions.
There are no known issues associated with deinstallation.
There are no known issues associated with reinstallation.
There are no known issues associated with migration.
|
Copyright © 2002 Oracle Corporation. All Rights Reserved. |
|