|
Oracle® Application Server Portal Error Messages Guide
10g Release 2 (10.1.4) B19304-01 |
|
 Previous |
|
Oracle® Application Server Portal Error Messages Guide
10g Release 2 (10.1.4) B19304-01 |
|
|
Previous |
This chapter contains all other messages that are either not numbered or not covered in the preceding chapters. The messages are grouped into the following subsections:
This section describes the error messages, their causes, and suggested actions, that you may encounter while configuring or logging into OracleAS Portal. For more information on securing OracleAS Portal, refer to the Oracle Application Server Portal Configuration Guide.
Make sure that the connect string parameter in the DAD has been defined correctly in the right TNSNAMES.ORA or LDAP.ORA file. A common error is to either misconfigure the TNS_ADMIN parameter, or not specify the correct values for the connect string in the Net Service name resolution files.
Make sure that the database listener is running and is accessible from the middle tier. Set your Oracle environment to point to the same environment as the middle tier, and issue tnsping connect_string where connect_string is the parameter specified for the PlsqlDatabaseConnectString in the Portal DAD. The relevant Oracle environment variables to be set prior to issuing tnsping are ORACLE_HOME, PATH, and TNS_ADMIN. On UNIX platforms, you will also need to set LD_LIBRARY_PATH or its corresponding equivalent.
Make sure the connect information, database user, and password information is correctly specified in the DAD. (The DAD can only be configured and edited through Oracle Enterprise Manager 10g.) The DAD can be edited within Oracle Enterprise Manager 10g by navigating to the PLSQL Properties under the HTTP Server. The orasso DAD is created under the Infrastructure HTTP Server, while the OracleAS Portal DAD is created under the middle-tier server. The connect string information should be specified in either SIDFormat (host:port:sid) or as NetServiceNameFormat.
http://host.domain:port/jpdk/providers/sample
If this does not work, then the OC4J_Portal instance is failing. Check the OC4J log files for more details. The log files are located in:
ORACLE_HOME/j2ee/OC4J_Portal/application-deployments/portal/OC4J_Portal_default_island_1
begin wwpre_api_value.set_value_as_varchar2( p_path=> 'oracle.portal.proxy', p_name=> 'name', p_level_type =>wwpre_api_value.SYSTEM_LEVEL_TYPE, p_level_name => null, p_value => NULL); wwpre_api_value.set_value_as_number( p_path=> 'oracle.portal.proxy', p_name=> 'port', p_level_type => wwpre_api_value.SYSTEM_LEVEL_TYPE, p_level_name => null, p_value=> NULL); end; /
After issuing these statements, the value of the proxy setting will be NULL.
This section describes the error messages, their causes, and suggested actions that you may encounter while developing applications and portlets in OracleAS Portal. For more information on OracleAS Portal application development, refer to the Oracle Application Server Portal User's Guide.
This section contains the following portlet development error messages:
This section contains the following error messages:
ORA-06510. PL/SQL: Unhandled user-defined exception.
ORA-20000. Error raised from call to WPG_SESSION.
portal=true cookie), or from a cookie corrupted in some manner (such as clicking Stop in mid-request).
portal=true cookie is generated by the Web calendar application.
error_log file may provide clues to the nature of the process_signon problem.
The following error message is generated by the middle tier when ORA-2000x errors are encountered:
For more information on ORA-2000x errors, refer to Appendix K, "Troubleshooting OracleAS Portal" in the Oracle Application Server Portal Configuration Guide.
The following error messages are unnumbered, and occur while running OracleAS Portal.
Error: 499 SSO Error on Provider Test Pages
Error: 'Call to utl_http failed' when clicking on a URL item link rendered 'in-place'.
Error: "Timeout for content" in one or more portlets.
Error: "400 bad request" or the Web browser just hangs when trying to access OracleAS Portal.
Error: "The portlet could not be contacted"
oracle.webdb.providerui.securedAccessParam to false in the following file:
ORACLE_HOME/j2ee/OC4J_Portal/applications/portalTools/providerBuilder/WEB-INF/web.xml
You can set the value back to true, when you are finished editing the test pages.
alter table wwv_text modify lob (text) (nocache);
Check to make sure your browser language preference is set to the language you have installed with OracleAS Portal. OracleAS Portal is supported on 24 different languages, with English as the default language.
Make sure that your browser is set to accept Java and Javascript.
Check the installation log file to see if wwvcbus.ctl and wwcus.ctl were loaded into OracleAS Portal's Globalization Support table, wwnls_strings$.
Scan the file ORACLE_HOME/j2ee/OC4J_Portal/applications/portal/portal/WEB-INF/web.xml for the parameter requesttime (default is 15 seconds). If you expect that your portlet should be taking less time than this to respond, then there is something wrong on the provider side. Look at the response characteristics of your provider, and make sure that it is performing within the period defined for requesttime.
Tune the performance of your provider so that it can respond within the requesttime interval defined in the PPE configuration.
Increase the default requesttime for the Parallel Page Engine. Note that the increased value should still be within limits of what end users expect to be acceptable Web performance.
Edit the file ORACLE_HOME/j2ee/OC4J_Portal/applications/portal/portal/WEB-INF/web.xml.
Locate the section <servlet-class>oracle.webdb.page.ParallelServlet.
Add or edit the parameter requesttime to a value high enough to allow the portlet time to respond. For example:
<init-param> <param-name>requesttime</param-name> <param-value>40</param-value> </init-param>
The value 40 can be substituted with a higher or lower number, depending on your requirements. For individual database portlets, you can also set the timeout in the portlet record. For web portlets, you can increase the timeout in provider.xml.
|
Note: In all the preceding options, the upper limit of how much time any portlet can take is defined by the PPE configuration parameterstall. Make sure that this parameter is configured a little higher than the maximum request time for any portlet in your system.
|
web.xml file, which is located in ORACLE_HOME/j2ee/OC4J_Portal/applications/portal/portal/WEB-INF:
<init-param>
<param-name>httpsports</param-name>
<param-value><your HTTPS port></param-value>
</init-param>
Display Item In Full Browser Window
Display Item In New Browser Window
In either case, in some modes for the portlet (for example, Customize, Edit Defaults and so on), this error message may display.
The server that the portlet's provider resides on, is down.
Domain Name Server (DNS) is down.
Network Address Translation (NAT) is not set up correctly in a configuration front-ended by a Load Balancing Router (LBR).
Review the errors in ORACLE_HOME/j2ee/OC4J_Portal/application-deployments/portal/OC4J_Portal_default_island_1/application.log to see the host name and port number of the portlet that cannot be contacted.
Check if the host is up by running the following command:
ping <host_name>
Restart the server that the portlet's provider resides on if needed.
If dynamic DNS is used, you must perform additional configuration in OC4J_Portal to prevent remote Web providers from timing out. You must change the sun.net.inetaddr.ttl system property for OC4J_Portal. On JDK 1.3 and later, the sun.net.inetaddr.ttl system property can be used to specify the "time to live" (TTL) in seconds for cached IP addresses.
|
Note: It is important that this system property is passed as a command line option to Oracle Application Server Containers for J2EE (OC4J). Setting the property inoc4j.properties will not help because the system property is read first before OC4J reads this file. Therefore, it is best to modify the <java-option> line in the OC4J_portal section of ORACLE_HOME/opmn/conf/opmn.xml.
|
If your configuration is front-ended by an LBR, you need to configure NAT properly. NAT is not set up the same way on all LBRs. Consult your LBR's configuration guide on how to set this up. For a detailed description on why the LBR needs additional configuration to make loopback communication successful, refer to the section on configuring multiple middle tiers with an LBR in the Oracle Application Server Portal Configuration Guide.
The following are standard HTTP error messages that may occur when using OracleAS Portal:
HTTP-400. Bad Request/Malformed Host Header.
HTTP- 403 with ORA1017. HTTP 403 Forbidden.
HTTP-503 with ORA-6550. Service Temporarily Unavailable.
HTTP-503 with ORA-12560. Service Temporarily Unavailable.
Other HTTP Error Codes (400 - 600)
tnsnames.ora file and verify that the tnsalias is pointing to the correct database. The tnsnames.ora file is located here:
ORACLE_HOME/network/admin
wwjni.jar library reference is not present in the ORACLE_HOME/j2ee/OC4J_Portal/application-deployments/portal/orion-application.xml file. This file's library entry may have been deleted during the redeployment of portal.ear, or may have been accidentally deleted.
ORACLE_HOME/j2EE/OC4J_Portal/application-deployments/portal/orion-application.xml file:
<orion-application><library path=ORACLE_HOME/portal/jlib/wwjni.jar"/></orion-application>
The instance crashed (that is, JVM crashed).
The instance overloaded and was restarted by OPMN.
The instance did not start up correctly.
The instance was intentionally shut down.
dmctl command. If Cause #2 occurred, no action is required since it may take a few moments for the instance to restart.
ORACLE_HOME/Apache/modplsql/conf/dads.conf. Remove the line from the DAD that includes the following:
PlsqlAuthenticationMode SingleSignOn
host:port:sid syntax of connecting to the backend database. If you have changed this to use a TNS entry, then make sure that the TNS_ADMIN environment variable is pointing to the correct tnsnames.ora file and that this entry can be resolved. You should also make sure that the TNS Listener and the database are up and running.
httpd.conf (StartServers+MaxSpareServers). One quick way to verify that you are hitting this issue is to connect as SYS through SQL*Plus, and issue this query:
select username from v$session
If the count of the number of rows is almost the same as the value of the processes parameter, then you are exceeding the maximum number of processes.
Check the following error log files for more details:
OHS error log ORACLE_HOME/Apache/Apache/logs/error_log
Portal OC4J error log ORACLE_HOME/j2ee/OC4J_Portal/application-deployments/portal/OC4J_Portal_default_island_1.
Verify that the Oracle Application Server HTTP Listener is up and running and that you can access static files. Access the URL http://host:port.
If there are mod_plsql related errors in the Apache error log file, do one of the following:
Confirm that you are trying to access a valid URL and that the URL name has been entered correctly.
For database connectivity issues: — Be sure that the database is up and running, and that you can connect to it using SQL*Plus with your ORACLE_HOME set to the Oracle Application Server home. — Check the DAD configuration file for valid user name, password, and connect string. — If there are multiple Oracle homes on the system, be sure that the proper tnsnames.ora file has been updated. If in doubt, you can use the host:port:SID syntax in the connect string field.
If you do not have connectivity issues, verify that you can access simple PL/SQL procedures through the Portal DAD; for example, http://host:port/portal/pls/portal/htp.p?cbuf=test.
For WPG_SESSION or WPG_SESSION_PRIVATE related errors, be sure that your install completed without problems. Verify that all the packages are valid by connecting as SYS and issuing the command "select object_name, status from all_objects where status like '%INVALID%;".
Verify that you can access the OC4J Portal instance by accessing http://host.domain:port/jpdk/providers/sample.
If you still have issues, refer to the "Troubleshooting" chapter in the mod_plsql documentation.
This section describes the error messages, their causes, and suggested actions that you may encounter while exporting and importing applications with OracleAS Portal. For more information about exporting and importing, refer to the Oracle Application Server Portal Configuration Guide.
|
Note: During the export and import process, you can click the View Log of Actions link to display a log of the export and import process, which includes the error messages contained in this chapter. To view a more detailed log of your export and import process, as well as more detailed debugging messages, select the Advanced Logging option. |
This section contains the following export and import error messages:
This section contains the following error messages:
ORA-00001: Unique constraint (PORTAL.WWSBR_PORTLET_OBJECT_UK) violated
ORA-02291: Integrity constraint (PORTAL.WWSBR_SILA_SITE_IS_SITE_FK) violated - parent key not found.
ORA-02291: Integrity constraint (PORTAL.WWSBR_THINGSUBTYPE_ID_FK) violated - parent key not found.
ORA-02291: integrity constraint (PORTAL.WWPOB_PORTLET_INST_SITE_FK) violated - parent key not found.
ORA-04088: Error during execution of trigger "PORTAL.WWSBR_THAT_BRIUD_TRG".
wwsbr_portlet$ raises the unique constraints violation when the corresponding entry is updated with new values. This error can occur when the page portlet or a navigation page imported in overwrite mode was not resolved.
Back up the page portlet.
Try deleting the page (exposed as portlet) in the target.
Run the import for this page portlet again in overwrite mode.
wwutl_sbr_tx_site_language$.
wwv_subtypeattribute) for thingsubtype,thingsubtype_siteid (itemtype information) is unresolved.
wwutl_sbr_tx_subtypeattribute$.
portlet_instance table from the transport set is pointing to the wrong siteid. This problem can occur when you import some of the external page portlets (other than porlets that are local to that page group), but not the page group.
subtypeattributeid of the Item Attributes transport table cannot find its corresponding subtypeattributeid from wwv_subtypeattributes table. The no_data_found exception is raised when the item attributes are inserted or updated.
subtypeattributeid exists in the target before the insertion of item attributes by doing the following:
For any page that is brought in the transport set which has an item based on a custom item type, the custom item type should already exist with all its attributes in the target.
If the custom item type is already a part of the transport set, make sure the records are inserted into the target before hand.
|
Note: The import of the item types occurs before the insertion of the items. |
This section contains the following unnumbered error messages:
Error: WWUTL_API_IMPORT_PAGEGROUP.post_resolve_items: ORA-01403: no data found.
Error: Encountered unknown error while registering portlet.
wwv_things$ is not resolved properly. This is an abnormal situation.
text_id in wwv_things does not match the entries in wwv_text.
Make sure that there is no data loss during export or import of dump in wwutl_sbr_tx_text$. (Set the exp client home compatible to Oracle Database to avoid data truncation/loss.)
Make sure that the itemtype and pagetype attributes are working properly after import. (If not, correct that first and try the import again.)
wwdoc_document$.
Make sure that there is no data loss during export or import of dump in wwutl_doc_tx_document$. (Set the exp client home compatible to Oracle Database to avoid data truncation or loss.)
Make sure that the itemtype and pagetype attributes are working properly after import. (If not correct that first and try the import again.)
url_id in wwv_things does not match the entries in wwsbr_url$.
|
Note: The portlet's container object will not be shown in the Manifest. Make sure the container object is also part of the transport set or exists in the target. |
This section provides information about the error and warning messages that you may encounter when upgrading to OracleAS Portal 10g Release 2 (10.1.4). The messages are grouped into the following sections:
Section 7.4.1, "Numbered Error Messages (WWU-00001 to WWU-24999 and WWU-26004 to WWU-26007)"
Section 7.4.2, "Numbered Warning Messages (WWU-25000 to WWU-26001)"
|
See Also: Appendix titled "OracleAS Portal Upgrade Error Messages" in the Oracle Application Server Portal Installation and Upgrade Guide. |
Refer to the error messages WWU-00001 to WWU-24999 and WWU-26004 to WWU-26007 in Chapter 4, "WWU-00001 to WWU-26007" for a description of the numbered error messages, their causes, and suggested actions that you may encounter while upgrading to OracleAS Portal 10g Release 2 (10.1.4).
Refer to the warning messages WWU-25000 to WWU-26001 in Chapter 4, "WWU-00001 to WWU-26007" for a description of the numbered warning messages, their causes, and suggested actions that you may encounter while upgrading to OracleAS Portal 10g Release 2 (10.1.4).
This section describes the unnumbered error messages, their causes, and suggested actions that you may encounter while upgrading to OracleAS Portal 10g Release 2 (10.1.4).
OracleAS Portal has not been configured correctly for the Oracle Internet Directory.
Oracle Internet Directory server is not running.
An unexpected error was encountered.
The following sections provide information on the common problems encountered while using WebDAV clients to connect to OracleAS Portal.
Section 7.5.2, "Error While Accessing the Portal Schema Using the DAV Client SiteCopy"
Section 7.5.5, "Misleading Error Messages in WebDAV Clients"
Section 7.5.6, "Problem: OraDAV assumes a default Character Set used by the clients"
If you are using a Web browser as the WebDAV client and you experience a Forbidden Error when accessing a WebDAV location, an error is written to the Web server error log that looks like this:
[Tue Jun 4 11:33:14 2002] [error] [client 144.25.248.140] Directory index forbidden by rule: /
To avoid this problem, you can add Options Indexes in the oradav.conf file, as shown in the following example:
<Location /dav_portal/portal>
DAV Oracle
DAVDepthInfinity On
DAVParam ORACONNECT dbhost:dbport:dbsid
DAVParam ORAUSER portal_schema
DAVParam ORAPASSWORD portal_schema_password
DAVParam ORACONTAINERNAME OraclePortal
DAVParam ORAPACKAGENAME portal_schema.wwdav_api_driver
Options Indexes
</Location>
After you have performed an upgrade from release 9.0.2 to release 10.1.2.0.2 or 10.1.4, if you try to access the portal schema using the DAV client, SiteCopy, then you may encounter a Forbidden Error. The reason for this is that the oradav.conf parameter, DAVDepthInfinity is set to OFF by default.
To avoid this problem, you must edit the oradav.conf file at ORACLE_HOME/Apache/oradav/conf/, and set the parameter DAVDepthInfinity to On, as shown in the following example:
<Location /dav_portal/portal> DAV Oracle DAVDepthInfinity On . . . </Location>
It is, however, recommended that you check all the oraDAV parameter settings. Refer to the Oracle HTTP Server Administrator's Guide for more information on the DAVDepthInfinity parameter.
Due to the way some WebDAV clients behave, users might experience authentication requests multiple times. To avoid this, you can increase the value for ORACookieMaxAge in the oradav.conf file (the default value is 0). Its value is specified as the time in seconds before the cookie expires, as shown in the following example:
<Location /dav_portal/portal>
DAV Oracle
DAVDepthInfinity On
DAVParam ORACONNECT dbhost:dbport:dbsid
DAVParam ORAUSER portal_schema
DAVParam ORAPASSWORD portal_schema_password
DAVParam ORACONTAINERNAME OraclePortal
DAVParam ORAPACKAGENAME portal_schema.wwdav_api_driver
DAVParam ORACookieMaxAge 28800
</Location>
If the WebDAV tables in OracleAS Portal need repopulating (due to inconsistent data), you can use the DAV Loader utility to repopulate them to the latest data available from OracleAS Portal. When data inconsistency occurs, the following error appears in the Web server's error log file:
[Fri Sep 13 11:33:19 2002] [error] [client 130.35.64.171] OraDAV (b8790): Apache OCI Error -9999/6510 : ORA-06510: PL/SQL: unhandled user-defined exception ORA-06512: at "PORTAL.WWPTH_API_PRIVATE", line 953 ORA-06510: PL/SQL: unhandled user-defined exception ORA-06512: at "PORTAL.WWPTH_API_PRIVATE", line 1515 ORA-06510: PL/SQL: unhandled user-defined exception ORA-06512: at "PORTAL.WWSBR_SITE_DB", line 801 ORA-01403: no data found ORA-06512: at "PORTAL.WWPTH_API_PRIVATE", line 982 ORA-06512: at "PORTAL.WWDAV_INTERNAL", line 2154
You can run the DAV Loader utility by executing the following procedure from SQL*Plus:
set serveroutput on size 1000000
begin
wwdav_loader.create_dav_content;
end;
This re-creates the entire set of DAV data. To get more debugging information, you can also use:
set serveroutput on size 1000000
begin
wwdav_loader.create_dav_content(
p_debug_mode => true);
end;
Running the DAV Loader removes any temporary documents from the DAV tables.
When attempting to perform delete or copy operations at the page group level in a WebDAV client, you may experience the following error message:
500 Internal Server Error
This is not a server error, but a forbidden operation, because you cannot perform write operations at the page group level.
When performing operations in Web Folders you may sometimes come across the following error message:
The current operation cannot be completed because some unexpected error has occurred
This can happen if the information in Web Folders is out of sync with that in the portal. To solve this, navigate to the top level of the page group in Web Folders and refresh. Look at the error log, a file named MY_ERROR_LOG.TXT in your personal page, if you continue to experience problems.
Cause: Some WebDAV clients send requests without specifying the character set in the content-type and XML headers. As a result, OraDAV assumes a default character set used by the clients.
Action: To work around this, the NLS_LANG environment variable must be set to match with that of the WebDAV client.
In the following example, the WebDAV client locale is Shift-JIS, and mod_oradav needs the NLS_LANG variable to be AMERICAN_AMERICA.ja16shjis. To set this:
Stop the HTTP Server listener.
Change the NLS_LANG environment variable by doing the following:
Open ORACLE_HOME/opmn/conf/opmn.xml.
Look for the <ias-component id="HTTP_server"> section.
In this section, look for the <process-set> subsection, then add the following:
<environment> <variable id="NLS_LANG" value="AMERICAN_AMERICA.ja16shjis" /> </environment>
Save the file.
Start the HTTP Server listener.
If the WebDAV packages become invalid, WebDAV becomes inaccessible and you find errors in the Web server's error log file, similar to:
[Wed Dec 10 04:11:23 2004] [error] OraDAV: Apache/OCI Error -9999/4061: ORA-04061: existing state of package body "PORTAL.WWDAV_INTERNAL" has been invalidated
Recompile the WebDAV packages to solve this problem.
