Oracle Application Express

Known Issues - Application Express 5.0.1

Application Express 5.0.1 was released on July 15, 2015.

This page was last updated on October 13, 2015.

  • 21839850 - REALPLAYER CAUSES REDIRECTS IN APEX TO START PAGE WITH A CHANGING SESSION ID
    When Application Express always redirects to the login page and generates new session IDs, the Real Player downloader software on the user's PC may be responsible. The downloader software re-sends HTTP requests with invalid combinations of session ID and session cookie.
    Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.
  • 21469957 - ORA-14552 BECAUSE OF LOV QUERY WITH BIND VARS IN CLASSIC REPORT
    When running a classic report that includes a call to apex_item.select_list_from_lov, the report fails with ORA-14552 if the LOV definition contains a bind variable.
    Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.
  • 21537995 - STATIC IMAGES BROKEN FOR OLD WORKSPACES WHEN USING APEX 5.0 AND ORDS 3
    If an instance has workspaces that were created before Application Express 4.1 and Oracle REST Data Services 3 is being used, static image links will not be displayed.
    Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.
  • 21501621 - CHANGE WORKSPACE IN DEV ENV AUTOMATICALLY LOGS IN TO SAME WORKSPACE
    After applying the 5.0.1 patch, Change Workspace (which is available for header based authentication and single sign-on) in the development environment automatically logs in to the same workspace again.
    Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.
  • 21479385 - SAMPLE GEOLOCATION LOCATION SHOWCASE ALWAYS INDICATES NO HTTP ACCESS
    In APEX 5.0.1, even when network HTTP access is configured properly, the Sample Geolocation Showcase application will display the "No HTTP access to Elocation Geocoder Service” notification.
    Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.
  • 21473086 - PKGAPP: LIVEPOLL AUTHENTICATED POLLS DON'T WORK
    In APEX 5.0.1, the LivePoll packaged application has a potential infinite redirect loop when a user tries to access a poll which requires authentication, preventing users from completing these sorts of polls.
    Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.
  • 21464312 - ORA-02091: TRANSACTION ROLLED BACK WHEN IMPORTING APP IN SQLPLUS
    When installing an application in SQL*Plus, the import fails with ORA-02091 if the application was exported in 4.1 or an older version and the application contains invalid references to shared components. Application Express raises this error on the final commit statement for invalid references from breadcrumb region to breadcrumb, list region to list or button to button template.
    Workaround: Install the application in Application Builder or fix the broken references in the old version before exporting again.
  • 21464648 - REFRESH THEME DELETES DISPLAY POINTS IN PAGE AND REGION TEMPLATES
    Using the 'Refreshing Theme' functionality deletes the Display Points configuration of all Page and Region Templates. This has the negative side effects in that Page Designer is not able to show friendly names for REGION_POSITION_xx display points anymore. When running the application the engine no longer knows if the region position supports a grid or not!
    Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.
    Note: If you have already refreshed the theme after upgrading to Application Express 5.0.1, applying the patchset exception and refreshing the theme again will restore the display points.
  • 21463521 - IMAGES DIRECTORY NOT UP-TO-DATE WARNING AFTER APPLYING 5.0.1 PATCHSET
    After applying the Application Express 5.0.1 patchset, developers might receive the below alert when they try to login into the Application Builder although the images files from the patchset have been copied:
    There is a problem with your environment because the Application Express files are not up-to-date! The files for version 5.0.0.00.31 have been loaded, but 5.0.1.00.06 is expected. Please verify that you have copied the images directory to your application server as instructed in the Installation Guide.
    Workaround: Perform a ‘Force Refresh’ in your browser when viewing the Application Builder Login page or clear browser cache. See http://www.wikihow.com/Force-Refresh-in-Your-Internet-Browser
  • 21445226 - COLUMN CSS CLASSES NOT AVAILABLE IN TRANSLATED VERSION
    If CSS classes are specified for the Grid Layout “Column CSS Classes” attribute of Regions, Items or Buttons then those classes will only be used for the primary application language, but will not be present for any translated language.
    Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.
  • 21441233 - DB APP SSO INTERNAL ERROR IF APP HAS CLEANUP PL/SQL CODE
    Database applications which use SSO authentication and have a non-empty Cleanup PL/SQL code block run into an internal error when processing the wwv_flow_custom_auth_sso.process_success callback.
    Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.
  • 21434612 - WEBSHEET SSO ERROR: ERROR PROCESSING AUTHENTICATION
    Websheets which use SSO authentication run into an error processing the authentication when processing the wwv_flow_custom_auth_sso.process_success callback.
    Solution: There is a patchset exception for this available on My Oracle Support - search by bug number 21441233.
  • 21435234 - PLUG-INS: REGION COLUMNS NOT FOUND FOR TRANSLATED APPS
    Regions of type “Column Toggle Report”, “Reflow Report” or custom Plug-ins using the “Region Columns” feature will fail with "ORA-00936: missing expression” when running a translated version of an application.
    Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.
  • 21410037 - HTTP_ERROR_STATUS_ON_ERROR_PAGE_ENABLED IS IGNORED
    The instance parameter HTTP_ERROR_STATUS_ON_ERROR_PAGE_ENABLED is ignored for non-internal errors. (See also "Configuring Unhandled Errors" - https://docs.oracle.com/cd/E59726_01/doc.50/e39151/adm_wrkspc002.htm#BABJHHJI)
    Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.
  • 21266549 - APEX_JSON.PARSE/TO_XMLTYPE RETURNING ORA-06502
    APEX_JSON can parse very large JSON objects, but the maximum length of any string member value is limited to 32767 bytes (i.e. the maximum size of a varchar2). Attempts to parse JSON with longer string member values will result in ORA-06502 Character string buffer too small.
    Workaround: There is no workaround currently available.
  • 11061801 - ORA-00604, ORA-06502 and ORA-06512 errors during index creation.
    If Oracle Workspace Manager is in use in the Oracle Database where you attempt to install Application Express, the installation of indexes may fail.
    Solution: Apply Database Patch 11061801 prior to attempting the upgrade. Search for 11061801 on the Patches tab at support.oracle.com to download the patch.
    Workaround: If you have not installed the patch, then you can workaorund the bug by adding spaces after the table name and each comma.
    For example, change
    create index wwv_flow_preferences$_fkidx on wwv_flow_preferences$(security_group_id,user_id,preference_name)
    to the following statement
    create index wwv_flow_preferences$_fkidx on wwv_flow_preferences$ (security_group_id, user_id, preference_name).
  • 20143941 - Interactive Report Fixed Headings not supported where report renders a complex table
    With Application Express 5.0, Interactive Reports now provide the capability to define fixed column headings, such that the header remains in a fixed in position when the user is scrolling down the report. When a ‘Control Break’ or a ‘Pivot’ is applied, the headings will no longer be fixed.
    Workaround: There is no workaround currently available.
  • 20806980 - Interactive Report Column Filter fails when column value is a link
    If an Interactive Report has a column value that is a link (where the link markup is constructed in the report query) , attempting to define a filter on this value from the column header menu fails. The link may have been defined in the report query as opposed to using the declarative column link support , for example in the case where you want to conditionally render a link, based on some query logic. Note: In previous versions of Application Express, this would work in setting the filter , however this would also have the negative consequence that you would be taken to the link target when selecting the filter value in the column header menu.
    Workaround: To workaround this issue, we recommend the following change to your report:
    1. Add another column to your query, that selects the equivalent of the link text from the link, and define a column alias of 'my_link_display'. This will be the value used in the column header menu.
    2. Change the 'my_link' column to be of type 'Hidden Column'.
    3. In the 'my_link_display' column, set the column heading to be the same as the 'my_link' column and set 'HTML Expression' to be '#MY_LINK#'. Keep the default 'Escape Special Characters' as 'Yes'.
    4. Run the page, and as this is an Interactive Report, you may need to re-order the columns to have the new column in the same position as the old one, via the 'Actions > Select Columns' dialog. Then save this as the defualt report via 'Actions > Save Report > 'Save as Default Report Settings').
    5. Observe now that the link still renders fine in the report, and the column header menu will now render just the 'my_link_display' value, which sets the filter correctly. You will also not be taken to the link target, as was the case in previous version of APEX.
    Note: For this example, we assume the original column name including the link is 'my_link'.
  • 20798913 - Migration from Legacy to CSS Calendar is broken if custom display was used
    Legacy calendar has two type of displaying event title (column or custom) . When the custom type is used, there is no automatic migration of the customized display text.
    Workaround: Change the SQL statement so that the custom column becomes a column that can be mapped to the Display Column attribute. Alternatively, use the Additional Information attribute to add a custom tooltip.