Oracle® Application Server and Oracle Developer Suite: Patch Set Notes 10g Release 2 (10.1.2) Patch Set 3 (10.1.2.3.0)

Oracle Application Server and Oracle Developer Suite
Patch Set Notes

10g Release 2 (10.1.2) Patch Set 3 (10.1.2.3.0)
March 2008
This document contains the following sections:
Section 1, "Introduction"
Section 2, "Patch Set Overview"
Section 3, "Patch Set Documentation"
Section 4, "Patch Set Requirements"
Section 5, "Before You Apply This Patch Set"
Section 6, "Patch Application for Oracle Collaboration Suite Environments"
Section 7, "Patch Set Application"
Section 8, "Postapplication Considerations"
Section 9, "Known Issues"
Section 10, "Fixed Platform-Specific Bugs for SPARC"
Section 11, "Fixed Platform-Specific Bugs for Windows"
Section 12, "Fixed Platform-Specific Bugs for AIX 5L Based Systems (64-Bit)"
Section 13, "Fixed Platform-Specific Bugs for Linux x86"
Section 14, "Patch Set Components"
Section 15, "Documentation Accessibility"
1 Introduction
This document accompanies Oracle Application Server and Oracle Developer Suite
10g Release 2 (10.1.2) Patch Set 3 (10.1.2.3.0) (OracleAS 10g Release 2 Patch Set 3). This
patch set is applicable for the following releases only:
Oracle Application Server 10g Release 2 (10.1.2.0.0)
Oracle Application Server 10g Release 2 Standard Edition One (10.1.2.0.1)
Oracle Application Server Forms and Reports Services (10.1.2.0.2)
Oracle Application Server Portal 10g Release 2 (10.1.4)
Oracle Application Server Portal 10g Release 2 Patch Set 2 (10.1.4.1)
Oracle Developer Suite 10g (10.1.2.0.2)
Oracle Business Intelligence 10g Release 2 (10.1.2)
Oracle Business Intelligence 10g Release 2 (10.1.2.0.2)
Oracle Business Intelligence Tools 10g Release 2 (10.1.2)
Oracle Business Intelligence Tools 10g Release 2 (10.1.2.0.2)
Oracle Business Intelligence Tools 10g (10.1.2.0.2) that shipped as part of Oracle
Developer Suite 10g Release 2 (10.1.2)
OracleAS 10g Release 2 Patch Set 1 (10.1.2.1.0)
OracleAS 10g Release 2 Patch Set 2 (10.1.2.2.0)

This patch set is not applicable to Oracle Application Server
Containers for J2EE standalone installations.
Note:
The names of the operating systems have been shortened for this document, as
follows:
Operating System
Abbreviated Name
Solaris Operating System (SPARC)
SPARC
Microsoft Windows
Windows
AIX 5L Based Systems (64-Bit)
AIX
2 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. Patch sets
contain generic fixes that apply to all platforms and may also include platform-specific
fixes.
Patch sets include all files 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 one
another. Because this patch set includes only low impact fixes, you are not required to
certify applications or tools against the server (unless specifically instructed by your
software vendor).
This patch set is cumulative and includes all of the fixes from OracleAS 10g Release 2
Patch Set 1 (10.1.2.1.0) and Patch Set 2 (10.1.2.2.0). It can be applied to any instance
listed in Section 1, "Introduction" as well as any of those instances that have applied
OracleAS 10g Release 2 Patch Set 1 (10.1.2.1.0) or Patch Set 2 (10.1.2.2.0).
This patch set is not a complete software distribution. You must install this patch set
over one of the releases listed in Section 1, "Introduction".
If this patch set is applied against an OracleAS Portal 10.1.4
repository, then the repository will be upgraded to 10.1.4.2. In
addition, repository should first be upgraded to Oracle Database 10g
by the application of the Oracle Database 10g Release 1 (10.1.0.5) patch
set.
Note:
The OracleAS 10g Release 2 Patch Set 3 updates the software on all applicable Oracle
Application Server installations. If you have a Portal and Wireless installation, then
you must also use this patch set to update your OracleAS Metadata Repository.
Refer to the installation guide and release notes for the base requirements for your
Oracle product, and confirm that all required patches have been installed on your
system.
To download free installation documentation, release notes, white papers, or other
collateral, go to Oracle Technology Network (OTN). You must register online before
using OTN; registration is free and can be done at
http://www.oracle.com/technology/membership
If you already have a user name and password for OTN, then you can go directly to
the documentation section of the OTN Web site at
http://www.oracle.com/technology/documentation
This patch set includes two updates: the Metadata Repository Update, and the
Software Update. In addition, you may need to apply a database patch. The following
sections provide additional information about the OracleAS 10g Release 2 Patch Set 3:
Section 2.1, "Metadata Repository Update"
Section 2.2, "Software Update"
Section 2.3, "Database Patch Set"
For a list of components included in this patch set, see the Section 14, "Patch Set
Components".
2.1 Metadata Repository Update

The Metadata Repository Update updates the software schemas in the Metadata
Repository that are used by all of your Oracle Application Server middle tier
installations. It also updates the binaries for Oracle Application Server Backup and
Recovery Tool and the Oracle Application Server Guard used in Metadata Repository
only installations.
You can apply the Metadata Repository Update patch to a middle tier Oracle home or
to an infrastructure Oracle home containing both Oracle Identity Management and
OracleAS Metadata Repository. Use the same Oracle home for future Metadata
Repository patch updates. The Metadata Repository Update only needs to be applied
once per Metadata Repository.
Back up the relevant database before applying the Metadata Repository Update.
During application of the Metadata Repository Update, the installer validates the
ORACLE_HOME/config/ias.properties file to verify that the Oracle home you
have designated on the installation screen is either a middle tier using Oracle Identity
Management Services, or an Oracle Identity Management installation with an
OracleAS Metadata Repository.
You must apply the Software Update to each of your middle-tier installations before
you apply the Metadata Repository Update to the Metadata Repository used by each
of the middle tiers. You must also apply the Software Update to the Metadata
Repository installation prior to applying the Metadata Repository Update to the
Metadata Repository.
2.2 Software Update

Application of the OracleAS 10g Release 2 Patch Set 3 Software Update (Software
Update) updates the software and configuration files contained in your Oracle
Application Server middle-tier and infrastructure Oracle home directories. Oracle
home is the full path of the Oracle directory that contains the Oracle Application
Server installation. ORACLE_HOME will be used in this documentation to refer to the
directory where the product is installed.
ORACLE_HOME should be replaced with the full path
name of the installed Oracle Application Server instance.
Note:
The installer used for the Software Update automatically determines which set of
software patches is appropriate for your installation.
The order of application of the Software Update to your middle tier and infrastructure
installation does not matter. However, the following should be noted:
You must apply the Software Update to each of your existing middle-tier
installations before you apply the OracleAS 10g Release 2 Patch Set 3 Metadata
Repository Update to the Metadata Repository used by each of the existing
middle-tiers. You must also apply the Software Update to the Metadata Repository
installation prior to applying the Metadata Repository Update to the Metadata
Repository.
If you will be adding additional middle-tier installations to the updated Metadata
Repository at a later time, you must apply the Software Update to the middle-tiers
that will be using the Metadata Repository.
Back up the relevant Metadata Repository before applying the Software Update.
For example, a distributed Oracle Application Server environment may be set up as

follows:
Computer 1 contains Oracle Identity Management Services including Oracle

Internet Directory, Oracle Directory Integration and Provisioning, Oracle
Delegated Administration Services, Oracle Application Server Single Sign-On
(OracleAS Single Sign-On), Oracle Application Server Certificate Authority
(OracleAS Certificate Authority).
Computer 2 contains the OracleAS Metadata Repository.
Computer 3 contains a Portal and Wireless instance.
Computer 4 contains a J2EE and Web Cache instance.
Computers 3 and 4, respectively, share the same Oracle Application Server

Infrastructure which exists collectively on Computers 1 and 2.
All of the computers in the environment require application of the Software
Update.
For this type of environment, the updates could be installed as follows:

1.
Apply the Oracle Database 10g Release 10.1.0.5 Patch Set on computer 2, if needed.
Computer 1 will get the patch during the software update.
2.
Apply the Software Update to the middle tier installations on computers 3 and 4.
3.
Apply the Software Update to computers 1 and 2.
4.
Apply the Metadata Repository Update to Computer 2 using the middle tier
installation on computer 3. Do not use the middle tier from computer 4. Using a
J2EE and Web Cache middle tier will result in the following message:
The Metadata Repository Update cannot be run from the selected ORACLE_HOME.
The Update must be run from either an Identity Management with Metadata
Repository installation ...
2.3 Database Patch Set

Oracle Database 10g Release 1 (10.1.0.5) is the minimum database release required by
OracleAS 10g Release 2 Patch Set 3. The Oracle Database 10g Release 1 (10.1.0.5) patch
set is available from OracleMetaLink at
https://metalink.oracle.com
To determine if you need to apply the database patch set, review the following:
If you applied OracleAS 10g Release 2 Patch Set 2, then you do not need to
re-apply the database patch.
The Oracle Database 10g Release 1 (10.1.0.5) patch set must be applied to all
databases containing a Metadata Repository before OracleAS 10g Release 2 Patch
Set 3 is applied.
If you have previously installed Oracle Application Server 10g Release 2 (10.1.2)
with Oracle Database release 9.2.0.6, you must first upgrade to Oracle Database
release 9.2.0.8.
If your database release is 9.2.0.8 or 10.2, then the Oracle Database 10g Release 1
(10.1.0.5) database patch is not required. The Metadata Repository Update for
upgrading the Metadata Repository should be run from the middle tier.
3 Patch Set Documentation

The documents below are related to this release of the Oracle Application Server patch
set:
Oracle Application Server and Oracle Developer Suite Patch Set Notes 10g Release 2
(10.1.2) Patch Set 3 (10.1.2.3.0) (this document). It provides the following
information:
All system requirements and instructions needed to install or deinstall the

patch set itself.
A list of known issues related to operating the OracleAS 10g Release 2 Patch
Set 3.
The SPARC document is contained in the file /OracleAppServer10g_

10.1.2.3_Solaris_Patchset/doc/readme.html in the patch set
distribution.
The Windows document is contained in the file \OracleAppServer10g_
10.1.2.3_Windows_Patchset\doc\readme.html in the patch set
distribution.
The Linux x86 document is contained in the file /OracleAppServer10g_
10.1.2.3_Linux_Patchset/doc/readme.html in the patch set distribution.
The AIX document is contained in the file /OracleAppServer10g_10.1.2.3_
AIX_Patchset/doc/readme.html in the patch set distribution.
The HP-UX PA-RISC document is contained in the file /OracleAppServer10g_

10.1.2.3_HP_Patchset/doc/readme.html in the patch set distribution.
The HP-UX Itanium document is contained in the file /OracleAppServer10g_
10.1.2.3_HP_Itanium_Patchset/doc/readme.html in the patch set
distribution.
Oracle Application Server and Oracle Developer Suite List of Bugs Fixed 10g Release 2
(10.1.2) Patch Set 3 (10.1.2.3.0). It provides a list of all generic (common to all
operating systems) bugs related to Oracle Application Server that have been fixed
in this release sorted by product group.
The SPARC document is contained in the file /OracleAppServer10g_
10.1.2.3_Solaris_Patchset/doc/bugsfixed.html in the patch set
distribution.
This Windows document is contained in the file \OracleAppServer10g_
10.1.2.3_Windows_Patchset\doc\bugsfixed.html in the patch set
distribution.
The Linux x86 document is contained in the file /OracleAppServer10g_
10.1.2.3_Linux_Patchset/doc/bugsfixed.html in the patch set
distribution.
The AIX document is contained in the file /OracleAppServer10g_10.1.2.3_
AIX_Patchset/doc/bugsfixed.html in the patch set distribution.
The HP-UX PA-RISC document is contained in the file /OracleAppServer10g_
10.1.2.3_HP_Patchset/doc/bugsfixed.html in the patch set distribution.
The HP-UX Itanium document is contained in the file /OracleAppServer10g_
10.1.2.3_HP_Itanium_Patchset/doc/bugsfixed.html in the patch set
distribution.
These documents are also available on OracleMetaLink at

In addition, the following OracleMetaLink notes have information related to this patch
set:
OracleMetaLink Note 555681.1 Oracle Application Server Patch Set Notes Addendum
10g Release 2 (10.1.2) Patch Set 3 (10.1.2.3.0)
OracleMetaLink Note 329361.1 Oracle Application Server 10g Release 2 (10.1.2)
Support Status and Alerts
OracleMetaLink Note 404838.1 How to Configure OID Referential Integrity in 10gAS
10.1.2.2
OracleMetaLink Note 339042.1 Performing Backup and Recovery Operations From
Application Server Control Console (10.1.2.1+)
To locate these documents, do the following:

1.
Log in to OracleMetaLink.
2.
Click Advanced at the top of the OracleMetaLink page.
3.
Enter the note number in the Document ID field, and click Submit.
See Also: Oracle Application Server installation guides and release

notes are available at Oracle Technology Network at
http://www.oracle.com/technology/index.html
4 Patch Set Requirements

Refer to your installation guide and release notes for the base requirements for your
system.
If your system does not meet one of the minimum
requirements listed in this section, then log a service request to
request assistance with this patch set.
Note:
4.1 Required Software

The following is a list of the required system software that must be installed before
installing this patch set:
One of the baseline releases identified in Section 1, "Introduction".

To check the release number of your Oracle Application Server instance, go to the
Home page of the Oracle Application Server Control Console and click About
Oracle Enterprise Manager 10g Application Server.
One of the following supported operating systems:

Oracle Application
Supported Operating System
Oracle Application Server 10g

Release 2 (10.1.2.0.0)
One of the following operating systems:
Microsoft Windows 2000 with Service Pack 3 or later
Microsoft Windows Server 2003 (32-bit)
Solaris Operating System 8 (5.8), 9 (5.9) or 10 (5.10)

supported by Oracle Application Server
Microsoft Windows XP SP2 is supported only for

these two types:
J2EE and Web Cache middle tier without

Oracle Application Server Infrastructure
OracleAS Developer Kits
Red Hat Enterprise Linux AS/ES 2.1
SUSE Linux Enterprise Server 8
AIX 5L Version 5.2
AIX 5L Version 5.3
HP-UX 11i (11.11 or 11.23) PA-RISC or later
HP-UX 11i Version 2 (11.23) Itanium or later
Oracle Application

Release 2 (10.1.2.0.1) Standard
Edition One
Microsoft Windows XP is supported only for the

following type:
J2EE and Web Services middle tier without

You can install other Oracle Application Server

installation types on Windows XP, but they are not
supported on Windows XP.

Release 2 (10.1.2.0.2)
OracleAS Portal 10.1.4
Solaris Operating System 8 (5.8), 9 (5.9), or 10 (5.10)

Microsoft Windows 2000 with Service Pack 3 or
higher.
Microsoft Windows Server 2003 (32-bit) with Service
Pack 1.
Microsoft Windows XP is supported only for the
following type:
J2EE and Web Cache middle tier without

J2EE and Web Cache middle tier running

on Windows XP, using services from an
running on a different (non-XP) platform.
You can install other Oracle Application Server

installation types on Windows XP, but they are not
supported on Windows XP. The installer will
display a warning but you will be able to continue
with the installation.
If you are running Windows XP with Service Pack 2,
please see OracleMetaLink Note: 280874.1 at
Release 2 Patch Set 1 (10.1.2.1.0)
For a list of supported operating systems, please refer to

the OracleAS 10g Release 2 Patch Set 1 (10.1.2.1.0)
readme.

Release 2 Patch Set 2 (10.1.2.2.0)
For a list of supported operating systems, please refer to

the OracleAS 10g Release 2 Patch Set 2 (10.1.2.2.0)
readme.
Oracle Application
Oracle Developer Suite 10g

(10.1.2.0.2)
Solaris Operating System 8 (5.8), or 9 52.9).

For more information about installing on Solaris 10,
please refer to "Section 3.1.2, Additional Steps for
Installation on the Solaris 10 Operating System" in
Oracle Application Server Release Notes 10g Release 2
(10.1.2) for Solaris Operating System (SPARC).
Microsoft Windows 2000 with SP3 or higher.

Microsoft Windows XP Professional Edition with
SP2 or higher.
Oracle Developer Suite 10g (10.1.2.0.2) is also certified on

Microsoft Windows Server 2003 (32-bit).
Oracle Business Intelligence 10g
Release 2 (10.1.2)

Microsoft Windows (32-bit)
AIX 5L Version 5.2
AIX 5L Version 5.3
HP-UX 11i (11.11 or 11.23) PA-RISC or later
HP-UX 11i Version 2 (11.23) Itanium or later
OracleBI Discoverer middle tier is also certified on

Pack 1.
Oracle Business Intelligence 10g
Release 2 (10.1.2.0.2)

Microsoft Windows (32-bit)
OracleBI Discoverer middle tier is also certified on

Pack 1.
Oracle Application
Oracle Business Intelligence Tools

10g Release 2 (10.1.2)
Microsoft Windows XP Professional Edition Service

Pack 1 or later

10g Release 2 (10.1.2.0.2) that
shipped as part of Oracle
Developer Suite 10g Release 2
(10.1.2)

10g Release 2 (10.1.2.0.2)
Notes:

Pack 1 or later

Pack 1 or later
The following notes are for SPARC only:
If you are installing this patch set on release 10.1.2.0.0 on a Solaris

10 (5.10) system, then you must download and apply patch
4510761 prior to installing OracleAS 10g Release 2 Patch Set 3. If
the 4510761 patch is not installed, then the pre-requisite operating system
check will fail. Refer to OracleMetaLink Note 330016.1 for more
information. The patch and note are available from OracleMetaLink at
The middle tier products can be run on Solaris 32-bit or 64-bit

systems. The infrastructure can only be run on 64-bit systems.
4.2 Preinstallation Requirements

The following list is the preinstallation requirements for this patch set:
Ensure the system configuration meets the recommended system configuration

described in your documentation.
Back up your Oracle software and inventory before applying this patch set, or
before making any other changes to your existing Oracle software. Refer to your
administrators guide for instructions on backing up your Oracle software and
inventory.
Back up the relevant database before applying the Software Update to an Oracle
Identity Management installation. Refer to your administrators guide for
instructions on backing up your database.
10
Backup up the OracleAS Metadata Repository before applying the Metadata

Repository Update.
5 Before You Apply This Patch Set

Read this section before applying this patch set to determine whether any of the
following topics apply to your Oracle system. Follow the instructions in the topic
before proceeding with installation of this patch set.
This section includes the following notes:
Section 5.1, "Stop all Oracle Developer Suite Processes and Programs"
Section 5.2, "OracleAS Infrastructure Must be Running During Software Update"
Section 5.3, "Setting and Unsetting Environment Variables"
Section 5.4, "Configure Oracle Application Server Web Cache for Checking Invalid
Requests"
Section 5.5, "Configure Virtual Server Names and Ports for the Load Balancer in a
High Availability Environment"
Section 5.6, "Applying the Oracle Database 10g Release 1 (10.1.0.5) Patch Set"
Section 5.7, "Installing the Patch Set to a Distributed Configuration Management
Cluster"
Section 5.8, "Software Update to a File-based Repository"
Section 5.9, "OracleAS Wireless Developer Kit does not Work with XHTML MP
Devices"
Section 5.10, "Stopping an Edge Job for OracleAS Wireless"
Section 5.11, "Stopping Sensor Edge Server"
Section 5.12, "Installation Requirements for Oracle Application Server Cluster

(Identity Management) Configuration"
Section 5.13, "Preinstallation and Postinstallation Requirements for Oracle
Application Server Cold Failover Cluster (Infrastructure) Update for Windows"
Section 5.14, "Upgrading an Earlier Release of Oracle Application Server"
Section 5.15, "Enable Components Prior to Patch Application"
Section 5.16, "Copying the Files to a Windows Directory"
Section 5.17, "Preparing for an Oracle Internet Directory Multimaster Replication

Update"
Section 5.18, "Oracle Directory Integration and Provisioning and Oracle Internet
Directory"
5.1 Stop all Oracle Developer Suite Processes and Programs

If you are running Oracle Developer Suite, you must stop all processes and programs
that are running from your Oracle Developer Suite instance before applying this
software patch.
11
5.2 OracleAS Infrastructure Must be Running During Software Update

When you apply the Software Update to an Oracle Application Server middle-tier or
an OracleAS Infrastructure Oracle home, the following must be up and running of the
infrastructure instance:
OracleAS Metadata Repository listener
Database containing OracleAS Metadata Repository
Oracle Internet Directory
5.3 Setting and Unsetting Environment Variables

The operating system user who will be installing this patch set should read Section 4.9,
"Environment Variables," in the Oracle Application Server Installation Guide before
performing the patch installation.
The section contains important information about the environment variables that need
to be set or unset prior to performing the installation.
5.4 Configure Oracle Application Server Web Cache for Checking Invalid
Requests
The current setting for frequency of checking invalid requests is in units of a tenth of a
second. After applying OracleAS 10g Release 2 Patch Set 3, the setting will be
microseconds. The new granularity allows more flexibility in setting the yield
frequency (invalidation chunk). Customers who do not change the setting will have
frequency setting for the old units (tenths of seconds) interpreted as the new units
(microseconds), which will cause performance issues. Do the following procedure to
update the frequency units:
1.
Open the internal.xml file using a text editor.
2.
Locate the section for the TICKSPERCHUNK attribute. If the attribute is not in the
file, then exit the text editor. No change is needed for the file.
3.
Multiple the value of the attribute by 100000 to convert it to microseconds. For

example, if the current value is 3, then make the new value 300000 to preserve the
same invalidation chunk size.
4.
Save the file, and exit the text editor.
5.5 Configure Virtual Server Names and Ports for the Load Balancer in a
High Availability Environment
If you have a configuration where the LDAP port numbers on the LDAP load balancer
(for example, 389 for non-SSL and 636 for SSL) map to but are different from the
physical LDAP port numbers on the Oracle Internet Directory node (for example, 1030
for non-SSL and 1040 for SSL), then you must change the physical LDAP ports on the
Oracle Internet Directory nodes to match the LDAP ports configured on the LDAP
load balancer before you install OracleAS 10g Release 2 Patch Set 3.
To do this:
1.
Change the values of orclnonsslport and orclsslport in the following

entry:
"cn=configset0,cn=osdldapd,cn=subconfigsubentry"
12
Set the orclnonsslport value to match the NONSSL LDAP port value on the
load balancer and the orclsslport value to match the SSL LDAP port value on
the load balancer.
2.
Shutdown and restart the Oracle Internet Directory instance.
3.
Install OracleAS 10g Release 2 Patch Set 3.

This procedure is required for all components other than
Oracle Internet Directory. However, if Oracle Internet Directory is
located on the same machine with SSO/DAS, then this procedure is
also required prior to the Oracle Internet Directory patch installation.
Note:
For more information, refer to Section 12.2.3, "Configure Virtual Server Names and
Ports for the Load Balancer" in the Oracle Application Server Installation Guide.
5.6 Applying the Oracle Database 10g Release 1 (10.1.0.5) Patch Set
The Oracle Database 10g Release 1 (10.1.0.5) patch set must be applied to all database
instances (for both the Identity Management and Metadata Repository installation
type and Metadata Repository only installation type) before applying OracleAS 10g
Release 2 Patch Set 3. If OracleAS 10g Patch Set 2 (10.1.2.2.0) has been applied
previously, then you do not have to apply the database patch.
If you are using the SPARC operating system, then you must also apply the one-off
patch 5255249 as described in Section 7.1.4, "Apply Patch 5255249 (SPARC Only)"
before you apply OracleAS 10g Release 2 Patch Set 3.
For more information about supported databases with OracleAS 10g Release 2 Patch
Set 3, see Section 2.3, "Database Patch Set".
If the Metadata Repository was updated to Oracle Application
Server 10g Release 2 (10.1.2.2.0), then it is not necessary to apply the
database patch again.
Note:
After applying the Oracle Database 10g Release 1 (10.1.0.5) patch, do the following
procedure:
1.
Start the database listener.
2.
Start the database.
3.
Use the following command to start the Application Server Control Console:
emctl start iasconsole
4.
Use the following command to start the Oracle Application Server processes:
opmnctl startall
13
5.7 Installing the Patch Set to a Distributed Configuration Management

Cluster
If you are installing this patch set to an instance belonging to a Distributed
Configuration Management (DCM) cluster which contains multiple instances, then it
is necessary to remove the instance from the cluster before applying the patch. Use the
following command to remove the instance:
dcmctl leavecluster
This will avoid possible configuration inconsistencies between multiple instances in

the cluster.
When applying the patch set to a file-based repository cluster, the first repository
instance must be patched before the instances attached to the repository instance. Use
the following command to determine the DCM repository:
dcmctl whichfarm
After applying the patch set to all individual standalone instances, you can restore the
cluster topology by running the following command from the instances:
dcmctl joincluster -cl cluster
In the preceding command, cluster is the name of the cluster.
5.8 Software Update to a File-based Repository

If you are applying the Software Update to an Oracle Application Server cluster which
uses a file-based repository, then you can apply the update to any cluster node in any
order. You can apply the update in this manner as long as the repository node is not
being updated at the same time as any of the cluster nodes.
5.9 OracleAS Wireless Developer Kit does not Work with XHTML MP
Devices
The OracleAS Wireless Developer Kit (WDK) does not work with XHTML MP devices.
To workaround this problem, complete the following steps:
1.
Back up the following directory prior to installing the OracleAS 10g Release 2
Patch Set 3:
UNIX:
ORACLE_HOME/j2ee/OC4J_Wireless/applications/wdk/wdk-web/repository
Windows:
ORACLE_HOME\j2ee\OC4J_Wireless\applications\wdk\wdk-web\repository
2.
Install the OracleAS 10g Release 2 Patch Set 3.

This will redeploy the WDK application.
3.
Shut down the OC4J_Wireless process.
4.
Replace the content of the following directory with the content from the previous
installation which was backed up in step 1.
UNIX:
14
ORACLE_HOME/j2ee/OC4J_Wireless/applications/wdk/wdk-web/repository
Windows:
ORACLE_HOME\j2ee\OC4J_Wireless\applications\wdk\wdk-web\repository
5.
Start the OC4J_Wireless process.
5.10 Stopping an Edge Job for OracleAS Wireless

If you are applying the Software Update to an OracleAS Wireless environment, then
the edge job must be stopped before applying the update. You will need to remove the
lock and clean the database. For information about the processes, refer to the OracleAS
Wireless chapter in the Oracle Application Server Release Notes.
5.11 Stopping Sensor Edge Server

If you are applying the Software Update to Oracle Application Server 10g Release 2
(10.1.2.0.0), then you should stop the edge task before applying the patch set. Use the
following command to stop the edge task:
exec edge.edg_utl.deschedule_job;
After applying the patch set, start the service to start receiving data, as follows:
1.
Log in to the database as follows:

Infra_Oracle_Home/bin/sqlplus /nolog
2.
Connect as sysdba using the following command:

sql> connect sys/password@sid as sysdba
3.
Start the edge task using the following command:

exec edge.edg_utl.schedule_job;
4.
Confirm the service has started using the following command:

select component_name, status from edge.edg_jobs;
The following message should be returned:

COMPONENT_NAME:EdgeDispatchJob
STATUS:Started
5.12 Installation Requirements for Oracle Application Server Cluster

(Identity Management) Configuration
The following steps describe how to patch your Oracle Application Server Cluster
(Identity Management) configuration.
1.
Modify the load balancer settings so that the load balancer VIP points to the first
Oracle Internet Directory instance.
2.
Apply the Software Update to the OracleAS Cluster (Identity Management)

instances as described in Section 7.2, "Applying OracleAS 10g Release 2 Patch Set 3
on OracleAS Cluster (Identity Management) Environments".
3.
Restore the load balancer settings after applying the patch to the instances.
15
4.
Ensure the load balancer port numbers, both internal and external, are the same
for the Oracle Internet Directory connection for SSL and non-SSL connections.
5.13 Preinstallation and Postinstallation Requirements for Oracle

Application Server Cold Failover Cluster (Infrastructure) Update for
Windows
The following steps describe how to update your OracleAS Cold Failover Cluster
(Infrastructure) from 10.1.2.0.0, 10.1.2.0.2, 10.1.2.1.0, or 10.1.2.2.0 to 10.1.2.3.0. For a
cluster with Microsoft Cluster Service (MSCS) and Oracle Fail Safe, this is a
prerequisite to prevent the failover during update of the OracleAS Infrastructure or the
You only need to update the infrastructure once from the active host for both
infrastructure Software Update and Metadata Repository Update.
Note: You must perform the steps detailed in Section 5.13.1, "Before
Application of the Software Update" before applying of the Software
Update to your OracleAS Infrastructure.
You must perform the steps detailed in Section 5.13.2, "After

Application of the Software Update" after applying of the Software
Update to your OracleAS Infrastructure.
5.13.1 Before Application of the Software Update

Perform the following steps before applying the Software Update:
1.
Verify that your password file and your database parameter, remote_login_
passwordfile, are set to EXCLUSIVE mode.
If you need to create a password file, then enter the following command:
C:> ORACLE_HOME\bin\orapwd file=fname password=password
In the preceding command, fname is the name of password file. For example,
I:\oracle\database\PWDSID_Name.ORA.
To check the database parameter value:
a.
Enter the following SQL command:

sqlplus "sys/password@SID as sysdba"
b.
Enter the following command at the SQL*Plus prompt:

SQL> show parameters
c.
Look for the value of the remote_login_passwordfile parameter.

If the value is set to NONE, then update the init.ora file parameter to
remote_login_passwordfile=EXCLUSIVE.
The init.ora file is located on your installation hard drive. For example,
I:\oracle\admin\database name\pfile\init.ora where ORACLE_
HOME is I:\oracle.
d.
Comment out SQLNET.AUTHENTICATION_SERVICES=(NTS) in the

sqlnet.ora file. The sqlnet.ora file is located on your installation hard drive.
16
For example, I:\oracle\network\admin where ORACLE_HOME is

I:\oracle.
The line should look as follows, when you are finished:
# SQLNET.AUTHENTICATION_SERVICES = (NTS)
e.
2.
3.
Restart the database.
On the Cluster Administrator Interface, select Cluster Group from Groups.

a.
Set the Oracle Services for MSCS to offline.
b.
Bring up the Oracle Services for MSCS properties, and on the Advanced tab
select Do not restart.
On the Oracle Fail Safe Interface, do the following:

a.
b.
Set the following Oracle Application Server entries to offline:
SID Name
OracleORACLE_HOMEProcessManager
OracleORACLE_HOMETNSListener-FslVirtual Address Name
OracleORACLE_HOMEASControl
Delete the following Oracle Application Server entries from the group:
SID Name
OracleORACLE_HOMEProcessManager
OracleORACLE_HOMEASControl
You will be prompted if Windows Services should be deleted from both nodes.
Select No.
4.
Restart the Cluster Service as follows:

a.
Open Microsoft Service Panel from the Administrative Tools on the Control
Panel.
b.
Restart Cluster Service from the Microsoft Service Panel.
c.
Go to the other host and perform a cluster group failover from Cluster
Administrator interface to bring back the shared drive on the original primary
host.
The orancrypt9.dll file will be accessible.

If the preceding steps are not performed, then you will receive
the following error message after you enter the OracleAS Metadata
Repository password:
Note:
Certain files which need to be reinstalled by OUI are being used by

one or more applications.
You will not be able to proceed with the process.

5.
Start the listener, database, OPMN processes, and Oracle Internet Directory
processes. Use the following command to start the database:
startup pfile=pfile_location
17
In the preceding command, pfile_location is the location of the pfile. Ensure the
database is up and running using a DOS prompt.
6.
Start the Software Update to update your OracleAS Infrastructure in order to

update your Infrastructure software and Metadata Repository. Refer to
Section 7.1.5, "Apply the OracleAS 10g Release 2 Patch Set 3 Software Update" and
Section 7.1.6, "Apply the Metadata Repository Update" for more information.
During the Software Update, if the Oracle Internet Directory Patch Configuration
Assistant fails, then stop and start the listener.
5.13.2 After Application of the Software Update

Perform the following steps after you have updated your CFC OracleAS
Infrastructure:
1.
Update the password file, as follows:

a.
Delete the password file from the location where you created it in Step 1 of
Section 5.13.1, "Before Application of the Software Update".
b.
Set the remote_login_passwordfile=NONE parameter in the init.ora

file.
For example, I:\oracle\admin\database name\pfile\init.ora
where ORACLE_HOME is I:\oracle.
c.
Uncomment out SQLNET.AUTHENTICATION_SERVICES=(NTS) in the

sqlnet.ora file. The sqlnet.ora file is located on your installation hard drive
in ORACLE_HOME\network\admin where ORACLE_HOME is the installation
directory. For example, I:\oracle\network\admin where ORACLE_HOME
is I:\oracle.
The line should look as follows, when you are finished:
SQLNET.AUTHENTICATION_SERVICES = (NTS)
2.
Restart the database.
3.
On the Cluster Administrator Interface, select Cluster Group from Groups.

a.
Set the Oracle Services for MSCS to online.
b.
Bring up the Oracle Services for MSCS properties, and on the Advanced tab
select Restart.
4.
On the Oracle Fail Safe Manager Interface, add all services as resources to the
Oracle Application Server group.
5.
Make OracleAS Metadata Repository available by adding it as a resource to the

group.
6.
Add the shared disk as a dependency for the listener using Oracle Fail Safe.
7.
Add OPMN as a resource to the group that you created in Oracle Fail Safe.
8.
Add Application Server Control as a resource to the group that you created in
Oracle Fail Safe.
9.
Check that the correct listener is active.
18
5.14 Upgrading an Earlier Release of Oracle Application Server

If you have an earlier release of Oracle Application Server, then the following should
be noted:
When upgrading from an Oracle9i Application Server (Oracle9iAS) 9.0.2.x or

9.0.3.x, or Oracle Application Server 10g (9.0.4.x) middle tier to an Oracle
Application Server 10g Release 2 (10.1.2) middle tier, you can patch the Oracle
Application Server middle tier with OracleAS 10g Patch Set 3 (10.1.2.3.0) prior to
running the Oracle Application Server Upgrade Assistant. Refer to the Oracle
Application Server Upgrade and Compatibility Guide for more information on the
upgrade process.
When upgrading an Oracle9i Application Server (Oracle9iAS) 9.0.3.x instance to
Oracle Application Server 10g Release 2 (10.1.2) patched instance, the OracleAS
Web Cache plug-in may fail. The workaround is to use Oracle9i Application Server
(Oracle9iAS) 9.0.2 webcache.dtd to replace the Oracle9i Application Server
(Oracle9iAS) 9.0.3 webcache.dtd. The dtd file is located in the ORACLE_
HOME/webcache/dtds directory (for both 9.0.2 and 9.0.3).
5.15 Enable Components Prior to Patch Application

When applying OracleAS 10g Release 2 Patch Set 3 on an Oracle home with a disabled
OC4J instance, the installer will display the following message:
Install has detected that the OC4J home instance is disabled in the
ORACLE_HOME where the patchset is being installed.
The OC4J home instance must be enabled first before the patchset installation
can proceed.
Please enable the OC4J home instance through Enterprise Manager and try
installing again.
Click OK and then manually enable the instance using Oracle Enterprise Manager 10g
as follows:
1.
Go to the Oracle Enterprise Manager 10g home page.
2.
Click Enable/Disable Components.
3.
Select the disabled component in the Disabled Components listing.
4.
Click Remove. The component will move to the Enabled Components listing.
5.
Click OK.
Once the instance has been enabled, click Next to continue the installation. After
successfully patching the instance, you can disable it.
When applying the patch using the silent installation method,
the installation will fail if the instance is disabled. The log file will
indicate that the installation failed due to the disabled instance. The
message will appear in English only.
Note:
To avoid this, enable the instance prior to applying the patch.
19
5.16 Copying the Files to a Windows Directory

If you want to copy the patch files to a Windows directory before installing the patch
set, then do not include any spaces in the directory name. For example, the directory
can be named C:\patchset, but not C:\patch set.
5.17 Preparing for an Oracle Internet Directory Multimaster Replication

Update
Before you begin patching Oracle Internet Directory 10.1.2.x.x in a replicated
environment, you must perform the following steps. The first step should be done for
all nodes in the replication group. The rest of the steps are for all replica nodes other
than Master Definition Site (MDS) Replica or Primary supplier replica.
1.
Delete the ORASSO.WWSEC_PERSON$ table from master and replica nodes as

follows:
On the master node run the following commands:

sqlplus repadmin/password
BEGIN
DBMS_REPCAT.DROP_MASTER_REPOBJECT
(
sname =>'ORASSO',
oname => 'WWSEC_PERSON$',
type => 'TABLE',
drop_objects => false
);
END;
/
On each node in the replication group, run the following command:

sqlplus "/ as sysdba"
delete from orasso.wwsec_person$ where user_name not like '%PUBLIC';
commit;
The preceding commands will need to be run anytime you

rectify a node.
Note:
For more information, refer to Oracle Application Server High

Availability Guide 10g Release 2 (10.1.2.0.2) available on Oracle
Technology Network at
http://www.oracle.com/technology
2.
Locate the database registration entry of the database replica to be updated using
the following command:
For UNIX:
ORACLE_HOME/bin/ldapsearch -h host -p port -D cn=orcladmin
-w superuser_password -b "cn=oraclecontext" -s one
"(objectclass=orcldbserver)" dn
For Windows:
20
ORACLE_HOME\bin\ldapsearch -h host -p port -D cn=orcladmin

-w superuser_password -b "cn=oraclecontext" -s one
"(objectclass=orcldbserver)" dn
This will return a list of Distinguished Names (DNs) corresponding to all the
databases registered in Oracle Internet Directory in the following form:
cn=database_name,cn=oraclecontext
3.
Locate the DN of the following entry, which will be used in Step 5 of this
procedure:
cn=dbname_of_replica_to_be_updated,cn=oraclecontext
4.
Identify the appropriate replica ID to be updated using the following command:
For UNIX:
ORACLE_HOME/bin/ldapsearch
-h hostname_of_replica_being_updated -p port -D cn=orcladmin
-w superuser_password -b "" -s base "(objectclass=*)" orclreplicaid
For Windows:
ORACLE_HOME\bin\ldapsearch
-h hostname_of_replica_being_upgraded -p port -D cn=orcladmin
-w superuser_password -b "" -s base "(objectclass=*)" orclreplicaid
5.
Modify the seealso attribute of Replica Subentry for the replica to be updated as
follows:
a.
Create a file, for example mod.ldif, with the following contents:

