Skip Headers

Oracle9i Application Server Release Notes
Release 1 (v1.0.2.2) for AIX-Based Systems, Compaq Tru64 UNIX, HP 9000 Series HP-UX, Linux Intel, and Sun Solaris Intel

Part Number A90377-01
Go To Table Of Contents
Contents

Go to previous page

1
Summary of Changes and New Features

This document is accurate to the best of our knowledge at the time of publication. Information that is discovered subsequent to publication will be available through normal support channels.

You can access the latest information and additions to these Release Notes from the following web-site:

http://docs.oracle.com

1.1 Purpose of this Document

This document notes differences between Oracle9i Application Server Release 1 (v1.0.2.2) for UNIX components and their documented functionality.

1.2 Product Naming

Product name changes in this release are:

Old Name  New Name 

Oracle8i JVM 

Oracle Enterprise Java Engine (EJE) 

Oracle Forms Service 

Oracle9iAS Forms Services 

Oracle LDAP Developer's Kit 

Oracle Internet Directory (Client) 

Oracle Database Client Developer's Kit 

Oracle Database Developer Kit 

Oracle XML Developer's Kit 

Oracle XML Developer Kit 

Oracle Portal 

Oracle9iAS Portal 

Oracle Portal-to-Go 

Oracle9iAS Wireless 

Oracle Database Cache 

Oracle9iAS Database Cache 

Oracle Web Cache 

Oracle9iAS Web Cache 

Oracle Reports Service 

Oracle9iAS Reports Services 

Oracle Discoverer 

Oracle9iAS Discoverer 

Oracle Transparent Gateways 

Oracle Gateways 

Oracle eMail Server 

Oracle9iAS Email 

Oracle Unified Messaging 

Oracle9iAS Unified Messaging 

Oracle Internet File System 

Oracle9i File System 

Oracle9i Application Server internet applications and their sub-components are listed below:

Oracle HTTP Server powered by Apache

Oracle9i Application Server Containers for J2EE

Oracle PL/SQL

Oracle9i Application Server Forms Services

Oracle9i Application Server Developer Kits

Oracle9i Application Server Portal

Oracle9i Application Server Wireless

Oracle9i Application Server Cache

Oracle9i Application Server Business Intelligence

Oracle Enterprise Manager

Oracle Advanced Security

Oracle9i Application Server Integration

Oracle Internet File System

1.3 Certification Information

You can access the most recent certification information at:

http://metalink.oracle.com

1.3.1 JDK/JRE Certification

Oracle has certified the use of both JDK/JRE 1.1.8 and JDK/JRE 1.2.x for building and deploying Java applications with mod_jserv. For this release, all Java class libraries (e.g. Oracle Business Components for Java, Oracle XML Developer's Kit) are shipped, compiled with JDK 1.1.8_10. These compiled classes are certified to run under both supported versions of the Java JRE, and they must not be recompiled.

For certification with JDK 1.3, refer to Oracle9i Application Server Release Notes Addendum.

1.3.1.1 Java Importer Environment Settings

The Java Importer feature is available in Oracle9iAS Forms. It requires JDK 1.2.2.


Note:

Since Oracle9i Application Server for Linux does not support the JDBC 1.2 driver, the Java Importer feature is not available on Linux. 


To enable this feature, perform the following steps:

  1. Set PATH to include <java_inst_dir>/bin.

  2. Set CLASSPATH to <IAS_HOME>/6iserver/lib/importer.jar and the locations of Java class files that you want to import.

    Set the library path variable, listed in the following table, that corresponds to your platform:


    Note:

    The java_inst_dir variable defines the location where you installed JDK and JRE 1.2. 


    Table 1-1 Environment Variables and Library Paths for UNIX platforms
    Platform  Environment Variable  Library Path 

    AIX 

    LIBPATH 

    <java_inst_dir>/jre/bin:<java_inst_dir>/jre/bin/classic
    
     

    HP 

    SHLIB_PATH 

    <java_inst_dir>/jre/lib/PA_RISC:<java_inst_dir>/jre/lib/PA_RISC/classic:

    <java_inst_dir>/jre/lib/PA_RISC/native_threads
    
     

    Sun Intel 

    LD_LIBRARY_PATH 

    <java_inst_dir>/jre/lib/i386
    
     

    Tru64 

    LD_LIBRARY_PATH 

    <java_inst_dir>/jre/lib/alpha:<java_inst_dir>/jre/lib/alpha/classic:
    <java_inst_dir>/jre/lib/alpha/native_threads
    
     

1.3.1.2 AIX-Based Systems JDK 1.2 Certification

Oracle9i Application Server Release 1 (v1.0.2.2) has the following certification for AIX-Based Systems:

Table 1-2 JDK Certification for AIX Versions
Operating System  Certification 

AIX 4.3.2 

JDK 1.1.8 

AIX 4.3.3 

JDK 1.1.8 and JDK 1.2.2 

1.3.1.2.1 Problems with Apache Jserv on AIX 4.3.2

JDK 1.1.8 causes problems starting Apache Jserv on AIX 4.3.2. The just-in-time compiler of JDK generates this problem. To disable JIT for ApacheJserv, users on AIX 4.3.2 with JDK 1.1.8 must add the following line to the $ORACLE_ HOME/Apache/Jserv/etc/jserv.properties file:

wrapper.env=JAVA_COMPILER=NONE
1.3.1.2.2 Problems with Apache Jserv on AIX

Users who want to use the standard IBM distribution of JDK 1.2.2 from /usr/java_dev2 may have problems running the Apache JServ. In the standard IBM distribution of JDK 1.2.2, the usr/java_dev2/bin directory does not contain the Java executable that Apache Jserv requires to run.

To enable Apache Jserv, replace the
wrapper.bin=<oracle-home>/Apache/jdk/bin/java
line in the $ORACLE_HOME/Apache/Jserv/etc/jserv.properties
file to the following:

wrapper.bin=<oracle-home>/Apache/jdk/jre/sh/java

Distributions of JDK 1.2.2 on IBM that have the Java executable at the default JDK_HOME/bin location do not require this modification.

1.3.1.3 Oracle9iAS Portal and Oracle9iAS Wireless

Oracle certifies Oracle9iAS Portal 3.0 and Oracle9iAS Wireless 1.1 with JDK 1.2.2 only. For AIX-Based Systems users, JDK 1.2.2 is only available on AIX 4.3.3. As a result, Oracle9iAS Portal 3.0 and Oracle9iAS Wireless 1.1 are only available on AIX 4.3.3.

1.3.1.4 Oracle9iAS Email Web Client

Oracle certified the Web client feature of Oracle9iAS Email with JDK 1.2.2 for AIX-Based Systems. Since JDK 1.2.2 is only available in AIX 4.3.3, Web Client will work properly only in AIX 4.3.3.

Oracle certified Web Client with JDK 1.1.8 only on Linux Intel.

1.3.2 Oracle Enterprise Manager Certification

Oracle9i Application Server Release 1 (v1.0.2.2) includes Oracle Enterprise Manager 2.2, which is not certified against the Oracle9i database.

1.3.3 Oracle9iAS Wireless Data Server Support

Oracle9iAS Wireless only supports Oracle 8.1.6 and above.

1.4 New Features

This section describes new features in Release 1 (v1.0.2.2) in each application area.

1.4.1 Internet Applications New Features

1.4.1.1 Oracle9i Application Server Containers for J2EE

Oracle9iAS Containers for J2EE is a pure Java container/runtime executing on JDK. It provides:

This release of Oracle9iAS Containers for J2EE is more stable when using the JDK version 1.2.2_07 or 1.3x. Oracle recommends using version 1.2.2_07, the JDK shipped with Oracle9iAS.

Oracle9iAS Containers for J2EE is distributed in the file oc4j.zip. Unzip the file and follow the instructions in the README.

The following J2EE components and services are featured:

1.4.1.1.1 Java Servlets

1.4.1.1.2 Java Server Pages

1.4.1.1.3 Enterprise JavaBeans (EJB)

1.4.1.1.4 Java Database Connectivity Services (JDBC)

1.4.1.1.5 Embedded SQL in Java (SQLJ) Implementation

The standard ANSI SQLJ implementation in Oracle9iAS Containers for J2EE allows placement of dynamic SQL directly in SQLJ statements, without the need to revert to JDBC (in most situations). The SQLJ implementation can perform fetch commands from an untyped ResultSetIterator, and allows omission of iterator declarations.

JDBC programs and logic can be transformed 1:1 into SQLJ. You can generate Oracle JDBC code directly, without having to generate or customize SQLJ profiles. Corresponding Oracle JDBC enhancements are also supported.

1.4.1.1.6 Infrastructure Services

Oracle9iAS Container for J2EE contains the following infrastructure components:

1.4.1.1.7 Configuration, Deployment, and Administration

Oracle9iAS Container for J2EE configuration is standardized upon XML and managed in server, generic, and application/component areas:

The following tools are included to streamline deployment processes:

1.4.1.1.8 System Administration

System administration can be done remotely or locally, with the command line tool. The management console shipped with Oracle9iAS Release 1 (v1.0.2.2) is a technology preview of features available in the next release. This console is not supported for production use. Oracle9iAS Release 2 will include a new management console fully integrated with Oracle Enterprise Manager.

Logging services are provided to aid system adminstration and development. You can log web access, applications, servers, and RMI and JMS activity.

In this release, Oracle9iAS assists system adminstration with the the following features and facilities:

1.4.1.1.9 Load Balancing and Availability Features

1.4.1.1.10 Clustering Facilities

1.4.1.2 Oracle HTTP Server powered by Apache

1.4.1.2.1 Note About Apache JServ Processes

The maximum number of Apache JServ processes supported in an Oracle9i Application Server site has been increased from the Apache distribution default maximum of 25 to an Oracle9i Application Server maximum 128. This value is not runtime configurable.

1.4.1.2.2 Support for Third Party Components in Oracle9i Application Server

All Third Party Components

Portions of Oracle9i Application Server are distributed by Oracle under license from third parties ("Third Party Components"), including Apache Web Server, version 1.3.19, licensed by Apache Software Foundation. Oracle is distributing these Third Party Components as part of the Oracle9i Application Server product and, except as specified, will provide standard product support for the Third Party Components, as such support is further defined in the Oracle technical support policies.


Note:

Oracle will only support the version of the Third Party Component shipped with Oracle9i Application Server and that other versions which may be freely available on the Internet will not be supported by Oracle. 


Oracle may, as a courtesy, refer enhancement requests regarding the Third Party Components to the party who licensed the Component to Oracle; Oracle shall have no obligation to do so. No technical assistance requests will be filed on the non-Third Party Components (the "Oracle Components") unless the problem can be reproduced in an environment consisting of only the Oracle Components.

Apache Modules

Oracle may distribute certain extensions to the Apache Web Server ("Apache Modules") to enhance the functionality provided by the Apache Web Server as part of Oracle9i Application Server. Apache Modules distributed by Oracle are referred to in these Release Notes as Oracle Apache Modules.

Oracle supports the following Oracle Apache Modules in this release:

http_core

Core Apache features.

mod_access

Host-based access control; provides access control based on client hostname or IP address.

mod_actions

Filetype/method-based script execution; provides for CGI scripts based on media type or request method.

mod_alias

Aliases and redirects; provides for mapping different parts of the host filesystem in the document tree, and for URL redirection.

mod_auth

User authentication using text files.

mod_auth_anon

Anonymous user authentication, FTP-style.

mod_autoindex

Automatic directory listings.

mod_cgi

Execution of CGI scripts; processes any file with mime type application/x-httpd-cgi.

mod_define

Configuration definitions.

mod_digest

MD5 authentication; provides for user authentication using MD5 Digest Authentication.

mod_dir

Basic directory handling; provides for "trailing slash" redirects and serving directory index files.

mod_env

Passing of environments to CGI scripts; provides for passing environment variables to CGI/SSI scripts.

mod_expires

Apply Expires: headers to resources; provides for the generation of Expires headers according to user-specified criteria.

mod_fastcgi

Routes requests to a pool of Fast CGI servers.

mod_headers

Add arbitrary HTTP headers to resources; headers can be merged, replaced or removed.

mod_include

Server-parsed documents; provides for server-parsed HTML documents.

mod_info

Server configuration information; provides a comprehensive overview of the server configuration including all installed modules and directives in the configuration files.

mod_jserv

Communication with servlet engine.

mod_log_config

User-configurable logging replacement for mod_log_common; provides for logging requests made to the server, using the Common Log Format or a user-specified format.

mod_log_referer

Logging of document references; provides for logging the documents that reference documents on the server.

mod_mime

Determining document types using file extensions.

mod_mime_magic

Determining document types using "magic numbers"; can be used to determine the MIME type of a file by looking at a few bytes of its contents.

mod_negotiation

Content negotiation.

mod_ose

Delegates URLS to stateful Java and PL/SQL servlets in Oracle Servlet Engine (OSE).

mod_oprocmgr

Provides process management and death detection to the servlet engine.

mod_perl

Support for writing Apache modules in Perl.

mod_plsql

PL/SQL support.

libproxy (mod_proxy)

Caching proxy abilities; provides for an HTTP 1.0 caching proxy server.

mod_rewrite

Powerful URL-to-filename mapping using regular expressions; provides a rule-based rewriting engine to rewrite requested URLs on the fly.

mod_setenvif

Set environment variables based on client information; provides for the ability to set environment variables based upon attributes of the request.

mod_so

Support for loading modules at runtime; provides for loading of executable code and modules into the server at start-up or restart time.

mod_speling

Automatically correct minor typographical errors in URLs; attempts to correct misspellings of URLs that users enter, by ignoring capitalization and allowing up to one misspelling.

mod_ssl

SSL support.

mod_status

Server status display; allows a server administrator to find out how well the server is performing, presenting an HTML page that gives the current server statistics in an easily readable form.

mod_unique_id

Generate unique request identifier for every request; provides a magic token for each request that is guaranteed to be unique across "all" requests under very specific conditions.

mod_userdir

User home directories; provides for user-specific directories.

mod_usertrack

User tracking using cookies.

mod_vhost_alias

Support for dynamically configured mass virtual hosting.

Any other Oracle Apache Modules that are included in Oracle9i Application Server are provided "as is" without warranty or support of any kind. Apache Modules from any source other than Oracle, including the Apache Software Foundation or a customer, will not be supported by Oracle.

In addition, Oracle will only provide technical support for problems that can be reproduced with an Apache configuration consisting only of supported Oracle Apache Modules.

Oracle supports the use of the included Perl interpreter within the supported Apache configuration only.

1.4.1.2.3 Building mod_perl DBI/DBD-Oracle and Apache::DBI

To build, install, and test mod_Perl DBI/DBD-Oracle and Apache::DBI for UNIX platforms, perform the following steps:

  1. Verify that the following software is available in your environment:

    • C compiler

    • GNU Make GNU Make version 3.77

    • Perl Perl version 5.005_03

  2. Verify that your PATH environment variable is set correctly to locate the required software.

  3. Install Oracle9iAS from your product CD. This version has mod_perl 1.21 built in. This installation does not include the following modules:

    • Apache::DBI

    • Perl DBI

    • Perl DBD-Oracle

  4. Set your PATH environment variable to pick up the correct Perl binaries. For example:

    prompt> setenv ORACLE_HOME /private1/iAS10 
    prompt> setenv PATH ${ORACLE_HOME}/Apache/perl/bin:${PATH}
    
    

    Note: There are other methods. Depending on your platform, they include setting the environment variables in the following table that make mod_perl DBI/DBD-Oracle work.

    Table 1-3 Environment Variables for UNIX platforms
    Platform  Environment Variable 

    AIX 

    LIBPATH 

    HP 

    SHLIB_PATH 

    Linux, Tru64, Sun Intel 

    LD_LIBRARY_PATH 

    All platforms 

    PERL5LIB 

  5. Set the environment variable PERL5LIB to the following:

    prompt> setenv PERL5LIB ${ORACLE_HOME}/Apache/perl/lib/5.00503:${ORACLE_
    HOME}/Apache/perl/lib/site_perl/5.005
    
    
  6. Go to the following web-site:

    http://www.cpan.org/modules/by-module 
    
    
  7. Download the following modules:

    DBI version 1.14

    DBD::Oracle version 1.06

    Apache::DBI version 0.87

  8. Unpack the DBI package and follow the README instructions carefully to build, test, and install the module.

  9. The DBD-Oracle module requires that path settings to Oracle software (such as $ORACLE_HOME/lib, $ORACLE_HOME/rdbms/lib etc.) are set in order to build the driver successfully. Make sure that you set the following environment variables:

    1. Set the ORACLE_HOME environment variable to point to a valid Oracle9i Application Server install or an Oracle database install (for example, 8.1.6, 8.1.7, etc.).

    2. Set the ORACLE_SID environment variable to point to a valid Oracle SID.

    3. Depending on your platform, verify that the appropriate environment variable in the following table points to the corresponding file:
      Table 1-4 Environment Variables, Filenames for UNIX platforms
      Platform  Environment Variable  File 

      AIX 

      LIBPATH 

      libclntsh.a 

      HP 

      SHLIB_PATH 

      libclntsh.sl 

      Linux, Solaris Intel, Tru64 

      LD_LIBRARY_PATH 

      libclntsh.so 

      To point to these files set $ORACLE_HOME/lib in the appropriate environment variable for your system.

    4. If you are using National Language Support (NLS), make sure that you set the ORA_NLS and ORA_NLS33 environment variables to avoid ORA-01019 errors.

    5. Set the ORACLE_USERID environment variable. If you choose not to set this, the tests will use scott/tiger by default).

  10. Unpack the DBD-Oracle package and follow the README instructions carefully to build, test, and install the module. The database must be "up" for the tests to run successfully.

  11. Unpack the Apache::DBI package and follow the README instructions to build and install the module. There are no tests available for this module yet. This step will install the Apache AuthDBI.pm and DBI.pm modules.

  12. Edit $ORACLE_HOME/Apache/Apache/conf/httpd.conf as follows:

    1. Uncomment the following line (remove the pound sign that is prepended):

      PerlModule Apache::DBI
      

      This allows the use of Apache::DBI's persistent database connections. For more information, refer to Examples in the Apache::DBI README instructions.


      Note:

      httpd.conf is the main Apache server configuration file. Be sure to understand the instructions at the beginning of this file.  


  13. Test your persistent connection. As an example, perform the following to test the connection via your startup.pl:

    1. Add this line to your httpd.conf file:

      PerlRequire <absolute path to ApacheDBI's startup.pl script>
      
      
    2. Modify the startup.pl connect call, such as:

      Apache::DBI->connect_on_init('dbi:Oracle:',"scott/tiger", '');
      
      
    3. Restart your Oracle HTTP Server:

      prompt> $ORACLE_HOME/Apache/Apache/bin/apachectl start
      
      
    4. Check Oracle HTTP Server logs to verify that connections were obtained correctly.


      Note:

      If Oracle HTTP Server logs report that the ORACLE_HOME environment variable is not set, try adding this line to your httpd.conf file: PerlSetEnv ORACLE_HOME "<absolute path to Oracle Home>" 


