apex

Oracle APEX Known Issues - APEX 19.2

Downloads

APEX 19.2.0.00.18 was released on November 1, 2019.

Please review the Release Notes for significant issues known at time of release. Any new significant issues will be added here. This page was last updated on February 5, 2020.

Note: Review the APEX 18.1 and above Known Issues Addendum for important information regarding flash charts.

  • 30741141 - CASCADING SELECT LIST SHOWS 'UNDEFINED' FOR NULL VALUES

    When a child select list (where it has a Cascading LOV Parent) is refreshed, if any of the new options returned are null, these will be incorrectly displayed as 'undefined' in the select list options.

    Solution: A PSE has been made available for this issue on MyOracleSupport.

    Navigate to Patches & Updates and search for patch number 30392181.

    Note: this PSE also contains other bug fixes, please review the README in the patch for more details.

  • 30646890 - ORACLE_APEX_DICTIONARY_CACHE JOB FAILS WITH ORA-06502

    If column statistics is not in sync with the column type change (i.e. change from VARCHAR2 to NUMBER), APEX data dictionary cache job, ORACLE_APEX_DICTIONARY_CACHE, fails with

    ORA-06502: PL/SQL: numeric or value error.

    Solution: A PSE has been made available for this issue on MyOracleSupport.

    Navigate to Patches & Updates and search for patch number 30392181.

    Note: this PSE also contains other bug fixes, please review the README in the patch for more details.

  • 30748465 - CREATE NEW SESSION AS PART OF "BECOME USER" DOES NOT WORK

    Applications that implement a "become user" feature, which creates a new session as a different user, can fail with APEX complaining that the session changed.

    Solution: A PSE has been made available for this issue on MyOracleSupport.

    Navigate to Patches & Updates and search for patch number 30392181.

    Note: this PSE also contains other bug fixes, please review the README in the patch for more details.

  • 30675432 - INTERACTIVE GRID VIRTUAL COLUMN WITH SOURCE=NONE DISPLAY NO ROWS

    In an interactive grid if you add a virtual column as a select list to the report, the existing records in the report will not display if you set the source for the virtual column to none.

    Solution: A PSE has been made available for this issue on MyOracleSupport.

    Navigate to Patches & Updates and search for patch number 30392181.

    Note: this PSE also contains other bug fixes, please review the README in the patch for more details.

  • 30675656 - ORACLE_APEX_DICTIONARY_CACHE FAIL WITH ORA-00001: UNIQUE CONSTRAINT (APEX_190200.WWV_DICTIONARY_CACHE_OBJ_IDX1)

    If a workspace contains other object types with the same name as a table, APEX data dictionary cache job, ORACLE_APEX_DICTIONARY_CACHE, fails with

    ORA-00001: UNIQUE CONSTRAINT (APEX_190200.WWV_DICTIONARY_CACHE_OBJ_IDX1)

    Workaround: Remove the duplicate object that is not a table. You can list database objects by selecting from sys.dba_objects.

    Solution: A PSE has been made available for this issue on MyOracleSupport.

    Navigate to Patches & Updates and search for patch number 30392181.

    Note: this PSE also contains other bug fixes, please review the README in the patch for more details.

  • 26788756 - THE E-MAIL ATTACHMENT GENERATED BY APEX IS NOT IN COMPLIANCE WITH RFC 2045

    The standard RFC 2045 (https://www.ietf.org/rfc/rfc2045.txt) describes Base64 Encoding (Page 24): "The encoded output stream must be represented in lines of no more than 76 characters each.". The e-mail attachment generated by APEX sometime contains lines longer than 76 characters.

    Solution: A PSE has been made available for this issue on MyOracleSupport.

    Navigate to Patches & Updates and search for patch number 30392181.

    Note: this PSE also contains other bug fixes, please review the README in the patch for more details.

  • 30636867 - APEX_WEB_SERVICE.MAKE_REST_REQUEST IN APEX 19.2 DOES NOT IMPLICITLY CONVERT P_BODY TO UNICODE ANY MORE

    When POSTing data with special characters via APEX_WEB_SERVICE.MAKE_REST_REQUEST on a database with a DB character set that is not AL32UTF8, the data remains in the DB character set and is not converted to UTF8, as in older APEX releases.

    Solution: A PSE has been made available for this issue on MyOracleSupport.

    Navigate to Patches & Updates and search for patch number 30392181.

    Note: this PSE also contains other bug fixes, please review the README in the patch for more details.

  • 30533928 - ORACLE_APEX_DICTIONARY ORA-29913: ERROR IN EXECUTING ODCIEXTTABLEOPEN CALLOUT

    If a workspace contains external tables and points to a file that does not exist, APEX data dictionary cache job, ORACLE_APEX_DICTIONARY_CACHE, fails with ORA-29913: error in executing ODCIEXTTABLEOPEN callout.

    Workaround: Place an empty file in the directory with the same file name external table is pointing to.

    Solution: A PSE has been made available for this issue on MyOracleSupport.

    Navigate to Patches & Updates and search for patch number 30392181.

    Note: this PSE also contains other bug fixes, please review the README in the patch for more details.

  • 30617262 - INTERACTIVE GRID OR REPORT FAILS WITH ORA 6502 ON 12.1 OR 11.2 IF LOV COLUMN HAS MORE THAN 26 CHARACTERS

    If APEX runs on 11.2 or 12.1 (Oracle Identifiers have 30 bytes max), an Interactive Grid column name is longer than 26 characters, and the Interactive Grid column is an LOV column, then page rendering fails with

    ORA-6502: Character String Buffer too small.

    Workaround: in the report query, use a column alias for the LOV column, which is below 27 bytes.

    Solution: A PSE has been made available for this issue on MyOracleSupport.

    Navigate to Patches & Updates and search for patch number 30392181.

    Note: this PSE also contains other bug fixes, please review the README in the patch for more details.

  • 30535914 - INTERACTIVE GRID DOWNLOAD RETURNS NULL VALUES FOR CASCADING LOV COLUMNS

    When downloading an Interactive Grid report then columns that are defined as Cascading LOVs are output as null columns.

    Solution: A PSE has been made available for this issue on MyOracleSupport.

    Navigate to Patches & Updates and search for patch number 30392181.

    Note: this PSE also contains other bug fixes, please review the README in the patch for more details.

  • 30520385 - INTERACTIVE GRID DML PROCESS WITH CUSTOM PL/SQL CODE USING :ROWID ERRORS OUT WITH "STOP APEX ENGINE"

    If a custom PL/SQL process, which uses the :ROWID alias, is used for a page process related to an Interactive Grid region, then it will raise an error when executed. Upon save, the process will throw "ORA-20876: Stop APEX Engine"

    Workaround: Select the ROWID column explicitly in the SQL query and use a column alias (select rowid rowid_alias, ... from ...). Then use the :ROWID_ALIAS bind in your custom PL/SQL code.

    Solution: A PSE has been made available for this issue on MyOracleSupport.

    Navigate to Patches & Updates and search for patch number 30392181.

    Note: this PSE also contains other bug fixes, please review the README in the patch for more details.

  • 30517479 - SAVE CHANGES FOR MASTER DETAIL INTERACT GRID FAILS WITH ORA-06502 FOR NEW MASTER WITH NEW DETAIL ROWS

    If you add both a master record and a detail in the one transaction then it will fail with "ORA-06502: PL/SQL: numeric or value error: character to number conversion error". This error is only raised if you submit the page, not if using a Save button within an Interactive Grid region.

    Workaround: Save the master row first, then add the detail rows.

    Solution: A PSE has been made available for this issue on MyOracleSupport.

    Navigate to Patches & Updates and search for patch number 30392181.

    Note: this PSE also contains other bug fixes, please review the README in the patch for more details.

  • 30512418 - APEX.ITEM('P1_SWITCH_ITEM').ISCHANGED() ALWAYS RETURNS TRUE

    Even if you do not change the value of a switch, e.g. P1_SWITCH_ITEM, apex.item('P1_SWITCH_ITEM').isChanged() always returns true.

    Solution: A PSE has been made available for this issue on MyOracleSupport.

    Navigate to Patches & Updates and search for patch number 30392181.

    Note: this PSE also contains other bug fixes, please review the README in the patch for more details.

  • 30512102 - SWITCH ITEM RETURNS EMPTY STRING IF ITS ON OR OFF VALUE IS SET TO 0

    If you have a Switch item defined using custom component settings with the "Off Value" set to "0", then the zero value will not be returned correctly.

    Solution: A PSE has been made available for this issue on MyOracleSupport.

    Navigate to Patches & Updates and search for patch number 30392181.

    Note: this PSE also contains other bug fixes, please review the README in the patch for more details.

  • 30511566 - FACETED SEARCH: COMPUTE COUNTS DOES NOT PROCESS WEB SRC PARAMETERS CORRECTLY

    This issue happens when a faceted search is created on top of a Web Source Module and one of the parameters has the "Use For Row Search" attribute set to "Yes". When a search is performed the results are displayed correctly, however, all facets are disabled and have zero counts.

    Solution: A PSE has been made available for this issue on MyOracleSupport.

    Navigate to Patches & Updates and search for patch number 30392181.

    Note: this PSE also contains other bug fixes, please review the README in the patch for more details.

  • 30505223 - TABLE/VIEW OWNER SELECT LIST ON EDIT LOV (4000:4111) PAGE CAN INITIALIZE WITH WRONG SCHEMA

    When using an LOV with Query Type = TABLE and the parsing schema of the application has select privileges on objects in other schemas, then the "Table / View Owner" select list on 4000:4111 is initialized with the wrong schema.

    Solution: A PSE has been made available for this issue on MyOracleSupport.

    Navigate to Patches & Updates and search for patch number 30392181.

    Note: this PSE also contains other bug fixes, please review the README in the patch for more details.

  • 30504903 - APEX_REGION.OPEN_QUERY_CONTEXT DOES NOT WORK WITH INTERACT. REPORT PIVOT VIEWS

    When using the new APEX_REGION.OPEN_QUERY_CONTEXT function for an interactive report PIVOT view, APEX throws an error "ORA-00903: invalid table name" and you can not view the context within debug output.

    Solution: A PSE has been made available for this issue on MyOracleSupport.

    Navigate to Patches & Updates and search for patch number 30392181.

    Note: this PSE also contains other bug fixes, please review the README in the patch for more details.

  • 30498697 - INTERACT GRID DOWNLOAD FAILS WITH ORA-1403 WHEN SQL QUERY IS USED AND ROWID IS THE FIRST COLUMN IN THE LIST

    For Interactive Grids based on a SQL Query, if the query selects the ROWID column and the ROWID column is the first in the Interactive Grid column list, then downloading the data (Actions > Download) fails with ORA-1403.

    Workaround: In Page Designer, move the ROWID column down in the column list.

    Solution: A PSE has been made available for this issue on MyOracleSupport.

    Navigate to Patches & Updates and search for patch number 30392181.

    Note: this PSE also contains other bug fixes, please review the README in the patch for more details.

  • 30489131 - READ ONLY INTERACTIVE GRID LOV COLUMN DOES NOT RESPECT DISPLAY EXTRA=NO

    If you have an Interactive Grid column based on a List of Values with "Display Extra Values" = No, and the column includes an invalid value, then that invalid value will be displayed instead of displaying null.

    Solution: A PSE has been made available for this issue on MyOracleSupport.

    Navigate to Patches & Updates and search for patch number 30392181.

    Note: this PSE also contains other bug fixes, please review the README in the patch for more details.

  • 30492531 - COPY FACETED SEARCH REGION TO OTHER PAGE FAILS WITH SERVER ERROR

    Copying a Faceted Search region to another page fails, and results in a server error.

    Workaround: No current workaround available.

  • 30489726 - INTERACTIVE GRID REVERT CHANGES IN EDIT MODE LEAVES FLOATING ITEM VISIBLE

    Reverting Changes from the Row Actions menu while in edit mode may causes a floating editing item to be visible in the upper left corner of the page.

    Workaround: Exit edit mode before reverting changes.

  • 30484315 - INTERACTIVE GRID: WHEN REGION IS MAXIMIZED, FLOATING EDITABLE CELL CONTENT DOESN'T SHOW

    When editing an Interactive Grid in a region that is maximized (standard region template maximize feature) any cells that are edited in floating popup are not visible.

    Workaround: Add this CSS rule to the page or in a global app css file: 

    
.a-GV-floatingItem {
    visibility: visible;
}
  • 30482266 - SIDE-EFFECTS OF REMOVAL OF JQUERY AUTOCOMPLETE LIBRARY IN PACKAGED APPS

    In the 19.2 development cycle, as part of cleaning our code base and standardizing the packaged apps, we removed all places where we referenced the old 'jquery-autocomplete' JavaScript library. This used to be used by our old 'Text with autocomplete' native item type pre-19.1, and still in 19.1 by the 'Tag Entry' custom plug-in, used in a number of packaged apps. All of the places we used this plug-in in our packaged apps were replaced with the new Popup LOV in 19.2, and we also removed the underlying library from the distribution. However this has had the undesirable consequence that immediately after upgrading to 19.2, existing packaged apps will run into errors on the pages where this was used, because the library has been removed. The affected packaged apps are:

    • Opportunity Tracker
    • Group Calendar
    • Customer Tracker
    • P-Track
    • Data Reporter
    • Bug Tracking
    • Incident Tracking

    Solution for 'Locked' Applications: Simply need to update the packaged app. Go to the packaged application you want to update, and select 'Update'.

Solution for 'Unlocked' Applications: This is a manual process, where you will need to do the following:

  1. Search for all occurrences of the 'Tag Entry' plug-in (you can see all the places it is used by going to the application, then Shared Components, Plug-ins, then select 'Utilization').
  2. Go into each affected page, and switch the item using the 'Tag Entry' plug-in over to use the new Popup LOV item type, with the following settings:
    1. Display Popup As: Inline (default)
    2. Multiple Values = On
    3. Manual Entry = On
    4. Search as you type = On
  3. Once all references have been removed, you can then safely remove the 'Tag Entry' plug-in from the packaged application.

Note: If you had written any custom JavaScript code utlizing the 'jquery-autocomplete' JavaScript library, if possible, we would recommend you look at switching over to using the new Popup LOV item type. Alternatively if that is not an option, you can download the same library that was used, and install that in your environment. It is still available to download here: http://www.bassistance.de/jquery-plugins/jquery-plugin-autocomplete/

  • 30472566 - INTERACTIVE GRID SAMPLE M-D PACKAGED APP -> STACKED WITH SUB DETAILS PAGE THROWS JS ERROR

    Using advanced configuration to disable the gridView of Interactive Grid as is done on page 17 of the Sample Master Detail app results in a JavaScript exception. The purpose is to force the master Interactive Grid to be in Single Row View mode.

    Workaround: Do not disable gridView but let the user manually enter Single Row View or do so programmatically after the page loads.

  • 30461018 - PARSING SCHEMA POPUP LOV ITEM ON APPLICATION SECURITY PAGE DISPLAYS NO VISIBLE RESULTS

    On the Security Attributes page of an application (available via Shared Components > Security Attributes), the 'Parsing Schema' Popup LOV item displays no visible results when opened, which means you are unable to select from the application's available parsing schemas.

    Workaround: You can still enter the parsing schema manually in that item. To see a list of available schemas, go to the SQL Workshop and there you will see the list of schemas in the 'Schema' select list on the right of the page.

Changed Behavior:

  • N/A - JQUERY AND JQUERY UI UPGRADE

    Oracle APEX 19.2 includes jQuery 3.4.1, which breaks compatibility with earlier 2.x versions. If your application relies on removed 2.x, or 1.x jQuery functionality, then this functionality will no longer work.

    Workaround: For applications that still rely on removed 2.x functionality, you can use the jQuery Migrate plug-in. To include this plug-in, set the Desktop User Interface Details attribute Include jQuery Migrate to Yes.

    If your application relies on removed 1.x jQuery APIs, that functionality will no longer work, and you must update the JavaScript to only use jQuery 3.1 APIs.

    Review the jQuery migration guides to learn more:

    For further information including information about the jQuery UI upgrade, please review section 9.1.3 Known Issues for jQuery and jQuery UI in the release notes.