Oracle Application Express 4.2.5

Known Issues

Application Express 4.2.5 was released on April 9, 2014.

This page was last updated on 20-May-2014.

  • 18719750 - ORA-01858 DURING APPLICATION IMPORT
    After upgrading to Application Express 4.2.5 or applying the Application Express 4.2.5 patch set, importing an application and overwriting an existing application results ORA-01858 error as follows:
    Execution of the statement was unsuccessful. ORA-01858: a non-numeric character was found where a numeric was expected
    begin wwv_flow_api.post_import_process(p_flow_id => wwv_flow.g_flow_id); null; end;
    ORA-01858: a non-numeric character was found where a numeric was expected

    Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.
  • 18658967 - CORRUPTED HTML MAIL MESSAGES ARE CREATED FROM APEX_MAIL.SEND
    After upgrading to Application Express 4.2.5 or applying the Application Express 4.2.5 patch set, on some mail servers, any messages sent with the APEX_MAIL.SEND API and which contain an HTML email body will appear to the recipient as corrupted. The recipient will often see that the body of the mail contains message boundaries and headers, like:
      ----=:0CF735AA12E385B1DA023B0BB6124789:
      Content-Type: text/html; charset=utf-8

    Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.
  • 18609856 - APEX_WEB_SERVICE.CLOBBASE642BLOB CONVERTS INCORRECTLY
    In some instances the function APEX_WEB_SERVICE.CLOBBASE642BLOB will fail to decode the input properly if the input was not encoded using APEX_WEB_SERVICE.BLOB2CLOBBASE64.
    Solution: If you have a BASE64 encoded document that is not properly decoded using APEX_WEB_SERVICE.CLOBBASE642BLOB, there is a patchset exception for this available on My Oracle Support - search by bug number.
  • 18601802 - ANYCHART XMLFILE WARNING DISPLAYED PRIOR TO FLASH CHART RENDERING
    When Flash charts that take a long time to render, the user may briefly see the following warning message displayed "XMLFile parameter is not supported by Oracle APEX, please use setXMLFile() method instead." The chart will still be rendered.
    Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.
  • N/A - P-TRACK FLEX FIELDS MISSING FROM MILESTONES REPORT
    After assigning a flex field to milestones in the P-Track packaged application, the new field(s) are not included in the interactive report view under the Milestones tab.
    Solution: Run the following code in the parsing schema for P-Track:
    insert into eba_proj_flex_page_map
      (flex_table, page_id, region_id, flex_column_prefix, region_type)
    select 'EBA_PROJ_STATUS_MS', 63, pr.region_id, 'MILESTONE', 'IR'
    from apex_application_page_regions pr
    where pr.application_name = 'P-Track'
    and pr.page_id = 63
    and pr.source_type_code = 'DYNAMIC_QUERY'
    and not exists (select null
                    from eba_proj_flex_page_map
                    where page_id = 63
                    and region_id = pr.region_id);