Another sample Perl script to test the connection is:

##### Perl script start ###### 
use DBI;
print "Content-type: text/plain\n\n"; 
$dbh = DBI->connect("dbi:Oracle:", "scott/tiger", "") || die $DBI::errstr; 	 
$stmt = $dbh->prepare("select * from emp order by empno")|| die $DBI::errstr; 
$rc = $stmt->execute() || die $DBI::errstr; 
while (($empno, $name) = $stmt->fetchrow()) { print "$empno $name\n"; } 
warn $DBI::errstr if $DBI::err; 
die "fetch error: " . $DBI::errstr if $DBI::err; 
$stmt->finish() || die "can't close cursor"; 
$dbh->disconnect() || die "cant't log off Oracle"; 
	##### Perl script End ######

1.4.2 Wireless New Features

1.4.2.1 Oracle9iAS Wireless

1.4.2.1.1 Oracle9iAS Wireless 1.1.1.1

Oracle 9i Application Server Wireless 1.1.1.1 is a patch for Oracle9i Application Server Wireless Edition 1.1 (which was shipped with Oracle9i Application Server 1.0.2.1.0). Oracle9i Application Server Wireless 1.1.1.1 is a super-patch that includes the Oracle9i Application Server Wireless 1.1.1 patch recently posted on Oracle Technology Network.

This patch fixes the following bugs:

1684463, 1644304, 1618453, 1561062, 1761993, 1684020, 1640550, 1618443, 1542848, 1745915,1646074, 1635012, 1605794, 1371832,1743977, 1644311, 1620174, 1576480, 1371822, 1743922, 1757409

1.4.2.1.2 Adapters

To address language-encoding issues, new optional input parameters have been added:

INPUT_ENCODING has been added to the URL adapter enabling it to specify the remote XML page's charset.

inputEncoding has been added to StripAdapter enabling it to specify the remote HTML page's charset.

1.4.2.1.3 Transformers

The HDML, TINY_HTML and WML1.1 transformers have been modified. By default, these modified transformers will NOT be loaded into the Repository.

If you HAVE NOT made changes to the transformers, upload up11-111.xml.

If you have modified the shipped version of these transformer, perform the following steps:

  1. Merge the differences.

  2. Upload the new transformers using the LoadXML utility upload.sh with up11-111.xml, shipped with the patch release. You can find the LoadXML utility at:

    $ ORACLE_HOME/panama/sample/upload.sh
    

    See also:

    For more information on LoadXML utility, refer to Oracle9i Application Server Wireless Configuration Guide

1.4.2.1.4 New Search/Sort Feature Introduced into Service Designer

