Skip Headers

Oracle9i Application Server Release Notes
Release 2 (9.0.3) for Solaris Operating System (SPARC)
Part No. B10015-08
  Go To Documentation Library
Core
Go To Product List
Platform
Go To Table Of Contents
Contents

Previous Next  

3 Installation and Migration

This chapter describes installation and migration issues and their workarounds associated with Oracle9iAS. It covers the following topics:

3.1 Preinstallation Issues

There are no known preinstallation issues.

3.2 Installation Issues

This section describes the following installation issues:

3.2.1 Installing Non-English Language Files

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

3.2.2 Installer Reports Insufficient Swap Space

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.

3.3 Postinstallation Issues

This section covers the following postinstallation issue:

3.3.1 Configure JServ after Installation

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

3.4 Deinstallation Issues

This section covers the following deinstallation issue:

3.4.1 Switching the Active Oracle Enterprise Manager before Deinstallation

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:

  1. Determine which Oracle9iAS instance contains the active Oracle Enterprise Manager.

    Check the ACTIVE_EMD_HOME entry in the /var/opt/oracle/emtab file.

  2. 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.

  3. Deinstall the instance.

3.5 Reinstalltion Issues

This section covers the following reinstallation issue:

3.5.1 Reinstallation not Supported

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.

3.6 Migration Issues

This section covers the following migration issue.

3.6.1 Symbolic Links not Migrated

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.

3.7 Documentation Errata

This section covers the following known documentation issues for the Oracle9i Application Server Migrating to Oracle9iAS Release 2 (9.0.3) guide:

3.7.1 Oracle9i Application Server Migrating to Oracle9iAS Release 2 (9.0.3)

This section covers the following known documentation issues for the Oracle9i Application Server Migrating to Oracle9iAS Release 2 (9.0.3) guide:

3.7.1.1 Incorrect Chapter Headings

This section describes incorrect chapter headings for the following chapters:

3.7.1.1.1 Chapter 3

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

3.7.1.1.2 Chapter 4

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

3.7.1.2 Incorrect Listing in Table

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

3.7.1.3 Delete Step

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

3.7.1.4 Incorrect Step Information

Step 15 in Chapter 6, "Migrating Distributed Configurations" which reads:

15. If you performed step 13

Should read as:

15. If you performed step 14

3.7.2 Oracle9iAS Containers for J2EE User's Guide

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.