These patch set notes accompany the Oracle Application Express 3.2.1.00.10 patch set.
This document contains these topics:
1 Patch Set Overview
Patch sets are a mechanism for delivering fully tested and integrated product fixes. Patch sets provide bug fixes only; they do not include new functionality and they do not require certification on the target system.
Patch sets include all of the libraries that have been rebuilt to implement the bug fixes in the set. All of the fixes in the patch set have been tested and are certified to work with each other.
Patch sets contain the same set of generic fixes across all platforms. Patch sets may also include additional patches specific to the platform on which they are released.
The Oracle Application Express 3.2.1.00.10 patch set can be applied to Oracle Application Express release 3.2.0.00.27. Apply the patch to the Oracle database where Oracle Application Express schemas are installed. This patch will determine if additional languages are installed, and will apply the patch for those languages as well. Oracle9i Database Release 2 (9.2.0.3) and higher supports this patch set.
When determining whether or not to install this patch set, consider the following rules:
1. If you have Oracle Application Express release 3.2 installed, download the Oracle Application Express 3.2.1 patch set and apply it.
2. If you have Oracle Application Express release 3.1.2 or earlier installed (including Oracle HTML DB release 1.5), download and install the entire Oracle Application Express 3.2.1 release from the Oracle Technology Network (OTN).
3. If you do not have Oracle Application Express installed, download and install the entire Oracle Application Express 3.2.1 release from the Oracle Technology Network (OTN).
2 Pre-Installation Tasks
Complete the following pre-installation tasks before installing the patch set:
Identify the Oracle Application Express Installation
Download and Extract the Installation Software
Optionally Backup the Oracle Database
Prevent Access to Oracle Application Express
2.1 Identify the Oracle Application Express Installation
This is not a complete software distribution. You must connect to an existing Oracle Database where the Oracle Application Express schemas are installed and run the apxpatch.sql installation script.
2.2 Download and Extract the Installation Software
Download the patch set to a computer with access to the Oracle Database. You will also need access to the Oracle home.
To download and extract the patch set installation software:
1. Download thep8548651_11106_GENERIC.zippatch set installation archive to a directory that is not the Oracle home directory or under the Oracle home directory.
2. Unzip and extract the installation files as follows:
o Microsoft Windows - Double-click thep8548651_11106_GENERIC.zipfile
o UNIX or Linux - Enter the following command:
o $ unzip p8548651_11106_GENERIC.zip
2.3 Optionally Backup the Oracle Database
The Application Express engine is a collection of tables and packages that reside wholly within the Oracle Database user accountsAPEX_030200 and FLOWS_FILES. This patch set updates the underlying tables and packages within theAPEX_030200 account. If your installation fails, you will not be able to rollback the patch set installation process. Therefore, Oracle recommends that you perform a complete backup of your Oracle instance before you install the patch set. Note that after the patch set is installed there is no way to remove it.
If you choose to perform a backup, restart the Oracle Database in restricted session mode to prevent any user access (that is, developer and end-user) while applying the patch set.
2.4 Prevent Access to Oracle Application Express
It is important that no developers or end users access Oracle Application Express while you are applying the patch set.
If your configuration includes Oracle HTTP Server andmod_plsql, you need to stop Oracle HTTP Server. See "Stop Oracle HTTP Server".
Alternatively, if your configuration includes the embedded PL/SQL gateway, you need to disable the Oracle XML DB HTTP Server. See"Disable Oracle XML DB HTTP Server".
2.4.1 Stop Oracle HTTP Server
To stop Oracle HTTP Server shipped with Oracle Database 10g release 1 (10.1) or later, enter commands using the following syntax, whereORACLE_BASE is the path to the Oracle base directory:
ORACLE_BASE\ORACLE_HTTPSERVER_HOME\opmn\bin\opmnctl stopproc ias-component=HTTP_Server
Note that if the Oracle HTTP Server is listening on a port less than 1024, then these commands must be executed as a privileged user (such asroot).
2.4.2 Disable Oracle XML DB HTTP Server
The embedded PL/SQL gateway runs in the Oracle XML DB HTTP server in the Oracle database. To disable it, you change the port number to 0. Before doing so, verify the port number. See "Verifying the Oracle XML DB HTTP Server Port".
To disable Oracle XML DB HTTP server:
1. Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS. For example:
o Windows:
o DRIVE_LETTER:\> sqlplus /nolog
o SQL> SQL> CONNECT SYS as SYSDBA
o Enter password: SYS_password
o UNIX and Linux:
o $ sqlplus /nolog
o SQL> SQL> CONNECT SYS as SYSDBA
o Enter password: SYS_password
2. Run the following statements:
3. EXEC DBMS_XDB.SETHTTPPORT(0);
4. COMMIT;
2.4.2.1 Verifying the Oracle XML DB HTTP Server Port
To verify the port number where the Oracle XML DB HTTP Server is running:
1. Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS specifying theSYSDBA role:
o On Windows:
o SYSTEM_DRIVE:\ sqlplus /nolog
o SQL> CONNECT SYS as SYSDBA
o Enter password: SYS_password
o On UNIX and Linux:
o $ sqlplus /nolog
o SQL> CONNECT SYS as SYSDBA
o Enter password: SYS_password
2. Enter the following statement to verify the port number:
3. SELECT DBMS_XDB.GETHTTPPORT FROM DUAL;
If the port number returns 0, the Oracle XML DB HTTP Server is disabled.
3 Installation Tasks
Complete the following tasks to install the patch set:
1. Set your current directory to the top-level "patch" directory where you unzipped thep7313609_11106_GENERIC.zipfile.
2. Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS specifying theSYSDBA role. For example:
o On Windows:
o SYSTEM_DRIVE:\ sqlplus /nolog
o SQL> CONNECT SYS as SYSDBA
o Enter password: SYS_password
o On UNIX and Linux:
o $ sqlplus /nolog
o SQL> CONNECT SYS as SYSDBA
o Enter password: SYS_password
3. Run apxpatch.sql. For example:
4. @apxpatch.sql
5. Review the log file apxpatch.log for any errors.
4 Post-Installation Tasks
Complete the following post-installation tasks before using the upgraded software:
Start Oracle Application Express
About Patching Oracle Application Express After Translating Languages
4.1 Update the Images Directory
During an upgrade, you must incorporate the new imagesdirectory. Copy the patch/images directory into the images directory used for Application Express.
4.1.1 Updating the Images Directory When Running Oracle HTTP Server
To locate the images directory on the file system, review the following files for the text alias /i/:
Oracle HTTP Server distributed Oracle9i Release 2—see thehttpd.conf file.
Oracle Application Server 10g—see the marvel.confor dads.conf files.
Oracle HTTP Server distributed with Oracle Database 11g—see themarvel.conf or dads.conf files.
When you locate the images directory path, copy it to the existingORACLE_HTTPSERVER_HOME home.
On a Windows system, run a command from a command prompt similar to the following example:
xcopy /E /I patch\images ORACLE_HTTPSERVER_HOME\Apache\Apache\images On UNIX or Linux based systems, run a command similar to the following example:
cp -rf patch/images ORACLE_HTTPSERVER_HOME/Apache/Apache In the preceding syntax examples,ORACLE_HTTPSERVER_HOME is the existing Oracle Application Server or Oracle HTTP Server Oracle home. The location of the Oracle Application Express images directory may be different in your configuration.
4.1.2 Updating the Images Directory When Running the Embedded PL/SQL Gateway
The images in an Oracle XML DB HTTP Server with the embedded PL/SQL gateway installation are in the XML DB repository. Updating the images is accomplished by running the SQL Scriptapxldimg.sql located in the top level directory where the patch was unzipped.
To update the images directory:
1. Set your current directory to the top-level "patch" directory where you unzipped thep7313609_11106_GENERIC.zipfile.
2. Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS specifying theSYSDBA role. For example:
o On Windows:
o SYSTEM_DRIVE:\ sqlplus /nolog
o SQL> CONNECT SYS as SYSDBA
o Enter password: SYS_password
o On UNIX and Linux:
o $ sqlplus /nolog
o SQL> CONNECT SYS as SYSDBA
o Enter password: SYS_password
3. Run apxldimg.sql passing the file system path to the "patch" directory where thep7313609_11106_GENERIC.zipfile was unzipped as shown in the following example:
o On Windows:
o @apxldimg.sql SYSTEM_DRIVE:\TEMP\patch
o On UNIX and Linux:
o @apxldimg.sql /tmp/patch
4.2 Start Oracle Application Express
If your configuration includes Oracle HTTP Server andmod_plsql, you need to start Oracle HTTP Server. See"About Patching Oracle Application Express After Translating Languages".
Alternatively, if your configuration includes the embedded PL/SQL gateway, you need to enable the Oracle XML DB HTTP Server. See"Enable Oracle XML DB HTTP Server".
4.2.1 Start Oracle HTTP Server
To start Oracle HTTP Server shipped with Oracle Database 10g release 1 (10.1) or later, enter commands using the following syntax, whereORACLE_BASE is the path to the Oracle base directory:
ORACLE_BASE\ORACLE_HTTPSERVER_HOME\opmn\bin\opmnctl startproc ias-component=HTTP_Server
Note that if the Oracle HTTP Server is listening on a port less than 1024, then these commands must be executed as a privileged user (such asroot).
4.2.2 Enable Oracle XML DB HTTP Server
Once disabled, you enable embedded PL/SQL gateway by assigning a port number.
To enable Oracle XML DB HTTP server:
1. Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS. For example:
o Windows:
o DRIVE_LETTER:\> sqlplus /nolog
o SQL> SQL> CONNECT SYS as SYSDBA
o Enter password: SYS_password
o UNIX and Linux:
o $ sqlplus /nolog
o SQL> SQL> CONNECT SYS as SYSDBA
o Enter password: SYS_password
2. Run the following statements:
3. EXEC DBMS_XDB.SETHTTPPORT(port);
4. COMMIT;
For example:
EXEC DBMS_XDB.SETHTTPPORT(8080);COMMIT; 4.3 About Patching Oracle Application Express After Translating Languages
It is safe to apply the Oracle Application Express 3.2.1.00.10 patch set repeatedly to an Application Express 3.2.1 instance. If you load additional translated versions of Oracle Application Express after applying this patch, you should apply the entire patch set again.
5 Fixed Bugs
The following table is a list of the bugs fixed with in this patch set.
Table 1 Bugs Fixed in the Oracle Application Express Patch Set
| Bug Number | Description |
| 5914368 | In Firefox, Find functionality in HTML Editor Standard is broken. |
| 5914374 | In Firefox, text inside a table in HTML Editor Standard is always striked. |
| 8320124 | Updates ignored when editing all regions. |
| 8320185 | Error displays when applying changes to include an Oracle Report in application migrations. |
| 8330936 | Oracle Reports with a SQL query greater than 4k cannot be converted in Forms conversion. |
| 8331010 | Oracle Report SQL queries greater than 4k are not displayed in Forms conversion project. |
| 8331201 | Export/import actions cause loss of interactive report print attributes. |
| 8334711 | Transactional SQL in SQL Commands results in a |
| 8338787 | Enhanced query not saved correctly when Apply Changes is clicked in application migrations. |
| 8338990 | Application import is slow and sometimes times out. |
| 8347332 | Unable to use greater than character ( |
| 8351256 | Upgrading runtime-only environment results in |
| 8355079 |
|
| 8358834 | Cannot create application from a Migration project with mixed case table names. |
| 8370221 | Create package with methods on database tables fails. |
| 8371342 | When using page groups, manage unassigned links goes to wrong page. |
| 8416002 | Slow performance when creating application on spreadsheet. |
| 8417143 |
|
| 8422688 |
|
| 8431814 | Unable to import SQL script using SQL Workshop, SQL Scripts, Import utility. |
| 8432829 | Poor performance when running Lists of Values Utilization report. |
| 8460439 | Interactive report from copied page takes bind variable value from original page. |
| 8466467 | Deep link lost after sso authentication. |
| 8466721 | Oracle Application Express schema needs |
| 8466935 | Allow developed applications to call |
| 8486277 | Unable to edit non-database blocks listed in application migrations. |
| 8494970 |
|
| 8512898 | Build Options display incorrectly in some Oracle Application Express views. |
| 8527710 | Tabs overlap in 2-level Tab template in Chrome/Safari for Theme 17. |
| 8530955 | Degraded performance using interactive reports over time. |
| 8534848 | Interactive report charts raise |
| 8551429 |
|
| 8553100 | Original query generated for Forms conversion uses incorrect column names. |
| 8555172 |
|
| 8567600 |
|
| 8567757 |
|
| 8568894 | JavaScript error using Interactive reports when selecting a column in Search bar. |
| 8571758 | Unable to upload Oracle Report XML to Forms conversion project on Oracle Database, release 9.2. |
| 8573453 | Create workspace fails - |
6 Other Issues and Changes
This section describes other changes included in Oracle Application Express that are not documented elsewhere.
This section contains the following topics:
AnyChart AnyGantt Flash Gantt and AnyChart AnyMap
6.1 Issue Applying the Oracle Application Express 3.2.1 Patch Set Against Oracle Database Release 11.1.0.7
When applying the Oracle Application Express 3.2.1 patch set against an Oracle Database release 11.1.0.7, you may encounter the error ORA-00600: internal error code, arguments: [kgiinb_invalid_obj]. This will be recorded in the generated patch set installation log,apxpatch.log.
If you encounter this error, you download and apply the patch for database bug 7420394 from Oracle MetaLink, and then attempt to install the Oracle Application Express 3.2.1 patch set again.
6.2 AnyChart AnyGantt Flash Gantt and AnyChart AnyMap
This release of Oracle Application Express includes the AnyChart AnyGantt Flash Gantt Component and the AnyChart AnyMap extension. These products are not exposed through the Oracle Application Express user interface, but can be used programatically in any Oracle Application Express application. To learn more, see:
AnyChart AnyGantt Flash Gantt Component:
http://www.anychart.com/products/anygantt/overview/ AnyChart AnyMap extension:
http://www.anychart.com/products/anymap/overview/ For specifics about the XML structures necessary to use these products, see:
AnyChart AnyGantt Flash Gantt Component:
http://anychart.com/products/anygantt/docs/
AnyChart AnyMap extension:
http://anychart.com/products/anymap/docs/
Please note that to use these products, you must manually enter the necessary XML code into the Custom XML property of the chart.
7 Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site athttp://www.oracle.com/accessibility/.
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
Deaf/Hard of Hearing Access to Oracle Support Services
To reach Oracle Support Services, use a telecommunications relay service (TRS) to call Oracle Support at 1.800.223.1711. An Oracle Support Services engineer will handle technical issues and provide customer support according to the Oracle service request process. Information about TRS is available athttp://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of phone numbers is available athttp://www.fcc.gov/cgb/dro/trsphonebk.html.
Oracle Application Express Patch Set Notes, Release 3.2.1.00.10
Copyright © 2009, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this software or related documentation is delivered to the
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to
This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
