Nine major considerations using Oracle9i database
Oracle HTTP Server in the Oracle Database has a change in the following changes in the 9.2.0.1.0 version:
First, About Apache JServ Process
The maximum number of Apache Jserve processes supported by Oracle HTTP Server has increased from the default value of the Apache to the maximum value 128, which is not real-time.
Second, JDK / JRE certification
Oracle is authenticated to establish and configure a Java application with a Mod_JSERV module using both JDK / JRE 1.2.2_01 and JDK / JRE 1.2.2_07.
In version 9.2.0.1.0, all Java class libraries (such as BC4J, XDK) are loaded and compiled with JDK 1.1.8_10. These compile classes are authenticated in the version of Java JRE support, and they must be reheated.
Third, the demand for module MOD_PLSQL
Using the MOD_PLSQL module for a specific backend database, you need to 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, make sure you only have it once. Note that the Oracle Application Server (OAS) user that already exists is migrated to Oracle HTTP Server, the old version of these packs must be replaced.
For more information on the PL / SQL gateway in Oracle HTTP Server, please check http: //hostname.domain: Port / PLS / Admin_ / Title.htm. Fourth, restore the OWA package for the application server
When you install a new MOD_PLSQL OWA package, they are placed in Sys database user mode, which will bring questions to the application server (Oracle Application Server) using the OAS PL / SQL CARTRIDGE component, if you encounter these problems and want to continue With the OAS's PL / SQL Cartridge component, some synonyms must be re-established, so that these synonyms refer 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 will delete all OWA publicity symbols established 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 installation mode OAS_PUBLIC, make sure the user has CREATE PUBLIC SYNONYM permissions, if not, you must do this to this user.
4. Run the following command. This will re-establish the OWA common synonym to refer to the OWA package of Oracle Application Server. CREATE PUBLIC SYNONYM OWA_CUSTOM for OWA_CUSTOM
Create Public Synynym 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. Preventing the configuration change of Oracle HTTP Server when reinstalling in the same Oracle home directory
Confirm that httpd.conf, jserv.conf, zone.properties, and all you have changed a copy of the Oracle HTTP Server configuration file. These profiles may be overwritten by news parts depending on the way you install Oracle9i's version 2 (9.2.0.1.0) to the same home directory of previous Oracle.
6. Add memory for Apache JSERV applications>
If the apache jserv log file or browser reports "Out of Memory", the reason is the JVM memory overflow, which typically occurs in the data held by the JVM exceeds its memory allocation unit. The steps in the maximum value of the memory pool allocated for JVM are as follows:
1. Add a line of wrapper.bin.parameters = -mxm in file $ oracle_home / apache / jserv / etc / jserv.properties
The unit is a megabyte (MB), and the memory default value is 1 MB. Oracle recommends 128 MB, then adds the following wrapper.bin.parameters = -MX128M
2. Restart Web Server
Seven, NLS Precautions 1. For Mod_PLSQL
When configuring mod_plsql, environment variable NLS_LANG is configured at each Web Server instance and not in the DAD level configuration. Make sure that the environment variable NLS_LANG is configured correctly before starting your Oracle HTTP Server instance.
2. For Oracle PSP (PL / SQL page)
For Oracle PSP, environment variable NLS_LANG must load the PL / SQL Server page (PSPS) to the database between the database using the LOADPSP command line program.
3. Using JDBC OCI8 drivers in JSERV and OracleJSP
If you connect to the database via the JDBC OCI8 drive, you need a suitable NLS_LANG setting in the file jserv.properties. For example: wrapper.env = nls_lang = American_america.utf8 eight, configure the listener.ora file for EJBS
In version 9.2.0.1.0, Oracle HTTP Server installation does not configure the listener.ora file to run Enterprise JavaBeans (EJBS), in order to run EJBS, you need to configure the listener.ora file:
Listener =
(Description_List =
(Description =
(Address_list =
(Address = (Protocol = IPC) (Key = extproc))))
(Address_list =
(Address = (protocol = IPC) (key = icache))
)
(Address_list =
(Address = (protocol = TCP) (Host =) (port = 1521))
)
(Description =
(Protocol_stack =
(Presentation = Giop)
(Session = RAW)
)
(Address = (protocol = TCP) (host =) (port = 2481))
)
)
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSEXTPROC)
(Oracle_Home =)
(Program = extproc)
)
(SID_DESC =
Global_dbname = icache)
(Oracle_Home =)
(SID_NAME = ICache)
)
Among them, your computer's actual host name is your Oracle home directory $ Oracle_home.
Nine, use Oracle XSU limitations
In version 9.2.0.1.0, Oracle XML SQL Utility (XSU) does not include the setEncoding method, in order to download the latest version of the XSU's support coding function, please consult http://otn.oracle.com/tech/te/xml/oracle_xsu/ .
