Oracle9iAS Portal Configuration Guide Release 3.0.9 Part Number A90096-01 |
|
This chapter lists possible solutions to errors that you may encounter while installing or using Oracle Portal.
Specific topics covered include:
If you are having any problems installing Oracle Portal, make sure that your system meets the system requirements in Chapter 1, "Verifying Requirements".
Always check the installation session log that describes the actions performed and the components created upon installation.
The log file is located in:
<ORACLE_HOME>/assistants/opca/install.log
To troubleshoot any issue, first identify which component of Oracle Portal may be causing the problem. The following is a quick checklist for identifying the component where the problem may likely be occurring:
http://host.domain:port
in your Web browser. Failure to access indicates an issue with the Oracle HTTP Server powered by Apache listener. For more information, see Section A.1.1, "Oracle HTTP Server Configuration File (httpd.conf)".
httpd_error.log
file. Note that externally, the server is addressed with the default port 80; however, internally, the server.company.com
is listening on port 7777. For more information, see Using the PL/SQL Gateway which is provided as part of the Oracle9i Application Server documentation set.
http://host.domain:port/pls/admin_/
in your Web browser. Failure to access indicates an issue with the PL/SQL Gateway (Apache mod_plsql) or its configuration. Check the DAD settings in mod_plsql and verify the username, password, and connect strings for both the Oracle Portal DAD and the Login Server (SSO) DAD. See Section A.1.3, "Database Access Descriptor (DAD) Configuration File (wdbsvr.app)".
http://host.domain:port/servlet/IsItWorking
in your Web browser. Failure to access indicates an issue with the Apache JServ. Most internal server errors are related to Apache JServ's failure to start due to a port conflict. Check the Apache JServ log files for more details. The log files are located in <ORACLE_HOME>/Apache/Jserv/logs
.
The Apache log files are located in the following directories:
Apache listener log file |
|
Apache JServ log file |
|
where <ORACLE_HOME>
is the location of your Oracle9i Application Server.
Try accessing Oracle Portal as described in Section 2.4, "Accessing Oracle Portal in Your Browser". If you still cannot connect to Oracle Portal and have just completed the installation, use the diagnostics tool or see Section 8.5, "Troubleshooting Oracle Portal".
The diagnostics tool locates any Oracle Portal configuration problems involving a single installation. Thus, this tool is not useful in a distributed Oracle Portal environment with multiple nodes.
Many of the portal connection problems occur because the ssodatan
script did not populate the configuration information in the Login Server when run.
To use this tool, verify that the following conditions exist:
webdb30/admin/plsql
(Oracle Portal version 3.0.6 and below) or portal30/admin/plsql
(version 3.0.6 and above) to run this tool. The owner must also have file creation privileges in the directory containing the diagnostics tool.
Many Oracle Portal connection problems arise due to a misconfiguration in the Login Server. During an Oracle Portal installation, the ssodatan
script is responsible for associating the Oracle Portal installation node with the appropriate Login Server and populating the enabler tables. However, if this script fails, the diagnostics tool can read the configuration information in both the Oracle Portal schema and the Login Server schema. A diagnostic report provides any missing information in these tables. In addition, this tool reads the configuration information for the partner applications from the Login Server.
For the URLs stored in both the partner enabler configuration information and the partner application configuration information, it performs the following checks:
The following is a list of problems that the diagnostics tool does not detect:
In Oracle Portal 3.0.8.5.3 and above, when the diagnostics tool is running, the Java class, Diagnose.class
, and the PL/SQL package, wwsec_diagnostics
, are loaded into the database.
If you are running an earlier Oracle Portal version, download the Java archive file, diag.jar
, from the Oracle Technology Network to your Oracle Portal installation location (portal30/admin/plsql
) and run the following command to extract the files (you can also use WinZip):
jar -xvf diag.jar
The wwc
directory is created if it does not already exist.
You run this tool from the command line:
diag.csh
diag.cmd
diag.csh -s portal30_schema -p portal30_schema_password -c connect_string
The diagnostics tool also provides any recommendations to the user based on these tests.
The diagnostics report, diag.txt, is created when the diagnostics command is run. Below is a sample report output.
Diagnostics Report v 1.0: Oracle Portal v 3.0.8.6.5 As of 14-Dec-2000 15:33:01 Schema Name: SM1 SSO Schema Name: sm1_SSO SM1.wwsec_enabler_config_info$ Login Server URL : http://host.domain.com:3000/pls/sm1_sso/sm1_SSO.wwsso_app_admin.ls_login DAD : sm1_sso Host connection : successful. mod_plsql : working. JServ : working. Schema name : sm1_sso Connect string : orcl Authentication mode : Single Sign-On sm1_sso.wwsec_enabler_config_info$ Login Server URL : http://host.domain.com:3000/pls/sm1_sso/sm1_SSO.wwsso_app_admin.ls_login DAD : sm1_sso Host connection : successful. mod_plsql : working. JServ : working. Schema name : sm1_sso Connect string : orcl Authentication mode : Single Sign-On ********************************** Partner Application Information **** Oracle Portal (sm1) **** Home URL : http://host.domain.com:3000/pls/sm1/sm1.home Success URL : http://host.domain.com:3000/pls/sm1/sm1.wwsec_app_priv.process_signon DAD : sm1 Host connection : successful. mod_plsql : working. JServ : working. Schema name : sm1 Connect string : orcl Authentication mode : Single Sign-On **** The Login Server (sm1_SSO) **** Home URL : http://host.domain.com:3000/pls/sm1_sso/sm1_SSO.home Success URL : http://host.domain.com:3000/pls/sm1_sso/sm1_SSO.wwsso_home.process_signon DAD : sm1_sso Host connection : successful. mod_plsql : working. JServ : working. Schema name : sm1_sso Connect string : orcl Authentication mode : Single Sign-On ********************************************* Diagnostics completed successfully!
When you are planning an installation or troubleshooting an Oracle Portal configuration problem, be aware of the various configuration control points which are discussed in Appendix A, "Oracle9i Application Server Configuration Files". For your convenience, the following table is provided below:
Configuration File/table | Location or Description |
---|---|
Oracle HTTP Server |
|
Apache JServ |
|
PL/SQL Gateway |
|
Database Connection |
|
Login Server enabler table |
Oracle Portal and Login Server's configuration table, |
Login server configuration table |
Login Server's Partner Applications configuration table, |
Local HOSTS file |
This file resolves IP names to IP addresses. On Windows NT, this file is at |
|
For more information, see Appendix B, "Oracle Portal Installation and Configuration Scripts". |
where <ORACLE_HOME>
is the location of your Oracle9i Application Server installation.
Depending on your Oracle Portal version, the default location of your installation files is as follows:
Oracle Portal 3.0.6 |
|
Oracle Portal 3.0.7 and above |
|
The following lists configuration errors and problems.
Problem or Error | |
---|---|
Error: The enabler configuration table, WWSEC_ENABLER_CONFIG_INFO$, does not have any entries. |
|
Error: There are invalid packages in the Oracle Portal schema. |
Problem or Error | |
---|---|
Cause |
The Oracle Portal Configuration Assistant did not detect any entries in the |
Solution |
Check the Oracle Portal installation and configuration log file for other errors. Additional errors in the log file are usually an indication that there is a more fundamental problem with the way the database is configured.
If there are no other errors, fix this problem by running the |
Cause |
The Oracle Portal Configuration Assistant did not find the Login Server schema in the database after the configuration was complete. |
Solution |
Check the Oracle Portal installation and configuration log file for other errors. Additional errors in the log file are usually an indication that there is a more fundamental problem with the way the database is configured. When the Login Server schema is not created, the configuration process generates a large number of errors which typically appear at the top of the log file. Once the problem has been determined and fixed, deinstall Oracle Portal and rerun the Configuration Assistant. See Section 2.7, "Deinstalling Oracle Portal". |
There are several potential reasons for this error message. Each reason is listed below with a corresponding solution.
Reason 1 |
The hostname specified in the |
Solution |
Modify the "servername" setting in the |
Reason 2 |
The SSOHash class has not been loaded into the database. Check this by running the following query in SQL Plus: select * from all_objects where object_type is like 'JAVA CLASS' |
Solution |
Manually load the SSOHash class using the following command: loadjava -resolve -user <PORTAL_SCHEMA>/<PORTAL_SCHEMA>@<CONNECT> SSOHash.class
where |
Reason 3 |
The |
Solution |
Increase the
Also, shutdown and restart your database anytime changes to the |
Reason 4 |
If you are installing or configuring Oracle Portal manually, then the URL may have been mistyped when running the |
Solution |
Rerun the |
Reason 5 |
An alias which is defined in the Apache configuration causes Apache to translate |
Solution |
Remove all such aliases from your Apache configuration file, |
Reason 6 |
The default domain is not set in the Apache configuration. When this occurs, only the hostname is shown in the Login link and the domain is not included. |
Solution |
Define the default domain in the Apache configuration file, |
Reason 7 |
The default HTTP port (port 80) was specified during installation, configuration, or when running the Unfortunately, Apache, and some browsers, drop the :80. |
Solution |
Run the |
Reason 8 |
Mismatch in the case of the hostname in Oracle Portal and Apache. |
Solution |
Change the hostname to all lowercase in: Oracle9iAS_Home/Apache/Apache/conf/httpd.conf |
Cause |
An incorrect proxy value may be specified if running within a firewall. |
Solution |
Verify that the proxy is properly set on the Global Settings page in Oracle Portal which is accessed from the Services portlet on the Administers tab page. Click the Administer tab on the Portal Home Page. In the Proxy Server section, provide appropriate values for the HTTP Server, HTTP Server Port, and No Proxy Servers for Domains beginning with fields. See Section 6.5.1, "Step 1: Set up the Global Page Settings". |
Cause |
This is not a time out of the content being returned from the request. This message occurs when a connection problem occurs and may appear for any of the following reasons: A connection is refused due to a server being down, overloaded, or a machine not found, and the like. A connection is closed during communication due to some type of instability with the machine, network, or listener. A connection takes too long to establish due to a DNS lookup, slow network, slow listener, and the like. The latter is usually the cause of this error. However, the first reason occurs occasionally with Web providers that do not having their listener up and running. |
Solution |
There is a parameter that can be set in the JServ configuration file,
The time in seconds serves as the a stalling mechanism for the connection. The default in the code is 10 sec, which may be insufficient if the DNS is taking too long. Normally, a connection is established almost immediately. However, if more time is required to establish the connection, a higher value can be entered. For example, entering a value of 20 sec or more may get things running. However, the higher the stall time set, the lower the performance. If the problem persists, locate the underlying reason for the connection failure. In the case of DNS, it may be a faster DNS server, or a bigger cache on the machine. It could be a port problem where there are not enough ports available for function. This may be related to File Descriptors on a UNIX box. See also: Section A.1.2, "JServ Configuration File (zone.properties)". |
If you encounter any errors while creating an interMedia Text index, first check the following:
Cause |
This error may display when you try to access the Oracle Portal home page and National Language Support (NLS) files are missing. |
Solutions |
You can solve in any of the following ways:
|
|
Copyright © 2001 Oracle Corporation. All Rights Reserved. |
|