Oracle® Application Express Patch Set Notes
Release 3.1.1.00.09
 

 

Oracle® Application Express

Patch Set Notes

Release 3.1.1.00.09

 

May 2008

These patch set notes accompany the Oracle Application Express 3.1.1.00.09 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.1.1.00.09 patch set can be applied to Oracle Application Express release 3.1.0.00.32. 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 release 2 (9.2.0.3) and higher supports this patch set.

2 Pre-Installation Tasks

Complete the following pre-installation tasks before installing the patch set:

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 local or remote 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 the p7032837_11106_GENERIC.zip patch 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:

    • Microsoft Windows - Double-click the p7032837_11106_GENERIC.zip file

    • UNIX or Linux - Enter the following command:

      $ unzip p7032837_11106_GENERIC.zip
      

2.3 Shut Down the Oracle Database

Shut down the existing Oracle Database instances with normal or immediate priority. On RAC systems, shut down all instances on each node.

If Automatic Storage Management (ASM) is running, shut down any database that uses ASM, and then shut down the ASM instance on each node of the cluster.


Note:

If you are using Oracle Cluster Ready Services (CRS) to restart all Oracle database processes, you must shut down all Oracle Database instances on all cluster nodes before applying the patch set to the CRS installation. After the CRS patch set installation is complete, you must shut down all Oracle Database and ASM instances running in the RAC Oracle home before applying the patch set to the RAC installation. If you shut down ASM instances, you must first shut down all database instances that use ASM.

2.4 Stop All Processes

Stop all listener and other processes running in the Oracle home directory where you want to install the patch set.


Note:

If you shut down ASM instances, you must first shut down all database instances that use ASM, even if the database runs from a different Oracle home.

2.4.2 For a CRS installation

If you are upgrading a CRS installation, shut down the following Oracle Database 11 g services before installing the patch set:


Note:

You must perform these steps in the order listed.

  1. Shut down any processes in the Oracle home on each node that might be accessing a database, for example Oracle Enterprise Manager Grid Control.

  2. Shut down all RAC instances on all nodes. To shut down a RAC instance, enter the following command where db_name is the name of the database:

    $  
                                              
    oracle_home/bin/srvctl stop database -d  
                                              
    db_name
                                            
  3. Shut down all ASM instances on all nodes. To shut down an ASM instance, enter the following command where node is the name of the node where the ASM instance is running:

    $  
                                              
    oracle_home/bin/srvctl stop asm -n  
                                              
    node
                                            
  4. Stop all node applications on all nodes. To stop node applications running on a node, enter the following command where node is the name of the node where the applications are running:

    $  
                                              
    oracle_home/bin/srvctl stop nodeapps -n  
                                              
    node
                                            
  5. Shut down the CRS process by entering the following command on all nodes as the root user:

    # /etc/init.d/init.crs stop
    

    Note:

    If the CRS installation is not on a shared Oracle home you can upgrade the CRS installation one node at a time. To do this, perform the preceding steps only on the first node that you are upgrading, and then follow the instructions on the installer screen.

2.4.3 For a RAC Installation

If you are upgrading a RAC installation and node applications are running in the RAC Oracle home, shut down the following Oracle Database 10 g services before installing the patch set:


Note:

You must perform these steps in the order listed.

  1. Shut down any processes in the Oracle home on each node that might be accessing a database, for example Oracle Enterprise Manager Grid Control.

  2. Shut down all RAC instances on all nodes. To shut down a RAC instance, enter the following command where db_name is the name of the database:

    $  
                                              
    oracle_home/bin/srvctl stop database -d  
                                              
    db_name
                                            
  3. Shut down all ASM instances on all nodes. To shut down an ASM instance, enter the following command where node is the name of the node where the ASM instance is running:

    $  
                                              
    oracle_home/bin/srvctl stop asm -n  
                                              
    node
                                            
  4. Stop all node applications on all nodes. To stop node applications running on a node, enter the following command where node is the name of the node where the applications are running:

    $  
                                              
    oracle_home/bin/srvctl stop nodeapps -n  
                                              
    node
                                            

2.5 Back Up the System

Oracle recommends that you create a backup of the Oracle Database installation before you install the patch set. After the patch set is installed, there is no way to remove it.