When you right click on the Master Services node or a folder node, you will find a Search/Sort command. You can search on service names (service names are case-insensitive); wild cards (such as `%') are accepted. Search results can be sorted by Name, LastUpdated Date, or Sequence Number. The new Search feature is more efficient when you are trying to load a large number of services.

The search results will be the new child nodes of the folder which will be automatically expanded. After you collapse the folder and re-expand it, all of its children will be loaded by default. In either case, if the result set is too large and surpasses the limit size specified in ptgsd.properties, you will receive a warning, and only part of the result set will be loaded. In this case, if your expected service is not displayed, you must fine tune your search criteria and reaccomplish the search.

1.4.2.1.5 System Logger

Previously, information for logging service requests and session were logged in the repository as these events occurred. This degraded the performance in high-load production environments.

In this patch, System Logger implementation has been improved. To avoid performance issues caused by queuing up the log information and logging to the database, changes were made to defer the database logging by first logging the data into files and having a separate process to read from the file and log to the database.

The Logger creates these directories:

Additional Configuration Needed

The following parameters must be set for the current release. Most of the new configurable parameters have default values. Administrators should reset these values to suite local requirements.

SystemLog.loggerOutputDirectory=xxx
(default same as the value set for property log.directory)

The Root path for the log, process and archive directories. These are created under this root directory. By default the System Logger uses the directory specified in the property log.directory which is defaulted to /tmp. This parameter may be left blank.

SystemLog.maxLogFileSize=xxx

The maximum size of the file in the log directory. Once the log file reaches this file size, the logging process will close this file and move it to the process directory.

SystemLog.logFileNamePrefix=xxx (default ias_)

The user-defined log file name prefix. The default prefix will be iaswe. A typical file name will be <SystemLog.logFileNamePrefix>_<ptginstancename_<creationtimestamp>.log

SystemLog.field.delimiter=xxx (default #%=%#)

Delimiter for the logged namevalue pairs. SystemLogger uses its default.

SystemLog.record.delimiter=xxx (default ~#$)

Delimiter for the logged records. SystemLogger uses its default.

SystemLog.maxLogFileSize=xxx

Maximum number of bytes per log file. This needs to be set to a suitably large number.

SystemLog.start.dbLogger=[true/false] (default is true)

Enable or Disable Database logging. If this is false, the logged records will only remain in files. If true, the records are picked from files and logged onto the database. The DB Logger thread is started. Values are True/False.

SystemLog.logger.wakeupFrequency=xxx (default is 1 min)

Number of minutes after which the DB Logger thread wakes up to check for any new log files in the process directory.

SystemLog.logger.maxSize=xxx (default 15)

Batch size for Database Logging.

SystemLog.driver=xxx
(default is taken as the value in the db.driver property, unless the user requires using a separate driver for the logger.)

Database JDBC driver <String> one of "THIN", "V7", "V8", "INTERNAL" and "CUSTOM"

SystemLog.driver.class=xxx (default is taken as Oracle's driver.)

Connect using a customized JDBC driver <class_name>. Not implemented in version 1. Must be set if SystemLog.driver=CUSTOM

The following are some existing configuration parameters in the oracle/panama/core/admin/System.properties file which will be retained:

SystemLog.enableServiceLogging=[true/ false]

Specifies whether or not the Service Logging is enabled.

SystemLog.enableSessionLogging=[true/ false]

Specifies whether or not the Session Logging is enabled.

The status of the last record logged into the database is stored in the status log files. The status log files assist administrators in crash recovery by enabling them to inspect the last processed file and record, and to ensure that the Database Logger does not attempt to log duplicate records.

How to Start DB Logger

The default configuration will start the DBLogger thread along with the panama servlet launch. However, you can turn this off by setting the property SystemLog.start.dbLogger to false.

You can launch DB Logger as a separate process:

- java -classpath <needed panama classes> oracle.panama.core.admin.DbLogger

If all software were installed under d:\, the startup command will look like this:

java -classpath d:\panama\lib\panama.zip;d:\panama\lib\panama_
core.zip;D:\jsdk2.0\lib\jsdk.jar;D:\panama\lib\classes12.zip;d:\panama\lib\jndi.
jar;D:\panama\lib\xmlparserv2.jar oracle.panama.core.admin.DbLogger

Debugging

Sending the PAdebug=1 flag as part of a query string will not, by itself, enable the debugging capability. The login user for the current session must be either a Designer or an Administrator. Refer to the Oracle9i Application Server Wireless Implementation Guide for information on how to create a Designer or an Administrator.

Testing Wizard

You must have the Designer role in order to use the Test Wizard inside the Service Designer. Otherwise only the device result will be displayed when a service is being tested.

1.4.2.1.6 E-mail and Directory Applications

FastForward Email and Directory applications enable you to provide your end users with access to their corporate email and directory lookup on any mobile device. For more information, refer to Oracle 9i Application Server Wireless Configuration Guide.

1.4.2.1.7 Multiple VM Setup for Oracle9iAS Wireless

To take advantage of the new group-based load-balancing features, make the following changes in the jserv.conf file:

  1. ApJServManual must be set to auto (as opposed to on or off) for the new feature directives to take effect.

  2. With the new load-balancing architecture, multiple instances can be grouped together. A group is a set of instances across which the traffic is load-balanced. The member instances of a group can exist on one or more machines. A group is defined by the following directive:

    ApJServGroup groupname nprocs weight propfile
    

    where:

    groupname is the name of the group.

    nprocs is the number of processes to start for this group on the local machine.

    weight is the traffic distribution skew factor assigned to this group on this host.

    propfile the path to the jserv.properties file

    Example:

    ApJServGroup group1 2 1

    P:\ORACLE\10210PWE\Apache/Jserv/etc/jserv.properties
    
    

    ApJServGroup group1 1 1

    P:\ORACLE\10210PWE\Apache/Jserv/etc/jserv.properties
    
    

    ApJServGroup group2 1 1

    P:\ORACLE\10210PWE\Apache/Jserv/etc/jservSoap.properties
    
    
  3. To make allowance for the groups, use the following directive in lieu of ApJServMount:

    ApJServGroupMount /mountpoint balance://groupname/zone
    
    

    where:

    mountpoint is the name of the URI path to mount jserv-url on

    groupname is one of the groups defined in the ApJServGroup directive

    zone is the zone this servlet is associated with

    Example:

    ApJServGroupMount /ptg balance://group1/root

    ApJServGroupMount /ptg balance://group1/root

    ApJServGroupMount /ptg balance://group1/root

1.4.3 Business Intelligence New Features

1.4.3.1 Oracle9i Application Server Business Intellience

1.4.3.1.1 Oracle9i Application Server Reports Security Scripts No Longer Needed

The Oracle9i Application Server documentation states that you must run Reports security scripts to enable the security features. This is no longer true, since in Oracle9i Application Server Release 1 (v1.0.2.2), the scripts are pre-loaded into the Portal, and have been removed from the install media.

1.5 Known Issues

This section describes known problems in Release 1 (v1.0.2.2).

1.5.1 Installation Issues

1.5.1.1 Selecting a Locale

To select a locale for Oracle9i Application Server installation, perform the following steps:

  1. On your platform with Common Desktop Environment (CDE), close all open windows.

  2. Log out (right-click your desktop, select Logout, and click OK).

  3. Select the desired locale from the Options menu. For example, a German locale can be chosen as follows:
    Options --> Language --> C to es_BO --> de (German)

  4. Log in (type user name and password).

  5. Open a terminal emulator window.

  6. Type the following command to verify the locale:

    env | grep LANG 
    
    

    The output of this command must include the LANG environment variable. It must have the value selected in Step 3.

    If the LANG environment variable is not shown or is set to a different value, check .profile, .login, .cshrc or other files where the LANG environment variable is set or unset.

    After fixing the problem, repeat these steps, beginning with Step 1.

  7. Install Oracle9i Application Server on your platform.

    The translated files for the selected locale are installed. In addition, English files are always installed.


    Note:

    Check that the LANG environment variable is unset on Linux before installing Oracle9i Application Server. 


1.5.1.2 Manual Setting of Initialization Parameter Required

Some Oracle9i Application Server components may not function correctly when interacting with the Oracle9i database, if the o7_dictionary_accessibility parameter on the database, is set to FALSE. In the Oracle9i database init.ora file, add the following line:

o7_dictionary_accessibility=TRUE

1.5.1.3 Oracle Universal Installer Shows Incorrect Installation Status

The Oracle Universal Installer may display `in progress' status after a component installation is complete. This was observed during installation of the Database Cache and Portal configuration tools, and resolved after canceling the first attempt. On the second attempt, the completed installation was properly reflected in the status display.

1.5.1.4 Install Failure

Before installing Oracle9i Application Server on UNIX platforms, be sure that the environment variables PATH, ORACLE_HOME, and LD_LIBRARY_PATH are not set in any command shell initialization files, such as .cshrc for csh, .bashrc for bash, or $ENV for ksh.

Setting one of these variables in an initialization file could cause the installation of Oracle9i Application Server to fail. Setting one of these environment variables in a login initialization file, such as .profile for sh, .login for csh, .kshrc for ksh, or .bash_login for bash will not affect the installation of Oracle9i Application Server.

1.5.1.5 Errors Opening redo Logs after Installation

After installing the Oracle9i Application Server seed database, you may see the following errors in the user dump location:

ORA-00313: open failed for members of log group 1 of thread 1 
ORA-00312: online log 1 thread 1: '<redo log file_name>' 
ORA-27037: unable to obtain file status

These are not serious errors. The redo logs are created in a future step of the seed database creation.

1.5.1.6 Standard Edition Character Set

The starter database provided as part of the Oracle9i Application Server Standard Edition (SE) installation uses the US7ASCII character set. To change the database character set after installation, connect to the database using sqlplus and issue the statement:

SQL> alter database character set <character set>

For more information, refer to the Oracle8i National Language Support Guide.

1.5.1.7 Root User Login for Installation

When installing Oracle9i Application Server, do not use this command to log in as root user:

$ su

The su command does not set the environment properly, and because of this the installation may fail. Instead, log in as root in a separate session, or use the following command:

$ su -root

1.5.1.8 Configuration Guide for Response Files for Silent Install

There are three Oracle Universal Installer response files, one for each installation option, included on the Oracle9iAS Release 1 (v1.0.2.2) CD-ROM. You will need to edit the response file to suit your installation option.

To use a response file, copy the response file from the Oracle9i Application Server CD-ROM to a drive mounted on your system. They are located on Disk#1 in the /stage/Response directory.

Edit the response file you want to use with any text editor to include information specific to your system. Each file contains instructions for properly configuring the response file.

This document may be used as a reference for editing the response file. It contains relevant sections from the above response files with sample values to proceed with a silent install. These sections are described below:

Total changes needed:

EE installation: 12 parameters plus 7 portal configuration assistant-specific entries

SE installation: 13 parameters plus 7 portal config assistant-specific specific entries

Minimal: 10 parameters plus 7 portal config assistant-specific entries


Note:

The parameter UNIX_GROUP_NAME is "Unix group to be set for the inventory directory." You do not have to enter anything for this value if you specify the inventory location with the installer command line to a local directory.

The parameter FROM_LOCATION_CD_LABEL should only be used in multi-CD installations. Its value is "Oracle9i Application Server 1.0.2.2.0"  


1.5.1.9 All Install Types (Minimal, SE & EE)

Total: 9

[SESSION] 

#Parameter: UNIX_GROUP_NAME 
#Type: String 
#Description: Unix group to be set for the inventory directory. Valid only in 
Unix platforms. 
#Example : UNIX_GROUP_NAME = "install" 
UNIX_GROUP_NAME=<Value Unspecified> 

#Parameter: FROM_LOCATION 
#Type: String 
#Description: Complete path of the products.jar. 
#Example : FROM_LOCATION =
"/net/tools-nfs/inst_ias/solaris/ias10220/production/Disk1/stage/products.jar" 
FROM_LOCATION="/net/tools-nfs/inst_
ias/solaris/ias10220/production/Disk1/stage/products.jar"

#Parameter: FROM_LOCATION_CD_LABEL 
#Type: String 
#Description: This variable should only be used in multi-CD installations. It 
includes the label of
the Compact Disk where the file "products.jar" exists. The label can be found in 
the file
"disk.label" in the same directory as products.jar. 
#Example : FROM_LOCATION_CD_LABEL = "CD Label" 
FROM_LOCATION_CD_LABEL=<Value Unspecified> 

#Parameter: ORACLE_HOME 
#Type: String 
#Description: Complete Location of the Oracle Home. 
#Example : ORACLE_HOME = "C:\OHOME1" 
ORACLE_HOME="/private2/oracle/iasse2" 

[oracle.webdb.apache_3.0.9.8.0] 

#Parameter: user_input2 
#Type: StringList 
#Description: This variable holds the input from dialog2. 
user_input2={"portal30", "portal30", "t816.world"} 

#Parameter: user_input1 
#Type: StringList 
#Description: This variable takes the input from the first dialog. 
user_input1={"portal30_sso", "portal30_sso", "t816.world"} 

[portaltogo.server_1.1.1.0.0] 

#Parameter: SYSTEM_PASSWORD 
#Type: String 
#Description: This will hold the panama SYSTEM user password 
SYSTEM_PASSWORD="manager" 

#Parameter: SRV_USER 
#Type: StringList 
#Description: This will hold the Portal-to-Go User and Password 
SRV_USER={"scott", "tiger"} 

#Parameter: SRV_HOST 
#Type: StringList 
#Description: This will hold the Portal-to-Go host variables 
SRV_HOST={"london.us.oracle.com", "2021", "l816"} 

1.5.1.10 Minimal & SE Install Types Only

Total: 1


[oracle.iappserver.iapptop_1.0.2.2.0] 

#Parameter: startupProcesses 
#Type: StringList 
#Description: StringList of processes to configure and start automatically in 
iAS Installation.  This
variable is used only in Enterprise Edition installs (in other install types, 
all processes are
automatically started).  Possible values that can be included in the StringList 
are the strings 
 "Oracle HTTP Server in Non-SSL mode" , "Oracle9iAS Portal".  If the StringList 
is empty, no
processes are started.  For example, the 
#StringList {""Oracle HTTP Server in Non-SSL mode"",  "Oracle9iAS Portal"} would 
configure
and start up those products. 
startupProcesses={"Oracle HTTP Server in Non-SSL mode" , "Oracle9iAS Portal}

1.5.1.11 SE Install Type Only

Total: 3

[oracle.assistants.dbca_8.1.7.0.0] 

#Parameter: s_globalDBName 
#Type: String 
#Description: Global Database Name 
s_globalDBName="m10ee2.world" 

#Parameter: s_mountPoint 
#Type: String 
#Description: Database file location:  directory for datafiles, control files, 
redo logs. 
s_mountPoint="/private2/oracle/iasee2/dbs" 

#Parameter: s_dbSid 
#Type: String 
#Description: Value that $ORACLE_SID will be set to. 
s_dbSid="m10ee2" 

1.5.1.12 EE Install Type Only

Total: 3

[oracle.iappserver.iapptop_1.0.2.2.0] 

#Parameter: startupProcesses 
#Type: StringList 
#Description: StringList of processes to configure and start automatically in 
iAS Installation.  This
variable is used only in Enterprise Edition installs (in other install types, 
all processes are
automatically started).  Possible values that can be included in the StringList 
are the strings
 "Oracle9iAS Database Cache" , "Oracle9iAS Forms and Reports Services" , "Oracle 
HTTP
Server in Non-SSL mode" , "Oracle9iAS Web Cache", "Oracle9iAS Portal", 
"Oracle9iAS
Discoverer", "Oracle Management Server".  If the StringList is empty, no 
processes are started. 
For example, the 
#StringList {"Oracle9iAS Database Cache" , "Oracle9iAS Forms and Reports 
Services" ,
"Oracle HTTP Server in Non-SSL mode" , "Oracle9iAS Web Cache", "Oracle9iAS 
Portal",
"Oracle9iAS Discoverer", "Oracle Management Server" } 

[oracle.icache.icacheca_1.0.2.2.0] 

#Parameter: sl_dbaReturn 
#Type: StringList 
#Description: Name and Password of SYSDBA user on origin DB. 
sl_dbaReturn={"sys", "change_on_install"} 

#Parameter: sl_connectStringReturn 
#Type: StringList 
#Description: Fields are: Name of origin DB machine, Port number of listener on 
origin (often
1521), Service name of origin DB. 
sl_connectStringReturn={"london.us.oracle.com", "2021", "l816.world"} 

1.5.1.13 For Portal Config Assistant Only (With All Install Types)

Total: 7


Note:

OPCA takes default values for 4 tablespace name parameters, if not specified with the response file. Following are their names and default values. If the defaults are acceptable, you do not need to specify them with your response files.

temporary_tablespace="TEMP"

logging_tablespace="USERS"

document_tablespace="USERS"

default_tablespace="USERS"  


[oracle.webdb_3.0.9.8.0] 

#Parameter: silent 
#Type: Boolean 
#Description: This variable is true if silent mode is on.  It is passed to the 
wwv component. 
silent=true 

[oracle.webdb.apache_3.0.9.8.0] 

#Parameter: opca_tnsconnect 
#Type: String 
#Description: tns connect string which is required by Oracle Portal Config 
Assistant.  This should
be in <machine name>:<port>:<sid> format. 
opca_tnsconnect="london.us.oracle.com:2021:l816" 

[oracle.webdb.wwv_3.0.8.9.8] 

#Parameter: sys_password 
#Type: String 
#Description: System Password for Portal's OPCA 
sys_password="change_on_install" 

#Parameter: temporary_tablespace 
#Type: String 
#Description: Temporary Tablespace for Portal's OPCA 
temporary_tablespace="TEMP" 

#Parameter: logging_tablespace 
#Type: String 
#Description: Logging tablespace for Portal's OPCA 
logging_tablespace="USERS" 

#Parameter: document_tablespace 
#Type: String 
#Description: Document Tablespace for Portal's OPCA 
document_tablespace="USERS" 

#Parameter: default_tablespace 
#Type: String 
#Description: Default Tablespace for Portal's OCPA 
default_tablespace="USERS" 

1.5.1.14 Other Configuration tools

DBCA & Net Configuration Assistant

These tools are run in typical mode while running Oracle9i Application Server silently, so no response files are required.

Oracle9iAS Database Cache Configuration Assistant

This tool's user input is specified with EE response file -2 parameters sl_dbaReturn and sl_connectStringReturn as mentioned above with component [oracle.icache.icacheca_1.0.2.0.0]

Oracle Internet File System Configuration Tool

Use the file template IfsConfig.properties provided with the shiphome. This is a post Oracle9i Application Server installation task. This configuration tool is not run with Oracle9i Application Server installation.

Oracle Management Server

Silent mode is not supported with Oracle9i Application Server 1.0.2 release. It is scheduled for Oracle9i Application Server 2.0.

root.sh Execution

You may set the parameter show_rootsh_confirmation=false and run the root.sh after the installation. You must make sure that /var/opt/oracle/oratab be writable by the owner of the installer process so that the Database configuration Assistant (DBCA) and iCache Configuration Assistant (icacheca) can update the oratab file. Otherwise, DBCA and icacheca will fail during the configuration tool launch phase.

1.5.1.15 Enterprise Edition Response File Sections and Parameters


[SESSION]
#Parameter: UNIX_GROUP_NAME 
#Type: String 
#Description: Unix group to be set for the inventory directory. Valid only in 
Unix platforms. 
#Example : UNIX_GROUP_NAME = "install" 
UNIX_GROUP_NAME=<Value Unspecified> 

#Parameter: FROM_LOCATION 
#Type: String 
#Description: Complete path of the products.jar. 
#Example : FROM_LOCATION = "../stage/products.jar" 
FROM_LOCATION="/private1/balbert/dve/production/Disk1/stage/products.jar" 

#Parameter: FROM_LOCATION_CD_LABEL 
#Type: String 
#Description: This variable should only be used in multi-CD installations. It 
includes the label of
the Compact Disk where the file "products.jar" exists. The label can be found in 
the file
"disk.label" in the same directory as products.jar. 
#Example : FROM_LOCATION_CD_LABEL = "CD Label" 
FROM_LOCATION_CD_LABEL="9iAppServer" 

#Parameter: ORACLE_HOME 
#Type: String 
#Description: Complete Location of the Oracle Home. 
#Example : ORACLE_HOME = "C:\OHOME1" 
ORACLE_HOME="/private1/oracle/iasee1" 

#Parameter: TOPLEVEL_COMPONENT 
#Type: StringList 
#Description: The Toplevel component that has to be installed in the current 
session. 
#The following choices are available. The value should contain only one of these 
choices. 
#The choices are of the form Internal Name, Version : External name. Please use 
the internal
name and version while specifying the value. 
# oracle.iappserver.iapptop, 1.0.2.0.1 : Oracle9i Application Server 1.0.2.0.1 
#Example : TOPLEVEL_COMPONENT = {"oracle.iappserver.iapptop","1.0.2.0.0"} 
TOPLEVEL_COMPONENT={"oracle.iappserver.iapptop","1.0.2.0.1"} 

[oracle.iappserver.iapptop_1.0.2.0.1] 

#Parameter: startupProcesses 
#Type: StringList 
#Description: StringList of processes to configure and start automatically in 
iAS Installation. This
variable is used only in Enterprise Edition installs (in other install types, 
all processes are
automatically started). Possible values that can be included in the StringList 
are the strings:
"Oracle Database Cache" , "Forms and Reports Server" , "Oracle HTTP Server (on 
port 7777)" ,
"Oracle Web Cache", "Oracle Discoverer 3i Viewer", "Oracle Portal", "Oracle 
Management
Server". If the StringList is empty, no processes are started. For example, the 
#StringList {"Oracle Database Cache","Forms and Reports Server"} would configure 
and start
up those products. 
#Possible Values are { "Oracle Database Cache" , "Forms and Reports Server" , 
"Oracle HTTP
Server (on port 7777)" , "Oracle Web Cache" , "Oracle Discoverer 3i Viewer" , 
"Oracle Portal",
"Oracle Management Server" } 
#But Following 4 config tools doesn't support silent modes: 
#1. "Oracle Web Cache" , 2. "Oracle Portal", 3. "Oracle Database Cache" , 4. 
"Oracle
Management Server" 