#File Name : mod.ldif
dn: orclreplicaid=replicaid_from_step_4,cn=replication configuration
changetype: modify
replace: seeAlso
#The DN used in seealso attribute is obtained in Step #1.
seealso: cn=dbname_of_replica_being_updated,cn=oraclecontext
b.
Modify the replica subentry using ldapmodify command, as follows:
For UNIX:
ORACLE_HOME/bin/ldapmodify
-h hostname_of_replica_being_updated -p port -D superuser_DN
-w superuser_password -v -f mod.ldif
For Windows:
ORACLE_HOME\bin\ldapmodify
-h hostname_of_replica_being_upgraded -p port -D superuser_DN
-w superuser_password -v -f mod.ldif
5.18 Oracle Directory Integration and Provisioning and Oracle Internet

Directory
If Oracle Directory Integration and Provisioning and Oracle Internet Directory are on
separate machines in an Oracle Application Server 10g Release 2 (10.1.2.0.0)
21
environment, then the initial ORACLE_HOME/network/admin/tnsnames.ora file

on the Oracle Directory Integration and Provisioning machine is incorrect.
The connection information in the tnsnames.ora file contains the host name of the
Oracle Directory Integration and Provisioning installation instead of the host name of
the actual machine that has Oracle Internet Directory and the database. The host name
should be changed to the host name where the database resides.
For example, if the Oracle Directory Integration and Provisioning server is located on
machine ntmachine1.example.com, and the Oracle Internet Directory and
database are located on machine unixmachine2.example.com, then the
tnsnames.ora file on ntmachine1.example.com will contain the following:
oradb = (DESCRIPTION=(ADDRESS_
LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=ntmachine1.example.com)(PORT=1521)))
(CONNECT_DATA=(SERVICE_NAME=oradb.us.example.com)))
This entry should be changed so the host name indicates the host with the database,
such as:
oradb = (DESCRIPTION=(ADDRESS
_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=unixmachine2.example.
com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=oradb.us.example.com)))
You can change the entry either by manually editing the file, or by using the network
configuration tool.
6 Patch Application for Oracle Collaboration Suite Environments

Oracle Collaboration Suite customers should review the current Oracle Collaboration
Suite Release Notes before applying any Oracle Application Server patches. The
documentation is available at
http://www.oracle.com/pls/cs101/homepage
7 Patch Set Application

This section contains the following topics:
Section 7.1, "Applying OracleAS 10g Release 2 Patch Set 3"

Section 7.2, "Applying OracleAS 10g Release 2 Patch Set 3 on OracleAS Cluster
(Identity Management) Environments"
Section 7.3, "Applying OracleAS 10g Release 2 Patch Set 3 on Distributed OracleAS
Cluster (Identity Management) Environments"
Section 7.4, "Applying OracleAS 10g Release 2 Patch Set 3 to OracleAS Portal
10.1.4 to Upgrade to OracleAS Portal 10.1.4.2"
Section 7.5, "Applying OracleAS 10g Release 2 Patch Set 3 to Oracle Developer
Suite"
Section 7.6, "Applying OracleAS 10g Release 2 Patch Set 3 to Oracle Application
Server Disaster Recovery Site"
Section 7.7, "Silent and Non-Interactive Patch Application"
Section 7.8, "Failure During Software Update"
22
7.1 Applying OracleAS 10g Release 2 Patch Set 3

This section describes application procedures for the OracleAS 10g Release 2 Patch Set
3. It includes the following steps:
Section 7.1.1, "Back up Your Existing Environment"
Section 7.1.2, "Check Port Designations (Windows Only)"
Section 7.1.3, "Apply the Oracle Database Update"
Section 7.1.4, "Apply Patch 5255249 (SPARC Only)"
Section 7.1.5, "Apply the OracleAS 10g Release 2 Patch Set 3 Software Update"
Section 7.1.6, "Apply the Metadata Repository Update"
Section 7.1.7, "Update OracleAS Portal Repositories that Reside in Oracle RAC
Manually"
Section 7.1.8, "Update OracleAS Portal Repository Manually"
Section 7.1.9, "Update OracleAS Wireless Repository Manually"
7.1.1 Back up Your Existing Environment

There is no automatic procedure for deinstalling the OracleAS 10g Release 2 Patch Set
3. Oracle recommends that you make a backup of your existing environment before
you install OracleAS 10g Release 2 Patch Set 3. If you choose to remove OracleAS 10g
Release 2 Patch Set 3, or if you encounter a problem with application of the patch, then
you can restore your original environment.
See Also: Oracle Application Server 10g Release 2 (10.1.2)
installation guide for complete deinstallation procedure.
7.1.2 Check Port Designations (Windows Only)

If you are using Windows, then the ports used for Application Server Control Console
should be checked and updated prior to applying the patch set. The following
procedure describes how to check and update the ports:
1.
Shut down all components of Oracle Enterprise Manager 10g, including

Application Server Control Console and emagent processes.
2.
Edit the ORACLE_HOME/sysman/config/emd.properties file as follows:
3.
4.
5.
a.
Locate the EMD_URL property.
b.
Change the port number to an unused port number in the range between
18130 and 18149.
Edit the ORACLE_HOME/sysman/j2ee/config/emd-web-site.xml file as

follows:
a.
Locate the Web-site entry.
b.
Update the port value to an unused port number in the range between 18100
and 18120.
Edit the ORACLE_HOME/sysman/emd/targets.xml file as follows:

a.
Locate the oracle_ias target StandaloneConsoleURL property.
b.
Modify the port to match the one used in the emd-web-site.xml file.
Edit the ORACLE_HOME/sysman/j2ee/config/rmi.xml file as follows:
23
6.
a.
Locate the rmi-server entry.
b.
Update the port value to an unused port number in the range between 18150
and 18169.
Edit the ORACLE_HOME/bin/emctl.pl file as follows:

a.
Locate the line that looks similar to EM_ADMIN_PORT=":18150";.
b.
Update the number to match the one in the rmi.xml file.
7.1.3 Apply the Oracle Database Update

If you plan to update your Metadata Repository to 10g Release 2 (10.1.2.3.0), then it is
necessary to apply the Oracle Database 10g Release 1 (10.1.0.5) patch set to the
database in the infrastructure Metadata Repository for Oracle Identity Management
with Metadata Repository or Metadata Repository only environments. The database
patch is available from OracleMetaLink.
The following procedure describes how to apply the patch to a Metadata Repository
that was created as part of the Infrastructure installation with Oracle Universal
Installer.
Notes:
If you installed a Metadata Repository into an existing database

using the Oracle Application Server Metadata Repository Creation
Assistant, or you are using Oracle Real Application Clusters, then
refer to Oracle Database Patch Set Notes (for Oracle Application Server
and Oracle Collaboration Suite) 10g Release 1 (10.1.0.5) for
instructions. The database patch set notes are available in the
following directory:
ORACLE_HOME/rdbms/notes
If the Metadata Repository was updated to Oracle Application

Server 10g Release 2 (10.1.2.2.0), then it is not necessary to apply
the database patch again.
For the certified Linux x86-64 platforms, you must set the
32-bit shell emulation mode before starting Oracle Universal Installer
or any other Oracle Application Server commands or scripts by
running the following command:
Important:
# linux32 bash
1.
Log in to the system.
2.
For Unix: Log in as the oracle user.

For Windows: Log in as a member of the Administrators group. If you are
installing on a Primary Domain Controller or Backup Domain Controller, then
log in as a member of the Domain Administrators group.
(For UNIX) Set the display for the local system using the following command, if
you are not installing the software on the local system.
Bourne, Bash or Korn shell:
24
DISPLAY=local_host:0.0 ; export DISPLAY
C shell:
setenv DISPLAY local_host:0.0
In the preceding commands, local_host is the host name or IP address of the system
that you want to display Oracle Universal Installer screens.
3.
Stop all listener, agent and processes running in or against the Oracle home as
follows:
a.
Stop the processes.

For UNIX:
ORACLE_HOME/opmn/bin/opmnctl stopall
For Windows:
ORACLE_HOME\opmn\bin\opmnctl stopall
Note: For UNIX, it is also necessary to shut down the Oracle Cluster
Synchronization Services daemon. Run the following command as the
root user:
/etc/init.d/init.cssd stop
b.
Stop Oracle Enterprise Manager 10g.

For UNIX, run the following commands:
ORACLE_HOME/bin/emctl stop iasconsole
ORACLE_HOME/bin/emctl stop dbconsole
For Windows, run the following commands:

ORACLE_HOME\bin\emctl stop iasconsole
ORACLE_HOME\bin\emctl stop dbconsole
c.
Shut down the existing Oracle instance using normal or immediate priority
using one of the following commands:
For normal shutdown:

SQL> SHUTDOWN;
For immediate shutdown:

SQL> SHUTDOWN immediate;
d.
Stop the database listener.

For UNIX
ORACLE_HOME/bin/lsnrctl stop
For Windows:
ORACLE_HOME\bin\lsnrctl stop
4.
Enter the following command to start Oracle Universal Installer:
25
For UNIX:
cd /tmp
/directory_location/runInstaller
For Windows:
Double-click directory_location/setup.exe in the Windows Explorer.
In the preceding commands, directory_location is the directory with the database

patch set files.
5.
Click Next on the Welcome screen.
6.
Click Browse on the Specify File Locations screen. It is next to the Path field in the
Source section.
7.
Select the products.xml file from directory where you put the patch files.
8.
Click Next.
9.
Select the Oracle home that will get the update in the Name field.
10. Click Next.

11. Click Install.
If you are installing the patch on UNIX, then you will have to
run the root.sh script in a separate window when prompted by the
system. Run the script as the root user.
Note:
12. Click Exit when the End of Installation screen appears.

13. Click Yes to exit from Oracle Universal Installer.
14. (Windows Only) Restart services for the infrastructure.
15. Start the Oracle instance using the following commands:
SQL> connect SYS as SYSDBA
SQL> startup
16. Set the value of the SHARED_POOL_SIZE initialization parameter to at least 150
MB, if using a server parameter file. Log in as the sys user and use the following
command to check the parameter:
SQL> show parameter SHARED_POOL_SIZE
If the parameter is less than 150 MB, then use the following command to set it:
SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M' SCOPE=spfile;
17. Set the value of the JAVA_POOL_SIZE initialization parameter to at least 150 MB,
if necessary. Log in as the sys user and use the following command to check the
parameter:
SQL> show parameter JAVA_POOL_SIZE
If the parameter is less than 150 MB, then use the following command to set the
parameter:
SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='150M' SCOPE=spfile;
26
18. Shut down the database using the following command:

SQL> SHUTDOWN
19. Enter the following SQL*Plus commands:
For UNIX:
SQL>
SQL>
SQL>
SQL>
STARTUP UPGRADE
SPOOL patch.log
@/ORACLE_HOME/rdbms/admin/catpatch.sql
SPOOL OFF
For Windows:
SQL>
SQL>
SQL>
SQL>
STARTUP UPGRADE
SPOOL patch.log
@\ORACLE_HOME\rdbms\admin\catpatch.sql
SPOOL OFF
20. Review the patch.log file for errors and inspect the list of components that is
displayed at the end of the catpatch.sql script. This list provides the release
and status of each SERVER component in the database.
21. If necessary, re-run the catpatch.sql script to correct any problems.
22. Restart the database as follows. You must be logged in as a member of the dba
group in order to start the database.

SQL> SHUTDOWN
SQL> STARTUP
23. Run the utlrp.sql script as the sys user to recompile all invalid PL/SQL
packages. Use the following command to run the script:
For UNIX:
SQL> @/ORACLE_HOME/rdbms/admin/utlrp.sql
For Windows:
SQL> @\ORACLE_HOME\rdbms\admin\utlrp.sql
7.1.4 Apply Patch 5255249 (SPARC Only)

After applying the Oracle Database 10g Release 1 (10.1.0.5) patch on SPARC, you must
apply patch 5255249 so that Oracle Internet Directory will start. The patch is available
from OracleMetaLink at
To apply patch 5255249, do the following:
1.
Ensure all services are stopped.
2.
Make sure the PATH environment variable contains a reference to the ORACLE_
HOME/OPatch directory, where ORACLE_HOME refers to the Oracle Home on
which the Oracle Database 10g Release 1 (10.1.0.5) patch was applied.
3.
Set the OPATCH_PLATFORM_ID environment variable to 453:

setenv OPATCH_PLATFORM_ID 453
4.
Set the ORACLE_HOME environment variable.
5.
Go to the directory where patch 5255249 is located and apply the patch:
27
cd 5255249
opatch apply
6.
Ensure the ORACLE_HOME environment variable is set and is pointing to the

Oracle Application Server Infrastructure installation location. This is necessary
when running the root.sh script.
7.
After the patch installation is completed, run the root.sh script bundled with
patch 5255249 as root user.
For more information, please refer to the Readme document bundled with patch
5255249.
7.1.5 Apply the OracleAS 10g Release 2 Patch Set 3 Software Update
The Software Update updates the software and configuration files contained in the
Oracle home.
When the Software Update is applied to an infrastructure Oracle home, it is referred to
as an Identity Management Update in these notes.
If you are running an installation that does not require an
infrastructure database, then you only need to apply the Software
Update portion of this patch set. No other updates are required.
Note:
For middle-tier installations, the Software Update may also upload data specific to
the middle-tier installation you are updating to the OracleAS Metadata
Repository.
For Oracle Identity Management installations, the Software Update also updates
the schemas in the Identity Management system.
When applying the software update to an Oracle home that
contains only OracleAS Metadata Repository, all Identity Management
and middle tier processes should be stopped prior to applying the
software update.
Note:
The following procedure describes how to apply the Software Update:

1.
Back up the relevant OracleAS Metadata Repository before applying the Software
Update.
2.
Log in to the Application Server Control Console as the same user name as the one
used for the original installation.
3.
If you are applying the software update to an Oracle infrastructure home, then the
database console must be shutdown before applying the software update.
Shutdown the database console using the following command:
For UNIX:
ORACLE_HOME/bin/emctl stop dbconsole
For Windows:
ORACLE_HOME\bin\emctl stop dbconsole
28
4.
Oracle Universal Installer is used to update the Oracle Application Server

software. Start the Oracle Universal Installer that comes with the OracleAS 10g
Release 2 Patch Set 3 as follows:
For UNIX:
> ./runInstaller
For Windows:
a.
Log in to the computer as a user who is a member of the Windows

Administrators group.
b.
Insert the installation media.
c.
If your computer supports the autorun feature, then the installer launches
automatically.
If your computer does not support the autorun feature, then you have to start
the installer manually as follows:
5.
CD-ROM users: Double-click the setup.exe file.
DVD users: Double-click the setup.exe file located in the

application_server directory.
Table 1 describes the steps and screens you will encounter during application of
the Software Update on an Oracle Application Server middle-tier, OracleAS
Infrastructure, or Oracle Business Intelligence installations.
Table 1
1.
Steps for Applying Oracle Application Server Patch
Screen
Action
Welcome
Review the Oracle Universal Installer Welcome screen and

click Next.
The Welcome screen provides information about Oracle
Universal Installer.
The following buttons appear on the installation screens:
Deinstall Products: Deinstall individual components

or the entire product. This button appears only on the
Welcome screen.
About Oracle Universal Installer: View the release
number of the installer.
Help: Access detailed information about the
functionality of each screen.
Installed Products: View currently installed products
or deinstall the entire product or components.
Back: Return to the previous screen. This button is
disabled on the Welcome screen.
Next: Proceed to the next screen.
Install: Install the selected product. This button is
Cancel: Quit the installation process and exit the
installer.
29
Table 1 (Cont.) Steps for Applying Oracle Application Server Patch
2.
Screen
Action
Specify File
Locations
Check the default source path, destination name, and

destination path shown on the Specify File Location page
for your update of your installed Oracle Application Server
software. If you do not want to use the defaults, then enter
the values you want to use. Click Next to continue.
The Specify File Locations screen allows you to enter the
full path for the source and destination locations for your
update of Oracle Application Server software. The Name
and Path fields must have the same values as the base
installation.
Source: This is the full path to the products.xml file

from which the product will be installed. The installer
detects and uses the default values of the
products.xml file of the installation program. Do
not change the path.
Name: Select the Oracle home name for the
environment to be patched.
Oracle homes are identified by name. The Oracle
home name identifies the program group associated
with a specific Oracle home and the installed Oracle
services associated with the home.
Path: This is the full path to the Oracle home for

application of the Software Update.
This field is filled automatically when you select the
Oracle home name.
3.
Select a Product to
Install
Browse: Navigate the file system to find source and

destination locations.
Select the following option:
Oracle Application Server Software Update

Select this option if you want to update your Oracle
Application Server software and/or Oracle Developer
Suite. You can update your Oracle Application Server
middle-tier, or infrastructure.
The Software Update also updates the database
schemas for Identity Management components.
For middle-tier installations, this option may also
upload data specific to the middle-tier installation you
are updating to the OracleAS Metadata Repository.
Click Next.
4.
Instance Password
(Oracle Application
Server only)
Enter the ias_admin user password. This is the same

password as the same as the Application Server Control
password.
The Oracle Application Server or Identity Management
instance that is receiving the update is displayed.
Click Next.
5.
Warning
The Oracle Application Server middle tier processes will be

shut down. There may be a brief pause in the installation
while the middle tier processes are stopped. Click OK.
30
6.
Screen
Action
Oracle Internet
Directory Login
The update installation must connect to your Oracle

Internet Directory.
Note: This screen

only appears when
patching the middle
tier and
infrastructure that
are associated with
Oracle Internet
Directory.
The user name and password identities you enter are

determined by your enterprise consisting of either a single,
or more than one Oracle Application Server realm.
You will see one of the following screens:
Single Realm: Oracle Internet Directory is configured

for single realm.
You can connect either by:
Entering the user name and password to log

in to the Oracle Internet Directory at the
hostname and port of your Oracle
Application Server installation.
You must be the Oracle Internet Directory
superuser. Use cn=orcladmin as the user
name if you are the Oracle Internet Directory
superuser.
Use your OracleAS Single Sign-On user

name if you have restricted installation
privileges.
Multiple Realm: Oracle Internet Directory is

configured for more than one realm.
You can connect either by:
Entering the user name, password, and

Identity Management Realm to connect and
log in to the Oracle Internet Directory at the
hostname and port.
The Identity Management Realm is an area
in Oracle Internet Directory where you
administer user identities and groups.You
must be the Oracle Internet Directory
superuser to apply the update to Identity
Management Realm. Use cn=orcladmin as
the user name if you are the Oracle Internet
Directory superuser.
7.
OracleAS Certificate
Authority
Administrator
Use your OracleAS Single Sign-On user

name if you have restricted installation
privileges.
(Required only if OracleAS Certificate Authority is)

configured).
Enter the password for the OracleAS Certificate Authority
Administrator. Updates to the Certificate Authority
configured require administrative privileges.
31
8.
Screen
Action
Enter Metadata
Repository SYS
Password
(Required only if selected update requires DBA access.)

Enter the password for the Metadata Repository SYS user
on the selected database.
Shut down Identity Management clients. This includes:
Warning
9.
Middle tiers using the Identity Management instance

for authentication or identity services.
Distributed Identity Management installations or
other Identity Management nodes which depend on
this Identity Management instance for authentication
or identity services.
Clustered Identity Management installations or other
un-patched Identity Management instances which are
a part of the Identity Management cluster.
Stop all the middle tier processes and clients of the Identity
Management instance you are updating when prompted to
do so.
All the processes of the selected Oracle home will be
stopped at this point.
Summary
10.
Verify your selections and click Install.

Oracle Process Manager and Notification Server (OPMN)
and Oracle Enterprise Manager 10g processes will be
stopped automatically.
11.
Install Progress
This screen shows the progress of the Software Update.
12.
Configuration
Assistants
This screen shows the progress of the configuration

assistants. Configuration assistants perform updates to
already configured components.
13.
End of Installation
Click Exit to quit the installer.
6.
If Oracle BPEL Process Manager is installed on the middle tier, then redeploy
TaskManager and TaskActionHandler by copying the JAR files to the deployment
directory, using the following commands:
For UNIX:
cp
$ORACLE_HOME/integration/orabpel/install/extensions/bpel_TaskActionHandler_
1.0
.jar $ORACLE_HOME/integration/orabpel/domains/default/deploy/
cp
$ORACLE_HOME/integration/orabpel/install/extensions/bpel_TaskManager_
1.0.jar
$ORACLE_HOME/integration/orabpel/domains/default/deploy/
For Windows:
copy
%ORACLE_HOME%\integration\orabpel\install\extensions\bpel_
TaskActionHandler_1.0.jar
%ORACLE_HOME%\integration\orabpel\domains\default\deploy\
copy
32
%ORACLE_HOME%\integration\orabpel\install\extensions\bpel_TaskManager_
1.0.jar
%ORACLE_HOME%\integration\orabpel\domains\default\deploy\
7.1.6 Apply the Metadata Repository Update

The following procedure describes how to apply the OracleAS Metadata Repository
Update.
1.
Back up the Metadata Repository database before applying the Metadata

Repository Update, if you have not already done so.
2.
Perform the Software Update as detailed in Section 7.1.5, "Apply the OracleAS 10g
Release 2 Patch Set 3 Software Update" prior to installing the Metadata Repository
Update portion of OracleAS 10g Release 2 Patch Set 3.
Each middle tier installation that uses the Metadata Repository must have the
Software Update prior to performing the Metadata Repository Update.
You can identify which middle tier installations are using a Metadata Repository
by running the following command from either Identity Management or
middle-tier installation. Oracle Internet Directory must be up and running before
running the command.
-
For UNIX:
ORACLE_HOME/bin/ldapsearch -h OID Host -p OID SSL Port -D OID User
-w OID Password -U 1 -s sub -b "cn=Associated
Mid-tiers,OrclReferenceName=GlobalDBName, cn=IAS Infrastructure
Databases,cn=IAS,cn=Products,cn=OracleContext" "objectclass=*"
uniquemember
For Windows:
C:\> ORACLE_HOME\bin\ldapsearch -h OID Host -p OID SSL Port -D OID User
-w OID Password -U 1 -s sub -b "cn=Associated
Mid-tiers,OrclReferenceName=GlobalDBName, cn=IAS Infrastructure
Databases,cn=IAS,cn=Products,cn=OracleContext" "objectclass=*"
uniquemember
In the preceding commands, the following variables were used:
OID Host: Oracle Internet Directory Server host name
OID SSL Port: Oracle Internet Directory Server Secure Sockets Layer (SSL) port
3.
OID User: Distinguished name of an Oracle Internet Directory user (default is

cn=orcladmin)
OID password: User password
GlobalDBName: Global Database Name for the Metadata Repository
Before running the Metadata Repository Update you must stop all Oracle
Application Server middle-tier instances that use the Metadata Repository.
To stop your middle tier instances, use the following commands:
To stop the Application Server Control Console:
For UNIX:
33
For Windows:
C:\> ORACLE_HOME\bin\emctl stop iasconsole
To stop your Oracle Application Server components:
For UNIX:
For Windows:
C:\> ORACLE_HOME\opmn\bin\opmnctl stopall
This command stops OPMN and all OPMN-managed processes such as Oracle
HTTP Server, OC4J instances, and OracleAS Web Cache.
4.
Oracle Universal Installer is used to install the OracleAS 10g Release 2 Patch Set 3
Metadata Repository Update. Start the Oracle Universal Installer that came with
the OracleAS 10g Release 2 Patch Set 3, as follows:
For UNIX:
> ./runInstaller
For Windows:
a.
Log in to the computer as a user who is a member of the Windows

Administrators group.
b.
Insert the installation media.
c.
If your computer supports the autorun feature, then the installer launches
automatically.
If your computer does not support the autorun feature, then you have to start
up the installer manually:
CD-ROM users: Double-click the setup.exe file.
DVD users: Double-click the setup.exe file located in the application_

server directory.
Caution: When applying the Metadata Repository Update, if

any errors are encountered, then do not attempt to retry the
update. After a failure of the update, the repository may be left
in an inconsistent, unsupported state. If any errors appear
during the first update attempt, then exit the installer and call
Oracle Support. Do not attempt to modify or access OracleAS
Metadata Repository components in any way before receiving
instructions from Oracle Support. You can access information
about technical support at
http://www.oracle.com/support
5.
Table 2 describes the steps and screens you will encounter during update of an
34
Table 2
Steps for Applying Metadata Repository Update
Screen
Action
1.
Welcome
Refer to Table 1 for the complete list of screen options.
2.
Specify File
Locations
During the update you must specify one of the following

Oracle home locations:
Portal and Wireless Middle Tier
Business Intelligence Middle Tier
Infrastructure containing both Identity Management

and Metadata Repository
J2EE and Web Services Middle Tier (Standard Edition
One only)
Portal Middle Tier (Standard Edition One only)
In OracleAS Portal only installation, Wireless will also
be listed, but will not have an effect on the Metadata
Repository update.
3.
Select a Product to
Install
Oracle Application Server Metadata Repository

Update
Select this option to update the metadata stored in
your OracleAS Metadata Repository that is used by
your Oracle Application Server middle tiers.
You must run the Oracle Application Server Software
Update on all of your Oracle Application Server middle-tier installations before using the Oracle Application Server Metadata Repository Update.
Click Next.
4.
Warning
Make sure the Oracle Database hosting the OracleAS

Metadata Repository is certified for version 10.1.2.3.0, a
database backup of OracleAS Metadata Repository has
performed, all middle-tiers using the OracleAS Metadata
Repository are updated to 10.1.2.3.0 or later .
Verify the tasks have been performed, and click OK.
5.
Applying Metadata
Repository Update
Select one of the following options:
Immediately install the update.

This option updates one of the registered Metadata
Repositories during this installation session.
Save update files for later use.

This option copies the update files to the Oracle home,
but does not apply them. The saved files can be used
to manually update the OracleAS Portal repository
and OracleAS Wireless repository at a later time. Refer
to Section 7.1.8, "Update OracleAS Portal Repository
Manually" for instructions on how to use the saved
files for updating the OracleAS Portal repository or the
OracleAS Wireless repository.
6.
Application Server
Instance Password
Enter the password for the Oracle Application Server

instance containing the OracleAS Metadata Repository that
you are updating.
This is the same password for the ias_admin user and the
same as the Application Server Control password.
Click Next.
35
Table 2 (Cont.) Steps for Applying Metadata Repository Update

Screen
Action
7.
Oracle Internet
Directory Login
Refer to Table 1 for the complete list of options.
8.
Select OracleAS
Metadata Repository
Select an available OracleAS Metadata Repository to

update.
The software on all of your Oracle Application Server
middle tier installations must be updated using the
procedure described in Section 7.1.5, "Apply the OracleAS
10g Release 2 Patch Set 3 Software Update".
9.
Enter Metadata
Repository SYS
Password
Enter the password for the Metadata Repository SYS user

on the selected database.
10.
Select Schema for

Update
Select the Oracle Application Server products whose

schema will be updated in the Metadata Repository. The
existing schema must be at 10.1.2.x.x to be updated by this
installation. Oracle Application Server products which are
not listed do not have schema changes in this update
release.
11.
Warning
Stop all the middle tier processes and clients of the IM

instance when asked to do so.
12.
Summary
13.
Install Progress
This screen shows the progress of patch set installation.
Shut down any Metadata Repository clients that you are

updating. This includes all Oracle Application Server
middle tiers which are associated with the Metadata
Repository.
Note: Application of the OracleAS 10g Release 2 Patch Set 3

to an instance of Oracle Application Server that uses Oracle
Internet Directory may take longer than expected. This
may occur if there is a large amount of data in the Oracle
Internet Directory.
14.
Configuration
Assistants
This screen shows the progress of the configuration

assistants. Configuration assistants update a single
component schema.
15.
End of Installation
6.
Start the Oracle Application Server components, as follows:
For UNIX:
ORACLE_HOME/opmn/bin/opmnctl startall
For Windows:
C:\> ORACLE_HOME\opmn\bin\opmnctl startall
This command starts OPMN and all OPMN-managed processes such as Oracle
7.
Start the Application Server Control Console:
For UNIX:
ORACLE_HOME/bin/emctl start iasconsole
For Windows:
36
C:\> ORACLE_HOME\bin\emctl start iasconsole

8.
Start the DCM daemon using the following command (Windows only):
C:\> ORACLE_HOME\opmn\bin\opmnctl startproc ias-component=dcm-daemon
7.1.7 Update OracleAS Portal Repositories that Reside in Oracle RAC Manually
If you are manually updating an OracleAS Portal repository (Section 7.1.8) that resides
in a Oracle Real Application Clusters (Oracle RAC), then perform the following steps:
1.
Create a TNS alias in the tnsnames.ora file for one of the active database
instances in your cluster. The file is located in the following directory:
For UNIX: The current ORACLE_HOME/network/admin directory.

For Windows: The current Oracle home ORACLE_HOME\network\admin
directory
2.
If it is applicable, turn off server-side load balancing in your Oracle RAC.
3.
Follow the instructions described in Section 7.1.8, "Update OracleAS Portal

Repository Manually" using the newly created TNS alias as the connect string.
4.
If it is applicable, turn on the server-side load balancing in your Oracle RAC.
7.1.8 Update OracleAS Portal Repository Manually

This section describes the procedures for manual update of the OracleAS Portal
Repository. You can apply this update to multiple repositories without repeated
installation of the update to the same Oracle home. You can also use this update for an
OracleAS Portal Repository that resides outside of the OracleAS Metadata Repository.
If your OracleAS Portal instance was originally installed
in release 3.0.9 or earlier, or if it was installed using ptlasst,
then it resides outside of an OracleAS Metadata Repository and
needs to be updated manually.
Note:
Perform the following steps to manually update your OracleAS Portal repository:
1.
Apply the Software Update as detailed in Section 7.1.5, "Apply the OracleAS 10g
Release 2 Patch Set 3 Software Update" to all middle-tier Oracle homes that are
associated with your OracleAS Portal repository if it has not already been done.
The OracleAS Portal instance will not function properly if the repository is
updated before the middle tiers that are configured for that repository.
2.
Create a cold backup of the database in which your OracleAS Portal repository
resides.
3.
Apply the Metadata Repository Update as detailed in Section 7.1.6, "Apply the
Metadata Repository Update".
The update can be performed using either available installation option:

When choosing this option, the OracleAS Portal repository is not updated and
the files needed to perform the update are simply copied to your Oracle home.
This option is useful when there are no OracleAS Portal repositories residing
37
in an OracleAS Metadata Repository that need updating, or when all instances

will be updated manually. The update can be performed from any OracleAS
middle-tier Oracle home or from an infrastructure Oracle home that contains
both a Metadata Repository and an Oracle Identity Management installation.

When choosing this option, the files needed to perform the update are copied
over to your Oracle home and then the OracleAS Portal repository in the
selected Metadata Repository is updated. This option can be chosen, for
example, to update an OracleAS Portal repository residing in a Metadata
Repository before running the update manually on an OracleAS Portal
instance residing outside of a Metadata Repository. This mode also copies the
files over that are necessary to perform any subsequent updates to other
repositories, so you can then use the installed files to manually update any
remaining OracleAS Portal instances that you use. The update can be
performed from any middle-tier Oracle home that is associated with the
Metadata Repository being updated, or from the infrastructure Oracle home
that contains the installation of the Metadata Repository being updated. After
the installation, the files that are copied over can be used to manually update
any other Portal repositories.
A manual update on the repository that was updated
automatically when this option was chosen should not be attempted.
The update will fail because it has already occurred.
Note:
4.
Set your ORACLE HOME environment variable to the Oracle home where the
Metadata Repository Update was applied.
5.
Obtain the OracleAS Portal Schema Password.

If your OracleAS Portal schema resides in the OracleAS Metadata Repository, then
the password will be randomized. Use the Oracle Directory Manager to obtain the
password.
a.
Start Oracle Directory Manager as follows:
For UNIX, use the following command:

ORACLE_HOME/bin/oidadmin
For Windows, select Programs from the Start menu, then select Oracle
Application Server instance name from Programs menu. Next, select
Integrated Management Tools, and then Oracle Directory Manager.
b.
Log in to Oracle Directory Manager as the orcladmin user.
c.
Expand Entry Management in the System Objects section. Enter the following
values:
cn=OracleContext
cn=Products
cn=IAS
cn=IAS Infrastructure Databases
OrclReferenceName=Infrastructure database name for OracleAS Metadata

Repository, such as asdb.server.example.com
38
6.
d.
Select the OrclResourceName=PORTAL entry to view the Portal schema

password.
e.
Click the Properties tab to view the schema password in the

orclpasswordattribute field.
Verify you can connect to the OracleAS Portal schema through SQL*Plus using the
schema password and the TNS name from the Oracle home where the Metadata
Repository Update was applied.
For example:
sqlplus portal/password@asdb
7.
Stop all Oracle Application Server services in the middle-tier Oracle homes that
are associated with the OracleAS Portal repository being updated as follows:
To stop the Application Server Control Console:
For UNIX:
For Windows:
C:\> ORACLE_HOME\bin\emctl stop iasconsole
To stop Oracle Application Server components:
For UNIX:
For Windows:
C:\> ORACLE_HOME\opmn\bin\opmnctl stopall
This command stops OPMN and all OPMN-managed processes such as Oracle
8.
Verify the Oracle Internet Directory associated with the OracleAS Portal schema is
up and running.
9.
Go to the following directory in the Oracle home where the Metadata Repository
Update was applied.
For UNIX: portal/upg/plsql
For Windows: portal\upg\plsql
The directory was created during the Metadata Repository update. If the directory
does not exist in your Oracle home, then either the update has not been applied or
the update was applied to a different Oracle home.
10. Run the upgrade script in precheck mode until there are no errors in the log. The
script generates the upgrade.log file and the upgrade directory, tmp, in the
current directory. The syntax is as follows:
For UNIX:
ORACLE_HOME/portal/upg/plsql/patch.sh -precheck
For Windows:
C:\> ORACLE_HOME\portal\upg\plsql\patch.bat -precheck
39
When the -precheck option is specified, only the pre-upgrade checks are done
and the upgrade exits afterward. In this mode, the upgrade is not immediately
terminated if a precheck fails. Instead, the errors for all prechecks are consolidated
in the upgrade.log file. Look at the end of the log to see a list of checks that
failed. Run the script in this mode until the precheck does not fail. In this mode,
the schema is not altered, so restoring from your backup is not necessary between
runs.
(UNIX only) The ocssd.bin process is started and controlled by
the operating system. If you receive an error that the process is
running, then it is necessary to log in as the root user and run the
following command:
Note:
/etc/init.d/init.cssd stop
11. Run the upgrade script without parameters after resolving all warnings and errors
from the precheck step. The syntax is as follows:
For UNIX:
ORACLE_HOME/portal/upg/plsql/patch.sh
For Windows:
C:\> ORACLE_HOME\portal\upg\plsql\patch.bat
The script prompts you for information about the system setup. Your answers are
echoed back for verification at the end of the script.
Table 3 shows the questions from the script. Default answers to the questions are
given in brackets.
Table 3
Upgrade Script Prompts
Prompt
Explanation
Have you backed up your database

(y|n)? [y]:
If you have backed up the database, then

answer y.
If you have not backed up the database, then
answer n, back up the database and restart the
script.
Enter the name of the schema you

would like to upgrade [portal]:
If your schema name is different from the

default OracleAS Infrastructure installation
schema name of portal, then enter the schema
name.
Enter the password of the schema

you would like to upgrade
[portal]:
Enter the database password for the schema

that is to be updated.
Enter the password for the SYS

user of your database [change_
on_install]:
Enter the password for the SYS user.
Enter the TNS connect string to

connect to the database [orcl]:
Provide the TNS connect string found in the

ORACLE_
HOME/network/admin/tnsnames.ora file.
40
Table 3 (Cont.) Upgrade Script Prompts

Prompt
Explanation
At this point, no changes have

been made to the database.
Please review all the details
displayed above.
If you choose to stop the
upgrade at this point, you will
be able to
start it again without restoring
from a backup.
If you continue and a problem
occurs, you will have to
retrieve your
backup and start over.
Is this information correct
(y/n)? [y]:
Verify that the answers are correct, and answer

the question:
Enter y to proceed with the upgrade.

Enter n to stop the upgrade. If necessary,
you can run the upgrade script again,
correcting answers as needed.
If you have entered any incorrect information,

then answer n. This will allow you to exit before
any changes are made by the script.
12. Examine the upgrade.log file.
Any errors that occurred during the upgrade are captured in the upgrade.log
file. You should examine this file to ensure that there were no errors and that the
upgrade was successful.
a.
Locate the upgrade.log log file. The location is the current directory.
b.
Open the log with a text editor.
c.
Go to the end of the file. You will either see a success message or a set of
errors.
d.
Check Oracle Application Server Portal Error Messages Guide for any errors or
warnings. The guide is available at Oracle Technology Network at
http://www.oracle.com/technology
Most errors require that you restore the repository, fix the problem, and re-run
the upgrade. Contact Oracle Support if there are any errors not shown in the
guide.
You cannot run OracleAS Portal until there is a successful upgrade. A
successful upgrade has no errors.
The following is an example of the end of the log file after a successful
upgrade. It includes the "Upgrade completed successfully" message and does
not have any error messages:
Example 1 Log File after Successful Upgrade

### Show errors and warnings
Step started at Tue Jan 12 04:17:22 2008
###
### WARNING: WWU-26002: Upgrade completed with the following warnings:
. . .
### Upgrade completed successfully
. . .
Upgrade Ended at Tue Jan 12 04:17:31 2008
41
The following examples show the log files from unsuccessful upgrades. Notice
the line numbers preceding the errors in Example 3.
Example 2 Premature Termination Showing Error Section
### ERROR: WWU-01013: Upgrade terminated with the following errors:
###
1278 : EXP-00003: no storage definition found for segment
(9, 10251)
###
1368 : ### ERROR: Exception Executing Script
upg/common/precln/../../frwk/export.pl :
. . .
### Upgrade aborted at Wed Jan 06 04:28:18 2008.
Example 3 Standard Termination, but with Errors
###
### Show errors and warnings
###
Upgrade step started at Thu Jan 07 03:52:56 2008
###
### WARNING: WWU-26002: Upgrade completed with the following warnings:
###
...
###
### ERROR: WWU-01012: Upgrade completed with the following errors:
###
8503:ERROR at line 1:
###
8504 : ORA-20000:
###
8505 : ORA-06512: at "UPGR309.WWPOF", line 440
. . .
Upgrade Ended at Thu Jan 07 04:28:08 2008
13. Start all Oracle Application Server services in the middle-tier Oracle homes that
are associated with the OracleAS Portal repository that was just updated as
follows:
To start Oracle Application Server components:
For UNIX:
ORACLE_HOME/opmn/bin/opmnctl startall
For Windows:
C:\> ORACLE_HOME\opmn\bin\opmnctl startall
To start the Application Server Control Console:
For UNIX:
ORACLE_HOME/bin/emctl start iasconsole
For Windows:
C:\> ORACLE_HOME\bin\emctl start iasconsole
To start the DCM daemon (Windows only):