2.6 Start the Oracle Database

After backing up the system, you must start the Oracle instance that contains Oracle Application Express. Do not start other processes such as the listener or Oracle HTTP Server.


Note:

If you are connecting to a remote database, then start the listener.

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 the p7032837_11106_GENERIC.zip file.

  2. Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS specifying the SYSDBA role. For example:. For example:

    • On Windows:

                                                 
      SYSTEM_DRIVE:\ sqlplus /nolog
      SQL> CONNECT SYS as SYSDBA
      Enter password:  
                                                
      SYS_password
                                              
    • On UNIX and Linux:

      $ sqlplus /nolog
      SQL> CONNECT SYS as SYSDBA
      Enter password:  
                                                
      SYS_password
                                              
  3. Run apxpatch.sql. For example:

    @apxpatch.sql
    

4 Post-Installation Tasks

Complete the following post-installation tasks before using the upgraded software:

4.1 Update the Images Directory

During an upgrade, you must overwrite your existing images directory. 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/:

  • Oracle9 i HTTP Server Release 2—see the httpd.conf file.

  • Oracle Application Server 10g—see the marvel.conf file.

  • Oracle HTTP Server 11 g—see the marvel.conf file.

When you locate the images directory path, copy it to the existing ORACLE_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 Script apxldimg.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 the p7032837_11106_GENERIC.zip file.

  2. Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS specifying the SYSDBA role. For example:

    • On Windows:

      SYSTEM_DRIVE:\ sqlplus /nolog
      SQL> CONNECT SYS as SYSDBA
      Enter password:  
                                                    
      SYS_password
                                                  
    • On UNIX and Linux:

      $ sqlplus /nolog
      SQL> CONNECT SYS as SYSDBA
      Enter password:  
                                                    
      SYS_password
                                                  
  3. Run apxldimg.sql passing the file system path to the "patch" directory where the p7032837_11106_GENERIC.zip file was unzipped as shown in the following example:

    • On Windows:

      @apxldimg.sql  
                                                    
      SYSTEM_DRIVE:\TEMP
                                                  
    • On UNIX and Linux:

      @apxldimg.sql /tmp
      

4.2 Start Processes

Start processes such as the listener and Oracle HTTP Server that were stopped as part of the pre-installation tasks.

4.3 Patching Oracle Application Express After f Languages

You can safely apply the Oracle Application Express 3.1.1.00.09 patch set repeatedly to an Application Express 3.1 instance. If you load additional translated versions of Oracle Application Express after applying this patch, you should apply the entire patch script 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 3.1.1.00.09 Patch Set

Bug Number Description

6360779

ORA-29262 Bad URL When Using Drag And Drop With Non-ASCII characters

6864252

Interactive report CSV download produces SSP checksum error

6871863

Interactive Report Theme 20 - Highlight cell does not show background color

6871948

JavaScript error being raised on calender attributes page

6872389

HTTP-404 and broken images when accessing uploaded files

6875685

Interactive Report - Import fails with computations

6875729

Import of multiple report queries produces inconsistent or no data in output

6883366

Substitution strings are not always replaced in interactive reports

6883403

Unique constraint error when creating highlight in interactive report

6883430

Interactive report queries fail when column aliases are Oracle reserved words

6886638

BLOB support in reports, problem when including multiple BLOBS

6887033

Error messages are suppressed in some cases while using an OnDemand process

6890516

Interactive Report - Creating <= Filter via Link results in >=

6890781

Using Go button on interactive report does not reset pagination

6895046

End user change password page is broken in translated applications

6902508

Reordering Region Items - Change of COLSPAN causes JavaScript error to display

6902574

ORA-06502 Character string buffer too small for translated messages

6903538

Interactive report drop down fails when values contain trailing backslash ( \)

6903974

APEX_ITEM.DATE_POPUP returns all values to row 1

6905263

Object Browser - Create 'Package With Methods On Tables' Not Creating Package

6912467

Cannot set chart type using interactive reports in Safari

6916399

Checkboxes in some cases have the same DOM ID

6919421

PDF Report is corrupted when application name has a special character

6929895

Border problem with new Theme 20 - Modern Blue

6930135

Charts in interactive reports fail when username is changed

6941194

JavaScript error In Internet Explorer on some popup LOV types