startupProcesses={"Forms and Reports Server" , "Oracle HTTP Server (on port 
7777)" , "Oracle
Discoverer 3i Viewer" } 

[oracle.webdb.apache_1.3.12.0.0a] 

#Parameter: user_input2 
#Type: StringList 
#Description: This variable holds the input from dialog2. 
user_input2={"portal30", "portal30", "t816.world"} 

#Parameter: user_input1 
#Type: StringList 
#Description: This variable takes the input from the first dialog. 
user_input1={"portal30_sso", "portal30_sso", "t816.world"} 

[portaltogo.server_1.0.2.2.0] 

#Parameter: SYSTEM_PASSWORD 
#Type: String 
#Description: This will hold the panama SYSTEM user password 
SYSTEM_PASSWORD="manager" 

#Parameter: SRV_USER 
#Type: StringList 
#Description: This will hold the Portal-to-Go User and Password 
SRV_USER={"scott", "tiger"} 

#Parameter: SRV_HOST 
#Type: StringList 
#Description: This will hold the Portal-to-Go host variables 
SRV_HOST={"toronto.us.oracle.com", "2021", "t816"} 

[oracle.icache.icacheca_1.0.2.0.0] 

#Parameter: sl_dbaReturn 
#Type: StringList 
#Description: Name and Password of SYSDBA user on origin DB. 
sl_dbaReturn={"sys", "change_on_install"} 

#Parameter: sl_connectStringReturn 
#Type: StringList 
#Description: Fields are: Name of origin DB machine, Port number of listener on 
origin (often
1521), Service name of origin DB. 
sl_connectStringReturn={"toronto.us.oracle.com", "2021", "t816.world"} 

1.5.1.16 OracleJSP Error

In HTTP Server and Standard Edition installations, the following OracleJSP error occurs when accessing Accessories from Browse Categories:

Error:

Request URI:/onlineorders_html/srch_results.jsp 

Exception:

oracle.jsp.parse.JspParseException: Line # 7, Error: Unable to find 
class for bean: parms defined by tag with class: 
jspclient.processParms 

To resolve the error, rename the JspClient directory to jspclient (all lower case). The directory is located in

$ORACLE_HOME/Apache/Apache/htdocs/onlineorders_html/

1.5.1.17 Oracle9iAS Database Cache Installation Errors

If the listener for the origin database is not properly configured, the following errors may occur when you attempt to install Oracle9iAS Database Cache:

Adding users to the cache failed. 
Reason: WTE-03501 Error updating list of users: Export failed on origin database 
OCI error - ORA-28575: unable to open RPC connection to external procedure agent

Refer to the Oracle9i Application Server Installation Guide for detailed instructions ON configuring the listener for the origin database.

1.5.1.18 Oracle9iAS Database Cache Configuration

When you install Oracle9i Application Server Enterprise Edition, you can choose whether to configure Oracle9iAS Database Cache during the installation or at a later time. If you choose to configure Oracle9iAS Database Cache during the installation, the installation procedure uses default values for the following Oracle9iAS Database Cache attributes:

If you want to specify values other than the default values, you can choose not to configure Oracle9iAS Database Cache during the installation. After the installation completes successfully, invoke the Oracle9iAS Database Cache Configuration Assistant using the following command:

prompt> $ORACLE_HOME/bin/wtacca -create -custom

For more details, refer to the Configuration Assistant online help.

1.5.1.19 Preserving Changes to Oracle HTTP Server Configuration on Re-installation in Same Oracle Home

Be sure to save copies of httpd.conf, jserv.conf, zone.properties, and any Oracle HTTP Server configuration files that you have changed. When you re-install Oracle9iAS into the same Oracle home, existing configuration files are overwritten with the newly installed files.

1.5.1.20 Apache Configuration Error Upon Installation

When installing Oracle9i Application Server Enterprise Edition, if you have installed Apache previously in the same ORACLE_HOME, Apache configuration fails with the following error:

Syntax Error on line 14 of
<ORACLE_HOME>/Apache/Apache/conf/mod__ose.conf 
Aurora Service - directive already effect for this server 
<ORACLE_HOME>/Apache/Apache/bin/httpdsctl start: httpd could not be
started 

To work around this error:

  1. Remove the double entry of mod__ose.conf in the file $ORACLE_HOME/Apache/Apache/conf/oracle_apache.conf.

  2. Restart your Oracle HTTP Server, using the following command:

    prompt>$ORACLE_HOME/Apache/Apache/bin/apachectl start
    

1.5.1.21 Automatic Class Reloading of JSPs Error

The Oracle9i Application Server installation adds the following extra entry to the $ORACLE_HOME/Apache/Jserv/etc/jserv.properties file:

wrapper.classpath=$ORACLE_HOME/Apache/Apache/htdocs/_pages

After installation, you need to delete this line and restart Oracle HTTP Server. Otherwise, automatic class reloading of JavaServer Pages (JSPs) will not work correctly.

1.5.1.22 Configuration Assistant Failure with Standard Edition Default Large Pool Size

During Oracle9i Application Server Standard Edition install, if you choose to install the Oracle9iAS Portal database objects into the newly created 8.1.7 Standard Edition database, the install fails because the default large_pool_size is not big enough. To increase the default large_pool_size before running the Oracle9iAS Portal Configuration Assistant, use the following workaround:

  1. Shut down the database.

  2. Double the size of the large_pool_size parameter in the init.ora file.

  3. Restart the database.

  4. Run the Oracle9iAS Portal Configuration Assistant.

Alternatively:

  1. Drop the old Oracle9iAS Portal user.

  2. Shut down the database.

  3. Double the size of the large_pool_size parameter in the init.ora file.

  4. Restart the database.

  5. Run the Oracle9iAS Portal Configuration assistant from the ORACLE_HOME located at $ORACLE_HOME/assistants/opca/launch.sh.


    Note:

    This problem does not occur if you install to a remote 8.1.6 database and has only been observed in a Standard Edition install. 


1.5.1.23 Response File Variable Settings for Oracle9iAS Portal Silent Install

If you wish to perform a silent install of Oracle Portal, you must set the certain variables in the response file. The variables are shown below, with sample values for each component. Note the following exceptions:

1.5.1.24 Web Cache Configuration Assistant Appears When Not Selected

The Web Cache Configuration Assistant starts after installation even if it is not selected in the configuration window.

1.5.1.25 Silent Installation of Oracle9i Application Server Wireless Not Supported

Silent installation for Oracle9i Application Server Wireless is not supported; it requires entry of information specific to Wireless and manual editing of configuration files.

1.5.1.26 JServ.conf Addition

If you are upgrading from the previous release of Oracle9i Application Server Wireless, you must make the following changes to the jserv.conf file, located at:

$ORACLE_HOME/Apache/Jserv/etc/jserv.conf

  1. Comment out ApJServMount /ptg /root

  2. Insert the following:

    # PTG 1.1.1 Begin
    ApJServGroupMount /ptg balance://group1/root
    # PTG 1.1.1 End
    
    

If you are doing a new installation of Oracle9i Application Server Wireless, insert the following:

# PTG 1.1.1 Begin
ApJServGroupMount /ptg balance://group1/root
# PTG 1.1.1 End

1.5.1.27 RDBMS Patch Install Dialog Appears

When you install Oracle9iAS Enterprise Edition, the following RDBMS patch installation dialog may appear:

