Oracle Application Express

Known Issues with Release 4.1.1

Application Express 4.1.1 was released on February 21, 2012.

Below is a list of known issues with 4.1.1.

This page was last updated on 1-June-2012.

  • Not Applicable - POSSIBLE MEMORY LEAK WHEN USING INTERNET EXPLORER 7
    Some customers have experienced memory leaks when accessing Application Express Builder using IE7.
    Solution: Use IE8 or above to access the Application Express development environment. Alternatively use Google Chrome, Firefox, or Safari as outlined in the Installation Guide - Browser Requirements here.
  • 13780604 - UPLOAD WIZARD FAILS IF EXPORTED TO A DIFFERENT WORKSPACE
    With Application Express 4.1.1, this issue can occur if an application developed in one workspace is exported and imported into another workspace. If the application has a Data Upload definition already created, it will contain the name of the previous owner and this will cause the data upload to fail.
    Solution: There is a patchset exception for this available on metalink - search by bug number.
  • 14075570 - CACHED RESULTS FOR RESULT_CACHE_MODE='FORCE' AND NON-DETERMINISTIC FUNCTIONS
    On Oracle 11g, a database-wide setting of RESULT_CACHE_MODE='FORCE' can cause errors in Apex Lists of Values.
    Solution: Set RESULT_CACHE_MODE='MANUAL' for the database instance.
  • 13331096 - CONVERTING APPLICATION EXPRESS 4.1.0 RUNTIME ENVIRONMENT TO 4.1.1 FULL DEVELOPMENT ENVIRONMENT
    When Application Express 4.1.0 runtime environment is upgraded to version 4.1.1 using patch set 13331096 and then converted to a full development environment, certain Application Builder fixes contained in the patch set are not applied. This issue does not occur when Application Express 4.1.0 full development environment is upgraded using this patch set.
    Solution: After converting the instance to a full development environment, re-apply version 4.1.1 patch set 13331096.
  • 13878034 - ORA-06550 ERROR WHEN EDITING USER IN INTERNAL ADMINISTRATION
    On Oracle 10g, the "Application Express Internal Administration" application raises the error above when clicking "Apply Changes" on the "Create / Edit User" page (4050:23). This error does not occur on Oracle 11g.
    Solution: There is a patchset exception for this available on metalink - search by bug number.
  • 13895777 - APP URL WITH FIRST PAGE AS PUBLIC AND AUTOMATIC TIMEZONE SET TO YES THROWS ERROR
    This error can occur when running applications where the first page is public and "Automatic Time Zone" is set to "Yes" (Home > Application Builder > Application xxx > Edit Globalization Attributes). The rendered output can be an empty page or a Java error stack, depending on whether mod_plsql, the Embedded PL/SQL Gateway or the Apex listener is used. The reason is that version 4.1.1 does not properly close the HTTP header before emitting it's timezone detection code.
    Solution: There is a patchset exception for this available on metalink - search by bug number.