Nine precautions for using Oracle9i Database OracleHTTPServer in Oracle Database 9.2.0.1.0 has the following changes: 1. the maximum number of ApacheJserv processes supported by the ApacheJserv process OracleHTTPServer has increased from the default value 25 released by Apache to the maximum value 128. This value cannot be configured in real time. II
Nine precautions for using Oracle9i Database OracleHTTPServer in Oracle Database 9.2.0.1.0 has the following changes: 1. the maximum number of ApacheJserv processes supported by the ApacheJserv process OracleHTTPServer has increased from the default value 25 released by Apache to the maximum value 128. This value cannot be configured in real time. II
Nine precautions for using Oracle9i
The Oracle HTTP Server in Oracle Database 9.2.0.1.0 has the following changes:
I. About the Apache Jserv Process
The maximum number of Apache Jserv processes supported by Oracle HTTP Server has been increased from the default value 25 released by Apache to the maximum value 128. This value cannot be configured in real time.
Ii. JDK/JRE Certification
Oracle is certified to use JDK/JRE 1.3.1 _ 01 and JDK/JRE 1.2.2 _ 07 to establish and configure a Java application with the mod_jserv module.
In version 9.2.0.1.0, all Java class libraries (such as BC4J and XDK), together with JDK 1.1.8 _ 10, are loaded and compiled. These compilation classes are certified to run in versions supported by Java JRE and must not be re-compiled.
Iii. Module mod_plsql requirements
To use the mod_plsql module for a specific backend database, you must manually install the Oracle PL/SQL Web Toolkit (owa pl/SQL packages) on a specific backend database. Owa pl/SQL packages should be installed in SYS database mode to ensure that you only install it once. Note that existing Oracle Application Server (OAS) users must replace the old versions of these packages when migrating to Oracle HTTP Server.
For more information about using PL/SQL gateway in Oracle HTTP Server, see http://hostname.domain: port/pls/admin _/title.htm.
4. Restore the OWA package of the application
When you install the new mod_plsql OWA packages, they are placed in SYS database user mode, which will cause problems for the Application Server (Oracle Application Server) to use the oas pl/SQL cartridge component, if you encounter these problems and want to continue using the PL/SQL cartridge component of OAS, you must recreate some synonyms so that these synonyms can be referenced in the OWA package. Follow these steps to create a synonym for the source database:
1. The SYS account is connected to the database in SQL * Plus.
2. Run the following command in SQL * Plus to delete all OWA public synonyms created in the Oracle HTTP Server installation process.
Drop public synonym OWA_CUSTOM;
Drop public synonym OWA_GLOBAL;
Drop public synonym OWA;
Drop public synonym HTF;
Drop public synonym HTP;
Drop public synonym OWA_COOKIE;
Drop public synonym OWA_IMAGE;
Drop public synonym OWA_OPT_LOCK;
Drop public synonym OWA_PATTERN;
Drop public synonym OWA_SEC;
Drop public synonym OWA_TEXT;
Drop public synonym OWA_UTIL;
Drop public synonym OWA_INIT;
Drop public synonym OWA_CACHE;
Drop public synonym WPG_DOCLOAD;
3. Connect to the OWA package's installation mode oas_public to ensure that the user has the create public synonym permission. If not, manually grant this permission to the user.
4. Run the following commands. This will recreate the OWA public synonym so that it can refer to the OWA package of Oracle Application Server.
Create public synonym OWA_CUSTOM for OWA_CUSTOM;
Create public synonym OWA_GLOBAL for OWA_CUSTOM;
Create public synonym OWA for OWA;
Create public synonym HTF for HTF;
Create public synonym HTP for HTP;
Create public synonym OWA_COOKIE for OWA_COOKIE;
Create public synonym OWA_IMAGE for OWA_IMAGE;
Create public synonym OWA_OPT_LOCK for OWA_OPT_LOCK;
Create public synonym OWA_PATTERN for OWA_PATTERN;
Create public synonym OWA_SEC for OWA_SEC;
Create public synonym OWA_TEXT for OWA_TEXT;
Create public synonym OWA_UTIL for OWA_UTIL;
Create public synonym OWA_INIT for OWA_CUSTOM;
Create public synonym OWA_CACHE for OWA_CACHE;
Create public synonym WPG_DOCLOAD for WPG_DOCLOAD;
5. Prevent Oracle HTTP Server configuration changes when you reinstall the same Oracle Home Directory
Make sure that you have saved httpd. conf, jserv. conf, zone. properties, and all the copy files of the Oracle HTTP Server configuration file that you have changed. Depending on how you install Oracle9i Version 2 (9.2.0.1.0) in the same home directory as Oracle, these configuration files may be overwritten by news articles.
