Application Express 5.0.4 was first released on July 12, 2016.

This page was last updated on October 10, 2016.

• 24673469 - APEX_UTIL.PREPARE_URL SLOW IN APEX 5.0.X

  The PREPARE_URL function is slow when referencing applications in a different workspace.

  Solution: There is a patchset exception for this available on My Oracle Support - search by bug number 24328069.

• 24810475 - APEX 5 PERFORMANCE ISSUE DOWNLOADING FROM SQL WORKSHOP

  Performance issue while trying to download SQL query results into .csv format from SQL Workshop > SQL Commands.

  Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.

• 24009816 - RESTFUL SERVICE IMPORT ORA-00001:UNIQUE CONSTRAINT (WWV_FLOW_RT$MODULES_PK)

  Importing a RESTful Services module using the UI (app 4850), can result in the following error:

  
  ORA-20001: WWV_FLOW_API.ERR_CREATE_REST_MODULE ORA-00001: unique constraint (APEX_050000.WWV_FLOW_RT$MODULES_PK) violated        
     Execution of the statement was unsuccessful. 
  ORA-20001: WWV_FLOW_API.ERR_CREATE_REST_MODULE ORA-00001: unique constraint (APEX_050000.WWV_FLOW_RT$MODULES_PK) violated

  Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.

• 22937702 - CSV TYPE DOWNLOAD IS TAKING A LONG TIME

  When trying to download a interactive report as csv type it's taking a long time.

  Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.

• 24704891 - GERMAN TRANSLATION FOR AN APEX APPLICATION - ORA-06502 ERROR ON WEB SERVICES

  Attempting to create a German translation for an application - Errors on Web Services. An application, developed in English, uses Restful Web Services to get and send data to remote data sources. - Created a German translation application using the Translate Application feature in Shared Components. - Seeded the data from the main application 1000 into a German sub application 1011. - Uploaded two pages that have been translated using the XLIFF files. Applied them and published it.

  Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.

• 24328069 - CHANGE BEHAVIOR OF HTTP_ERROR_STATUS_ON_ERROR_PAGE_ENABLED

  This request is to augment the functionality imposed by instance setting HTTP_ERROR_STATUS_ON_ERROR_PAGE_ENABLED, and only have it raise an HTTP 400 if the user running the application is not also logged into the APEX development environment.

  Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.

• 24413804 - APEX_MAIL: ORA-06502 AND MAIL STUCK IN QUEUE

  When sending mails with length n*900+2 where the last characters are CRLF (\000d\000a), APEX_MAIL raises ORA-06502, on database versions prior to Oracle Database 12cR1 (12.1.0.2). The mail will be sent multiple times, because it is stuck in the queue.

  Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.

• 24347447 - WORKSPACE W/ ONLY SQL WORKSHOP ACCESS CONTINUOUSLY PROMPTS TO CHANGE PASSWORD

  When workspace developers who have only SQL Workshop Access (i.e. no Application Builder Access or Team Development Access) attempt to log in, they always get redirected to the change password page.

  Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.

• 24009816 - RESTFUL SERVICE IMPORT FAILS WITH A UNIQUE CONSTRAINT ERROR

  Importing a RESTful Services module using the Application Builder (App 4850), can result in the following error:

  
  ORA-20001: WWV_FLOW_API.ERR_CREATE_REST_MODULE ORA-00001: unique constraint (APEX_050000.WWV_FLOW_RT$MODULES_PK) violated. 
  Execution of the statement was unsuccessful.

  Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.

• 22588461 - ORDS 3.0.3 FAILS WHEN RUN AGAINST A NEW INSTALLATION OF APEX 5.0.3

  If you have configured Oracle REST Data Services (ORDS) 3.0.3 against a new or upgraded installation of Oracle Application Express 5.0.3, static image links will not be displayed. This issue impacts both new installations and patched installations of APEX 5.0.3, where ORDS is newly configured against the APEX instance after the install/upgrade to APEX 5.0.3.

  Solution: Download ORDS 3.0.6 from OTN, and upgrade from ORDS 3.0.3 to 3.0.6, in order to resolve this issue.

• 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

  Copy

  
  create index wwv_flow_preferences$_fkidx on wwv_flow_preferences$(security_group_id,user_id,preference_name)

  to the following statement

  Copy

  
  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.