Skip Headers

Oracle9i Application Server Release Notes
Release 2 (9.0.2) for Windows NT/2000

Part Number A90334-03
Go To Documentation Library
Home
Go To Table Of Contents
Contents

Go to previous page Go to next page

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 Oracle9iAS on Machine With Static IP Address

Make sure you install Oracle9iAS on a machine that has a static IP address.

2.1.2 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.3 MS-DOS Windows Appear During Installation

During the installation process, when the various configuration tools are running, some MS-DOS windows appear. There is no information displayed on the windows regarding why they appear.

These windows appear due to a JDK 1.3 related issue. Do not kill these windows as they will disappear automatically once the configuration tool completes its actions.

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

  1. From your browser, point to Oracle Enterprise Manager at http://<host>:1810.

  2. Log in to Enterprise Manager as ias_admin/<password supplied at install time>.

  3. Select your middle tier instance.

  4. Select OC4J_Wireless. The OC4J_Wireless screen appears.

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

  6. Use the Java Options field to set the heap size.

  7. Remove the option -noclassgc.

  8. 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 issue:

2.2.1 Information About Starting The Directory Integration Server on Windows NT

Only the owner of the OracleDirectoryService, which runs with the name "OracleDirectoryService_%SID%" in any Oracle installation, can start the Directory Integration Server. By default, on Windows NT, all the services run with the credentials of a user named SYSTEM, which is internal for NT. So, the owner of the OracleDirectoryService needs to be reset to the administrator/loginid authorized to run Oracle Directory and related services. To do this, perform the following steps:

  1. Configure a user with login service privileges. To achieve this, do the following:

    1. Click on Start > Settings > Control Panel > Services.

    2. When you double click on OracleDirectoryService_%SID%, a service windows appears.

    3. In the "Logon as" section, select "this account".

    4. Specify the login ID and password. Click OK.

    5. Stop and start the service.

  2. Register the Directory Integration Server by running odisrvreg.

  3. Start the Directory Integration Server using oidctl.

2.3 Deinstallation Issues

This section covers the following deinstallation issue:

2.3.1 Information about Deinstalling OracleProcessManager Service

If you install Oracle9iAS with Oracle9iDS, and then deinstall Oracle9iAS, OracleProcessManager service will not be deinstalled. This service can only be deinstalled with Oracle9iDS. However, it is safe to remove this service manually without deinstalling Oracle9iDS.

2.4 Reinstallation Issues

There are no known issues associated with reinstallation.

2.5 Migration Issues

This section covers the following migration issue:

2.5.1 osslconvert Tool Might Fail During Certificate Migration

The osslconvert tool may fail during certificate migration. During the failure, a popup window appears with the following message:

application osslconvert.exe: 
The instruction at "xxxxxxxx" referenced memory at "xxxxxxxx". The memory could 
not be written.

You should ignore this failure and continue with the migration process. If this failure persists, then edit the ComSpec environment variable to add more environment space. This is done by adding /e:<size> to the end of the ComSpec value. The maximum size is 32768 bytes.


Go to previous page Go to next page
Oracle
Copyright © 2002 Oracle Corporation.

All Rights Reserved.
Go To Documentation Library
Home
Go To Table Of Contents
Contents