Oracle Application Express

Known Issues - Application Express 5.0.3

Application Express 5.0.3 was first released on December 21, 2015.
The same files were released again on January 22, 2016 to correct Bug 22588461.

This page was last updated on January 22, 2016.

  • 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 installation of Oracle Application Express 5.0.3, static image links will not be displayed. This issue only impacts new installations of APEX 5.0.3, and not updates from early versions of APEX 5.0.x using the APEX 5.0.3 patch set.
    Note: Application Express 5.0.3 download files (apex_5.0.3.zip and apex_5.0.3_en.zip) obtained after January 22, 2016 already include the corrected files.
    Solution: There is a patchset exception for this available on My Oracle Support - search by bug number 21537995. This file will run against Application Express 5.0.3 installations.
    Workaround: If you do not have acces to My Oracle Support to obtain the patchset exception, we recommend the following based on the Oracle Database installation:
    1. Download Application Express 5.0.3 from the Oracle Application Express download page.
    2. Unzip the downloaded zip file.
    3. Change your working directory to apex/core.
     
    For NON Multitenant environments (Oracle Database 11g and Oracle Database 12c Stand Alone):
    4. Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS specifying the SYSDBA role.
    5. Run the following commands:
    alter session set current_schema = APEX_050000;
    @view.sql
    alter session set current_schema = SYS;
    exec sys.validate_apex;

     
    For Oracle Database 12c Multitenant where Application Express is installed into individual PDBs:
    4. Start SQL*Plus and connect to each PDB where Oracle Application Express is installed as SYS specifying the SYSDBA role.
    5. Run the following commands in each PDB:
    alter session set current_schema = APEX_050000;
    @view.sql
    alter session set current_schema = SYS;
    exec sys.validate_apex;

     
    For Oracle Database 12c Multitenant where Application Express is installed in the Container Database (CDB):
    4. Create a new text file in that directory named invoke_view.sql consisting of the following:
    alter session set current_schema = APEX_050000;
    @view.sql
    alter session set current_schema = SYS;
    exec sys.validate_apex;

    5. Create another text file named invoke_vew_cdb.sql consisting of the following:
    set define '^'
    whenever sqlerror exit
    column :cdb_home new_value OH_HOME NOPRINT
    variable cdb_home varchar2(255)
    set serverout on
    begin
    -- get oracle_home
    sys.dbms_system.get_env('ORACLE_HOME',:cdb_home);
    if length(:cdb_home) = 0 then
    sys.dbms_output.put_line(lpad('-',80,'-'));
    raise_application_error (
    -20001,
    'Oracle Home environment variable not set' );
    end if;
    end;
    /
    whenever sqlerror continue
    set termout off
    select :cdb_home from sys.dual;
    set termout on
    host ^OH_HOME/perl/bin/perl -I ^OH_HOME/rdbms/admin ^OH_HOME/rdbms/admin/catcon.pl -b invoke_view_cdb invoke_view.sql

    6. Start SQL*Plus and connect to CDB$ROOT of the database where Oracle Application Express is installed as SYS specifying the SYSDBA role.
    7. Execute the following commands:
    @invoke_vew_cdb.sql
  • 22532860 - APEX_JSON: XML TO JSON CONVERSION TREATS 0 AS STRING AND 0123 AS NUMBER
    The overloaded APEX_JSON.WRITE procedures for XMLTYPE and SYS_REFCURSOR convert XML to JSON. This conversion emitted the number 0 as a JSON string value and digits preceded by leading zeroes (e.g. 0123) as a (invalid) JSON number.
    Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.
  • 22493656 - UPGRADING APEX 4.2 TO 5.0.3 THROWS ORA-20001: COMPILE ERROR: "PACKAGE BODY”
    Upgrading Oracle Application Express to 5.0.3 on Oracle Databases prior to version 11.2.x will result in a reported error in the installation log and the APEX component set to INVALID in sys.dba_registry.
    Note: This patchset exception only applies to database versions prior to 11.2.x. It is not necessary to apply this patch to Oracle Database versions 11.2.x and above.
    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.