Skip Headers

Oracle9i Application Server Release Notes Addendum
Release 2 (9.0.2.0.1) for Microsoft Windows
Part No. A90336-10
  Go To Documentation Library
Home
Go To Table Of Contents
Contents

Previous Next  

11 Oracle9iAS Personalization

This chapter addresses the following topics:

11.1 General Issues and Workarounds

This section describes general issues and their workarounds for Oracle9iAS Personalization.

11.1.1 Supported Windows Platforms

The OP release notes, in the section "Supported Windows Platforms," contains two errors:

  • The release notes state that Windows XP is a supported platform. This is incorrect; OP is not certified to run on Windows XP.

  • The release notes state that the service pack for the supported Windows NT 4.0 platform is SP5. This is incorrect; users should refer to the iAS documentation for the supported Windows platforms and the required service packs.

11.1.2 NLS_LANG Setting

Oracle9iAS Personalization is certified against UTF8 only. If NLS_LANG is set to Japanese_Japan.JA16EUC, MTR tables are not successfully created in the target DB, the login to the OP Admin home page therefore fails, and error messages result.

There is no workaround currently.

11.1.3 Cannot Reuse an RE Name after Deleting

An RE name that has been deleted should be available for reuse; instead, reuse of the name results in an error message saying that RE names must be unique in an RE farm.

The workaround is to click the Apply button after deleting the RE and before creating a new RE with the same name.

11.1.4 Leaving the "Send Notification to" Field Blank

After building and deploying a package or creating a report, leaving the "Send notification to" field blank results in the following error in the message log: java.lang.NullPointerException

There is no workaround currently.

11.1.5 Database Alias Cannot Exceed 30 Bytes

When creating an MTR database connection or a new RE Farm, the user must enter an alias for the database. If the alias exceeds 30 bytes, it is rejected with an error message that says "Database alias cannot be more than 30 bytes."

Workaround: Limit the database alias to 30 bytes.

11.1.6 Syntax Problem with opconfig.bat on NT

When running opconfig.bat on NT, the following error message is displayed at the end: "The syntax of the command is incorrect." You can ignore this message.

11.1.7 Bad Email Address in "Send Us Your Comments" Form

In the documentation for Oracle9iAS Personalization and for Oracle9i Data Mining, the email address provided for sending comments on the "Send Us Your Comments" form is given as DARWINDOC@us.oracle.com; this is incorrect. The correct email address is DARWINDOC_US@oracle.com.

11.1.8 Running Config File with Relative Pathname

Instructions for running the configuration wizard do not work as given on page 3-3 of the administrator's guide. You must be in the $ORACLE_HOME\dmt\admin directory, from which you run opconfig.bat. to install successfully.

11.1.9 Messages re Users Cannot Be Dropped

If you are installing OP for the first time, you may see error messages announcing that various users cannot be dropped. You can safely ignore these messages. For example, you may see a message that the user OPWFBASE cannot be dropped. This user does not exist and therefore cannotbe dropped

11.1.10 Sample Program Not Found

The Oracle9iAS Personalization Programmer's Guide Release 2 (v 9.0.2), page A-1 refers to a sample program named ProxyTest.java that is not installed in the directory indicated. The program is presented in that document, starting on page A-1. You can cut and paste the program from the HTML version of the document.

11.2 Administrative Issues

This section describes administrative issues for Oracle9iAS Personalization.

11.2.1 Local Naming Should Be Consistent

If you are using the local naming method to identify connect descriptors for database services within your network, the net service names (aliases) provided in the tnsnames.ora file on each client must be identical. You can ensure this by copying the properly configured tnsnames.ora and sqlnet.ora files to the same locations on the other clients.