|
Oracle9i Application Server Release Notes
Release 2 (9.0.3) for Microsoft Windows Part No. B10006-09 |
|
|
|
|
Oracle9i Application Server Release Notes
Release 2 (9.0.3) for Microsoft Windows Part No. B10006-09 |
|
|
|
|
This chapter describes installation and migration issues and their workarounds associated with Oracle9iAS. It covers the following topics:
This section describes the following installation issues:
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> drive:\setupNLS.bat
This section covers the following postinstallation issue:
If you update your Java Development Kit (JDK) to Version 1.4, you may experience the following error when you attempt to start or stop the Enterprise Manager Web site. Specifically, the following error may be reported:
"Error: native VM not supported"
To workaround this problem:
Use a text editor to open the following file:
%ORACLE_HOME%\bin\emctl.pl
Locate all occurrences of the following text string within the file:
%JAVA_HOME%\bin\java -native
Remove the -native argument from each of occurrence, so the command appears as follows:
%JAVA_HOME%\bin\java
Save the changes and close the emctl.pl file.
Repeat steps 1 through 4 for the following additional control files:
%ORACLE_HOME%\bin\launchEMD.bat %ORACLE_HOME%\bin\stopEMD.bat
Run the emctl start or emctl stop command again.
Be sure to remove all occurrences of "-native" from these files and save your changes.
This section covers the following deinstallation issues:
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:
Determine which Oracle9iAS instance contains the active Oracle Enterprise Manager.
Click Start > Run, type in regedit.exe, and click OK.
The Registry Editor is displayed.
Navigate to the following key in the Registry: HKEY_LOCAL_MACHINE > SOFTWARE > ORACLE > em_loc. The em_loc appears on the right side of the window.
This key contains the path of the ORACLE_HOME that contains the active Oracle Enterprise Manager.
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.
Deinstall the instance.
If you have 9.0.2 or 9.0.3 and Release 2 (9.0.4) instances on the same computer, and you want to deinstall a 9.0.2 or 9.0.3 instance, perform these steps:
Apply patch 3234681 to your 9.0.2 or 9.0.3 instances. You can download the patch from OracleMetaLink (http://metalink.oracle.com).
Stop all processes associated with the instance you want to deinstall.
Run the installer to deinstall the 9.0.2 or 9.0.3 instance. Make sure you run the installer for the 9.0.2 or 9.0.3 instance.
For 9.0.2 and 9.0.3 instances, the installer is located in the oui/install directory at the same level as the Oracle home directory. For example, if the 9.0.2 or 9.0.3 Oracle home is /opt/oracle/orahome902, then the installer would be /opt/oracle/oui/install/runInstaller.
If you have multiple 9.0.2 and/or 9.0.3 instances on the same computer, these instances share an Oracle Enterprise Manager. This is the "active Oracle Enterprise Manager". When you deinstall the instance that contains the active Oracle Enterprise Manager using the installer, the installer needs to switch the active Oracle Enterprise Manager to one of the remaining instances. If there is only one remaining instance, then the installer automatically makes it the active Oracle Enterprise Manager. If more than one instance remain, the installer prompts you to select the instance to contain the active Oracle Enterprise Manager.
Unlike 9.0.2 or 9.0.3 instances, Oracle9i Application Server Release 2 (9.0.4) instances on the same computer do not share an Oracle Enterprise Manager. Each Release 2 (9.0.4) instance has its own Oracle Enterprise Manager.
Because Release 2 (9.0.4) instances do not share an Oracle Enterprise Manager, you must not select a Release 2 (9.0.4) instance to contain the active Oracle Enterprise Manager. You must select a 9.0.2 or 9.0.3 instance to contain the active Oracle Enterprise Manager.
If you select a Release 2 (9.0.4) instance, or if the installer automatically switches the active Oracle Enterprise Manager to a remaining instance that happens to be a Release 2 (9.0.4) instance, the installer overwrites files in the Release 2 (9.0.4) Oracle home with files from the 9.0.2 or 9.0.3 home. This causes Oracle Enterprise Manager to stop working.
The patch prevents the installer from automatically switching the active Oracle Enterprise Manager to a Release 2 (9.0.4) instance in the case where the only remaining instances are Release 2 (9.0.4) instances. It also prevents the installer from displaying Release 2 (9.0.4) instances in the list where you select the instance to contain the active Oracle Enterprise Manager.
If a Release 2 (9.0.4) instance becomes the active Oracle Enterprise Manager, Oracle Enterprise Manager will stop working.
To fix this, perform these steps in the Release 2 (9.0.4) Oracle home:
Shut down the Oracle Enterprise Manager Application Server Control.
prompt> emctl stop iasconsole
Rename the following files. Do not delete the files, because you might need them in step 5. You can rename them with an "active" suffix (for example, iasadmin.properties.active):
ORACLE_HOME/sysman/config/iasadmin.properties
ORACLE_HOME/sysman/emd/targets.xml
ORACLE_HOME/sysman/j2ee/config/jazn-data.xml
ORACLE_HOME/sysman/webapps/emd/WEB-INF/config/consoleConfig.xml
Copy the backup files for the files listed in the preceding step.
The backup files are in the same directory as the listed files. The names of the backup files are suffixed with a digit (for example, iasadmin.properties.1). Check the timestamp, or check the content, of the backup files to determine the most recent backup file.
Start the Oracle Enterprise Manager Application Server Control.
prompt> emctl start iasconsole
If you have remaining 9.0.2/9.0.3 instances on the computer, you need to designate one of them to contain the active Oracle Enterprise Manager.
Copy the files listed in step 2 (which you renamed with the active suffix) to the 9.0.2/9.0.3 instance's Oracle home. Rename them back to the original names (that is, remove the active suffix).
Edit /var/opt/oracle/emtab to set the DEFAULT property to refer to the new active Oracle Enterprise Manager.
This section covers the following reinstallation issue:
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.
This section covers the following migration issues:
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.
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.
This section covers the following known documentation issues for the Oracle9i Application Server Migrating to Oracle9iAS Release 2 (9.0.3) guide:
Section 3.7.1, "Oracle9i Application Server Migrating to Oracle9iAS Release 2 (9.0.3)"
Section 3.7.2, "Oracle9iAS Containers for J2EE User's Guide"
This section covers the following known documentation issues for the Oracle9i Application Server Migrating to Oracle9iAS Release 2 (9.0.3) guide:
This section describes incorrect chapter headings for the following chapters:
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
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
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
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