C:\> ORACLE_HOME\opmn\bin\opmnctl startproc ias-component=dcm-daemon
14. Test your updated OracleAS Portal instance.
42
7.1.9 Update OracleAS Wireless Repository Manually

This section describes the procedures for a manual update of the OracleAS Wireless
Repository.
1.
Apply the Software Update as detailed in Section 7.1.5, "Apply the OracleAS 10g
Release 2 Patch Set 3 Software Update" to all middle-tier Oracle homes that are
associated with your OracleAS Wireless repository, if it has not already been done.
2.
Apply the Metadata Repository Update as detailed in Section 7.1.6, "Apply the
Metadata Repository Update".
The update can be performed using either available installation option:

When choosing this option, the OracleAS Wireless repository is not updated
and the files needed to perform the update are simply copied to your Oracle
home. This option is useful when there are no OracleAS Wireless repositories
residing in an OracleAS Metadata Repository that need updating, or when all
instances will be updated manually. The update can be performed from any
OracleAS middle-tier Oracle home or from an infrastructure Oracle home that
contains both a Metadata Repository and an Oracle Identity Management
installation.

When choosing this option, the files needed to perform the update are copied
over to your Oracle home and then the OracleAS Wireless repository in the
selected Metadata Repository is updated. This option can be chosen, for
example, to update an OracleAS Wireless repository residing in a Metadata
Repository before running the update manually on an OracleAS Wireless
instance residing outside of a Metadata Repository. This mode also copies the
files over that are necessary to perform any subsequent updates to other
repositories, so you can then use the installed files to manually update any
remaining OracleAS Portal instances that you use. The update can be
performed from any middle-tier Oracle home that is associated with the
Metadata Repository being updated, or from the infrastructure Oracle home
that contains the installation of the Metadata Repository being updated. After
the installation, the files that are copied over can be used to manually update
any other Wireless repositories.
A manual update on the repository that was updated
automatically when this option was chosen should not be attempted.
The update will fail because it has already occurred.
Note:
3.
Use the following command to apply the OracleAS Wireless update. The
ORACLE_HOME environment variable must be set for the script to run.
For UNIX:
ORACLE_HOME/wireless/upgrade_infra/bin/patchinfra.sh -P password
-C tnsname
For example:
ORACLE_HOME/wireless/upgrade_infra/bin/patchinfra.sh -P
YXYhR16V -C "(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)
(HOST=rhine985.us.example.com)(PORT=1521)))
43
(CONNECT_DATA=(SERVICE_NAME = asdb.us.example.com)))"
For Windows:
ORACLE_HOME\wireless\upgrade_infra\bin\patchinfra.bat -P password
-C tnsname
For example:
ORACLE_HOME\wireless\upgrade_infra\bin\patchinfra.bat -P
YXYhR16V -C "(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)
(HOST=rhine985.us.example.com)(PORT=1521)))
(CONNECT_DATA=(SERVICE_NAME = asdb.us.example.com)))"
In the preceding commands, password is the OracleAS Wireless schema password,

and tnsname is the net description string.
Caution: The password is passed in clear text. To have an encoded
password, use the - E option with the encoded password instead of
the -P option.
7.2 Applying OracleAS 10g Release 2 Patch Set 3 on OracleAS Cluster

(Identity Management) Environments
This section describes how to apply OracleAS 10g Release 2 Patch Set 3 to an OracleAS
Cluster (Identity Management) environment. Before applying the patch set, consider
the following:
Oracle Internet Directory may be the only Identity Management component in its
Oracle home or it can be co-located with other Identity Management components.
If it is co-located, then shutting down Oracle Internet Directory indicates that you
will need to shut down all Identity Management components, and starting Oracle
Internet Directory indicates starting all Identity Management components.
LDAP traffic can be directed to a node as soon as it has been patched to OracleAS
10g Patch Set 3 (10.1.2.3.0). It is not necessary to patch all Oracle Internet Directory
nodes before directing traffic.
-
If there is an LDAP load balancer in the environment, then ensure that the
load balancer routes LDAP traffic to the patched Oracle Internet Directory
nodes only.
The following steps describe how to apply OracleAS 10g Release 2 Patch Set 3 to
OracleAS Cluster (Identity Management) environments.
1.
Do a full backup of the OracleAS Metadata Repository and the individual Identity
Management Oracle homes.
If patch application fails for any reason, then a complete
restoration of the OracleAS Metadata Repository and Oracle Identity
Management Oracle homes will be required prior to retrying patch
application.
Note:
2.
Select one Identity Management node for installation of the patch set, such as IM_
Node1.
44
3.
Ensure that the Identity Management instance is up and running on the node.
4.
Use the following command on all other Identity Management nodes so that only
the first node, IM_Node1, remains in the cluster:
dcmctl leavecluster
5.
Shut down the Identity Management instances on all other Identity Management
nodes. If the instances are not shut down, then the installer will give the following
error while patching IM_Node1:
Oracle Universal Installer has detected active Oracle Internet Directory
instances connected to the OracleAS Metadata Repository. All Oracle Identity
Directory instances using the OracleAS Metadata Repository must be shut down
before continuing.
6.
Apply OracleAS 10g Release 2 Patch Set 3 on the first node, IM_Node1, according
to the instructions in Section 7.1, "Applying OracleAS 10g Release 2 Patch Set 3".
The Identity Management instance will be up and running after applying the
patch. Leave it up and running.
7.
Select another Identity Management node, IM_Node2.
8.
Start Identity Management on this node, IM_Node2.
9.
Apply OracleAS 10g Release 2 Patch Set 3 to the second node, IM_Node2,
according to the instructions in Section 7.1, "Applying OracleAS 10g Release 2
Patch Set 3".
The Identity Management instance will be up and running after applying the
10. Use the following command to join IM_Node2 to the DCM cluster:

11. Use the following command to bring up the Oracle Application Server Single
Sign-On/Oracle Delegated Administration Services applications:

opmnctl startall
12. Repeat steps 7 through 11 for each subsequent Identity Management node in the
cluster, one node at a time.
7.3 Applying OracleAS 10g Release 2 Patch Set 3 on Distributed OracleAS

Cluster (Identity Management) Environments
The following steps describe how to apply OracleAS 10g Release 2 Patch Set 3 to a
distributed OracleAS Cluster (Identity Management) environments. Before applying
the patch set, note the following:
Oracle Internet Directory may be the only Identity Management component in its
Oracle home or it can be co-located with other Identity Management components.
If it is co-located, then shutting down Oracle Internet Directory requires that you
will need to shut down all Identity Management components, and starting Oracle
Internet Directory requires starting all Identity Management components.
45
1.
LDAP traffic can be directed to a node as soon as it has been patched to 10g
Release 2 (10.1.2.3.0). It is not necessary to patch all Oracle Internet Directory
nodes before directing traffic.
-
In a distributed Identity Management configuration, the Oracle Application

Server Single Sign-On/Oracle Delegated Administration Services Oracle
patching can start as soon as one Oracle Internet Directory node is patched to
10g Release 2 (10.1.2.3.0). This will minimize overall downtime.
If there is an LDAP load balancer in the environment, then ensure that the
load balancer routes LDAP traffic to the patched Oracle Internet Directory
nodes only.
Do a full backup of the OracleAS Metadata Repository, the individual Oracle

Internet Directory Oracle homes, and the individual Oracle Application Server
Single Sign-On/Oracle Delegated Administration Services Oracle homes.
If patch application fails for any reason, then a complete
restoration of the OracleAS Metadata Repository and Oracle Identity
Management Oracle homes will be required prior to retrying patch
application.
Note:
2.
Select one Oracle Application Server Single Sign-On/Oracle Delegated

Administration Services node for installation of the patch set, such as SSO_Node1.
3.
Use the following command on all other Oracle Application Server Single
Sign-On/Oracle Delegated Administration Services nodes so that only the first
node, SSO_Node1, remains in the cluster:
dcmctl leavecluster
4.
Shut down all Oracle Application Server Single Sign-On/Oracle Delegated

Administration Services instances running against the Oracle Internet Directory
environment that you will be applying the patch, including SSO_Node1.
5.
Select one Oracle Internet Directory node, OID_Node1, and ensure Oracle Internet
Directory is up and running on the node.
6.
Shut down Oracle Internet Directory on all other Oracle Internet Directory nodes.
If Oracle Internet Directory on the other nodes is not shut down, then the installer
will give the following error while patching OID_Node1.
Oracle Universal Installer has detected active Oracle Internet Directory
instances connected to the OracleAS Metadata Repository. All Oracle Identity
Directory instances using the OracleAS Metadata Repository must be shut down
before continuing.
7.
Apply OracleAS 10g Release 2 Patch Set 3 on the Oracle Internet Directory node,
OID_Node1, according to the instructions in Section 7.1, "Applying OracleAS 10g
Release 2 Patch Set 3".
The Oracle Internet Directory instance will be up and running after applying the
8.
Ensure the LDAP load balancer in the configuration routes LDAP traffic to the
patched Oracle Internet Directory node, OID_Node1, only.
9.
In order to minimize downtime, the first Oracle Application Server Single

Sign-On/Oracle Delegated Administration Services instance can be patched. The
46
following steps describe how to patch the Oracle Application Server Single
Sign-On/Oracle Delegated Administration Services instance.
If you prefer to patch all the Oracle Internet Directory instances prior to the
patching Oracle Application Server Single Sign-On/Oracle Delegated
Administration Servicesinstance, then go to step 10.
a.
Start the first Oracle Application Server Single Sign-On/Oracle Delegated

Administration Services instance, SSO_Node1.
b.
Apply OracleAS 10g Release 2 Patch Set 3 to SSO_Node1, according to the

instructions in Section 7.1, "Applying OracleAS 10g Release 2 Patch Set 3". The
Oracle Application Server Single Sign-On/Oracle Delegated Administration
Services instance will be up and running after applying the patch. Leave it up
and running.
c.
Select another Oracle Application Server Single Sign-On/Oracle Delegated

Administration Services node, SSO_Node2.
d.
Start OracleAS Single Sign-On on the second node.
e.
Apply OracleAS 10g Release 2 Patch Set 3 to the second node, SSO_Node2,
according to the instructions in Section 7.1, "Applying OracleAS 10g Release 2
Patch Set 3". The Oracle Application Server Single Sign-On/Oracle Delegated
Administration Services instance will be up and running after applying the
f.
Use the following command to join SSO_Node2 to the DCM cluster:


g.
Use the following command to bring up the Oracle Application Server Single
opmnctl startall
h.
Repeat steps c through g for each subsequent Oracle Application Server Single
Sign-On/Oracle Delegated Administration Services node, one at a time.
i.
Select another Oracle Internet Directory node, OID_Node2.
j.
Start the Oracle Internet Directory instance on the second Oracle Internet
Directory node, OIDNode2.
k.
Apply OracleAS 10g Release 2 Patch Set 3 to the second Oracle Internet
Directory node, OID_Node2, according to the instructions in Section 7.1,
"Applying OracleAS 10g Release 2 Patch Set 3".
The Oracle Internet Directory instance will be up and running after applying
the patch Leave it up and running.
l.
Repeat steps i through k for each subsequent Oracle Internet Directory node,
one at a time.
m. Reconfigure the LDAP load balancer in the environment to route LDAP traffic
to all patched Oracle Internet Directory nodes.

10. Use the following steps to apply the patch set to all remaining Oracle Internet
Directory instances before the Oracle Application Server Single Sign-On/Oracle

Delegated Administration Services instances.
47
If you prefer to apply the patch to one Oracle Application Server Single
Sign-On/Oracle Delegated Administration Services instance in order to minimize
downtime, the follow the steps in step 9.
a.
Select a second Oracle Internet Directory node, OID_Node2.
b.
Start the Oracle Internet Directory instance on this node.
c.
Apply OracleAS 10g Release 2 Patch Set 3 to the second node, OID_Node2.
The Oracle Internet Directory instance will be up and running after applying
the patch. Leave it up and running.
d.
Repeat steps b and c for each subsequent Oracle Internet Directory node, one
at a time.
e.
Start the Oracle Application Server Single Sign-On/Oracle Delegated

Administration Services instance on the first Oracle Application Server Single
Sign-On/Oracle Delegated Administration Services node, SSO_Node1. This
node was selected in step 2.
f.
Apply OracleAS 10g Release 2 Patch Set 3 to the node. The Oracle Application
Server Single Sign-On instance will be up and running at the end of the
installation. Leave it up and running.
g.
Select another Oracle Application Server Single Sign-On/Oracle Delegated

Administration Services node, SSO_Node2.
h.
Start Oracle Application Server Single Sign-On on the second node, SSO_
Node2.
i.
Apply OracleAS 10g Release 2 Patch Set 3 to the node. The Oracle Application
Server Single Sign-On instance will be up and running after applying the
j.
Use the following command to join SSO_Node2 to the DCM cluster:


k.
Use the following command to bring up the Oracle Application Server Single
opmnctl startall
l.
Repeat steps g through k for each subsequent Oracle Application Server Single
Sign-On/Oracle Delegated Administration Services node, one at a time.
m. Reconfigure the LDAP load balancer in the configuration to route LDAP traffic
to all the patched Oracle Internet Directory nodes.
7.4 Applying OracleAS 10g Release 2 Patch Set 3 to OracleAS Portal 10.1.4
to Upgrade to OracleAS Portal 10.1.4.2
If your OracleAS Portal repository is release 10.1.4, or 10.1.4.1, then you must first
apply OracleAS 10g Release 2 Patch Set 3 against the middle tier and infrastructure.
This patches the middle tier and infrastructure to release 10.1.2.3. Then, apply the
release 10.1.2.3 Metadata Repository update against OracleAS Portal repository release
10.1.4 to upgrade it to release 10.1.4.2.
48
If you have upgraded the OracleAS Portal repository to release 10.1.2.3 from release
10.1.2.x or later, and you want to upgrade to OracleAS Portal release 10.1.4.2, then you
must do the following:
1.
Upgrade the OracleAS Portal repository to release 10.1.4.
2.
Re-apply the release 10.1.2.3 Metadata Repository update against OracleAS Portal
repository release 10.1.4 to upgrade it to release 10.1.4.2.
Follow the instructions in Section 7.1.6, "Apply the Metadata Repository Update" to
apply the OracleAS Portal release 10.1.4.2.0 patch.
If you are manually upgrading OracleAS Portal in a customer database, refer to the
instructions in Section 7.1.8, "Update OracleAS Portal Repository Manually".
7.5 Applying OracleAS 10g Release 2 Patch Set 3 to Oracle Developer Suite
Table 4 describes how to apply OracleAS 10g Release 2 Patch Set 3 to an Oracle
Developer Suite release 10.1.2.0.2 installation.
Table 4
1.
Steps for Applying Oracle Application Server Patch to Oracle Developer Suite
Screen
Action
Welcome
The Welcome screen provides information about Oracle

Universal Installer.
The following buttons appear on the installation screens:
Deinstall Products: Deinstall individual components

or the entire product. This button appears only on the
Welcome screen.
About Oracle Universal Installer: View the release
number of the installer.
Help: Access detailed information about the
functionality of each screen.
Installed Products: View currently installed products
or deinstall the entire product or components.
Back: Return to the previous screen. This button is
Next: Proceed to the next screen.
Install: Install the selected product. This button is
Cancel: Quit the installation process and exit the
installer.
Click Next to continue.
49
Table 4 (Cont.) Steps for Applying Oracle Application Server Patch to Oracle Developer
2.
Screen
Action
Specify File
Locations
Check the default source path, destination name, and

destination path shown on the Specify File Location page
for your update of your installed Oracle Developer Suite
software. If you do not want to use the defaults, then enter
the values you want to use.
The Specify File Locations screen allows you to enter the
full path for the source and destination locations for your
update of Oracle Developer Suite software. The Name and
Path fields must have the same values as the base
installation.
Source: This is the full path to the products.xml file

from which the product will be installed. The installer
detects and uses the default values of the
products.xml file of the installation program. Do
not change the path.
Name: Select the Oracle home name for the
environment to be patched.
Oracle homes are identified by name. The Oracle
home name identifies the program group associated
with a specific Oracle home and the installed Oracle
services associated with the home.
Path: This is the full path to the Oracle home for

application of the Software Update.
This field is filled automatically when you select the
Oracle home name.
Browse: Navigate the file system to find source and

destination locations.

3.
Select a Product to
Install
Oracle Application Server Software Update

Select this option if you want to update your Oracle
Application Server software and/or Oracle Developer
Suite.

4.
Summary
5.
Install Progress
This screen shows the progress of the Software Update.
6.
End of Installation
7.6 Applying OracleAS 10g Release 2 Patch Set 3 to Oracle Application

Server Disaster Recovery Site
This section describes how to apply OracleAS 10g Release 2 Patch Set 3 to Oracle
homes in an Oracle Application Server Disaster Recovery site.
1.
Back up the production site to ensure that the starting state is secure.
2.
Perform an ASG sync topology operation using a mandatory policy to

synchronize all the instances in the topology. This ensures that prior to patching
the configuration is updated at the standby site.
3.
Perform an ASG failover operation, but do not perform a DNS switchover for
the topology. This breaks the production/standby relationship of the topology and
50
forms two sites. This is the last recovery point of the site prior to the patch
application.
4.
Apply the patch at the former standby site. The patch application of the former
standby site is a test that the procedure will be successful. Because a DNS
switchover was not performed in the previous step, access to the site is still
maintained at the former production site. Your recovery point is effectively the
point of the backup.
5.
If problems occur in the previous step, you will remedy them when upgrading the
former production site.
6.
When the standby site patch application is complete, apply the patch to the former
production site.
7.
Perform an ASG discover topology operation at the former production site.
8.
Perform an ASG instantiate topology operation at the production site to

establish the relationship between the production and standby sites, mirror the
configuration, and synchronize the standby site with the production site.
Patch application is complete. Your Disaster Recovery topology is ready to resume

processing.
It is also possible to upgrade or update the version of Oracle
Application Server Guard (OracleAS Guard) that is installed in the
existing Oracle home for an Oracle Application Server instance. This
OracleAS Guard-only upgrade only upgrades the OracleAS Guard
(ASG) utility. It does not affect the runtime operation of the other
components in the Oracle Application Server home.
Note:
Refer to the section on using OracleAS Guard in an Oracle Application

Server Disaster Recovery topology in the Oracle Application Server
Disaster Recovery Guide for more information about how to upgrade
OracleAS Guard in an Oracle Application Server home.
7.7 Silent and Non-Interactive Patch Application

This section describes how to apply OracleAS 10g Release 2 Patch Set 3 either by silent
or non-interactive methods. Use silent patch application when you want to do similar
applications to more than one computer. You can also use silent patch application to
apply from a remote location using the command line. Use non-interactive patch
application when you want to see specific screens, or when you want to enter some
information interactively.
To do a silent or non-interactive patch application, you supply the installer with a text
file called a response file. The installer uses the variables and parameter values in the
response file to provide answers to some or all of the installer prompts.
7.7.1 Silent Patch Application

With silent patch application, you do not need to monitor the procedure because you
do not enter information, and you do not have a graphical user interface to watch.
To do a silent patch application, supply the installer with a response file and specify
the -silent flag on the command line.
51
7.7.2 Non-interactive Patch Application

With non-interactive patch application, the installer displays a graphical user interface
as in a normal patch application. If your response file does not have an entry for a
particular installer prompt, then you must provide the response during the procedure.
7.7.3 Response Files

You must create a response file before you apply the patch set. You can edit the
response files with any text editor. Start by copying the response file templates
oracle.iappserver.patchset.rsp (Software Update) and
oracle.iappserver.dbpatch.rsp (Metadata Repository Update) provided in the
following directory of your OracleAS 10g Release 2 Patch Set 3 product media:
For UNIX: stage/Response
For Windows: stage\Response
In the template, parameters have three types of values:
Constants
Optional Values
Required Values
The following sections describe the parameters.
Constants
These are text or Boolean values that are pre-set to give you a successful patch set
application. Unless you are an advanced user, do not change these values.
Examples:
-
UNIX example:
FROM_LOCATION="../stage/products.xml"
SHOW_SUMMARY_PAGE=false
Windows example:
FROM_LOCATION="E:\Disk1\stage\products.xml"
SHOW_SUMMARY_PAGE=false
Optional Values
When a parameter is set to the string <Value Unspecified>, the installer
ignores the parameter. The installer either uses the default value for the parameter,
or obtains the value from your current Oracle Application Server 10g Release 2
(10.1.2) installation. Unless you are an advanced user, do not change these values.
Examples:
-
UNIX example:
UNIX_GROUP_NAME=<Value Unspecified>
Windows example:
RESTART_SYSTEM=<Value Unspecified>
Required Values
When a parameter is set to the string <Value_Required>, you must replace the
string with a text or Boolean value. For a silent patch application, if you do not
52
supply a value, then the process will fail. For a non-interactive patch application, if
you do not replace the string with a text or Boolean value, then the process will
pause and display the normal screen that prompts for this value.
The OracleAS 10g Release 2 Patch Set 3 application requires values for the
following parameters:
-
ORACLE_HOME
This is the full path of the Oracle home directory that contains the Oracle
Application Server installation you want to patch.
*
For a silent patch application, you must update the entry

ORACLE_HOME=<Value_Required>
with the path to your Oracle home, as follows:

For UNIX: ORACLE_HOME="/private/oracle/AppSrvHome"
For Windows: ORACLE_HOME="C:\privateoracle\AppSrvHome"
If you do not update the entry, then the process will fail.
*
-
For a non-interactive patch application, if you do not update the entry,

then the installer will pause and display the File Locations dialog.
szl_InstanceInformation
This is the instance password for the current Oracle Application Server 10g
instance. The password value must match the existing password already
established for the instance. The password must be specified in clear text. For
security reasons, restrict access to the silent application response files and
delete them when they are no longer needed. The following describe how to
use the parameter:
*
For software update application on middle tiers associated with OracleAS

Portal, OracleAS Wireless, or J2EE installations associated with Oracle
Internet Directory.
oracle.iappserver.st_midtier:szl_InstanceInformation=<Value
Unspecified>
oracle.iappserver.st_midtier:szlSpecifyOIDLogin=<Value
Unspecified>
For J2EE installations not associated with Oracle Internet Directory

oracle.iappserver.st_midtier:szl_InstanceInformation=<Value
Unspecified>
For Developer Kits installations

oracle.iappserver.devkit:szl_InstanceInformation=<Value
Unspecified>
For infrastructure installations

oracle.iappserver.st_infrastructure:szl_InstanceInformation=<Value
Unspecified>
oracle.iappserver.st_infrastructure:szlSpecifyOIDLogin=<Value
Unspecified>
53
szl_SYSPassword=<Value Unspecified>
szl_OCAInformation=<Value Unspecified>
The szl_OACInformation parameter is required if Oracle Application

Server Certificate Authority is configured for the environment.
7.7.4 Performing Silent or Non-interactive Patch Application

The following procedure describes how to perform silent or non-interactive patch
application:
If any files are in use during a silent patch application, such as
a user has an open file, then the process may terminate. If that
happens, then the open file must be determined and its corresponding
process shut down. The patch application can be restarted after
shutting down the process.
Note:
1.
Copy the response file template from the product installation media to your
computer.
2.
Make the necessary changes to the copy of the file, and save it.
3.
Start the patch application. Specify the response file path and filename as the value
of the installers responseFile parameter. For a silent patch application, also
specify the silent parameter. In the following Windows examples, E is the
installation media drive.
Examples:
Silent patch application:
For UNIX:
> ./runInstaller -silent -responseFile absolute_path_and_filename
For Windows:
E:\> setup.exe -silent -responseFile absolute_path_and_filename
Non-interactive patch application
For UNIX:
> ./runInstaller -responseFile absolute_path_and_filename
For Windows:
E:\> setup.exe -responseFile absolute_path_and_filename
4.
Check the log files in your inventory directory for any errors.The log files are
located in the following directory:
For UNIX:
/oracle_inventory_path/logs/installActiontodays_date_time.log
The value of oracle_inventory_path is stored in the following file:

/var/opt/oracle/oraInst.loc
54
For Windows:
C:\oracle_inventory_path\logs\installActiontodays_date_time.log
The value of oracle_inventory_path is stored in the following file:

C:\Program Files\Oracle\Inventory
In the preceding examples, the C:\ drive is assumed to be the location of the
file. To determine the location of the file, check the HKEY_LOCAL_
MACHINE\SOFTWARE\Oracle\inst_loc registry entry.
The log file name has the format installActionstodays_date_time.log.
(UNIX only) If the base installation was done using the
graphical user interface, then Oracle Internet Directory will not be up.
Note:
7.8 Failure During Software Update

If there is a failure during application of the Software Update, then Oracle
recommends restoring your Oracle Application Server installation from the backup
release, and retrying application of the patch.
If you have no backup installation available and want to retry application of the
Software Update after a failure, then try the following steps:
1.
Correct the issue that caused the original failure during application of the Software
Update.
2.
Start the Software Update application.
3.
When the Available Products screen is displayed, expand all of the tree elements
on the screen and select all the checkboxes next to the individual patch names.
4.
Continue the Software Update application.
8 Postapplication Considerations
This section describes postapplication considerations for OracleAS 10g Release 2 Patch
Set 3. It contains the following topics:
Section 8.1, "Perform a Complete Backup"
Section 8.2, "Update File Permissions"
Section 8.3, "Re-application of the OracleAS 10g Release 2 Patch Set 3"
Section 8.4, "Restart OracleAS Metadata Repository Processes in Distributed

Environment"
Section 8.5, "Configuration Assistant Log Files"
Section 8.6, "Directories and Files Backed up by Oracle Universal Installer"
Section 8.7, "Applying Patch 4700543 for OracleAS Web Cache"
8.1 Perform a Complete Backup

It is necessary to perform a complete backup of your Oracle Application Server
environment after applying the patch set. Earlier backups will not work with the
updated Oracle Application Server Backup and Recovery Tool.
55
8.2 Update File Permissions

After applying OracleAS 10g Release 2 Patch Set 3, you need to update the file
permissions for the ORACLE_HOME/sso/bin/ssoreg.sh file. The following is an
example of the command:
chmod ug+x ORACLE_HOME/sso/bin/ssoreg.sh
8.3 Re-application of the OracleAS 10g Release 2 Patch Set 3

During re-application of OracleAS 10g Release 2 Patch Set 3, the Available Product
Components screen is displayed. To continue with patch application, you must
expand the component tree and manually select all of the components for patch
re-application. Failure to do so will prevent successful re-application of OracleAS 10g
Release 2 Patch Set 3.
8.4 Restart OracleAS Metadata Repository Processes in Distributed

Environment
If you have a distributed environment with an Infrastructure with Oracle Internet
Directory and OracleAS Metadata Repository on one computer, computer1, and an
infrastructure with OracleAS Metadata Repository on another computer, computer2,
then you should restart the processes on the computer2 after applying the patch sets.
The following steps describe how to restart the processes on computer2:
1.
Start the Net Listener as follows:

-
For UNIX:
ORACLE_HOME/bin/lsnrctl start
For Windows:
ORACLE_HOME\bin\lsnrctl start
2.
Start the OracleAS Metadata Repository instance as follows:

-
For UNIX:
ORACLE_HOME/bin/sqlplus /nolog
SQL> startup
SQL> quit
For Windows:
ORACLE_HOME\bin\sqlplus /nolog
SQL> startup
SQL> quit
8.5 Configuration Assistant Log Files

The locations for specific Oracle Application Server configuration assistant log files are
described in the Oracle Application Server Installation Guide.
56
8.6 Directories and Files Backed up by Oracle Universal Installer

Table 5 lists the OracleAS Portal directories backed up by Oracle Universal Installer
during installation of OracleAS 10g Release 2 Patch Set 3.
Table 5
OracleAS Portal Directories Backed up by Oracle Universal Installer
From
To
ORACLE_HOME/j2ee/OC4J_
Portal/applications/jpdk/jpdk/
htdocs
Portal.timestamp/applications/jpd
k/jpdk/htdocs
Portal/applications/jpdk/jpdk/
WEB-INF
k/jpdk/WEB-INF
Portal/application_
deployments/jpdk
Portal.timestamp/application_
deployments/jpdk
Portal/applications/jpdk/pdkst
ruts/htdocs
k/pdkstruts/htdocs
Portal/applications/jpdk/pdkst
ruts/WEB_INF
k/pdkstruts/WEB_INF
Portal/applications/portalTool
s/providerBuilder/WEB-INF
Portal.timestamp/applications/por
talTools/providerBuilder/WEB-INF
s/omniPortlet/WEB-INF
talTools/omniPortlet/WEB-INF
s/omniPortlet/plugins
talTools/omniPortlet/plugins
s/webClipping/WEB-INF
talTools/webClipping/WEB-INF
ORACLE_HOME/portal/conf
ORACLE_HOME/portal.timestamp/conf
Table 6 lists the OracleAS Portal files backed up by Oracle Universal Installer during
installation of OracleAS 10g Release 2 Patch Set 3:
Table 6
OracleAS Portal Files Backed up by Oracle Universal Installer
From
To
ORACLE_
HOME/portal/pdkjava/providerGr
oups/iasProviders.xml
ORACLE_
HOME/portal.timestamp/pdkjava/pro
viderGroups/iasProviders.xml
ORACLE_
HOME/portal/jlib/portaltools.j
ar
ORACLE_
HOME/portal.timestamp/jlib/portal
tools.jar
Portal/applications/portal/por
tal/WEB-INF/web.xml
portal.timestamp/applications/por
tal/portal/WEB-INF/web.xml
57
8.7 Applying Patch 4700543 for OracleAS Web Cache

If you are using OracleAS Web Cache with SSL enabled, then you must download and
apply patch 4700543 on top of Oracle Database 10.1.0.5 after you apply OracleAS 10g
Release 2 Patch Set 3. This patch is available from OracleMetaLink at
The fix of OracleAS Web Cache bug 4503759, which is included in OracleAS 10g
Release 2 Patch Set 3, requires the fix of network bug 4700543. If patch 4700543 is not
applied, then Internet Explorer 6.0 will not be able to access OracleAS Web Cache with
SSL enabled.
9 Known Issues
This section contains known issues in the product and documentation for OracleAS
10g Release 2 Patch Set 3. The content is organized as follows:
Section 9.1, "General Oracle Application Server Issues"
Section 9.2, "Error Messages You May Encounter"
Section 9.3, "Using Oracle Real Application Clusters Database with OracleAS
Disaster Recovery"
Section 9.4, "Oracle Real Application Clusters Database with OracleAS Disaster
Recovery Issues"
Section 9.5, "Oracle Business Intelligence"
Section 9.6, "Oracle Business Intelligence Issues and Workarounds"
Section 9.7, "OracleBI Discoverer Support for OracleAS Single Sign-On in an

Oracle E-Business Suite Environment Issues"
Section 9.8, "Oracle Business Intelligence Spreadsheet Add-In Issues and
Workarounds"
Section 9.9, "Oracle Business Intelligence Discoverer Portlet Provider Issues"
Section 9.10, "Oracle Business Intelligence Discoverer Viewer Issues"
Section 9.11, "Oracle Application Server Portal Metadata Repository Upgrade in a

RAC Environment"
Section 9.12, "Oracle Application Server Portal and Upgrading Database
Repository to Release 11g"
Section 9.13, "Oracle Application Server Web Cache Issues"
Section 9.14, "Oracle Application Server Wireless Issues"
Section 9.15, "Cloning Issues"
9.1 General Oracle Application Server Issues

This section contains the following:
Section 9.1.1, "Platform-Independent Issues"
Section 9.1.2, "Windows Issues"
Section 9.1.3, "SPARC Issues"
58
9.1.1 Platform-Independent Issues

This section contains general Oracle Application Server issues applicable to all
supported platforms. It contains the following topics:
Section 9.1.1.1, "Port Ranges Incorrect for Oracle Application Server"
Section 9.1.1.2, "Modifying the ias.properties File"
Section 9.1.1.3, "Relinking Oracle Application Server Web Cache"
Section 9.1.1.4, "OracleAS Single Sign-On in Non-English Languages"
Section 9.1.1.5, "Oracle Internet Directory Configuration Failures"
Section 9.1.1.6, "Missing Oracle Management Agent Configuration Files"
Section 9.1.1.7, "Central Agent Not Displayed in Oracle Application Server Control
Console"
Section 9.1.1.8, "Incorrect Farm Name Returned"
Section 9.1.1.9, "Visigenics ORB3.4.0.0.0 Appears Under "New Installations""
Section 9.1.1.10, "Command Line Options Documented Incorrectly"
Section 9.1.1.11, "The emctl set password Command can be Run Without
Parameters"
Section 9.1.1.12, "Silent Upgrade is not Supported if Oracle Internet Directory is
Configured to use Port 389"
Section 9.1.1.13, "Incremental Midtier Upgrade is not Supported"
Section 9.1.1.14, "Non-ASCII Character Limitations in Oracle Portal"
Section 9.1.1.15, "Installing Interconnect EIS Adapter"
Section 9.1.1.16, "Start All Button does not Start OC4J Components Created by
User"
Section 9.1.1.17, "Inactive Oracle Application Server Instance does not Show Start
Time"
Section 9.1.1.18, "Application Server Control Allows the Creation of a JAZN User
with a Null Password"
Section 9.1.1.19, "Upgrading to Oracle Identity Management 10.1.4 leaves app_
registry Entry for Oracle Internet Directory invalid"
Section 9.1.1.20, "OracleBI Discoverer Fails to Discover RAC Database"
Section 9.1.1.21, "Application of OracleAS 10g Release 2 Patch Set 3 to Oracle
Collaboration Suite 10.1.2.2 may be Blocked on the Middle Tier"
Section 9.1.1.22, "Oracle Application Server Guard Required for Database Oracle
Home"
Section 9.1.1.23, "Using the Back Button on the Summary Screen Causes Validation
to Fail"
Section 9.1.1.24, "Patching Clustered Oracle HTTP Server Installation"
Section 9.1.1.25, "Error While Patching Middle Tier after Configuring
Components"
Section 9.1.1.26, "OracleAS Forms Services and WebUtil Raise Error FRM-40735"
59
9.1.1.1 Port Ranges Incorrect for Oracle Application Server

After applying the patch set, the following components will display incorrect port
numbers. The actual numbers have not changed.
Oracle Application Server Web Cache port numbers when viewing online help
and Oracle Enterprise Manager 10g. The displayed port numbers will in the 9000
range. The actual port numbers are in the 4000 range.
Oracle Enterprise Manager 10g Application Server Control Console port numbers
when viewing the port summary page in Application Server Control Console. The
displayed port range will be in the 18000 range. The actual port numbers are in the
1800 range.
9.1.1.2 Modifying the ias.properties File

Bug 4915423
If the Metadata Repository was installed by selecting Identity Management and
Metadata Repository option and deselecting all other components or the Metadata
Repository was not registered with Oracle Internet Directory before applying the
patch, then it is necessary to modify the ias.properties file. Make the following
change in the file:
Original line in file: InstallType=Infrastructure
Modified line in file: InstallType=Infrastructure_Meta
9.1.1.3 Relinking Oracle Application Server Web Cache

In certain circumstances, it may be necessary to relink OracleAS Web Cache to prevent
startup errors while loading shared libraries. The following commands show how to
relink OracleAS Web Cache:
cd ORACLE_HOME/webcache/lib
make -f ins_calypso.mk install
If the permissions were previously modified, then you will need to rerun the
webcache_setuser.sh script. After running the script, start OracleAS Web Cache
using Oracle Process Manager and Notification Server with the following command:
opmnctl startproc ias-component=WebCache
See Also: Oracle Application Server Web Cache Administrators Guide

for more information about the webcache_setuser.sh script.
9.1.1.4 OracleAS Single Sign-On in Non-English Languages

Bug 4143761
If you run OracleAS Single Sign-On in either forced authentication mode or use the
Global Inactivity Timeout feature with non-English languages, then you may see one
of the following messages in English on the log in page:
"Sign in as a different user"

"The user name submitted for authentication does not match the user name
present in the existing OracleAS Single Sign-On session"
This occurs because translation strings are not provided for non-English languages.
9.1.1.5 Oracle Internet Directory Configuration Failures
60
The Oracle Internet Directory patch configuration assistant has the classpath coded as
ORACLE_HOME/jlib/ldapjclnt9.jar instead of ORACLE_
HOME/jlib/ldapjclnt10.jar. This will cause the configuration assistant to fail. To
avoid this problem, do the following:
1.
Exit the Oracle Universal Installer.
2.
Modify the ORACLE_HOME/cfgtoollogs/configtoolCommands file as

follows:
a.
Locate the Oracle Internet Directory configuration assistant section of the file.
b.
Change the classpath so that ORACLE_HOME/jlib/ldapjclnt10.jar is

before ORACLE_HOME/jlib/ldapjclnt9.jar similar to the following
example.
-classpath
/apps/infra10/ldap/postcfg/oidca.jar:
/apps/infra10/jlib/javax-ssl-1_2.jar:
/app s/infra10/jlib/jssl-1_2.jar:
/apps/infra10/jlib/ldapjclnt10.jar:
/apps/infra10/j lib/ldapjclnt9.jar:
/apps/infra10/jlib/netcfg.jar:
.
.
.
3.
Set the ORACLE_HOME environment variable to point to the correct Oracle home
using the following command:
export ORACLE_HOME=/apps/infra10
4.
Set the LD_LIBRARY_PATH environment variable to point the correct Oracle

home using the following command:
export LD_LIBRARY_PATH=$ORACLE_HOME/lib32/:$ORACLE_HOME/lib
5.
Run the configToolCommands script using the following command:

./configToolCommands
9.1.1.6 Missing Oracle Management Agent Configuration Files

Bug 4861052
Oracle Management Agent included in this patch set is missing some configuration
fixes. All customers using this product should download the fix for the issue.
To obtain a fix for this issue, contact Oracle Support. You can access information about
technical support at:
9.1.1.7 Central Agent Not Displayed in Oracle Application Server Control Console
A newly-installed central agent is not automatically listed in the Central Management
section of the OracleAS Infrastructure tab of Oracle Application Server Control
Console. The following steps describe how to display the agent:
1.
Configure the new agent by clicking Configure on the Application Server Control
Infrastructure tab.
61
2.
Refresh your browser to update the page.
9.1.1.8 Incorrect Farm Name Returned

After applying OracleAS 10g Release 2 Patch Set 3 to the instance that is hosting the
repository, the dcmctl whichfarm command does not return the correct farm name.
9.1.1.9 Visigenics ORB3.4.0.0.0 Appears Under "New Installations"

