|
Oracle9i Application Server Release Notes Addendum,
Release 2 (9.0.2) for AIX-Based Systems, hp HP-UX PA-RISC (64-bit), hp Tru64 UNIX, and Linux x86 Part No. A97395-09 |
|
|
|
|
Oracle9i Application Server Release Notes Addendum,
Release 2 (9.0.2) for AIX-Based Systems, hp HP-UX PA-RISC (64-bit), hp Tru64 UNIX, and Linux x86 Part No. A97395-09 |
|
|
|
|
This chapter summarizes issues associated with Oracle9i Application Server. Topics include:
The following are known issues associated with Oracle9iAS Clickstream Intelligence:
When you configure a dedicated database by command line, the file click-app.properties in ORACLE_HOME/click/conf directory is not updated after the installation is done. Thus, the Clickstream Runtime Admin still points to the seed database.
Complete the following steps for a workaround:
After the installation is done, backup the original click-app.properties file.
Modify the click-app.properties file and change the value of following variables to correspond the your dedicated database:
db_hostname, db_port and db_sid
Restart the Oracle HTTP Server using the following commands:
ORACLE_HOME/opmn/bin/opmnctl stopall ORACLE_HOME/opmn/bin/opmnctl startall
Clickstream Analytics requires Oracle Discoverer and since Discoverer is not available on Tru64 UNIX, the ability to analyze, view, and create reports of click data does not exist on Tru64 UNIX installations of Clickstream. All other functionality of Clickstream (such as administrating, capturing, and loading click data) functions properly on Tru64 UNIX.
Because Analytics is not supported on Tru64 UNIX, both the "Analytics - Discoverer Viewer" and "Analytics - Discoverer Plus" links on the main page of the Clickstream installation on Tru64 UNIX produce a message similar to:
Clickstream Discoverer Viewer does not appear to be running
As a workaround, use Clickstream Analytics on a different platform that supports Analytics (for example, HP-UX, Linux and AIX) to analyze the click data captured by Clickstream on Tru64 UNIX
For Oracle9iAS Clickstream Intelligence to work with a Oracle9i Server release 2 (9.2.0.1.0) database, you need to apply the patch for bug 2435787.
This patch is available at:
http://metalink.oracle.com
The following are known issues associated with Oracle9iAS Discoverer:
The Discoverer servlet requires access to an X server to support its charting functionality. Note that the X server does not have to run on the same machine as the Discoverer servlet.
The following potential problems can occur if the X server is not running or is not configured correctly:
Discoverer Does Not Start
If the X server is not running or is not configured correctly, you might be unable to run Discoverer at all. The first time you specify the URL for Discoverer Plus or Discoverer Viewer, the browser session will simply hang.
Discoverer Viewer Hangs When Attempting to Display Charts
If the X server is not running or is not configured correctly, you might be unable to open workbooks in Discoverer Viewer that contain charts.
To confirm that the problem is related to accessing the X server:
Set the default value of the CHARTING element in the configuration.xml file to FALSE.
Use Oracle Enterprise Manager to stop and start the OC4J_BI_Forms component.
Attempt to launch Discoverer Viewer by specifying the appropriate URL.
If you successfully started Discoverer Viewer, attempt to open a workbook containing a chart.
If Discoverer Viewer starts successfully with the CHARTING element set to FALSE, the problem is probably related to accessing the X server software.
Remember to set the default value of the CHARTING element in the configuration.xml file back to TRUE.
To resolve problems related to accessing the X server, complete the following:
Confirm that the X server software has been installed on a suitable machine. The X server software must be installed on a machine that meets certain hardware pre-requisites such as a keyboard and a hardware frame buffer (typically on a graphics card).
Alternatively, you can run a pseudo-X server such as XVFB or VNC that uses an in-memory virtual frame buffer instead of a hardware frame buffer.
|
See Also: "Setting Environment Variables" section in the Oracle9i Application Server Installation Guide for information about virtual frame buffers. |
Confirm that the X server is running.
To start the X server on most UNIX platforms, simply log in to the console from the UNIX machine.
Note that if you are using the X server, you must remain logged in and have the X server running at all times. To avoid this requirement, use a pseudo-X server such as XVFB, VNC instead.
|
See Also: "Setting Environment Variables" section in the Oracle9i Application Server Installation Guide. |
Confirm that the machine running the X server is specified by the DISPLAY environment variable on the machine running the Discoverer servlet.
|
See Also: "Setting Environment Variables" section in the Oracle9i Application Server Installation Guide for information about setting theDISPLAY variable.
|
You can change the DISPLAY environment variable after installation by editing the value of the DISPLAY property in the opmn.xml file. This file is located in the <ORACLE_HOME>/opmn/conf directory.
Confirm that the machine running the Discoverer servlet has permission to access the X server.
To give the Discoverer servlet machine access to the X server, type the following on the machine running the X server:
xhost +<server_name>
where <server_name> is the name of the Discoverer servlet machine.
Confirm that another X application will launch successfully from the machine running the Discoverer servlet.
For example, you might run xterm or xclock from the machine running the Discoverer servlet. If the DISPLAY environment variable is set correctly and the machine can access the X server, the X application will run without error messages.
When you select the link to start Discoverer Plus, you may repeatedly be prompted for the password. Perform the following steps to fix the problem:
This issue can be fixed by making a change to the HTML file which contains the link. Accordingly, locate the HTML file "disc_demo_plus.htm" in the following directory:
<ORACLE_HOME>/j2ee/OC4J_BI_Forms/applications/discoverer/web/intro/html
Search and delete the file for the text "&release=true". For example, the part of the link which needs to be edited looks like:
../../plus?ac=SCOTT%7E40DISCODEMO&eul=SCOTT&nlsl=en-us&release=true&_plus WorkbookSource=Database...
After making the change, it will look like:
../../plus?ac=SCOTT%7E40DISCODEMO&eul=SCOTT&nlsl=en-us&_plus_WorkbookSource=Database...
When attempting to migrate the Discoverer preferences as per the method documented in the Oracle9i Application Server: Migrating from Oracle9i Application Server 1.x, you may get the error below:
ld.so.1: ./dis51pr: fatal: liborb_r.so: open failed: No such file or directory Killed
If you get this error, then no migration actions are performed. To work around this issue, execute the following command before migrating preferences.
Navigate to the following directory:
<ORACLE_HOME>/discoverer902
Issue the following command:
./discwb.sh
Then issue the following command:
dis51pr -migrate
Discoverer public connections can be created in the "General Discoverer" configuration page which is part of the Oracle Enterprise Manager Web site.
Please note that the EUL entered in this page is case sensitive. If the EUL name is all uppercase then it must be entered using uppercase characters.
Make sure that the following processes are running after installation is complete:
oad
osagent
If either of these processes is not running, perform the following steps:
Change directory as follows:
$ cd $ORACLE_HOME/discoverer902/util
Run the following scripts:
$ unregistersession.sh $ stopall.sh $ startall.sh $ registerall.sh
The out-of-box connection for the Discoverer Plus Demo pages does not work.
The workaround is to:
Use Oracle Enterprise Manager to delete the existing demonstration connection.
Use Oracle Enterprise Manager to create a new connection.
Set the connection details as follows:
| Parameter | Setting |
|---|---|
| user | scott
|
| passwd | tiger
|
| Database | discodemo
|
| EUL | SCOTT
|
There is a known issue with Discoverer 9.0.2 (Unix) running against an infrastructure database setup with the UTF8 character set. It causes the following problems:
The General Discoverer Page in Enterprise Manager OEM does not work properly
The connection page for Viewer and Plus displays an error:
An error occurred trying to communicate with the connection store
The portlet provider works but there are no connections that you can chose from in the Edit Defaults page for either the "worksheet" or "list of workbooks" portlet.
Oracle recommends that you re-install using a non-UTF8 character set for the infrastructure database.
If that is not possible, you need to delete a single row from the ORASSO schema in the infrastructure database:
|
Note: Oracle recommends that you re-install using a non-UTF8 character set to avoid completing this procedure. |
Find the password for seed database schema user ORASSO:
Run oidadmin from $ORACLE_HOME/bin (This is the infrastructure Oracle Home).
Connect to the OID running the infrastructure install. Use the ias_admin username and the password you provided when performing the Infrastructure installation.
Navigate to Entry Management, cn=Oracle Context, cn=Products, cn=IAS, cn=IAS infrastructure Databases, orclReferenceName=iasdb..., orclReferenceName=ORASSO
Note the value for orclPasswdAttribute for ORASSO, this is the database password for ORASSO.
Connect to the seed database using the ORASSO username and the password obtained from Step 1.
Delete the offending row:
Do a select to make sure there's only one row:
select from wwsso_psex_user_info$ where app_id like '1326';
There should be only one row.
Delete this row :
delete from wwsso_psex_user_info$ where app_id like '1326' ;
Now the OEM, Viewer, Portlet Provider should all work.
The following are known issues associated with Oracle9iAS Forms Services:
HTTP and HTTPS Cannot Be Used Simultaneously with Single Sign-On
Steps Required to Set Up PJCs Generated by JDeveloper in Forms
Java Plug-in Security Warning Message Pops Up When Web Form are Run in Native Netscape Browser
JVM Dump on Creating Trigger or Program Unit When Classpath Exceeds 511 Characters
For improved functionality, it is recommended that you use JInitiator 1.3.1.9, which is available for download on OTN, rather than the version of JInitiator that was included with your installation of Forms.
When you use Single-Sign-On (SSO) with Forms, you must register the mod_osso partner on the middle-tier server. If you run a form in http mode, you must register it with the required http information. If you run a form in https mode, you must register it with the required https information. However, you can only register one or the other with mod_osso. Therefore, you cannot simultaneously run forms in http and https mode with SSO.
In the Property Inspector, you must set the property "Query Data Source Name" for the control block otherwise Forms Developer will crash when creating a relation using the New Relation Wizard.
When you create a Pluggable Java Component (PJC) using the JDeveloper PJC Wizard, you will need to make dependent Java classes available at runtime for the PJC to use. These dependent classes are:
oracle.jdeveloper.pjc.BeanWrapper
oracle.jdeveloper.pjc.TypeConverter.
The simplest way to make them available is to include the jdev-rt.jar file along with the Custom PJC Jar file in the archive tags for your application. However, to reduce the size of the download, you can explicitly include the two required classes into your custom PJC jar file by using the JDeveloper deployment profile settings.
To include the classes, complete the following
Create or edit a deployment profile to create a simple Jar file.
In the Dependency Analyzer settings, select the JDeveloper Runtime node, and select Add to add them to the dependency analyzer's classpath radio button. The generated jar file will then include the BeanWrapper and TypeConverter classes if they are required by the PJC.
In order to run the JDAPI, you will need to have f90jdapi.jar in your CLASSPATH:
CLASSPATH =<oraclehome>\forms90\java\f90jdapi.jar
When using JInitiator, certificates are already loaded and applets are trusted with the signature. However, when using a native browser, certificates are not loaded automatically. Therefore, select Grant or Grant Always in your browser to avoid this warning.
When the FORMS90_BUILDER_CLASSPATH exceeds 511 characters, Forms Developer has a JVM dump when trying to create a trigger or a Program Unit. The workaround is to set CLASSPATH=FORMS90_BUILDER_CLASSPATH, either in the f90desm.sh script or at the command line.
The online help system may fail to start and may generate an error (FRM-18105) for Japanese installations of Forms Developer on all operating systems. The reason is that one online help file was installed to the wrong directory.
The workaround is to access the ORACLE_HOME/forms90/doc/JA directory and locate the fmhelp.jar file. Move this file to the ORACLE_HOME/forms90/doc/JA/fmdevhelp directory.
The default configuration for Oracle9iAS Forms Services does not run in SSO mode. The default configuration for Oracle9iAS Reports Services does run in SSO mode.
Forms applications calling integrated Oracle9iAS Reports Services using the Forms Run_Report_Object built-in will not experience any problems when Forms is running in non-SSO mode and Reports is running in SSO mode as long as Reports Services and the requested Reports module are not registered with Oracle9iAS Portal.
Other Requirements
The property, Report Server, must be set explicitly for all report objects in a Forms module.
If a Reports server other than the default is being used, that server must be started from the command line as follows:
rwserver server=<Reports server name>
The system variable, REPORTS_PATH, must be modified in the file <ORACLE_HOME>/bin/reports.sh to reference the location of Reports.
The first time a Reports server is started, it creates a configuration file called <ORACLE_HOME>/server/conf/<server_name>.conf.
The default status of a Reports server is secure. To change the Reports server status to non-secure, modify <ORACLE_HOME>/server/conf/<reports_server_name>.conf by commenting out the <security> tag and removing securityId from the <job> tags.
After making these modifications, the Reports server must be restarted.
If Forms Services is configured to run in SSO mode, then Reports requests are sent with the authid provided, based on the SSO user login.
Protected Reports and Reports Servers can be registered in Oracle9iAS Portal.
The Table 7-1 lists the possible Forms/Reports combinations and expected results:
Table 7-1 Outcome of Forms/Reports Integration when Forms is Running in SSO Mode or Non-SSO Mode
| Reports Type | Registered, Secure Reports ServerRuns Only Registered Reports | Registered, Secure Reports ServerRuns Any Reports | Non-Secure Reports Server |
|---|---|---|---|
| Reports with public access | report generated
|
report generated
|
report generated
|
| Reports with specific user access | report generated
|
report generated
|
report generated
|
| Reports with no specific user access | report not generated
|
report not generated
|
report generated
|
| Non-registered reports | report not generated
|
report not generated
|
report generated |
You may encounter the following error when attempting to access a sample form using a browser:
URL Not Found; The requested URL /forms90/f90servlet was not found on this server.
As a workaround, add the following entry to the oracle_apache.conf file:
<ORACLE_HOME>/forms90/server/forms90.conf
where <ORACLE_HOME> is the value of Oracle home for the Oracle9iAS installation.
Oracle9i Developer Suite is not supported on AIX-Based Systems or Tru64 UNIX. Please use Oracle9i Developer Suite on Windows as your Forms development environment.
The following are known issues with Oracle HTTP Server:
Microsoft Internet Explorer Might Report Incorrect Host Header After a Redirect
Microsoft Internet Explorer Might Report Errors When Two OSSO Protected Servers are on the Same Host
Information About Protecting Metadata Directories Used by OJSP
Configuring a Virtual Host Improperly Can Cause DADs to Break
Oracle HTTP Server (1.0.2.2.x) Cannot Be Used with Oracle9iAS (9.0.2.x)
If an infrastructure Single Sign-On Server install and a middle tier install are on the same machine (in different Oracle homes), Microsoft Internet Explorer reports an incorrect host header after a redirect. This incorrect host headed causes mod_osso to generate an error message when trying to access a protected resource after the user has been redirected from the Single Sign-On Server back to the original server. If you click on reload in Internet Explorer, the session continues successfully. This issue will not occur if any of the following conditions are true:
You do not use Microsoft Internet Explorer.
Protected resource and the Single Sign-On Server are running behind Oracle HTTP Server instances with different server names or on different hosts. This is the most likely deployment.
Single Sign-On Server and the protected resource are running behind a single Oracle HTTP Server port.
When you install an infrastructure instance of Oracle9iAS and a middle tier installation on the same machine, Microsoft Internet Explorer might report various errors where an incorrect host header is sometimes passed after redirection. Specifically, if you have already logged on via the Single Sign-On Server to the middle-tier instance and then click on a link that tries to redirect them to the infrastructure instance, you will receive an OSSO error page. Pressing the Back button allows you to continue to the page they originally wished to reach.
If you issue the "opmnctl stopproc" command in a process seconds after the process was killed or abnormally terminated, the "opmnctl stopproc" command might hang. This might prevent you from issuing other process-related commands.
In this situation, issue the following commands:
opmnctl reload opmnctl stopproc
If you are using dcmctl, then the "dcmctl stop" command not hang, but fail. Issue the following commands to resolve the situation:
dcmctl updateconfig opmn dcmctl stop
Perform the following steps to protect metadata directories used by OJSP:
Add the following lines to httpd.conf file:
<DirectoryMatch /WEB-INF/> Order deny,allow Deny from all </DirectoryMatch>
Modify the following lines in the ojsp.conf file:
<Location /_pages/> Order deny,allow Deny from all </Location>
to be:
<DirectoryMatch /_pages/> Order deny,allow Deny from all </DirectoryMatch>
After installation, you can configure Virtual Hosts in the httpd.conf file, either by using the 'advanced' section of the EMD console or by using a text editor.
Ensure that the server definitions for VirtualHosts are provided after the Port, Listen and ServerName directives. A simple example of a correctly set Virtual Host section might be as follows:
#
# these are set at the end of the httpd.conf file after the IAS installation
occurs
#
Port 7778
ServerName someServer.mycompany.com
Listen 7779
#
# these lines were added manually to create a virtualHost
#
NameVirtualHost 1.2.3.4
<VirtualHost 1.2.3.4>
DocumentRoot /u01/app/oracle/product/iAS9020_portal/Vhost1.htdocs
ServerName Vhost1.mycompany.com
</VirtualHost>
Oracle does not support using the Oracle HTTP Server component that is supplied with Oracle9iAS Release 1 (1.0.2.2.x) as a front end to the Containers for J2EE (OC4J) component supplied with Oracle9iAS Release 2 (9.0.2.x), that is, you must not use the mod_Proxy module to route data between these two components.
Always use the mod_oc4j module to route data to and from the OC4J component supplied with Oracle9iAS Release 2 (9.0.2.x). Use the mod_proxy module to route data between the HTTP Server component supplied with Oracle9iAS Release 1 (1.0.2.2.x) and the OC4J component supplied with Oracle9iAS Release 1 (1.0.2.2.x).
Ensure that if you use a regular text editor to make changes to the file, you use the following dcmctl utility to update your changes.
<ORACLE_HOME>/dcm/bin/dcmctl updateConfig
This is automatically done for you if you edit the file through the EMD console.
The following are known issues associated with Oracle9iAS InterConnect:
To use the HTTP adapter to send messages via SSL, you need to modify the -classpath in the start script to use the correct version of http_client.jar.
You need to replace the ORACLE_HOME/lib/http_client.jar with ORACLE_HOME/j2ee/home/lib/http_client.jar.
The MQ Series adapter is based on the IBM MA88 support pac. IBM has recently released a version 5.2.1 of it's MA88 support pac which contains the following:
MQSeries classes for Java version V5.2.1
MQSeries classes for Java Message Service (JMS) V5.2.1
The MQ Series adapter was developed based on version 5.2.0 of these classes.
The following instructions apply only if you have installed the 5.2.1 version of the MA88 support pack (or if it came on the installation CD from IBM). You can verify your version in the readme.txt file in the following directory:
/opt/mqm/java/doc/en_US
If you have 5.2.0 or earlier version installed, ignore the section below.
Version 5.2.1 introduces a dependency on the J2EE Connector Architecture exception javax.resource.ResourceException, which is defined in the MQ Series JAR file connector.jar.
MQ Series 5.2.x is available on all major UNIX operating systems except Tru64 UNIX. The latest MQ Series version available on Tru64 UNIX is 5.1
Consequently, the MQ Series adapter configuration must be modified to include this JAR file in the classpath, to avoid receiving the following error while starting the MQ Series adapter:
java.lang.NoClassDefFoundError: javax/resource/ResourceException at com.ibm.mq.MQEnvironment.<clinit>(MQEnvironment.java)
The connector.jar file can normally be found in the following directory:
/opt/mqm/java/lib
As a workaround, the last line of the start script must be changed to the following:
java -server ... -classpath /opt/mqm/java/lib/connector.jar:<previous>
Finally, the directory java/lib should be added to the OS dynamic link library path.
Modify the MQ Series adapter start script in the following way:
if [ -z "LD_LIBRARY_PATH" ] then
LD_LIBRARY_PATH=/opt/mqm/java/lib:/u01/app/oracle/product/ias902/lib export LD_LIBRARY_PATH;
else
LD_LIBRARY_PATH=/opt/mqm/java/lib:/u01/app/oracle/product/ias902/lib:{LD_ LIBRARY_PATH}
export LD_LIBRARY_PATH;
fi
|
Note: The name of the library path variable is not the same on all platforms. On HP-UX systems, replaceLD_LIBRARY_PATH with SHLIB_PATH in the previous section. On AIX systems, replace LD_LIBRARY_PATH with LIBPATH in the previous section.
|
Oracle Management Server (OMS) starts and manages Interconnect services. OMS is installed during the Infrastructure installation of Oracle 9iAS 9.0.2. When OMS is installed on IBM AIX and the value of $ORACLE_HOME (full directory path where OMS is installed into) is long, OMS is unable to start the Interconnect services, resulting in the following failures:
Service cannot be found message when selecting Interconnect services from the Oracle Enterprise Manager (OEM) Console
oracle.oai.tools.oaiconsole.emclient.OAIExtService.getOAIServiceRef error message in the $ORACLE_HOME/sysman/log/OAIClient.log file on the machine where OEM Console was run
This is a known issue, tracked by Oracle bug no. 2427401. As a workaround, the patch/bug2427401/oai_service.sh file is available on disk 1 of both the 9iAS 9.0.2 and 9iAS 9.0.2 Integration CD-ROMs to start the OMS Interconnect services. To start the OMS Interconnect services:
Copy CD_mount_dir/patch/bug2427401/oai_service.sh to the IBM AIX machine where OMS is installed. CD_mount_dir represents the mount directory of the 9iAS 9.0.2 CD no. 1 or 9iAS 9.0.2 Integration CD no. 1.
Set $ORACLE_HOME to the install home of OMS.
Enter the following command:
sh oai_service.sh
Try detecting the Interconnect services from the OEM Console.
A comma-separated values (CSV) file consists of multiple lines. Each line contains values separated by commas that end when a new line is required:
a,b,c,d 1,2,3
Two string types have been added that make it easier to parse CSV files.
termstring
String type termstring is a variation of limstring, but requires only a terminating delimiter and, not a beginning delimiter. For example:
<termstring endchar="," />
This parses any string contents until a comma is encountered.
simplestring
String type simplestring is a special data type only used when the nearest parent structure defines a valid set of delimiters, which for the current data definition description language (D3L) library is limited to limarray. For example:
<limarray contchar="," endchar="\n">
<simplestring />
</limarray>
These new string types provide two ways for parsing CSV files. The examples provided in the following sections use imparray so that input can be any number of elements, lines, or both.
All CSVs are Read into an Array
|
See Also: Appendix B, "Using the Data Definition Description Language" of the Oracle9iAS InterConnect User Guide for additional information on D3L |
With this method, all CSVs on each line are assigned to named fields (fixed number of fields per line). Example 7-1 provides an example.
Example 7-1 CSVs Assigned to Named Fields
<message name="createPhone" object="Phone" type="phoneRecord">
<imparray id="lines">
<struct>
<field name="rectype"> <termstring endchar=","/ > </field> <field name="quantity"><termstring endchar=","/ > </field> <field name="endHour"> <termstring endchar=","/ > </field> <field name="endMin"> <termstring endchar=","/ > </field> <field name="cost"> <termstring endchar="\n"/> </field>
</struct>
</imparray> <struct id="phoneRecord">
<field name="csv"> <typeref type="lines" /> </field>
</struct>
</message>
The native format message payload for Example 7-1 is as follows:
4,,9,22,2324.29 ,,,,, 55,2342,11,46,728372339.57
With this method, all CSVs on each line are read into an array (variable number of fields per line). Example 7-2 provides an example.
Example 7-2 All CSVs are Read into an Array
<message name="createPhone" object="Phone" type="phoneRecord">
<limarray id="linearr" contchar="#44" endchar="\n">
<simplestring />
</limarray> <imparray id="myArray">
<struct>
<field name="line"> <typeref type="linearr" /> </field>
</struct>
</imparray> <struct id="phoneRecord">
<field name="csv"> <typeref type="myArray" /> </field>
</struct>
</message>
The native format message payload for Example 7-2 is as follows:
4,,9,22,2324.29 55,2342,11,46,728372339.57 55,2342,11,46,728372339.57,4,,9,22,2324.29 1,2,3,4,5,6,7,8,9,0,1,2,3,4,5,6,7,8,9,0
The delimiters for limstring, termstring, and limarray have been enhanced to allow multiple characters, as well as three new encoding styles. The associated ASCII table codes are shown in parentheses:
Escaping using "\"; this works for "\r" (13), "\n" (10), "\t" (9), and "\f" (12)
where:
(13) is the ASCII code for a carriage return (CR)
(10) is the ASCII code for a line feed (LF)
(9) is the ASCII code for a horizontal tab (HT)
(12) is the ASCII code for a form feed (FF)
Escaping ASCII code using "#"; for example, "#13"
Escaping ASCII hexadecimal code using "#x"; for example, "#x0D"
Example 7-3 provides several examples.
Example 7-3 Delimiter Encoding Styles
<termstring endchar="#x2C" />
<termstring endchar="\n" />
<limarray id="linearr" contchar="," endchar="\r\n">
<simplestring />
</limarray>
"\r\n" on line 3 of Example 7-3 represents a DOS style line break.
You can download the patch file that includes D3L enhancements from OracleMetaLink.
To obtain the D3L enhancements patch:
Log into OracleMetaLink at the following Web site:
http://metalink.oracle.com
You must register online before using OracleMetaLink.
Click Patches in the left-hand column.
Enter the values defined in the following table and click Submit:
Find the patch identified as "THIS IS THE BASE BUG FOR PATCH RELEASE 9.0.2.1 - For UNIX Platforms Only."
Review the readme file before proceeding with the download. The readme file describes how to apply the patch.
Click Download to download the patch.
The following are known issues associated with Oracle Internet Directory:
Oracle Internet Directory Server May Log Extra Information When LDAP Main Page is Accessed
Updated Information for Oracle Internet Directory Port Numbers
Insufficient Privileges For Portal Installation When Not Installed as Oracle Internet Directory User
When you access the LDAP main page of EMD, the Oracle Internet Directory server may log extra information in a log file named oidldap00.log. This log file can be ignored.
In order to bring up the Oracle Internet Directory server on the default non-SSL port 389 and SSL port 636 at the end of the installation, the following conditions must hold true:
The default ports 389, 636 should not be in use.
The /etc/services file should not have any line containing these port numbers.
If either of these conditions is not met, the Oracle Internet Directory server will be brought up on a different port which is logged in the file ORACLE_HOME/ldap/install/oidca.out.
Delegated Administration Service (DAS) is deployed automatically in the infrastructure installation. In some situations, there may be a requirement to deploy DAS on a different host other than infrastructure. To deploy DAS on a different machine where the middle tier is installed, perform the following steps:
Verify that the machine has at least the core installation installed and the installation is pointing to an existing Oracle Internet Directory/SSO.
Navigate to the ORACLE_HOME/dcm/bin directory.
Create a new component using the following command:
dcmctl createcomponent -verbose -debug -ct oc4j -co OC4J_DAS
Start the component using the following command:
dcmctl start -verbose -debug -co OC4J_DAS
Deploy the DAS ear file using the following command:
dcmctl deployApplication -debug -verbose -a oiddas -f ORACLE_HOME/ldap/das/oiddas.ear -co OC4J_DAS
Perform the following steps to add the LD_LIBRARY_PATH and DISPLAY environment variables to the opmn.xml file:
Navigate to the ORACLE_HOME/opmn/conf directory and open opmn.xml in a text editor.
Add the following lines in the OC4J_DAS section of opmn.xml:
<environment> <prop name="DISPLAY" value="%hostname%:0.0"/> <prop name="LD_LIBRARY_PATH" value="%ORACLE_HOME%/lib"/> </environment>
Replace hostname and ORACLE_HOME with the appropriate values. Hostname should point to a machine where X server is running.
Note the placement of the section <environment> in the sample below:
<oc4j maxRetry="3" instanceName="OC4J_DAS" gid="OC4J_DAS" numProcs="1">
<config-file path="/home/ias902/j2ee/OC4J_DAS/config/server.xml"/>
<oc4j-option value="-properties"/>
<port ajp="3001-3100" jms="3201-3300" rmi="3101-3200"/>
<environment>
<prop name="DISPLAY" value="sandal:0.0"/>
<prop name="LD_LIBRARY_PATH" value="/home/ias902/lib"/>
</environment>
</oc4j>
|
Note: The name of the library path variable is not the same on all platforms. On HP-UX systems, replaceLD_LIBRARY_PATH with SHLIB_PATH in the previous section. On AIX systems, replace LD_LIBRARY_PATH with LIBPATH in the previous section.
|
Navigate to the ORACLE_HOME/dcm/bin directory.
Save the changes to the repository using the following command:
dcmctl updateconfig -verbose -debug -ct opmn
Restart OPMN using the following command:
dcmctl restart -verbose -ct opmn
Stop and start OC4J_DAS instance using the following commands:
dcmctl stop -verbose -debug -ct oc4j -co OC4J_DAS dcmctl start -verbose -debug -ct oc4j -co OC4J_DAS
In Oracle9iAS you can install multiple Oracle9iAS components against a shared Oracle Internet Directory. In such a case, Oracle Internet Directory administrators might prefer to install Oracle9iAS Portal as an Oracle9iAS administrator so that they do not require Oracle Internet Directory super user privileges for such an installation. Currently, you can install most components and Oracle9iAS middle tiers if you have Oracle9iAS administrators privileges in Oracle Internet Directory. However, to perform an Oracle9iAS Portal installation, you will require Oracle Internet Directory super user privileges because an incorrect Access Control Policy in Oracle Internet Directory prevents you from installing as an Oracle9iAS administrator.
As a workaround, change the Access Control Policy on one of the nodes in Oracle Internet Directory. This should be done once Oracle Internet Directory has been installed and before you attempt to install Oracle9iAS Portal as an Oracle9iAS administrator. Also, the Oracle Internet Directory identity used to perform the Oracle9iAS Portal installation should be a member of the following group:
cn=OracleDASAdminGroup,cn=Groups,<DN of Default Subscriber Oracle Context> # Ldif script to change the ACL policy on Groups container. dn: cn=Groups, <Default Subscriber DN> changetype: modify replace: orclEntryLevelACI orclEntryLevelACI: access to entry by group="cn=oracledascreategroup, cn=groups,%s_OracleContextDN%" added_object_constraint=(objectclass=orclgroup) (browse, add) by group="cn=iASAdmins, cn=Groups,<DN of subscriber Oracle Context>" (browse, add) by * (none)
Perform the following to change the Access Control Policy:
Substitute the <default Subscriber DN> in the ldif script above with the real DN of the default subscriber.
Substitute the <DN of subscriber Oracle Context> to the DN of the subscriber Oracle Context. It is usually cn=OracleContext, <default Subscriber DN>.
Save the script as temp.ldif.
Use the ldapmodify command line tool to make the change in Oracle Internet Directory. For example:
ldapmodify -p <OID port> -h <OID host> -D <DN of OID Super User> -w <password of OID Super user> -v -f temp.ldif
The following are known issues associated with Oracle9iAS Containers for J2EE:
XML-Based JAAS Demo README.TXT Refers to a Non-Existent README
Information About Updating OC4J Admin Password Using JAZN Administration Tool
Updated Information About Sharing Cached Objects in an OC4J Servlet
A customized version of the DataDirect Connect JDBC driver is shipped with Oracle9iAS to provide connectivity to non-Oracle databases. Do not use the DataDirect Connect JDBC driver outside of Oracle9iAS. You should refer to standard DataDirect documentation and release notes for technical information on the DataDirect JDBC driver. However, it is important to note the differences between the standard DataDirect JDBC driver and this customized version:
The customized DataDirect driver jar files use the YM prefix. The following DataDirect jar files are distributed with Oracle9iAS:
YMbase.jar YMinformix.jar YMsqlserver.jar YMutil.jar YMdb2.jar YMsybase.jar
The URL sub-protocol prefix is oracle. When you connect, use the correct sub-protocol. For example:
jdbc:oracle:db2://server1:1433
The package names are com.oracle.ias.
The vendor message prefix is [oias].
The customized DataDirect driver is configured to run within the Oracle9iAS product. Attempting to use the customized DataDirect JDBC driver outside Oracle9iAS, will yield the following exception:
java.sql.SQLException: [oias][... JDBC Driver]
This driver is locked for use with embedded applications.
The README.txt in the ORACLE_HOME/j2ee/home/jazn/demo/callerInfo directory has a reference to ORACLE_HOME/dcm/README, which does not exist. JAAS Readme is referenced to you from a core install at:
http:<servername>/J2EE.htm
Perform the following steps to update the OC4J admin password using the JAZN administration tool:
Make sure that your ORACLE_HOME environment variable is set and you are using the correct java from the ORACLE_HOME/jdk/bin directory.
In the ORACLE_HOME/j2ee/home directory, use the following command to change the admin password to the ias_admin password: (Here, the ias_admin password is "welcome1".)
java -Doracle.security.jazn.config=ORACLE_HOME/j2ee/home/jazn/install/jazn.xml -jar jazn.jar -setpasswd jazn.com admin welcome welcome1
Verify the change by completing the following:
java -Doracle.security.jazn.config=ORACLE_HOME/j2ee/home/jazn/install/jazn.xml -jar jazn.jar -checkpasswd jazn.com admin -pw welcome1
You should see "Successful verification of user/password pair".
The affected jazn-data.xml is located in the ORACLE_HOME/j2ee/home/config directory.
Make sure the following lines exist in the $JAVA_HOME/jre/lib/security/java.security configuration file:
auth.policy.provider=oracle.security.jazn.spi.PolicyProvider login.configuration.provider=oracle.security.jazn.spi.LoginConfigProvider
These lines make sure that Oracle9iAS JAAS is used as the provider for JAAS Login Configuration as well as Policy.
In order to take advantage of the java cache's distributed functionality or to share a cached object between servlet, some minor modification to an applications deployment may be necessary. Any user defined objects that will be shared between servlets or distributed between JVM's must be loaded by the system class loader. By default objects loaded by a servlet are loaded by the context class loader. These objects are only visible to the servlets within the context that loaded them. The object definition is not available to other servlets or to the cache in another JVM. If the object is loaded by the system class loader, the object definition will be available to other servlets and to the cache on other JVM's.
With Jserv, this was accomplished by including the cached object in the classpath definition available when Jserv process was started.
With OC4J, the system classpath is derived from the manifest of the oc4j.jar file and any associated .jars, including cache.jar. The classpath in the environment is ignored. To include a cached object in the classpath for OC4J, the .class file should be copied to ORACLE_HOME/javacache/sharedobjects/classes or added to the jar file ORACLE_HOME/javacache/cachedobjects/share.jar. Both the classes directory and the share.jar file have been included in the manifest for cache.jar.
OC4J contains a default Java Message Service (JMS) provider called OC4J/JMS (sometimes referred to as OrionJMS). Because OC4J/JMS is not fully JMS 1.02-compliant and was not used to achieve J2EE 1.3 compatibility, we recommend using the Oracle JMS (OJMS) implementation, which is provided. This JMS provider leverages Advanced Queueing (AQ) from the Oracle9i Database and is integrated into Oracle9iAS by means of a resource provider interface.
For failover to work properly in Oracle9iAS release 2 (9.0.3), you must specify the attribute setting load-on-startup="true" in the <web-app> subelement of the <web-site> element of the Web site XML file (such as default-web-site.xml or http-web-site.xml). For general information about load-on-startup, refer to the Oracle9iAS Containers for J2EE Servlet Developer’s Guide.
The following are known issues associated with Oracle9iAS Personalization:
Use HTTPS to Invoke Oracle9iAS Personalization Administrative Utility
Oracle9iAS Personalization Configuration Requires Oracle Shared Library Location
Port Numbers for Oracle9iAS Personalization Must Be Four Digits or Fewer
Restart OC4J_BI_FORMS After Running Oracle9iAS Personalization Configuration Wizard
Oracle9iAS Personalization REAPI Demo User ID and Applications Session ID Must Not Be the Same
Default Mail Server For Oracle9iAS Personalization Cannot Be Changed
Flat Taxonomies are Not Supported by Oracle9iAS Personalization
Use "https" in the URL to start the Oracle9iAS Personalization Administrative Utility. The correct URL is:
https://<mysystem>:<port>/OP/Admin
where <mysystem> is the URL of the system where Oracle9iAS Personalization is installed and <port> is the port number that was configured for Oracle9iAS Personalization.
The setupinfo.txt file located in the ORACLE_HOME/Apache/Apache directory contains a list of the configured ports.
Before configuring Oracle9iAS Personalization, add "ORACLE_HOME/lib" to LD_LIBRARY_PATH.
|
See Also: Oracle9i Administrator's Reference Release 1 for UNIX Systems for information about setting these variables. |
|
Note: The name of the library path variable is not the same on all platforms. On HP-UX systems, replaceLD_LIBRARY_PATH with SHLIB_PATH in the previous section. On AIX systems, replace LD_LIBRARY_PATH with LIBPATH in the previous section.
|
If you specify a port number for Oracle9iAS Personalization with 5 or more digits, you will not be able create an MTR connection; the Administrative Utility does not allow you to enter 5 or more digits for the port number.
You must restart OC4J_BI_FORMS after you run the Oracle9iAS Personalization Configuration Wizard. If you do not restart, the changes specified with the Wizard are not implemented.
Follow these steps to restart OC4J_BI_FORMS:
Start Oracle Enterprise Manger by opening http://<host>:1810.
In the Application Server list, click on the server where Oracle9iAS Personalization is installed.
Select OC4J_BI_FORMS by clicking the appropriate radio button.
Click the restart button.
For Oracle9iAS Personalization REAPI demo, the user ID and the application session ID must not be the same. If the values are equal, Oracle9iAS Personalization REAPI demo may fail.
You cannot change the default mail sever location for email notifications in Oracle9iAS Personalization.
Oracle9iAS Personalization does not support flat taxonomy, that is, a taxonomy where all categories derive directly from the root and none of the categories have child categories.
For a workaround, change the flat taxonomy by creating a parent category for all existing categories. Some restrictions may apply.
If LD_LIBRARY_PATH is not set when configuring Oracle9iAS Personalization, import fails to load the data to the MTR schema.
|
Note: The name of the library path variable is not the same on all platforms. On HP-UX systems, replaceLD_LIBRARY_PATH with SHLIB_PATH in the previous section. On AIX systems, replace LD_LIBRARY_PATH with LIBPATH in the previous section.
|
The following are known issues with Oracle9iAS Portal:
Oracle9iAS Portal Configuration Fails Through Oracle Enterprise Manager
Registering Oracle Portal Provider for Wireless Web Tool and Wireless Customization Fails
Oracle9iAS Web Cache Errors Occur If Templates Used by More Than 25 Pages
Working With a Oracle9i Server Release 2 (9.2.0.1.0) Database
If you does not configure Oracle9iAS Portal during install time and want to configure at a later time through Oracle Enterprise Manager, the portal configuration might fail with the following error:
"The component failed during the configuration operation. Correct any errors reported on this page and in the error logs and retry the operation."
The workaround is to manually configure Oracle9iAS Portal during postinstallation by performing the following steps:
Run the ptlem.sh script from ORACLE_HOME/assistants/opca directory.
Run the OC4J deployment tool to deploy Portal. Please refer to the Administrator's guide for details on running the OC4J deployment tool manually.
If both the infrastructure and middle-tier are installed in the same machine and the EMD running in the machine refers to the infrastructure Oracle home, the "Register Oracle Portal Provider for Wireless Web tool" and "Register Oracle Portal Provider for Wireless Customization" from the Wireless site displays "java.lang.NoClassDefFoundError" errors.
As a workaround, be sure that the Oracle9iAS Portal jars, pdk java.jar and ptlshare.jar, in the orion-web.xml of the infrastructure install point to the middle tier installation.
For example, if the infrastructure is installed in location /private/ias20_infra/ and the middle tier is installed in location /private/ias20_midtier/ then the following entries in the EMD's orion-web.xml:
<classpath path="/private/ias20_infra/portal/jlib/pdkjava.jar"/> <classpath path="/private/ias20_infra/portal/jlib/ptlshare.jar"/>
should be replaced with
<classpath path="/private/ias20_midtier/portal/jlib/pdkjava.jar"/> <classpath path="/private/ias20_midtier/portal/jlib/ptlshare.jar"/>
Please restart the opmn process for the changes to take effect.
If a template is used by more than 25 pages, one of the following two errors can occur:
Could not open web cache connection. The portal use-web-cache setting is set to ON while Web cache may be down. (WWC-40019)
General invalidation message processing exception: ORA-06502: PL/SQL: numeric or value error (WWC-40018)
This is caused by a known exception in the invalidation message processing. The workaround is to turn "OFF" Web Cache in Oracle9iAS Portal.
For more information about troubleshooting Oracle9iAS Web Cache related issues in Oracle9iAS Portal, refer to chapter eight of the Oracle9iAS Portal Configuration Guide. This guide is available on OTN, see http://portalstudio.oracle.com.
Depending on the network configuration into which Oracle9iAS is installed, it may be necessary to disable IP checking in cookie validation.
This action is necessary if HTTP access to the Portal server is through a set of proxies that do not each assert the same IP address when calling Portal. In such cases the login request that invokes the creation of the session cookie may be routed via one proxy, but subsequent requests are routed through different proxies. This raises a security violation during the IP checking step and access to the page denied.
To change the state of IP checking in cookie validation, update data in both the Portal schema and the SSO schema as detailed in Table 7-2.
Table 7-2 Enabling and Disabling IP Checking
| Action | Portal Schema | SSO Schema |
|---|---|---|
| Enable IP checking | update wwsec_enabler_config_info
|
update wwsec_enabler_config_info
|
| Disable IP checking | update wwsec_enabler_config_info
|
update wwsec_enabler_config_info
|
This information supersedes all other instructions in Oracle9iAS Portal documentation that describes how to disable IP checking during cookie validation, For example, Oracle9iAS Portal Release Notes, and Oracle9iAS Portal Configuration Guide Appendix B. These sections should now read as follows:
Oracle9iAS Portal Release Notes Section 5.5 - IP Cookie Validation Failure
Some proxy server configurations may cause cookie validation to fail. This problem, probably only observed when Portal is being accessed from outside an intranet, such as from a mobile device, causes "Invalid Session" errors to appear in the client.
The workaround is to disable the IP checking stage of cookie validation by entering the SQL detailed earlier in the section "Disabling the IP Check of Cookie Validation".
Oracle9iAS Portal Release Notes Section 7.7 - Need to Disable IP Checking if Accessing Mobile Pages
An error occurs when logging into Oracle9iAS Portal to access mobile-enabled pages on a wireless device, turn off IP-checking during the authentication sequence.
To do this, enter the SQL detailed earlier in the section "Disabling the IP Check of Cookie Validation".
Oracle9iAS Portal Configuration Guide - Appendix B
To disable the IP check of cookie validation, enter the SQL detailed in the Portal Release Note section "Disabling the IP Check of Cookie Validation".
When creating a form based on a table or view (for a Portal DB provider), specify the table/view on which to base the form. Sometimes, if you click the LOV icon to display a list of available tables/views, the following message is displayed instead:
No Response from Application Web Server There was no response from the application web server for the page you requested. Please notify the site's webmaster and try your request again later.
The workaround is to enter the name (schema.objectname) directly into the "Table or View" field, for example, SCOTT.EMP.
It is not possible to create or copy items or pages using WebDAV clients. This issue causes a duplicate item to be created with the same name with nothing in it (0 bytes). It is possible to browse all the standard pages and "file" type items created through the Oracle Portal UI. To fix this, apply a patch which will be available on OracleMetalink at:
http://metalink.oracle.com
To use a Oracle9i Server release 2 (9.2.0.1.0) database as the Oracle9iAS Portal repository, you need to use the ptlasst scripts to perform the following changes before installing the repository on the Oracle9i Server release 2 (9.2.0.1.0) database:
Resolve the errors associated with loading the soap.jar file, by running the following commands in the order listed below:
$ dropjava -user sys/change_on_install@database_connect_string mail.jar $ dropjava -user sys/change_on_install@database_connect_string\ activation.jar $ loadjava -resolve -verbose -synonym -grant PUBLIC -user sys/\ change_on_install@database_connect_string ORACLE_HOME/j2ee/home/ejb.jar $ loadjava -resolve -verbose -synonym -grant PUBLIC -user sys/\ change_on_install@database_connect_string ORACLE_HOME/lib/activation.jar $ loadjava -resolve -verbose -synonym -grant PUBLIC -user sys/\ change_on_install@database_connect_string ORACLE_HOME/lib/mail.jar
Resolve ORA-03113: end-of-file on communication channel errors associated with the Portlet Categorization Site installation and importing doc_seed by applying the patch for bug no. 2430504 on the Oracle9i Server release 2 (9.2.0.1.0) database.
The following are known issues associated with Oracle9iAS Reports Services:
Incorrect Link in Oracle9iAS Reports Services Getting Started
Reports in-process server gives REP-3000 error when running report
Oracle9iAS Reports Services Crashes When Running Reports with Graphs
Oracle9iAS Reports Services only supports the following documented syntax for the GETJOBID:
getjobid[n]
No other syntax for GETJOBbID will work in this release.
In order import a report component into Oracle9iAS Portal, you must update the import_portal_config.xml file to point to the correct Oracle home. import_portal_config.xml is located in
ORACLE_HOME/reports/templates
In the file, you need to find the following line and replace orawin90 with your Oracle home.
<template_base_dir>/orawin90/reports/templates</template_base_dir>
Any user that is created through DAS will have the shell entry created as part of the DAS create user process. If the user is not created through DAS, this shell entry will be missing in OID and the user cannot grant this privilege to themselves.
The workaround is to add the user to the access control list so they may grant access to themselves using the following command:
ldapmodify -h <host> -p <port> -D cn=orcladmin -w <adminpwd> -v -f acimod.ldif
The following are contents of acimod.ldif:
#file acimod.ldif dn: cn=Extended Properties,cn=OracleContext,dc=us,dc=oracle,dc=com changetype: modify add: orclentrylevelaci orclentrylevelaci: access to entry by * added_object_constraint=(objectClass=orclreferenceobject) (nobrowse,add,nodelete,noproxy)
To ensure that spaces and control characters are passed correctly, you may need to turn URL encoding on or off for the fields in your report. You can turn URL encoding on or off with the RW:FIELD tag in a report:
<rw:field ... urlEncode=yes|no ... />
The default value for urlEncode is no.
In JDK 1.3.1, a bug causes the bold Korean font to appear incorrectly. Oracle9iAS Reports Services uses JRE 1.3.1 and therefore all bold Korean strings in graphs within reports are incorrectly.
After installation, the Reports Server instance is not accessible from Oracle Enterprise Manager. The password set for the reports target is not the Oracle9i Application Server admin password.
Complete the following for a workaround:
Open the file ORACLE_HOME/sysman/emd/targets.xml.
Search for the reports target. The target type for reports is oracle_repserv. The target definition contains a property for Password, for example:
<Property NAME="Password" VALUE="3f769c1e7cfd7411" ENCRYPTED="TRUE"/>
Change the VALUE to be the Oracle9i Application Server admin password and set ENCRYPTED = "FALSE" for example:
<Property NAME="Password" VALUE="adminpasswd" ENCRYPTED="FALSE"/>
Search for the server name property of the Reports Server. For example, if the Reports Server is installed on the machine prod1-sun in domain us.oracle.com, it would have the following server property:
<Property NAME="Server" VALUE="rep_prod1-sun.us.oracle.com"/>
Delete the domain portion of the server name. For example, in the case above, you would remove us.oracle.com:
<Property NAME="Server" VALUE="rep_prod1-sun"/>
Restart Oracle Enterprise Manager:
# $ORACLE_HOME/bin/emctl stop # $ORACLE_HOME/bin/emctl start
Oracle Enterprise Manager automatically encrypts the password and set the ENCRYPTED flag to TRUE.
The link to the Oracle Express example in the Oracle9iAS Reports Services Getting Started is incorrect. The version of the Getting Started available on the Oracle Technology Network (http://otn.oracle.com/products/reports/) has the correct link.
The default configuration for Oracle9iAS Forms Services does not run in SSO mode. The default configuration for Oracle9iAS Reports Services does run in SSO mode.
Forms applications calling integrated Oracle9iAS Reports Services using the Forms Run_Report_Object built-in will not experience any problems when Forms is running in non-SSO mode and Reports is running in SSO mode as long as Reports Services and the requested Reports module are not registered with Oracle9iAS Portal.
Other Requirements
The property, Report Server, must be set explicitly for all report objects in a Forms module.
If a Reports server other than the default is being used, that server must be started from the command line as follows:
rwserver.sh server=<Reports server name>
The system variable, REPORTS_PATH, must be modified in the file <ORACLE_HOME>/bin/reports.sh to reference the location of Reports.
The first time a Reports server is started, it creates a configuration file called <ORACLE_HOME>/server/conf/<server_name>.conf.
The default status of a Reports server is secure. To change the Reports server status to non-secure, modify <ORACLE_HOME>/server/conf/<reports_server_name>.conf by commenting out the <security> tag and removing securityId from the <job> tags.
After making these modifications, the Reports server must be restarted.
If Forms Services is configured to run in SSO mode, then Reports requests are sent with the authid provided, based on the SSO user login.
Protected Reports and Reports Servers can be registered in Oracle9iAS Portal.
The Table 7-3 lists the possible Forms/Reports combinations and expected results:
Table 7-3 Outcome of Forms/Reports Integration when Forms is Running in SSO Mode or Non-SSO Mode
| Reports Type | Registered, Secure Reports ServerRuns Only Registered Reports | Registered, Secure Reports ServerRuns Any Reports | Non-Secure Reports Server |
|---|---|---|---|
| Reports with public access | report generated
|
report generated
|
report generated
|
| Reports with specific user access | report generated
|
report generated
|
report generated
|
| Reports with no specific user access | report not generated
|
report not generated
|
report generated
|
| Non-registered reports | report not generated
|
report not generated
|
report generated |
Reports/Express PDS is not available on AIX-Based Systems, Tru64 UNIX, HP-UX, nor Linux with this release of Oracle9i Application Server.
If an Oracle9iAS 1.0.2.2.x visibroker process is running on a server, the current version of the Reports Server might not start correctly. To check if a Oracle9iAS 1.0.2.2.x visibroker process is running, search for the oad or osagent processes. Shut down these processes before starting the Oracle9iAS Report Server.
The Visibroker Smart Agent (osagent) is not available on Tru64 UNIX. The Visibroker Smart Agent is required for communication between the Reports client and Reports server.
To use Reports Server on Tru64 UNIX, Oracle Corporation recommends that you install osagent from Oracle9i Developer Suite Release 9.0.2 on Windows NT on an NT workstation that is on the same subnet as the Tru64 UNIX Reports Server.
Make sure that the osagent is running before starting the Tru64 UNIX Reports Server. If the osagent on NT workstation is not on the same subnet as the Tru64 reports server or osagent is not running, then the Reports server might not work properly
To start the osagent on Oracle9i Developer Suite Release 9.0.2 on Windows NT, simply go to the ORACLE_HOME\vbroker4\bin directory and run the following command:
Command prompt> osagent
To run osagent on particular port, run the following command:
Command prompt> osagent -p <port number>
To confirm osagent is running, run the following command:
Command prompt> osfind
This command displays a list of hostnames where osagent is running. It is possible that the list might be empty, in which case osfind has been unable to locate any other instances of osagent running on the subnet.
Oracle9i Developer Suite is not supported on AIX-Based Systems or Tru64 UNIX. Please use Oracle9i Developer Suite on Windows as your Reports development environment.
You might see the following message associated with the Reports binaries on Tru64 UNIX:
Unalligned access pid=xxxx .....
To avoid this message, run the following command:
$ /bin/uac p noprint
As part of Reports Backward Compatibility Support, 6i CGI should be able to use 9i Reports Server. To use this feature on AIX, you must apply the patch for bug no. 2413270, to be available in Automated Release Updates.
When running a sample report using the report in-process server, an error message like the following can appear in the browser:
REP-3000: Internal error starting Oracle Toolkit. REP-3000: Internal error starting Oracle Toolkit.
Use the following sample URL to test for this error message using the appropriate hostname, domainname, port and two_task entries:
http://hostname.domainname:port/reports/rwservlet?report=test.rdf&userid=scott/tiger@two_task&destype=cache&desformat=htmlcss
If the REP-3000 error message appears, the display is not set correctly. When running a report server from the command line, the environment variable DISPLAY setting is used. However, the reports in-process server uses the following configuration file for the display setting:
$ORACLE_HOME/j2ee/OC4J_BI_Forms/config/oc4j.properties
The default display entry is as follows:
oracle.display=:0.0
On some servers, there might not be an X server running on :0.0 or this entry might not be resolved correctly. In such cases, change the display setting to a machine where an X server is present and can be accessed by this server.
To test whether an X server is running on given machine and you have permissions to connect to it, you can use the following command:
xterm -display myserver:0.0
If you do not have permissions to access the display or if there is no such display running on the given machine, an error similar to the following is displayed:
Xlib: connection to "myserver:0.0" refused by server Xlib: Client is not authorized to connect to Server xterm Xt error: Can't open display: myserver:0.0
Once you have identified a machine with a valid X server, or started the display on the server machine being used, you can change the default entry to the new display. For example to use the X server running on myserver:0.0 we would change the default entry to:
oracle.display=myserver:0.0
After these changes are completed, it is necessary to restart the Forms/Reports oc4j instance with the following commands:
$ cd $ORACLE_HOME/opmn/bin $ ./opmnctl stopproc type=oc4j instancename=oc4j_bi_forms $ ./opmnctl startproc type=oc4j instancename=oc4j_bi_forms
You can now test the sample URL again to make sure that the in-process server works correctly. When using the sample URL, the sample test.rdf report should be displayed in the browser.
On UNIX, Oracle9iAS Reports Services fails to run reports that contain graphs built with the Business Intelligence Graph Bean. The problem is caused by a conflict in X libraries linked against the Business Intelligence Graph Bean and those linked against the Oracle9iAS Reports Services shared library.
The workaround is to re-link the shared library against the latest version of libXm:
Edit the following file:
ORACLE_HOME/reports/lib/env_reports.mk
Change the following line:
(MOTIFHOME)lib/libXm.so.3
to look like this line:
(MOTIFHOME)lib/libXm.so
Re-link the Reports shared library:
make -f cus_reports.mk sharedlibs
During installation, if the Reports Configuration Assistant fails and gives the following message:
Process destroyed exception (in the installer configuration palette)
then perform the following procedures:
Remove Security Page:
Log on to Oracle9iAS Portal.
Click Builder.
Click Navigator.
Click Contents for the Portal Design-Time Pages page group.
Click Pages.
Click Delete for the Oracle Reports Security page.
Remove Security Provider:
Log on to Oracle9iAS Portal.
Click Builder.
Go to the Build tab by clicking Build.
In the Providers portlet, type ORACLE REPORTS SECURITY in the name field.
Click Delete.
Run rwaddpag.sql:
Log on to the Oracle Internet Directory and obtain the Oracle9iAS Portal user database password.
Log on to the metadata repository as the Oracle9iAS Portal user and run the following script:
ORACLE_HOME/portal/admin/plsql/wwd/rwaddpag.sql
This creates the Reports portlet in Oracle9iAS Portal.
Alternatively, you can create a tnsnames entry and execute the script as the Oracle9iAS Portal user with the user password obtained from the Oracle Internet Directory in Step 1.
When you run JSP reports from Oracle9iAS Portal, you need to have a complete path for the CSS file because Oracle9iAS Reports Services and Oracle9iAS Portal have different virtual directories. For example, if you use css/my.css for a JSP report in Oracle9iAS Portal, the browser will construct the URL as follows:
http://<server>:<port>/<portal-path>/css/foo.css
This URL will not work. The URL needs to be as follows, which requires you to enter a fully qualified path in the JSP report:
http://<server>:<port>/reports/css/foo.css.
The following are known issues associated with Oracle9iAS Single Sign-On:
The ssocfg.sh script is used to change the host, port, or protocol of the single sign-on server, as explained in Chapter 2 of the Oracle9iAS Single Sign-On Administrator's Guide.Script can be executed only if the environment variable LD_LIBRARY_PATH includes the value ORACLE_HOME/lib.
|
Note: The name of the library path variable is not the same on all platforms. On HP-UX systems, replaceLD_LIBRARY_PATH with SHLIB_PATH in the previous section. On AIX systems, replace LD_LIBRARY_PATH with LIBPATH in the previous section.
|
In Oracle9iAS requests that are forwarded to the Single Sign-On Server for authentication can only use the HTTP method GET. If an application that is using OSSO utilizes methods other than GET, then the first page that is authenticated should be a GET. Also, the idle timeout feature should be disabled to insure that future requests that may potentially not be GET are not forwarded to the Single Sign-On Server.
The following are known issues associated with Oracle9iAS Web Cache:
If you do not configure Oracle9iAS Web Cache during installation and want to configure it at a later time using EMD, then Oracle9iAS Web Cache may fail to start. This might happen due to port conflicts with another Oracle9iAS Web Cache running on the same machine.
As a workaround, modify the Oracle9iAS Web Cache listen port number for SSL and non-SSL by logging into the Oracle9iAS Web Cache administration GUI and starting Oracle9iAS Web Cache. Since Oracle9iAS Web Cache was not configured during installation, some additional configuration steps are required to change the PORT directive in httpd.conf to the Oracle9iAS Web Cache port number.
|
See Also: "Directives to Oracle HTTP Server" section in the Oracle9iAS Web Cache Release Notes. |
Also, depending on the site configuration, change the Oracle9iAS Web Cache listen port value in ORACLE_HOME/webcache/webcache.xml and ORACLE_HOME/sysman/emd/targets.xml.
The following are known issues associated with Oracle9iAS Web Services:
A patch kit for UDDI v1.0 compliance of the Oracle9iAS UDDI registry can be downloaded from OracleMetalink at:
http://metalink.oracle.com
Follow the README.TXT in the top-level directory of the patch kit for installation and verification instructions.
When installed, this patch provides full UDDI v1.0 publishing support for the Oracle9iAS UDDI registry. Client applications can publish UDDI data, such as business information and WSDL for a Web service, to the Oracle9iAS UDDI registry programmatically via SOAP. For the convenience of client-side Java development environments, the Java APIs for UDDI, supplied with Oracle9iAS
Oracle9iAS includes the full set of UDDI v1.0 publishing capabilities.
The README for Oracle9iAS SOAP stock quote sample is outdated. Keep in mind of the following information when working with this sample.
You can also start OC4J using dcmctl.
Replace orion.jar with oc4j.jar.
To run stock quote sample behind the firewall:
If starting OC4J with dcmctl, define proxyHost and proxyPort in j2ee/home/config/oc4j.properties by adding the following lines:
proxyHost=<proxy host> proxyPort=<proxy port>
If starting OC4J on command line, define the proxy properties with the following information:
java -DproxyHost=<proxy host> -DproxyPort=<proxy port> -jar oc4j.jar
The following client programs for the Oracle SOAP Stored Procedure sample demo need to modified before compilation in order to run:
<ORACLE_HOME>/soap/samples/sp/company/ChangeSalary.java <ORACLE_HOME>/soap/samples/sp/company/GetAddress.java <ORACLE_HOME>/soap/samples/sp/company/GetEmp.java <ORACLE_HOME>/soap/samples/sp/company/GetEmpInfo.java <ORACLE_HOME>/soap/samples/sp/company/RemoveEmp.java
All these programs use java.math.BigDecimal as one of the input parameters of the SOAP call. Any reference to java.math.BigDecimal.class should be changed to int.class.
The following are known issues with Oracle9iAS Wireless:
Registering Oracle Portal Provider for Wireless Web Tool and Wireless Customization Fails
Generic Single Sign-On Errors Encountered When Using Microsoft Internet Explorer
Oracle9iAS Wireless Modules: Important Information About an Upcoming Patch
Oracle9iAS Wireless Process Status Unavailable for Multiple ORACLE_HOMEs with External Repository
If both the infrastructure and middle tiers are installed on the same machine, and the Enterprise Manager daemon running on that computer is referring to the infrastructure home, then the "Register Oracle Portal Provider for Wireless Webtool" and "Register Oracle Portal Provider for Wireless Customization" from the Wireless site will throw "java.lang.NoClassDefFoundError" errors.
In the orion-web.xml file of the infrastructure install, pdkjava.jar and ptlshare.jar should refer the middle tier installation location.
For example, if the infrastructure is installed in: /private/ias20_infra/
and the middle tier is installed in: /private/ias20_midtier/
then the following entries in the Enterprise Manager daemon orion-web.xml:
<classpath path="/private/ias20_infra/portal/jlib/pdkjava.jar"/> <classpath path="/private/ias20_infra/portal/jlib/ptlshare.jar"/>
should be replaced with:
<classpath path="/private/ias20_midtier/portal/jlib/pdkjava.jar"/> <classpath path="/private/ias20_midtier/portal/jlib/ptlshare.jar"/>
Restart the opmn process for the changes to take effect.
There is a generic error that affects some Oracle9iAS components, including Oracle9iAS Wireless. This errors occur when you use Microsoft Internet Explorer to access the Web tool on a machine that has both infrastructure and a middle tier installed on it. You may encounter the following errors:
When you log onto the webtool (entering username and password, and clicking the Login button), an SSO warning (error) appears. Click the Refresh button on your browser to continue.
From the Oracle9iAS Wireless User Manager, clicking the Create button causes an SSO warning (error) to appear. You must click the Back button in Microsoft Internet Explorer to proceed (clicking the Refresh button WILL NOT enable you to continue as it does in the previous situation above).
SimpleImage supports an alt attribute which provides alternate text for display devices, and an alternate .wav file for the voice deviceclass devices. For example:
<SimpleBind>
<SimpleMatch> </SimpleMatch> <SimpleTask> </SimpleTask> <SimpleDisplay>
<SimpleTextItem deviceclass="voice">
<SimpleAudio src="http://somehost/audio.wav"/>
</SimpleTextItem> <SimpleTextItem deviceclass="pda, microbrowser">
Hello welcome
</SimpleTextItem>
</SimpleDisplay>
</SimpleBind>
The Modules included in this production release are complete and functional. There are, however, important updates to the modules that will soon be released as a patch.
You can use the Modules as they are, but be advised that the patch will make significant database and other changes, requiring you to discard previous end-user personalization information. You will not be able to migrate your previous information when you install the patch.
The Web Component Developer is a java-based GUI tool that allows you to create Web Components that can be delivered by the Web Component Provider, as Wireless Services. There is a known issue of the Web Component Developer in the generation of Web Component Definition files. This renders the developing of composite Web Components not possible. This known bug is scheduled to be fixed and delivered to customers via the Automated Release Updates.
In Oracle9iAS wireless applications cannot be clustered using the Oracle9iAS clustering mechanism. However, it is still possible to configure Oracle9iAS such that a high availability deployment can be achieved. Complete the following steps for high availability deployment.
|
Note: Remember to back up all files before you modify them. |
Install the Oracle9iAS infrastructure on a machine and install multiple middle tiers on separate machines. Ensure that each of these middle tier installations point to the infrastructure.
Shut down DCM and all process by running the following command:
ORACLE_HOME/dcm/bin/dcmctl stop
Shut down Oracle Enterprise Manager by running following the command:
ORACLE_HOME/bin/emctl stop
Verify that the file ORACLE_HOME/opmn/conf/ons.conf on each of the middle tiers and on the infrastructure contains IP address entries for all the other tiers. If not, file and add missing IP-address entries.
On each middle tier, increase the number of processes that need to participate in the default island for the OC4J_Wireless OC4J instance to the desired number. This can be done from the EM console or by modifying the file ORACLE_HOME/opmn/conf/opmn.xml.
|
See Also: Oracle9iAS Containers for J2EE documentation for details and concepts of OC4J instance and islands. |
For instance, if you modify opmn.xml, a typical entry to start four OC4J processes in the default island would be of the form:
<oc4j maxRetry="3" instanceName="OC4J_Wireless" gid="OC4J_Wireless" numProcs="4">
In the mod_oc4j configuration file for each middle tier (that is: ORACLE_HOME/Apache/Apache/conf/mod_oc4j.conf), modify the mount point entries for the Wireless runtime. If two middle tiers (M1 and M2) are used, the entries should be of the form:
Oc4jMount /ptg instance://m1.c1.mysite.com:OC4J_Wireless,m2.c2.se4637-u-sr006.us.oracle.com:OC4J_Wireless
and
Oc4jMount /ptg/* instance://m1.c1.mysite.com:OC4J_Wireless,m2.c2.se4637-u-sr006.us.oracle.com:OC 4J_Wireless
where c1 and c2 are the respective Oracle9iAS instance names and can be determined by running the command:
ORACLE_HOME/dcm/bin/dcmctl whichInstance
These entries should be exactly the same for all middle tier machines.
Run ORACLE_HOME/dcm/bin/dcmctl updateConfig to update the DCM repository with the configuration file changes.
On slow machines, it is likely that a DCM error (timeout) of the form ADMN-906005 is displayed. If this occurs, run the command ORACLE_HOME/dcm/bin/dcmctl getReturnStatus and wait until the command exits. This confirms that the changes have been propagated to the DCM repository.
Add the tag <cluster-config/> under the <orion-web-app> tag in the following file:
ORACLE_HOME/j2ee/OC4J_wireless/application-deployments/ptg/ptg-web/orion-web.xml.
Start DCM and all processes by running the following command:
ORACLE_HOME/dcm/bin/dcmctl start
Start EM by running the following command:
ORACLE_HOME/bin/emctl start
Configure a hardware load-balancer to point to the middle tiers.
Currently, high availability support is only available for the core server runtime (by default mapped to the URI /ptg/rm).
|
See Also: Oracle9iAS Containers for J2EE documentation for more information. |
When installing both middle and infrastructure tiers on the same machine and changing the Wireless schema from the Enterprise Manager console to point to a schema other than the one available as part of the infrastructure install, the Wireless process status changes are not displayed on the Enterprise Manager console. This problem occurs on all platforms.
Here is the workaround for this problem:
From the ORACLE_HOME of the middle-tier for which the schema has been changed, copy the following fragment from the file
<middle-tier ORACLE_HOME>/config/iasschema.xml
and paste it over (overwrite) the corresponding entry in the infrastructure ORACLE_HOME file
<infrastructure ORACLE_HOME>/config/iasschema.xml <SchemaConfigData> <ComponentName>Wireless</ComponentName> <BaseName>WIRELESS</BaseName> <Override>true</Override> <SchemaName>the new schema name</SchemaName> <DBConnect>the new DB connect string</DBConnect> <Password>the new DB password (encrypted)</Password> </SchemaConfigData>
Restart Enterprise Manager after this is done.
The following are known issues associated with Oracle Ultra Search:
Oracle Ultra Search schedule might fail in an Ultra Search instance created as a SSO user.
To workaround this issue, grant the database user the Ultra Search super user privilege ('wkproxy'). To do this, complete one of the following:
Log on to SQLPLUS as "wksys" or "sys", and type the following:
exec wk_adm.grant_sysadmin('WKPROXY')
or,
Log on to Ultra Search admin as a Ultra Search super user, for example, "orcladmin", "Portal", or "wksys".Then go to the "Users" tab and "Super-Users" subtab. Select user type as "Database User", and the user name as "wkproxy", and click Add.
Perform the above mentioned workaround before a SSO user creates Ultra Search instances. Otherwise, the schedule will failed for the Ultra Search instance created by a SSO user.
Note that Ultra Search instances created by a database user will not experience the schedule failure problem. A database user can go to
http://<hostname>:<port>/ultrasearch/admin/index.jsp
where hostname:port should point to your Oracle9iAS instance to create a Ultra Search instance.
Ultra Search provides the SQL script wk0upgrade.sql for migrating the user data and database objects from an existing Ultra Search 9.0.1 database to a migrated Ultra Search 9iR2 database. However, users will generate errors when running into the stage "stop all of the crawler schedules and database jobs". Also, the script may fail and stop during the stage "re-creating all of the user instances". You can request for a patch to fix this problem.
The following are known issues associated with Oracle9iAS Unified Messaging:
Oracle9iAS Unified Messaging supports multiple e-mail domains on a single instance of the message store.
To add a new e-mail domain, perform the following steps:
Create a new subscriber entry and associated directory information tree elements in Oracle Internet Directory.
The new subscriber objectclass and naming attribute can be configured per the customer's requirements. For example, customers can use domain objectclass with dc as the naming attribute for the subscriber, or it can be organization objectclass with o as the naming attribute for the subscriber, or it can be something else depending on the requirements.
|
Note: Each Oracle Internet Directory subscriber required for an Oracle9iAS Unified Messaging namespace is equivalent to an e-mail domain. To avoid confusion between e-mail subscribers and Oracle Internet Directory subscribers, the Oracle Internet Directory subscribers of the Object class domain are referred to as domains in this section. |
Create a new e-mail domain in Oracle9iAS Unified Messaging and provision the users to have e-mail access.
Creating a new Domain in Oracle Internet Directory
The directory administrator should use the following steps to create a new domain in Oracle Internet Directory:
Determine the deployment-specific domain defaults:
The naming attribute of the domain. (orclSubscriberNicknameAttribute)
The deployment specific objectclass associated with the naming attribute.
The common parent entry of all domains in the DIT. (orclSubscriberSearchBase)
This information can be determined by querying the following entry in the root OracleContext: cn=common,cn=products,cn=oraclecontext, using the following command:
ldapsearch -h <host> -p <port> -s base \ -b "cn=common,cn=products,cn=oraclecontext" \ "objectclass=*" orclSubscriberSearchBase orclSubscriberNicknameAttribute
For example, the out-of-box defaults for a directory deployment on a host with a DNS name of machine1.acme.com are:
orclSubscriberSearchBase: dc=com
orclSubscriberNicknameAttribute: dc
Based on the nickname attribute of dc, the deployment specific objectclass chosen here is domain.
Invoke the create_subscriber.sh script to create the domain:
Login to the infrastructure ORACLE_HOME in which Oracle Internet Directory is running
Change directory to ORACLE_HOME/ldap/schema/oid
Run create_subscriber.sh script
For example, to create a domain called NewCompany using the out-of-the-box defaults for a directory server running on a host with a DNS hostname of machine1.acme.com, invoke the create_subscriber.sh script as follows:
./create_subscriber.sh -host machine1.acme.com -port 389 -SubscriberName NewCompany \ -SubscriberNamingAttribute dc \ -SubscriberObjectclass domain \ -SubscriberParentDN dc=com \ -CurrentUserDN cn=orcladmin \ -CurrentUserPassword <SuperUserPassword>
This creates a new domain in Oracle Internet Directory with the DN of dc=NewCompany,dc=com. Oracle software expects to find users for this domain under the DN cn=users,dc=NewCompany,dc=com.
Provisioning Users in the New Domain with E-mail Access
Once the new domain has been created in Oracle Internet Directory, create the associated e-mail domain and users through the Oracle9iAS Unified Messaging administration tool.
|
See Also: Chapter 3, of the Oracle9iAS Unified Messaging Administrator's Guide |
On most UNIX systems, sendmail is configured by default and is started when the system comes up. To enable the SMTP server to listen to the default SMTP protocol port (port 25), sendmail must to be shutdown.
Run the following command as root to shut down sendmail:
For HP:
/sbin/init.d/sendmail stop
For Linux:
/etc/init.d/sendmail stop
For Tru64 UNIX:
/sbin/init.d/sendmail stop
For AIX:
/stopsrc -s sendmail
To prevent sendmail from restarting if the system is rebooted, remove the sendmail startup from the OS init files. If no other application running on that server uses it, rename the sendmail executable under /usr/lib.
On HP-UX and AIX systems, the database listener must be configured to use extproc32 for external procedure agent callouts:
Modify the listener.ora file of the database installation to set the program parameter to extproc32 instead of extproc as follows:
(program=extproc32)
Restart the listener.
You might see the following error message in the Oracle9iAS Containers for J2EE (OC4J) log file while running Java Messaging Service application:
# # HotSpot Virtual Machine Error, Internal Error # Please report this error at # http://java.sun.com/cgi-bin/bugreport.cgi # # Error ID: 43113F32554E54494D45110E43505002D3 # # Problematic Thread: prio=1 tid=0x6c40f320 nid=0x6f6d runnable #
This is a result of a known bug in JDK1.3.1_02 on Linux.
