This page was last updated on 29-June-2015.

• 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.

• 20931298 - Report download files are broken if DB Version < 11.2.0.3

  If your database version is 11.1.x, 11.2.0.1, 11.2.0.2 or 11gXE, downloading Interactive Reports, Classic Reports or uploaded report layout files can produce corrupt data in the downloaded file.

  Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.

  If using ORDS (Apex Listener), restart it after installing the patch.

• 20974582 - apex_json.parse errors when parsing clobs if DB Version < 11.2.0.3

  If your database version is 11.1.x, 11.2.0.1, 11.2.0.2 or 11gXE, apex_json.parse may report errors when parsing a clob.

  Solution: There is a patchset exception for this available on My Oracle Support - search by bug number 20931298. If using ORDS (Apex Listener), restart it after installing the patch.

  Workaround: If you have not installed the patch, then you can use the overloaded parse procedures which take varchar2 or table of varchar2 instead.

• 21041454 - Password error in create workspace (4050:72) if internal auth is LDAP or DB

  If you changed the authentication scheme of the development environment to "Database Accounts" or "LDAP Directory", the Create Workspace wizard reports a verification failure for the workspace administrator's password.

  Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.

  Workaround: If you have not installed the patch, then you can either temporarily switch back to "Application Express Accounts" authentication to create the workspace or use the documented API APEX_INSTANCE_ADMIN.ADD_WORKSPACE in sqlplus.

• 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

  Copy

  Copied to Clipboard

  Error: Could not Copy

  create index wwv_flow_preferences$_fkidx on wwv_flow_preferences$(security_group_id,user_id,preference_name)

  to the following statement

  Copy

  Copied to Clipboard

  Error: Could not Copy

  create index wwv_flow_preferences$_fkidx on wwv_flow_preferences$ (security_group_id, user_id, preference_name).

• 20929652 - Page Designer splitter widget issues when changing builder language

  When switching the Application Builder to a language that uses a comma as the decimal separator the Page Designer splitters give an error, which leaves the Page Designer unusable. This only happens if the page designer was previously used in a language that uses period as the decimal separator AND the browser reported the splitter position with a decimal part.

  Workaround: Remove splitter preferences with the following code entered in SQL Workshop > SQL Commands then change languages:

  Copy

  Copied to Clipboard

  Error: Could not Copy

  begin
    apex_util.remove_preference( 'F4000_1157687726908338238_SPLITTER_STATE' );
    apex_util.remove_preference( 'F4000_203904827661009901_SPLITTER_STATE' );
    apex_util.remove_preference( 'F4000_203906404237009921_SPLITTER_STATE' );
    apex_util.remove_preference( 'F4500_1157684150404338202_SPLITTER_STATE' );
    apex_util.remove_preference( 'F4500_1157684743709338208_SPLITTER_STATE' );
    apex_util.remove_preference( 'F4500_1157684935965338210_SPLITTER_STATE' );
    apex_util.remove_preference( 'F4500_1157686386582338224_SPLITTER_STATE' );
    commit;
  end;

• 20921875 - API Guide: Typo in apex_json find_paths_like function example

  Within the Application Express 5.0 API Guide a number of the APEX_JSON function syntax and example code snippets are incorrectly documented.

  Workaround: Review the package specification for APEX_050000.WWV_FLOW_JSON.

• 20539071 - ORA-00979: Not a group by expression, raised on apex active sessions page

  On the Workspace Administration -> Monitor Activity -> Active Sessions page, this report will return ORA-00979: NOT A GROUP BY EXPRESSION in Oracle Database 12.1.0.1 and 12.1.0.2.

  Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.

• 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.

• 20860160 - Cannot load > 32k spreadsheet data with copy and paste to an existing table

  The data cuts off when trying to load more than 32KB to an existing table using copy and paste option in spreadsheet load wizard of data workshop (SQL Workshop > Utilities > Data Workshop > Load Spreadsheet Data).

  Solution: There is a patchset exception for this available on My Oracle Support - search by bug number. As a workaround, you can upload the file instead of using the copy and paste option.

• 20381781 - Error occurs when upgrading apex 4.2.5.00.08 in 12.1.0.2 DB to APEX 5.0

  When attempting to upgrade a multitenant container database (CDB) to Oracle Application Express 5.0, catcon.pl will report an error and the following errors can be seen in the catcon.pl installation logs:

  ORA-00001: unique constraint (APEX_050000.WWV_FLOW_BANNER_U_IDX) violated

  Solution: Apply Database Patch 20618595 prior to attempting the upgrade. Search for 20618595 on the Patches tab at support.oracle.com to download the patch.

• 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'.

• 20729435 - Interactive Report Column Link Text property quick pick does not set the value

  Properties that are displayed due to a dependency to some other property (eg Link Text displays when the Link is defined) , that also have quick picks, will have their quick picks not selecting the value directly after the property has been displayed. In addition, after new properties have been displayed due to a dependency , this also makes some other properties with quick picks no longer open their quick pick menu (eg Column Filter > Type, after a Link has been defined).

  Workaround: After refreshing the Property Editor, (for example by saving and reloading the page, or by selecting a different component, then going back to the component) , quick picks will once again work.

• 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.