10g (9.0.4)
Part Number B10608-01
 Home |
 Solution Area |
 Contents |
 Index |
| Oracle Application Server Portal Error Messages Guide 10g (9.0.4) Part Number B10608-01 |
|
This chapter 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 using OracleAS Portal, refer to the Oracle Application Server Portal User's Guide, located on Portal Center (http://portalcenter.oracle.com).
This chapter contains the following portlet development error messages:
This section contains the following error messages:
ORA-06510 and ORA-06512. PL/SQL: Unhandled user-defined exception.
ORA-20000. Error raised from call to WPG_SESSION.
Cause: The host name was changed and Oracle Portal was not correctly configured with the new host name.
Action: Run opca MIDTIER mode to associate Oracle Portal with the new host name.
Cause: The authentication mode of the DAD is "Basic" rather than "Single Sign-on." It could also be caused by the session row having been deleted from the session table, if the cleanup job cleaned out an active session that was still being used. By default, active sessions are cleaned out 1 week after they are created.
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.
Cause: The cookie value is used to select the session row from the session table. Therefore, a NO_DATA_FOUND error can result from a bogus cookie (such as the portal=true cookie), or from a cookie corrupted in some manner (such as clicking Stop in mid-request).
Action: Close the browser and try to connect to OracleAS Portal only. The "portal=true" cookie is generated by the Web calendar application.
Cause: If a problem has occurred in process_signon (such as an OID problem or a webcache invalidation problem), the session row gets updated in process_signon with the new cookie value, but the cookie does not get set in the browser because of an exception raised in process_signon that causes the error page to show.
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.
WWC-43102. The name field is empty.
WWC-43103. The name field exceeds the maximum length.
WWC-43105. The implementation owner field is empty.
WWC-43107. The implementation name field is empty.
WWC-43109. The implementation name exceeds the maximum length.
WWC-43112. The timeout must be left blank or be a positive value.
Cause: The provider name field was not populated.
Action: Fill in the provider name field.
Cause: The provider name you have entered is too long.
Action: Enter a provider name less that 200 characters long.
Cause: The implementation owner field is mandatory for database providers.
Action: Enter an implementation owner.
Cause: The implementation name field is mandatory for database providers.
Action: Enter an implementation name.
Cause: The implementation name entered is too long.
Action: Enter an implementation name less than 2000 characters long.
Cause: The timeout value entered is negative.
Action: Either leave the timeout blank or enter a positive value.
This section contains the following error messages:
WWC-44009. The name you specified is already in use. Recommended Name: New Name.
WWC-44081. Specify a display name for this style.
WWC-44091. Specify a numeric value for the region width.
WWC-44102. Please specify a valid name and display name.
WWC-44156. Specify a display name for this layout.
WWC-44552. Please specify a numeric value for the space between portlets.
Cause: There already exists a page with the name specified.
OracleAS Portal recommends the usage of a new name for the page.
Cause: When the user does not enter a display name for a style. Error message is seen both when creating a style and when copying a style.
Action: Make sure that the display name for the style is not blank.
Cause: This error is seen in the Edit Region screen. If the user tries to specify a non-numeric value for the Width attribute
Action: Make sure that the value is an integer value (preferably between 1 and 100). If the width is a relative width, make sure to specify the % symbol (e.g., 65%). If the width is an absolute width, then specify only the numeric value (e.g., 35).
Cause: If the user does not enter a name or a display name for a page.
Action: Make sure that the name and the display name for the page are not left blank.
Cause: The user did not enter a display name for a layout. Error message is seen both when creating a layout and when copying a layout.
Action: Make sure that the display name for the layout is not blank.
Cause: The portal page does not exist.
Action: Check that the Name or the ID of the page that you are trying to view or edit is correct.
Cause: This error is seen in the Edit Region screen when the user tries to specify a non-numeric value for the "Space between Portlets" attribute.
Action: Make sure that the value is an integer value (preferably between 1 and 100). If you do not want to specify any value for the space between portlets, then either set the value = 0 or null the field.
Cause: This error is seen in the Edit Region screen when the user tries to specify a non-numeric value for the "Space around Portlets" attribute
Action: Make sure that the value is an integer value (preferably between 1 and 100). If users do not want to specify any value for the space around portlets, then either set the value = 0 or null the field.
Cause: An error occurred while creating the page parameter.
Action: Please refresh the screen and verify that the page is still available.
Cause: An error occurred while reordering the page parameter.
Action: Please refresh the screen and verify that the page and page parameter are still available.
Cause: An error occurred while deleting the page parameter.
Action: Please refresh the screen and verify that the page and the page parameter are still available.
Cause: An error occurred while editing the value of the page parameter.
Action: Please refresh the screen and verify that the page parameter is available.
Cause: The page parameter name is not valid.
Action: Enter a valid page parameter name. See the Page Properties Parameter tab for a list of valid page parameter names.
Cause: An error occurred while editing the value of the portlet parameter.
Action: Please refresh the screen and verify that the portlet parameter is available.
Cause: An error occurred while customizing the page parameter.
Action: Please refresh the screen and verify that the page parameter is still available.
Cause: An error occurred while resetting the page parameters to default values.
Action: Please refresh the screen and verify that you still have access to the customization screen.
Cause: An error occurred while fetching portlet parameters.
Action: Please refresh the screen and verify that the portlet is still available.
Cause: An error occurred while editing the value of the event parameter.
Action: Please refresh the screen and verify that the event parameter is available.
Cause: An error occurred while linking an event to a page.
Action: Please refresh the screen and verify that the event and the page are available.
Cause: An error occurred while removing a link from an event.
Action: Please refresh the screen and verify that the event is available.
Cause: An error occurred while updating the target page for an event.
Action: Please refresh the screen and verify that the event and page are available.
Cause: The event output name is not valid.
Action: Enter a valid event output name.
Cause: The name that you entered has already been used.
Action: Pick a name that is unique.
Cause: An error occurred while creating the parameter.
Action: Please refresh the screen and verify that the parent object is still available.
Cause: An error occurred while editing the parameter.
Action: Please refresh the screen and verify that the parent object is still available.
Cause: The parameter cannot be customized.
Action: Please refresh the screen and verify that the parameter is not customizable.
This section contains the following error messages:
WWC-44761. Error while deleting parameter: parameter
WWC-44762. Parameter "parameter" not found
WWC-44765. Search for parameter "parameter" caused an error: error
WWC-44766. Error while creating the parameter mapping: parameter
WWC-44767. Error while updating the parameter mapping: parameter
WWC-44768. Unsupported from type "source type"
WWC-44769. Parameter "parameter" already has the smallest display order and can't be moved up.
WWC-44770. Moving parameter "parameter" up in the display order failed: %2
WWC-44775. Flow element not found
WWC-44779. Error while creating flow link "flow link"
WWC-44780. Error while deleting flow link "flow link"
WWC-44781. Flow link not found
WWC-44783. Invalid parent type for event "event"
WWC-44784. Parent of event "event" is not a portlet
WWC-44786. Event "event" already exists
WWC-44787. Error while creating event "event": event
WWC-44788. Error while deleting event: event
WWC-44789. Error while deleting events: event
WWC-44791. Event "event" not found
WWC-44793. Error while creating event map: event map
WWC-44794. Error while deleting event map: event map
WWC-44795. Event map not found
Cause: An error occurred while deleting the parameter.
Action: Please refresh the screen and verify that the parent object and the parameter are still available.
Cause: The parameter was not found.
Action: Please refresh the screen and verify that the parent object is still available and that you have access to it.
Cause: An error occurred while searching for the parameter.
Action: Please refresh the screen and verify that the object is still available and that you have access to it.
Cause: An error occurred while creating the parameter map.
Action: Please refresh the screen and verify that the parent object is still available.
Cause: An error occurred while editing the parameter map.
Action: Please refresh the screen and verify that the parent object is still available.
Cause: This type of source object is not supported.
Action: Please select another source object.
Cause: You attempted to move the parameter up in the display order even though it first in the list.
Action: Please refresh the screen and verify that the parameter is first in the list.
Cause: You attempted to move the parameter up in the display order.
Action: Please refresh the screen and verify that the parameter is still available.
Cause: The flow element was not found.
Action: Please refresh the screen and verify that the dependent object is still available.
Cause: An error occurred while creating a flow link.
Action: Please refresh the screen and verify that the parent page is still available.
Cause: An error occurred while deleting a flow link.
Action: Please refresh the screen and verify that the parent page is still available.
Cause: The flow link was not found.
Action: Please refresh the screen and verify that the parent page is still available.
Cause: The parent object does not have a valid type.
Action: Please refresh the screen and verify that the parent object is still available.
Cause: The parent object is not a portlet.
Action: Please specify a portlet.
Cause: The event name is a duplicate.
Action: Please enter a unique event name.
Cause: An error occurred while creating an event.
Action: Please refresh the screen and verify that the parent object is still available.
Cause: An error while deleting an event.
Action: Please refresh the screen and verify that the event is still available.
Cause: An error occurred while deleting events.
Action: Please refresh the screen and verify that the events are still available.
Cause: The event was not found.
Action: Please refresh the screen and verify that the parent object is still available.
Cause: The event was not found.
Action: Please refresh the screen and verify that the parent object is still available.
Cause: The events were not found.
Action: Please refresh the screen and verify that the parent object is still available.
Cause: An error occurred while creating an event map.
Action: Please refresh the screen and verify that the event is still available.
Cause: An error occurred while deleting an event map.
Action: Please refresh the screen and verify that the event is still available.
Cause: The event map was not found.
Action: Please verify that the parent object is still available.
This section contains the following error messages:
WWC-44801. Error while searching for parameter mapping: parameter map
WWC-44803. Duplicate event maps not allowed
WWC-44812. Error while fetching portlet events
WWC-44815. Error while retrieving link from event "event"
WWC-44816. Error while retrieving the target page for event "event"
WWC-44829. Error while writing parameter map metadata: parameter map metadata
WWC-44833. Error adding display name or description for event "event"
WWC-44834. Error while editing the event: %1
WWC-44835. Error while creating page event from portlet event "event": event
WWC-44836. Error while invalidating page cache after updating event: event
WWC-44840. Invalid context for parameter "parameter"
WWC-44841. Error during a parameter change event: event
WWC-44843. Page not found: page, page
WWC-44891. The system variable "variable" is not valid. Please choose a different value.
WWC-44899. Error during a parameter map change event: parameter map
WWC-44901. Error while deleting flow link children: flow link children
WWC-44902. Error while deleting parameter maps: parameter map
Cause: The parameter map was not found.
Action: Please refresh the screen and verify that the parent object is still available and that you have access to it.
Cause: You tried to duplicate an event map.
Action: Please edit or delete the existing event map instead of creating a new event map.
Cause: An error occurred while fetching portlet events.
Action: Please refresh the screen and verify that the portlet is still available.
Cause: An error occurred while retrieving the link for an event.
Action: Please refresh the screen and verify that the event is available.
Cause: An error occurred while retrieving the target page for an event.
Action: Please refresh the screen and verify that the event is available.
Cause: An error occurred while writing the parameter map metadata.
Action: Please refresh the screen and verify that the parameter map is still available.
Cause: An error occurred while adding a display name or description.
Action: Please refresh the screen and verify that the event is still available.
Cause: An error occurred while editing the event.
Action: Please refresh the screen and verify that the event is still available.
Cause: An error occurred while creating a page event from a portlet event.
Action: Please refresh the screen and verify that the portlet event is still available.
Cause: An error occurred while updating a event.
Action: Please refresh the screen and verify that the event or dependent object is still available.
Cause: The parent object (portlet, page, or event) for the parameter is not valid.
Action: Please refresh the screen and verify that the parent object exists.
Cause: An error occurred while updating a parameter.
Action: Please refresh the screen and verify that the parameter and/or dependent object are still available.
Cause: The page was not found.
Action: Verify that the page exists and that you have entered the page correctly.
Cause: The system variable is not valid.
Action: Enter one of the following valid system variables: 1. USER_NAME 2. USER_ID 3. COMPANY_NAME 4. SUBSCRIBER_ID 5. NLS_LANG 6. NLS_TERRITORY 7. TRANSLATION_LANG
Cause: An error occurred while updating a parameter map.
Action: Please refresh the screen and verify that the parameter map and/or the dependent objects are still available.
Cause: An error occurred while deleting a flow link's children.
Action: Please refresh the screen and verify that the dependent objects are still available.
Cause: An error occurred while deleting the parameter maps.
Action: Please refresh the screen and verify that the dependent objects are still available.
Cause: An error occurred while refreshing the portlet repository.
Action: This page is published as a portlet, therefore you may want to refresh the repository manually.
This section contains the following error messages;
WWC-49104. The date entered uses an invalid format.
WWC-49105. The color value entered uses an invalid format.
WWC-51000: The preference path does not exist.
WWC-57267.- An error occurred while configuring the page group.
WWC-57268. Error while writing parameter metadata: parameter metadata
WWC-57269. The parent object 'parent object' does not have a valid ID.
WWC-57270. Error during a flow link change event: flow link
Cause: When the user enters an invalid format for the date.
Action: Use valid Oracle Date format for entering dates, such as 23-apr-2000 for April 23, 2000.
Cause: The value for the color is invalid.
Action: Make sure that the color value is in hexadecimal format (for example, #FFFF93).
Cause: This error will occur when leaving the heading blank on the Column Formatting tab and then trying to run a Report from SQL Query.
Action: Fill in every heading on the Column Formatting tab.
Cause: An error occurred while configuring the page group.
Action: Please refresh the screen and verify that the page group is still availabe.
Cause: An error occurred while writing the parameter metadata.
Action: Please refresh the screen and verify that the parameter is still available.
Cause: The parent object does not have a valid ID.
Action: Please refresh the screen and verify that the parent object is still available.
Cause: An error occurred while updating a flow link.
Action: Please refresh the screen and verify that the dependent pages are still available.
Cause: The reference path for the portlet instance has an incorrect format. This may happen due to some data corruption in the user's instance.
Action: Contact Support Services to resolve this issuet. For more information on contacting Support Services, refer to Calling Oracle Support Services.
WWS-19679. Item has been approved!
WWS-19680. Item has been rejected!
WWS-19699. You do not have permission to view this item.
WWS-22507. Item does not exist.
WWS-25827. This portlet can not search any of the submitted page groups.
WWS-25828. This portlet can not search all the submitted page groups.
WWS-25829. This portlet can not search any of the default page groups from the submitted portlet.
WWS-25830. This portlet can not search all of the default page groups from the submitted portlet.
WWS-25838. The expiry time must be an integer value between 1 and 1440 minutes.
Cause: You are trying to approve or reject an item that has already been approved.
Action: Refresh your browser window to update your notifications. The item you were trying to approve or reject will no longer be listed.
Cause: You are trying to approve or reject an item that has already been rejected.
Action: Refresh your browser window to update your notifications. The item you were trying to approve or reject will no longer be listed.
Cause: You do not have the appropriate privilege to view this item.
Action: Ask the page group administrator or page manager to grant you the appropriate privilege.
Cause: You attempted to perform an action on an item that no longer exists.
Action: Refresh the page so that it displays the current content.
Cause: A search portlet has submitted a search to a different search portlet to show the search results. The results portlet is customized to show results from a specific set of page groups which do not include any of the page groups chosen in the the submission portlet.
Action: Review the list of page groups chosen in the submission portlet or change the customizations in the Edit Defaults of the results portlet to allow it to search in the page groups chosen in the submission portlet.
Cause: A search portlet has submitted a search to a different search portlet to show the search results. The results portlet is customized to show results from a specific set of page groups which do not include all of the page groups chosen in the the submission portlet. Only those page groups common to the submission portlet and the customizations of the result portlet will be searched.
Action: Review the list of page groups chosen in the submission portlet or change the customizations in the Edit Defaults of the results portlet to allow it to search in the page groups chosen in the submission portlet.
Cause: A search portlet has submitted a search to a different search portlet to show the search results. The list of page groups to search from the submission portlet are those chosen as the defaults for that portlet. The results portlet is customized to show results from a specific set of page groups which do not include any of the page groups chosen as the default list of page groups to search in the submission portlet.
Action: Review the list of default page groups chosen in the Edit Defaults of the submission portlet or change the customizations in the Edit Defaults of the results portlet to allow it to search in the page groups chosen in the submission portlet.
Cause: A search portlet has submitted a search to a different search portlet to show the search results. The list of page groups to search from the submission portlet are those chosen as the defaults for that portlet. The results portlet is customized to show results from a specific set of page groups which do not include all of the page groups chosen as the default list of page groups to search in the submission portlet. Only those page groups common to the submission portlet's default page groups and the customizations of the result portlet will be searched.
Action: Review the list of default page groups chosen in the Edit Defaults of the submission portlet or change the customizations in the Edit Defaults of the results portlet to allow it to search in the page groups chosen in the submission portlet.
Cause: An expiry time has been specified that is not an integer between 1 and 1440 minutes.
Action: Enter an expiry time that is an integer between 1 and 1440 minutes.
This section contains the following error messages:
WWV-06406. No link is specified.
WWV-17005. Invalid column column datatype: Mismatch between datatype and default value.
WWV-17078. You need to specify a constraint name
Cause: Editing a dynamic page that contains 32k of HTML code.
Action: Avoid writing more than 32k of HTML code into a dynamic page.
Cause: Attempting to edit a link on the 'Column Formatting' tab that has not been selected and given a value.
Action: Select a link from the combo box.
Cause: Attempting to create a new application component within the same db schema using the same name.
Action: Create the new component using a different name or within a different schema.
Cause: The default value and the column are different datatypes.
Action: Change the datatypes to match.
Cause: Trying to name a new constraint with a name that is already in use.
Action: Select a different name.
Cause: You haven't specified a name for the constraint you are creating.
Action: Name the constraint.
Cause: Trying to edit an index from a unique/primary key.
Action: Change the integrity constraints from the table instead of the unique/primary key.
Cause: The constraint was not added to the table.
Action: Click the Add to List button to add the constraint to the table.
The following error messages are unnumbered, and occur while running OracleAS Portal.
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.
Cause: You may encounter this error if you click an Edit link on a Provider test page for the Web Clipping Provider, OmniPortlet Provider, or Sample Provider, and Oracle Application Server Single Sign-On protection of these pages is enabled, or if Oracle Application Server Single Sign-On is not configured correctly.
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.
Cause: This error can sometimes occur when editing text items. This issue only occurs if you are using an Oracle Database version prior to 9.2
Action: Modify the table wwv_text and disable LOB caching as follows:
alter table wwv_text modify lob (text) (nocache);
Cause: Unable to connect to the OracleAS Portal database.
Action: Contact your administrator.
Cause: This error may display when you try to access the OracleAS Portal home page and National Language Support (NLS) files are missing.
Action: There are several solutions for this error message:
Cause: An incorrect proxy value may have been specified if running within a firewall.
Action: Click on 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.
Cause: The Parallel Page Engine is timing out before the portlet has a chance to respond.
Action: Do one of the following:
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."
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.
Cause: If SSL has been configured, the most likely reason for this error is because the Parallel Page Engine is trying to communicate with HTTP over an HTTPS port.
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>
Cause: When you place a Web portlet on a page, you can display a link to the portlet, rather than the portlet itself. The link can be set to either:
In either case, in some modes for the portlet (e.g. Customize, Edit Defaults etc.), this error message may display.
Action: Display the portlet in place, rather than a link.
The following are standard HTTP error messages that may occur when using OracleAS Portal:
HTTP-400. Bad Request/Malformed Host Header.
HTTP-503 with ORA-6550. Service Temporarily Unavailable.
HTTP-503 with ORA-12560. Service Temporarily Unavailable.
HTTP-503 with ORA-06506. Service Temporarily Unavailable.
Cause: This situation can happen when the hostname on the machine where OHS is running contains the underscore `_' character. Underscores are invalid in URLs.
Action: Change the name of the host to something without an underscore or access the machine by IP Address.
Cause: You cannot create a provider group from the Portal user interface in OracleAS Portal 9.0.4.
Action: See the articles Understanding Provider Groups and Provider Group Server Setup on Portal Center for more information about how to configure provider groups manually.
Cause: The password has changed or the tnsalias entry was changed.
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
Cause: 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.
Action: Make sure the following entry is in the $ORACLE_HOME/j2EE/OC4J_Portal/application-deployments/portal/orion-application.xml file:
<orion-application><library path=ORACLE_HOME/portal/jlib/wwjni.jar"/></orion-application>
Cause: The OC4J_Portal instance is down. This may have been caused by any of the following:
Action: Start the OC4J_Portal in the Oracle Application Server instance via Enterprise Manager or via the dmctl command. If Cause #2 occurred, no action is required since it may take a few moments for the instance to restart.
Cause: A DAD was configured using SSO authentication, but the PL/SQL application does not use SSO authentication. This may occur when the DAD was added using Enterprise Manager and the user chose type "Portal" or "General."
Action: Modify the authentication mode by opening the file $ORACLE_HOME/Apache/modplsql/conf/dads.conf. Remove the line from the DAD that includes the following:
PlsqlAuthenticationMode SingleSignOn
Cause: Unable to connect to the OracleAS Portal database.
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.
Cause: Maximum number of database sessions has been reached.
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.
Cause: OWA_UTIL package of the OWA packages is invalid in the SYS schema.
Action: Follow these steps:
Cause: Failure in mod_plsql while executing an OracleAS Portal stored procedure or in the Portal OC4J instance while executing OracleAS Portal code.
Action: Follow these steps:
|
 Copyright © 2002, 2003 Oracle Corporation. All Rights Reserved. |
|