Oracle Application Express

Known Issues with Release 4.1

Application Express 4.1 was released on August 24, 2011.

Below is a list of known issues with 4.1.

This page was last updated on 28-Nov-2011.

  • 12934779 - EXISTS/NOT EXISTS/PLSQL EXPRESSION DOESN'T WORK FOR HIERARCHICAL LIST ENTRY
    In version 4.1, if the "List Entry Current for Page Type" for an hierarchical static list entry is set to one of the following: Exists SQL Query, Not Exists SQL Query or PL/SQL Expression, the list will fail with an ORA-20001: Query must begin with SELECT or WITH error.
    Solution: There is a patchset exception for this available on metalink - search by bug number.
  • 13375538 - APEXEXPORT -EXPFEEDBACK NOT WORKING IN 4.1
    13355663 - APEXEXPORT WORKSPACE EXPORT NO LONGER WORKS
    Using the APEXExport java program located in the utilities directory results in a 0 byte file when exporting either workspaces or Team Development feedback on an Application Express 4.1 instance. This patchset exception also fixes bug 12931249.
    Solution: There is a patchset exception for this available on metalink which corrects both bugs - search by bug number 13375538.
  • 13349731 - SESSION 0: INITIAL REDIRECT TO SET COOKIES CONFUSES SEARCH BOTS
    If a user sends a request for a public page with session 0, e.g. f?p=myapp:home:0, APEX responds with a redirect to f?p=myapp:home:0 that sets the session cookie. This is a change in behaviour from previous versions, which did not cause this redirect. The redirect confuses some search bots, who do not set the cookie when re-sending the request and therefore cause an endless loop.
    Solution: There is a patchset exception for this available on metalink - search by bug number.
  • 13045147 - APEX_CUSTOM_AUTH.POST_LOGIN SHOULD NOT CALL AUTHENTICATION FUNCTION
    In version 4.1, calls to wwv_flow_custom_auth_std.post_login() behave like calls to login(). The procedure called the pre-authentication and authentication functions. It therefore required a valid username/password combination and could not be used to simply change the user, as in previous versions.
    Solution: There is a patchset exception for this available on metalink - search by bug number.
  • 12955671 - HTTP HEADER VARIABLE AUTH: ENDLESS REDIRECT IF USERNAME IS CASE SENSITIVE
    An authentication scheme of type 'HTTP Header Variable' performed endless redirects if the username provided in the environment variable was mixed-case or in lowercase. This patchset exception also makes the authentication scheme work correctly with Oracle Access Manager.
    Solution: There is a patchset exception for this available on metalink - search by bug number.
  • 12934733 - NOT ABLE TO UPDATE WEB SERVICE PROCESS
    If a Web service process is updated which references a Web service with parameters, the Builder raises a ORA-01403: no data found when the "Apply Changes" button is clicked.
    Solution: There is a patchset exception for this available on metalink - search by bug number.
  • 12931249 - SESSION STATE PROTECTION VIOLATION ERROR FOR URL CONTAINING CHECKSUM
    If the URL which is used to access an APEX application contains the cs parameter to provide an application level checksum for the page item arguments, it will get escaped when then APEX authentication performs a redirect to display the new session id.
    For example, http://abc/apex/f?p=732:2:::NO::P2_DEPTNO:20&cs=17DCBC90CAC9D16166EFA839ABB56107A
    becomes http://abc/apex/f?p=732:2:::NO::P2_DEPTNO:20%26cs%3D17DCBC90CAC9D16166EFA839ABB56107A
    which will result in the error:
    "Session state protection violation: This may be caused by manual alteration of a URL containing a checksum or by using a link with an incorrect or missing checksum. If you are unsure what caused this error, please contact the application administrator for assistance."
    This error will only occur if APEX has no valid session when a page is rendered. For example if such a URL is bookmarked. Checksums generated and used during an APEX session will work fine.
    Solution: There is a patchset exception for this available on metalink - search by bug number.
  • 12927540 - IMPORTED TRANSLATIONS HAVE AN INCORRECT MAPPING FROM ID
    When importing an application export which includes translations, the ID values in the imported translation repository may not reflect the adjusted language mapping ID. Since the IDs are incorrect in the translation repository, the publish operation will not use the translated text from the translation repository.
    Solution: There is a patchset exception for this available on metalink - search by bug number.
  • 12927199 - EXPORT TRANSLATIONS RESULTS IN ERROR ORA-06502 WHEN TRANSLATING LARGE VALUES
    When perform an an application export and including translations in the application export, if any translatable value is over 4,000 characters in length, the export operation will result in error ORA-06502: PL/SQL: numeric or value error: character string buffer too small.
    Solution: There is a patchset exception for this available on metalink - search by bug number.
  • 12920544 - WORKSPACE TO SCHEMA ASSIGMENT THROWS ORA-01741 ERROR FOR EXISTING SCHEMAS
    When manually assigning an existing schema to a workspace, the final step of the wizard will result in error ORA-01741: illegal zero-length identifier.
    Solution: There is a patchset exception for this available on metalink - search by bug number.