Oracle9i Application Server Release Notes Release 2 (9.0.2) for Windows NT/2000 Part Number A90334-03 |
|
This chapter describes installation and migration issues and their workarounds. Topics include:
This section covers these installation issues:
Make sure you install Oracle9iAS on a machine that has a static IP address.
If you are using Oracle9iAS Metadata Repository, edit the init.ora
file to remove the following entry:
_optim_peek_user_binds=FALSE
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.
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
.
http://<
host
>:1810.
ias_admin
/<password supplied at install time
>.
OC4J_Wireless
. The OC4J_Wireless
screen appears.
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.
-noclassgc
.
"Setting the JVM Heap Size for OC4J Processes" section in the Oracle9i Application Server Performance Guide.
See Also:
This section covers the following postinstallation issue:
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:
odisrvreg
.
oidctl
.
This section covers the following deinstallation issue:
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.
There are no known issues associated with reinstallation.
This section covers the following migration issue:
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.
|
![]() Copyright © 2002 Oracle Corporation. All Rights Reserved. |
|