2
Installation and Migration Issues

This chapter describes installation and migration issues and their workarounds. Topics include:

2.1 Installation Issues

This section covers these installation issues:

2.1.1 Install the Latest Operating System Patch Cluster Before Installing Oracle9iAS

Before installing Oracle9i Application Server, you must download and install the latest patch cluster for your operating system version from

http://sunsolve.sun.com

2.1.2 Oracle9iAS Installation and Multiple Operating System Users

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.

2.1.3 Multiple Infrastructure-based Deployment

Oracle9iAS supports multiple infrastructure installations. The first (or primary) infrastructure installation must contain SSO, Oracle Internet Directory, a Metedata Repository, and, optionally, Oracle Management Server. Any subsequent (or secondary) infrastructure installations:

must point to the SSO in the primary installation.
must point to the Oracle Internet Directory in the primary installation.
must contain their own Metadata Repository.
may optionally contain Oracle Management Server.

The purpose of a secondary installation is to provide an additional Metadata Repository in case the load on the primary Metadata Repository is excessive.

You can install a secondary infrastructure by choosing a custom installation and selecting Metadata Repository and optionally Oracle Management Server. You will be prompted for SSO and Oracle Internet Directory information, at which time you should supply the information for the primary infrastructure.

The middle tier application server installations that are installed after a secondary infrastructure can use that secondary infrastructure. This means that you cannot change existing middle tier application server installations to use the secondary infrastructure.

If you want a middle tier installation to use the secondary infrastructure, specify the SSO and Oracle Internet Directory from the primary infrastructure at install time. When you are prompted to specify which infrastructure's Metadata Repository you would like to use, choose the Metadata Repository from the secondary installation.

2.1.4 Start Dependencies When Installing Against Oracle9iAS Infrastructure

When installing Oracle9iAS against an existing Oracle9iAS Infrastructure, ensure that the following infrastructure components are running:

Oracle9iAS Metadata Repository
Oracle Internet Directory
Oracle9iAS Single Sign-On
Oracle HTTP Server
Oracle9iAS Containers for J2EE

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.

2.1.5 Prompt for Database Files Location During Install

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.

2.1.6 Modification in init.ora for Oracle9iAS Metadata Repository

If you are using Oracle9iAS Metadata Repository, edit the init.ora file to remove the following entry:

_optim_peek_user_binds=FALSE

2.1.7 Multiple Install Types into the Same Infrastructure Instance Overwrites Portal

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:

Log on to Portal runtime.
Click Builder to get the Portal design time home page.
Click Administer.
Click Global Settings within the services portlet.
Click cache.
Deselect the Enable Web Cache for caching portal content checkbox.
Click Apply and OK.

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.

2.1.8 Oracle9iAS Wireless Installation Requires Oracle9iAS Portal

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.

2.1.9 Oracle HTTP Server Does Not Start if SSO/mod_osso Registration Failed

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.

If you do not have installed applications that use Oracle9iAS Single Sign-On Server, you can comment out the following line in the file 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.
If you have installed applications that use Oracle9iAS Single Sign-On Server, manually run the 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.

2.1.10 Enabling Oracle9iAS Web Cache and mod_osso

When the Oracle9iAS installer initially registers mod_osso with the Oracle9iAS Single Sign-On, it passes the registration URLs containing the port number of the Oracle HTTP Server, instead of the port number of Oracle9iAS Web Cache. Since the installer passes the incorrect port number, it bypasses Oracle9iAS Web Cache.

For mod_osso to work correctly, manually re-register mod_osso using URLs that have the Oracle9iAS Web Cache port.

See Also:

"Component Configuration Dependencies" chapter in the Oracle9i Application Server Administrator's Guide for detailed information on how changes in hostname and port affect Oracle9i Application Server, and, specifically, how mod_osso and Oracle9iAS Single Sign-On may be affected,

Another alternative workaround is to shutdown Oracle9iAS Web Cache instead of re-registering the SSO partner. Since the entry point is now Oracle HTTP Server instead of Oracle9iAS Web Cache, the error would not show up.

Note:

You can use the above mentioned workaround before re-registering using the Oracle9iAS Web Cache port. Also, when you use this workaround, you have to enter with the Oracle HTTP Server port. For example, if Oracle HTTP Server is running on 7779 and Oracle9iAS Web Cache is running on 7778, then you need to enter the following URL: http://<host.domain>:7779.

On Microsoft Internet Explorer, refresh the page once the changes are made. Otherwise, you might encounter the following error:

Forbidden
You don't have permission to access /osso_login_success on this server.

2.1.11 Report Configuration Assistant Fails During Installation

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:

Log on to Oracle Internet Directory and obtain the Portal user database password.
Log on to the metadata repository as Portal user and run the following script:
```
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.

2.1.12 Service Errors and NoClassDefFound Exceptions

After accessing a large number of different module services or HTTP adapter-based services (with JSP-based content sources hosted on the same Java VM), some of the services fail with a 'service error'. Accessing the target JSPs results in a 'NoClassDefFound' exception. Restarting the server corrects the problem.

When an application is loaded for the first time, the OC4J classloaders read the class bytes in the library jars into memory; it does so even without the classes being instantiated (because the application instantiates classes from an in-memory array).

Class files resulting from compiling JSP files are loaded dynamically. With time, the heap gets filled up and newer classes from compiled JSPs cannot be read into the memory array(s), nor instantiated on the heap. Hence the top-level classloaders fail with a 'NoClassDefFound' exception. In subsequent lookups, the 'OutOfMemoryError' is not thrown since the JDK classloader loadClass( ) implementation semantics prescribe NOT reloading classes that could not deterministically be loaded earlier.

To determine if this is the case, check the number of OutOfMemoryErrors in sys_panama.log. That number should be the same as the number of times the server has been restarted.

If it is the case, increase the heap-size for the VM by modifying the Java option subelement of the OC4J element corresponding to the instanceName OC4J_Wireless.

From your browser, point to Oracle Enterprise Manager at http://<host>:1810.
Log in to Enterprise Manager as ias_admin/<password supplied at install time>.
Select your middle tier instance.
Select OC4J_Wireless. The OC4J_Wireless screen appears.
Select "Server Properties" (located under Instance Properties at the bottom of the OC4J_Wireless page) to invoke the Server Properties page. A page with command-line options appears which includes an editable field for Java Options which you use to set the heap size.
Use the Java Options field to set the heap size.
Remove the option -noclassgc.
Click Apply.

See Also:
"Setting the JVM Heap Size for OC4J Processes" section in the Oracle9i Application Server Performance Guide.

2.2 Postinstallation Issues

This section covers the following postinstallation issues:

DISPLAY Environment Variable is Set to localhost:0

2.2.1 DISPLAY Environment Variable is Set to localhost:0

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.