When the Software Update is applied against a J2EE standalone version 9.0.4,
Visigenics ORB3.4.0.0.0, which is part of RDBMS, appears on the Summary Page under
"New Installations." This is a known issue and does not adversely affect product
functionality.
9.1.1.10 Command Line Options Documented Incorrectly
In the Oracle Application Server High Availability Guide and Oracle Application Server
Containers for J2EE User's Guide, command line options such as Java options, OC4J
options, and Java executables are defined as instance-specific parameters, and are
basically excluded from the common configuration in a DCM-managed OracleAS
cluster. However, this does not work by default so these command line options need to
be configured manually in the instspec.xmlfile:
1.
Edit ORACLE_HOME/opmn/conf/instspec.xml as follows:


<InstanceScopeItem target=
"/opmn/process-manager/ias-instance/ias-component/process-type/module-data/
category/data"/>
category/data[id='java-options']"/>
category/data[id='oc4j-options']"/>
category/data[id='java-bin']"/>
2.
If the Oracle Application Server instance is associated with an Oracle

Database-based farm, then you must also run the following command:
java -jar ORACLE_HOME/dcm/lib/dcm.jar registerplugin -f
ORACLE_HOME/opmn/conf/register.xml -o ORACLE_HOME
9.1.1.11 The emctl set password Command can be Run Without Parameters
Bug 5450118
The emctl set password command can be run without specifying any parameters.
If used in this manner, then the emctl set password command will prompt
(without echo) the user for the password, which can then be entered from the
command line.
62
9.1.1.12 Silent Upgrade is not Supported if Oracle Internet Directory is Configured to use Port
389
Bug 4907640
Silent upgrade to Oracle Application Server 10g Release 2 (10.1.2.0.0) is not supported
if Oracle Internet Directory is configured to listen on port 389.
9.1.1.13 Incremental Midtier Upgrade is not Supported
Bug 5475108 and 5480646
Incremental upgrades of your Oracle Application Server middle tier are supported
only if J2EE and Web Cache are not upgraded to 10.1.2.3.0. For example:
If you install J2EE and Web Cache, then upgrade this middle tier with Business
Intelligence and Forms, then you can apply OracleAS 10g Patch Set 3 (10.1.2.3.0)
on this middle tier.
If you install J2EE and Web Cache and upgrade it to 10.1.2.3.0, then upgrade this
middle tier with Business Intelligence and Forms, OracleAS 10g Patch Set 3
(10.1.2.3.0) is not supported.
9.1.1.14 Non-ASCII Character Limitations in Oracle Portal

Bug 5516952
In some non-ASCII character set environments, you cannot use the Browse Users or
Browse Groups list of values to retrieve user or group data.
As a workaround, you can directly enter the user or group name that you want to
modify.
9.1.1.15 Installing Interconnect EIS Adapter
Bug 4912998
Before installing Interconnect EIS adapter, you must manually update the ORACLE_
HOME/opmn/conf/opmn.xml file as follows:
1.
Locate the following section in the opmn.xml file:

<ias-component id="InterConnect" status="enabled">
<environment>
<variable id="CLASSPATH"
value="ORACLE_HOME/integration/interconnect/lib/oai.jar"
append="true"/>
2.
Insert the line shown below in bold font. This will include iwoic.jar in the
CLASSPATH.
<ias-component id="InterConnect" status="enabled">
<environment>
value="ORACLE_HOME/integration/interconnect/lib/iwoic.jar"
append="true"/>
value="ORACLE_HOME/integration/interconnect/lib/oai.jar"
append="true"/>
3.
Save your changes to the opmn.xml file.
After making this change, you can install and start Interconnect EIS adapter.
63
9.1.1.16 Start All Button does not Start OC4J Components Created by User
Bug 5572460
The Start All button on cluster page fails to start OC4J components created by the user
if these components are in a cluster under a file-based farm.
The workaround is to access and start the OC4J components from Enterprise Manager.
9.1.1.17 Inactive Oracle Application Server Instance does not Show Start Time
Bug 5572417
If you have multiple Oracle Application Servers installed on a single host and
configured to listen through single Application console URL (Collapsed mode), and
you click on the inactive Oracle Application Server from the Application Server
Control Console, then no start time appears in the Start Time column for the
Management component listed in the System Components table.
This is because the inactive Application Server Control is not running and has not
been started.
9.1.1.18 Application Server Control Allows the Creation of a JAZN User with a Null Password
Application Server Control allows creation of a JAZN user with a null password. If
you create a JAZN user with the null password, then you should delete that user, and
create a new user that has a password. Having a user with a null password creates an
environment that is not secure.
9.1.1.19 Upgrading to Oracle Identity Management 10.1.4 leaves app_registry Entry for Oracle
Internet Directory invalid
Bug 5553539
After upgrading OracleAS 10g Release 2 Patch Set 3 to Oracle Identity Management
10.1.4, the status of the PL/SQL package RIDELPLG and app_registry entry for Oracle
Internet Directory will show as invalid.
The workaround is to run the RDBMS utility utlrp.sql immediately after
upgrading. This will validate the RIDELPLG package; however, the app_registry entry
for Oracle Internet Directory will still show as invalid.
9.1.1.20 OracleBI Discoverer Fails to Discover RAC Database
Bug 5596170
OracleBI Discoverer fails to discover a database instance if the database is a Real
Applications Cluster database.
To workaround this problem, use the add instance command to manually add this
database instance to the topology.
9.1.1.21 Application of OracleAS 10g Release 2 Patch Set 3 to Oracle Collaboration Suite 10.1.2.2
may be Blocked on the Middle Tier
Bug 5606858
If you installed Oracle Collaboration Suite 10.1.2.2 and try to apply OracleAS 10g
Release 2 Patch Set 3 to its middle tier, then patch application may be blocked and
displaying an error message similar to the following:
OC4J Home instance must be started.
64
To work around this problem, enable the OC4J home instance in Oracle Enterprise
Manager before installing OracleAS 10g Release 2 Patch Set 3 over the Oracle
Collaboration Suite middle tier.
9.1.1.22 Oracle Application Server Guard Required for Database Oracle Home
Bug 5610659
Oracle Application Server Guard 10.1.2.2.0 standalone kit is available on Oracle
Technology Network:
http://www.oracle.com/technology/
This kit must be installed on your database Oracle Home directory so that the database
is included in the topology.
9.1.1.23 Using the Back Button on the Summary Screen Causes Validation to Fail
Bug 5597727
Once you have reached the Summary screen during the patch application process,
using the "Back" button on the Summary screen and then returning to the Summary
screen will cause the component validations to fail.
To work around this issue, you must start up the components and processes in the
Oracle Home, such as Oracle Internet Directory, and database, so that the validation
succeeds.
9.1.1.24 Patching Clustered Oracle HTTP Server Installation
If you have installed Oracle HTTP Server in cluster mode from the Oracle Database
10.2 Companion CD, then you cannot apply this patch set to the clustered node. You
can apply this patch set to standalone Oracle HTTP Server installations.
9.1.1.25 Error While Patching Middle Tier after Configuring Components
While applying the Software Update to Oracle Business Intelligence, a window may
appear with the following message:
Certain files which need to be re-installed by Oracle Universal installer are
being used by one or more applications.Please close any running applications
before continuing."
If you received this message, then you will need to stop Oracle Universal Installer,
restart the machine, and apply the patch again.
9.1.1.26 OracleAS Forms Services and WebUtil Raise Error FRM-40735
If you encounter error "FRM-40735: WHEN_CUSTOM_ITEM_EVENT trigger raised
unhandled exception ORA_06508," then recompile or resave webutil.pll and
restart your form.
9.1.2 Windows Issues

This section contains general Oracle Application Server issues specific to Windows
platforms. It contains the following topics:
Section 9.1.2.1, "Using an F5 Load Balancer for Monitoring Oracle Internet

Directory"
65
Section 9.1.2.2, "Oracle Enterprise Manager 10g Web Service not Completely
Terminated"
Section 9.1.2.3, "Redeploying an Application Fails in Oracle JDeveloper"
Section 9.1.2.4, "Must Disable Internet Protocol Version 6"
Section 9.1.2.5, "Windows Native Authentication Fails"
Section 9.1.2.6, "OracleAS Forms Services Stop Responding when Exiting"
Section 9.1.2.7, "GET_WINDOW_PROPERTY Returns 0 on Microsoft Windows"
9.1.2.1 Using an F5 Load Balancer for Monitoring Oracle Internet Directory

Bug 4047709
If you use an F5 load balancer to monitor Oracle Internet Directory on a Microsoft
Windows 2000 system, then configure the load balancer to use LDAP protocol to
monitor Oracle Internet Directory.
9.1.2.2 Oracle Enterprise Manager 10g Web Service not Completely Terminated
Bug 3843269
The Oracle Enterprise Manager 10g Web service is stopped using net stop
servicename. The return of the command indicates that the service has exited
successfully. However, the service may not always completely terminate.
There are four processes involved in the Oracle Enterprise Manager 10g Web service:
nmesrvc.exe (the service driver)
emagent.exe (the EM Agent)
java.exe (the OC4J instance for Application Server Control)
perl.exe (which controls the watchdog Perl script)
When you are unable to completely stop the Oracle Enterprise Manager 10g Web
service, it is because the nmesrvc.exe process has not terminated. The service
continues running although none of the associated processes are up and running.
Because the nmesrvc.exe process is running, the nmesrvc.exe file cannot be
overwritten during application of OracleAS 10g Release 2 Patch Set 3.
The following steps describe how to determine whether the net stop servicename
is working:
1.
Open a DOS window.
2.
Stop Oracle Enterprise Manager 10g Web service using the following command:
net stop servicename
3.
Check the exit status for the command.
If the nmesrvc.exe process is still active after completing the preceding steps, then
do the following steps:
1.
Select Administrative Tools from the Control Panel.
2.
Select Services from the Administrative Tools.
3.
Locate the Oracle<oracleHome>ASControl process in the Services windows.
4.
Set the process to manual startup.
66
5.
Restart your computer and restart application of the OracleAS 10g Release 2 Patch
Set 3.
9.1.2.3 Redeploying an Application Fails in Oracle JDeveloper

Bug 5616954
If you are deploying an application with Oracle JDeveloper such that the EAR file
contains multiple WAR files that have profile dependencies, redeployment of that
application will fail if you access the application. For example:
1.
Deploy the application from Oracle JDeveloper.
2.
Run the application (for example, access the applications URL with a browser).
3.
Deploy the application again from Oracle JDeveloper.

The redeployment of the application will fail.
To work around this issue, stop and restart Oracle Application Server Containers for
J2EE (OC4J), then redeploy the application.
9.1.2.4 Must Disable Internet Protocol Version 6
By default, Internet Protocol version 6 (IPv6) is enabled for the Microsoft Windows
Vista operating system. IPv6 does not work with Oracle Application Server 10g
Release 2 (10.1.2), so it must be disabled. The following procedure describes how to
disable IPv6:
1.
Remove or comment out the following line in

C:\Windows\System32\drivers\etc\hosts file:
::1 localhost
2.
Deselect IPv6 for all your connections and adapters, using the Network
Connection Properties page. The page is available from Control Panel.
3.
Open the Registry Editor.
4.
Go to the HKEY_LOCAL_
MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\Disabled
Components directory.
5.
Add the registry entry DWORD and set the value to 0xFF.
6.
Exit the Registry Editor.
7.
Restart the computer.
9.1.2.5 Windows Native Authentication Fails

Windows Native Authentication (WNA) fails when using WNA with a release of JDK
later than 1.4.2_13. To avoid this problem, use JDK release 1.4.2_13 or earlier. For
information about downloading and applying JDK release 1.4.2_13, refer to
OracleMetaLink Note 469747.1.
9.1.2.6 OracleAS Forms Services Stop Responding when Exiting
OracleAS Forms Services stop responding when exiting a form, if the Forms Runtime
has started a JVM controller. Restarting the form correct the issue.
9.1.2.7 GET_WINDOW_PROPERTY Returns 0 on Microsoft Windows
67
GET_WINDOW_PROPERTY(FORMS_MDI_WINDOW,WINDOW_HANDLE) returns
zero even with separateframe=true. Oracle Forms Online Help states that this should
work on windows platform. This is incorrect as this Built-in does not support MDI.
9.1.3 SPARC Issues

This section contains general Oracle Application Server issues specific to SPARC
platforms. It contains the following topics:
Section 9.1.3.1, "GNU Tar is Required for ASG Clone Topology or Clone Instance
Operations"
Section 9.1.3.2, "Absolute Paths Required for System Calls in .cshrc File"
Section 9.1.3.3, "System Prompts for Oracle JDeveloper Path"
9.1.3.1 GNU Tar is Required for ASG Clone Topology or Clone Instance Operations
Bug 5590680
When using the ASG clone topology or clone instance operations, the tar utility is
utilized. The target systems of these operations must have a version of GNU tar in the
default PATH of the system user account in which the standalone ASG install runs.
GNU tar can be obtained at the following location:
http://www.gnu.org/software/tar/
9.1.3.2 Absolute Paths Required for System Calls in .cshrc File

Bug 5577412
If you make system calls to hostname, uname, or stty (as examples) in your .cshrc
file, then use absolute paths. For example:
/usr/bin/hostname
/use/bin/unanme
/usr/bin/stty
If you do not use the absolute path, then you may see core dump messages like the
following:
hostname: Command not found
Segmentation Fault (core dumped)
stty: : Invalid argument
uname: Command not found
You may see a core dump message for uname after making the change. This message is
harmless and can be ignored.
9.1.3.3 System Prompts for Oracle JDeveloper Path
When applying the patch on Solaris Operating System 8 (5.8), you will see the
following message:
Type the full pathname of a J2SE installation (or Ctrl-C to quit), the path will
be stored in ~/.jdev_jdk?
68
Error: Java home /bin/java is not a J2SE SDK.

Running Oracle9i JDeveloper under a JRE is not supported.
If the Java VM specified by the SetJavaHome is actually a full J2SDK installation
then add 'SetSkipJ2SDKCheck true' to the jdev.conf configuration file
Enter the full path to Oracle JDeveloper Kit (JDK). The path will be added to the jdev_
jdk file.
9.2 Error Messages You May Encounter

This section describes some error messages you may encounter while working with
OracleAS 10g Patch Set 3 (10.1.2.3.0). Where applicable, workarounds are also
described.
Section 9.2.1, "Fatal Error when Upgrading Oracle Identity Management"
Section 9.2.2, "Error Messages when Applying Patch to Infrastructure"
Section 9.2.3, "Error Messages when Applying Patch to Middle Tier"
Section 9.2.4, "Error Message when Applying Patch to Oracle Wireless"
Section 9.2.5, "Error Message when Applying Patch over Portal 10.1.4.0.0"
Section 9.2.6, "Error Message when Re-Applying OracleAS 10g Release 2 Patch Set
3"
Section 9.2.7, "Error Messages after Applying OracleAS 10g Release 2 Patch Set 3"
Section 9.2.8, "Error Message after Cancelling Patch Application"
Section 9.2.9, "Error Message During Incremental Installation"
Section 9.2.10, "Error Message During Deinstallation"
Section 9.2.11, "Servlet Error when Restarting Infrastructure"
Section 9.2.12, "Error Message from Portal Targets in Enterprise Manager"
Section 9.2.13, "Error Message From ASG Clone Instance Operation When
Performing a Node Backup"
Section 9.2.14, "Error Message When Running Reports Request with
destype=oracleportal"
Section 9.2.15, "Error Message When Running Oracle BPEL"
Section 9.2.16, "Error Message when Applying OracleAS 10g Release 2 Patch Set 3
on an Oracle Developer Suite Oracle Home (Windows Only)"
Section 9.2.17, "Error Message when Applying OracleAS 10g Release 2 Patch Set 3
on an Oracle B2B Configuration (Windows Only)"
Section 9.2.18, "Error Message when Applying OracleAS 10g Patch Set 3
(10.1.2.3.0) on Developer Kits (Windows Only)"
9.2.1 Fatal Error when Upgrading Oracle Identity Management

If you upgrade Oracle Identity Management from Oracle Application Server release
9.0.4 to Oracle Application Server 10.1.2.0.2 where the database version is already
upgraded to version 10.2.x.x, then "DBMS_IAS_VERSION package Configuration
Assistant" will throw the following error:
69
Output generated from configuration assistant "DBMS_IAS_VERSION package

Configuration Assistant":
Database Version is 10.2.0.1.0
Fatal Error: database version is 10.2.0.1.0. Please upgrade database to 9.2. or
10.1. before running this script.
To avoid this error, you must load the latest version of rdbmsloadversion.jar in
the ORACLE_HOME/jlib directory and run "DBMS_IAS_VERSION package
Configuration Assistant." The latest version of rdbmsloadversion.jar is available
from patch 4687475 from OracleMetaLink.
9.2.2 Error Messages when Applying Patch to Infrastructure

The following error messages when applying the patch to the infrastructure:
The following error message may appear in the Oracle Universal Installer logs
(.log and .out) when applying the patch to the infrastructure:
Error: can not append, there is a same named process type element in the
existing ias-instance.ias-component
This error can be ignored.
If you are applying the software patch to an Oracle Home containing only an
Infrastructure or only Identity Management, you may see the following error
message:
Unable to write to file oranldap10.dll
To avoid this problem, make sure you exit out of all SQL*Plus sessions in this
Oracle Home before you attempt to apply the patch.
The following error message may appear when applying the patch to the
Metadata Repository or Identity Management installation:
Exception thrown from action: removeFile
Exception Name: FileNotFoundException
Exception String: File not found C:\WORK\mr5113\lib\libagtsh.so
Exception Severity: 2
Starting install Install Phase 1 of component New Database ID Patch
The following error may appear in the opmn_status.log file:

Start output from spawned process:
---------------------------------opmnctl: opmn is already running
start status 0
opmnctl: starting opmn managed processes...
The following error about file size mismatching may appear in the installation log:
/scratch/iasinst/DevSuiteHome_1/forms/lib32/ui10.o
/scratch/iasinst/DevSuiteHome_1/forms/lib32/uiicxd.o \
-lig -ligo -lipg -lipc -liplsd -lic -licg -lig -ligo -lifg -lifc
-lijc -liwg -liwc -liwg -liwc -lidg -lidl -lid2 -lid1 -lit -litg
-lig -ligo -limg -limc -lipg -lipc -lifc -lijc -liwc -liplsd -lidg
-lihm -lic -licg -lsosd -limg -limc -liic -lic -licg
-lioc
\
-lnn -lobx -lzrc
-lvgs -lde -lucol
-lca
-luicc -lmma -lmmiw
70
-lmmov -lmma -lmmos -lmmoi