"You have enabled the ORATAB_FAIL feature by setting the environment variable 
ORATAB_FAIL to TRUE. This will allow you to continue installation eventhough 
there is no write permission on ORATAB (/var/opt/oracle/oratab) file. 
Currently ORATAB file does not exist, or is not writtable by the user. You can 
run the orainst/oratab.sh script as the root user to create the file or modify 
its permissions. In that case select [Shell] to invoke a new window from which 
to run the oratab.sh script, or exit the installer and restart it after 
oratab.sh has been run. 
If you decide to continue without changing the ORATAB permissions, select OK. 
But this installation session will not update ORATAB file and OCSM 
functionalities may not work properly. However running root.sh in the end will 
update the ORATAB file."

Select OK to continue with the installation. You do not need to start a shell or run any scripts, as suggested in the dialog.

1.5.1.28 Oracle Forms, Reports and Discoverer Patch Installation

When installing a patch, use <IAS_HOME>/6iserver as your ORACLE_HOME for Forms, Reports and Discoverer products, where <IAS_HOME> is the ORACLE_HOME used for Oracle9iAS.

1.5.2 Deinstallation and Migration Issues

1.5.2.1 Deinstalling Oracle9iAS Database Cache with OUI Removes Dependent Components

If you use Oracle Universal Installer to deinstall Oracle9iAS Database Cache, all services are also deinstalled. To deinstall Oracle Database cache, use the following processes:

  1. Ensure that the cache is started. If necessary, start it with the Cache Manager or the cachstrt script in the $ORACLE_HOME/bin directory.

  2. Run the Database Cache Configuration Assistant, specifying the -deinstall option:

    prompt>wtacca -deinstall
    

1.5.2.2 OraInventory Directory Requires Backup Before Migration

Before running the migration process in the Oracle Universal Installer, you must back up the OraInventory directory.

If migration fails or is cancelled in progress, subsequent attempts might also fail because of changes the installer made to the OraInventory directory. After any incomplete migration process, restore the OraInventory directory from your pre-migration backup before attempting migration again.

1.5.2.3 Error When Starting Oracle HTTP Server

The following error may occur when you start the HTTP Server after de-installation and re-installation of Oracle9i Application Server into the same Oracle home:

Syntax error on line 14 of <ORACLE_HOME>Apache/Apache/conf/mod_ose.conf:
AuroraService - directive already in effect for this server

To resolve this error, perform the following steps:

  1. Open the <ORACLE_HOME>Apache/Apache/conf/oracle_apache.conf file.

  2. Remove the duplicate of the following line:

    include "<ORACLE_HOME>Apache/Apache/conf/mod_ose.conf:"
    
    
  3. Re-start the HTTP Server.

1.5.2.4 Upgrading Oracle9i Application Server Wireless

You can only upgrade to Oracle 9i Application Server Wireless 1.1.1.1 (on Oracle9i Application Server 1.0.2.2.0) from Oracle 9i Application Server Wireless 1.1 (on Oracle 9i Application Server 1.0.2.1.0).

If you are migrating from earlier releases, you must first upgrade to Oracle 9i Application Server Wireless 1.1 (on Oracle 9i Application Server 1.0.2.1.0), then up to this current release.

1.5.2.5 Reinstallation of Oracle9i Wireless

During Oracle9i Application Server Wireless installation, a Wireless repository is created.

Deinstallation of Oracle9i Application Server Wireless DOES NOT automatically remove the database schema. Therefore, if you reinstall Oracle9i Application Server Wireless (using the same database user name as you did in the previous installation) after deinstalling the software, you must MANUALLY remove the database schema. Before you remove the database schema, backup the data under the database schema appropriately. One way to remove the database schema is to delete the Wireless database user.

For example: if during installation, you have specified panama as the Wireless repository owner, perform the following steps:

  1. Launch SQLPLUS connected as System user (or other user with DBA privileges).

  2. Use the following SQLPLUS commands to remove the repository owner:

    SQLPLUS> drop user panama cascade
    SQLPLUS> commit
    SQLPLUS> exit
    

1.5.2.6 Upgrading Oracle9iAS Wireless Schema from Oracle8i Database to Oracle9i Database

If you upgrade from Oracle8i database to Oracle9i database AFTER this maintenance release is installed, run:

migrate_8i_to_9i.sql

against your database, connecting with proper user name, password and schema name.

1.5.2.7 SOAP Release Notes and Documentation Link Inactive

After upgrading or migrating from Release 1 ( v1.0.2) or Release 1 (v1.0.2.1) to Release 1 (v1.0.2.2), the link on the index.html page titled "SOAP Release Notes and Documentation" does not work.

To resolve this problem:

  1. Add the following directive to the ORACLE_HOME/Apache/Apache/conf/httpd.conf file:

    Alias /soapdocs/ "ORACLE_HOME/soap/"
    
    

    (where ORACLE_HOME is the full path to your Oracle home directory).

  2. Restart the server.

1.5.2.8 nmxw.ora Instantiation Required After Migration

After you have migrated from Oracle9iAS Release 1 (v1.0.2.0.1) or Release 1 (v1.0.2.1) to Release 1 (v1.0.2.2), you must manually instantiate the nmxw.ora file to populate the values for the web server directives ServerRoot, ConfigFile, and ApacheVersion. If these are not populated, the Enterprise Manager Console cannot detect the HTTP Server.

The file's path is ORACLE_HOME/network/agent/config/.

1.5.3 Internet Applications Solution Area Issues

1.5.3.1 Oracle HTTP Server powered by Apache

1.5.3.1.1 Global Server IDs for Oracle HTTP Server powered by Apache

You can use Global Server IDs to legally upgrade an export-level browser to use high grade encryption (128 bit) if the Apache server contains an appropriate GS-ID certificate and the browser has been patched to accept a GS-ID certificate. While all browsers are shipped with high encryption, it is disabled for export products. Note that with the recent change in US export laws, using GS-ID will not be necessary in the future; for now, however, if you have an export grade browser and require a high level of encryption, follow the steps below to obtain a GS-ID certificate and enable your browser:

  1. Buy a GS-ID Certificate.

    Obtain a GS-ID certificate from an appropriate vendor. Oracle has tested the GS-ID certificate from Verisign. For more information on this, visit the following web-site:

    http://www.verisign.com/server/prd/g/index.html
    
    

    Follow the instructions for downloading and saving the certificate on your server. After obtaining the certificate, the Oracle HTTP Server administrator must update the httpd.conf file. The lines to update are:

    SSLCertificateFile <pathname>/gsid.crt 
    SSLCertificateKeyFile <pathname>/gsid.key
    SSLCertificateChainFile <pathname>/gsidintermediate.crt

    where pathname is the fully qualified path to the installed Verisign file(s).

  2. Buy the Browser Patch.

    Obtain a patch that will allow your browser to upgrade the encryption method. You can obtain browser patches from Apache, and Fortify. Their web-sites are:

    http://www.apache.org
    http://www.fortify.net/intro.html
    
1.5.3.1.2 Oracle Demo Certificates Replacement

Oracle Demo certificates (dummy certificates) are included with the Oracle HTTP Server powered by Apache build so that the server may be tested in a non-production mode. Before going to production mode, you MUST replace the Oracle Demo certificate with a real certificate.

1.5.3.1.3 Errors Starting Oracle HTTP Server powered by Apache with "APCHECTL -START" When Using Virtual Hosts

If the port number directive and the NameVirtualHost directive ports do not match, this error will occur. To resolve this issue, make sure that both the port and NameVirtualHost are set to the same port. This can also be resolved by not specifying a port number in the NameVirtualHost directive.

This problem occurs when starting without SSL only.

1.5.3.1.4 Increasing Memory for Apache JServ Applications

If the Apache JServ log or the browser report an "Out Of Memory" condition, the cause is most likely to be that the JVM ran out of memory. This normally happens when data handled by the JVM exceeds its memory allocation pool.

To increase the maximum size of the memory allocation pool for a JVM, use the following steps:

  1. Add this line to
    $ORACLE_HOME/Apache/Jserv/conf/jserv.properties:

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

    where <size> is the size, in megabytes, of the memory allocation pool. The default value is 1 megabyte of memory. Oracle recommends that you use a size of 128 megabytes. To set the value to 128 megabytes, add the following line:

    wrapper.bin.parameters=-mx128m
    
    
  2. Restart the Web server after this change so that it can take effect.

1.5.3.1.5 HTTP Server Stops Responding After Prolonged Use of mod_plsql

Intermittently, the HTTP Server stops responding within two to three days after prolonged use of mod_plsql.

To resolve this issue, restart the HTTP Server.

1.5.3.1.6 mod_plsql Requirement

To use the mod_plsql module against a given back-end database, you need to manually install the Oracle PL/SQL Web ToolKit (OWA PL/SQL packages) on the back-end database. The OWA PL/SQL packages should be installed into the SYS database schema; make sure that you have only one installation of the OWA PL/SQL packages. Note that existing Oracle Application Server (OAS) customers upgrading to the Oracle9i Application Server have an older version of these packages that must be replaced.

For more information, see Using the PL/SQL Gateway in the Oracle9i Application Server Documentation Library. Or, you can access the online documentation available at http://hostname.domain:port/pls/admin_/title.htm.

1.5.3.1.7 mod_plsql Caching Error

If mod_plsql caching is not working properly, remove the final slash from the two cache_dir entries in
$ORACLE_HOME/Apache/modplsql/cfg/cache.cfg.

1.5.3.1.8 Restoring Oracle Application Server OWA Packages

When you install the new mod_plsql OWA packages, it places them in the SYS database schema. This can create problems with Oracle Application Server applications using the PL/SQL cartridge. If you experience these problems and want to continue to use your Oracle Application Server PL/SQL cartridge applications, you must recreate the synonyms that reference the Oracle Application Server OWA packages.

To create these synonyms on the origin database machine, perform the following steps:

  1. Connect to the origin database as the SYS user in SQL*Plus.

  2. Run the following commands in SQL*Plus. This drops all of the OWA public synonyms created during the Oracle9i Application 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 "oas_public" OWA package installation schema.

  4. Ensure that the user schema has "CREATE PUBLIC SYNONYM" privileges. If it does not, grant these privileges to the user schema before continuing with the next step.

  5. Run the following commands in SQL*Plus. This recreates the OWA public synonyms so that they reference the Oracle Application Server OWA packages.

    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;
    
    
1.5.3.1.9 Manual Installation of OWA Packages Causes Error

If the OWA packages are installed manually in <$ORACLE_HOME>Apache/modplsql/owa, a "File not found" error occurs.

To resolve the error:

  1. Open the file <$ORACLE_HOME>Apache/modplsql/owa/owacomm.sql.

  2. Change the line

    spool ..\..\portal30\admin\plsql\owa\owaldscr.sql
    
    

    to

    spool owaldscr.sql
    
1.5.3.1.10 Executing the owaload.sql script

To make the owaload.sql script run correctly, you must always execute it in <ORACLE_HOME>/assistants/opca/. An error occurs if you execute it in <ORACLE_HOME>/Apache/modplsql/owa/.

1.5.3.1.11 Known Issue in Upgrading from 8.1.7.0 to 8.1.7.1

If you are running Oracle9i Application Server-based mod_plsql applications (such as Oracle Portal), the upgrade to 8.1.7.1 will reinstall the default OWA packages provided with the database. These packages are older than those provided withOracle9i Application Server/Oracle Portal and will cause issues while running some components of Oracle Portal.

See Also:

Bug no. 1745320 

To get around this problem, reinstall the OWA packages from the Oracle9i Application Server shiphome at the end of the upgrade.

If you have not yet upgraded to 8.1.7.1,an alternative workaround is:

  1. Edit the file $ORACLE_HOME/rdbms/admin/catproc.sql

  2. Comment out the @@owacomm.sql line.

    The OWApreserves the packages already loaded in the database from Oracle9i Application Server.


    Note:

    If you reinstall the OWA packages, you should recompile all dependent objects that are invalidated. 


1.5.3.1.12 mod_rewrite Security Vulnerability

A security vulnerability is present in mod_rewrite that allows certain rules to offer access to any file on the Web server. To avoid these problems, rewrite rules should always map to a full URL rather than mapping directly to a file.

For example, if you have a Web server where DocumentRoot is set to /webroot, do not use:

RewriteRule /foobar/(.*)  /webroot/myfiles/$1 

which directly maps the request to a file-system location. Rather, use a rule such as:

RewriteRule /foobar/(.*) http://myserver.mydomain.com/myfiles/$1 

which restricts access to files that are accessible by the Apache instance (that is, files under the DirectoryRoot directory tree).

1.5.3.1.13 No Support for CA Facilities of OpenSSL

The Certifying Authorities (CA) facilities of OpenSSL are not supported and should not be used. Oracle9i Application Server has moved to the Certicom SSL stack, which does not include the CA features of SSL. You should use the openssl command only for generating certificate requests. Other functionality such as examining certificates, signing certificates, are not supported by Oracle.

1.5.3.1.14 mod_ssl Limitations