6952089

APEX_APPLICATION_TEMP_REPORT view missing primary key

6953214

Translatable text report does not respect language selection

6953420

Interactive report filter on CLOB column raises JavaScript error

6953499

Report format not respect for columns of data type BINARY_DOUBLE

6956070

ORA-06502 When creating report region with SQL Query larger than 1700 characters

6956469

Interactive Report - Changing tab with filter create dialog open causes error

6963877

RESET_IMAGE_PREFIX SCRIPT not clearing cache for cached page regions

6964243

APEX_MAIL.SEND with CLOB type body fails

6965231

Page Icons not displayed in applications generated via migration projects

6968973

Developer Activity Log (Audit Trail) truncated to Past 31 days

6968988

No Page ID in URL causes deep link and other info to get lost

6968995

Duplicate page submission show link feature no longer works

6970008

Interactive report compute feature raises error for queries using #OWNER#

6970151

Create SQL Report with search region does not reset pagination on reset

6973197

Interactive report charts do not load for some combinations of values and format masks

6976538

Fieldset as containers of popup LOVs items does not render correctly

6979561

Download filename not preserved when converting interactive reports

6980200

HTTP-404 ORA-06502 - When PL/SQL dynamic content greater than 4000 characters

6987070

Hidden and protected item checksum error when item contains special characters

6988690

Unique constraint error thrown during creation of migration project

6998669

Link columns not included in report exports (CSV and Print)

7001615

Interactive report help not translated for custom translations

7010171

Application export files inconsistent even when no changes made to application

7013435

MRU process in Create Application Wizard-generated master detail not working correctly

7021151

Runtime WHERE clause in row fetch process with CLOB causes SQL syntax error

7031752

Lossy conversion error reported by CSSCAN on package body WWV_MIG_ACC_LOAD


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:

6.1 Secure Session Cookies

Most Oracle Application Express applications that require some form of user authentication use the "login API", specifically procedures in the PL/SQL package WWV_FLOW_CUSTOM_AUTH_STD. These procedures employ a session cookie as a key component of the authentication and session management framework. The Oracle Application Express engine sends this cookie to the user's browser immediately after authentication and then checks for the existence of this cookie and checks its validity as it handles each page request throughout the life of the session. Any application that calls the package WWV_FLOW_CUSTOM_AUTH_STD to perform login or logout actions falls into this category.

Prior to Oracle Application Express release 3.1.1, these session cookies would be sent using the OWA_COOKIE.SEND procedure using the default value ( NULL) for the secure parameter. This would enable these cookies to be sent back and forth regardless of the protocol (http or https) in use.

In Oracle Application Express 3.1.1, the use of the "secure" parameter can be demanded by the application developer. This causes a non-null value for "secure" to be passed to OWA_COOKIE.SEND resulting in cookies being transmitted only when the current request protocol is https.

To use this feature, developers must pass p_use_secure_cookie => true to the key procedures in the Oracle Application Express login API (that is, the WWV_FLOW_CUSTOM_AUTH_STD PACKAGE). This includes procedures login, post_login, and logout. Most applications will already have calls to these procedures in the login process on the login page of an application (to the login procedure), in the authentication scheme's logout URL attribute (to the logout procedure), and in variously situated calls to the post_login procedure in custom implementations.

This new feature enables developers to enhance the security of their applications.

6.2 About FSP_DML_LOCK_ROW

In Oracle Application Express 3.0, a SELECT FOR UPDATE is issued on a row when performing an UPDATE or DELETE using APEX Automatic DML. In Oracle Application Express 3.0.1 and all later versions, the value of a substitution string or item item named FSP_DML_LOCK_ROW will be examined. If the value is anything other than FALSE, the default behavior of SELECT FOR UPDATE will be performed when issuing an UPDATE or DELETE operation through Automatic DML. If the value of FSP_DML_LOCK_ROW is exactly FALSE, then no SELECT FOR UPDATE will be issued.

7 Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. 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 at

http://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.

TTY Access to Oracle Support Services

Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, seven days a week. For TTY support, call 800.446.2398.


Oracle Database Application Express Patch Set Notes, Release 3.1.1.00.09

Copyright © 2008, Oracle. All rights reserved.

The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.

The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.

If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.

Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.