Oracle Application Express - Known Issues
application-express
Oracle Application Express 4.2
Known Issues
Application Express 4.2 was released on October 12, 2012.
This page was last updated on 13-Dec-2012.
- HTML ESCAPING MODE CAN NOT BE CHANGED IF COMPATIBILITY IS PRE 4.1
The region &Browser Security& on an application's 'Security' tab contains the option &HTML Escaping Mode&. While this option is also relevant for applications which run in compatibility mode &Pre 4.1&, it is not visible if that mode is configured.
Solution: Change the &Compatibility Mode& to 4.1 or newer, modify &HTML Escaping Mode& and reset &Compatibility Mode&.
- MAPS AND GANTTS SHOULD NOT BE AVAILABLE FOR UPGRADE TO HTML5 IN 4.2
After an upgrade from Application Express 4.1 to 4.2, when the Upgrade Application wizard is used to upgrade Flash charts to HTML5 in an application exported from an earlier version of APEX, maps are included in the list of Flash regions to upgrade. An upgraded map will result in the following error:
Error Message: Feature is not supported. Feature: Plot type Map.
AnyChart does not currently support HTML5 maps, therefore maps should not be included in the Upgrade Application wizard.
Solution: No workaround currently available.
- PAGE SUBMIT DOES NOT WORK ON WINDOWS PHONE
Submitting pages using the Application Express JavaScript APIs apex.submit or apex.confirm does not work on Windows Phones, the page will not be submitted. This also means that buttons with an 'Action When Button Clicked' of 'Submit' and the 'Submit Page' dynamic action will also not work.
Solution: No workaround currently available.
- CREATE LIST VIEW WIZARD PREVIOUS BUTTON REDIRECTS TO TAB OPTIONS PAGE
When stepping through the Create List View Page wizard, if a user clicks the Previous button on the &Settings& step of the wizard, they are incorrectly redirected to the Tab Options step instead of the Source step of the wizard.
Solution: On the Tab Options page, click Next to proceed to the Source page.
- COUNTRIES MISSING FROM ANYCHART WORLD.AMAP FILE
The AnyChart World and World (without Greenland) maps are missing some map reference information for a number of countries, and the countries cannot be represented on the generated map. The missing countries include Serbia, Kosovo, Antarctica, and Palau.
Solution: No workaround currently available.
- APEX_LDAP.IS_MEMBER DOES NOT WORK WITH ANONYMOUS BIND
When using the APEX_LDAP.IS_MEMBER function with a null password, user can get &LDAP client/server error: Invalid credentials.&
Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.
- MAX WIDTH ATTRIBUTE OF TEXTAREAS SHOULD NOT BE EMITTED FOR PRE APEX 4.2 APPS
Textareas now emit the &Maximum Width& attribute which is respected by all modern browsers except for IE. This changed behavior can result in problems in existing applications if the attribute value isn't high enough, which wasn't a problem in previous APEX versions, because it wasn't checked. To avoid this issue existing applications have to be modified during upgrade, the &Max Width& attribute of text areas should only be emitted for applications where the &Compatibility Mode& attribute is set to &= 4.2
Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.
Workaround: Use Internet Explorer to edit textareas.
- CREATION OF DATA LOADING IN NON-ENGLISH RESULTS IN ORA-20001, ORA-02291
If running Application Express in a language other than English, and trying to add Data Loading wizard pages to your application, the wizard will fail with the following error:
ORA-02291: integrity constraint violated - parent key not found
Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.
- LDAP AUTHENTICATION: ERROR IF USE_EXACT_DN IS NULL
The &Use Exact Distinguised Name (DN)& attribute of LDAP authentication schemes sometimes contains NULL instead of &Yes&. This can cause the following error:
ORA-31202: DBMS_LDAP: LDAP client/server error: Bad search filter on authentication.
Solution: Open the authentication scheme and save it again.
- UNABLE TO COPY HTML5 CHART IN A MOBILE APP
When attempting to copy a page containing a HTML5 chart, users get the following error:
A page containing a Flash Chart can only be copied to a page with a Desktop user interface
Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.
- FETCH ROW DML PROCESS DOES NOT SET ITEMS WITH ROWID AS SOURCE
If a form page contains a database item that has ROWID as source, the fetch row process may leave the item empty. This does not affect fetches where the ROWID value gets passed via the URL, e.g. where the link from a report page passes the ROWID.
Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.
- COPY PAGE WIZARD LOSING REFERENCES TO TEMPLATES
When attempting to copy a page from another application, references to templates in the new page may be incorrectly set to an ID instead of a given template name.
Solution: Edit the new page, and update the region template using the Template select list item.
Note: A page containing a Flash Chart can only be copied to a page with a Desktop user interface.
- RESET_IMAGE_PREFIX.SQL REFERENCES APEX_040100 INSTEAD OF APEX_040200 SCHEMA
The reset_image_prefix.sql script in the utilities directory doesn't work because it references the schema APEX_040100 instead of APEX_040200.
Solution: Manaually modify the reset_image_prefix.sql script, within the installation files, and update the two occurences of APEX_040100 to APEX_040200.
- CUSTOM AUTHENTICATION CAN CAUSE WWV_FLOW_DATA_SESSION_FK CONSTRAINT VIOLATION
If an application uses a custom authentication scheme with a sentry function, users may encounter the following error when running from the Application Express development environment or when opening links that contain an old session id:
ORA-02291: integrity constraint (APEX_040200.WWV_FLOW_DATA_SESSION_FK) violated - parent key not found
Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.
- REST ERRORS REPORTED IN WWV_FLOW_UPGRADE_PROGRESS FOLLOWING UPGRADE TO 4.2
After an upgrade from Application Express 4.1 to 4.2, users get the following error reported in WWV_FLOW_UPGRADE_PROGRESS:
exception on copy &APEX_040100&.&WWV_FLOW_RT$TEMPLATE& ORA-00942: table or view does not exist
A similar error will be reported for the following tables: WWV_FLOW_RT$MODULE, WWV_FLOW_RT$HANDLER, WWV_FLOW_RT$PARAMETER, WWV_FLOW_OA$CLIENT, WWV_FLOW_OA$SCOPE, WWV_FLOW_OA$SCOPE_MODULE, and WWV_FLOW_OA$CLNT_SCOPE_GRNT.
Solution: These reported errors can be ignored and do not impact the upgrade.
- WORKSPACES EXPORTED IN 4.1.1 OR OLDER CAUSE ERROR WHEN IMPORTING ON 4.2
When importing a workspace from an earlier version of Application Express to 4.2, users get the following error:
ORA-02291: integrity constraint (APEX_040200.WWV_FLOW_DEV_FK) violated - parent key not found
ORA-06512: at &APEX_040200.WWV_FLOW_FND_USER_API&, line 926
Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.
- INSTANCE PASSWORDS FOR SMTP AND WALLET CAUSE ORA-28817 AFTER MIGRATION FROM 4.1
If Application Express has been migrated from 4.1 or 4.1.1, accessing instance parameters for the SMTP and wallet passwords raises ORA-28817. For example, Administrators may encounter this error when navigating to the Instance Settings page.
Solution: Before the upgrade, the current password values can be queried with:
select apex_instance_admin.get_parameter('SMTP_PASSWORD')
, apex_instance_admin.get_parameter('WALLET_PWD')
After the upgrade, these parameters should be reset via API calls if they had values in the older release:
&&apex_instance_admin.set_parameter('SMTP_PASSWORD','my smtp password');
&&apex_instance_admin.set_parameter('WALLET_PWD','my wallet password');
- CHECKBOXES AND RADIO GROUPS IN MOBILE APPLICATIONS HAVE NO LABEL
When checkbox or radio group page items are used in pages using the 'jQuery Mobile Smartphone' user interface type, they do not display their label.
Solution: Edit the page template &Page& for the jQuery Mobile Smartphone theme and add the following in the 'Cascading Style Sheet & Inline' attribute:
.ui-controlgroup-label {
&&visibility:
- MAKE DEVELOPER TOOLBAR AVAILABLE FOR MOBILE APPS
The Developer Toolbar is not included on jQuery Smartphone pages. After clicking the 'Run Application' from the Application Builder then the only way to get back to the Application Builder is to user the browser back button. You will need to go back once for each mobile page visited.
Solution: Right click on the 'Run Application' button and launch the application using 'Open Link in New Tab' or 'Open Link in New Window' or similar. The exact command varies by browser.
Note: For applications with both desktop and mobile user interfaces you can access the Session State for a mobile page by navigating to a desktop page and using the developer toolbar and then changing the page number.
- UNIQUE CONSTRAINT VIOLATED DURING SAMPLE DIALOG APP INSTALL ON HOSTED INSTANCE
When attempting to install the Sample Dialog or Sample Master Detail packaged application, users may get the following error:
Execution of the statement was unsuccessful. ORA-00001: unique constraint (APEX_040200.WWV_FLOW_MESSAGES_IDX1) violated
Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.
- BUTTONS THAT REDIRECT TO AN EXTERNAL URL FAIL IN MOBILE APPLICATIONS
Buttons on pages using a 'jQuery Mobile Smartphone' user interface type, that have an 'Action when button clicked' attribute of 'Redirect to URL', will fail when the URL links to a desktop page, or external web page.
Solution: Instead of defining only the URL In the &URL Target& attribute, the JavaScript function location.href function should be called directly for Desktop and external button targets, e.g. use &javascript:location.href='';& instead of just &&.
- CASCADING RADIO GROUP AND CHECK BOX ITEMS BROKEN IN JQUERY MOBILE UI
In an application that uses a jQuery Mobile user interface, Radio Group or Checkbox item types will not work if they have a Cascading LOV Parent Item defined. If this is defined, those items will not be displayed on the page at all.
Solution: No workaround currently available.
- COPY PAGE ITEM WIZARD, ERROR INCORRECTLY SHOWS WHEN 'SOURCE' ITEM CONTAINS CERTAIN CHARACTERS
When copying page items, the final page of the wizard titled 'New Item' has a 'Source' page item. If 'Source' contains any of the following reserved characters (&,& or &), an error will display: &Source contains &, & or & which are invalid characters.&
Solution: The item is still copied even though the error is raised.
- CANNOT LOAD & 32K SPREADSHEET DATA WITH COPY AND PASTE OPTION
The copy and paste of spreadsheet data when creating application from spreadsheet and within data workshop does not allow loading greater than 32KB of data.
Solution: Load files rather than using cut and paste.
- CREATE LIST VIEW/PLUGIN REGION WIZARD DOESN'T STORE ALL ENTERED ATTRIBUTE VALUES
If a new List View region is created with the Create Region Wizard, it will not store the entered values for the attributes &Link Target&, &Split Button Target&, &Search Type&, &Search Column&, &Search Box Placeholder& and &Nested List Column&. The same problem also occurs for region type plug-ins with more than 15 custom attributes.
Solution: Use the Create Page Wizard or set the attributes with Edit Region after creating the region.
- THEME 50 HAS INCORRECT &UI-LI-ASIDE& CSS CLASS DEFINITION
There is additional CSS being applied to the .ul-li-aside class that is causing the list sub text to render incorrectly.
Solution: Paste the following styles in the CSS Inline Styles field in the Edit Page screen where this behavior is observed:
.ui-li-aside {
&&width: 50%;
&&text-align:
&&padding: 0;
- THEME 50 HAS INCORRECT VIEWPORT META TAG ALLOWING FOR ZOOM ON MOBILE DEVICES
On iOS devices, users are able to zoom on jQuery Mobile pages. The viewport meta tag is set to
Solution: Edit the page template &Page& for the jQuery Mobile Smartphone theme and replace &&meta name=&viewport& content=&width=device-width, initial-scale=1&&& with &&meta name=&viewport& content=&width=device-width, initial-scale=1, maximum-scale=1.0, user-scalable=no&&&.
- PAGE SUBMIT ACTIONS DO NOT WORK FOR LONGER MOBILE SELECT LISTS, WHEN DEFINED TO FIRE WHEN THE SELECT LIST VALUE CHANGES
In an application that uses a jQuery Mobile user interface, some form elements use native items when running on actual smartphone or tablet devices. Select lists are rendered using a native control as long as the LOV includes up to 10 items. When there are more than 10 items, select lists are rendered as jQuery Mobile dialogs, making it easier to find and pick a value in long lists.
When using the &Page Action when Value Changed& attribute to make the page submit when the value is changed, will only work when the native control is rendered. Once the select list gets rendered as the dialog with more than 10 items, the page no longer gets submitted. The same is also true when a Dynamic Action that is defined to fire on 'Change' of one of these select lists, where the action is set to 'Submit Page'.
Solution: No workaround currently available.
- DATA LOADING TRANSFORMATION RULE FAILS IF COLUMN 1 IS SUBSTRING OF COLUMN 2
If the Data Loading definition has two (or more) columns, and one (or more) is a substring of the other column. For example, if first column is COL, and second column is EXTRACOL. In this case, a Data Transformation rule of type (PLSQL EXPRESSION/FUNCTION BODY and SQL QUERY) will fail if the definition refers only to the longer column name, in our example EXTRACOL. In such cases both columns are considered part of the definition causing an error.
Solution: No workaround currently available.
- APEX INTERACTIVE REPORT SUBSCRIPTIONS GET LOST AFTER AN IMPORT OF AN APPLICATION
When importing a new version of application, subscriptions created before the import are lost.
Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.
- THEME 25 JAVASCRIPT FILE HAS CONSOLE.LOG CAUSING ERRORS IN IE
Running Internet Explorer 8 and below prompts user with javascript errors relating to console.log statements in 4_2.js.
Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.
Alternative Workaround: If a 'Global Page' does not already exist, create one, and add an HTML region called 'Temporary JavaScript', with the following HTML Text Region Source:
&script type=&text/javascript&&
&&if (!console) { var console = {}; console.log = function(){} }
Note: Once the bug has been fixed, either by applying the Patch Set Exception, or updating to a future version of Application Express where bug # is fixed, this region can be removed.
- PAGE LEVEL PAGE AND DIALOG TRANSITION VALUES ARE NOT USED
The page level attributes &Page Transition& and &Dialog Transition& do not have any effect for a jQuery Mobile application, if that page isn't the first page loaded by the application. Only the theme level attributes work all the time.
Solution: No workaround currently available.
- QBE GIVES INCOMPLETE SQL USING FUNCTION ON ANY COLUMN NAME WITH SPACES
Query Builder cannot handle table or column names with space characters in them.
Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.
- ISSUES WITH EDITING ITEMS AFTER UPGRADE
After an upgrade users get one of the following errors when they try to edit or delete an item:
Error during rendering of page item P4311_PROTECTION_LEVEL. or
ORA-20001: Query must begin with SELECT or WITH
Solution: Restart Oracle Application Express Listener. For more information, see Oracle Application Express Listener Installation and Developer Guide:
Oracle Cloud
Customers and Events
Email Subscriptions
Communities
Services and Store
Contact and Chat
US Sales: +1.800.633.0738博客访问： 486999
博文数量： 144
博客积分： 8000
博客等级： 中将
技术积分： 1520
注册时间：
IT168企业级官微
微信号：IT168qiye
系统架构师大会
微信号：SACC2013
分类： Oracle
以下面两张表为例：
SQL> desc person名称&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 是否为空? 类型----------------------------------------- -------- ------------------------
PERSONID&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& NOT NULL NUMBER(9)PROFESSION&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& NUMBER(2)IDORPASSPORTNO&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& VARCHAR2(18)INSURANCE&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& VARCHAR2(32)FIRSTNAME&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& VARCHAR2(32)LASTNAME&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& VARCHAR2(32)CHINESENAME&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& VARCHAR2(64)SEX&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& CHAR(1)BIRTHDAY&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& DATEUSERTYPE&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& VARCHAR2(2)SEARCHCODE&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& CHAR(10)ORGID&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& NUMBER(9)ADDRESSID&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& NUMBER(9)
SQL> desc PERSONPROFESSION名称&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 是否为空? 类型----------------------------------------- -------- ------------------------
PROFESSIONID&&&&&&&&&&&&&&&&&&&&&&&&&&&&& NOT NULL NUMBER(2)NAME&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& VARCHAR2(32)ALIAS&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& VARCHAR2(32)INITCREDIT&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& NUMBER(3)MEMO&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& VARCHAR2(200)
假定PERSONPROFESSION为父表，PERSON为子表，建立如下约束条件：
SQL>ALTER TABLE PERSONPROFESSION ADD (CONSTRAINT PK_PERSONPROFESSION PRIMARY KEY (PROFESSIONID) USING INDEX TABLESPACE WACOS;
表已更改。
SQL>ALTER TABLE PERSON ADD (CONSTRAINT PK_PERSON PRIMARY KEY (PERSONID) USING INDEX TABLESPACE WACOS;
表已更改。
增加PERSON表的外键约束：
SQL>ALTER TABLE PERSON ADD (CONSTRAINT FK_PERSON1 FOREIGN KEY (PROFESSION) REFERENCES PERSONPROFESSION (PROFESSIONID) );
表已更改。
分别向两张表里插入一行数据：
SQL>insert into PERSONPROFESSION values('1','sdfd','df','342','dfs');
已创建 1 行。
提交完成。
SQL>insert into person values('10','1','dsf','d','d','df','df','0','','sd','s','11','11');
已创建 1 行。
SQL> select PERSONID,PROFESSION
PERSONID PROFESSION---------- ----------&&&&&&& 10&&&&&&&&& 1
SQL> select PROFESSIONID,name from PERSONPROFESSION;
PROFESSIONID NAME------------ --------------------------------&&&&&&&&&& 1 sdfd
SQL> delete from PERSONPROFESSION;delete from PERSONPROFESSION*ERROR 位于第 1 行:ORA-02292: 违反完整约束条件 (WACOS.FK_PERSON1) - 已找到子记录日志.
报错是因为父表里存在子表的记录，应先删除子表记录，再删除父表记录：
SQL> delete from PERSON;
已删除 1 行。
SQL> delete from PERSONPROFESSION;
已删除 1 行。
提交完成。
那么，如何实现两张表的级连删除呢？
重新建立PERSON的外键，加上ON DELETE CASCADE选项试一下：
SQL> alter table person drop CONSTRAINT FK_PERSON1;
表已更改。
SQL>ALTER TABLE PERSON ADD (CONSTRAINT FK_PERSON1 FOREIGN KEY (PROFESSION) REFERENCES PERSONPROFESSION (PROFESSIONID) ON DELETE CASCADE);
表已更改。
增加外键约束的时候加ON DELETE CASCADE选项目的是可以在子表记录存在的情况下直接删除父表记录，而不用受约束的限制：SQL> delete from PERSONPROFESSION;
已删除 1 行。
SQL> select PERSONID,PROFESSION
PERSONID PROFESSION---------- ----------&&&&&&& 10&&&&&&&&& 1
SQL> select * from PERSONPROFESSION;
以上可以看出父表记录删除了，子表记录还存在。
那么在delete语句的末尾加上CASCADE，就可以实现两张表的级删除：
SQL> delete from PERSONPROFESSION
已删除 1 行。
SQL> select *
SQL> select * from PERSONPROFESSION;
以下是ON DELETE的官方解释：
ON DELETEThe ON DELETE clause indicates that when a DELETE is executed on a referenced row in the referenced table, one of the following actions will be executed upon the constrained column, as specified by action:
NO ACTION(default)The NO ACTION clause produces an error if the reference is violated. This is the default if action is not specified.
CASCADEThe CASCADE keyword removes all rows which reference the deleted row. Exercise caution with this action.
SET NULLThe SET NULL clause assigns a NULL value to all referenced column values
阅读(17953) | 评论(0) | 转发(0) |
相关热门文章
给主人留下些什么吧！~~
请登录后评论。