Symmetric encryption algorithms RC2, RC5, IDEA are not supported in Release 1 (v1.0.2.2).

1.5.3.1.15 mod_oprocmgr Documentation Incorrect

Using mod_oprocmgr with mod_jserv in the Oracle9i Application Server Documentation Library (Part No. A90282-01) refers to a status handler that is not completely functional. The items below enclosed in quotation marks should be deleted from the document to reflect the current functionality of mod_oprocmgr:

Page 2, System Administration section:

"mod_oprocmgr provides a status handler which displays process information stored in shared memory."

Page 3, Changes to httpd.conf section:

"<Location /oprocmgr-status>

SetHandler oprocmgr-status

</Location>"

Page 4, Changes to jserv.properties section:

"or

port=8007 9000-9010 8010"

Page 7, Checking JServ Process Status section:

"The directive shown in "Changes to httpd.conf" includes a status handler that enables you to monitor JServ processes managed by mod_oprocmgr. You can access the status handler at http://myhost:port/oprocmgr-status, and display a page similar to that shown below."

The screen capture should also be removed because it shows buttons that are not functional.

"If there are zeroes instead of port numbers in the Process Port column, it could be that the JServ processes have not yet registered with the process manager. If you refresh the browser window and the port numbers still do not appear, then the JServ processes were unable to start (possibly because the specified ports were unavailable). Ensure that the specified ports are free, and that you have allotted enough port numbers for the JServ processes. To determine the cause of errors, see jserv.log and mod_jserv.log."

1.5.3.1.16 HTTP Server Insfrastructure Watcher May Suspend JVM

The infrastructure contains a watcher component that monitors the automatically started JServ processes. If a JServ process stops responding, the watcher terminates it and starts another process to replace it. If the JVM is heavily loaded or performing garbage collection, the JVM will also be suspended. To prevent the JVM from terminating, increase its timeout value (ApJServVMTimeout) in the jserv.conf file, or decrease the JVM heap size to reduce garbage collection time.

1.5.3.1.17 Valid Servlet Requests Fail on Second Request Using Same URL

If a valid servlet is requested once, and then requested again, using the URL-encoded version of the servlet's URL, the second request may fail with an error logged in the Apache error_log.

For example, the second URL in the example below may cause an HTTP error:

http://mysite/demo/basic/hellouser/hellouser.jsp
http://mysite/demo/basic/hellouser/hellouser%2ejsp

The server will continue to run, and the unencoded version of the URL continue to function properly.

The workaround is to use the encoded version of each URL or use the unencoded version of each URL. If it is necessary to use both, use the encoded version before using the unencoded version (for each run of the server).

1.5.3.1.18 DMS Clients Require Configuration Change

DMS clients, including flexmon, oasomo, ohsTree, and EMD require a small configuration change to soap.properties in order to operate properly. The SOAP server (and every process group with its own JServ properties file) must contain a zone called "root". DMS clients use this zone to retrieve performance metrics.

To add the "root" zone to the soap.properties file, perform the following steps:

  1. Open the %ORACLE_HOME%/Apache/Jserv/etc/ jservSoap.properties file and change the line that looks like this:

    zones=soap 
    
    

    to this:

    zones=soap,root 
    
    

    Following the line that looks like this:

    soap.properties=%ORACLE_ \ 
    HOME%/soap/webapps/soap/WEB-INF/config/soap.properties
    
    

    Add the line:

        root.properties=%ORACLE_HOME%/Apache/Jserv/etc/zone.properties 
    
    

    (replace %ORACLE_HOME% with your expanded ORACLE_HOME environment variable)

  2. Restart the server.

  3. To test, use this URL (replace mysite with the hostname:port of your site):

    @  http://mysite/dms/AggreSpy 
    
    

    The first access to the URL may indicate that some metrics are not available, but subsequent accesses should return valid metric values. If the server is not configured correctly, the URL will cause long timeout delays, errors in the Apache error_log file, and error responses to the HTTP request.

1.5.3.1.19 LANG Environment Variable in JServ

The LANG environment variable specifies the default locale for application programs. To make servlets and JSPs work in non-English locales, perform the following after installing Oracle9iAS, and before starting the Oracle HTTP Server:

Open $ORACLE_HOME/Apache/Jserv/etc/jserv.properties file so that the default locale of the Java VM running the Servlets and JSPs can be initialized corresponding to the LANG environment variable.

#wrapper.env.copy=LANG
1.5.3.1.20 HTTP Server Timeouts Under Heavy Load

When the Oracle HTTP Server is under heavy load, requests may time out, resulting in incomplete transmission of large (over 10 MB) static files. To correct this, increase the value of TimeOut directive in httpd.conf.

1.5.3.2 Oracle9i Application Server Forms Services

1.5.3.2.1 Graphics Builder Environment Variable Must Be Set on UNIX

To make Graphics integration work, set the following environment variables:

setenv PRINTER <printer name>
setenv TK2_PRINT_STATUS echo
1.5.3.2.2 JInitiator 1.1.7.31 HTTP(S) Limitations

Oracle9i Application Server Release 1 (v1.0.2.2) ships with JInitiator 1.1.7.31. This JInitiator release does not work using HTTP(S) communication for Oracle9iAS Forms Services because of a missing DLL. To enable HTTP(S) communication with Oracle9iAS Forms Services, download the latest JInitiator from the Oracle Technology Network (OTN) at:

http://technet.oracle.com/products/forms

Click the Software tab and select the latest JInitiator posted, Release 1.1.7.32 or later.


Note:

This release of Oracle9iAS Forms Services (6.0.8.11) has not been tested with releases of JInitiator earlier than 1.1.7.31. 


1.5.3.2.3 Internet Explorer 5.0 Native JVM Limitations

Oracle9iAS Forms Services provides a signed CAB file to enable bronze support for Internet Explorer 5.0 running the native JVM (Java Virtual Machine). This support requires that the HTTP(S) Forms Server and Web listener run on the same machine.

The following are current limitations when running with Internet Explorer 5.0 and the native JVM:

For the latest information about the current level of client support and HTTP(S) restrictions, refer to the Client Platform Statement of Direction document at:

http://technet.oracle.com/products/forms
1.5.3.2.4 Oracle9iAS Forms Services non-SSL Listener Requirement

Oracle9iAS Forms Services requires that Apache be listening on at least one port in non-SSL mode, because Oracle JInitiator cannot download the Forms Applet via SSL.

1.5.3.2.5 Oracle 9iAS Forms/Enterprise Manager Limitations

A patch is available on ARU and Metalink to resolve the following problems:

Bug 1286040, version 2.1 - NLS: Multibyte characters in Forms Listener Process Log are corrupted.

Bug 1544477, version 6.08.11.3 - Event de-registering causes Error VD-1525.

Bug 1554211, version 2.2 - Forms event fails with database version 8.1.7.

Bug 1562864, version 2.1 - Oracle Agent cannot discover Forms servers in multiple Oracle homes on the same server.

Bug 1562887, version 2.1.0.1.0 - Multiple SIDs will not start the Forms listener from Oracle Enterprise Manager.

1.5.4 Portals Solution Area Issues

1.5.4.1 Oracle9i Application Server Portal

1.5.4.1.1 Cannot Install Reports Scripts Into Multiple Instances of Oracle9iAS Portal in Same Database

If you upgrade to Release 1.0.2.2 from an earlier version of Oracle9i Application Server, but do not upgrade Oracle9iAS Portal to version 3.0.9, you will not be able to install reports scripts into multiple instances of Oracle9iAS Portal.

1.5.4.1.2 High Load on Portal Pages Causes Core Dump

Under high load (in testing with 500 clients), a Portal page causes a core dump in the database. The remedy is to increase the database shared pool size.

1.5.4.1.3 Report Output Requirement

To schedule a report page in Oracle9iAS Portal, you must specify the output folder name and the status folder name in the Schedule Report Page dialog box. If you do not specify these names, the report output will not display in the content area for which the report component is defined.

1.5.5 Wireless Solution Area Issues

1.5.5.1 Oracle9i Application Server Wireless

1.5.5.1.1 Adapters

To address language-encoding issues, new optional input parameters have been added:

1.5.5.1.2 Transformers

The HDML, TINY_HTML and WML1.1 transformers have been modified. These modified transformers will NOT be loaded into the Repository by default.

If you HAVE NOT made changes to the transformers, upload up11-111.xml.

If you have modified the shipped version of these transformers: perform the following steps:

  1. Merge the differences.

  2. Upload the new transformers using the LoadXML utility.

    You can use upload.bat/or upload.sh, depending on your hardware platform, with up11-111.xml shipped with the patch release. You can find the upload.bat/or upload.sh script file in panama/sample under ORACLE_HOME. Refer to Oracle9i Application Server Wireless Edition Configuration Guide for more information on the LoadXML utility.

1.5.5.1.3 New Search/Sort Feature Introduced into Service Designer

When you right click on the Master Services node or a folder node, you will find a Search/Sort command. You can search on service names (service names are case-insensitive); wild cards (such as '%') are accepted. Search results can be sorted by Name, LastUpdated Date, or Sequence Number.

The new Search feature is more efficient when you are trying to load a large number of services.

The search results will be the new child nodes of the folder which will be automatically expanded. After you collapse the folder and re-expand it, all of its children will be loaded by default. In either case, if the result set is too large and surpasses the limit size specified in ptgsd.properties, you will receive a warning, and only part of the result set will be loaded. In this case, if your expected service is not displayed, you must fine tune your search criteria and reaccomplish the search.

1.5.5.1.4 Debug

Sending the PAdebug=1 flag as part of a query string will not, by itself, enable the debugging capability. The login user for the current session must be either a Designer or an Administrator.

See Also:

For information on how to create a Designer or an Administrator, refer to Oracle9i Application Server Wireless Edition Implementation Guide. 

1.5.5.1.5 Test Wizard

To use the Test Wizard inside the Service Designer, you must have the Designer role. Otherwise, only the device result will be displayed when a service is being tested.

1.5.5.1.6 JDBC Driver

This release of Wireless Edition only supports the classes12.zip JDBC driver. classes111.zip is no longer supported.

1.5.5.1.7 Supported Devices and Gateways

For a list of certified devices and gateways supported by Wireless Edition, visit the following web-site:

http://docs.oracle.com
1.5.5.1.8 Third Party Location Service Providers

To obtain third party files for using location services in Wireless Edition, see the OTN web site at:

http://docs.oracle.com
1.5.5.1.9 Database Connections

The default database created by the Oracle8i installation may not be tuned properly for your installation. The "ORA-00020: maximum number of processes exceeded errors" message may appear.

To prevent this, ensure that the max_processes database parameter is set high enough, and that the Oracle Net8 dead process detection is configured in your system. Refer to the Oracle8i documentation for more detailed database configuration and performance information.

1.5.5.1.10 Notifications

When using Oracle9iAS Wireless Edition notifications (the AQ Daemon process), if a job terminates with an error, it is removed from the job queue. To continue to use the job, correct the error and reschedule the job.

1.5.5.1.11 Bootstrap Repository Provisioning Service

To use the Provisioning Service in the bootstrap repository, you must set the input parameters of the master service to be User Customizable.

1.5.5.1.12 SQL Adapter Master Services

Numeric input parameter names are not allowed in the master service PL/SQL code.

JDBC connect strings that specify a user name and password are not allowed. The following is an example of an incorrect string:

jdbc:oracle:thin:user/password@hostname:port:sid

The connect string information must be of the form:

jdbc:oracle:thin:@hostname:port:sid

The user name and password must be specified in the User Name and Password fields in the Service Designer.

1.5.5.1.13 Bookmarks in the Personalization Portal

When creating a bookmark in the Personalization Portal, the http:// prefix must be included in the URL, for example:

http://domain_name.com 


Note:

Oracle9iAS Wireless version 1.0.2.2 for Linux Intel does not include this feature. 


1.5.5.1.14 Service Designer Folder Contents Display

This release of Oracle9iAS Wireless allows you to limit the number of objects displayed in the Service Designer navigational tree. To enable this feature, set the number of objects you want to display by editing the ptgsd.properties file.

1.5.5.1.15 Multibyte Character Set Support

To support multibyte character sets in Oracle9iAS Wireless, apply the following configuration changes to your server. The Java Virtual Machine (JVM) bundled with Web Integration Developer and Web Integration Server does not contain the i18n.jar and font.properties files and therefore does not support multibyte character sets.

Perform the following steps on the application server:

  1. Download the internationalized (or localized) version of the Java Runtime Environment (JRE) from the JavaSoft Web site.

  2. Replace the font.properties file of the JVM with font.properties.<locale>.

    The JVM path for the server is:

    %ORACLE_HOME%/panama/WebIntegration/Server/jvm/lib
    
    
  3. Edit the server.sh file to add the following as a Java command line option:

    -Dfile.encoding=< encoding>
    
    

    The path for the server script is:

    %ORACLE_HOME%/panama/WebIntegration/Server/bin/server.sh
    
    

    For example:

    %JDKDIR%/bin/java -Dfile.encoding=SJIS -ms64M -mx256M classpath %CLASSPATH% 
    watt.app.server.Main %1 %2 %3 %4  %5 %6 %7 %8 %9
    
