Release 1.0.2.2 for Sun SPARC Solaris
Part Number A90217-01
 Library |
 Contents |
| Oracle9i Application Server Release Notes Release 1.0.2.2 for Sun SPARC Solaris Part Number A90217-01 |
|
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 on the Oracle Technology Network at:
http://technet.oracle.com/products/ias
This document notes differences between Oracle9i Application Server Release 1.0.2.2 for Sun SPARC Solaris components and their documented functionality.
Product name changes in this release are:
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
You can access the most recent certification information at:
http://metalink.oracle.com
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.
Oracle9iAS Release 1 (v1.0.2.2) includes Oracle Enterprise Manager 2.2, which is not certified against the Oracle9i database.
Oracle9iAS Wireless only supports Oracle 8.1.6 and above.
This section describes new features in this release in each application area.
New in this release is Oracle9iAS Containers for J2EE, a pure Java runtime executing on JDK. It is lightweight (using less than 10 MB disk and 20 MB memory) and installs quickly (within a couple of minutes). It provides:
This release of Oracle9iAS Containers for J2EE is more stable wehn 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:
Java Servlets
Full support for Servlet 2.2 and significant parts of Servlet 2.3 (Public Draft), including:
Java Server Pages
Full support for JSP 1.1, including:
Enterprise JavaBeans (EJB)
Full support for EJB 1.1 and significant parts of EJB 2.0 (Public Draft), including:
Java Database Connectivity Services (JDBC)
Advanced Features
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 need to revert to JDBC (in most situations). The SQLJ implementation can perform fetches from an untyped ResultSetIterator, and allows omission of iterator declarations.
In addition, 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.
Infrastructure Services
Oracle9iAS Container for J2EE contains the following infrastructure components:
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:
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 coming 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 increases reliability and simplifies system adminstration with the these features and facilities:
Load Balancing and Availability Features
Clustering Facilities
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.
Portions of Oracle9i Application Server are distributed by Oracle under license from third parties ("Third Party Components"), including the Apache Web Server, version 1.3.19, licensed by the Apache Software Foundation. Oracle is distributing these Third Party Components as part of the Oracle9i Application Server product and, except as specified herein, will provide standard product support for the Third Party Components, as such support is further defined in the Oracle technical support policies. Please note that 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; however, Oracle shall have no obligation to do so. In addition, 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.
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:
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.
To build, install, and test mod_Perl DBI/DBD-Oracle and Apache::DBI for the Solaris platform, follow these steps:
C compiler Sun SparcWorks version 5.0
GNU Make GNU Make version 3.77
Perl Perl version 5.005_03
Apache::DBI
Perl DBI
Perl DBD-Oracle
prompt> setenv ORACLE_HOME /private1/iAS10 prompt> setenv PATH ${ORACLE_HOME}/Apache/perl/bin:${PATH}
prompt> setenv PERL5LIB ${ORACLE_HOME}/Apache/perl/lib/5.00503:${ORACLE_ HOME}/Apache/perl/lib/site_perl/5.005
DBI version 1.14
DBD::Oracle version 1.06
Apache::DBI version 0.87
PerlRequire <absolute path to ApacheDBI's startup.pl script>
Apache::DBI->connect_on_init('dbi:Oracle:',"scott/tiger", '');
prompt> $ORACLE_HOME/Apache/Apache/bin/apachectl start
Tip: 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 ######
Oracle 9i Application Server Wireless 1.1.1.1 is a patch for Oracle 9i Application Server Wireless Edition 1.1 (which was shipped with Oracle 9i Application Server 1.0.2.1.0). Oracle 9i Application Server Wireless 1.1.1.1 is a super-patch that includes the Oracle 9i Application Server Wireless 1.1.1 patch recently posted on Oracle Technology Network.
The 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
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.
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, simply upload up11-111.xml.
If you have modified the shipped version of these transformers:
$ORACLE_HOME/panama/sample/upload.sh
See the Oracle9i Application Server Wireless Configuration Guide for more information on the LoadXML utility.
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.
Previously, logging information for service requests and the session were logged in the repository as these events occurred. However, performance was degraded 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 suit 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 false, then the logged records will only remain in files. If true, the records are picked from files and logged onto the database (that is, 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. See 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.
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. Mobile email will drive productivity within your enterprise, allowing employees to stay in touch while away from the office. For more information, see Oracle 9i Application Server Wireless Configuration Guide.
To take advantage of the new group-based load-balancing features, you must make the following changes in the jserv.conf file:
auto (as opposed to on or off) for the new feature directives to take effect.
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
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
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.0.2.2, the scripts are pre-loaded into the Portal and have been removed from the install media.
This section describes known problems in this release.
Before using Oracle9i Application Server, read through each item in this section to gain an understanding of the restrictions and limitations in this release that may require additional steps. The items are categorized by solution area.
To select a locale for Oracle9i Application Server installation:
env | grep LANG
The output of this command must include the LANG environment variable, and 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.
The translated files for the selected locale are installed. In addition, English files are always installed.
Some Oracle9i Application Server components may not function correctly when interacting with the Oracle9i database if the o7_dictionary_accessibility parameter is set to FALSE. In the Oracle9i database init.ora file, add the following line:
o7_dictionary_accessibility=TRUE
The Oracle Universal Installer may display 'in progress' status after a component installation is in fact 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.
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.
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.
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, see the Oracle8i National Language Support Guide.
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 this command:
$ su -root
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.
Minimal Edition : oracle.iappserver.iapptop.Minimal.rsp
Standard Edition : oracle.iappserver.iapptop.Standard.rsp
Enterprise Edition : oracle.iappserver.iapptop.Enterprise.rsp
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
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"}
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}
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"
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"}
For Portal Config Asst. Only (With All Install Types) - Total : 7
[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"
Other Configuation tools
DBCA & NetCA
These tools are run in typical mode while running 9iAS silently, so no repsonse files are required.
Oracle9iAS Database Cache Configuration Assistant
This tool's user input is specified with EE response file - 2 parameters sl_dbaReturn & sl_connectStringReturn, as mentioned above with component [oracle.icache.icacheca_1.0.2.2.0]
Oracle Internet File System Configuration Tool
Use the file template IfsConfig.properties provided with the shiphome. This is a post-installation task. This configuration tool is not run with 9iAS installation.
Oracle Management Server
Silent mode is NOT supported with Oracle9iAS 1.0.2 release. Scheduled for Oracle9iAS 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.
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"}
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/
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 to configure the listener for the origin database.
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. Then, 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.
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.
When installing Oracle9i Application Server Enterprise Edition, and 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:
prompt>$ORACLE_HOME/Apache/Apache/bin/apachectl start
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.
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. The workaround is to increase this size before running the Oracle9iAS Portal Configuration Assistant, as follows:
If you do not perform these steps during an install, you can fix the problem as follows:
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:
log_tablespace, def_tablespace, doc_tablespace, or
b_configurePortal only if you are performing a standalone installation of Oracle Portal.
[oracle.webdb_3.0.8.9.8] #Parameter: silent #Type: Boolean #Description: This variable is true if silent mode is on. It is passed to the wwv component. silent=true #Parameter: b_configurePortal #Type: Boolean #Description: This is a public variable. When set it will disable the configuration wizard (OPCA) as well as the dialogs. b_configurePortal=true [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: tmp_tablespace #Type: String #Description: Temporary Tablespace for Portal's OPCA tmp_tablespace="TEMP" #Parameter: log_tablespace #Type: String #Description: Logging tablespace for Portal's OPCA log_tablespace="USERS" #Parameter: doc_tablespace #Type: String #Description: Document Tablespace for Portal's OPCA doc_tablespace="USERS" #Parameter: def_tablespace #Type: String #Description: Default Tablespace for Portal's OCPA def_tablespace="USERS" [oracle.webdb.apache_1.3.12.0.2b] #Parameter: port #Type: String #Description: This variable holds the value of the port on which the #listener will be started. Default value for apache is 7777 on solaris #and 80 on nt. port="7777" #Parameter: user_input1 #Type: StringList #Description: This variable takes the input from the first dialog. user_input1={"portal30_sso", "portal30_sso", "a816"} #Parameter: user_input2 #Type: StringList #Description: This variable holds the input from dialog2. user_input2={"portal30", "portal30", "a816"} #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="machine_name:port:sid"
The Web Cache Configuration Assistant starts after installation even if it is not selected in the configuration window.
Silent installation for Oracle9i Application Server Wireless is not supported; it requires entry of information specific to Wireless and manual editing of configuration files.
If you are upgrading from the previous release of Oracle9iAS Wireless, you must make the following changes to the jserv.conf file, located at:
$ORACLE_HOME/Apache/Jserv/etc/jserv.conf
ApJServMount /ptg /root
# PTG 1.1.1 Begin
ApJServGroupMount /ptg balance://group1/root
# PTG 1.1.1 End
If you are doing a new installation of Oracle9iAS Wireless:
If you want to use the Oracle9i database with components such as Oracle9iAS Portal, you must patch the JDBC driver. The patch is at the top level JDBC patch directory of the Oracle9iAS Release 1, v1.0.2.2 Administrative and Development Client CD for Windows 95/98/NT (available with the release across all operating systems platforms).
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.
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.
If you use Oracle Universal Installer to deinstall Oracle9iAS Database Cache, all services are also deinstalled. To deinstall Oracle Database cache, use the command shown below:
cachstrt script in the $ORACLE_HOME/bin directory.
prompt>wtacca -deinstall
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.
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:
<ORACLE_HOME>Apache/Apache/conf/oracle_apache.conf file.
include "<ORACLE_HOME>Apache/Apache/conf/mod_ose.conf:"
You can only upgrade to Oracle 9i Application Server Wireless 1.1.1.1 (on Oracle 9i Application Server Release 1 (v1.0.2.2.0) from Oracle 9i Application Server Wireless 1.1 (on Oracle 9i Application Server Release 1 (v1.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 Release 1 (v1.0.2.1.0)), then up to this current release.
During Oracle 9i Application Server Wireless installation, a Wireless repository is created.
Deinstallation of Oracle 9i Application Server Wireless DOES NOT automatically remove the database schema. Therefore, if you reinstall Oracle 9i 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, then:
sqlplus>drop user panama cascade
sqlplus>commit
sqlplus>exit
If you upgrade from Oracle8i database to Oracle9i database AFTER this maintenance release is installed, run:
migrate_8i_to_9i.sql
against the database containing your Wireless repository, connecting with proper user name, password and schema name.
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" will not work.
To resolve this problem:
Alias /soapdocs/ "ORACLE_HOME/soap/"
(where ORACLE_HOME is the full path to your Oracle home directory).
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/.
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:
Obtain a GS-ID certificate from an appropriate vendor. Oracle has tested the GS-ID certificate from Verisign (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).
Obtain a patch that will allow your browser to upgrade the encryption method. Sources include Apache (www.apache.org) and Fortify (www.fortify.net/intro.html). Oracle has tested the patch from Fortify. It is straightforward to download and apply to your browser.
Oracle Demo certificates (that is, 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.
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.
Note that this problem will only occur when starting without SSL.
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:
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
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.
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.
On NT, mod_plsql crashes under moderate load. This issue is explained in Bug No. 1432961 and requires backports for Bug No. 1179779 and Bug No. 1405498 on the Oracle Client and Server side. These fixes should be applied to the 8.1.7 Oracle Client libraries in your Oracle home, and the corresponding server side fix should be applied to the Oracle Database Server.
Internal testing could not reproduce the issue on Solaris, although the bug does exist on all platforms. If you have these problems on your system, please apply the required patches (8.1.7.1.1 for the Oracle Client and Server side, and 8.1.6.3.2 for the Oracle Server side. ) to your platform as well. These patches are complete SQL*Net patches, and information on applying them is released with them. They contain fixes other than the mod_plsql fix described here.
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.
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:
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;
oas_public" OWA package installation schema.
CREATE PUBLIC SYNONYM" privileges. If it does not, then grant these privileges to the user schema before continuing with the next step.
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;
If the OWA packages are installed manually in <$ORACLE_HOME>Apache/modplsql/owa, a "File not found" error occurs.
To resolve the error:
<$ORACLE_HOME>Apache/modplsql/owa/owacomm.sql.
spool ..\..\portal30\admin\plsql\owa\owaldscr.sql
to
spool owaldscr.sql
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/.
When running mod_plsql against a 9.0.1 database, you will not be able to upload files if the cursor_sharing parameter in the database initialization file initorcl.ora is set to "similar". In this case, an ORA-3106 error occurs.
This problem will be corrected in the next patch release of 9.0.1. Until then, the workaround is to not use "similar" for the cursor_sharing parameter.
If you are running Oracle9i Application Server-based mod_plsql applications (such as Oracle Portal), please note that 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 bug no. 1745320 for more details). To get around this problem, you will need to 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, there is another workaround. Edit the file $ORACLE_HOME/rdbms/admin/catproc.sql and comment out the "@@owacomm.sql"
line which loads OWA packages so that the upgrade script will not reload the OWA packages provided by the database. Instead, the OWA packages already loaded in the database from Oracle9i Application Server will be preserved.
|
Note: If you reinstall the OWA packages,you should recompile all dependent objects that are invalidated. |
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 filesystem 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).
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, and so on, are not supported by Oracle.
In this release, the symmetric encryption algorithms RC2, RC5, IDEA are not supported.
The document Using mod_oprocmgr with mod_jserv in the Oracle9i Application Server DocumentationLibrary (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 in order for it 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."
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.
If a valid servlet is requested once, and then requested again a second time using the URL-encoded version of the servlet's URL, then 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 always use the encoded version of each URL or always use the unencoded version of each URL. If it is necessary to mix them, always use the encoded version before using the unencoded version (for each run of the server).
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, you must change one line in soap.properties and add one new line to soap.properties.
To make these changes:
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
root.properties=%ORACLE_HOME%/Apache/Jserv/etc/zone.properties
(replace %ORACLE_HOME% with your expanded ORACLE_HOME environment variable)
@ 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, then the URL will cause long timeout delays, errors in the Apache error_log file, and error responses to the HTTP request.
The LANG environment variable specifies the default locale for application programs. To make servlets and JSPs work properly in non-English locales, you must perform the following steps after installing Oracle9iAS, and before starting the Oracle HTTP Server:
#wrapper.env.copy=LANG
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 remedy this, increase the value of TimeOut directive in httpd.conf.
To make Graphics integration dmwork, you must set the following environment variables:
setenv PRINTER <printer name>
setenv TK2_PRINT_STATUS echo
This release of Oracle9i Application Server 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.
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
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.
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 1549369, version 2.2.0 - Cannot de-register Forms Listener Up/Down Event
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
Bug 1383239, version 6.0.8.8 - OEM startup job returns "completed" status if it fails
Bug 1479367, version 8.1.7 - nmiforms.tcl is looking for an ORACLE_HOME environment variable in the wrong way
If you are using ADTs or char fields in a compound key with an Oracle9i database, you should apply Forms patch 1777190 on top of your Oracle9iAS Release 1 (v 1.0.2.2) installation.
If you upgrade to Release 1 (v1.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,
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.
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.
To address language-encoding issues, new optional input parameters have been added:
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, simply upload up11-111.xml.
If you have modified the shipped version of these transformers: 1.) merge the differences, then 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. See Oracle9i Application Server Wireless Edition Configuration Guide for more information on the LoadXML utility.
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.
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 Oracle9i Application Server Wireless Edition Implementation Guide for information on how to create a Designer or an Administrator.
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.
This release of Wireless Edition only supports the classes12.zip JDBC driver. classes111.zip is no longer supported.
For a list of certified devices and gateways supported by Wireless Edition, see the OTN web site at:
http://otn.oracle.com/products/iaswe
To obtain third party files for using location services in Wireless Edition, see the OTN web site at:
http://otn.oracle.com/products/iaswe
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. See the Oracle8i documentation for more detailed database configuration and performance information.
When using Oracle9iAS Wireless Edition notifications (the AQ Daemon process), note that 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.
To use the Provisioning Service in the bootstrap repository, you must first set the input parameters of the master service to be User Customizable.
Numeric input parameter names are not allowed in the master service PL/SQL code.
Also, JDBC connect strings that specify a user name and password are not allowed, for example:
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.
When creating a bookmark in the Personalization Portal, the http:// prefix must be included in the URL, for example:
http://domain_name.com
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.
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 and font.properties files and therefore does not support multibyte character sets.)
On the application server:
font.properties file of the JVM with font.properties.<locale>.
The JVM path for the server is:
%ORACLE_HOME%/panama/WebIntegration/Server/jvm/lib
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
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.)
On the Oracle9iAS Wireless client:
http://java.sun.com/products/jdk/1.2/jre
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
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\
developer.bat file. The path for the file is:
%ORACLE_HOME%\panama\WebIntegration\Developer\bin\developer.bat
SET JDKDIR=C:\OraHome1\panama\WebIntegration\Developer\jvm
REM SET JDKDIR=C:\OraHome1\panama\WebIntegration\Developer\jvm SET JDKDIR=jre1.2
SET CLASSPATH="%JDKDIR%\LIB\RT.JAR;%DEVDIR%\LIB\DEVELOPER.ZIP; %DEVDIR%\packages\wmroot\code\classes"
SET CLASSPATH="%JDKDIR%\LIB\RT.JAR;%DEVDIR%\LIB\DEVELOPER; %DEVDIR%\packages\wmroot\code\classes"
"%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
-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
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 to 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.
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
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.
The PAPz-based personalization portal released before Oracle9iAS Wireless Edition 1.1 is being officially deprecated in the Oracle9iAS Release 1 (v1.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.
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
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.
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.
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 Oracle9iAS Release 1 (v1.0.2) releases is available to fix this problem. The patch is not specific to NT as reported, but 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:
wtcsini.plb to the following directory:
WIndows NT: <ORACLE_HOME>\icache\admin
UNIX: <ORACLE_HOME>/icache/admin
Rerun the Oracle9iAS Database Cache Configuration Assistant from the bin directory.
Windows NT:
cd <ORACLE_HOME>\bin wtacca -create -typical "username=sys" "password=your_password"
Unix:
cd <ORACLE_HOME>/bin wtacca -create -typical "username=sys" "password=your_password"
The Oracle9iAS Database Cache Configuration Assistant completes without errors.
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.
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.
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.
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.
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. In such a case, you can start Oracle9iAS Reports Service from an MS-DOS 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.
Oracle9iAS Reports Services hangs when users authenticate.
To make Reports Portal integration work seamlessly, apply
tcpatch 6_0_8_11_3.
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 9iAS 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
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:
The following instructions explain how to install and configure the VNC X-Windows server software to be in conjunction with an Oracle9i Application Server Release 1 (v1.0.2.2) installation on Sun Solaris. This is used as a substitute for the requirement of the 'xhost +machinename' command when running Discoverer 4i and Oracle Portal, and allows the software to be run in a more secure mode. This software removes the requirement for the user to execute the 'xhost' command and also eliminates the need to remain logged into the Sun machine. This is because the 'xhost' setting is session dependent, and is therefore lost when the user logs out of the machine on which the command was issued.
Using this VNC software to mange the X-windows sessions in the background, the Oracle9i Application Server software is run using this as the VNC Xwindows server, without needing to access the standard X-windows system. The steps to implement this are as follows:
prompt>vncserver :13 -pn -localhost
The server starts on display number 13. You can use any display number, as long as it is available and unused by any other software. The default display value is 1.
A password prompt appears (if this is the first time you are starting VNC after installing it).
prompt>vncserver :13 -pn -localhost
The following message appears (where 'oracle-sun' is the machine name):
New 'X' desktop is oracle-sun:13 Starting applications specified in /private1/oracle/.vnc/xstartup Log file is /private1/oracle/.vnc/oracle-sun:13.log
prompt>cat /private1/oracle/.vnc/oracle-sun:13.log
A listing similar to that below appears:
20/02/01 15:37:59 Xvnc version 3.3.3r2 20/02/01 15:37:59 Copyright (C) AT&T Laboratories Cambridge. 20/02/01 15:37:59 All Rights Reserved. 20/02/01 15:37:59 See http://www.uk.research.att.com/vnc for information on VNC 20/02/01 15:37:59 Desktop name 'X' (oracle-sun:1) 20/02/01 15:37:59 Protocol version supported 3.3 20/02/01 15:37:59 Listening for VNC connections on TCP port 5903 20/02/01 15:37:59 Listening for HTTP connections on TCP port 5803 20/02/01 15:37:59 URL http://oracle-sun:7777 Can't find include file /private1/oracle/.Xresources
jserv.properties file located in:
/$ORACLE_HOME$/Apache/jserv/etc/
#Oracle Portal wrapper.env=DISPLAY=oracle-sun:13.0 #RV adding lines for disco4iv wrapper.env=DISPLAY=oracle-sun:13.0
Ensure that the entries for both Discoverer and Oracle Portal are the same, so that both values point to the VNC Server. The key is the value chosen as part of the install (in this example, the display number 13).
setenv DISPLAY oracle-sun:13.0
xhost +oracle-sun
where oracle-sun is the machine name. You cannot use 'localhost' to refer to the machine name. JServ will not work without the specific machine name.
The virtual X display starts. You can log off of the console, and the VNC Server will continue to start X Windows sessions for the Discoverer software when required.
vncserver -kill :13
The server stops.
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. We strongly advise you to obtain and 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.
"==> NEW! Click here for ALL Product Patches"
The patchset numbers are:
1750560: Discoverer Plus and Viewer Version 4.1.36 patch for Sun SPARC Solaris
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:
When you try to access Oracle Enterprise Manager with a browser, an error is returned because your system cannot find the oem.conf file. The Oracle Enterprise Manager entry in the oracle_apache.conf file contains both backslashes and forward slashes. This is incorrect.
Edit the entry as shown below to resolve this issue.
The incorrect entry is
D:\Oracle\M6/oem_webstage/oem.conf
The correct entry is
D:\Oracle\M6\oem_webstage\oem.conf
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.
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 colum of the line, or the Oracle HTTP Server will not strip out comment lines correctly.
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 colum of the line, or the Oracle HTTP Server will not strip out comment lines correctly.
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.
The Oracle9i File System e-mail component and the Oracle eMail server both use Sendmail for mail transfer. Oracle9i File System requires Sendmail version 8.9.3 or later and eMail Server requires versions of Sendmail later than 8. Oracle9i File System ships an open source version of Sendmail 8.9.3 for Solaris and other UNIX ports. Windows NT and Windows 2000 installations require purchasing Sendmail version 3.0 or 3.0.2 (respectively) for both e-mail components.
To run the Oracle eMail server and Oracle9i File System on the same machine, you must configure them by following the steps below in the order shown:
sendmail.cf file. (For more information, see the postinstallation steps in the Oracle9i File System Installation Guide).
sendmail.cf. (For more information, see Chapter 3, Postinstallation, in the Oracle9iAS Email Installation Guide.)
If the IMAP servers provided by Oracle9i File System and Oracle9iAS Email are to be run on the same machine, you must configure them to listen on different ports. (Use the Oracle9i 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 Oracle9i 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 Oracle9iAS installations.
The recommended minimum database init.ora parameter values to run all Interconnect adapters are as follows:
db_block_buffers=3200
shared_pool_size=314572800
large_pool_size=61440000
java_pool_size=60971520
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.
The OracleJSP demos included with this distribution are not intended to run on the server in Oracle Servlet Engine (OSE)/JVM. Please use the following instructions (which replace instructions in earlier versions of the demo REAMDE), to install the JSP demos in your Oracle9iAS environment:
To run the CallEJB.jsp sample:
prompt> cd $ORACLE_HOME/javavm/demo/examples/ejb/basic/sqljimpl prompt> make
To run the CallCORBA.jsp sample on OSE:
prompt> cd $ORACLE_HOME/javavm/demo/examples/corba/basic/helloworld prompt> make
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");
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.
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.
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 Oracle8i National Language Support Guide.
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.
The following are known NLS bugs in this release:
| For the language... | Replace <lang> with ... |
|---|---|
|
Brazilian |
ptb |
|
French |
f |
|
German |
d |
|
Iberian Spanish |
e |
|
Italian |
i |
|
Japanese |
ja |
|
Latin American Spanish |
esa |
|
Russian |
ru |
In this release, Oracle9iAS Portal Configuration Assistant is certified for use in English only.
|
 Copyright © 2001 Oracle Corporation. All Rights Reserved. |
|