Oracle® Database Application Express Patch Set Notes
Release 3.0.1.00.08
 

 

Oracle® Database Application Express

Patch Set Notes

Release 3.0.1.00.08

 

June 2007

These patch set notes accompany the Oracle Application Express 3.0.1.00.08 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.0.1.00.08 patch set can be applied to Oracle Application Express release 3.0.0.00.20 and 3.0.1.00.07. 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 p6113844_10203_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 p6113844_10203_GENERIC.zip file

    • UNIX or Linux - Enter the following command:

      $ unzip p6113844_10203_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 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
    
                                            
  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 p6113844_10203_GENERIC.zip file.

  2. Connect as SYS to the database where Oracle Application Express is installed and run apxpatch.sql. Consider the following example:

    sqlplus "sys/syspass as sysdba" @apxpatch.sql
    

4 Post-Installation Tasks

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

4.1 Update the Images Directory

Copy the patch/images directory into the images directory used for Application Express.

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 HTTP Server 11 g—see the marvel.conf file.

  • Oracle Application Server 10g—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.

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 Loading Languages

You can safely apply the Oracle Application Express 3.0.1.00.08 patch set repeatedly to an Application Express 3.0 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.0.1.00.08 Patch Set

Bug Number Description

5395708

When a Form on SQL Query is created on a page for a second time an ORA-20001 Error displays

5955327

In Pop-Up LOVs for certain themes, the Next button does not work

5959729

Added link functionality to HTML Editor item type

5965308

Report queries always display as PDF, regardless of the selected output type

5973745

PDF rendering fails when a report is generated with a decimal separator of comma

5979567

Error during LDAP authentication when using a built-in login page

5979712

Switching a theme can cause an invalid number error

5982678

ORA-06550 encountered when approving workspaces in Request mode

5986209

When creating Flash charts, labels move in Pie Charts

5988337

Legend in flash chart not correctly displayed when using the Omit Label Interval attribute

6013380

PDF of a report region with item session state of % results in a blank PDF

6025216

Manual Web references not properly imported in page processes

6025383

Region caching attributes not included in export or import of some region types

See Also: "About Exporting Applications and Pages that Use Region Caching"

6026605

ORA-02014 can occur with automatic data manipulation language (DML) against certain database views

6032689

Manage Users from drop-down menu links to an invalid page

6052104

Manually edited translations do not show all translatable attributes

6054073

Slow response when adding rows to a tabular form

6058672

Targetnamespace attribute incorrectly picked up from WSDL when creating web reference

6067589

Session time zone set to DBTIMEZONE when it should be system time zone


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.2 About Exporting Applications and Pages that Use Region Caching

As described in "Fixed Bugs", this patch set corrects the behavior described in Bug 6025383 - Region caching attributes not included in export or import of some region types.

Applications exported from Oracle Application Express release 3.0.1 may be imported into Oracle Application Express release 3.0 if the application does not use region caching. Region caching enables various types of page regions to be cached during application execution.

Because of a PL/SQL API revision in release 3.0.1, Application Express applications exported from release 3.0.1 cannot be imported into release 3.0 if the application uses the region caching feature.

When working with applications developed in and exported from Application Express release 3.0, note the following issues:

  • Applications imported back into release 3.0 or into a later version may be functionally incomplete with respect to region caching attributes.

  • Applications that utilize region caching in release 3.0 may lack region caching attributes for all types of SQL query regions and calendar regions, making them functionally incorrect.

  • These applications may also lack attributes for all region types that specify caching conditions on cached regions.

Oracle recommends that all installations of Oracle Application Express release 3.0 be patched to release 3.0.1.

6.4 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, the value of a substitution string or 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.0.1.00.08

Copyright © 2007, 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.