This chapter describes issues associated with Oracle Portal. It includes the following topics:
In addition to the known problems and workarounds described in this document, Oracle recommends that you read the My Oracle Support note 834615.1 - Oracle Fusion Middleware 11g Portal (11.1.1) Support Status and Alerts. This article contains known issues that were discovered after the release of Oracle Portal 11g Release 1 (11.1.1).
This section describes general issues and workarounds. It includes the following topics:
If the database where the portal schema is installed is version 10.2 or later, then users must re-enter the remote user's password when they rename or edit a database link from the Portal Navigator's Database Objects tab. This is applicable only for those database links that are created with the Specific User option.
Moving content between pages or between regions of the same page does not trigger approvals. For example, when a target page is configured with an approval process and a contributor moves content from a source page to the target page, the moved content does not trigger the approval process on the target page, even when approval is required for all users.
Firefox and Safari browsers do not support the display of tooltip text, which is set using the ALT attribute for image descriptions.
As a workaround, you can download and install browser-specific add-ons, such as Popup ALT Attribute for Firefox (see
If the JVM default character encoding is set to ISO8859-1, the Portal repository database character set must match with the JVM default character encoding. If this condition is not satisfied, non-ASCII URLs may become inaccessible.
If you are adding a zip file to a page under a pagegroup using non-ascii character name, and when you unzip the file, it throws the following exception:
IllegalArgumentException: null and unzip will be failed.
To avoid this exception, you must use ascii character as the zip file name.
Any manual changes to Oracle Portal default objects, such as tables, views, packages, or indexes are not supported. Such changes may render Oracle Portal unusable. Note that the internal structure of Portal objects can change between versions.
For more information, see the 403179.1 My Oracle Support note.
If RCU portal schema creation fails with the error message ORA-24246: empty access control list (ACL) not allowed, do the following:
Connect to the database as a SYS user.
At the SQL prompt, run the following command:
BEGIN DBMS_NETWORK_ACL_ADMIN.drop_acl ( acl => '/sys/acls/portal-permissions.xml'); COMMIT; END; /
Portal throws an error message
The Discoverer Provider is busy, please try again later. This occurs when you perform the following steps:
Click Edit Portlet defaults
Click Update for Database section
Change selection for User not logged sub-section
Click Next to fetch worksheet list
To workaround this issue perform the following steps:
stall timeout to $DOMAIN_HOME/servers/WLS_PORTAL/
Restart WebLogic Server Portal
When you try to add the sample Scrolling RSS Portlet or the sample Simple RSS portlet to a Portal page, an error message is displayed.
The error occurs because the RSS used by the sample portlets are no longer available.
Currently, there is no workaround for this problem.
If you have Oracle Text enabled, the following internal server error may occur when you are searching for Pages:
Internal error (WWC-00006) An unexpected error has occurred (WWS-32100) Unknown Exception (WWC-45131) User-Defined Exception (WWV-11230) Unexpected error - ORA-00600: internal error code, arguments: [qkeIsExprReferenced1], , , , , , ,  (WWC-35000)
If this error occurs, you must download and install the patch ID 7041059 from
After creating the Oracle Portal schema, you may get the following error:
checkinstall2=Add ACL for network packages if DB is 11.1 or higher... old 4: schema varchar2(2000) := upper('&&1'); new 4: schema varchar2(2000) := upper('CLASSIC17_PORTAL'); Package DBMS_NETWORK_ACL_ADMIN exists, assign ACL if not already assigned Removing dangling principals,if any from the ACL privilege list ... ERROR: when assigning network ACL declare * ERROR at line 1: ORA-24246: empty access control list (ACL) not allowed ORA-06512: at "SYS.DBMS_NETWORK_ACL_ADMIN", line 421 ORA-06512: at line 1 ORA-01403: no data found ORA-06512: at line 83
To fix this error, you must create a schema with a different prefix, and then run the following command to clean out the dangling ACL:
begin DBMS_NETWORK_ACL_ADMIN.DELETE_PRIVILEGE('portal-permissions.xml','PREFIX_PORTA L'); end;
PREFIX_PORTAL is replaced with the schema prefix used in the schema that was dropped.
You must run the Repository Creation Utility to install the new schema.
In Oracle Portal database object, if you insert one row data which has MB character and then update the row, the update will not work. You must manually update the table and view in the database to avoid this issue and update the table and view successfully.
This section describes the upgrade issues and workarounds. It discusses the following topics:
When you upgrade SSL environment from Oracle Portal 10g to Oracle Portal 11g Release 1 (11.1.1), you will not able to login to Oracle Portal, when you have SSO and Portal Midtier on the same hostname. Internet Explorer has a problem redirecting back and forth on the same hostname between two different ports under SSL mode. As a workaround, you can use Mozilla Firefox.
This section describes the interoperability issues and workarounds. It discusses the following topics:
For this interoperability scenario to work, you must download and install the patch ID 7971335 from
In Portal 11g 1 (11.1.1), you cannot create webproviders when you are using 11g midtier with 10g portal repository.
This section describes issue and workaround related to the Oracle Portal user interface. It includes the following topic:
If you use the List View to set access privileges for one or more pages, then privileges will not be set on pages inheriting privileges from a parent page or template. As a workaround, change the privileges for such pages individually, that is, using the Access tab for the subpage.
This section describes issues and workarounds related to export and import in Oracle Portal. This section includes the following topics:
If you include Reports Server Components within a transport set, then they are deleted on export and import. In addition, do not configure the Oracle Reports item type in any page groups intended for export and import. If you do, then the following error is displayed when you try to configure item types in the imported page group (by clicking the Content Type and Classifications Edit link on the Configure tab for the page group):
Internal error (WWC-00006) Unexpected error - User-Defined Exception (WWC-35000) Unexpected error - ORA-01403: no data found (WWC-35000)
After you complete the transport set transfer, click Display Manifest to display the transport set manifest. Ensure that you save the transport set before performing the precheck of the transferred data. This step takes the manifest changes.
Importing a page group may fail with the following error message:
[Error: (WWU-80338)] context = Schema Validation user = ORCLADMIN There were some inconsistencies found and hence import process is aborted.Check the debug log for further details.Fix those inconsistencies, by running schema validation in cleanup mode to proceed
This problem might occur after deleting a page group containing shared portlets. You must run SVU in cleanup mode to ensure a smooth export or import process.
This section describes issues and workarounds related to OmniPortlet, Web Clipping, Simple Parameter Form, Page portlet, and WSRP providers. This section includes the following topics:
The Federated Portal Adapter enables you to display remote portal pages in your portal. However, if both portal instances do not share the same Oracle Single Sign-On server, then you cannot display a remote portal page as a page portlet, even if the remote page is public. A message is displayed instead of the page portlet, as shown in the following example:
Portlet 257,75057 responded with content-type text/plain when the client was requesting content-type text/html
As a workaround, configure both portal instances to use the same Oracle Single Sign-On server.
When you redeploy your portlets to the portlet container, all existing sessions between the producer and all of its consumers are lost. If a consumer tries to reuse an existing producer session, then it may receive an error message the first time it tries to contact the producer after redeployment, as shown in the following example:
Error: Could not get markup. The cookie or session is invalid or there is a runtime exception.
To reestablish the producer's session, refresh the portal page. You will not see this error message if you are reaccessing the portlet from a new browser session because it automatically establishes a new producer session.
SSL support is not available for Oracle Portal Integration Solutions (Microsoft Exchange). This is a known limitation.
Oracle Portal Developer Kit (PDK) version 10.1.2 is included with the Portal and Wireless installation. Release notes for the PDK-Java and PDK-PL/SQL can be found at the following middle-tier
New versions of the Oracle PDK are released periodically providing new features, new APIs, and additional documentation. To take advantage of all the latest features, download the latest PDK from the PDK downloads page on the Oracle Technology Network (OTN) at
Release notes for the latest Oracle PDK version are available on Oracle Portal on OTN and also in these PDK download locations:
This section describes issues and workarounds related to Globalization Support in Oracle Portal. It includes the following topics:
The direction of all text areas and fields is right to left (RTL). However, you may want some text areas to work left to right (LTR). Internet Explorer users can change this by pressing the left hand side Ctrl and Shift keys.
When you copy and paste an item URL containing non-ASCII characters from one browser Location or Address field into another, you may not be able to access the item if your login credentials have not been authenticated through OracleAS Single Sign-On.
As a workaround, log in to the portal before you access the item and copy the item URL.
In some scenarios, multibyte characters in log files may get corrupted.
For example, when the WLS_PORTAL managed server is started from the Oracle WebLogic Server Administration Console, multibyte characters, such as
is starting, may get corrupted.
-Dfile.encoding=utf8 in the WLS_PORTAL start-up parameter through the Oracle WebLogic Server Administration Console.
-Dfile.encoding=utf8 in the
setDomainEnv.sh file (Located at
For more information, see note 403179.1.