7 Other Error Messages

Action: Run opca MIDTIER mode to associate OracleAS Portal with the new host name.

Action: Check that the authentication mode of the DAD is "Single Sign-on," rather than "Basic". Close all browser windows (to remove session cookies) and reconnect to OracleAS Portal.

Action: Close the browser and try to connect to OracleAS Portal only. The "portal=true" cookie is generated by the Web calendar application.

Action: Determine what's causing the problem in process_signon and fix that. Examining the Oracle HTTP Server error_log may provide clues to the nature of the process_signon problem.

Action: Click the OracleAS Portal home page to go directly to the OracleAS Portal home page, or if your browser does not automatically redirect you. If you continue to have problems while accessing OracleAS Portal, close all your browser instances and try again.

For more information on ORA-2000x errors, refer to Appendix K, "Troubleshooting OracleAS Portal" in the Oracle Application Server Portal Configuration Guide.

Action: Disable Oracle Application Server Single Sign-On protection on these pages. To do this, change the parameter value for 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.

Action: Modify the table wwv_text and disable LOB caching as follows:

alter table wwv_text modify lob (text) (nocache);

Action: Contact your administrator.

Action: There are several solutions for this error message:

• Check to make sure your browser language preference is set to the language you've 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$.

Action: Click the 'Administer' tab on the OracleAS Portal home page. Click the 'Global Settings' link under the 'Services' banner. Make sure that the values specified under the 'Proxy Server' section are correct. Provide appropriate values for 'HTTP Server', 'HTTP Server Port', and 'No Proxy Servers for Domains beginning with' fields.

Action: Do one of the following:

• 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.

Action: Add the following configuration lines in the web.xml file. It 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>
 

Action: Display the portlet in place, rather than a link.

Action: To resolve this problem, perform the following actions:

• 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 in oc4j.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

Action: Change the name of the host to something without an underscore or access the machine by IP Address.

Action: See the articles Understanding Provider Groups and Provider Group Server Setup on OracleAS Portal Center for more information about how to configure provider groups manually.

Action: Make sure the password is correct in the DAD for the schema you're trying to connect to. Also, make sure the 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

Action: Correct the DAD name in the URL.

Action: Make sure that the "library path" entry is in the ORACLE_HOME/j2EE/OC4J_Portal/config/application.xml file contains the following entries:

<library path="ORACLE_HOME\portal\jlib\wwjni.jar"/>

<library path="ORACLE_HONME\opmn\lib\optic.jar"/>

Action: Start the OC4J_Portal in the iAS instance through the Enterprise Manager or through the dmctl command. If Cause #2 occurred, no action is required since it may take a few moments for the instance to restart.

Action: Make sure the database connect information in the DAD is configured correctly. This is typically configured to use the 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.

Action: Check the processes parameter in your database configuration file (init$SID.ora => processes=NNN). This number should be greater than or equal to the maximum number of Apache processes configured in 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 likely exceeding the maximum number of processes.

Action: Follow these steps:

1. 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

   • WebCache log file ORACLE_HOME/webcache/logs/event_log

2. 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.

3. If there are database connectivity/PL/SQL exception stacks in the application.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/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.

Action: Perform the following actions:

1. Back up the page portlet.

2. Try deleting the page (exposed as portlet) in the target.

3. Run the import for this page portlet again in overwrite mode.

Action: Check whether the corresponding page group included in the transport set is resolved and propagating its values to wwutl_sbr_tx_site_language$.

Action: Make sure the item type is resolved and propagating its new values to wwutl_sbr_tx_subtypeattribute$.

Action: Make sure that all the page portlets for a given page are included with the page group or exist in the target.

Action: Make sure the subtypeattributeid exists in the target before the insertion of item attributes by doing the following:

1. 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.

2. 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.

   
   

Action: Since this error may occur when importing some of the navigation pages, try importing the navigation pages before importing any of the pages that reference this navigation page.

Action: Do one or both of the following:

• 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/pagetype attributes are working properly after import. (If not, correct that first and try the import again.)

Action: Do one or both of the following:

• 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/loss.)

• Make sure that the itemtype/pagetype attributes are working properly after import. (If not correct that first and try the import again.)

Action: Make sure that the itemtype/pagetype attributes are working properly after import. (If not, correct that first and try the import again.)

Action: Verify whether the parent object exists in the target or in the transport set (resolved).

Action: Include the underlying portlet in the transport set.

Action: Make sure the page and page template have different names within the same page group.

Action: Ensure that all the external objects for an explicit object already exist in the target. Otherwise, include them in the transport set (by promoting them).

Action: Ignore this warning.