Oracle Portal Configuration Guide Release 3.0.8 Part Number A87566-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 documented.
Always check the installation session log that describes the actions performed and the components created upon installation. Check the log file for ORA and PLS errors that may have occurred during installation.
The log file is located in the following location:
<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:
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 "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 refer to the "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:
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. Run -xvf diag.jar
to extract the files. 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, WWSEC_ENABLER_CONFIG_INFO$. |
Login server configuration table |
Login Server's Partner Applications configuration table, |
Local HOSTS file |
The HOSTS file is used by Microsoft TCP/IP stack for your Windows operating system and is typically located in the Windows directory on your local machine. |
|
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 is a list of errors and page references to their solutions which are grouped according to the problem you are encountering.
Problem or Error |
---|
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 "Deinstalling Oracle Portal". |
Cause |
The Database Access Descriptor (DAD) for
Oracle Portal may be incorrect or the TNS names entry used in the DAD is
not defined in the |
Solution |
Verify the DAD configuration by entering the following URL:
For details, see "Accessing the Gateway DAD Configuration Page". Make sure that the connect string information for the database is correct and the same when connecting through SQL*Plus. If you have multiple Oracle Homes, confirm
that the appropriate connect string is added to Also, for UNIX, check the following file to verify that the appropriate ORACLE_HOME is being used:
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. |
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 |
Cause |
This may occur when mod_plsql cannot connect to the database because the maximum number of database sessions has been reached. The database connection pool in mod_plsql is not shared across Apache processes meaning each process maintains its own pool.The total number of database connections pooled in Apache mod_plsql is directly related to the number of Apache processes that are spawned off and the number of DADs used to access different PL/SQL applications. The PL/SQL Gateway (mod_plsql) pools one database session per DAD per Apache process. Simply stated, the maximum number of database sessions that is pooled by mod_plsql is calculated as follows:
Currently on Windows NT/2000, since Apache is multi-threaded, all threads share the same database connection pool. The maximum number of database sessions that is pooled by mod_plsql on Windows NT is calculated as follows:
Ideally, every thread can take advantage of a database session created by another thread. Thus, on platforms where Apache is not multi-threaded, it is important that it be tuned carefully. |
Solution |
The Apache process configuration requires tuning so that processes are not started up or shutdown heavily (each process takes down its connection pool, and a new process needs to replenish its pool). This tuning is governed by the load on the Web server. The maximum number of database sessions
needs to be setup according to the maximum number of Apache processes
expected. Edit the following parameters in the
This configuration ensures that Apache processes are very rarely shutdown and the overhead of creating an Apache process/new database connection is greatly reduced. |
Solution |
Check the One way to verify that you have this
problem is to connect as SYS through SQL*Plus, and issue the query |
Solution |
Configure a separate Apache Listener to handle only PL/SQL requests.The main Apache Listener can be used to redirect all PL/SQL requests to the new listener. For the new Oracle9i Application Server listener, specify a low number for the Apache processes parameter since it only handles PL/SQL requests. Thus, the database session numbers are kept to a minimum. See "Setting the Number of Requests That Can Be Handled by the Apache Listener". |
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: "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. |
|