Oracle® Application Server Portal Error Messages Guide
10g Release 2 (10.1.4) B19304-01 |
|
Previous |
Next |
An error occurred when an invalidation message was sent. This can occur when OracleAS Web Cache goes down, or is stopped while OracleAS Portal writes an invalidation message to the OracleAS Web Cache invalidation port.
Some other unexpected exception occurred while processing an invalidation message.
OracleAS Web Cache was not running. It might have been stopped on purpose in order to front-end with the Oracle HTTP server, instead of OracleAS Web Cache. Alternatively, OracleAS Web Cache might have crashed, or it been restarted at the time when the invalidation messages were sent from OracleAS Portal or providers.
OracleAS Web Cache invalidation port problems were encountered. This can happen if the OracleAS Web Cache invalidation port value specified in OracleAS Portal is different from the actual OracleAS Web Cache invalidation port. Alternatively, the invalidation port value supplied to OracleAS Portal using the "-cport_i" parameter during installation could also have been wrong, or the OracleAS Web Cache invalidation port was changed in OracleAS Web Cache after the OracleAS Portal install.
Another process used the OracleAS Web Cache invalidation port before OracleAS Web Cache started listening on it.
Issues with the OracleAS Web Cache invalidation password were encountered. Either the OracleAS Web Cache invalidator password value in OracleAS Portal is different from the actual OracleAS Web Cache invalidator password, or the invalidator password value supplied to OracleAS Portal using the "-wc_inv_pwd" parameter during installation was wrong.
The invalidator password was provided instead of the OracleAS Web Cache administrator password for security setting changes in OracleAS Web Cache.
Issues with the OracleAS Web Cache host name were encountered. Either the OracleAS Web Cache host name value in OracleAS Portal is different from the actual OracleAS Web Cache host name, or the host name value supplied to OracleAS Portal using the "-host" and "-chost" parameters during the install was wrong.
OracleAS Web Cache moved to a different server after the OracleAS Portal installation and the host on which OracleAS Web Cache runs is inaccessible from OracleAS Portal.
The host name specified did not include the entire domain name.
OracleAS Web Cache was not properly disabled. OracleAS Portal can work without OracleAS Web Cache front-ending the middle tier. To do this, "enable_wc_caching" flag in OracleAS Portal should be turned off. If this is not the done, any operation that attempts to send an invalidation message fails with exceptions such as "Portal Web Cache setting is On when Web Cache may be down".
An attempt was made to delete a special group, such as the DBA or PORTAL_ADMIN group.
The specified group profile does not exist in Oracle Internet Directory.
An alias defined in the Apache configuration caused Apache to translate host.domain.com to just host. If this is the case, the Login link will only show host:port (dropping the domain).
The default domain was not set in the Apache configuration. When this occurs, only the host name is shown in the Login link and the domain is not included.
OracleAS Portal was configured with an incorrect host or port.
Remove all such aliases from your Apache configuration.
Include the domain in the ServerName parameter.
Fix the Host in the IASInstance element and ListenPort in the WebCacheComponent element in iasconfig.xml and run ptlconfig -dad portal -site. The ptlconfig script and the iasconfig.xml file are normally located in the directory portal/conf under the OracleAS Portal and OracleAS Wireless middle-tier home.
The OracleAS Single Sign-On Server may not be operational.
There was an incorrect Querypath URL Prefix in the OracleAS Single Sign-On Server settings.
Check whether the OracleAS Single Sign-On Server is up and running.
Verify the Querypath URL Prefix in the OracleAS Single Sign-On Server settings.
OracleAS Single Sign-On was using a stale user entry from its cache when transmitting user data to the OracleAS Portal repository.
The user profile for the specified user name already existed in the OracleAS Portal schema, but it contains an incorrect Globally Unique Identifier.
Add a user or group entry in Oracle Internet Directory that already exists.
Add an owner/member to a group that has already been added.
The portlet was customized to hide all external applications.
No external applications existed.
Display one or more applications in the portlet.
Add an external application. Portal administrators with single sign-on administrator privileges can add external applications.
An attempt was made to assign a group as the default group when the user was not a member of that group.
The user did not have sufficient privileges to perform this task.
An error occurred while accessing the Oracle Internet Directory.
Is accessed within the same browser session.
Falls within the relaxed scope specified when the cookie was created.
Any custom cookies created by the Web provider have names that are unique to that Web provider.
All portal instances accessed using the Federated Portal Adapter are configured with different DAD names.
PDK-Java release 1 (JServ) Web providers requiring this setting are installed in uniquely named JServ servlet zones.
PDK-Java release 2 (OC4J) Web providers do not use this setting if they use servlet sessions. This is because the cookie used to identify the session is always called JSESSIONID. This name is specified in the Servlet 2.3 specification. Relaxing the scope of a JSESSIONID cookie will almost certainly cause session related problems to occur in other, unrelated, Web applications.