-lmmia -lmmft -lmmcm
-luihx -luc -luipr
-luimotif -lot -lrem -lree -lrec -luiimg -luimotif -luipr -luiimg -luc -lrem
-luimotif -luia -ltknqap -luipr -luimotif -lutt -lix -lixd -lix -lixd -lrod
-lror -lros -lrod -lror -lros -lrod -ldfc -luat -lutc -lutj -lutl -lutsl
-lpls10 -lplp10 -lplc10 -lpls10 -lplp10 -lslax10 -lsql10 -lthread -lclntsh
`cat /scratch/iasinst/DevSuiteHome_1/lib32/ldflags`
-lnsslb10 -lncrypt10
-lnsgr10 -lnzjs10 -ln10 -lnnz10 -lnl10 -lnro10 `cat
/scratch/iasinst/DevSuiteHome_1/lib32/ldflags`
-lnsgr10 -lnzjs10 -ln10 -lnnz10 -lnl10 -lclient10 -lnnetd10 -lvsn10
-lcommon10 -lgeneric10 -lmm -lcore10 -lxml10 -lunls10 -lsnls10 -lnls10
-lcore10 -lnls10 `cat /scratch/iasinst/DevSuiteHome_1/lib32/ldflags`
-lnsslb10 -lncrypt10 -lnsgr10 -lnzjs10 -ln10 -lnnz10 -lnl10 -lnro10 `cat
/scratch/iasinst/DevSuiteHome_1/lib32/ldflags`
-lnsgr10 -lnzjs10 -ln10 -lnnz10 -lnl10 -lclient10 -lnnetd10 -lvsn10
-lcommon10 -lgeneric10
-lcore10 -lxml10 -lunls10 -lsnls10 -lnls10
-lcore10 -lnls10 -lclient10 -lnnetd10 -lvsn10 -lcommon10 -lgeneric10
-lcore10 -lxml10 -lunls10 -lsnls10 -lnls10 -lcore10 -lnls10
`cat
/scratch/iasinst/DevSuiteHome_1/lib32/sysliblist` -R
/opt/SUNWcluster/lib:/scratch/iasinst/DevSuiteHome_1/lib32:/opt/ORCLcluster/li
b/ -Y P,:/opt/SUNWcluster/lib:/opt/ORCLcluster/lib/:/usr/ccs/lib:/usr/lib
-Qy -lc -laio
-lm /scratch/iasinst/DevSuiteHome_1/lib32/WS6U2/lib/crtn.o
-lsnls10 -ljvm
-L/usr/dt//lib -Bdynamic -lXm -lgen -L/usr/openwin/lib/
-R/usr/openwin/lib/ -lXt -lX11 -lw -lm
ld: warning: symbol ùiicxda' has differing sizes:
(file /scratch/iasinst/DevSuiteHome_1/forms/lib32/uiicxd.o value=0x81e0;
file /scratch/iasinst/DevSuiteHome_1/lib32//libuimotif.so value=0xe00);
/scratch/iasinst/DevSuiteHome_1/forms/lib32/uiicxd.o definition taken
ld: warning: symbol ùi1010' has differing sizes:
(file /scratch/iasinst/DevSuiteHome_1/forms/lib32/ui10.o value=0x80; file
/scratch/iasinst/DevSuiteHome_1/lib32//libuimotif.so value=0x64);
/scratch/iasinst/DevSuiteHome_1/forms/lib32/ui10.o definition taken
ld: warning: symbol ùi1011' has differing sizes:
(file /scratch/iasinst/DevSuiteHome_1/forms/lib32/ui10.o value=0x36; file
/scratch/iasinst/DevSuiteHome_1/lib32//libuimotif.so value=0x64);
/scratch/iasinst/DevSuiteHome_1/forms/lib32/ui10.o definition taken
9.2.3 Error Messages when Applying Patch to Middle Tier

The following error messages may appear in the Oracle Universal Installer logs or at
the command prompt when applying OracleAS 10g Release 2 Patch Set 3 to the middle
tier:
In the .err and .log files:

chmod: WARNING: can't access
/private/AS10121PatchInstalls/AS1012MT/ldap/odi/conf/profiles.lst
chmod: WARNING: can't access
/private/AS10121PatchInstalls/AS1012MT/ldap/odi/conf/srvWallet*
/private/AS10121PatchInstalls/AS1012MT/bin/bndlchk: /usr/bin/ar: not
found
/private/AS10121PatchInstalls/AS1012MT/bin/bndlchk: /usr/bin/ar: not
found
In the .log file:

*** Install Page***
Starting install Install Phase 1 of component Oracle Universal Installer
Dependent component failed to install before this phase
:oracle.swd.oui.core,
71
10.1.0.4.0, >0.0.0.0.0, [ 453 ][OH:2]

Skipping component :oracle.swd.oui, 10.1.0.4.0, >0.0.0.0.0, [ 453 ][OH:2]
Has completed the interview phase false
Starting install Install Phase 1 of component Oracle One-Off Patch
Installer
:oracle.swd.oui.core,
10.1.0.4.0, >0.0.0.0.0, [ 453 ][OH:2]
Skipping component :oracle.swd.opatch, 10.1.0.4.0, >0.0.0.0.0,
[ 453 ][OH:2]
Has completed the interview phase false
At the command prompt:

ERROR emSDK.config - oracle.sysman.emSDK.conf.TargetAdditionException:
@ Target[oracle_integic,co4718.example07.us.example.com_IC_Instance] already
present in /scratch/example/installs/auto_work/co4718/sysman/emd/targets.xml
example.sysman.emSDK.conf.TargetAdditionException: @ Target[oracle_
integic,co4718.example07.us.example.com_IC_Instance] already present in
/scratch/example/installs/auto_work/co4718/sysman/emd/targets.xml
at example.sysman.emSDK.conf.TargetInstaller.addTargetInt(TargetInstaller.java:
114 8)at example.sysman.emSDK.conf.TargetInstaller.addTargetFromFile
(TargetInstaller.jav a:1075)
at example.sysman.emSDK.conf.TargetInstaller.main(TargetInstaller.java:3669)
Warning: more than one process-type Element in the snippet. only the 1st one
is appended Error: can not append,there is a same named process type element in
the exisitng ias-instance.ias-component
All of these error messages can be ignored.
9.2.4 Error Message when Applying Patch to Oracle Wireless

Bug 4612167
The following error messages may appear in the upgrade_CA.out log when
applying the patch to the OracleAS Portal and Wireless home and the OracleAS
Wireless Configuration Assistant is running:
SQL Exception : java.sql.BatchUpdateException: error occurred during
batching: ORA-01430: column being added already exists in table
These error messages can be ignored if you are upgrading from a release 2 (10.1.2)
instance, such as one that has not been upgraded from Oracle9i Application Server
(Oracle9iAS) 9.0.2.x or 9.0.3.x, or Oracle Application Server 10g (9.0.4.x).
9.2.5 Error Message when Applying Patch over Portal 10.1.4.0.0

Bug 5502911
After applying OracleAS 10g Release 2 Patch Set 3 over Portal 10.1.4.0.0, the following
error appears in the log files:
NOTE : Portal Configuration Assistant (OPCA) has detected that the version of
Portal repository to which the language install was targeted is different than the
version of the Portal midtier. Portal language install between different versions
72
is not supported. OPCA has skipped this language install.
There are two workarounds for this issue:
Install all your required languages before applying OracleAS 10g Release 2 Patch
Set 3.
Do the following procedure:
1.
Download patch 8977866 from OracleMetaLink.
2.
Mount the Portal release 10.1.4.0.0 MRUA CD-ROM or shiphome.
3.
Copy the entire contents from the CD-ROM to a local directory, such as
MRUA_COPY, with write privileges or create symbolic or soft links to the
contents from MRUA_COPY directory except for the $MRUA_
HOME/assistants/opca/jlib directory.
4.
Create the assistants/opca/jlib directory under MRUA_COPY directory.
5.
Copy the opca.jar file from the patch $MRUA_

HOME/assistants/opca/jlib directory to MRUA_
COPY/assistants/opca/jlib.
6.
Run the ptllang.sh script from the MRUA_COPY/assistants/opca

directory to install languages in any Oracle Portal repository release 10.1.4.0.0
and later.
9.2.6 Error Message when Re-Applying OracleAS 10g Release 2 Patch Set 3
Bug 5488356
The following error will appear if you re-apply OracleAS 10g Release 2 Patch Set 3
over an Oracle Application Server Infrastructure that has already been updated with
OracleAS 10g Release 2 Patch Set 3:
error in writing to file "ORACLE_HOME/bin/extjob" permission denied.
The workaround is to change the ownership and group of the extjob.nobody file to
the user and group with which the installation is being performed, respectively.
9.2.7 Error Messages after Applying OracleAS 10g Release 2 Patch Set 3
Bugs 5452850 and 5474565
After applying OracleAS 10g Release 2 Patch Set 3 to one of the following existing
Oracle Application Servers:
Oracle Business Intelligence 10g Release 2 (10.1.2)
Oracle Business Intelligence 10g Release 2 (10.1.2.0.2)
The following error message is written to error file in the inventory directory:
stty: : Invalid argument
After applying OracleAS 10g Release 2 Patch Set 3 to Oracle Application Server 10g
Release 2 (10.1.2.0.0), the following error message is written to the log file:
:oracle.swd.opatch,10.1.0.4.0, >0.0.0.0.0, [ 912 ][OH:2]
73
These error messages can be ignored.
9.2.8 Error Message after Cancelling Patch Application

Bug 4912485
If you start applying OracleAS 10g Release 2 Patch Set 3, cancel it, and start applying it
again, then you may get the following error:
Error in moving the file
ORACLE_HOME\bin\oranldap10.dll" to ORACLE_HOME\bin\oranldap10.dll.old
To work around this problem, remove the .old file to continue applying the patch.
9.2.9 Error Message During Incremental Installation

Bug 4887988
If installing an incremental installation, such as incrementing from a J2EE installation
to Portal and Wireless installation, after applying OracleAS 10g Release 2 Patch Set 3,
then you may receive the following error:
Error in invoking target 'utitlities' of makefile
/private1/iasinst/Ora1012J2EE1/rdbms/lib/ins_rdbms.mk
The error can be ignored. Click Continue to proceed with the incremental installation.
After completing the installation, you must reapply OracleAS 10g Release 2 Patch Set 3
to the incremented installation.
9.2.10 Error Message During Deinstallation

Bug 4707427
During deinstallation of Oracle Application Server, the installer shows the status of the
deinstallation. Another window may appear stating the following:
Fatal exception occurred. Program will terminate.
You will be prompted to click OK. After clicking OK, the deinstallation process will
continue and be successful.
See Also: Oracle Application Server Installation Guide for more
information about performing a complete deinstallation
9.2.11 Servlet Error when Restarting Infrastructure

Bug 4899571
In an infrastructure failover scenario, or any scenario in which the infrastructure is
restarted, there may be a servlet error. To work around this issue, stop and restart
Oracle Process Manager and Notification Server on the middle tier using the following
commands:
MT_Home\opmn\bin\opmnctl stopall
MT_Home\opmn\bin\opmnctl startall
74
9.2.12 Error Message from Portal Targets in Enterprise Manager

Bug 5529235
PPE's application.log file will contain entries of the following error:
ERROR: Repository Gateway error: Database Error: ORA=1036 ORA-01036: illegal
variable name/number
The workaround is to remove the Portal target from the Enterprise Managers
targets.xml file and restart the Enterprise Manager. For more information about
removing Portal targets from the targets.xml file, please see Section B.1.3,
"Updating the Oracle Enterprise Manager 10g targets.xml File" in the Oracle Application
Server Portal Configuration Guide.
9.2.13 Error Message From ASG Clone Instance Operation When Performing a Node
Backup
Bug 5593308
ASG clone instance operation fails with the following errors when executing a node
backup:
@ asinfra:
@ asinfra:
@ asinfra:
@ asinfra:
failed.
-->ASG_SYSTEM-100:
-->ASG_SYSTEM-100:
-->ASG_SYSTEM-100:
-->ASG_SYSTEM-100:
Failure : prepare failed

cannot start dcm-daemon.
Status code:
Starting of the process dcm-daemon.dcm-daemon
The workaround is to increase the retry parameter value in the OPMN configuration
file for the dcm-daemon component's <start> operation. For example:
<start timeout="1200" retry="5" />
9.2.14 Error Message When Running Reports Request with destype=oracleportal

Bug 5611121
If you are running Oracle Reports requests with destype=oracleportal for
pushing the output to OracleAS Portal 10.1.4.1 will run into following error:
ORA-02291: integrity constraint (PORTAL.WWDOC_DOPA_FK) violated - parent key not
found
To work around this issue, you must apply patch 4575029.
9.2.15 Error Message When Running Oracle BPEL

Users of Oracle BPEL Developers Edition installation may get the following error
message when they click Visual Flow on Oracle BPELConsole:
"Error : Internal/Bug(# 106)"
element has no child: creation-date
OracleAS 10g Patch Set 3 (10.1.2.3.0) is not supported on Oracle BPEL Developers
Edition. User should use the middle tier installation for their production work.
9.2.16 Error Message when Applying OracleAS 10g Release 2 Patch Set 3 on an Oracle
Developer Suite Oracle Home (Windows Only)
Bug 5478713
75
If you have a machine where both Oracle Application Server and Oracle Developer
Suite are installed, you may encounter the following error message when applying
OracleAS 10g Release 2 Patch Set 3:
Certain files which needs to be reinstalled by Oracle
Universal Installer are being used by one or more running services.
This issue is due to the PATH environment variable have pointers to multiple Oracle
Home directories. The workaround for this issue is to:
1.
Modify your PATH environment variable and place the references to the Oracle
Developer Suite Oracle Home directory towards the end of the directory list.
2.
Restart the machine.
3.
Install OracleAS 10g Release 2 Patch Set 3 against the Oracle Developer Suite
Oracle Home directory.
9.2.17 Error Message when Applying OracleAS 10g Release 2 Patch Set 3 on an Oracle
B2B Configuration (Windows Only)
When applying the patch to an Oracle B2B configuration, you may encounter the
following error message in the error log:
D:\j2ee_b2b\ip\lib>%ORACLE_HOME%\perl\5.6.1\bin\MSWin32-x86\perl
%ORACLE_HOME%\ip\oem\edifecs\XEngineInstaller.pl
-d %ORACLE_HOME%\ip\oem\edifecs -s %ORACLE_HOME%\ip\oem\edifecs
Checking OS compatibility... OK
Checking XEngine version... OK
Checking distribution... [D:\j2ee_b2b\ip\oem\edifecs\package.ex_] OK
Reading destination:
Destination is D:\j2ee_b2b\ip\oem\edifecs
EDIFECS root is D:\j2ee_b2b\ip\oem\edifecs
.
Installing files:
Unpacking files
Delivering files
Done
.
Registering COM-servers:
Done
.
Setting environment variables... OK
D:\j2ee_b2b\ip\lib\setx.ex_' is not recognized as an internal or
external command,operable program or batch file.
D:\j2ee_b2b\ip\lib\setx.ex_' is not recognized as an internal or external
command,operable program or batch file.
D:\j2ee_b2b\ip\lib\setx.ex_' is not recognized as an internal or external
command,operable program or batch file.
Preparing configuration files... OK
Installation completed successfully!
The error message can be ignored.
9.2.18 Error Message when Applying OracleAS 10g Patch Set 3 (10.1.2.3.0) on
Developer Kits (Windows Only)
When applying the patch on an environment that has developer kits, you may
encounter the following error message in the error log:
Calling Action fileActions10.1.0.3.0
76
removeFile
selectedNodes = null
source = C:\OraHome_1\bin\orasrvmhas.dll
Exception
Exception
Exception
Exception
thrown from action: removeFile

Name: FileNotFoundException
String: File not found C:\OraHome_1\bin\orasrvmhas.dll
Severity: 2"
The error message can be ignored.
9.3 Using Oracle Real Application Clusters Database with OracleAS

Disaster Recovery
This section describes how to configure your OracleAS Disaster Recovery topology if
you are using a Real Application Clusters database for your OracleAS Metadata
Repository. You can use Real Application Clusters database on both your primary and
standby sites, or just on the primary site (the standby site uses a non-Real Application
Clusters database). The following subsections cover these cases:
Section 9.3.1, "Configuring OracleAS Disaster Recovery Where Both the Primary
and Standby Sites Use Oracle Real Application Clusters Databases"
Section 9.3.2, "Configuring OracleAS Disaster Recovery Where Only the Primary
Site Uses Oracle Real Application Clusters Database (Standby Site Uses a
Non-Real Application Clusters Database)"
9.3.1 Configuring OracleAS Disaster Recovery Where Both the Primary and Standby
Sites Use Oracle Real Application Clusters Databases
This section describes how to set up OracleAS Disaster Recovery in a topology where
both the primary and standby sites use Oracle Real Application Clusters database.
This section contains the following subsections:
Section 9.3.1.1, "Assumptions"
Section 9.3.1.2, "Configuration Procedure"
Section 9.3.1.3, "Switchover Procedure"
Section 9.3.1.4, "Switchback Procedure (for Switching Back to the Primary Site)"
Section 9.3.1.5, "Failover Procedure"
9.3.1.1 Assumptions Note the following assumptions:
Real Application Clusters software has been installed on both primary and
standby sites.
You need to install the standalone version of OracleAS Guard in the database
Oracle homes on all the Real Application Clusters nodes on the primary and
standby sites. The standalone version of OracleAS Guard can be found on Oracle
Application Server Companion CD Disk 2.
For instructions on how to run the standalone OracleAS Guard installer, see the
"Installing in High Availability Environments" chapter in the Oracle Application
Server Installation Guide for your platform.
The database on the standby site should be down, and the SID should be deleted.
These steps, which are described in Section 9.3.1.2, "Configuration Procedure", are
77
required before you can run the "create standby database" command later in the
procedure.
The database on the standby site will be overwritten by the "create standby
database" command.
Table 7 shows the host and database names that will be used in the steps below.
The procedure assumes a two-node Real Application Clusters on each site.
Table 7
Host and Database Names on the Primary and Standby Sites

Primary Site
Standby Site
Physical host names
prodnode1, prodnode2
standbynode1, standbynode2
Virtual host names
vracnode1, vracnode2
Database name
orcl.oracle.com
orcl.oracle.com
Database SID
orcl1 on prodnode1
orcl1 on standbynode1
orcl2 on prodnode2
The vracnode1 virtual hostname should be mapped to the machines IP address.

You set up this mapping in each machines hosts file. For example:
On the primary site, edit SystemRoot\system32\drivers\etc\hosts
(Windows) or /etc/hosts (UNIX) to add an entry similar to the following:
ip_address
prodnode1.domain.com
prodnode1
vracnode1.domain.com
vracnode1
On the standby site, edit the same hosts file to add an entry similar to the
following:
ip_address
vracnode1
standbynode1.domain.com
standbynode1
9.3.1.2 Configuration Procedure Perform the following steps to configure OracleAS

Disaster Recovery topologies where the primary and standby sites use Real
Application Clusters databases.
1.
Stop the Real Application Clusters database on the standby site and disable
automatic database restart using CRS.
> DBHOME/bin/srvctl stop database -d orcl
> DBHOME/bin/srvctl disable database -d orcl
2.
On standbynode1, delete the SID. If you do not delete the SID, you will get an
error when you run the "create standby database" command.
On Windows, run the oradim command to delete the Oracle SID:
> oradim -delete -sid orcl1
On UNIX, comment out the database SID/database name entry in the oratab file.
For Real Application Clusters databases, the entry in the oratab file has the
following format:
DBuniqueName:oracle_home
3.
On prodnode1, stop the Real Application Clusters database and disable automatic
database restart using CRS.
78

4.
Start up the database on prodnode1 only. Ensure that the database instances on the
other Real Application Clusters nodes are down. You must be logged in as a
member of the dba group in order to start the database.
> DBHOME/bin/sqlplus / as sysdba
SQL> startup
5.
On prodnode1, run the following ASGCTL commands to create a database on

standbynode1.
Some notes on the commands below:
The "create standby database" command overwrites your existing database of

the same name on standbynode1.
On UNIX, the "add instance" command uses orcl (the database name) to
locate the oratab entry.
On Windows, it uses orcl1 (the database SID) to locate the registry entry.
The "set primary database" and "create standby database" commands use
orcl (the database name) on UNIX, but on Windows they use orcl1 (the
database SID).
ASGCTL> connect asg prodnode1 ias_admin/<adminpwd>

ASGCTL> set trace on all
UNIX only: ASGCTL> add instance orcl on vracnode1
Windows only: ASGCTL> add instance orcl1 on vracnode1
ASGCTL> dump topology
ASGCTL> verify topology
ASGCTL> set noprompt
UNIX only: ASGCTL> set primary database sys/<passwd>@orcl
Windows only: ASGCTL> set primary database sys/<passwd>@orcl1
UNIX only: ASGCTL> create standby database orcl on standbynode1
Windows only: ASGCTL> create standby database orcl1 on standbynode1
ASGCTL> verify topology with standbynode1
ASGCTL> instantiate topology to standbynode1
6.
Propagate orcl_remote1 or orcl1_remote1 entries from prodnode1 to other nodes

on the primary site.
a.
Copy the orcl_remote1 (UNIX) or orcl1_remote1 (Windows) entries in

tnsnames.ora on prodnode1 to all the other Real Application Clusters nodes
On UNIX, the entry uses the database name (orcl), but on Windows it uses
the database SID (orcl1). A "_remote<n>" is appended to the name of the
entry, where <n> is a number.
In some cases, the <n> number will advance, and the _remote<n> entry
specified in the SERVICE attribute of the LOG_ARCHIVE_DEST_<n>
parameter needs to be propagated as well.
79
b.
On prodnode2, restart the listener using CRS:

> CRSHOME/bin/crs_stop ora.prodnode2.LISTENER_PRODNODE2.lsnr
> CRSHOME/bin/crs_start ora.prodnode2.LISTENER_PRODNODE2.lsnr
c.
Make sure that the standby database mentioned in the remote entry can be
pinged using TNS.
UNIX only: > tnsping orcl_remote1
Windows only: > tnsping orcl1_remote1
7.
On prodnode2, start up the database and create an spfile. You must be logged in as
a member of the dba group in order to start the database.
SQL> startup
UNIX only: SQL> create spfile='<ORADATASHAREDLOCATION>/orcl/spfileorcl.ora'
from pfile='<DBHOME>/dbs/initORCL2.ora';
Windows only: SQL> create spfile='<ORADATASHAREDLOCATION>\orcl\spfileorcl.ora'
from pfile='<DBHOME>/database/initORCL2.ora';
SQL> shutdown immediate;
You shut down the database because you will be starting up all the Real
Application Clusters instances.
8.
Shut down the single database instance running on prodnode1 because you will
be starting up all the Real Application Clusters database instances on the primary
site. You need all the instances to be running to perform a "sync topology"
command.
a.
Stop the database on prodnode1.

b.
Start up the Real Application Clusters database instances. You must be logged
in as a member of the dba group in order to start the database.
> srvctl enable database -d orcl
> srvctl start database -d orcl
9.
On prodnode1, run the ASGCTL "sync topology" command.

ASGCTL> connect asg ias_admin/<adminpwd>
ASGCTL> sync topology to standbynode1
9.3.1.3 Switchover Procedure This section describes how to run the ASGCTL switchover
command to switch from the primary site to the standby site to prepare for a
scheduled outage of the primary site.
After the scheduled outage is over, you can switch back to the primary site. See
Section 9.3.1.4, "Switchback Procedure (for Switching Back to the Primary Site)" for
details.
80
For unscheduled outages, you should perform the steps in Section 9.3.1.5, "Failover
Procedure" instead.
Procedure for switching over to the standby site for scheduled outages:
1.
On the primary site, stop the database and disable automatic database restart by
CRS because you will start up one database instance only. This is required for the
upcoming switchover operation.
On prodnode1, run the following commands:
> srvctl stop database -d orcl
> srvctl disable database -d orcl
Start up a single database instance on prodnode1. You must be logged in as a

SQL> startup
2.
On prodnode1, run the switchover command:

ASGCTL> switchover topology to standbynode1
ASGCTL> disconnect
If you see a "Primary database must be mounted exclusive" message in the

console, it means that more than one Real Application Clusters database instance
is running. See the previous step for instructions on how to start up only one
database instance.
3.
On standbynode1, shut down the orcl1 instance after the switchover.

4.
On standbynode1, modify parameters in the initorcl1.ora file.

a.
On standbynode1, make a backup copy of the file

DBHOME/dbs/initorcl1.ora (UNIX) or
DBHOME\database\initorcl1.ora (Windows). You will be editing the file
in the next step.
b.
Verify that these parameters in DBHOME/dbs/initorcl1.ora (UNIX) or

DBHOME\database\initorcl1.ora (Windows) are set to the following
values:
*.cluster_database_instances=2
*.cluster_database=TRUE
*.remote_listener='LISTENERS_ORCL'
c.
Copy initorcl1.ora from standbynode1 to the corresponding directory on

standbynode2 (DBHOME/dbs on UNIX, DBHOME\database on Windows).
d.
On standbynode2, rename the file to initorcl2.ora.
e.
On standbynode2, update the initorcl2.ora file to replace any

instance-specific parameters. For example, you would change these lines:
81
*.service_names=orcl1
*.instance_name=orcl1
to:
*.service_names=orcl2
*.instance_name=orcl2
5.
Propagate orcl_remote1 or orcl1_remote1 entries from standbynode1 to other Real

Application Clusters nodes on the standby site.
a.

tnsnames.ora on standbynode1 to all the other Real Application Clusters
nodes on the standby site.
b.
On standbynode2, restart the listener using CRS:

> CRSHOME/bin/crs_stop ora.standbynode2.LISTENER_STANDBYNODE2.lsnr
> CRSHOME/bin/crs_start ora.standbynode2.LISTENER_STANDBYNODE2.lsnr
c.
pinged using TNS.
6.
On standbynode2, start up the database, create an spfile, and shut down the
database. You must be logged in as a member of the dba group in order to start the
database.
SQL> startup;
UNIX only: SQL> create spfile='<ORADATASHAREDLOCATION>/orcl/spfileorcl.ora'
from pfile='<DBHOME>/dbs/initORCL2.ora';
Windows only: SQL> create spfile='<ORADATASHAREDLOCATION>\orcl\spfileorcl.ora'
from pfile='<DBHOME>/database/initORCL2.ora';
7.
On standbynode1, restart the Real Application Clusters database instances on the

standby site using CRS. You must be logged in as a member of the dba group in
order to start the database.
9.3.1.4 Switchback Procedure (for Switching Back to the Primary Site) When the scheduled
outage of the primary site is over, perform these steps to switch back to the primary
site.
82
Note that on the primary site, which is the site you want to switch back to, the Real
Application Clusters database should be up on one node only. To do this, you start it
up manually using SQL*Plus, instead of using CRS. This is shown in step 1 below.
This is because the "sync topology" command may need to run media recovery against
the database that you want to sync to (that is, prodnode1). Media recovery requires an
exclusive mount of the database.
1.
On the primary site, which is the site you want to switch back to, run the Real
Application Clusters database on one node only. In these steps, you run it on
prodnode1 only.
On prodnode1, start up a single database instance. You must be logged in as a

SQL> startup
2.
Sync the standby sites database to the primary sites database.

ASGCTL>
ASGCTL>
ASGCTL>
ASGCTL>
3.
connect asg standbynode1 ias_admin/<adminpwd>

verify topology with prodnode1
set trace on all
sync topology to prodnode1
On the standby site, stop all the database instances, disable automatic database
restart, and start the database on standbynode1 only. You must be logged in as a
SQL> startup
4.
On standbynode1, run the switchover command.

ASGCTL> connect asg standbynode1 ias_admin/<adminpwd>
ASGCTL> verify topology with prodnode1
ASGCTL> switchover topology to prodnode1
ASGCTL> disconnect
5.
On prodnode1, shut down the single database instance. You will start up all the
Real Application Clusters instances using CRS and perform a "sync topology".
> DBHOME\bin\sqlplus / as sysdba
> DBHOME\bin\srvctl enable database -d ORCL
> DBHOME\bin\srvctl start database -d ORCL
83
6.
Perform a "sync topology" command.

ASGCTL> disconnect
9.3.1.5 Failover Procedure This section describes the steps for failing over to the standby
site. Use these steps for unscheduled outages of the primary site. For scheduled
outages, see the steps in Section 9.3.1.3, "Switchover Procedure".
1.
On the standby site, run the failover command and activate it as the new primary
site.
UNIX only: ASGCTL> set new primary database sys/<passwd>@orcl
Windows only: ASGCTL> set new primary database sys/<passwd>@orcl1
ASGCTL> failover
ASGCTL> disconnect
2.
On the standby site, shut down the database and start it up using CRS. You must
be logged in as a member of the dba group in order to start the database.
> srvctl enable database -d rac
> srvctl start database -d rac
9.3.2 Configuring OracleAS Disaster Recovery Where Only the Primary Site Uses
Oracle Real Application Clusters Database (Standby Site Uses a Non-Real Application
Clusters Database)
This section describes how to set up OracleAS Disaster Recovery that uses Oracle Real
Application Clusters database on only the primary site. The standby site uses a
standard Oracle database.
This section contains the following subsections:
Section 9.3.2.1, "Assumptions"
Section 9.3.2.2, "Configuration Procedure"
Section 9.3.2.3, "Switchover Procedure"
Section 9.3.2.4, "Switchback Procedure"
Section 9.3.2.5, "Failover Procedure"
9.3.2.1 Assumptions Note the following assumptions:
84
Real Application Clusters software has been installed on the primary site.
You need to install the standalone version of OracleAS Guard in the database
Oracle homes on all the Real Application Clusters nodes on the primary site, and
on the database Oracle home on the standby site. The standalone version of
OracleAS Guard can be found on Oracle Application Server Companion CD Disk
2.
For instructions on how to run the standalone OracleAS Guard installer, see the
"Installing in High Availability Environments" chapter in the Oracle Application
Server Installation Guide for your platform.
The database on the standby site should be down, and the SID should be deleted.
These steps, which are described in Section 9.3.2.2, "Configuration Procedure", are
required before you can run the "create standby database" command later in the
procedure.
The database on the standby site will be overwritten by the "create standby
database" command.
Table 8 shows the host and database names that will be used in the steps below.
The procedure assumes a two-node Real Application Clusters on the primary site.
Table 8
Host and Database Names on the Primary and Standby Sites

Primary Site
Standby Site
Physical host names
prodnode1, prodnode2
standbynode1
Virtual host names
vracnode1
Database name
orcl.oracle.com
orcl.oracle.com
Database SID
orcl1 on prodnode1
orcl2 on prodnode2
The vracnode1 virtual hostname should be mapped to the machines IP address.

You set up this mapping in each machines hosts file. For example:
On the primary site, edit SystemRoot\system32\drivers\etc\hosts
(Windows) or /etc/hosts (UNIX) to add an entry similar to the following:
ip_address
prodnode1.domain.com
prodnode1
vracnode1
On the standby site, edit the same hosts file to add an entry similar to the
following:
ip_address
vracnode1
standbynode1.domain.com
standbynode1
9.3.2.2 Configuration Procedure Perform the following steps to configure your OracleAS
Disaster Recovery topology where the primary site uses a Real Application Clusters
database, but the standby site uses a non-Real Application Clusters database.
1.
Stop the Real Application Clusters database on the standby site.

2.
On standbynode1, delete the SID. If you do not delete the SID, you will get an
error when you run the "create standby database" command.
85
On Windows, run the oradim command to delete the Oracle SID:

> oradim -delete -sid orcl1
On UNIX, comment out the database SID/database name entry in the oratab file.
For non-Real Application Clusters databases, the entry in the oratab file has the
following format:
DBSID:oracle_home
3.
database restart using CRS. You must be logged in as a member of the dba group
in order to start the database.
4.
Start up the database on prodnode1 only. Ensure that the database instances on the
other Real Application Clusters nodes are down. You must be logged in as a
SQL> startup
5.
On prodnode1, run the following ASGCTL commands to create a database on

standbynode1.
Some notes on the commands below:
The "create standby database" command overwrites your existing database of

the same name on standbynode1.
On UNIX, the "add instance" command uses orcl (the database name) to
locate the oratab entry.
On Windows, it uses orcl1 (the database SID) to locate the registry entry.
The "set primary database" and "create standby database" commands use
orcl (the database name) on UNIX, but on Windows they use orcl1 (the
database SID).

UNIX only: ASGCTL> add instance orcl on vracnode1
Windows only: ASGCTL> add instance orcl1 on vracnode1
ASGCTL> dump topology
ASGCTL> verify topology
ASGCTL> set noprompt
UNIX only: ASGCTL> create standby database orcl on standbynode1
Windows only: ASGCTL> create standby database orcl1 on standbynode1
ASGCTL> instantiate topology to standbynode1
86
6.
Propagate orcl_remote1 or orcl1_remote1 entries from prodnode1 to other nodes

a.

tnsnames.ora on prodnode1 to all the other Real Application Clusters nodes
b.
On prodnode2, restart the listener using CRS:

> CRSHOME/bin/crs_stop ora.prodnode2.LISTENER_PRODNODE2.lsnr
> CRSHOME/bin/crs_start ora.prodnode2.LISTENER_PRODNODE2.lsnr
c.
pinged using TNS.
7.
Shut down the single database instance running on prodnode1 because you will
be starting up all the Real Application Clusters database instances on the primary
site. You need all the instances to be running to perform a "sync topology"
command.
a.
Stop the database on prodnode1.

b.
Start up the Real Application Clusters database instances. You must be logged
in as a member of the dba group in order to start the database.
8.
On prodnode1, run the ASGCTL "sync topology" command.

9.3.2.3 Switchover Procedure This section describes how to run the ASGCTL switchover
command to switch from the primary site to the standby site to prepare for a
scheduled outage of the primary site.
After the scheduled outage is over, you can switch back to the primary site. See
Section 9.3.2.4, "Switchback Procedure" for details.
For unscheduled outages, you should perform the steps in Section 9.3.2.5, "Failover
Procedure" instead.
87
Procedure for switching over to the standby site for scheduled outages:
1.
On the primary site, stop the database and disable automatic database restart by
CRS because you will start up one database instance only. This is required for the
upcoming switchover operation.
On prodnode1, run the following commands:
Start up a single database instance on prodnode1. You must be logged in as a

SQL> startup
2.
On prodnode1, run the switchover command:

ASGCTL> switchover topology to standbynode1
ASGCTL> disconnect
If you see a "Primary database must be mounted exclusive" message in the

console, it means that more than one Real Application Clusters database instance
is running. See the previous step for instructions on how to start up only one
database instance.
9.3.2.4 Switchback Procedure This section describes the steps for switching back to the
primary site when the scheduled outage is over.
Note that on the primary site, which is the site you want to switch back to, the Real
Application Clusters database should be up on one node only. To do this, you start it
up manually using SQL*Plus, instead of using CRS. This is shown in step 1 below.
This is because the "sync topology" command may need to run media recovery against
the database that you want to sync to (that is, prodnode1). Media recovery requires an
exclusive mount of the database.
1.
On the primary site, which is the site you want to switch back to, run the Real
Application Clusters database on one node only. In these steps, you run it on
prodnode1 only.
On prodnode1, start up a single database instance. You must be logged in as a

SQL> startup
2.
On standbynode1, run the following commands to switch back to the primary site:
88

ASGCTL> verify topology with prodnode1
ASGCTL> switchover topology to prodnode1
3.
On prodnode1, shut down the single database instance and start up all the Real
Application Clusters instances using CRS. All the instances need to be up for the
"sync topology" command. You must be logged in as a member of the dba group
in order to start the database.
> DBHOME\bin\srvctl enable database -d ORCL
> DBHOME\bin\srvctl start database -d ORCL
4.
Perform a "sync topology" command.

ASGCTL> disconnect
9.3.2.5 Failover Procedure This section describes the steps for failing over to the standby
site. Use these steps for unscheduled outages of the primary site. For scheduled
outages, see the steps in Section 9.3.2.3, "Switchover Procedure".
Run the failover command on the standby site and activate it as the new primary:
UNIX only: ASGCTL> set new primary database sys/<passwd>@orcl
Windows only: ASGCTL> set new primary database sys/<passwd>@orcl1
ASGCTL> failover
ASGCTL> disconnect
9.4 Oracle Real Application Clusters Database with OracleAS Disaster

Recovery Issues
This section describes issues related to highly available topologies using the OracleAS
Disaster Recovery solution.
The following topics are covered:
Section 9.4.1, "OracleAS Guard Returned an Inappropriate Message When It Could

Not Find the User Specified Database Identifier"
89
Section 9.4.2, "OracleAS Guard Add Instance Command Failed When Attempting
to Add an Oracle RAC Database to the Topology (Windows Only)"
Section 9.4.3, "OracleAS Guard Operations Do Not Time Out"
Section 9.4.4, "Problem in an Oracle RAC-non Oracle RAC Environment with
Naming Conventions"
Section 9.4.5, "In an Oracle RAC-non Oracle RAC Environment, an asgctl create
standby database Operation Returns Error When the Database Is Already in a
Physical Standby State"
Section 9.4.6, "Only One Oracle RAC Node with an Instance on the New Primary
Site Is Started Up Following an asgctl switchover Operation"
Section 9.4.7, "OracleAS Guard Is Unable to Shutdown the Database Because More
Than One Instance of Oracle RAC is Running"
Section 9.4.8, "Resolve Missing Archived Logs"
9.4.1 OracleAS Guard Returned an Inappropriate Message When It Could Not Find the
User Specified Database Identifier
Bugs 5409824 and 5409806
When adding an Oracle RAC instance to the topology using the OracleAS Guard add
instance command and OracleAS Guard could not find the user specified identifier, an
inappropriate error message was returned. If the user had entered the database name
rather that the Oracle instance SID, there was no indication that this was the problem.
Now if OracleAS Guard is unable to locate the oratab entry (on Unix) or the system
registry service (on Windows) for the user specified database identifier, the following
ASG_SYSTEM-100 message now precedes the existing ASG_DUF-3554 message and
both messages will be displayed to the console:
On Unix systems:
ASG_SYSTEM-100: An Oracle database is identified by its database unique name (db_
name)
ASG_DUF-3554: The Oracle home that contains SID <user specified identifier> cannot
be found
On Windows systems:
ASG_SYSTEM-100: An Oracle database is identified by its system identifier (SID)
ASG_DUF-3554: The Oracle home that contains SID <user specified identifier> cannot
be found
9.4.2 OracleAS Guard Add Instance Command Failed When Attempting to Add an
Oracle RAC Database to the Topology (Windows Only)
Bugs 5409824 and 5409806
The Oracle RAC database install on Windows does not store the Oracle RAC DBname
or the global DBname anywhere in the registry or oratab. Therefore, the workaround
to this problem for Windows systems is as follows. When using the asgctl add instance
command, always use the Oracle instance SID of a RAC database and proceed with
rest of the Oracle Disaster Recovery cycle of operations, such as create standby
database, instantiate topology, sync topology, and switchover topology. For example:
asgctl> add instance <InstanceSID of Oracle RAC> on <virtualhost>
90
asgctl> add instance orcl1 on asinfra.us.oracle.com
In a Windows environment, an error message will be returned directing the user to use
the Oracle instance SID of an Oracle RAC database in asgctl commands.
9.4.3 OracleAS Guard Operations Do Not Time Out

In releases prior to OracleAS 10g Patch Set 3 (10.1.2.3.0), some long running Oracle
Application Server Guard (OracleAS Guard) operations timed out due to the
underlying network configuration. For example, OracleAS Guard instantiate
topology, clone topology, clone instance, or create standby
database operations might timed out.
When all the Oracle Application Server instances involved in the OracleAS Guard
operation are upgraded to OracleAS 10g Patch Set 3 (10.1.2.3.0), OracleAS Guard
implements a keep alive message to ensure that idle connections are not closed by the
network.
9.4.4 Problem in an Oracle RAC-non Oracle RAC Environment with Naming

Conventions
Bug 5478869
There is a problem with the naming conventions used in the Oracle RAC/non Oracle
RAC environment. The asgctl set primary database command must be issued for both
the primary and standby site within asgctl to define the service name mapping within
OracleAS Guard before attempting an asgctl create standby database command;
otherwise, the following error message is returned.
ASG_DUF-4902: Object not found in clipboard for key "orcl1keySourceDb".
9.4.5 In an Oracle RAC-non Oracle RAC Environment, an asgctl create standby

database Operation Returns Error When the Database Is Already in a Physical Standby
State
Bug 5480679
An error ora-01671 will occur, when attempting to perform an asgctl create standby
database operation from a database that is already in 'physical standby' state. An
appropriate error message should be echoed indicating that a standby database is
already running, rather than returning this error. This is a known issue.
9.4.6 Only One Oracle RAC Node with an Instance on the New Primary Site Is Started
Up Following an asgctl switchover Operation
Bug 5502497
In a Disaster Recovery environment that involves Oracle RAC databases, after a
switchback operation (switchover topology to <primary site>), the
database will be started up on only one of the Oracle RAC nodes by OracleAS Guard;
however, the remaining Oracle RAC instances on the primary site must be started up
manually.
9.4.7 OracleAS Guard Is Unable to Shutdown the Database Because More Than One
Instance of Oracle RAC is Running
Bug 5455252
91
When you are running OracleAS Guard in an Oracle RAC environment, you should
have only one Oracle RAC instance running while performing OracleAS Guard
operations. Otherwise, an error will occur where the primary database will complain
that it is mounted by more than one instance, which will prevent a shutdown.
For example, when performing an OracleAS Guard create standby database operation
in an Oracle RAC environment with more than one Oracle RAC instance running, the
following error will be seen:
ASGCTL> create standby database orcl1 on stanb06v3
.
.
.
This operation requires the database to be shutdown. Do you want to
continue? Yes or No
y
Database must be mounted exclusive
stanb06v1: -->ASG_DUF-4950: An error occurred on host "stanb06v1" with IP
"141.86.22.32" and port "7890"
stanb06v1: -->ASG_DUF-3514: Failed to stop database orcl1.us.oracle.com.
stanb06v1: -->ASG_DGA-13002: Error during Create Physical Standby:
Prepare-primary processing.
stanb06v1: -->ASG_DUF-3027: Error while executing Creating physical standby
database - prepare phase at step - primary processing step.
9.4.8 Resolve Missing Archived Logs

Bug 5559914
If a sync topology command in a RAC-RAC Linux environment fails and you
receive missing archive logs errors (as shown below), ping the standby node using
tnsping. If you are unable to ping the standby node, stop and restart the listener for
that node and retry the tnsping.
ASG_SYSTEM_-100: Please resolve missing archived logs and try again.
9.5 Oracle Business Intelligence

Section 9.5.1, "Database Access"
Section 9.5.2, "Discoverer Catalog Update for Oracle Business Intelligence"
Section 9.5.3, "New Features for Oracle Business Intelligence"
Section 9.5.4, "Setting Up OracleBI Spreadsheet Add-In for Write-Back"
Section 9.5.5, "Setting up Oracle Discoverer Web Services"
Section 9.5.6, "Creating Advanced Custom Members"
Section 9.5.7, "Sharing Workbooks in Oracle Discoverer Plus OLAP"
Section 9.5.8, "Integrating Oracle BI Publisher with Oracle Discoverer"
Section 9.5.9, "Code Example for Calculation and Validation Program"
Section 9.5.10, "Support for Offset-based Time Calculations"
Section 9.5.11, "Enhancements to Oracle Discoverer OLAP"
Section 9.5.12, "Oracle Business Intelligence Discoverer Connections API"
92
9.5.1 Database Access

The Oracle Business Intelligence components that ship with 10g Release 2 (10.1.2)
support the following versions for the database that contains the data on which you
want to report:
Oracle9i Release 2 Database (9.2.0.8 or later)
Oracle Database 10g Release 1 (10.1.0.4 or later)
Oracle Database 10g Release 2 (10.2.0.2 or later)
Note the following:
When performing relational analysis, you can use Oracle Database Standard
Edition or Oracle Database Enterprise Edition. You must use Oracle Database
Enterprise Edition if you want to take advantage of materialized views, analytic
functions, and the Advanced Security Option (ASO) and Transparent Application
Failover (TAF) database features.
When performing multidimensional analysis, you must use Oracle Database
Enterprise Edition with the OLAP Option. In addition, if you want to use:
-
The calculated member feature of OracleBI Discoverer Plus OLAP, then:

*
You must use Oracle Database 10g Release 2, Patchset 10.2.0.2 with the
5146470 patch and higher.
You must connect to an analytic workspace in Standard Form that was

built with an Oracle tool such as Oracle 10g Analytic Workspace Manager.
The write-back features of OracleBI Spreadsheet Add-In, then see Section 9.5.4,
"Setting Up OracleBI Spreadsheet Add-In for Write-Back".
Tip: If you want to upgrade an analytic workspace from Oracle Database 10g
Release 1 to Release 2, then consult the appropriate section in the Oracle OLAP 10g
Release 2 Application Developer's Guide.
The latest information on supported versions is on the Certify application on:
https://metalink.oracle.com/
9.5.2 Discoverer Catalog Update for Oracle Business Intelligence

Bug 5198004
Consult the following list to decide whether you must update the Discoverer Catalog
by running scripts.
You want to use the features that are available in this patch and that use the
Discoverer Catalog.
You have an existing Discoverer Catalog from a previous version.
The following procedure describes how to perform the Catalog update:

1.
Obtain the files that are needed for the update as follows:
a.
Locate the d4o.jar file in the following directory:

BI_Home\sysman\webapps\emd\WEB-INF\lib
b.
From the d4o.jar file, extract these files: bibcores.pls, bibcoreb.pls,

and biberrcs.pls. The jar file has packing scope. Use the following
commands to extract each file from the jar file to a local directory. Enter each
command on a single line.
93
jar -xf d4o.jar

oracle/dss/persistence/storagemanager/bi/scripts/bibcores.pls
jar -xf d4o.jar
oracle/dss/persistence/storagemanager/bi/scripts/bibcoreb.pls
jar -xf d4o.jar
oracle/dss/persistence/storagemanager/bi/scripts/biberrcs.pls
If the jar command does not run successfully, then either verify that the
directory that contains the jar.exe file is in the path environment variable or
enter the complete path name for the file, such as c:/jdk/bin/jar.exe.
2.
Apply the patch as follows:

a.
At the command prompt, enter:

cd oracle\dss\persistence\storagemanager\bi\scripts
b.
Open a sqlplus session. For example, enter:

sqlplus d4osys/password@mydb
where mydb is the connect string and password is the password of the owner
of the schema that hosts the Discoverer Catalog.
c.
At the sqlplus prompt, enter the following commands:

SQL> @bibcores.pls
SQL> @bibcoreb.pls
SQL> @biberrcs.pls
d.
Compile the contents of the files by entering the following commands:

SQL> ALTER PACKAGE BISM_ERRORCODES COMPILE PACKAGE;
SQL> ALTER PACKAGE BISM_CORE COMPILE PACKAGE;
3.
Ensure that the object is valid as follows:

a.
Reopen the sqlplus session.
b.
Enter the following SQL commands:

SQL> column OBJECT_NAME format a30;
SQL> column STATUS format a10;
SQL> select object_name, status from user_objects where object_name='BISM_
CORE';
The following display indicates that the patch has been applied successfully:
OBJECT_NAME STATUS
-----------------------------------------------BISM_CORE VALID
BISM_CORE VALID
9.5.3 New Features for Oracle Business Intelligence

This patch set provides the features that are described in the following table. For
information on all the new features, consult the updated Help systems for OracleBI
Discoverer Plus OLAP and OracleBI Spreadsheet Add-In.
94
Table 9
New Features
Feature
Description
Applicable Products
Calculated Members You can create calculated members

through a wizard in OracleBI
Discoverer Plus OLAP and view
them in other products.
OracleBI Discoverer Plus

OLAP, OracleBI Discoverer
Viewer, OracleBI Discoverer
Portlet Provider, OracleBI
Spreadsheet Add-In
Write-back
With the appropriate privileges,

you can write data back to the
analytic workspace in the Oracle
database. You can also perform
calculations and validations on the
data, which will run on the server.
OracleBI Spreadsheet Add-In
Graph Styles
You can use six new graph styles

that have been added to create
attractive presentations easily. Each
new style includes a gradient plot
area or a gradient background, or
both.
OracleBI Discoverer Plus,

OracleBI Discoverer Viewer,
OracleBI Discoverer Portlet
Provider.
The names of the new graph styles

are:
April
Comet
Confetti
Glass
Nautical
Southwest
Discoverer Catalog
Support
You can save and retrieve

calculations, saved selections, and
calculated members from the
Discoverer Catalog for use in
OLAP queries.
Share Calculations
You share calculations and saved
and Saved Selections selections across queries in a
In a Workbook
workbook, even when the
workbook is not connected to the
Discoverer Catalog.
Toolbar
You can use toolbar buttons to

perform actions that were
previously available only using
menus and keystrokes.
Floating OracleBI
Query Editor
You can allow the Query Editor to

stay on top of Excel while you edit
the query.
Enhanced
Refreshing of
Queries
You can refresh multiple queries in

a single request, including
refreshing all queries in a
workbook.
VBA Macros
You can call numerous VBA macros OracleBI Spreadsheet Add-In

to programmatically perform
write-back and other operations.
95
9.5.4 Setting Up OracleBI Spreadsheet Add-In for Write-Back

This section provides information for database administrators and application
developers to set up for write-back for users of OracleBI Spreadsheet Add-In. It
contains the following sections:
Section 9.5.4.1, "What is Write-Back?"
Section 9.5.4.2, "What are the Design Considerations for Write-Back?"
Section 9.5.4.3, "What are the Considerations for Aggregation?"
Section 9.5.4.4, "What User Interface Elements in OracleBI Spreadsheet Add-In

Affect Write-Back?"
Section 9.5.4.5, "How Do I Set Up for Writing Data Back Permanently from
OracleBI Spreadsheet Add-In?"
Section 9.5.4.6, "How Do I Set Up for Writing Data for Calculation and Validation
in OracleBI Spreadsheet Add-In?"
Important: Write-back is a very powerful feature. You should implement write-back

only if you are very familiar with Oracle OLAP and analytic workspaces.
9.5.4.1 What is Write-Back? As a database administrator or application developer for
OracleBI Spreadsheet Add-In, you can use write-back in the following two cases:
To allow the values to be written back permanently to an analytic workspace in

the database.
To allow a calculation and validation program from the analytic workspace to be
run on each value. This type of write-back can simulate Excel-style calculations.
This OLAP DML program is triggered by the user entering data in an Excel
worksheet. All the values in the active query are scanned for any cell value
changes. If changes are found, they are submitted to the analytic workspace but
not committed (that is, saved permanently) to the database. OracleBI Spreadsheet
Add-In then refreshes the query with the latest data from the analytic workspace.
One flavor of this approach is sometimes referred to as "what-if analysis." In this
type of analysis, users enter values to see the effect that those changed values have
on other values, such as totals. Users can view the effects of the changes, then
discard their work without saving values permanently to the worksheet (if they
have a read-only connection) or back to the analytic workspace (if they have a
read/write connection).
9.5.4.2 What are the Design Considerations for Write-Back? Write-back should be performed
only on analytic workspaces that have been designed for that purpose. As a database
administrator who is designing an analytic workspace to be used for write-back, you
must adhere to the following considerations:
Database access: You must adhere to the following requirements:

-
In single-writer mode, use Oracle Database 10g Release 1 (10.1.0.4 and higher).
In multiwriter mode with compressed composites, use Oracle Database 10g

Release 2, Patchset 10.2.0.2 with the 5146470 patch and higher.
In either mode, connect to an analytic workspace in Standard Form that was

built with an Oracle tool such as Oracle 10g Analytic Workspace Manager.
User access: You must ensure that users who need to write back to the analytic
workspaces have the appropriate privileges.
96
PERMITs: If you plan to perform scoping of the analytic workspace using the
OLAP DML PERMIT command, then ensure that you read and understand the
information on the PERMIT _READ and PERMIT _WRITE startup programs in the
Oracle OLAP DML Reference. In particular, note the following about startup
programs:
-
When OracleBI Spreadsheet Add-In establishes a read-only connection to an

analytic workspace, the PERMIT_READ program runs, if it exists.
When OracleBI Spreadsheet Add-In establishes a read/write connection to an

analytic workspace, the PERMIT_WRITE program runs, if it exists.
Important: Ensure that you understand the use of the PERMIT_WRITE
startup program, as errors in the PERMIT _WRITE program can lock you out
of the analytic workspace.
Data types: When performing write-back, users can enter values only of one of the
following supported types: integer, decimal, and text. Date and Boolean types are
not supported.
Partitioning strategy: You must implement an appropriate partitioning strategy to
accommodate write-back, as outlined in Oracle OLAP documentation.
Aggregation considerations: You must use care when handling aggregated values
for write-back. See Section 9.5.4.3, "What are the Considerations for Aggregation?"
Global composites: When global composites are used, the analytic workspace does
not support multiwriter connections. See the Help for Analytic Workspace
Manager for information on global composites.
Value caching: By default, analytic workspaces in Standard Form cache
dynamically computed aggregate values during the users session. When
debugging a write-back solution, you might find it helpful to temporarily disable
session caching of dynamically computed aggregate values by setting the
SESSCACHE option to NO.
Additional information: For more information, see the following sources:
-
Oracle OLAP documentation, especially, the Oracle OLAP DML Reference for
information about the multiwriter feature in Oracle OLAP. Consult the topics
for the AGGREGATE command, the AGGREGATE function, the CACHE
statement within the AGGMAP command, the CLEAR command, the
SESSCACHE option, and the $VARCACHE property.
Write-back topics in the OracleBI Spreadsheet Add-In Help system for

end-user information on this topic.
Section 9.8, "Oracle Business Intelligence Spreadsheet Add-In Issues and

Workarounds" for important known issues that affect write-back in OracleBI
Spreadsheet Add-In.
9.5.4.3 What are the Considerations for Aggregation? The aggregation strategy for the cubes
in the analytic workspace affects which data cells can be updated and what the results
of the updates are, as described in the following list:
Writing data back to a leaf level: Generally you allow users to enter data at the
lowest leaf level. Ensure that you consider any dimensions that are on the page
edge when creating the query.
If users want to see the effect of the data that they enter at a leaf level on an
aggregate level, another step is necessary. In this case, if any aggregate levels are
97
precomputed or caching is enabled, then you must either rerun the AGGREGATE
command or (if no levels are precomputed), flush the cache.
Writing data back to an aggregate level: Use care when allowing users to enter
data for aggregated values and follow these guidelines:
-
Data that users write back to a dynamically computed aggregate level has no
effect on any other levels, either above or below that level.
If you want to allow users to write back data at only specified aggregate
levels, then in the aggregation plan for the cube, specify those levels as
precomputed.
Data that users write back to a precomputed aggregate level affects

non-cached, dynamically computed aggregate values at higher levels, up to
but not including the next precomputed aggregate level. If users want to see
the effect of that data at higher aggregate levels and caching is enabled, then
you must either rerun the AGGREGATE command or (if no higher levels are
precomputed), flush the cache.
You must execute any Allocation logic that is required for users to see the
effect of the newly written-back data at lower levels.
You can handle the automatic allocation of write-back data at the aggregate
level by attaching a write trigger to the target variable or formula. This trigger
is an OLAP DML program that runs when an object is the target of an
assignment (=) command. You can use the write trigger for a formula to write
back to the source data variables and even allocate the value to detail levels.
Writing data back as NA: Users can write NA data back at the leaf level and at
precomputed aggregation levels. They cannot write NA data back at dynamically
computed aggregation levels, because the AGGREGATE function triggers its own
dynamic computations when it encounters an NA value.
9.5.4.4 What User Interface Elements in OracleBI Spreadsheet Add-In Affect Write-Back?
OracleBI Spreadsheet Add-In includes the following user interface elements that
support write-back:
Connect dialog: The Connect dialog includes two boxes that affect write-back:
-
Read-only box This box specifies whether users establish a read-only

connection to the database, and the box is checked by default. Users can
uncheck this box to establish a read/write connection, if they have the
appropriate privileges and want to enter data in cells.
Enable calculation & validation by Oracle OLAP box This box indicates
whether users want to perform calculations and validations from the Oracle
OLAP option on the data that they enter in a worksheet. This box is
unchecked by default for read-only connections, and users must check it each
time that they establish a read-only connection and want to perform
calculation and validation operations.
Options dialog: The Options dialog includes a Calculation & Validation tab. This
tab has these options that allow users to specify when values are calculated and
validated during write-back:
-
Automatic Specifies to calculate and validate automatically each value that

users enter into a cell in worksheets that contain data from Oracle OLAP.
98
Manual Specifies to calculate and validate cells that contain data from
Oracle OLAP only when users choose the appropriate menu option or toolbar
button.
Menu options and toolbar buttons: The following menu options and toolbar
buttons affect write-back:
-
Calculate and Validate Now This option on the OracleBI menu and toolbar
specifies to calculate and validate the OLAP values that users have entered in
the current worksheet.
Save This option on the Excel File menu and toolbar specifies to calculate
and validate the OLAP values that users have entered and to save to the
analytic workspace the appropriate changes. Changes are saved for all queries
that use the same read/write connection. Changes are also saved to the
workbook files.
9.5.4.5 How Do I Set Up for Writing Data Back Permanently from OracleBI Spreadsheet Add-In?
For users to write data back permanently to the analytic workspace from Excel, you
must perform the following steps:
1.
Adhere to the requirements that are specified in Section 9.5.4.2, "What are the
Design Considerations for Write-Back?"
2.
Start Excel with a new, empty workbook and select New Query from the OracleBI
menu.
3.
In the Connect dialog, perform the following steps:
4.
a.
Uncheck the Read-only box.
b.
Enter the appropriate information to connect to the database.
c.
Choose OK.
In the Query Editor, create the query in which users will enter values.
Important: Ensure that users know which values in the worksheet can be edited.
Users can enter values in cells that contain OLAP calculations and calculated
members and will receive no notification of this, but these values cannot be saved
to the analytic workspace. If you include calculations or calculated members in the
query, then ensure that users understand this limitation, for example by providing
instructions and visual cues in the worksheet.
5.
Save changes to the workbook and close it.
6.
Send the workbook to users.
A user performs the steps that are described in the "Performing Write-Back" topic in
the OracleBI Spreadsheet Add-In Help system to write values back to the analytic
workspace. The Read-only box in the Connect dialog will be unchecked, because the
workbook was last saved with that setting.
9.5.4.6 How Do I Set Up for Writing Data for Calculation and Validation in OracleBI Spreadsheet
Add-In? For users to write data for calculation and validation, you must perform the
following steps:
1.
Adhere to the requirements that are specified in Section 9.5.4.2, "What are the
Design Considerations for Write-Back?"
2.
Start Excel with a new, empty workbook and select New Query from the OracleBI
menu.
99
3.
4.
In the Connect dialog, perform the following steps:

a.
Uncheck the Read-only box.
b.
Check the Enable calculation & validation by Oracle OLAP box.
c.
Enter the appropriate information to connect to the database.
d.
Choose OK.
In the Query Editor, create the query in which users will enter values.
Important: Ensure that users know which values in the worksheet can be edited.
Users can enter value in cells that contain OLAP calculations and calculated
members and will receive no notification of this, with unpredictable results. If you
include calculations or calculated members in the query, then ensure that users
understand this limitation, for example by providing instructions and visual cues
in the worksheet.
5.
Decide in which analytic workspace you will store the OLAP DML program that
will perform the calculation and validation. Consider the following:
You can store the program in the same analytic workspace that contains the
data on which users are querying. The workspace is attached to the users
session at connection time.
You can store the program in an analytic workspace that has been designated
to store programs for applications. You must ensure that you attach this
workspace so that programs are available during the users session.
6.
Create the OLAP DML program in the appropriate workspace, using Analytic
Workspace Manager or OLAP Worksheet. See Section 9.5.4.7, "How do I Create an
OLAP DML Program?"
7.
Use the BIA_RegisterCalcValidationProgram() macro to register the OLAP DML

program. In the following example code, the name of the query in the worksheet is
Query 1 and the name of the OLAP DML program is wbvalidator. If the
program does not exist in the same analytic workspace as the data, then you must
specify the fully qualified name of the program, in the form
owner.workspace!program, such as pedro.mydemo!wbvalidator.
Private Sub CommandButton1_Click()
BIA_RegisterCalcValidationProgram", "Query 1", "wbvalidator"
' comment
MsgBox "Calculation & Validation enabled."
End Sub
You can include the BIA_RegisterCalcValidationProgram() macro in the auto_open

procedure to automatically register the program for calculation and validation
when a workbook is opened.
See the OracleBI Spreadsheet Add-In Help system for information on coding
macros.
8.
Save changes to the workbook and close it.
9.
Send the workbook to users.
A user performs the steps that are described in the "Performing Write-Back" topic in
the OracleBI Spreadsheet Add-In Help system to write data for calculation and
validation.
9.5.4.7 How do I Create an OLAP DML Program?
100
Use the following procedure to create an OLAP DML program:

1.
In Analytic Workspace Manager, locate and make note of the object names that
you need to reference in the program.
These objects include the name of the measure for which users are writing values
and the dimensions and dimension values of that measure. For example, users
might select the Sales measure in OracleBI Spreadsheet Add-In. In Analytic
Workspace Manager, you might find that the object name for the Sales measure is
WB_DEMO.SH_AW!SALES.
2.
In Analytic Workspace Manager, right-click the analytic workspace in which you

want to create the program, then select OLAP Worksheet.
You can store the program in the same analytic workspace that contains the data
on which users are querying or in a workspace that has been designated to store
programs for applications.
3.
At the command line, enter the following:

DEFINE WBVALIDATOR PROGRAM
4.
To edit the program, enter the following:

EDIT WBVALIDATOR
5.
Enter the code for the program.

For more information, Section 9.5.9, "Code Example for Calculation and Validation
Program".
6.
Save your changes and exit the editor.
7.
To save the program in the database, enter the following at the command line:
UPDATE
COMMIT
8.
Exit the OLAP Worksheet.
For information on the OLAP DML, see the Oracle OLAP Application Developer's Guide
and the Oracle OLAP DML Reference.
9.5.5 Setting up Oracle Discoverer Web Services

Before setting up Oracle Discoverer Web Services, make a backup of any file you edit.
For example, rename the file .backup so any changes can quickly be undone. There are
files with the same name in multiple locations, ensure you have the right location
before making any changes.
After applying the 10.1.2.3 patch, the following steps are required to configure the
Oracle Discoverer Web services.
1.
Create an OID Container. An Oracle Internet Directory container needs to be

created to allow the Oracle Discoverer Web services to work with all types of
Oracle Discoverer systems.
a.
Set the ORACLE_HOME environment variable.
b.
Create the container by running the following batch file located in the
ORACLE_HOME\discoverer\util directory:
For UNIX:
createoidcontainer.sh orcladmin AppServerAdmin_password
101
For Windows:
createoidcontainer.bat orcladmin AppServerAdmin_password
2.
Update Java policy file by adding the following permission in the ORACLE_
HOME/j2ee/OC4J_BI_Forms/config/java2.policy file:
grant codebase
"file:${oracle.home}/j2ee/OC4J_BI_Forms/application-deployments/discoverer/-"
{
permission java.lang.RuntimePermission
"oracle.discoverer.connections";
}
3.
Define a trusted user to access the Oracle Discoverer Web Services by creating a
trusted user to access the Oracle Discoverer Web services. This user and a group
are created using Oracle Application Server Enterprise Manager from your BI &
Forms installation.
a.
Log into Application Server Control and navigate to the following location:
OC4J_BI_FORMS > Applications > Discoverer
4.
b.
Select the Security link to display the security page.
c.
Click Add Group and add a group called sr_users. You should see
jazn.com/sr_users group being created under Group category.
d.
Click Add User and add a single user, for example, bipublisher, and add them
to the group sr_users. You should now see jazn.com/bipublisher user created
in the Users category.
Map Group/Users to an application specific role. This step requires you to edit a
file to map the users and role you just created to a pre-existing application specific
role called sr_users. Edit the ORACLE_HOME/j2ee/OC4J_BI_
Forms/application-deployments/discoverer/orion-application.xml file by adding
the following section before the last </orion-application>:
<security-role-mapping name="sr_users">
<group name="jazn.com/sr_users"/>
<user name="jazn.com/bipublisher"/>
</security-role-mapping>
5.
Restart the OC4J_BI_Forms.
6.
Verify access to the Oracle Discoverer Web Services by navigating to the following
URL
http://<host>:<port>/discoverer/wsi
You should be prompted for the user and password created in the previous
steps.You should be able to see the list of Oracle Discoverer Web Services APIs.
7.
Add the following entry to the configuration.xml file to control the

configuration parameters:
<ws logLevel="debug" maxSessions="20">
<enableWS status="true"/>
</ws>
In the preceding entry, logLevel specifies the logging level, maxSessions specifies
the maximum number of Oracle Discoverer sessions that can be active at the same
102
time (the recommended value is 20), and enableWS specifies whether the Oracle
Discoverer Web Services is enabled.
9.5.6 Creating Advanced Custom Members

This patch includes greater flexibility in creation of custom groupings and calculated
members by increasing the range of mathematical operators that can be used to create
calculated members. Go to the custom member dialog as follows:
1.
Select Calculated Members from the Tools menu, then select the dimension.
2.
Click the New Calculated Member icon in the Available Items pane.
A new option has been introduced that offers the following choices:
Aggregate Selected Members. This allows the selection of the following

aggregation methods for the selected members: Default By Measure, Add or
Subtract Members, Sum, Average, Minimum, Maximum or Count.
Create Custom Expression. This allows the use of the operators + - * / ( ) in
addition to numeric values in the creation of flexible formulae for calculated
members.
9.5.7 Sharing Workbooks in Oracle Discoverer Plus OLAP

If you want other users to share workbooks that you have created, then you can do
that easily with the Share Workbook dialog. When you share a workbook, you store a
shortcut to the workbook in a Shared folder. Other users click the shortcut to access the
shared workbook.
1.
Open the workbook that you want to share in Oracle Discoverer Plus OLAP.
2.
From the File menu, select Workbook Properties.
3.
In the Workbook Name Properties dialog, select Share.
4.
In the Location tab of the Share dialog, enter the name and shared folder in which
to store the shortcut for the shared folder.
5.
Click Privileges.
6.
Click Add.
7.
In the Add Users and Roles dialog, specify the users or roles that you want to add
to the object and assign the privileges that you want them to have. A
recommended privilege for sharing with other users is Read privilege.
8.
Click OK to return to the Privileges tab.
9.
Select Update Privileges for the Dependent Objects to specify that all objects on
which the shared workbook depends have their privileges updated such that they
are also available to the users that can access the shared workbook.
10. Click OK to create a shortcut for the shared workbook.
9.5.8 Integrating Oracle BI Publisher with Oracle Discoverer

For integrating Oracle BI Publisher with Oracle Discoverer refer to Oracle Business
Intelligence New Features Guide Release 10.1.3.3.2 Part No. E10416-03 available at
http://download.oracle.com/docs/cd/E10415_
01/doc/bi.1013/e10416/discointeg.htm#BABIDJBC
103
9.5.9 Code Example for Calculation and Validation Program

This section describes and provides an example of an OLAP DML program called
WBVALIDATOR that validates the data that is entered within certain ranges for
various measures in OracleBI Spreadsheet Add-In. It contains the following sections:
Section 9.5.9.1, "How the Program Works"
Section 9.5.9.2, "Argument for the Program"
Section 9.5.9.3, "Specifying the Measure"
Section 9.5.9.4, "Finding the Data Value"
Section 9.5.9.5, "Finding the value of a Specific Dimension"
Section 9.5.9.6, "Taking Actions with the Values"
Section 9.5.9.7, "Complete Program Code"
9.5.9.1 How the Program Works The WBVALIDATOR program is run for every cell that a
user has updated. The write-back engine in Oracle OLAP passes to the program a fully
qualified data reference (QDR) and the data value that the user entered in the cell. The
program then checks the QDR and data value and takes the appropriate action. If an
error occurs, then the program returns a string for display in OracleBI Spreadsheet
Add-In.
9.5.9.2 Argument for the Program The WBVALIDATOR program takes a single argument
that is passed in from the write-back engine. The string that is passed in contains
information about the active measure, the current dimension values, and the data
value that is being written back. The format of this string argument is as follows:
schema.awname!variable_name(schema.awname!dimension1_name
'dimension1_value\', schema.awname!dimension2_name
'dimension2_value\'... ,schema.awname!dimensionN_name
'dimensionN_value\')=2000
The following is an example of an argument that can be passed to the program:
SH_OLAP.SH_AW!SALES_PRT_TOPVAR(SH_OLAP.SH_AW!SALES_PRT_MEASDIM 'REVENUE'
SH_OLAP.SH_AW!TIME '1717',SH_OLAP.SH_AW!GEOGRAPHIES '52785',
SH_OLAP.SH_AW!PRODUCTS '15',SH_OLAP.SH_AW!CHANNELS '3')=12
9.5.9.3 Specifying the Measure To calculate and validate the data, the WBVALIDATOR
program must use the name of the measure on which it is running. The following code
fragment shows how to specify the Sales Revenue measure in the SH_OLAP database
schema.
measID = 'SH_OLAP.SH_AW!SALES_PRT_TOPVAR(SH_OLAP.SH_AW!SALES_PRT_MEASDIM
\'REVENUE\''
9.5.9.4 Finding the Data Value The WBVALIDATOR program must know the data value
that the user entered in the cell, such as 12345. If the argument that is passed into the
program is stored in a variable called _qdr, then the following line of code extracts the
data value from the argument and stores that name in a variable called _value.
_value = blankstrip(extchars(_qdr, findchars(_qdr, '=') + 1), BOTH)
The calculation and validation program must handle the case where the user clears a
cell in Excel and saves the changes. Without the handling of empty cells, errors can
occur with unpredictable results. The program can check for empty cells by locating
104
NA values. In the following example, the program checks for NA values and exits the
program if one is found. You can write a program that handles NA values in a
different way.
if nafill(_value, NA) eq NA
then return
9.5.9.5 Finding the value of a Specific Dimension The WBVALIDATOR program must
know the value of each dimension, to perform the appropriate actions. To find the
value of a specific dimension, the program uses the OLAP DML EXTCHARS and
FINDCHARS functions to first remove the text beyond value name and then the text
before the value name, as shown in the following example.
" Find the QDR value for PRODUCTS
ProdID = 'SH_OLAP.SH_AW!PRODUCTS'
_ProdQDRValue = extchars(_qdr, findchars(_qdr, '\'', findchars(_qdr, ProdID))+1)
_ProdQDRValue = extchars(_ProdQDRValue, 1, findchars(_ProdQDRValue, '\'')-1)
9.5.9.6 Taking Actions with the Values When the WBVALIDATOR program obtains the
values that it needs, it can check for conditions and take appropriate actions. For
example, the program can verify that the value that the user entered is within a certain
limit. If the value is outside the limit, then the program can display an error message.
The following example code checks if the value is above 200,000 and if it is not, then
the program stores error message text in the _retcode variable. The RETURN
command displays the text in an error message box in Excel.
if convert(_value, decimal) le 200000
then _retcode = joinchars('Sales Revenue for ', _TimeQDRLongDesc, ' must be above $200000')
return _retcode
See the complete program code for an example of performing a calculation if values
are within an allowed range.
9.5.9.7 Complete Program Code This section contains the complete code for the
WBVALIDATOR program.
DEFINE WBVALIDATOR PROGRAM
PROGRAM
" This program is a sample OLAP DML program that can be used
" with the BI Beans write-back engine
" or the OracleBI Spreadsheet Add-in write-back feature.
" It demonstrates how to find data and dimension values and
" process them for validation purposes,
" in this case, to check whether values entered are in a certain range.
" The program is called once for each cell that has been updated.
" You should be familiar with OLAP DML in order to create or
" modify such a program.
arg _qdr
text
vrb _value
vrb _retcode
text
text
vrb _numeric
vrb _text
text
text
"
"
"
"
"
"
105
Argument to program
Contains full string of QDR pairs/data values
from the write-back engine for all cells.
Contains the data value
Return code from this program will be
passed back to add-in for display
vrb measID text

vrb ProdID text
vrb _ProdQDRValue
" Must be set to full measure ID from first part of _qdr

text
vrb GeogID text

vrb _GeogQDRValue text
vrb ChanID text
vrb _ChanQDRValue text
vrb TimeID text
vrb _TimeQDRValue text
" After arguments have been parsed, this

" variable contains the PRODUCT dimension value.
" variable contains the GEOGRAPHY dimension value.
" variable contains the CHANNEL dimension value.
" variable contains the TIME dimension value.
vrb _TimeQDRLongDesc text

vrb _dimLongDesc text
trap on error noprint
_retcode = '0'
if findchars(_qdr, '=') gt 0
then do
" Specify measure for the program to process, in this case 'Sales Revenue'
measID = 'SH_OLAP.SH_AW!SALES_PRT_TOPVAR(SH_OLAP.SH_AW!SALES_PRT_MEASDIM
\'REVENUE\''
" Exit if not correct measure
if findchars(_qdr, measID) eq 0
then return
" Parse arguments to find MEASURE data value
_value = blankstrip(extchars(_qdr, findchars(_qdr, '=') + 1), BOTH)
" Find the QDR value for PRODUCTS
ProdID = 'SH_OLAP.SH_AW!PRODUCTS'
_ProdQDRValue = extchars(_qdr, findchars(_qdr, '\'', findchars(_qdr, ProdID))+1)
_ProdQDRValue = extchars(_ProdQDRValue, 1, findchars(_ProdQDRValue, '\'')-1)
" Find the QDR value for GEOGRAPHIES
GeogID = 'SH_OLAP.SH_AW!GEOGRAPHIES'
_GeogQDRValue = extchars(_qdr, findchars(_qdr, '\'', findchars(_qdr, GeogID))+1)
_GeogQDRValue = extchars(_GeogQDRValue, 1, findchars(_GeogQDRValue, '\'')-1)
" Find the QDR value for CHANNELS
ChanID = 'SH_OLAP.SH_AW!CHANNELS'
_ChanQDRValue = extchars(_qdr, findchars(_qdr, '\'', findchars(_qdr, ChanID))+1)
_ChanQDRValue = extchars(_ChanQDRValue, 1, findchars(_ChanQDRValue, '\'')-1)
" Find the QDR value for TIME
TimeID = 'SH_OLAP.SH_AW!TIME'
_TimeQDRValue = extchars(_qdr, findchars(_qdr, '\'', findchars(_qdr, TimeID))+1)
_TimeQDRValue = extchars(_TimeQDRValue, 1, findchars(_TimeQDRValue, '\'')-1)
" Get TIME long description to use in message
dimLongDesc = lmt(name to obj(property 'AW$ROLE') eq 'ATTRDEF' and obj(property 'AW$PARENT_NAME') eq 'TIME' and -
106
obj(property 'AW$TYPE') eq 'MEMBER_LONG_DESCRIPTION')

_TimeQDRLongDesc = &_dimLongDesc(TIME _TIMEQDRValue)
" Handle NA values by setting cells to NA
if nafill(upcase(_value), 'NA') eq 'NA'
then do
push PRODUCTS GEOGRAPHIES CHANNELS
limit PRODUCTS to _ProdQDRValue
limit GEOGRAPHIES to _GeogQDRValue
limit CHANNELS to _ChanQDRValue
SH_OLAP.SH_AW!SALES_PRT_TOPVAR(SH_OLAP.SH_AW!SALES_PRT_MEASDIM 'REVENUE' TIME
'1717') = NA
'1718') = NA
'1719') = NA
pop PRODUCTS GEOGRAPHIES CHANNELS
return
doend
" Display message
" less than 200000
if convert(_value,
then _retcode =
if Sales Revenue is
or more than 2000000
decimal) le 200000
joinchars('Sales Revenue for ', _TimeQDRLongDesc, ' must be above $200000')
if convert(_value, decimal) gt 2000000
then _retcode = joinchars('Sales Revenue for ', _TimeQDRLongDesc, ' must be below $2000000')
" Perform calculation, if values are within allowed range.
" Take input value for October 05 (1717)
" Multiply by 1.10 and put in Nov 05 (1718)
" Multiply by 1.20 and put in Dec 05 (1719)
if _retcode eq '0'
then do
SH_OLAP.SH_AW!SALES_PRT_TOPVAR(SH_OLAP.SH_AW!SALES_PRT_MEASDIM
'1718') = SH_OLAP.SH_AW!SALES_PRT_TOPVAR(SH_OLAP.SH_AW!SALES_PRT_MEASDIM
'1717')*1.1
SH_OLAP.SH_AW!SALES_PRT_TOPVAR(SH_OLAP.SH_AW!SALES_PRT_MEASDIM
'1719') = SH_OLAP.SH_AW!SALES_PRT_TOPVAR(SH_OLAP.SH_AW!SALES_PRT_MEASDIM
'1717')*1.2
doend
doend
'REVENUE' TIME
'REVENUE' TIME
'REVENUE' TIME
'REVENUE' TIME
" If no error conditions have been encountered,

" then _retcode will be '0', which indicates success.
" If an error occurs, such as a variable out of range,
" then _retcode contains text to be passed back to
" OracleBI Spreadsheet Add-in
return _retcode
" If an error occurred during execution of the program,
" then return the error message.
error:
return joinchars('An error occured during validation:',
errortext)
END
107
errorname, ' ', -
9.5.10 Support for Offset-based Time Calculations

A new configuration parameter "EnableLevelOffsetBasedTimeCalc" needs to be
manually set in the configuration.xml file to support offset based calculations.
EnableLevelOffsetBasedTimeCalc: Specifies the kind of calculation templates that
Oracle Discoverer Plus OLAP users see. When this configuration parameter is set to
true users see the level-offset based templates. Users will see the calendar-based
templates when they edit a calculation that was created with those templates.
9.5.11 Enhancements to Oracle Discoverer OLAP

The following are enhancements to Oracle Discoverer OLAP:
Ability to open a worksheet with a double-click. Users can open the workbook
from the recently used list by double clicking on it.
Ability to expand and collapse all members in crosstab. In a cross table option of
expanding the dimension till its leaf node level is available through drop down
context sensitive menu. Similarly collapsing to the top most level of the dimension
is available.
9.5.12 Oracle Business Intelligence Discoverer Connections API

This section provides release notes for the OracleBI Discoverer Connections API and
contains the following topics:
Section 9.5.12.1, "What is an OracleBI Discoverer Connection?"
Section 9.5.12.2, "What is the OracleBI Discoverer Connections API?"
Section 9.5.12.3, "What is an OracleBI Discoverer Connections API Command?"
Section 9.5.12.4, "What is an OracleBI Discoverer Connections API Command

Modifier?"
Section 9.5.12.5, "What are the Prerequisites for Using the OracleBI Discoverer
Connections API?"
Section 9.5.12.6, "How to Update Security Permissions Required by the OracleBI
Discoverer Connections API"
Section 9.5.12.7, "What Command Syntax Conventions Does This Guide Use?"
Section 9.5.12.8, "What is the Syntax for Commands?"
Section 9.5.12.9, "How to Run OracleBI Discoverer Connections API Commands"
Section 9.5.12.10, "How to Run a Command Directly at an Operating System

Command Prompt"
Section 9.5.12.11, "How to Run Multiple Commands Stored in an Operating
System Command File"
Section 9.5.12.12, "How to Create, Edit, and Delete OracleBI Discoverer
Connections"
Section 9.5.12.13, "OracleBI Discoverer Connections API Command Reference"
Section 9.5.12.14, "OracleBI Discoverer Connections API Comment Modifier
Reference"
9.5.12.1 What is an OracleBI Discoverer Connection? An OracleBI Discoverer connection is

a stored set of login details such as database user name, database password, and
108
database name. OracleBI Discoverer connections enable end users to start OracleBI
Discoverer without having to enter login details.
OracleBI Discoverer connections can be private or public, as follows:
A private OracleBI Discoverer connection is only accessible to an individual

OracleBI Discoverer end user (typically an OracleAS Single Sign-On user). For
example, a private OracleBI Discoverer connection called 'Western data analysis'
that is created for the OracleAS Single Sign-On user jchan is only accessible to the
user jchan.
A public OracleBI Discoverer connection is accessible to all OracleBI Discoverer
end users. For example, a public OracleBI Discoverer connection called "Global
data analysis" is accessible to all OracleBI Discoverer end users.
You can use only private connections with OracleBI Discoverer Plus OLAP. Public
connections are not supported. However, you can use public connections with
OracleBI Discoverer Viewer and OracleBI Discoverer Portlet Provider to access
worksheets that you have created with OracleBI Discoverer Plus OLAP.
9.5.12.2 What is the OracleBI Discoverer Connections API? The OracleBI Discoverer
Connections API is a set of text-based commands that enable you to programmatically
create and manipulate OracleBI Discoverer connections. For example, you might use
the OracleBI Discoverer Connections API to create a set of OracleBI Discoverer
connections for an Oracle Business Intelligence installation.
The OracleBI Discoverer Connections API enables you to create and manipulate both
public and private OracleBI Discoverer connections for all three types of data source:
Relational data sources
OLAP data sources
Oracle Applications data sources
You can run OracleBI Discoverer Connections API commands individually at an

operating system command prompt, or in batch-mode from an operating system
command file (for more information, see Section 9.5.12.9, "How to Run OracleBI
Discoverer Connections API Commands").
Notes
OracleBI Discoverer end users can also create, edit, and delete private OracleBI
Discoverer connections using the Connect to OracleBI Discoverer page that is used
to start OracleBI Discoverer Plus and OracleBI Discoverer Viewer (if they have the
required privileges). For information about displaying the Connect to OracleBI
Discoverer page, see Oracle Business Intelligence Discoverer Plus Users Guide or
Oracle Business Intelligence Discoverer Viewer Users Guide.
Middle-tier administrators can also create, edit, and delete public OracleBI
Discoverer connections using the OracleBI Discoverer Public Connections page
that is accessed using the OracleBI Discoverer Administration tab in Application
Server Control. For information about managing public connections, see Oracle
Business Intelligence Discoverer Configuration Guide.
9.5.12.3 What is an OracleBI Discoverer Connections API Command? An OracleBI Discoverer

Connections API command is an instruction that creates, updates, or deletes an
OracleBI Discoverer connection. For example, the -create_conn command creates a
new OracleBI Discoverer connection. For a description of each OracleBI Discoverer
109
Connections API command, see Section 9.5.12.13, "OracleBI Discoverer Connections

API Command Reference".
9.5.12.4 What is an OracleBI Discoverer Connections API Command Modifier? An OracleBI
Discoverer Connections API command modifier is an instruction that qualifies or
refines an OracleBI Discoverer Connections API command. For example, the -type
command modifier specifies whether an OracleBI Discoverer connection is public or
private. For a description of each OracleBI Discoverer Connections API command
modifier, see Section 9.5.12.14, "OracleBI Discoverer Connections API Comment
Modifier Reference".
9.5.12.5 What are the Prerequisites for Using the OracleBI Discoverer Connections API? To use
the OracleBI Discoverer Connections API, you need:
To know the orcladmin password for the Oracle Application Server installation.
To use the OracleBI Discoverer Connections API, you must connect as the
orcladmin user by using the command -connect orcladmin/<orcladmin password>).
If you need to find out the orcladmin password, then use the ldapsearch command
(for more information, see Oracle Identity Management User Reference).
To register the util directory on the Oracle Business Intelligence middle-tier

machine (for example, on UNIX, <ORACLE_HOME>/discoverer/util) in the
environment variables for that machine.
To enable OracleAS Single Sign-On for the Oracle Business Intelligence installation
(if you want to use the OracleBI Discoverer Connections API to create private
OracleBI Discoverer connections).
9.5.12.6 How to Update Security Permissions Required by the OracleBI Discoverer Connections
API Before you can run OracleBI Discoverer Connections API commands, you must
add the required security permissions to the jazn-data.xml file and the
java.policy file. You must update the jazn-data.xml file and the java.policy
file on each middle tier machine on which you want to run OracleBI Discoverer
Connections API commands.
To update the security permissions that required by the OracleBI Discoverer
Connections API:
1.
On the middle-tier machine, open the jazn-data.xml file in an XML editor or

text editor.
For example, on UNIX, open ORACLE_HOME/config/jazn-policy.xml.
2.
Add the following XML code inside the <jazn-policy> tag:

<grant>
<grantee>
<codesource>

<url>file:/<ORACLE_HOME>/discoverer/lib/capi.jar</url>
</codesource>
</grantee>
<permissions>
<permission>
<class>
oracle.ias.repository.schemaimpl.CheckRepositoryPermission
</class>
110
<name>getDBConnect</name>
</permission>
<permission>
<class>
</class>
<name>getDBPassword</name>
</permission>
<permission>
<class>
</class>
<name>getSchema</name>
</permission>
<permission>
<class>
</class>
<name>isProductChildExist</name>
</permission>
<permission>
<class>
</class>
<name>makeNewOIDEntry</name>
</permission>
<permission>
<class>
</class>
<name>addInstanceAccessToOIDEntry</name>
</permission>
<permission>
<class>
</class>
<name>getOIDConnect</name>
</permission>
<permission>
<class>
</class>
<name>getSchema</name>
</permission>
<permission>
<class>
</class>
<name>getDBPassword</name>
</permission>
<permission>
111
<class>
</class>
<name>connectAs</name>
</permission>
</permissions>
</grant>
3.
On the middle-tier machine, open the java.policy file in a text editor.

For example, on UNIX, open JAVA_HOME/JRE/LIB/SECURITY/java.policy.
4.
Add the following lines:

grant {
permission java.lang.RuntimePermission "oracle.discoverer.connections";
permission java.lang.RuntimePermission "oracle.discoverer.activation";
};
Note: The first line (permission java.lang.RuntimePermission

"oracle.discoverer.connections") might already by present.
5.
Save changes to the files.
9.5.12.7 What Command Syntax Conventions Does This Guide Use? This guide uses the
following command syntax conventions:
Commands and command modifiers are shown in plain type and are prefixed
with a dash (-).
Note: Do type the dash.
Mandatory command text is enclosed in angle brackets < >.

Note: Do not type the angle brackets.
Optional command text is enclosed in square brackets [].

Note: Do not type the square brackets.
Variable command text (that is, where you supply the value) is shown in italics.
Where command text is separated by a pipe character (|), choose one option from
the list. For example, '-olap <"true" | "false">' means specify either -olap "true" or
-olap "false".
Note: Do not type the pipe character.
9.5.12.8 What is the Syntax for Commands? Use the following syntax for OracleBI
Discoverer Connections API commands:
On Windows, use the following syntax:

capi.bat -connect orcladmin/<orcladmin password> <-command> <command
modifiers>
On UNIX, use the following syntax:

capi.sh -connect orcladmin/<orcladmin password> <-command> <command
modifiers>
112
Notes:
Commands and command modifiers are case-sensitive. In other words, you

cannot use uppercase and lowercase characters interchangeably.
Unless stated otherwise, variable command arguments are not case-sensitive.
Command modifiers can appear in any order as long as their arguments
immediately follow them in the correct order.
You must specify commands in a single line with no line breaks or carriage
returns.
Enclose command modifier arguments in double quotes (""). For example, if an
End User Layer is called Video Store Analysis, then specify the End User Layer
name as -eul "Video Store Analysis".
9.5.12.9 How to Run OracleBI Discoverer Connections API Commands You can run
anOracleBI Discoverer Connections API command in two ways:
by running the command directly at an operating system command prompt (for

more information, see Section 9.5.12.10, "How to Run a Command Directly at an
Operating System Command Prompt")
by running multiple commands stored in an operating system command file (for
more information, see Section 9.5.12.11, "How to Run Multiple Commands Stored
in an Operating System Command File")
9.5.12.10 How to Run a Command Directly at an Operating System Command Prompt You run
an OracleBI Discoverer Connections API command directly at a command prompt as a
convenient way to manage OracleBI Discoverer connections. For example, you might
want to create a public OracleBI Discoverer connection for an OLAP data source
without having to use the Connect to OracleBI Discoverer page in OracleBI Discoverer.
To run a command directly at an operating system command prompt:
1.
Display the operating system command prompt.
2.
Type or enter a command.

For example, to create a public OracleBI Discoverer connection for an OLAP data
source on Windows, you might enter the following command:
capi.bat connect orcladmin/tiger -create_conn -cname "Analyze
Sales Q1" -cdesc "Analyze Sales First Quarter" AppsSSOEnabled
"false" -type "public" -olap "true" -apps "false" -dbuser
"jchan" -dbpasswd "12345" -dbname "host1:1521:DB2"
-showdetails "true"
9.5.12.11 How to Run Multiple Commands Stored in an Operating System Command File You
run multiple commands stored in an operating system command file as a convenient
way to manage OracleBI Discoverer connections. For example, you might want to
create a set of public OracleBI Discoverer connections without having to use
Application Server Control.
You create OracleBI Discoverer Connections API commands in a Windows *.bat file or
a UNIX *.sh file that is stored in the util directory on the Oracle Business Intelligence
middle-tier machine. For example, on Windows, you might create a batch file called
create_connections.bat in <ORACLE_HOME>\discoverer\util\create_
connections.bat.
113
You enter OracleBI Discoverer Connections API commands in a command file (one
command per line) as follows:
on Windows, prefix each command with 'call' followed by a space, as follows:

call capi.bat -connect orcladmin/<orcladmin password> <-command> <mandatory
command modifiers> [optional command modifiers]
on UNIX, prefix each command with './', as follows:

./capi.sh -connect orcladmin/<orcladmin password> <-command> <mandatory
command modifiers> [optional command modifiers]
For example, to create three OracleBI Discoverer connections called 'Analyze Sales Q1',
'Analyze Sales Q2', and 'Analyze Sales Q3' on Windows, a command file might contain
the following text:
call capi.bat connect orcladmin/tiger -create_conn -cname
"Analyze Sales Q1" -cdesc "Analyze Sales First Quarter"
AppsSSOEnabled "false" -type "public" -olap "false" -apps
"false" -dbuser "jchan" -dbpasswd "12345" -dbname "db1"
-showdetails "true"
"Analyze Sales Q2" -cdesc "Analyze Sales Second Quarter"
-showdetails "true"
"Analyze Sales Q3" -cdesc "Analyze Sales Third Quarter"
-showdetails "true"
To run multiple commands stored in an operating system command file:
1.
Create a command file in the directory in which the OracleBI Discoverer

Connections API is installed, as follows:
on Windows, create a batch (*.bat) file (for example, <ORACLE_

HOME>\discoverer\util\create_connections.bat)
on UNIX, create a script (*.sh) file (for example, <ORACLE_
HOME>/discoverer/util/create_connections.sh)
2.
Enter (or copy) the OracleBI Discoverer Connections API commands into the
command file.
3.
Execute the command file.

For example, you might open a command prompt, type the name of the command
file, and then press Enter.
9.5.12.12 How to Create, Edit, and Delete OracleBI Discoverer Connections This section
explains how to create, edit, and delete OracleBI Discoverer connections, and contains
the following topics:
Creating a Private OracleBI Discoverer Connection for a Relational Data Source
Creating a Public OracleBI Discoverer Connection for a Relational Data Source
Creating a Private OracleBI Discoverer Connection for an OLAP Data Source
114
Creating a Public OracleBI Discoverer Connection for an OLAP Data Source

Creating a Private OracleBI Discoverer Connection for an Oracle Applications
Data Source
Creating a Public OracleBI Discoverer Connection for an Oracle Applications Data
Source
Updating a Private OracleBI Discoverer Connection for a Relational Data Source
Deleting a Private OracleBI Discoverer Connection for a Relational Data Source
Note: This section does not cover every task that you might undertake using the
OracleBI Discoverer Connections API. For comprehensive reference information about
available commands, see Section 9.5.12.13, "OracleBI Discoverer Connections API
Command Reference".
Creating a Private OracleBI Discoverer Connection for a Relational Data Source
You create a private OracleBI Discoverer connection for a relational data source to
enable an end user to start OracleBI Discoverer and analyze relational data without
entering login details.
To create a private OracleBI Discoverer connection for a relational data source:
1.
Enter a command based on the following syntax:

capi.bat | capi.sh -connect orcladmin/<orcladmin password> -create_conn -cname
<"Discoverer connection name"> [-cdesc <"Discoverer connection description">] -sso_
user <"Single Sign-On user name"> -AppsSSOEnabled "false" -type "private" -olap
"false" -apps "false" -dbuser <"Database user name"> -dbpasswd <"Database
password"> -dbname <"Database name"> -eul <"End User Layer name">
[-showdetails <"true" | "false">] [-locale <"Locale">]
The following example command creates a private OracleBI Discoverer connection
for a relational data source on Windows.
Sales" -cdesc "Analyze Sales First Quarter" -sso_user "jchan"
AppsSSOEnabled "false" -type "private" -olap "false" -apps
"false" -dbuser "jchan" -dbpasswd "12345" -dbname "db1" -eul
"Video Stores" -showdetails "true" -locale "EN_US"
Creating a Public OracleBI Discoverer Connection for a Relational Data Source

You create a public OracleBI Discoverer connection for a relational data source to
enable end users to start OracleBI Discoverer and analyze relational data without
To create a public OracleBI Discoverer connection for a relational data source:
1.

<"Discoverer connection name"> [-cdesc <"Discoverer connection description">]
-AppsSSOEnabled "false" -type "public" -olap "false" -apps "false" -dbuser
<"Database user name"> [-dbpasswd <"Database password">] -dbname <"Database
name"> -eul <"End User Layer name"> [-showdetails <"true" | "false">] [-locale
<"Locale">]
The following example command creates a public OracleBI Discoverer connection
for a relational data source on Windows.
115

Sales" -cdesc "Analyze Sales First Quarter" AppsSSOEnabled
"false" -type "public" -olap "false" -apps "false" -dbuser
"jchan" -dbpasswd "12345" -dbname "db1" -eul "Video Stores"
-showdetails "true" -locale "EN_US"
Creating a Private OracleBI Discoverer Connection for an OLAP Data Source
You create a private OracleBI Discoverer connection for an OLAP data source to enable
an end user to start OracleBI Discoverer and analyze multi-dimensional data without
To create a private OracleBI Discoverer connection for an OLAP data source:
1.

"true" -apps "false" -dbuser <"Database user name"> -dbpasswd <"Database
password"> -dbname <"Database name"> [-showdetails <"true" | "false">] [-locale
<"Locale">]
for an OLAP data source on Windows.
AppsSSOEnabled "false" -type "private" -olap "true" -apps
"false" -dbuser "jchan" -dbpasswd "12345" -dbname
"host1:1521:DB2" -showdetails "true" -locale "EN_US"
Creating a Public OracleBI Discoverer Connection for an OLAP Data Source

You create a public OracleBI Discoverer connection for an OLAP data source to enable
end users to start OracleBI Discoverer and analyze multi-dimensional data without
Public connections are not supported with OracleBI Discoverer Plus OLAP. However,
you can use public connections with OracleBI Discoverer Viewer and OracleBI
Discoverer Portlet Provider to access worksheets that you have created with OracleBI
Discoverer Plus OLAP.
To create a public OracleBI Discoverer connection for an OLAP data source:
1.

-AppsSSOEnabled "false" -type "private" -olap "true" -apps "false" -dbuser
<"Database user name"> -dbpasswd <"Database password"> -dbname <"Database
name"> [-showdetails <"true" | "false">] [-locale <"Locale">]
for an OLAP data source on Windows.
"false" -type "public" -olap "true" -apps "false" -dbuser
"jchan" -dbpasswd "12345" -dbname "host1:1521:DB2"
116
Creating a Private OracleBI Discoverer Connection for an Oracle Applications Data Source
You create a private OracleBI Discoverer connection for an Oracle Applications data
source to enable an end user to start OracleBI Discoverer and analyze Oracle
Applications data without entering login details.
To create a private OracleBI Discoverer connection for an Oracle Applications data
source:
1.

user <"Single Sign-On user name"> -AppsSSOEnabled "true" | "false" -type
"private" -olap "false" -apps "true" -dbuser <"Database user name"> [-dbpasswd
<"Database password">] -dbname <"Database name"> -eul <"End User Layer name">
-resp <"Oracle Applications Responsibility"> -sg <"Oracle Applications Security
Group"> [-showdetails <"true" | "false">] [-locale <"Locale">]
for an Oracle Applications data source on Windows.
AppsSSOEnabled "true" -type "private" -olap "false" -apps
"true" -dbuser "jchan" -dbpasswd "12345" -dbname "db1" -eul
"HR" -resp "HR Manager" -sg "US HR Security Group"
Note: A database password (that you specify using the -dbpasswd command
modifier) is mandatory in a non-OracleAS Single Sign-On installation, but optional in
an OracleAS Single Sign-On installation.
Creating a Public OracleBI Discoverer Connection for an Oracle Applications Data Source
You create a public OracleBI Discoverer connection for an Oracle Applications data
source to enable end users to start OracleBI Discoverer and analyze Oracle
Applications data without entering login details.
To create a public OracleBI Discoverer connection for an Oracle Applications data
source:
1.

-AppsSSOEnabled "true" | "false" -type "private" -olap "false" -apps "true" -dbuser
<"Database user name"> [-dbpasswd <"Database password">] -dbname <"Database
name"> -eul <"End User Layer name"> -resp <"Oracle Applications Responsibility"> -sg
<"Oracle Applications Security Group"> [-showdetails <"true" | "false">] [-locale
<"Locale">]
for an Oracle Applications data source on Windows.
"true" -type "public" -olap "false" -apps "true" -dbuser
"jchan" -dbpasswd "12345" -dbname "db1" -eul "HR" -resp "HR
Manager" -sg "US HR Security Group" -showdetails "true"
-locale "EN_US"
117
Updating a Private OracleBI Discoverer Connection for a Relational Data Source

You update a private OracleBI Discoverer connection for a relational data source to
change the login details of an OracleBI Discoverer connection.
To update a private OracleBI Discoverer connection for a relational data source:
1.

capi.bat | capi.sh -connect orcladmin/<orcladmin password> -update_conn -cname
"false" -apps "false" -dbuser <"Database user name"> [-dbpasswd <"Database
password">] -dbname <"Database name"> -eul <"End User Layer name">
[-showdetails <"true" | "false">] [-locale <"Locale">]
The following example command changes the name of the End User Layer for a
private OracleBI Discoverer connection for a relational data source to
RegionalSales on Windows:
capi.bat connect orcladmin/tiger -update_conn -cname "Analyze
AppsSSOEnabled "false" -type "private" -olap "false" -apps
"false" -dbuser "jchan" -dbpasswd "12345" -dbname "db1" -eul
"RegionalSales" -showdetails "true" -locale "EN_US"
Deleting a Private OracleBI Discoverer Connection for a Relational Data Source

You delete a private OracleBI Discoverer connection for a relational data source to
remove a connection from an OracleBI Discoverer end users connection list.
To delete a private OracleBI Discoverer connection for a relational data source:
1.

capi.bat | capi.sh -connect orcladmin/<orcladmin password> -delete_conn -cname
<"Discoverer connection name"> -AppsSSOEnabled "false" -sso_user <"Single
Sign-On user name"> -type "private"
The following example command deletes a private OracleBI Discoverer connection
for a relational data source on Windows:
capi.bat connect orcladmin/tiger -delete_conn -cname "Analyze
Sales" AppsSSOEnabled "false" -sso_user "jchan" -type
"private"
9.5.12.13 OracleBI Discoverer Connections API Command Reference

This section contains detailed reference information about each command in the
OracleBI Discoverer Connections API, and contains the following topics:
-connect
-create_conn
-update_conn
-delete_conn
-connect
Use this command to identify the orcladmin user as a prerequisite to running a
-create_conn, -update_conn, or -delete_conn command.
118
Information
Details
Syntax:
-connect orcladmin/<orcladmin password>
Examples:
-connect orcladmin/tiger
For more command examples, see Section 9.5.12.12, "How to
Create, Edit, and Delete OracleBI Discoverer Connections".
-create_conn
Use this command to create a new OracleBI Discoverer connection that end users can
use to start OracleBI Discoverer.
Information
Details
Syntax:
-create_conn <command modifiers>
Command modifiers:
-apps <"true" | "false">

-AppsSSOEnabled <"true" | "false">
-cdesc <"Discoverer connection description">
-cname <"Discoverer connection name">
-dbname <"Database name">
-dbpasswd <"Database password">
-dbuser <"Database user name">
-eul <"End User Layer name">
-locale <"Locale">
-olap <"true" | "false">
-resp <"Oracle Applications Responsibility">
-sg <"Oracle Applications Responsibility Security Group">
-showdetails <"true" | "false">
-sso_user <"Single Sign-On user name">
-type <"private" | "public">
Examples:
For command examples, see Section 9.5.12.12, "How to

-update_conn
Use this command to update the details of an existing OracleBI Discoverer connection.
Information
Details
Syntax:
-update_conn <command modifiers>
119
Information
Details
Command modifiers:

-locale <"Locale">
-sg <"Oracle Applications Responsibility Security Group">
Examples:
For command examples, see Section 9.5.12.12, "How to

-delete_conn
Use this command to permanently remove an existing OracleBI Discoverer connection.
Information
Details
Syntax:
-delete_conn <command modifiers>
Command modifiers:

Examples:
For a command example, see Deleting a Private OracleBI

Discoverer Connection for a Relational Data Source.
9.5.12.14 OracleBI Discoverer Connections API Comment Modifier Reference This section
contains detailed reference information about each command modifier in the OracleBI
Discoverer Connections API, and contains the following topics:
-apps
-AppsSSOEnabled
-cdesc
-cname
-dbname
-dbpasswd
-dbuser
-eul
120
-locale
-olap
-resp
-sg
-showdetails
-sso_user
-type
-apps
Use this command modifier to specify whether anOracleBI Discoverer connection
accesses an Oracle Applications End User Layer.
Information
Details
Syntax:
Optional or Mandatory:
Mandatory
Notes:
If -apps is set to true, then you must also set

-AppsSSOEnabled to "true".
Examples:
-apps "true"
-AppsSSOEnabled
Use this command modifier to specify whether OracleAS Single Sign-On is enabled.
Information
Details
Syntax:
Mandatory
Notes:
If -AppsSSOEnabled is set to true, then you must also set

-apps to "true".
Examples:
-AppsSSOEnabled "false"
For an example of creating a public OracleBI Discoverer
connection in an OracleAS Single Sign-On installation, see
Creating a Public OracleBI Discoverer Connection for an
Oracle Applications Data Source.
-cdesc
Use this command modifier to specify a description for an OracleBI Discoverer
connection. For example, you might use a description to inform users which sales
region they can analyze when they select the connection to start OracleBI Discoverer.
The description that you specify is displayed in the Description column on the
Connect to OracleBI Discoverer page.
Information
Details
Syntax:
Optional
121
Information
Details
Notes:
The description must be between 1 and 200 characters in

length.
If you create an OracleBI Discoverer connection without
specifying a description using -cdesc, then the Description
column on the Connect to OracleBI Discoverer page is
blank.
If you update an OracleBI Discoverer connection without
specifying a description using -cdesc, then the existing
description (if any) is maintained.
Examples:
-cdesc "Analyze sales for the Eastern

region"
-cname
Use this command modifier to specify a connection name. If you are creating an
OracleBI Discoverer connection, then use this command modifier to specify a unique
name that you want to use to identify the connection.
The connection name that you specify is displayed in the Name column on the
Connect to OracleBI Discoverer page.
Information
Details
Syntax:
Mandatory
Notes:
The name must be between 1 and 1000 characters in length.

If you are updating or deleting an OracleBI Discoverer
connection, then ensure that you:
Examples:
Specify the connection name correctly (including initial

capitalization and spaces where these appear in the
connection name).
Specify the connection type correctly using the -type
command modifier (two different OracleBI Discoverer
connections can have the same name if one is a public
OracleBI Discoverer connection and one is a private
OracleBI Discoverer connection).
-cname "Eastern First Quarter Sales"
-dbname
Use this command modifier to specify the database that is used by an OracleBI
Discoverer connection.
Information
Details
Syntax:
Mandatory
122
Information
Details
Notes:
For an OracleBI Discoverer connection to a relational or

Oracle Applications data source, the database that you
specify using -dbname must meet one of the following
conditions:
The name must be included in the tnsnames.ora file on
the machine on which the OracleBI Discoverer
Connections API program is installed.
The name must include the full database details, such

as address, protocol, port, and SID.
For example (DESCRIPTION = (ADDRESS_LIST =

(ADDRESS = (PROTOCOL = TCP)(HOST =
hostname.organization.com)(PORT = 1523)))
(CONNECT_DATA = (SID = VIS)))
For an OracleBI Discoverer connection to an OLAP data
source, the database that you specify using -dbname must
be in the following format:
host:port:SID
where:
host is the machine hosting the database containing the
data
port is the TNS listener port
SID is the database system identifier
For an OracleBI Discoverer connection to an OLAP data

source, the SID must be in uppercase. For more information,
contact the database administrator.
Examples:
-dbname "db1" (for a relational data source)

-dbname "host1:1521:DB2" (for an OLAP data source)
-dbpasswd
Use this command modifier to specify the database password for the database user
name that you specify using the -dbuser command modifier.
Information
Details
Syntax:
The -dbpasswd command modifier is mandatory when

you create or edit a private OracleBI Discoverer
connection in a non-OracleAS Single Sign-On installation.
The -dbpasswd command modifier is optional in the
following cases:
You create or edit a public OracleBI Discoverer

connection.
You create or edit a private OracleBI Discoverer
connection in an OracleAS Single Sign-On
installation.
For an example, see Section , "Creating a Private
OracleBI Discoverer Connection for an Oracle
Applications Data Source".
123
Information
Details
Notes:
When the -dbpasswd command modifier is optional:
Examples:
If you do not specify a database password using

-dbpasswd, then end users are prompted for a
password when they select the connection.
If you do specify a database password using
-dbpasswd, then end users are not prompted for a
password when they select the connection.
-dbpasswd "12345"
-dbuser
Use this command modifier to specify the database user name (or Oracle Applications
user) that is used by an OracleBI Discoverer connection.
Information
Details
Syntax:
Mandatory
Notes:
If you are creating or updating a private OracleBI

Discoverer connection, then ensure that you also specify
the OracleAS Single Sign-On user name correctly using the
-sso_user command modifier.
Examples:
-dbuser "jchan"
-eul
Use this command modifier to specify an End User Layer for an OracleBI Discoverer
connection to a relational or Oracle Applications data source.
Information
Details
Syntax:
This command modifier is mandatory for an OracleBI

Discoverer connection to a relational or Oracle
Applications data source.
Do not use this command modifier for an OracleBI
Discoverer connection to an OLAP data source.
Notes:
End User Layer names are case-sensitive. For example, you

must specify an End User Layer called VIDEO5 as
"VIDEO5", not "Video5" or "video5".
Examples:
-eul "Video Stores Analysis"
-locale
Use this command modifier to specify a language and country for an OracleBI
Discoverer connection (using a standard ISO language code and country code).
Information
Details
Syntax:
-locale <"Language Code_Country Code">
Optional
124
Information
Details
Notes:
If you do not specify a locale, then OracleBI Discoverer

uses the locale specified in the end users Web browser.
Examples:
-locale "EN_US"
-olap
Use this command modifier to specify that an OracleBI Discoverer connection is for an
OLAP data source.
Information
Details
Syntax:
Mandatory
Notes:
None.
Examples:
-olap "true"
-resp
Use this command modifier to specify an Oracle Applications Responsibility (for
example, HR Manager) for an OracleBI Discoverer connection.
Information
Details
Syntax:

Discoverer connection to an Oracle Applications data
source.
Discoverer connection to a relational or OLAP data
source.
Notes:
None.
Examples:
-resp "HR Manager"
-sg
Use this command modifier to specify an Oracle Applications Security Group (for
example, US HR Security Group) for an OracleBI Discoverer connection.
Information
Details
Syntax:
-sg <"Oracle Applications Security Group">

Discoverer connection to an Oracle Applications data
source.
Discoverer connection to a relational or OLAP data source.
Notes:
None.
Examples:
-sg "US HR Security Group"
125
-showdetails
Use this command modifier to specify whether you want to enable OracleBI
Discoverer end users to view login details for an OracleBI Discoverer connection on
the Connect to OracleBI Discoverer page (and in the About dialog in OracleBI
Discoverer Plus).
Information
Details
Syntax:
Optional
Notes:
If you do not use the -showdetails command modifier, then

OracleBI Discoverer end users can view login details by
default.
Examples:
-showdetails "false"
-sso_user
Use this command modifier to specify an OracleAS Single Sign-On user name for a
private OracleBI Discoverer connection. This command modifier enables you to
provide private OracleBI Discoverer connections for authenticated OracleAS Single
Sign-On users.
Information
Details
Syntax:
This command modifier is mandatory for a private

OracleBI Discoverer connection.
Do not use this command modifier for a public OracleBI
Discoverer connection.
Notes:
To create a private OracleBI Discoverer connection, you

must also set the value of -type to "private".
Examples:
-sso_user "jchan"
-type
Use this command modifier to specify whether an OracleBI Discoverer connection is
public or private. For more information about public and private OracleBI Discoverer
connections, see Section 9.5.12.1, "What is an OracleBI Discoverer Connection?".
Information
Details
Syntax:
-type "public" | "private"
Mandatory
Notes:
To create a private OracleBI Discoverer connection using

the OracleBI Discoverer Connections API, OracleAS Single
Sign-On must be enabled on the Oracle Business
Intelligence installation.
If you create a private OracleBI Discoverer connection, then
you must also specify an OracleAS Single Sign-On user
name using -sso_user.
Examples:
-type "public"
126
9.6 Oracle Business Intelligence Issues and Workarounds

This section describes general issues and workarounds for Oracle Business Intelligence
products. It contains the following topics:
Section 9.6.1, "Applying Patch Set to Oracle Business Intelligence Developer Suite
Release 10.1.2.x"
Section 9.6.2, "Permission Issue on .apachectl and webcached Files"
Section 9.6.3, "Manually Update Discoverer Catalog"
Section 9.6.4, "Updated Samples Available"
Section 9.6.5, "Updated Translated Help Systems Available"
Section 9.6.6, "New Configuration Setting for Parameter Values in OracleBI

Discoverer Plus"
Section 9.6.7, "OracleBI Discoverer Plus Applet Not Overwritten Within Client Sun
Java Plug-in"
Section 9.6.8, "Issue with Attributes Listed on Conditions Tab in Query Editor"
Section 9.6.9, "Corrections to Release Notes"
Section 9.6.10, "Improving Scrolling Behavior in Oracle Discoverer Plus"
Section 9.6.11, "Enable Selection of Oracle Discoverer Viewer Data to Clipboard"
Section 9.6.12, "Enable Oracle Discoverer Portlets to Post URL as Tracking Link
Data"
Section 9.6.13, "Define Rows and Columns in Oracle Discoverer Worksheet Portlet
When Called From List of Worksheets Portlet"
Section 9.6.14, "Define the Amount of Databody to Display in Wide Crosstab
Reports"
Section 9.6.15, "Workaround to Allow Users to Connect to Oracle Discoverer Using
Connect Strings"
Section 9.6.16, "Workaround for Issues with Preference VALIGN=CENTER"
Section 9.6.17, "Workaround for Seeing Different Fonts in Oracle Discoverer
Workbook After Upgrading from Oracle Discoverer 9"
Section 9.6.18, "New Setting Enables Page Navigation in Oracle Discoverer
Viewer"
Section 9.6.19, "Workaround When Getting 'invalid Username / Password
Combination"
Section 9.6.20, "New Configuration Settings for Oracle Discoverer for OLAP"
Section 9.6.21, "Workaround When Having Problems Prompting Saving a
Workbook in Oracle Discoverer Viewer"
Section 9.6.22, "Workaround to Private Connections Not Showing After Creating
with Connections API"
9.6.1 Applying Patch Set to Oracle Business Intelligence Developer Suite Release
10.1.2.x
Ensure that Microsoft Excel is installed on the Oracle Business Intelligence Developer
Suite release 10.1.2.x server before applying OracleAS 10g Patch Set 3 (10.1.2.3.0) to the
127
server. If Microsoft Excel is not on the server before applying the patch, then the OLAP
- Spreadsheet Addin will not work with Microsoft Excel.
9.6.2 Permission Issue on .apachectl and webcached Files

You may recieve error messages about writing to the webcached and .apachectl files
when applying OracleAS 10g Patch Set 3 (10.1.2.3.0) to an Oracle Business Intelligence
installation. To correct the permission problem on the files during patch application,
do the following. In the procedure, iasinst is the user ID who performed the
installation.
1.
Keep the installer open.
2.
Open a shell and log in as the root user.
3.
Change to the ORACLE_HOME/Apache/Apache/bin directory.
4.
Change the ownership of the apachectl file to the iasinst user, as follows:
chown iasinst .apachectl
5.
Change to the ORACLE_HOME/webcache/bin directory.
6.
Change the ownership of the webcached files to the iasinst user, as follows:
chown iasinst webcached
7.
In the installer, select the Error Message box, and click Retry. The installation
should continue and complete successfully.
9.6.3 Manually Update Discoverer Catalog

Bug 5198004
If you want to use the features that are available in this patch and that use the
Discoverer Catalog, then you must update the Catalog by running scripts. See
Section 9.5.2, "Discoverer Catalog Update for Oracle Business Intelligence" for the
procedure that describes how to perform the Catalog update after you apply the patch.
9.6.4 Updated Samples Available

Bug 5148883
To assist you in working with the new features that are available in this patch, new
and updated sample schemas called SH_OLAP and CS_OLAP are available. You can
download these sample schemas and information on installing and working with
them, as described in the following list:
SH_OLAP schema has the following characteristics:

-
It was created in Standard Form in Oracle Database 10g Release 2. Therefore, it

supports all the features of the 10.1.2.2 release, including calculated members
and write-back in OracleBI Spreadsheet Add-In.
You must install this schema only on a supported version of Oracle Database
10g Release 2.
It does not support forecasting functionality, so you cannot use it with

OracleBI Beans sample applications that previously worked with the CS_
OLAP schema. Forecasting support will be added to this schema in a future
release.
You can access the file for the schema using the following URL:
128
http://download.oracle.com/otndocs/products/bi/samples/bi_10_1_
2_2_samples.zip
CS_OLAP schema has the following characteristics:

-
It was not created in Standard Form in Oracle Database 10g Release 2.

Therefore, it does not support all the features of the 10.1.2.2 release.
It has been updated since its last release with several bug fixes and has been
modified to include more recent labels for the Time dimension. The
installation scripts have been modified, and they no longer support Oracle9i
Release 2 Database. You must install this schema only on a supported version
of Oracle Database 10g Release 1 or higher.
It includes metadata and structures in the analytic workspace to support

forecasting. Therefore, it can support legacy OracleBI Beans sample
applications, such as Executive Insight.
You can access the file for the schema using the following URL:
http://download.oracle.com/otndocs/products/bi/samples/bi_10_1_
2_v2_samples.zip
9.6.5 Updated Translated Help Systems Available

The OracleBI Discoverer Plus OLAP and OracleBI Spreadsheet Add-In Help files have
been updated for 10.1.2.2. When you install this patch set, new Help files for the
languages that you originally selected for OracleBI Discoverer Plus OLAP when you
installed 10.1.2 will automatically be installed. If you want to install Help files for
languages that you had not originally selected, then follow the instructions in Section
4.7.1 of the Oracle Business Intelligence Installation Guide at
http://www.oracle.com/technology/documentation/bi.html
Section 4.7.1 mentions that the OracleBI Discoverer Plus Help files are available as JAR
files in the /extras directory on the CD-ROM and DVD for Oracle Business
Intelligence. However, for the 10.1.2.3 patch set, you can access a ZIP file that contains
all the newly translated JAR files from the following location:
http://www.oracle.com/technology/documentation/discoverer.html
After you obtain the JAR files from Oracle Technology Network, you can use the
instructions in the Oracle Business Intelligence Installation Guide for installing the
translated Help.
9.6.6 New Configuration Setting for Parameter Values in OracleBI Discoverer Plus
Bug 4718749 and 5336806
OracleBI Discoverer Plus currently prompts for parameter values differently from the
way that OracleBI Discoverer Viewer prompts for parameter values. The intended
functionality in OracleBI Discoverer Plus and OracleBI Discoverer Viewer is that the
only time users are prompted to enter parameter values is when they initially open
and run a worksheet or they explicitly choose to edit parameter values. In OracleBI
Discoverer Plus by default, users are also prompted for parameter values when they
choose to refresh or drill in a worksheet.
You can change this default behavior by adding the
genericParameterPromptOnRefresh=false setting in the pref.txt file. If this
setting has a value of false, then users are not prompted for parameter values unless
they open and run a worksheet or explicitly invoke the Edit Parameter Values dialog.
129
To use this setting, edit the pref.txt file and add the
genericParameterPromptOnRefresh setting in the Generic Properties section.
This file is located in the ORACLE_HOME/discoverer/util directory.
9.6.7 OracleBI Discoverer Plus Applet Not Overwritten Within Client Sun Java Plug-in
Bug 4766174
When a client machine with cached content connects to a patched server with OracleBI
Discoverer, the Sun Java Plug-in cache content may still have the earlier OracleBI
Discoverer Plus Applet version. If this is the case, then a Java Console exception, or the
following error may appear:
An internal Server Error occurred while trying to perform the
current operation. This could happen due to network errors or
memory problems. If this persists contact your Discoverer
manager.
To fix the error, clear the client plug-in cache, and reconnect to the server.
9.6.8 Issue with Attributes Listed on Conditions Tab in Query Editor

Bug 5243174
There is a known issue that affects the display of attributes on the Conditions tab of
the Dimensions panel in the Query Editor for OracleBI Discoverer Plus OLAP,
OracleBI Spreadsheet Add-In, and OracleBI Beans. Suppose that you are working in
the Query Editor, access the Dimension panel and select a hierarchy, then select the
Available Conditions tab. In the Conditions tab, drill in the Match folder. If you can
create conditions with attributes, you will see a line for attributes. If you click the
hyperlink for an attribute name, you will see a drop-down box that lists all the
attributes for the dimension, rather than only those attributes that are associated with
the hierarchy that you selected.
This issue has no workaround.
9.6.9 Corrections to Release Notes

Bug 3884041
Previous versions of the Oracle Business Intelligence and Oracle Business Intelligence
Tools Release Notes included an item that stated that when printing a worksheet that
contains large numbers in the data cells, the string ####### may be printed instead of
the actual numbers. This issue has been fixed and the numbers are now visible.
9.6.10 Improving Scrolling Behavior in Oracle Discoverer Plus

Bug 5450764
Three new preference settings can be added to pref.txt. These should be put under the
[Generic Properties] section in pref.txt.
genericStandardFetchSpan. This is the number of rows to be fetched at a time in

Plus.
genericDefaultCacheCapacity. This is the default capacity of cache to hold the
rows above.
genericMaxCacheCapacity. The maximum capacity of the cache.
The following should always be true for a better performance:
130
genericMaxCacheCapacity > genericDefaultCacheCapacity >=

genericStandardFetchSpan
For example:
genericStandardFetchSpan = 1000
genericDefaultCacheCapacity = 1000
genericMaxCacheCapacity = 1000
9.6.11 Enable Selection of Oracle Discoverer Viewer Data to Clipboard

A new configuration setting enableDataSelection enables Viewer data to be copied to
the clipboard has been added to configuration.xml. When set to "true" users can
select and copy to the clipboard as they would on a normal HTML page. When set to
"false" enableDataSelection disables data selection. The default value for this
parameter is "true". This parameter should be added to the viewer section of
configuration.xml.
9.6.12 Enable Oracle Discoverer Portlets to Post URL as Tracking Link Data
A new configuration setting named enableDrillUrl="true", that enables Oracle
Discoverer Portlets to post URL as tracking link data, can be added to
configuration.xml. When set to "true," drilling is enabled on portlet objects.
This setting can be added to the portlet section of configuration.xml.
9.6.13 Define Rows and Columns in Oracle Discoverer Worksheet Portlet When Called
From List of Worksheets Portlet
Two optional configuration settings, numColsForLOW and numRowsForLOW can be
added to the portlet section of  in
configuration.xml. For example:
<portlet showPivotLabel="true" logKey="disco.portlet.fatal" logLevel="error"
pickerCompatibleVersions="10.1.2" maxDataRows="1000" numColsForLOW="0"
numRowsForLOW="25">
When you set numColsForLOW="0", then all columns in the underlying worksheet are
displayed. When you set numRowsForLOW="0", then all rows in the underlying
worksheet are displayed. For performance reasons, you should not set these values to
0 in case the number of columns or rows in the worksheet is too large.
These parameters are optional, but if they are not specified in configuration.xml,
default values (to display 6 columns and 25 rows) are applied. The minimum number
of rows or columns that can be displayed has been changed from 1 to 0. If you set the
number of rows to display to 0 in the Single Worksheet Viewer, then all rows in the
worksheet are displayed (this rule also applies to the number of columns). In previous
releases, the minimum value for the number of rows or columns to display was 1.
9.6.14 Define the Amount of Databody to Display in Wide Crosstab Reports

Bug 5117216.
Two new preference settings that determine the amount of databody displayed when
row or column headers are very long have been added to pref.txt. The preferences are
genericDatabodyColumnWidth and genericDatabodyRowWidth. These
preference settings control column and row width respectively. These preference
settings come into effect only if row headers and column headers are big enough, and
if the preference genericHeaderScroll is set to true.
131
9.6.15 Workaround to Allow Users to Connect to Oracle Discoverer Using Connect

Strings
The following error message is displayed when a user tries to connect using connect
strings:
A connection error has occurred. Connect string not allowed specify the TNSNames
alias
This error message is only applicable to the English language, other languages will
display error code 3965 for the same error.
To allow users to connect to Oracle Discoverer using connect strings, do the following:
1.
Stop OPMN services
2.
Navigate to the ORACLE_HOME/opmn/conf directory.
3.
Backup or copy the opmn.xml file. For example:

cp opmn.xml opmn.xml_orig
4.
Edit the opmn.xml file to add the environment variable as follows:

<variable id="DISCOVERER_ALLOW_DB_CONNECT_STRING" value="YES"/>
In the following two Oracle Discoverer environment sections:

<ias-instance id=..../>"
<ias-component id="Discoverer">
For example,
<ias-instance id="10122_Bi.xyz-pc.idc.oracle.com">
<environment>
<variable id="DISCOVERER_ALLOW_DB_CONNECT_STRING value="YES"/>
</environment>
<ias-component id="Discoverer">
<environment>
<variable id="DISCOVERER_ALLOW_DB_CONNECT_STRING" value="YES"/>
</environment>
5.
Save the opmn.xml file.
6.
Start the OPMN services.
9.6.16 Workaround for Issues with Preference VALIGN=CENTER

Bug 5887565
A new Boolean preference setting UseAdminDefinedFormat determines whether to
use the formatting for individual columns in the worksheet as defined by the user in
Oracle Discoverer Administrator, or as set in pref.txt. A value of 1 (the default) is to
use the formatting defined by the user through Oracle Discoverer Administrator. A
value of 0 is to use formatting defined by the preference server in pref.txt. This
preference is added under the [Application] section of pref.txt.
9.6.17 Workaround for Seeing Different Fonts in Oracle Discoverer Workbook After
Upgrading from Oracle Discoverer 9
Bug 5902903
A new preference setting genericPreferredZoomFactor enables a zooming factor for
the data font displayed in a Oracle Discoverer Plus worksheet. The default value is 1
132
and the range of possible values is from 0 to 2. A value less than or equal to zero, and
greater than two is not allowed. If a value outside the range is used, then the default
value will be used. This preference setting is added under the [generic properties]
section of pref.txt. For example:
[generic properties] genericPreferredZoomFactor=1.125
You should only use small increments when changing this value, such as between .001
and .01, as even minor changes can have an effect on data font display in Oracle
Discoverer Plus.
9.6.18 New Setting Enables Page Navigation in Oracle Discoverer Viewer

A new page navigation control is available in Viewer that enables a user to easily
navigate to the first, previous, next, last, or a specified worksheet page. The Boolean
setting, pageNavigation was added to configuration.xml.
When pageNavigation is set to true, a page navigation toolbar appears in Viewer
worksheet pages. It was added because non-incremental query when the complete
query result data is returned in a single fetch or increment has to be run to show the
page serial number information correctly, thus resulting in relatively longer show-up
time for a worksheet based on how large the worksheet is the first time it is rendered.
It is recommended to set this parameter to false, because setting it to true makes the
query non-incremental, which is a performance trade-off.
9.6.19 Workaround When Getting 'invalid Username / Password Combination

Bug 5156055
The fix for bug 5156055 requires Visual Studio 2005 to be installed or the Microsoft
Redistributable bundle to support run-time of its files.
If the machine that you are running does not have Microsoft Visual Studio 2005
installed, then install the Microsoft Visual C++ 2005 Redistributable Package (x86) to
ensure you have the proper DLLs. This package can be retrieved in two ways:
Download the installation from

http://go.microsoft.com/fwlink/?linkid=65127&clcid=0x409%20ta
rget=
Run the installation fromVS 2005

installdir\SDK\v2.0\BootStrapper\Packages\vcredist_
x86\vcredist_x86.exe
9.6.20 New Configuration Settings for Oracle Discoverer for OLAP

New configuration settings have been introduced for Oracle Discoverer for OLAP as
follows:
OlapBufferSize
This option takes an integer value, and controls the OLAP API Cursor buffer size.
The default value is 5000. In general, larger values of this option will improve the
performance of very large worksheets. However, it is important to try different
settings to achieve optimum query execution and scroll performance.
AlphabeticalSortingBetweenLevels
This option takes a Boolean value, and affects newly created Alphabetical Sorts for
value-based hierarchies. The default value is ('false').
133
When this option is set to 'true', then newly created Alphabetical Sorts on
selections against value-based hierarchies will result in sorting the dimension
members without regard to the hierarchical order.
When this option is set to 'false', then newly created Alphabetical Sorts on
selections against value-based hierarchies will result in sorting sibling members
alphabetically, but underneath their hierarchical parent members.
CopyDataFlavor
This option can take 3 values - "excel", "text" or "both." This will determine the
data flavour to be copied to clipboard when cells are chosen in crosstab and
copied."excel" will be the default value for this parameter.
ExcludeDuplicateRowsDuringExcelExport and
ExcludeDuplicateColumnsDuringExcelExport
These options take a Boolean value (true or false) and are independent of each
other. The default for both of these options is 'false'. If
'ExcludeDuplicateRowsDuringExcelExport' is set to 'true' duplicate rows present
in the crosstab are not displayed in Excel after export operation.
EnableLevelOffsetBasedTimeCalc'
This option takes a Boolean value (true or false). When this option is set to true, it
enables level offset based non-gregorian time calculations.
The preceding options can be set in configuration.xml in the following location:

ORACLE_HOME/discoverer/config
For example, you could add the following entry before the </plus> tag:
<D4O OlapBufferSize="5000" AlphabeticalSortingBetweenLevels="false"
CopyDataFlavor="excel" ExcludeDuplicateRowsDuringExcelExport='true'
ExcludeDuplicateColumnsDuringExcelExport='true'
EnableLevelOffsetBasedTimeCalc='true'/>
9.6.21 Workaround When Having Problems Prompting Saving a Workbook in Oracle

Discoverer Viewer
Bugs 5719064 and 5962480
Introduced a configurable parameter named worksheetSaveBehavior that should be
added to configuration.xml in the viewer section. To enable the fix for bugs
5719064 and 5962480:
1.
Stop OPMN services.
2.
Navigate to ORACLE_HOME/opmn/conf.
3.
Back up of the opmn.xml file using the following command:

cp opmn.xml opmn.xml_orig).
4.
Edit the opmn.xml file, and search for '<viewer' section and add
worksheetSaveBehavior="<preferred value>". For example:
<viewer queryRefreshPeriod="3000" queryRequestTimeout="1000"
numberOfLOVsToBeDisplayed="100000"
longRequestRefreshPeriod="6000" longRequestTimeout="10000"
userDefinedConnections="true" logLevel="none"
laf="dc_blaf" worksheetSaveBehavior="always_save" defaultLocale="en"
134
disableBrowserCaching="false">
Valid values for worksheetSaveBehavior are -:
never_save
Never save the worksheet unless its saved manually. Do not prompt for
saving.
always_save
Always save the worksheet automatically. Do not prompt for saving
prompt
Always prompt to the user whether to save the sheet or not. This is the default
action.
5.
Save opmn.xml.
6.
Start OPMN Services.
9.6.22 Workaround to Private Connections Not Showing After Creating with

Connections API
After upgrading or implementing Oracle Discoverer on release 10.1.2.2 private
connections are not showing up when created using capi.sh.
The capi.sh script runs without error when creating private connections however,
when the Oracle Discoverer Plus or Viewer page is accessed those connections are not
displayed. To resolve this issue refer to the following link:
https://metalink.oracle.com/metalink/plsql/ml2_
documents.showDocument?p_database_id=NOT&p_id=463346.1
9.7 OracleBI Discoverer Support for OracleAS Single Sign-On in an Oracle

E-Business Suite Environment Issues
The following sections describe documentation errata for OracleBI Discoverer for
OracleAS Single Sign-On in an Oracle E-Business Suite Environment for the
appropriate platforms:
Section 9.7.1, "Documentation Errata Section for OracleBI Discoverer Support for
OracleAS Single Sign-On in an Oracle E-Business Suite Environment for Microsoft
Windows"
OracleAS Single Sign-On in an Oracle E-Business Suite Environment for Sun
Solaris"
OracleAS Single Sign-On in an Oracle E-Business Suite Environment for Linux
x86"
OracleAS Single Sign-On in an Oracle E-Business Suite Environment for AIX 5L
Based Systems"
OracleAS Single Sign-On in an Oracle E-Business Suite Environment for HP-UX
PA RISC"
135
OracleAS Single Sign-On in an Oracle E-Business Suite Environment for HP-UX
Itanium"
9.7.1 Documentation Errata Section for OracleBI Discoverer Support for OracleAS
Single Sign-On in an Oracle E-Business Suite Environment for Microsoft Windows
The 10.1.2.2 release implements OracleBI Discoverer for OracleAS Single Sign-On in an
Oracle E-Business Suite Environment. This implementation requires the following
documentation changes:
In the OracleBI Discoverer Connections Help system, the information for the
'Apply and Connect' button on the 'Account Details: Select User Name' page is
incorrect and should read as follows:
Continue
Use this button to save the details that you have entered on this page.
Certain sections of the following release notes documents must be ignored, as

outlined in the following table:
Part No. B16032-02 - Oracle Business Intelligence Release Notes 10g Release 2
(10.1.2.1) for Microsoft Windows and Solaris Operating System
Part No. B15501-11 - Oracle Application Server Release Notes 10g Release 2
(10.1.2) for Microsoft Windows
The following table outlines that sections to be ignored. The section numbers in the
table are correct as of the specified release notes version. The section numbers might
be different if you use a different version of the release notes.
Section number in Oracle
Business Intelligence
release notes:
Part No. B16032-02
Section number in
Oracle Application
Server release notes
Part No. B15501-11
Account Details: Username

and Password page Help
topic
3.12.4
15.1.9.4
Account Details: Select

Username page Help topic
3.12.5
15.1.9.5
Enter connection details page 3.12.6

Help topic
15.1.9.6
Corrections to the Oracle

Business Intelligence
Discoverer Configuration
Guide
3.13 bullets 2,3,4,5
15.1.10 bullets 1,2,3,4
Discoverer Administration
page Help topic
3.14.8
15.1.11.8
Task steps in the "How do I

create and save login
information in a Discoverer
connection?" Help topic
7.9.5
15.5.8.5
Section Title
136
Single Sign-On in an Oracle E-Business Suite Environment for Sun Solaris
The 10.1.2.2 release implements OracleBI Discoverer for OracleAS Single Sign-On in an
Oracle E-Business Suite Environment. This implementation requires the following
documentation changes:
Continue

(10.1.2.1) for Microsoft Windows and Solaris Operating System
(10.1.2) for Solaris Operating System (SPARC)
The following table outlines that sections to be ignored. The section numbers in the
Section number in
OracleBI release notes
Part No. B16032-02
Section number in
OracleAS release notes
Part No. B14501-11
Account Details:
Username and
Password page Help
topic
3.12.4
14.1.9.4

Username page Help
topic
3.12.5
14.1.9.5
Enter connection details 3.12.6

page Help topic
14.1.9.6
Corrections to the
Oracle Business
Intelligence Discoverer
Configuration Guide
3.13 bullets 2,3,4,5
14.1.10 bullets 1,2,3,4
Discoverer
Administration page
Help topic
3.14.8
14.1.11.8
Section Title
Task steps in the "How 7.9.5

do I create and save
login information in a
Discoverer connection?"
Help topic
14.5.8.5
Single Sign-On in an Oracle E-Business Suite Environment for Linux x86
The 10.1.2.2 release implements OracleAS Single Sign-On functionality for connections
from OracleBI Discoverer in an Oracle E-Business Suite environment. This
implementation requires the following documentation changes:
137
Continue

(10.1.2) for Linux x86
(10.1.2) for Linux x86
The following table outlines the sections to be ignored. The section numbers in the
Section number in
Part No. B19316-06
Section number in
Part No. B19312-10
Account Details:
Username and
Password page Help
topic
3.22.4
17.1.21.4

Username page Help
topic
3.22.5
17.1.21.5

page Help topic
17.1.21.6
Corrections to the
Oracle Business
Configuration Guide
3.23
17.1.22
Discoverer
Administration page
Help topic
3.24.1
17.1.23.1

Help topic
17.5.10.5
Section Title
Single Sign-On in an Oracle E-Business Suite Environment for AIX 5L Based Systems
Continue
138

(10.1.2) for AIX 5L Based Systems
(10.1.2) for AIX 5L Based Systems
Section number in
Part No. B25207-06
Section number in
Part No. B25203-08
Account Details:
Username and
Password page Help
topic
3.21.4
17.1.21.4

Username page Help
topic
3.21.5
17.1.21.5

page Help topic
17.1.21.6
Corrections to the
Oracle Business
Configuration Guide
3.22
17.1.22
Discoverer
Administration page
Help topic
3.23.1
17.1.23.1

Help topic
17.5.10.5
Section Title
Single Sign-On in an Oracle E-Business Suite Environment for HP-UX PA RISC
Continue

139
(10.1.2) for HP-UX PA-RISC
(10.1.2) for HP-UX PA-RISC
Section number in
Part No. B25191-06
Section number in
Part No. B25187-08
Account Details:
Username and
Password page Help
topic
3.21.4
17.1.21.4

Username page Help
topic
3.21.5
17.1.21.5

page Help topic
17.1.21.6
Corrections to the
Oracle Business
Configuration Guide
3.22
17.1.22
Discoverer
Administration page
Help topic
3.23.1
17.1.23.1

Help topic
17.5.10.5
Section Title
Single Sign-On in an Oracle E-Business Suite Environment for HP-UX Itanium
Continue

(10.1.2) for HP-UX Itanium
(10.1.2) for HP-UX Itanium
140
Section number in
Part No. B25199-06
Section number in
Part No. B25195-08
Account Details:
Username and
Password page Help
topic
3.21.4
17.1.21.4

Username page Help
topic
3.21.5
17.1.21.5

page Help topic
17.1.21.6
Corrections to the
Oracle Business
Configuration Guide
3.22
17.1.22
Discoverer
Administration page
Help topic
3.23.1
17.1.23.8

Help topic
17.5.10.5
Section Title
9.8 Oracle Business Intelligence Spreadsheet Add-In Issues and

Workarounds
This section provides release notes for Oracle Business Intelligence Spreadsheet
Add-In (OracleBI Spreadsheet Add-In). It contains the following topics:
Section 9.8.1, "Editing Changes Lost After Cut and Paste"
Section 9.8.2, "Issue with Saving Selections with Insufficient Privileges"
Section 9.8.3, "Toolbar Returns to Default Position"
Section 9.8.4, "Issues with VBA Macros"
Section 9.8.5, "User Files Stored in New Location"
Section 9.8.6, "Issues with Multiple Users Writing to a Partitioned Cube"
Section 9.8.7, "Issues with Multiple Users on a Single Machine"
Section 9.8.8, "Error Message BIA-4085 is Displayed When a Second Analytic

Workspace is Attached"
Section 9.8.9, "Corrections to Release Notes"
9.8.1 Editing Changes Lost After Cut and Paste

Bug 5206779
141
You can lose editing changes in the following situation. You highlight all the cells in a
query, cut the cells, paste the cells to a different location in the same worksheet, and
edit the query. As you edit, the body of the query moves back to its original location,
the edits are lost, and the page controls remain in their new location.
This situation occurs because Excel does not provide OracleBI Spreadsheet Add-In
with enough information about the cells that you moved. To work around this
situation, either refresh the query or save the workbook immediately after the cut and
paste operation and before editing the query.
9.8.2 Issue with Saving Selections with Insufficient Privileges

Bug 5126958
As you work in OracleBI Spreadsheet Add-In, you can save selections to the
Discoverer Catalog. If you try to save a selection to a folder in the Catalog for which
you lack write privileges, then the selection will appear to be saved. However, the
selection is not saved and you will see no warning message to this effect. You will
discover this situation when you try to locate the saved selection.
To work around this issue, save selections only to those folders for which you know
that you have the appropriate privileges.
9.8.3 Toolbar Returns to Default Position

Bug 4897808
By default, the OracleBI toolbar appears docked along the left side of the Excel
window. You can move the toolbar to a different location, undock it, and so on during
an Excel session. After you exit and restart Excel, you will find that, unlike other Excel
toolbars, the OracleBI toolbar has returned to its default location. To work around this
issue, move the toolbar back to the desired position each time that you start Excel.
9.8.4 Issues with VBA Macros

The following list describes issues with VBA macros
Bug 5220564
If you call the BIA_Disconnect() macro and specify a value for the QueryName
argument, then the macro will not disconnect the specified query unless the active
cell is within the query. If you call the BIA_Disconnect() macro without any
arguments, then you will not experience any issue and all queries will be
disconnected.
To work around this issue when you need to specify a query, set the active cell
before calling the BIA_Disconnect() macro.
Bug 5148820
Several keyboard mnemonics have changed on the OracleBI menu. If you wrote
any VBA code that uses the SendKeys command to invoke menu items from the
OracleBI menu, then compare that code against the menu to ensure that it is still
accurate.
9.8.5 User Files Stored in New Location

Bug 5148804
In previous releases, the following files were stored in the installation directory, which
is generally named c:\Program Files\Oracle\BIAddin:
142
oraolapxl.prefs, which contains user preferences.

oraolapxl.con, which contains information about the connections that the user
created.
The files are now stored in the users Application Data directory, which is generally
named c:\Documents and Settings\username\Application
Data\Oracle\BISpreadsheetAddin.
When you install the OracleBI Spreadsheet Add-In release 10.1.2.2 over an existing
installation, these two files are copied to this new location.
9.8.6 Issues with Multiple Users Writing to a Partitioned Cube

Bug 5201012
When multiple users are accessing a read/write query from a partitioned cube and
they are writing back to that same cube, they might see errors about the partitioned
cube such as:
Sheet1!C6 - Object WBDEMO!BUDGET_CUBE_PART_TIME_PRT_TOPVAR is
locked by another user.
This error occurs in the following situations:
When multiple users attempt to save changes to the database by selecting Save
from the File menu. To work around this issue, a user can wait until another user
has finished saving, then the first user can attempt the save operation again.
When multiple users attempt to perform calculation and validation by selecting
Calculate and Validate Now from the OracleBI menu. To work around this issue,
a user can:
-
Perform calculation and validation only in read-only mode.
Wait until another user has finished performing calculation and validation,
then the first user can attempt the operation again.
9.8.7 Issues with Multiple Users on a Single Machine

Bug 5187391
If you and another user are running OracleBI Spreadsheet Add-In on the same
machine, then the other user must manually perform the following steps:
Copy the oraolapxl.prefs and oraolapxl.con files to the other users

Application Data directory, to ensure that you and the other user have your own
copies of these files. See Section 9.8.5, "User Files Stored in New Location".
Manually load OracleBI Spreadsheet Add-In into Excel by choosing Add-Ins from
the Tools menu.
9.8.8 Error Message BIA-4085 is Displayed When a Second Analytic Workspace is

Attached
Bug 5521143
Suppose that you are performing write-back and are using the BIA_SaveData( ) macro.
Suppose further that a second analytic workspace has been attached read-write in that
same session. You might see error message BIA-4085, which states that changes cannot
be saved to the database.
143
You can ignore this error message, because it should not be displayed. The data will be
saved to an analytic workspace that is attached read-write.
9.8.9 Corrections to Release Notes

The following list describes corrections to the Release Notes for 10.1.2.1:
Bug 3584258
The previous release notes for OracleBI Spreadsheet Add-In included the
following information:
"Saved selections and calculations that you create are specific to one query, and
you cannot share them across queries. If you create saved selections and
calculations in a workbook and you want to share those items with another user,
then give that user a copy of the workbook."
With this patch release, the first sentence is no longer true. You can now share
saved selections and calculations across queries in a workbook. See the
"Understanding Storage of Objects" topic in the Help system for complete
information.
Bug 4317412
The previous release notes included a section entitled "Renaming Sheets when
OracleBI Spreadsheet Add-In is not Running". Replace the text in that section with
the following revised text:
Use care when renaming a worksheet that contains an OLAP query in the
following situations:
-
Do not rename a worksheet that contains an OLAP query when you open it on
a PC on which OracleBI Spreadsheet Add-In is not installed or is not running
or on which you have deferred startup of OracleBI Spreadsheet Add-In. If you
rename the worksheet under these circumstances, then OracleBI Spreadsheet
Add-In cannot associate the query on that worksheet with the database when
you next open the worksheet.
You can easily determine whether OracleBI Spreadsheet Add-In is running by
observing the OracleBI menu in Excels menu bar.
If you have manual calculation turned on, then you see a message to remind
you of this setting being on when you start OracleBI Spreadsheet Add-In. By
default, calculation is set to automatic. You change the calculation setting on
the Calculation tab of Excels Options dialog. If you have manual calculation
turned on and you rename a worksheet, then you must press F9 to force a
recalculation and to allow the name change to be recognized.
Bug 4528054
The previous release notes included a section entitled "Issue with Hidden Rows
and Queries Without Data". Replace the text in that section with the following
revised text:
You can specify to hide rows whose values are all NA or whose values are all zero
and all NA. If you specify to hide these rows and create a query that returns no
data, then you might either:
-
See only a cell that contains the text "No Data" in the worksheet.
Be unable to edit the query again.
144
Normally, you can select a cell in the query area and choose Edit Query from the
OracleBI menu to begin the process of editing the query. Suppose you have hidden
rows whose values are all NA and you create a query that returns no data. The
resulting worksheet has all the rows hidden, and OracleBI Spreadsheet Add-In
tries to create a cell that contains the text "No Data".
If you find it impossible to edit the query because the worksheet has no cells with
data and no cell that contains the text "No Data", then work around this issue by
completing the following steps:
1.
Exit Excel without saving changes to the workbook.
2.
Reopen the workbook to restore the query to the point at which it was last
saved.
9.9 Oracle Business Intelligence Discoverer Portlet Provider Issues

This section provides release notes for OracleBI Discoverer Portlet Provider. It contains
Section 9.9.1, "Issue with Changes from OracleBI Discoverer Viewer Not
Displaying in Portal"
Section 9.9.2, "Issue with Item Labels in Crosstab Workbook Not Being Visible"
Section 9.9.3, "New viewerURLForPublicUser Setting"
Section 9.9.4, "New cacheThreshold Configuration Setting"
9.9.1 Issue with Changes from OracleBI Discoverer Viewer Not Displaying in Portal
Bug 5056846
If you change a worksheet in OracleBI Discoverer Viewer and another user displays
that worksheet in a portal, then the user does not see those changes, even with the
Allow Saving Changes made in OracleBI Discoverer Viewer setting enabled. The
user must explicitly refresh the browser to see the changes in the portal. This issue has
no workaround.
9.9.2 Issue with Item Labels in Crosstab Workbook Not Being Visible
Bug 4864454
In versions prior to 10.1.2.2, item labels in crosstab worksheets were not displayed
when the worksheet was included in an OracleBI Discoverer portlet. Starting with
release 10.1.2.2 and later, you can display item labels in a crosstab portlet by editing
the configuration.xml file to include the showPivotLabel="true" setting in the
portlet tag under the  section, as shown in the
following example:
<portlet showPivotLabel="true"
logKey="disco.portlet.fatal"
logLevel="error"
pickerCompatibleVersions="10.1.2"
maxDataRows="1000">
9.9.3 New viewerURLForPublicUser Setting

Bug 4725681
145
In releases of OracleBI Discoverer prior to 10.1.2.0.0, a public user (that is, a user who
accesses a portal page without logging in to OracleBI Discoverer Portlet Provider or
OracleAS Single Sign-On) was not prompted for an OracleAS Single Sign-On
password when clicking the Analyze link in an OracleBI Discoverer portlet. Instead,
OracleBI Discoverer Viewer would open with a worksheet displayed.
OracleBI Discoverer 10.1.2.0.0 introduced the concept of "Single Worksheet Viewer,"
which opens when users click the Analyze link in an OracleBI Discoverer portlet. In
"Single Worksheet Viewer," users can customize the worksheet and save changes back
to the portlet. Because this customization is supported on a per-user basis, OracleBI
Discoverer always asks for the user name and password for OracleAS Single Sign-On.
With OracleBI Discoverer 10.1.2.2 and later, you can use the viewerURLForPublicUser
configuration setting. This setting returns OracleBI Discoverer to the behavior prior to
10.1.2.0.0, in which public users can launch OracleBI Discoverer Viewer (not "Single
Worksheet Viewer") from an OracleBI Discoverer portlet by clicking the Analyze link.
Users no longer must provide the user name and password for OracleAS Single
Sign-On.
The following procedure explains how to use this setting:
1.
Edit the configuration.xml file in the ORACLE_HOME/discoverer/config

directory by adding the viewerURLForPublicUser setting to the portlet tag and
assigning the "normalViewer" value, as shown in the following example:
This line in the configuration file:
<portlet logKey="disco.portlet.fatal" logLevel="error"
pickerCompatibleVersions="10.1.2" maxDataRows="1000">
Is rewritten as:
pickerCompatibleVersions="10.1.2" maxDataRows="1000"
viewerURLForPublicUser="normalViewer">
2.
Reboot Oracle Application Server.
Note the following about this setting:
The "Cancel and return to Portal" option is available only in "Single Worksheet
Viewer." When viewerURLForPublicUser is set, users can return to the portal only
by clicking the Back button in the browser.
This setting affects only public portal pages. If a user logs in to OracleBI
Discoverer Portlet Provider or OracleAS Single Sign-On and clicks the Analyze
link in a portlet, then the worksheet opens in "Single Worksheet Viewer" regardless
of the viewerURLForPublicUser setting.
9.9.4 New cacheThreshold Configuration Setting

Bug 4725681
You can use the cacheThreshold configuration setting to improve the display of portlet
data as a user changes parameter values. By default, OracleBI Discoverer Release
10.1.2 keeps portlet results for only the current and the previously used set of
parameter values. If a user changes the parameter values of a portlet to the most
recently used set of parameter values, then the results will be found in the portlet
result set and will display relatively quickly. When parameter values are changed to
values other than the most recently used values, then OracleBI Discoverer Portlet
Provider must issue a new query and is slower to display data.
146
With OracleBI Discoverer Release 10.1.2.2, you can control how many total result sets
are cached for parameter value combinations. You can set cacheThreshold in the
configuration.xml file to control the number of cache entries that are maintained. The
default value is "1", which means that OracleBI Discoverer Portlet Provider maintains
only the previous cache entry in the ptm5_cache table in the Infrastructure database, in
addition to the results for the current combination of values.
To increase the number of cached result sets, use the following steps:
1.
Edit the configuration.xml file in the ORACLE_HOME/discoverer/config

directory by adding the cacheThreshold setting to the portlet tag and assigning an
integer value greater than 1, as shown in the following example:
This line in the configuration file:
pickerCompatibleVersions="10.1.2" maxDataRows="1000">
Is rewritten as:
pickerCompatibleVersions="10.1.2" maxDataRows="1000" cacheThreshold="15">
2.
Reboot Oracle Application Server.
After you follow these steps, OracleBI Discoverer Portlet Provider will cache results
for the current combination of parameter values and a number of previous
combinations of parameter values, based on the number that you specify in the
cacheThreshold setting. This should improve the performance of displaying results as
the user changes parameter values.
Setting cacheThreshold to a value higher than 1 will likely increase the amount of
space that is consumed in the Infrastructure database and the amount of time that is
required for each portlet to refresh. In the example above, with cacheThreshold set to
15, it is possible that at refresh time, the query for the portlet will run 15 times and that
the database space that is needed to store the results will be 15 times greater. Use care
when setting cacheThreshold and monitor the portlet refreshes to ensure that they are
completing in a timely manner.
9.10 Oracle Business Intelligence Discoverer Viewer Issues

This section provides release notes for Oracle Business Intelligence Discoverer Viewer
(OracleBI Discoverer Viewer). It contains the following topic:
Section 9.10.1, "New isCurrentPageItemsExportForOLAP Configuration Setting"
9.10.1 New isCurrentPageItemsExportForOLAP Configuration Setting

Bug 4540925
You can use the isCurrentPageItemsExportForOLAP configuration setting to control
how OracleBI Discoverer Viewer exports worksheets of OLAP data that have page
items when you export to Microsoft Excel or to HTML. The values for the setting are
true or false:
True specifies to export a worksheet of OLAP data to Microsoft Excel or to HTML

with the current set of page items.
False (the default setting) specifies to export all possible combinations of page
items to Microsoft Excel or to HTML.
147
The following example shows the optional isCurrentPageItemsExportForOLAP setting

included in the <viewer> tag:
<viewer queryRefreshPeriod="3000" queryRequestTimeout="1000"
longRequestRefreshPeriod="6000" longRequestTimeout="10000"
userDefinedConnections="true" logLevel="error" laf="dc_blaf"
switchWorksheetBehavior="prompt" defaultLocale="en" disableBrowserCaching="false"
isCurrentPageItemsExportForOLAP="true">
9.11 Oracle Application Server Portal Metadata Repository Upgrade in a

RAC Environment
When upgrading Oracle Application Server Portal Metadata Repository to release
10.1.4 or 10.1.2.3 and the database is in a RAC environment, then the upgrade may fail
and the following error may appear in the upgrade error log:
ERROR: WWU-01012: Upgrade completed with the following errors
###
177 : ERROR at line 1:
###
178 : ORA-38301: can not perform DDL/DML over objects in Recycle Bin
The workaround for this issue is as follows:

1.
Connect to the database from SQL*Plus as the sys user.
2.
Run the following command:

purge recyclebin;
3.
Perform the upgrade again.
9.12 Oracle Application Server Portal and Upgrading Database Repository

to Release 11g
If you have Oracle Application Server Portal release 10.1.4.1 running on Oracle
Database 10g and upgrade the database to Oracle Database 11g Release 1 (11.1), then
you must do the following:
1.
Run the following command:

loadjava -user portal_schema/password@tns
MT_ORACLE_HOME/porta/upg/plsql/upg/1014xpatch/lib/dbwsclient-jdk15-user.jar
- verbose -force -resolve
In the preceding command, MT_ORACLE_HOME is the middle tier Oracle home

directory. The jar file is included in the patch set.
2.
Run SQL*Plus as follows:

sqlplus sys/password@tns DB_ORACLE_HOME/rdbms/admin/utlrp.sql
In the preceding command, DB_ORACLE_HOME is the database Oracle home

directory. The utlrp.sql script is shipped with the database.
3.
Set the database compatibility paramter to at least 11.0.0. See OracleMetaLink Note
465968.1 step 7 for more information.
4.
Run the following script from the 10.1.4.2 patch set. You will be prompted to enter
the portal schema name.
MT_ORACLE_HOME/portal/upg/plsql/upg/1014xpatch/wwv/wdbigra.sql
148
9.13 Oracle Application Server Web Cache Issues

This section contains known issues and workarounds for Oracle Application Server
Web Cache. It contains the following topics:
Section 9.13.1, "Client Certificate Validation with Certificate Revocation Lists"
Section 9.13.2, "Disable Use of Diffie-Hellman Anonymous Cipher Suites"
9.13.1 Client Certificate Validation with Certificate Revocation Lists

Bug 4546678
In this release, OracleAS Web Cache provides the capability of client certificate
validation with Certificate Revocation Lists (CRL). Client certificate revocation status
is checked against CRLs that are located in a file system directory. Typically, CRL
definitions are valid for a few days, and must be updated on a regular basis. Whenever
the CRL definitions are modified, you must restart OracleAS Web Cache.
When CRL validation is enabled and available, OracleAS Web Cache performs
certificate revocation status checking for client certificates. The SSL connection is
rejected if a certificate is revoked. SSL connections are accepted if no CRL is found, or
if the certificate has not been revoked.
You must configure this feature manually in the webcache.xml file. Application
Server Control and OracleAS Web Cache do not support configuration of this feature.
To configure certificate validation with CRL:
1.
Use a text editor to open the webcache.xml file (located in the ORACLE_
HOME/webcache directory).
2.
Enable client certificate for the HTTPS listen port.

For more information, refer to "Task 7: (Optional) Require Client-Side Certificates"
in Chapter 9, "Configuring OracleAS Web Cache for HTTPS Requests" in the
Oracle Application Server Web Cache Administrators Guide for information on how to
configure client side certificate settings.
3.
Locate the HTTPS listen port in webcache.xml for which CRL checking needs to
be enabled, and add the SSLCRLENABLE="YES" parameter to the LISTEN
directive.
For example:
<LISTEN IPADDR="ANY" PORT="443" PORTTYPE="NORM" SSLENABLED="SSLV3_V2H" CLIENT_
CERT="YES" SSLCRLENABLE="YES" STRONG_CRYPTO_ONLY="NO" Key="IPADDR PORT">
Before setting this parameter, ensure the HTTPS listen port is

configured to require client-side certificates.
Note:
For more information about client-side certificates, see "Task 7:

(Optional) Require Client-Side Certificates," in Chapter 9,
"Configuring OracleAS Web Cache for HTTPS Requests" in the Oracle
Application Server Web Cache Administrator's Guide.
4.
Configure CRL file or location by adding the SSLCRLPATH and SSLCRLFILE

parameters to the HTTPS LISTEN directive.
149
SSLCRLPATH: Enter the path to the directory where CRLs are stored. Ensure that
the path is correct; otherwise CRL checking will not work. This parameter has no
default value.
SSLCRLFILE: Enter the path to a comprehensive CRL file where PEM-encoded
(BASE64 CRLs are concatenated in order of preference in one file. If this parameter
is set, then the file must be present at the specified location. Otherwise CRL
checking will not work.
For example:
CERT="YES" SSLCRLENABLE="YES"SSLCRLFILE="/oracle_home/webcache/crls/sample_crl"
SSLCRLPATH="/oracle_home/webcache/crls/" STRONG_CRYPTO_ONLY="NO" Key="IPADDR
PORT">
You must use the command line utility orapki to rename

CRLs in your file system. See the section titled "Certificate Revocation
List Management" in the Oracle Database Advanced Security
Administrator's Guide from the Oracle Database documentation library
for information about using orapki.
Note:
5.
Restart OracleAS Web Cache for the changes to take effect. You can use the
following command:
opmnctl restartproc ias-component=WebCache
In a cluster configuration, when configuration changes are

made directly to a cluster member's webcache.xml file, use
Application Server Control and OracleAS Web Cache Manager to
propagate the change to other OracleAS Web Cache cluster members.
Note:
9.13.2 Disable Use of Diffie-Hellman Anonymous Cipher Suites

Bug 5577648
In this release, OracleAS Web Cache provides the capability to disable the use of
Diffie-Hellman (DH) anonymous cipher suites for the HTTPS listen port.
You must configure this feature manually in the webcache.xml file. Application
Server Control and OracleAS Web Cache do not support configuration of this feature.
To disable DH anonymous cipher suites:
1.
Use a text editor to open the webcache.xml file (located in the ORACLE_
HOME/webcache directory).
2.
Locate the HTTPS listen port in webcache.xml for which DH cipher suites you
want to disable, and add the ANON_CRYPTO_FORBIDDEN="YES" parameter to
the LISTEN element.
For example:
CERT="YES" STRONG_CRYPTO_ONLY="YES" ANON_CRYPTO_FORBIDDEN="YES" Key="IPADDR
PORT">
150
3.
Restart OracleAS Web Cache for the changes to take effect. You can use the
following command:
opmnctl restartproc ias-component=WebCache
Notes:
In a cluster configuration, when configuration changes are made

directly to a cluster member's webcache.xml file, use
Application Server Control or OracleAS Web Cache Manager to
propagate the change to other OracleAS Web Cache cluster
members.
The OracleAS Web Cache Auto-Restart mechanism uses DH
Anonymous Cipher suite to ping the OracleAS Web Cache process
on HTTPS listen ports. If there are no non-SSL NORM listening
ports, and ANON_CRYPTO_FORBIDDEN="YES" is set for SSL
NORM listening ports, then you must disable auto-restart
pinging. This is true for all OracleAS Web Cache installation
types. When you disable auto-restart pinging, you can still enable
the auto-restart mechanism.
For more information, see "Task 3: Configure Auto-Restart Settings" in
Chapter 8, "Setup and Configuration," of the Oracle Application Server Web
Cache Administrators Guide for information about the auto-restart settings.
9.14 Oracle Application Server Wireless Issues

This section contains known issues and workarounds for Oracle Application Server
Wireless. It contains the following topics:
Section 9.14.1, "Wireless SMPP Driver Configuration for ESM_CLASS Value

Support"
Section 9.14.2, "Unable to Download Oracle Application Server Wireless
Repository Objects"
Section 9.14.3, "Oracle Application Server Wireless and Oracle Directory
Integration and Provisioning User Data"
9.14.1 Wireless SMPP Driver Configuration for ESM_CLASS Value Support

An enhancement in this patch set enables users to set the ESM_CLASS variable in the
SMPP driver. In order to do so, add the parameter manually using the SMPP driver
configuration in Oracle Enterprise Manager 10g to support the ESM_CLASS variable.
9.14.2 Unable to Download Oracle Application Server Wireless Repository Objects

Bug 4759129
The following error may occur when downloading Oracle Application Server Wireless
repository objects over SSL using Microsoft Internet Explorer:
Page cannot be displayed
The workaround is available from Microsoft Support at

http://support.microsoft.com/?kbid=323308#XSLTH31741211241201211
20120
151
9.14.3 Oracle Application Server Wireless and Oracle Directory Integration and
Provisioning User Data
Bug 4884709
After performing a middle tier OracleAS Metadata Repository in Oracle Application
Server 10g Release 2 (10.1.2), the OracleAS Wireless registration with the Oracle
Directory Integration and Provisioning server does not function correctly. As a result,
any changes to the user attributes made using the Oracle Internet Directory Delegated
Administrative Services tool are not propagated to OracleAS Wireless until the user
logs in to the mobile device portal. This may impact OracleAS Wireless messaging and
notification features.
The workaround for this issue is as follows:
Users can change their attributes using the OracleAS Wireless Web tool. Those
changes will be immediately propagated to Oracle Internet Directory.
Users can log in to the mobile device portal after making changes using the Oracle
Internet Directory Delegated Administrative Services tool.
9.15 Cloning Issues

This section contains known issue and workarounds for cloned instances. It includes
Section 9.15.1, "Updating the Hostname in Files for a Cloned Instance"
Section 9.15.2, "Files Need to be Deleted in Cloned Instance"
Section 9.15.3, "Cloning not Supported for Infrastructure Installations"
Section 9.15.4, "Update the oraparam.ini File after Cloning"
Section 9.15.5, "Change File Permissions for jlib Directory and infratool.jar File for
Cloned Instance"
9.15.1 Updating the Hostname in Files for a Cloned Instance

Bug 4949149
The links to the Application Server Control Console from the Welcome pages need to
be updated with the correct URLs.
For more information about updating the links, refer to Oracle Application Server
Administrators Guide 10g Release 2 (10.1.2.0.2). The guide is available at:
http://www.oracle.com/technology/documentation/
9.15.2 Files Need to be Deleted in Cloned Instance

Bug 4919720
Oracle Universal Installer does not delete files without language suffixed such as
index.html and demo.htm in the ORACLE_HOME\Apache\Apache\htdocs
directory for a cloned instance. If the files are not deleted, then the default page will be
shown in English only. To avoid this problem, delete the index.html and demo.htm
files in the ORACLE_HOME\Apache\Apache\htdocs directory for the cloned
instance.
152
9.15.3 Cloning not Supported for Infrastructure Installations

Bug 4694458
Cloning infrastructure installations is not supported for this patch set.
9.15.4 Update the oraparam.ini File after Cloning

Bugs 4890531 and 4887969
When cloning a cloned instance, it is necessary to update the JRE_LOCATION
parameter in the ORACLE_HOME/oui/oraparam.ini file with JRE_
LOCATION=../../jdk/jre instead of JRE_LOCATION=%JRE_LOCATION%, before
running the following command:
perl clone.pl
9.15.5 Change File Permissions for jlib Directory and infratool.jar File for Cloned
Instance
Bugs 5017106 and 4998726
It is necessary to change the file permission for the jlib directory and the
infratool.jar file before running the perl clone.pl command in cloned
instances. The following are examples of the commands to change the permissions:
chmod u-w OH/jlib
chmod u-w OH/jlib/infratool.jar
The permissions can be changed back to their original settings after cloning is done.
10 Fixed Platform-Specific Bugs for SPARC

Table 10 describes the bugs fixed in OracleAS 10g Release 2 Patch Set 3 for SPARC.
Table 10
Bugs Fixed for SPARC in OracleAS 10g Release 2 Patch Set 3
Bug Number Component
Description
4747587
Oracle Reports
Developer
Engine crashes when running reports with

desformat=delimited.
4540895
Oracle Process
Manager and
Notification Server
CPU load goes to high because of OPMN process

on Solaris 5.9.
4309112
Oracle Enterprise
Manager
Double re-deploy gives java.lang.nullpointer

exception.
6069982
Oracle Reports
Developer
DESTYPE=PRINTER fails on Solaris 5.10
5954872
Oracle HTTP Server
Configuring APACHE2 with mod_oc4j.so, will

cause the HTTPD status to fail
11 Fixed Platform-Specific Bugs for Windows

Table 11 describes the bugs fixed in OracleAS 10g Release 2 Patch Set 3 for Windows.
153
Table 11
Bugs Fixed for Windows in OracleAS 10g Release 2 Patch Set 3
Description
3575301
OracleBI Discoverer
Diagnostic script collectlogs.bat does not

work properly.
5120345
Oracle HTTP Server
Immediate timeout in an OSSO protected

resource when the last access was in the last five
minutes of an hour.
4599568
Oracle Reports
Developer
Rwclient cannot handle files larger than 50MB

when destype=localfile.
5262456
Oracle Reports
Developer
Reports with maximum text hang on

'FORMATTING PAGE N' after several browser
runs.
3588086
OracleAS Forms
Services
Mouse was losing focus in XP when it was

returning to the parent window of a Modal
Dialog Window.
4139420
Oracle HTTP Server
Japanese URL containing 0x5c character is not

available for Windows J2EE mod_oc4j
application.
5439667
Oracle Internet
Directory
OIDLDAPD core dumps when huge size >

12K filter is sent.
12 Fixed Platform-Specific Bugs for AIX 5L Based Systems

(64-Bit)
Table 12 describes the bugs fixed in OracleAS 10g Release 2 Patch Set 3 for AIX.
Table 12
Bugs Fixed for AIX in OracleAS 10g Release 2 Patch Set 3
Description
5682614
OracleAS Forms
Services
procbuilder component fails to relink.
5722496
OracleAS Forms
Services
libfrmjsl.a loads instead of libfrmjsl.so.
5614162
OracleAS Forms
Services
FRM-92101 when running a form while ftrace

is activated and charset in NLS_LANG is set to
UTF8.
5735249
OracleAS Forms
Services
frmweb executable unable to resolve some

symbols
5685431
OracleAS Forms
Services
frmweb executable unable to resolve some

symbols
5739492
OracleAS Forms
Services
Relinking frmweb using the make -f ins_

forms.mk frmweb command throws warning
message.
6059204
OracleAS Forms
Services
make -f ins_forms.mk installation fails.
6128858
OracleAS Forms
Services
Problem with SHORT_LIBS in loc_forms.mk.
154
13 Fixed Platform-Specific Bugs for Linux x86

Table 13 describes the bugs fixed in OracleAS 10g Release 2 Patch Set 3 for Linux x86.
Table 13
Bugs Fixed for Linux x86 in OracleAS 10g Release 2 Patch Set 3
Description
5882005
OracleAS Forms
Services
env_forms.mk file needs LIBDIR=lib and

PASTA_LIBDIR=lib.
5894896
OracleAS Forms
Services
ins_procbuilder.mk file needs LIBDIR=lib

and PASTA_LIBDIR=lib.
5283622
OracleAS Forms
Services
CPUAPR2006 fails to make on SLES9 64-bit

Forms/Reports standalone.
5872676
Oracle Procedure
Builder
JDAPI program fails with LIBCLNTSH.SO.9.0.
6127521
OracleAS Forms
Services
WEBUTIL_FILE.FILE_SAVE_DIALOG returns
NULL even if the file is selected.
14 Patch Set Components

Table 14 provides a list of patch set components for Oracle Application Server:
Table 14
OracleAS 10g Release 2 Patch Set 3 Components
Component Name
Release
Apache Module for Oracle Distributed Authoring and

Versioning
10.1.2.3
Development Environment Layer
10.1.2.3
Java Authorization
10.1.2.3
LDAP Required Support Files
10.1.2.3
Oracle ADF Business Components Configuration Assistant
10.1.2.3
Oracle ADF Business Components Runtime Library
10.1.2.3
Oracle Application Server
10.1.2.3
Oracle Application Server Containers for J2EE (OC4J)
10.1.2.3
Oracle Application Server Distributed Configuration

Management (DCM)
10.1.2.3
Oracle Application Server High Availability Components
10.1.2.3
Oracle Application Server JAAS Support Common Files
10.1.2.3
Oracle Application Server Port Tunnel
10.1.2.3
Oracle Application Server Portal (OracleAS Portal)
10.1.2.3
Oracle Application Server Repository API Patch
10.1.2.3
Oracle Application Server SOAP Client
2.2.0.0.2b
Oracle Application Server SOAP Server
2.2.0.0.2b
Oracle Application Server UIX Configuration
2.2.20.0.0
Oracle Application Server Upgrade Assistant
10.1.2.3
Oracle Application Server Web Cache (OracleAS Web Cache)
10.1.2.3
155
Table 14 (Cont.) OracleAS 10g Release 2 Patch Set 3 Components

Component Name
Release
Oracle Application Server Web Services Common Files
10.1.2.3
Oracle Application Server Wireless (OracleAS Wireless)
10.1.2.3
Oracle B2B
10.1.2.3
Oracle BPEL Process Manager
10.1.2.3
Oracle Business Intelligence Discoverer Administrator
10.1.2.3
Oracle Delegated Administration Services
10.1.2.3
Oracle Discoverer
10.1.2.3
Oracle Discoverer EUL Java Command Line for Java Patch
10.1.2.3
Oracle Discoverer Libraries Patch
10.1.2.3
Oracle Discoverer Management Plugin
10.1.2.3
Oracle Discoverer Services
10.1.2.3
Oracle Discoverer Servlets
10.1.2.3
Oracle Distributed Configuration Management
10.1.2.3
Oracle Distributed Software Assistant
10.1.2.3
Oracle Distributed Software Assistant Client
10.1.2.3
Oracle Distributed Software Assistant Common
10.1.2.3
Oracle Distributed Software Assistant Server
10.1.2.3
Oracle Dynamic Monitoring Service
10.1.2.3
Oracle Dynamic Services Midtier
10.1.2.3
Oracle Enterprise Manager 10g Process Utility
10.1.2.3
Oracle Enterprise Manager Agent
10.1.2.3
Oracle Enterprise Manager Application Server Control
10.1.2.3
Oracle Enterprise Manager Common Files
10.1.2.3
Oracle Extended Windowing Toolkit
3.4.40.0.0
Oracle Help for the Web
2.0.8.0.0
Oracle HTTP Server Files
10.1.2.3
Oracle InterConnect
10.1.2.3
Oracle Internet Directory Client
10.1.2.3
Oracle Internet Directory Client Common Files
10.1.2.3
Oracle Internet Directory Configuration Assistant
10.1.2.3
Oracle Internet Directory Server
10.1.2.3
Oracle Internet Directory Tools
10.1.2.3
Oracle Java Object Cache
10.1.2.3
Oracle Java Portal Development Kit
10.1.2.3
Oracle Java Server Pages
10.1.2.3
Oracle JDeveloper
10.1.2.3
156
Table 14 (Cont.) OracleAS 10g Release 2 Patch Set 3 Components

Component Name
Release
Oracle JFC Extended Windowing Toolkit
4.2.34.0.0
Oracle JInitiator
1.3.1.26.0
Oracle LogLoader
10.1.2.3
Oracle mod_plsql Gateway
10.1.2.3
Oracle Notification Service
10.1.2.3
Oracle OLAP Spreadsheet Add-in
10.1.2.3
Oracle Process Management and Notification Server (OPMN) 10.1.2.3

Oracle SQL Manager
10.1.2.3
Oracle UIX
2.2.20.0.0
OracleAS Certificate Authority
10.1.2.3
10.1.2.3
OracleAS Forms and Reports Services
10.1.2.3
OracleAS Infrastructure
10.1.2.3
OracleAS MapViewer
10.1.2.3
OracleAS Portal
10.1.4.2
OracleAS Portal Configuration Assistant
10.1.2.3
OracleAS Portal Development Kit
10.1.2.3
OracleAS Portal Documentation
10.1.2.3
OracleAS Portal Images
10.1.2.3
OracleAS Portal Midtier Components
10.1.2.3
OracleAS Portal Monitoring
10.1.2.3
OracleAS Portal NLS
10.1.2.3
OracleAS Portal Performance Reporting
10.1.2.3
OracleAS Portal Servlets
10.1.2.3
OracleAS Portal Single Sign-On
10.1.2.3
OracleAS Portal SQL Component
10.1.2.3
OracleAS Portal Utility Scripts Component
10.1.2.3
OracleAS Single Sign-On
10.1.2.3
OracleAS Single Sign-On Server
10.1.2.3
OracleAS Wireless Developer Kit (WDK)
10.1.2.3
OracleAS Wireless OracleAS Single Sign-On Pages
10.1.2.3
OracleAS Wireless Server
10.1.2.3
OracleAS Wireless Server Agent
10.1.2.3
OracleAS Wireless Server Management
10.1.2.3
SQLJ Runtime
10.1.2.3
157
The latest Oracle Business Intelligence Beans plug-in for Oracle JDeveloper is not
included in this patch set. It can be downloaded from Oracle Technology Network at:
http://www.oracle.com/technology/products/bib/index.html
The latest release of Oracle JDeveloper is available at:

http://www.oracle.com/technology/software/products/jdev/index.html
15 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, 7 days a week. For TTY support,
call 800.446.2398. Outside the United States, call +1.407.458.2479.
Oracle Application Server and Oracle Developer Suite Patch Set Notes, 10g Release 2 (10.1.2) Patch Set 3 (10.1.2.3.0)
Copyright 2005, 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 SoftwareRestricted 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 USA, Inc. 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
158
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.
159
160

Oracle® Application Server and Oracle Developer Suite: Patch Set Notes 10g Release 2 (10.1.2) Patch Set 3 (10.1.2.3.0)

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Oracle® Application Server and Oracle Developer Suite: Patch Set Notes 10g Release 2 (10.1.2) Patch Set 3 (10.1.2.3.0)

Încărcat de

Drepturi de autor:

Formate disponibile

Oracle Application Server and Oracle Developer Suite

Patch Set Notes

This document contains the following sections:

Section 2, "Patch Set Overview"

Section 3, "Patch Set Documentation"

Section 4, "Patch Set Requirements"

Section 5, "Before You Apply This Patch Set"

Section 6, "Patch Application for Oracle Collaboration Suite Environments"

Section 7, "Patch Set Application"

Section 8, "Postapplication Considerations"

Section 9, "Known Issues"

Section 10, "Fixed Platform-Specific Bugs for SPARC"

Section 11, "Fixed Platform-Specific Bugs for Windows"

Section 13, "Fixed Platform-Specific Bugs for Linux x86"

Section 14, "Patch Set Components"

Section 15, "Documentation Accessibility"

Oracle Application Server 10g Release 2 (10.1.2.0.0)

Oracle Application Server 10g Release 2 Standard Edition One (10.1.2.0.1)

Oracle Application Server 10g Release 2 (10.1.2.0.2)

Oracle Application Server Forms and Reports Services (10.1.2.0.2)

Oracle Application Server Portal 10g Release 2 (10.1.4)

Oracle Application Server Portal 10g Release 2 Patch Set 2 (10.1.4.1)

Oracle Developer Suite 10g (10.1.2.0.2)

Oracle Business Intelligence 10g Release 2 (10.1.2)

Oracle Business Intelligence 10g Release 2 (10.1.2.0.2)

Oracle Business Intelligence Tools 10g Release 2 (10.1.2)

Oracle Business Intelligence Tools 10g Release 2 (10.1.2.0.2)

OracleAS 10g Release 2 Patch Set 1 (10.1.2.1.0)

OracleAS 10g Release 2 Patch Set 2 (10.1.2.2.0)

Solaris Operating System (SPARC)

AIX 5L Based Systems (64-Bit)

2 Patch Set Overview

Section 2.1, "Metadata Repository Update"

Section 2.2, "Software Update"

Section 2.3, "Database Patch Set"

2.1 Metadata Repository Update

2.2 Software Update

For example, a distributed Oracle Application Server environment may be set up as

Computer 1 contains Oracle Identity Management Services including Oracle

Computer 2 contains the OracleAS Metadata Repository.

Computer 3 contains a Portal and Wireless instance.

Computer 4 contains a J2EE and Web Cache instance.

Computers 3 and 4, respectively, share the same Oracle Application Server

For this type of environment, the updates could be installed as follows:

Apply the Software Update to computers 1 and 2.

2.3 Database Patch Set

3 Patch Set Documentation

All system requirements and instructions needed to install or deinstall the

The SPARC document is contained in the file /OracleAppServer10g_

The HP-UX PA-RISC document is contained in the file /OracleAppServer10g_

These documents are also available on OracleMetaLink at

To locate these documents, do the following:

Click Advanced at the top of the OracleMetaLink page.

See Also: Oracle Application Server installation guides and release

4 Patch Set Requirements

4.1 Required Software

One of the baseline releases identified in Section 1, "Introduction".

One of the following supported operating systems:

Supported Operating System

Oracle Application Server 10g

One of the following operating systems:

Microsoft Windows 2000 with Service Pack 3 or later

Microsoft Windows Server 2003 (32-bit)