1.5.5.1.16 Multibyte Character Set Support on Client

To support multibyte character sets in Oracle9iAS Wireless, apply the following configuration changes to your client installations. (The Java Virtual Machine (JVM) bundled with Web Integration Developer and Web Integration Server does not contain the i18n.jar or font.properties files and therefore does not support multibyte character sets.)

Peform the following on the Oracle9iAS Wireless client:

  1. Download the internationalized (or localized) version of the Java Runtime Environment (JRE) from the JavaSoft Web site at:

    http://java.sun.com/products/jdk/1.2/jre
    
    
  2. Install the Java Runtime Environment (JRE) from JavaSoft.

  3. Replace the font.properties file of the JVM with font.properties.<locale>.

    The JVM path for the client is:

    %JREDIR%\lib
    
    

For example:

SET JDKDIR=jre1.2\lib

  • Extract the developer.zip file.

    The path for the file is:

    %ORACLE_HOME%\panama\WebIntegration\Developer\lib\developer.zip 
    
    

    Extract the file's content to:

    %ORACLE_HOME%\panama\WebIntegration\Developer\lib\developer\
    
    
  • Edit the developer.bat file.

    The path for the file is:

    %ORACLE_HOME%\panama\WebIntegration\Developer\bin\developer.bat
    
    
    1. Comment out (REM) the following line:

      SET JDKDIR=C:\OraHome1\panama\WebIntegration\Developer\jvm
      
      
    2. Point JDKDIR to the new JRE directory where JRE1.2 is installed, for example:

      REM SET JDKDIR=C:\OraHome1\panama\WebIntegration\Developer\jvm
      SET JDKDIR=jre1.2
      
      
    3. Comment out (REM) the following line:

      SET CLASSPATH="%JDKDIR%\LIB\RT.JAR;%DEVDIR%\LIB\DEVELOPER.ZIP;
      %DEVDIR%\packages\wmroot\code\classes"
      
      
    4. Change DEVELOPER.ZIP to DEVELOPER in the CLASSPATH. For example:

      SET CLASSPATH="%JDKDIR%\LIB\RT.JAR;%DEVDIR%\LIB\DEVELOPER;
      %DEVDIR%\packages\wmroot\code\classes"
      
      
    5. Comment out (REM) the following line:

      "%JDKDIR%\bin\jre" -ms16M -mx32M -classpath %CLASSPATH% 
      watt.app.watt.Main -config "%DEVDIR%\config\developer.cnf" 
      -home "%DEVDIR%" %1 %2 %3 %4 %5 %6 %7 %8 %9
      
      
    6. Add the following line:

      -Dfile.encoding=<encoding>
      
      

      Add the line as a Java command line option, such as:

      "%JDKDIR%\bin\java" -Dfile.encoding=<encoding> -ms16M 
      -mx32M -classpath %CLASSPATH% watt.app.watt.Main -config 
      "%DEVDIR%\config\developer.cnf" -home "%DEVDIR%" 
      %1 %2 %3 %4 %5 %6 %7 %8 %9
      
      

      For example:

      "%JDKDIR%\bin\java" -Dfile.encoding=SJIS -ms16M -mx32M 
      -classpath %CLASSPATH% watt.app.watt.Main -config 
      "%DEVDIR%\config\developer.cnf" -home "%DEVDIR%" 
      %1 %2 %3 %4 %5 %6 %7 %8 %9 
      
    1.5.5.1.17 Images in the Personalization Portal

    To display the images from the Personalization Portal properly, the DISPLAY environment variable in the jserv.properties file must be set properly to configure access the host on which the server runs.

    If the X server runs on the same machine as the Oracle9iAS Wireless server, the DISPLAY environment variable in the jserv.properties file is set by the installation as follows:

    wrapper.env=DISPLAY=localhost:0.0
    
    

    From the X server host machine (x_server_host_name in the following example) run the following command:

    prompt> xhost + <x_server_host_name>
    
    

    If the X server runs on a different machine (x_server_host_name in the following example) than the Oracle9iAS Wireless server, set the DISPLAY environment variable in the jserv.properties file as follows:

    wrapper.env=DISPLAY=<x_server_host_name>:0.0
    
    

    From the X server host machine, run the following command using the Oracle9iAS Wireless host (wireless_edition_host_name in the following example):

    prompt> xhost + <wireless_edition_host_name>
    
    

    For both cases, remain logged into the console while the xhost commands are executed. Otherwise, properties set through the xhost command may be lost and images may not be displayed properly in the Personalization Portal.


    Note:

    Oracle9iAS Wireless version 1.0.2.2 for Linux Intel does not include this feature. 


    1.5.5.1.18 Web Integration Components and JDK

    Web Integration Server requires JDK 1.1. If you experience problems with this component, check the Java settings in the following startup file: %ORACLE_HOME%\panama\WebIntegration\Server\bin\server.bat. In some cases, Oracle 8.1.6 on Windows NT modifies a machine's Java environment. As a result, Oracle9iAS Wireless Web Integration Developer may generate error messages or fail to start. To fix the problem, either restore your original Java environment by reinstalling Java, or verify that the Web Integration Developer starts with the JVM from the 8.1.6 installation. To do this, modify the following file:

    %ORACLE_HOME%\panama\WebIntegration\Developer\bin\developer.bat
    
    

    Change the line:

    SET JDKDIR=%ORACLE_HOME%\panama\WebIntegration\Developer\jvm
    
    

    to:

    SET JDKDIR=%ORACLE_HOME%\jre\1.1.7
    
    1.5.5.1.19 Failed to Load Large XML File from Service Designer in Oracle9i Application Server Wireless

    A problem has been discovered concerning corruption of some XML stylesheets (especially in large files) when they are loaded from ServiceDesigner. It is caused by the XML Parser. A patch has posted at:

    tcpatch:/u01/patch/xdkpatches/bug1736840
    
    

    This directory contains three files: README, changed_classes.zip and a new xmlparserv2.jar. The readme file inside the patch directory contains more detailed information about the nature of the problem.

    To apply the patch, copy xmlparserv2.jar to $<ORACLE_HOME>/lib.

    1.5.5.1.20 Personalization Portal

    The PAPz-based personalization portal released before Oracle 9i Application Server Wireless Edition 1.1 is being officially deprecated in the Oracle 9i Application Server 1.0.2.2.0 release, and will be totally de-supported in the next (2.0) production release. The portal-based personalization portal will be the preferred personalization portal and will be the only supported personalization portal in the next production release.

    1.5.6 Caching Solution Area Issues

    1.5.6.1 Oracle9iAS Database Cache

    1.5.6.1.1 Using Oracle9iAS Database Cache with Servlets

    To access data cached in the middle tier using servlets, you must enable Oracle9iAS Database Cache by setting the ORA_OCI_CACHE environment variable in the servlet environment. Add the following line to the jserv.properties file in the $ORACLE_HOME/Apache/Jserv/etc directory:

    wrapper.env=ORA_OCI_CACHE=1 
    
    

    In addition, the TNS_ADMIN environment variable must be set to the location of the local network configuration. By default, the value is $ORACLE_HOME/network/admin. Add the following additional line to jserv.properties:

    wrapper.env=TNS_ADMIN=<absolute path to Oracle Home>/network/admin
    
    1.5.6.1.2 loadjava Limitation in Oracle9iAS Database Cache Environment

    Because of known issues with LOB support in the Oracle9iAS Database Cache environment (when ORA_OCI_CACHE is set to 1), the loadjava utility will not work.

    1.5.6.1.3 Changes to tnsnames.ora and init.ora Requirement

    To use the Oracle9iAS Database Cache PL/SQL API, you must connect using a Net8 net service name that is constructed using the service name, not the SID. As a result, the tnsnames.ora and init.ora file shipped with this release of Oracle9i Application Server need to be changed. See the Oracle9iAS Database Cache README file for information about the necessary changes.

    1.5.6.1.4 Oracle9iAS Database Cache Configuration Assistant Failure

    The Oracle9iAS Database Cache Configuration Assistant fails when 'Updating User List' is 96% complete. The following error appears:

    Updating User List 
    Adding users to the cache 
    Adding users to the cache failed. 
    Reason: WTE-03501 Error updating list of users: 
    Export failed on origin database. 
    OCI error - ORA-06520: PL/SQL: Error loading external library 
    ORA-06522: dlopen: cannot load /lib/libc.so 
    ORA-06512: at "SYS.WTCSYS", line 11 
    ORA-06512: at "SYS.WTCSYS", line 66 
    ORA-06512: at line 1 
    Processing failed. 
    
    

    A patch for all Oracle9i Application Server 1.0.2 releases is available to fix this problem. The patch fixes the problem on all Oracle9iAS Database Cache platforms that have an Oracle origin database running on the following UNIX operating systems:

    Follow these steps to apply the patch:

    1. Complete the Oracle9i Application Server installation after the error described above occurs.

    2. Copy wtcsini.plb to the following directory:

      <ORACLE_HOME>/icache/admin
      
      

    Rerun the Oracle9iAS Database Cache Configuration Assistant from the bin directory.

    cd <ORACLE_HOME>/bin 
    wtacca -create -typical "username=sys" "password=your_password" 
    
    

    The Oracle9iAS Database Cache Configuration Assistant completes without errors.

    1.5.6.1.5 Oracle Database Cache Stops Responding When Caching a Table That Contains a Context Index

    Using the dbms_icache.add_table procedure to cache a table that contains a context index will cause Oracle Database Cache to stop responding, or "hang." This will also generate an ORA-600 error in the back-end database. Currently, there is no fix available to resolve this issue.

    1.5.6.1.6 Cache Environment Variable Setting

    A problem with the ORA_OCI_CACHE system environment variable causes mod_plsql to suspend or stop under moderate load. Ensure that this variable is not set when the Oracle HTTP Server is started.

    1.5.6.2 Web Cache

    1.5.6.2.1 Configuration Assumes Incorrect Listener Port

    The default configuration of Oracle9iAS Web Cache assumes that the primary Web listener is listening on port 7777. Oracle HTTP Server chooses the port number to listen on dynamically when installed.

    If the HTTP Server chooses a port other than 7777, Oracle9iAS Web Cache will return an error when trying to access its own port of 1100 because it is unable to connect to port 7777 of the web server.

    To correct this problem, change the port number in the "Application Web Servers" screen of the Web Cache Manager to the port on which the HTTP Server is listening.

    1.5.6.2.2 Oracle9iAS Web Cache Core Dumps if Capacity Parameter Too Low

    If the number of requests processed is much larger than the capacity parameter setting, and most of the requests are made to non-cacheable pages, then the web cache may core dump.

    To remedy this, set the capacity parameter to a number close to the number of requests expected. A core dump did not occur in a test with 400 clients requesting a non-cacheable page, with the capacity parameter set to 400. In the same test, with the parameter set to 30 (the default), a core dump occurred.

    The capacity parameter setting is located in the Application Web Server section.

    1.5.7 Business Intelligence Solution Area Issues

    1.5.7.1 Oracle9iAS Reports Services

    1.5.7.1.1 Reports Service Fails to Start

    If you have set the TNS_ADMIN environment variable or registry key to an alternate value, Oracle9iAS Reports Service may fail to start with an error 186 or REP-0186. Start Oracle9iAS Reports Service from a UNIX command prompt as follows:

    prompt> setenv TNS_ADMIN <IAS_HOME>/6iserver/network/admin
    prompt> <IAS_HOME>/6iserver/reports60_server start
    
    

    replacing <IAS_HOME> with the directory where you installed Oracle9i Application Server. This will force Oracle9iAS Reports Service to use the tnsnames.ora file at <IAS_HOME>/6iserver/network/admin.

    1.5.7.1.2 Oracle9iAS Reports Services Hangs Upon Authentication

    Oracle9iAS Reports Services hangs when users authenticate.

    To improve Reports Portal integration, apply the following patch:
    tcpatch 6_0_8_11_3.

    1.5.7.1.3 Oracle9iAS Discoverer

    1.5.7.1.4 xhost Command Required for Oracle9i Application Server Enterprise Edition for Discoverer

    An XWindow display must be available to the Oracle Discoverer servlet for its graphing and charting functions. After you install the Enterprise Edition, you must grant XWindow permissions to the host named in the DISPLAY environment variable in:

    $ORACLE_HOME/.../Apache/JServ/etc/jserv.properties
    
    

    By default, the DISPLAY variable is the hostname of the machine running Oracle9i Application Server. In order for Apache JServ to function properly, you must log in to the console of the host named in the DISPLAY environment variable and issue the xhost command.

    For example, if Oracle9iAS is installed on the host london, the DISPLAY environment variable setting in jserv.properties will be:

    wrapper.env=DISPLAY=london:0.0
    
    

    You must log in to the console of the host london and issue the following command:

    prompt>/usr/openwin/bin/xhost +london 
    
    

    If you change the value of DISPLAY in jserv.properties to a different host, you must log in to the console of that host and grant it the XWindow permissions.

    For example, suppose 9iAS is installed on the host called london, but the DISPLAY variable in jserv.properties is changed to the host berlin, as shown below:

    wrapper.env=DISPLAY=berlin:0.0

    Before using Apache JServ, you must log into the console of berlin and execute the following command to grant london permission to use berlin as a display:

    prompt>/usr/openwin/bin/xhost +london 
    


    Note:

    Each time the DISPLAY host system is restarted, you must issue the xhost command.  


    1.5.7.1.5 Using Oracle Internet Server (Discoverer3i) and Oracle9iAS Discoverer (Discoverer 4i) Simultaneously

    Oracle Internet Server (Discoverer3i) and Oracle9iAS Discoverer (Discoverer4i) share several common components. To run Discoverer3i and Oracle9iAS Discoverer (Discoverer4i) on the same machine, you must execute the following scripts in the order shown below:

    1. <iAS_HOME>/6iserver/discwb4/util/stopall.sh

    2. <iAS_HOME>/6iserver/discwb33/util/startoad.sh

    3. <iAS_HOME>/6iserver/discwb33/util/startosagent.sh

    4. <iAS_HOME>/6iserver/discwb33/util/startlocator.sh

    5. <iAS_HOME>/6iserver/discwb4/util/startlocator.sh

    1.5.7.1.6 Oracle9iAS Discoverer Patch

    A patch is now available for Oracle9iAS Discoverer. The patch resolves a number of issues and also automates the migration of user preferences from Discoverer3i to Discoverer4i. Apply this patch as part of the process of installing and configuring Oracle9iAS Discoverer.

    You can obtain the patch from Oracle Metalink at:

    http://metalink.oracle.com/
    
    

    or through the usual support channels.

    1. Login to MetaLink.

    2. Click on the `Patches' tab in the left-hand navigation bar. Metalink patch areas have changed, so follow the directions below.

    3. On the new page, click on the link:

    "==> NEW! Click here for ALL Product Patches"

    1.5.7.1.7 Discoverer 3i Viewer Server Fails on Non-Pseudocolor X11

    There is an known issue with ORCA installer running on the X emulator. It happens in the Oracle9i Application Server Enterprise Edition install which launches the ORCA/orainst installer to install Discoverer. The orainst installer has a bug that prevents it from running against some types of X emulators. As a result, orainst does not launch and Discoverer scripts are not installed.

    Exceed for Win32 X Server and Reflection X Server for Win32 will work, if you set the visual to PsuedoColor:

    1. Start the Xconfig program and select "Screen Definition".

    2. Set the "Visual" to PsuedoColor.

    3. Reset the server.

    1.5.8 Management Solution Area Issues

    1.5.8.1 Oracle Enterprise Manager

    1.5.8.1.1 Error Occurs When Expanding JServer Node in Enterprise Manager Navigator Window

    If JServer is installed at a port number other than 2481, the following error occurs when you try to expand the JServer node in the Navigator window:

    org.omg.CORBA INTERNAL (completed=MAYBE)
    
    

    To work around this error, enter the correct JServer port number in the dialog box that appears with the error message.

    1.5.8.1.2 HTTP Server Port Number Not Shown in the Enterprise Manager Navigator Window

    The port number associated with the Oracle HTTP Server does not appear in the Navigator window.

    To correct this problem, edit httpd.conf to remove any spaces or tabs at the beginning of comment lines. The comment symbol # must appear in the first column of the line, or the Oracle HTTP Server will not strip out comment lines correctly.

    1.5.8.1.3 Java Exception Occurs When Editing HTTP Server from Enterprise Manager

    A Java exception occurs if you try to edit the Oracle HTTP Server from the Enterprise Manager console, due to a logic error in parsing the httpd.conf file.

    To correct this problem, edit httpd.conf to remove any spaces or tabs at the beginning of comment lines. The comment symbol # must appear in the first column of the line, or the Oracle HTTP Server will not strip out comment lines correctly.

    1.5.8.1.4 Direct Connect Not Supported for Web Servers

    The Direct Connect feature of Performance Manager is not supported for web servers. An error occurs if you attempt to use the Direct Connect feature with the web server. There is no workaround.

    1.5.9 E-Business Integration Solution Area Issues

    1.5.9.1 Oracle9i File System

    1.5.9.1.1 Configuring Oracle9i File System and Oracle9iAS Email to run on the same machine

    The Oracle Internet File System e-mail component and the Oracle9iAS Email both use Sendmail for mail transfer.

    Oracle Internet File System requires Sendmail version 8.9.3 or later and Oracle9iAS Email requires Sendmail version 8 or later. Oracle Internet File System ships an open source version of Sendmail 8.9.3 for UNIX platforms.

    To run the Oracle9iAS Email and Oracle Internet File System on the same machine, you must configure them by performing the following steps in the order shown:

    1. Use the Oracle Internet File System post-installation scripts to set up the Sendmail 8.9.3 executable and generate the sendmail.cf file.

    2. Incorporate the changes required for Oracle9iAS Email into sendmail.cf.

      See Also:

      Post-installation steps in Oracle Internet File System Installation Guide and the Oracle9iAS Email Installation Guide


      Note:

      If you incorporate the Oracle9iAS Email configuration changes into sendmail.cf and then run the scripts, the scripts will overwrite the changes (regenerating sendmail.cf).  


    If you plan to run the IMAP servers provided by Oracle Internet File System and Oracle9iAS Email on the same machine, you must configure them to listen on different ports. Use the Oracle Internet File System configuration utility and the Oracle9iAS Email Administration tool to specify the port for the component.

    For example, you can configure the Oracle9iAS Email to listen on the default port 143, and configure the Oracle Internet File System IMAP server to listen on some other port, as required by the installation.

    The clients accessing the IMAP servers must have accounts mapped to these specific ports. To access both servers at the same time, you must use clients that allow you to set the IMAP port number. Alternatively, you can run the two IMAP4 servers on two different Internet Application Server installations.

    1.5.9.2 Oracle9i Application Server Interconnect

    1.5.9.2.1 Recommended init.ora Values

    The following are the recommended minimum database init.ora parameter values to run all Interconnect adapters:

    db_block_buffers = 3200

    shared_pool_size = 314572800

    large_pool_size = 61440000

    java_pool_size = 60971520

    1.6 Examples and Demos

    Demos and examples for most Oracle9i Application Server components can be found at http://<hostname:port> where hostname is the name of your machine and port is your Oracle HTTP Server listener port. For more information on this port, refer to the Apache documentation.

    In addition, examples and demos of Oracle9i Application Server components are provided on your product CD-ROM and installed in the component directories.

    1.6.1 Demo Limitations

    1.6.1.1 OracleJSP Demos

    1.6.1.1.1 OracleJSP Demos Intended to Run on Client SIde

    The OracleJSP demos included with this distribution are intended to run on the client side in Oracle9i Application Server, not in the database's Oracle Servlet Engine (OSE). Several of the new demos, including the Email, Cache, JESI, XML Dom and info demos depend on libraries which will not be automatically loaded into the server. Follow the instructions in the non-OSE section of the demo README file instead of trying the make or makeit.bat files.

    1.6.1.2 Oracle Business Components for Java Demo Failure

    If the Business Components for Java demo does not work, your system may not be set up for it. Click on the link for the Business Components for Java on the HTTP Server home page, and follow the instructions in the Sample Application Setup link.

    $ORACLE_HOME/Apache/Apache/htdocs/OnlineOrders_html/submit_login. \
    jspsession.putValue("CSSURL","/webapp/cabo/images/cabo_styles.css"); 
    session.putValue("ImageBase", "/webapp/jsimages");
    

    1.7 National Language Support (NLS) Issues

    1.7.0.3 NLS_LANG Environment Variable

    mod_plsql

    When configuring mod_plsql, the NLS_LANG environment variable is configured on a per Web server instance level and not at the DAD level.

    Ensure that you have the correct NLS_LANG setting before starting your Oracle9i Application Server instance.

    Oracle PSP

    For Oracle PSP, the NLS_LANG environment variable must be set before loading PL/SQL Server Pages (PSPs) into the database using the loadpsp command.

    Using the JDBC OCI8 driver with JServ and OracleJSP

    If connecting to Oracle via the JDBC OCI8 driver, the appropriate NLS_LANG setting is required in jserv.properties. For example:

    wrapper.env=NLS_LANG=AMERICAN_AMERICA.UTF8 
    

    For information on the NLS_LANG environment variable, refer to the Oracle9i National Language Support Guide.

    1.7.0.4 NLS Parameters in the initicache.ora File

    The Oracle9iAS Database Cache installation creates a cache using the same database character set as the origin database. However, it does not set other National Language Support (NLS) features, such as date format or currency symbols.

    If the initialization file (initSID.ora) of your origin database specifies NLS parameters, you must copy those parameters to the initialization file (initicache.ora) of the cache (NLS parameters begin with "NLS_").

    For example, if the initialization file of your origin database contains the following parameters, copy them to initicache.ora:

    NLS_LANGUAGE = JAPANESE
    NLS_CALENDAR = "Japanese Imperial"
    NLS_DATE_FORMAT = "E YY-MM-DD"
    
    

    The initicache.ora file is located in the
    $ORACLE_HOME/admin/icache/pfile directory.

    1.7.0.5 NLS Limitations

    The following are known NLS bugs in this release:

    1.7.0.6

    For the language...  Replace <lang> with ... 

    Brazilian 

    ptb 

    French 

    German 

    Iberian Spanish 

    Italian 

    Japanese 

    ja 

    Latin American Spanish 

    esa 

    Russian 

    ru 

    Configuration Assistant Language Limitation

    In this release, Oracle9iAS Portal Configuration Assistant is certified for use in English only.

    1.8 Oracle Workflow

    1.8.1 Oracle Workflow Installation

    To install Oracle Workflow Release 2.6, you must include the connect string for your database in your tnsnames.ora file ($ORACLE_\ HOME/network/admin/tnsnames.ora). The Workflow installation process requires this information in order to connect to the database. This step is no longer required for subsequent releases of Oracle Workflow.

    1.8.2 Oracle Workflow Notification Mailer

    In Release 2.6 of Oracle Workflow, the perpetual shell script wfmail.csh, which restarts the UNIX Sendmail version of the Oracle Workflow Notification Mailer, calls wfmail rather than wfmail.snd. Before using wfmail.csh in Release 2.6, edit the script manually to call wfmail.snd. This step is no longer required for subsequent releases of Oracle Workflow.

    1.9 Required Patch for AIX-Based Systems

    Patch 1477485 fixes the problem with loading ctx/bin/ctxhx. Apply the patch to the origin database. This patch is in the following directory:

    <CDROM>/patch/bug1477485
    

    1.10 Configuring Oracle9iAS Wireless on AIX and Linux

    To use XSL for XML document conversion in Oracle9iAS Wireless, you must disable the JIT compiler in jserv. To disable the JIT compiler, add the following lines to the jserv.properties file.

    # PTG Start 
    wrapper.env=JAVA_COMPILER=NONE 
    # PTG End 
    
    

    After you add the lines to the jserv.properties file, restart Oracle HTTP Server.

    1.11 Forms/Reports for HP-UX

    For Forms/Reports on HP-UX there is a known issue if the machine has either of the two OS patchsets installed:

    PHSS_21959

    PHSS_22946

    The Forms designer will yield the following error message:

    ASSERTION FAILED STATUS = CLIPBOARDSUCCESS FILE UICL.C LINE 985
    

    This problem has been fixed in the latest Motif OS Patchset bundle. Upgrade the OS to Motif Cummulative patchset: PHSS_23823.

    To check the patchsets installed on the machine use the following command:

    $ /usr/sbin/swlist -l fileset
    

    1.12 Network Card Issues for Compaq Tru64 UNIX

    If Oracle installation on Compaq Tru64 UNIX takes a long time when using a remote X terminal and network collisions occur (identified by netstat -i), you might have a conflict with the auto-negotiation between the DE602 network interface card in the ES40 and the network routing device.

    To solve this conflict, set the DE602 interface speed and mode to match the network routing device speed and mode using the lan_config command. The following is an example command line:

    lan_config -iee0 -a0 -s100 -x1

    In Compaq Tru64 UNIX v. 5.1, Oracle9i Application Server no longer uses the console variables to set the parameters for the network interface cards. To make this change persist over reboots, enter the appropriate lan_config command at the end of the /etc/inet.local file.

    See Also:

    For more information on the lan_config command, see the man lan_config pages on your Compaq Tru64 UNIX system. 


  • Go to previous page
    Oracle
    Copyright © 2001 Oracle Corporation.

    All Rights Reserved.
    Go To Table Of Contents
    Contents