Considerations for using the Oracle9i database

oracle| Data | The Oracle HTTP server in the 9.2.0.1.0 version of the database Oracle database changes as follows:

First, about the Apache Jserv process

The maximum number of Apache Jserv processes supported by Oracle HTTP Server has been increased from the default value of Apache 25 to a maximum of 128, and this value is not configurable in real time.

Second, JDK/JRE certification

Oracle is certified to use both Jdk/jre 1.3.1_01 and Jdk/jre 1.2.2_07 to build and configure Java applications with Mod_jserv modules.

In the 9.2.0.1.0 version, all Java class libraries (such as BC4J, XDK) are loaded and compiled along with JDK 1.1.8_10. These compiled classes are certified to run in a version supported by the Java JRE, and they must not be recompiled.

Third, the requirements of module Mod_plsql

To use the Mod_plsql module for a particular backend database, you need to manually install the Oracle Pl/sql WEB Toolkit (OWA pl/sql packages) on a specific backend database. The OWA pl/sql packages should be installed in the SYS database mode to ensure that you install it only once. Note the existing Oracle Application Server (OAS) users must replace the old versions of these packages when migrating to Oracle HTTP server.

For more information on using the Pl/sql Gateway in Oracle HTTP Server, refer to http://hostname.domain:port/pls/admin_/title.htm.

Iv. Recovery of OWA packages for application servers

When you install new Mod_plsql OWA packages, they are placed in sys database user mode, which can cause problems for the application server (Oracle Application Server) using OAS Pl/sql cartridge components, If you encounter these problems and want to continue using the OAS Pl/sql cartridge component, you must re-establish synonyms so that these synonyms are referenced to the OWA package. The steps to establish synonyms on the source database are as follows:

1. SYS account is connected to the database in Sql*plus

2. Run the following command in Sql*plus, which deletes all OWA public synonyms that were established during 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. Install mode oas_public that connects to the OWA package to ensure that the user has create public synonym permissions, and if not, you must manually grant this permission to this user.

4. Run the following command. This will re-establish the OWA public synonyms to refer to the Oracle Application Server's OWA package.


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;




V. Prevent configuration changes to Oracle HTTP server when reinstalling in the same Oracle home directory

Verify that the copy files for httpd.conf, jserv.conf, Zone.properties, and all of your changed Oracle HTTP server configuration files have been saved. Depending on how you install Oracle9i version 2 (9.2.0.1.0) to the same home directory as the previous Oracle, these profiles may be overwritten by the news item.

Six, add memory for Apache Jserv application

If the Apache jserv log file or browser reports "out of Memory" because of a JVM memory overflow, this typically occurs when the JVM holds data that exceeds its memory allocation unit. The steps to increase the maximum value of the memory pool allocated for the JVM are as follows:

1. Add a row to the file $oracle_home/apache/jserv/etc/jserv.properties


Wrapper.bin.parameters=-mx<size>m




<size> is in megabytes (MB), the memory default is 1 Mb,oracle recommended to use 128 MB, add the following line


wrapper.bin.parameters=-mx128m




2. Restart the Web server

Vii. NLS Considerations

1. For Mod_plsql

When configuring Mod_plsql, the environment variable Nls_lang is configured at each instance level of the Web server rather than at the dad level. Be sure to configure the environment variable Nls_lang correctly before starting your Oracle HTTP server instance.

2. For Oracle PSP (Pl/sql page)

For Oracle PSP, environment variable Nls_lang must be configured between the database using the LOADPSP command-line program to load the Pl/sql Server page (PSPs).

3. Using the JDBC OCI8 driver in Jserv and oraclejsp

If you connect to a database through a JDBC OCI8 drive, you need the appropriate Nls_lang settings in the file jserv.properties. Like what:

Wrapper.env=nls_lang=american_america. UTF8

Viii. Configuring Listener.ora files for EJBs

In the 9.2.0.1.0 version, the installation of the Oracle HTTP server did not configure the Listener.ora file to run Enterprise JavaBeans (EJBs), and in order to run EJBs, You need to configure Listener.ora files as follows:


LISTENER =
(Description_list =
(DESCRIPTION =
(Address_list =
(address = (PROTOCOL = IPC) (KEY = Extproc))
)
(Address_list =
(address = (PROTOCOL = IPC) (KEY = Icache))
)
(Address_list =
(address = (PROTOCOL = TCP) (HOST = )
)
(DESCRIPTION =
(Protocol_stack =
(presentation = GIOP)
(Session = RAW)
)
(address =
(PROTOCOL = TCP) (HOST = )
)
Sid_list_listener =
(Sid_list =
(Sid_desc =
(Sid_name = Plsextproc)
(Oracle_home = <ORACLE_HOME>)
(program = Extproc)
)
(Sid_desc =
(Global_dbname = Icache)
(Oracle_home = <ORACLE_HOME>)
(Sid_name = Icache)
)
)





Where
IX. Limitations of using Oracle xSU

In the 9.2.0.1.0 version, Oracle XML SQL Utility (XSU) does not contain the Setencoding method, and in order to download the latest version of the xSU support encoding feature, consult http://otn.oracle.com/tech/xml/ oracle_xsu/.