Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Section 1, "Introduction"
Section 12, "Fixed Platform-Specific Bugs for AIX 5L Based Systems (64-Bit)"
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 Business Intelligence Tools 10g (10.1.2.0.2) that shipped as part of Oracle
Developer Suite 10g Release 2 (10.1.2)
Note:
The names of the operating systems have been shortened for this document, as
follows:
Operating System
Abbreviated Name
SPARC
Microsoft Windows
Windows
AIX
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:
For a list of components included in this patch set, see the Section 14, "Patch Set
Components".
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.
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.
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 ...
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.
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:
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.
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+)
Log in to OracleMetaLink.
2.
3.
Enter the note number in the Document ID field, and click Submit.
http://www.oracle.com/technology/index.html
Note:
Oracle Application
Oracle Application
Oracle Application
Notes:
10
Section 5.1, "Stop all Oracle Developer Suite Processes and Programs"
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"
11
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.
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.
4.
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.
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.
3.
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.
2.
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
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
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.
3.
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.
After applying the patch set, start the service to start receiving data, as follows:
1.
2.
3.
4.
Modify the load balancer settings so that the load balancer VIP points to the first
Oracle Internet Directory instance.
2.
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.
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.
b.
c.
d.
16
3.
b.
Bring up the Oracle Services for MSCS properties, and on the Advanced tab
select Do not restart.
b.
SID Name
OracleORACLE_HOMEProcessManager
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.
Open Microsoft Service Panel from the Administrative Tools on the Control
Panel.
b.
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.
Note:
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.
During the Software Update, if the Oracle Internet Directory Patch Configuration
Assistant fails, then stop and start the listener.
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.
c.
2.
3.
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.
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.
18
Click OK and then manually enable the instance using Oracle Enterprise Manager 10g
as follows:
1.
2.
3.
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:
19
Note:
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
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.
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.
b.
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
21
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.
22
Section 7.1.5, "Apply the OracleAS 10g Release 2 Patch Set 3 Software Update"
Section 7.1.7, "Update OracleAS Portal Repositories that Reside in Oracle RAC
Manually"
2.
3.
4.
5.
a.
b.
Change the port number to an unused port number in the range between
18130 and 18149.
b.
Update the port value to an unused port number in the range between 18100
and 18120.
b.
Modify the port to match the one used in the emd-web-site.xml file.
23
6.
a.
b.
Update the port value to an unused port number in the range between 18150
and 18169.
b.
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.
2.
(For UNIX) Set the display for the local system using the following command, if
you are not installing the software on the local system.
24
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.
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.
Shut down the existing Oracle instance using normal or immediate priority
using one of the following commands:
d.
For Windows:
ORACLE_HOME\bin\lsnrctl stop
4.
25
For UNIX:
cd /tmp
/directory_location/runInstaller
For Windows:
Double-click directory_location/setup.exe in the Windows Explorer.
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.
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:
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
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
For UNIX:
SQL> @/ORACLE_HOME/rdbms/admin/utlrp.sql
For Windows:
SQL> @\ORACLE_HOME\rdbms\admin\utlrp.sql
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.
4.
5.
Go to the directory where patch 5255249 is located and apply the patch:
27
cd 5255249
opatch apply
6.
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:
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.
> ./runInstaller
For Windows:
a.
b.
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.
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.
Screen
Action
Welcome
29
2.
Screen
Action
Specify File
Locations
3.
Select a Product to
Install
Click Next.
4.
Instance Password
(Oracle Application
Server only)
5.
Warning
30
6.
Screen
Action
Oracle Internet
Directory Login
7.
OracleAS Certificate
Authority
Administrator
31
8.
Screen
Action
Enter Metadata
Repository SYS
Password
Warning
9.
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.
11.
Install Progress
12.
Configuration
Assistants
13.
End of Installation
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\
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
OID SSL Port: Oracle Internet Directory Server Secure Sockets Layer (SSL) port
3.
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:
For UNIX:
ORACLE_HOME/bin/emctl stop iasconsole
33
For Windows:
C:\> ORACLE_HOME\bin\emctl stop iasconsole
For UNIX:
ORACLE_HOME/opmn/bin/opmnctl stopall
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.
b.
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:
5.
Table 2 describes the steps and screens you will encounter during update of an
OracleAS Metadata Repository.
34
Table 2
Screen
Action
1.
Welcome
2.
Specify File
Locations
3.
Select a Product to
Install
Click Next.
4.
Warning
5.
Applying Metadata
Repository Update
6.
Application Server
Instance Password
35
Action
7.
Oracle Internet
Directory Login
8.
Select OracleAS
Metadata Repository
9.
Enter Metadata
Repository SYS
Password
10.
11.
Warning
12.
Summary
13.
Install Progress
Configuration
Assistants
15.
End of Installation
6.
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
HTTP Server, OC4J instances, and OracleAS Web Cache.
7.
For UNIX:
ORACLE_HOME/bin/emctl start iasconsole
For Windows:
36
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:
2.
3.
4.
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:
37
Note:
4.
Set your ORACLE HOME environment variable to the Oracle home where the
Metadata Repository Update was applied.
5.
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.
c.
Expand Entry Management in the System Objects section. Enter the following
values:
cn=OracleContext
cn=Products
cn=IAS
38
6.
d.
e.
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:
For UNIX:
ORACLE_HOME/bin/emctl stop iasconsole
For Windows:
C:\> ORACLE_HOME\bin\emctl stop iasconsole
For UNIX:
ORACLE_HOME/opmn/bin/opmnctl stopall
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.
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.
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
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
Prompt
Explanation
40
Explanation
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.
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:
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:
For UNIX:
ORACLE_HOME/opmn/bin/opmnctl startall
For Windows:
C:\> ORACLE_HOME\opmn\bin\opmnctl startall
For UNIX:
ORACLE_HOME/bin/emctl start iasconsole
For Windows:
C:\> ORACLE_HOME\bin\emctl start iasconsole
42
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:
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)))"
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.
8.
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
patch. Leave it up and running.
10. Use the following command to join IM_Node2 to the DCM cluster:
dcmctl joincluster -cl cluster
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.
-
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.
Note:
2.
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.
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
patch. Leave it up and running.
8.
Ensure the LDAP load balancer in the configuration routes LDAP traffic to the
patched Oracle Internet Directory node, OID_Node1, only.
9.
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.
b.
c.
d.
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
patch. Leave it up and running.
f.
Use the following command to bring up the Oracle Application Server Single
Sign-On/Oracle Delegated Administration Services applications:
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.
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
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.
b.
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.
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.
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
patch. Leave it up and running.
j.
Use the following command to bring up the Oracle Application Server Single
Sign-On/Oracle Delegated Administration Services applications:
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
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.
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
49
Table 4 (Cont.) Steps for Applying Oracle Application Server Patch to Oracle Developer
2.
Screen
Action
Specify File
Locations
Select a Product to
Install
Summary
5.
Install Progress
6.
End of Installation
Back up the production site to ensure that the starting state is secure.
2.
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.
8.
Note:
51
Constants
Optional Values
Required Values
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.
*
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:
*
53
szl_SYSPassword=<Value Unspecified>
szl_OCAInformation=<Value Unspecified>
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:
For UNIX:
> ./runInstaller -silent -responseFile absolute_path_and_filename
For Windows:
E:\> setup.exe -silent -responseFile absolute_path_and_filename
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
54
For Windows:
C:\oracle_inventory_path\logs\installActiontodays_date_time.log
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:
Correct the issue that caused the original failure during application of the Software
Update.
2.
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.
8 Postapplication Considerations
This section describes postapplication considerations for OracleAS 10g Release 2 Patch
Set 3. It contains the following topics:
Section 8.3, "Re-application of the OracleAS 10g Release 2 Patch Set 3"
55
For UNIX:
ORACLE_HOME/bin/lsnrctl start
For Windows:
ORACLE_HOME\bin\lsnrctl start
2.
For UNIX:
ORACLE_HOME/bin/sqlplus /nolog
SQL> connect SYS as SYSDBA
SQL> startup
SQL> quit
For Windows:
ORACLE_HOME\bin\sqlplus /nolog
SQL> connect SYS as SYSDBA
SQL> startup
SQL> quit
56
From
To
ORACLE_HOME/j2ee/OC4J_
Portal/applications/jpdk/jpdk/
htdocs
ORACLE_HOME/j2ee/OC4J_
Portal.timestamp/applications/jpd
k/jpdk/htdocs
ORACLE_HOME/j2ee/OC4J_
Portal/applications/jpdk/jpdk/
WEB-INF
ORACLE_HOME/j2ee/OC4J_
Portal.timestamp/applications/jpd
k/jpdk/WEB-INF
ORACLE_HOME/j2ee/OC4J_
Portal/application_
deployments/jpdk
ORACLE_HOME/j2ee/OC4J_
Portal.timestamp/application_
deployments/jpdk
ORACLE_HOME/j2ee/OC4J_
Portal/applications/jpdk/pdkst
ruts/htdocs
ORACLE_HOME/j2ee/OC4J_
Portal.timestamp/applications/jpd
k/pdkstruts/htdocs
ORACLE_HOME/j2ee/OC4J_
Portal/applications/jpdk/pdkst
ruts/WEB_INF
ORACLE_HOME/j2ee/OC4J_
Portal.timestamp/applications/jpd
k/pdkstruts/WEB_INF
ORACLE_HOME/j2ee/OC4J_
Portal/applications/portalTool
s/providerBuilder/WEB-INF
ORACLE_HOME/j2ee/OC4J_
Portal.timestamp/applications/por
talTools/providerBuilder/WEB-INF
ORACLE_HOME/j2ee/OC4J_
Portal/applications/portalTool
s/omniPortlet/WEB-INF
ORACLE_HOME/j2ee/OC4J_
Portal.timestamp/applications/por
talTools/omniPortlet/WEB-INF
ORACLE_HOME/j2ee/OC4J_
Portal/applications/portalTool
s/omniPortlet/plugins
ORACLE_HOME/j2ee/OC4J_
Portal.timestamp/applications/por
talTools/omniPortlet/plugins
ORACLE_HOME/j2ee/OC4J_
Portal/applications/portalTool
s/webClipping/WEB-INF
ORACLE_HOME/j2ee/OC4J_
Portal.timestamp/applications/por
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
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
ORACLE_HOME/j2ee/OC4J_
Portal/applications/portal/por
tal/WEB-INF/web.xml
ORACLE_HOME/j2ee/OC4J_
portal.timestamp/applications/por
tal/portal/WEB-INF/web.xml
57
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.3, "Using Oracle Real Application Clusters Database with OracleAS
Disaster Recovery"
Section 9.4, "Oracle Real Application Clusters Database with OracleAS Disaster
Recovery Issues"
58
Section 9.1.1.7, "Central Agent Not Displayed in Oracle Application Server Control
Console"
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.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
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.
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
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.
2.
Locate the Oracle Internet Directory configuration assistant section of the file.
b.
3.
Set the ORACLE_HOME environment variable to point to the correct Oracle home
using the following command:
export ORACLE_HOME=/apps/infra10
4.
5.
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.
2.
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.
2.
Insert the line shown below in bold font. This will include iwoic.jar in the
CLASSPATH.
<ias-component id="InterConnect" status="enabled">
<environment>
<variable id="CLASSPATH"
value="ORACLE_HOME/integration/interconnect/lib/iwoic.jar"
append="true"/>
<variable id="CLASSPATH"
value="ORACLE_HOME/integration/interconnect/lib/oai.jar"
append="true"/>
3.
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.
65
Section 9.1.2.2, "Oracle Enterprise Manager 10g Web Service not Completely
Terminated"
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.
2.
Stop Oracle Enterprise Manager 10g Web service using the following command:
net stop servicename
3.
If the nmesrvc.exe process is still active after completing the preceding steps, then
do the following steps:
1.
2.
3.
4.
66
5.
Restart your computer and restart application of the OracleAS 10g Release 2 Patch
Set 3.
2.
Run the application (for example, access the applications URL with a browser).
3.
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.
2.
Deselect IPv6 for all your connections and adapters, using the Network
Connection Properties page. The page is available from Control Panel.
3.
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.
7.
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.
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"
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/
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)
hostname: Command not found
Segmentation Fault (core dumped)
hostname: Command not found
Segmentation Fault (core dumped)
stty: : Invalid argument
uname: Command not found
Segmentation Fault (core dumped)
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
Enter the full path to Oracle JDeveloper Kit (JDK). The path will be added to the jdev_
jdk file.
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.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)"
69
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.
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
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 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
71
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).
72
Install all your required languages before applying OracleAS 10g Release 2 Patch
Set 3.
Do the following procedure:
1.
2.
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.
5.
6.
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:
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:
Dependent component failed to install before this phase
:oracle.swd.opatch,10.1.0.4.0, >0.0.0.0.0, [ 912 ][OH:2]
73
To work around this problem, remove the .old file to continue applying the patch.
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.
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
To obtain a fix for this issue, contact Oracle Support. You can access information about
technical support at:
http://www.oracle.com/support
74
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:
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" />
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.
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!
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
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.4, "Switchback Procedure (for Switching Back to the Primary Site)"
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
Standby Site
prodnode1, prodnode2
standbynode1, standbynode2
vracnode1, vracnode2
vracnode1, vracnode2
Database name
orcl.oracle.com
orcl.oracle.com
Database SID
orcl1 on prodnode1
orcl1 on standbynode1
orcl2 on prodnode2
orcl2 on standbynode2
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
vracnode1.domain.com
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
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.
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).
79
b.
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.
> DBHOME/bin/sqlplus / as sysdba
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.
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.
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
4.
b.
c.
d.
e.
81
*.service_names=orcl1
*.instance_name=orcl1
to:
*.service_names=orcl2
*.instance_name=orcl2
5.
b.
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
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';
SQL> shutdown immediate;
7.
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, stop the Real Application Clusters database and disable automatic
database restart using CRS.
> DBHOME/bin/srvctl stop database -d orcl
> DBHOME/bin/srvctl disable database -d orcl
3.
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
member of the dba group in order to start the database.
> srvctl stop database -d orcl
> srvctl disable database -d orcl
> DBHOME/bin/sqlplus / as sysdba
SQL> startup
4.
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
SQL> shutdown immediate;
> DBHOME\bin\srvctl enable database -d ORCL
> DBHOME\bin\srvctl start database -d ORCL
83
6.
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.
ASGCTL> connect asg standbynode1 ias_admin/<adminpwd>
UNIX only: ASGCTL> set primary database sys/<passwd>@orcl
UNIX only: ASGCTL> set new primary database sys/<passwd>@orcl
Windows only: ASGCTL> set primary database sys/<passwd>@orcl1
Windows only: ASGCTL> set new primary database sys/<passwd>@orcl1
ASGCTL> set trace on all
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.
> DBHOME\bin\sqlplus / as sysdba
SQL> shutdown immediate;
> 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:
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
Standby Site
prodnode1, prodnode2
standbynode1
vracnode1, vracnode2
vracnode1
Database name
orcl.oracle.com
orcl.oracle.com
Database SID
orcl1 on prodnode1
orcl1 on standbynode1
orcl2 on prodnode2
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
vracnode1.domain.com
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.
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 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.
On prodnode1, stop the Real Application Clusters database and disable automatic
database restart using CRS. You must be logged in as a member of the dba group
in order to start the database.
> DBHOME/bin/srvctl stop database -d orcl
> DBHOME/bin/srvctl disable database -d orcl
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.
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).
86
6.
b.
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.
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.
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
8.
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:
> srvctl stop database -d orcl
> srvctl disable database -d orcl
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, stop the Real Application Clusters database and disable automatic
database restart using CRS.
> DBHOME/bin/srvctl stop database -d orcl
> DBHOME/bin/srvctl disable database -d orcl
On standbynode1, run the following commands to switch back to the primary site:
88
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\sqlplus / as sysdba
SQL> shutdown immediate;
> DBHOME\bin\srvctl enable database -d ORCL
> DBHOME\bin\srvctl start database -d ORCL
4.
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:
ASGCTL> connect asg standbynode1 ias_admin/<adminpwd>
UNIX only: ASGCTL> set primary database sys/<passwd>@orcl
UNIX only: ASGCTL> set new primary database sys/<passwd>@orcl
Windows only: ASGCTL> set primary database sys/<passwd>@orcl1
Windows only: ASGCTL> set new primary database sys/<passwd>@orcl1
ASGCTL> set trace on all
ASGCTL> failover
ASGCTL> disconnect
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
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.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.
92
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:
-
You must use Oracle Database 10g Release 2, Patchset 10.2.0.2 with the
5146470 patch and higher.
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/
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.
Obtain the files that are needed for the update as follows:
a.
b.
93
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.
b.
where mydb is the connect string and password is the password of the owner
of the schema that hosts the Discoverer Catalog.
c.
d.
3.
b.
The following display indicates that the patch has been applied successfully:
OBJECT_NAME STATUS
-----------------------------------------------BISM_CORE VALID
BISM_CORE VALID
94
Table 9
New Features
Feature
Description
Applicable Products
Write-back
Graph Styles
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
Floating OracleBI
Query Editor
Enhanced
Refreshing of
Queries
VBA Macros
95
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:
In single-writer mode, use Oracle Database 10g Release 1 (10.1.0.4 and higher).
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:
-
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.
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.
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:
-
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:
-
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.
4.
a.
b.
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.
6.
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.
b.
c.
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.
9.
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
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.
3.
4.
5.
6.
7.
To save the program in the database, enter the following at the command line:
UPDATE
COMMIT
8.
For information on the OLAP DML, see the Oracle OLAP Application Developer's Guide
and the Oracle OLAP DML Reference.
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.
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.
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.
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.
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:
Open the workbook that you want to share in Oracle Discoverer Plus OLAP.
2.
3.
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.
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.
103
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
106
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
107
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.
Section 9.5.12.7, "What Command Syntax Conventions Does This Guide Use?"
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:
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:
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.
109
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).
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.
2.
110
<name>getDBConnect</name>
</permission>
<permission>
<class>
oracle.ias.repository.schemaimpl.CheckRepositoryPermission
</class>
<name>getDBPassword</name>
</permission>
<permission>
<class>
oracle.ias.repository.schemaimpl.CheckRepositoryPermission
</class>
<name>getSchema</name>
</permission>
<permission>
<class>
oracle.ias.repository.schemaimpl.CheckRepositoryPermission
</class>
<name>isProductChildExist</name>
</permission>
<permission>
<class>
oracle.ias.repository.schemaimpl.CheckRepositoryPermission
</class>
<name>makeNewOIDEntry</name>
</permission>
<permission>
<class>
oracle.ias.repository.schemaimpl.CheckRepositoryPermission
</class>
<name>addInstanceAccessToOIDEntry</name>
</permission>
<permission>
<class>
oracle.ias.repository.schemaimpl.CheckRepositoryPermission
</class>
<name>getOIDConnect</name>
</permission>
<permission>
<class>
oracle.ias.repository.schemaimpl.CheckRepositoryPermission
</class>
<name>getSchema</name>
</permission>
<permission>
<class>
oracle.ias.repository.schemaimpl.CheckRepositoryPermission
</class>
<name>getDBPassword</name>
</permission>
<permission>
111
<class>
oracle.ias.repository.schemaimpl.CheckRepositoryPermission
</class>
<name>connectAs</name>
</permission>
</permissions>
</grant>
3.
4.
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.
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:
112
Notes:
9.5.12.9 How to Run OracleBI Discoverer Connections API Commands You can run
anOracleBI Discoverer Connections API command in two ways:
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.
2.
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:
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"
call capi.bat connect orcladmin/tiger -create_conn -cname
"Analyze Sales Q2" -cdesc "Analyze Sales Second Quarter"
AppsSSOEnabled "false" -type "public" -olap "false" -apps
"false" -dbuser "jchan" -dbpasswd "12345" -dbname "db1"
-showdetails "true"
call capi.bat connect orcladmin/tiger -create_conn -cname
"Analyze Sales Q3" -cdesc "Analyze Sales Third Quarter"
AppsSSOEnabled "false" -type "public" -olap "false" -apps
"false" -dbuser "jchan" -dbpasswd "12345" -dbname "db1"
-showdetails "true"
To run multiple commands stored in an operating system command file:
1.
2.
Enter (or copy) the OracleBI Discoverer Connections API commands into the
command file.
3.
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:
114
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.
115
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.
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.
117
-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:
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:
Command modifiers:
Examples:
-update_conn
Use this command to update the details of an existing OracleBI Discoverer connection.
Information
Details
Syntax:
119
Information
Details
Command modifiers:
Examples:
-delete_conn
Use this command to permanently remove an existing OracleBI Discoverer connection.
Information
Details
Syntax:
Command modifiers:
Examples:
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:
Examples:
-apps "true"
-AppsSSOEnabled
Use this command modifier to specify whether OracleAS Single Sign-On is enabled.
Information
Details
Syntax:
Optional or Mandatory:
Mandatory
Notes:
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 or Mandatory:
Optional
121
Information
Details
Notes:
Examples:
-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:
Optional or Mandatory:
Mandatory
Notes:
Examples:
-dbname
Use this command modifier to specify the database that is used by an OracleBI
Discoverer connection.
Information
Details
Syntax:
Optional or Mandatory:
Mandatory
122
Information
Details
Notes:
-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:
Optional or Mandatory:
123
Information
Details
Notes:
Examples:
-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:
Optional or Mandatory:
Mandatory
Notes:
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:
Optional or Mandatory:
Notes:
Examples:
-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:
Optional or Mandatory:
Optional
124
Information
Details
Notes:
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:
Optional or Mandatory:
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:
Optional or Mandatory:
Notes:
None.
Examples:
-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:
Optional or Mandatory:
Notes:
None.
Examples:
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 or Mandatory:
Optional
Notes:
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:
Optional or Mandatory:
Notes:
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:
Optional or Mandatory:
Mandatory
Notes:
Examples:
-type "public"
126
Section 9.6.1, "Applying Patch Set to Oracle Business Intelligence Developer Suite
Release 10.1.2.x"
Section 9.6.8, "Issue with Attributes Listed on Conditions Tab in Query Editor"
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.
2.
3.
4.
Change the ownership of the apachectl file to the iasinst user, as follows:
chown iasinst .apachectl
5.
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.
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
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.
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.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.
130
genericStandardFetchSpan = 1000
genericDefaultCacheCapacity = 1000
genericMaxCacheCapacity = 1000
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 <!-- Portlet Provider configuration. --> 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.
131
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.
2.
3.
4.
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.
6.
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.
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.
2.
Navigate to ORACLE_HOME/opmn/conf.
3.
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">
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.
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"
Section 9.7.2, "Documentation Errata Section for OracleBI Discoverer Support for
OracleAS Single Sign-On in an Oracle E-Business Suite Environment for Sun
Solaris"
Section 9.7.3, "Documentation Errata Section for OracleBI Discoverer Support for
OracleAS Single Sign-On in an Oracle E-Business Suite Environment for Linux
x86"
Section 9.7.4, "Documentation Errata Section for OracleBI Discoverer Support for
OracleAS Single Sign-On in an Oracle E-Business Suite Environment for AIX 5L
Based Systems"
Section 9.7.5, "Documentation Errata Section for OracleBI Discoverer Support for
OracleAS Single Sign-On in an Oracle E-Business Suite Environment for HP-UX
PA RISC"
135
Section 9.7.6, "Documentation Errata Section for OracleBI Discoverer Support for
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.
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
3.12.4
15.1.9.4
3.12.5
15.1.9.5
15.1.9.6
Discoverer Administration
page Help topic
3.14.8
15.1.11.8
7.9.5
15.5.8.5
Section Title
136
9.7.2 Documentation Errata Section for OracleBI Discoverer Support for OracleAS
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:
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.
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. B14500-11 - Oracle Application Server Release Notes 10g Release 2
(10.1.2) for Solaris Operating System (SPARC)
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
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
3.12.5
14.1.9.5
14.1.9.6
Corrections to the
Oracle Business
Intelligence Discoverer
Configuration Guide
Discoverer
Administration page
Help topic
3.14.8
14.1.11.8
Section Title
14.5.8.5
9.7.3 Documentation Errata Section for OracleBI Discoverer Support for OracleAS
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
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.
Part No. B19316-06 - Oracle Business Intelligence Release Notes 10g Release 2
(10.1.2) for Linux x86
Part No. B19312-10 - Oracle Application Server Release Notes 10g Release 2
(10.1.2) for Linux x86
The following table outlines the 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
OracleBI release notes
Part No. B19316-06
Section number in
OracleAS release notes
Part No. B19312-10
Account Details:
Username and
Password page Help
topic
3.22.4
17.1.21.4
3.22.5
17.1.21.5
17.1.21.6
Corrections to the
Oracle Business
Intelligence Discoverer
Configuration Guide
3.23
17.1.22
Discoverer
Administration page
Help topic
3.24.1
17.1.23.1
17.5.10.5
Section Title
9.7.4 Documentation Errata Section for OracleBI Discoverer Support for OracleAS
Single Sign-On in an Oracle E-Business Suite Environment for AIX 5L Based Systems
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:
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
138
Use this button to save the details that you have entered on this page.
Part No. B25207-06 - Oracle Business Intelligence Release Notes 10g Release 2
(10.1.2) for AIX 5L Based Systems
Part No. B25203-08 - Oracle Application Server Release Notes 10g Release 2
(10.1.2) for AIX 5L Based Systems
The following table outlines the 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
OracleBI release notes
Part No. B25207-06
Section number in
OracleAS release notes
Part No. B25203-08
Account Details:
Username and
Password page Help
topic
3.21.4
17.1.21.4
3.21.5
17.1.21.5
17.1.21.6
Corrections to the
Oracle Business
Intelligence Discoverer
Configuration Guide
3.22
17.1.22
Discoverer
Administration page
Help topic
3.23.1
17.1.23.1
17.5.10.5
Section Title
9.7.5 Documentation Errata Section for OracleBI Discoverer Support for OracleAS
Single Sign-On in an Oracle E-Business Suite Environment for HP-UX PA RISC
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:
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.
139
Part No. B25191-06 - Oracle Business Intelligence Release Notes 10g Release 2
(10.1.2) for HP-UX PA-RISC
Part No. B25187-08 - Oracle Application Server Release Notes 10g Release 2
(10.1.2) for HP-UX PA-RISC
The following table outlines the 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
OracleBI release notes
Part No. B25191-06
Section number in
OracleAS release notes
Part No. B25187-08
Account Details:
Username and
Password page Help
topic
3.21.4
17.1.21.4
3.21.5
17.1.21.5
17.1.21.6
Corrections to the
Oracle Business
Intelligence Discoverer
Configuration Guide
3.22
17.1.22
Discoverer
Administration page
Help topic
3.23.1
17.1.23.1
17.5.10.5
Section Title
9.7.6 Documentation Errata Section for OracleBI Discoverer Support for OracleAS
Single Sign-On in an Oracle E-Business Suite Environment for HP-UX Itanium
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:
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.
Part No. B25199-06 - Oracle Business Intelligence Release Notes 10g Release 2
(10.1.2) for HP-UX Itanium
Part No. B25195-08 - Oracle Application Server Release Notes 10g Release 2
(10.1.2) for HP-UX Itanium
140
The following table outlines the 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
OracleBI release notes
Part No. B25199-06
Section number in
OracleAS release notes
Part No. B25195-08
Account Details:
Username and
Password page Help
topic
3.21.4
17.1.21.4
3.21.5
17.1.21.5
17.1.21.6
Corrections to the
Oracle Business
Intelligence Discoverer
Configuration Guide
3.22
17.1.22
Discoverer
Administration page
Help topic
3.23.1
17.1.23.8
17.5.10.5
Section Title
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.
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.
142
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.
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:
-
Wait until another user has finished performing calculation and validation,
then the first user can attempt the operation again.
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.
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.
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.
2.
Reopen the workbook to restore the query to the point at which it was last
saved.
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"
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 <!-- Portlet Provider configuration. --> section, as shown in the
following example:
<portlet showPivotLabel="true"
logKey="disco.portlet.fatal"
logLevel="error"
pickerCompatibleVersions="10.1.2"
maxDataRows="1000">
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.
Is rewritten as:
<portlet logKey="disco.portlet.fatal" logLevel="error"
pickerCompatibleVersions="10.1.2" maxDataRows="1000"
viewerURLForPublicUser="normalViewer">
2.
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.
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.
Is rewritten as:
<portlet logKey="disco.portlet.fatal" logLevel="error"
pickerCompatibleVersions="10.1.2" maxDataRows="1000" cacheThreshold="15">
2.
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.
147
2.
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
Use a text editor to open the webcache.xml file (located in the ORACLE_
HOME/webcache directory).
2.
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">
Note:
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:
<LISTEN IPADDR="ANY" PORT="443" PORTTYPE="NORM" SSLENABLED="SSLV3_V2H" CLIENT_
CERT="YES" SSLCRLENABLE="YES"SSLCRLFILE="/oracle_home/webcache/crls/sample_crl"
SSLCRLPATH="/oracle_home/webcache/crls/" STRONG_CRYPTO_ONLY="NO" Key="IPADDR
PORT">
Note:
5.
Restart OracleAS Web Cache for the changes to take effect. You can use the
following command:
opmnctl restartproc ias-component=WebCache
Note:
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:
<LISTEN IPADDR="ANY" PORT="443" PORTTYPE="NORM" SSLENABLED="SSLV3_V2H" CLIENT_
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:
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.
Section 9.15.5, "Change File Permissions for jlib Directory and infratool.jar File for
Cloned Instance"
152
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.
Description
4747587
Oracle Reports
Developer
4540895
Oracle Process
Manager and
Notification Server
4309112
Oracle Enterprise
Manager
6069982
Oracle Reports
Developer
5954872
153
Table 11
Description
3575301
OracleBI Discoverer
5120345
4599568
Oracle Reports
Developer
5262456
Oracle Reports
Developer
3588086
OracleAS Forms
Services
4139420
5439667
Oracle Internet
Directory
Description
5682614
OracleAS Forms
Services
5722496
OracleAS Forms
Services
5614162
OracleAS Forms
Services
5735249
OracleAS Forms
Services
5685431
OracleAS Forms
Services
5739492
OracleAS Forms
Services
6059204
OracleAS Forms
Services
6128858
OracleAS Forms
Services
154
Bugs Fixed for Linux x86 in OracleAS 10g Release 2 Patch Set 3
Description
5882005
OracleAS Forms
Services
5894896
OracleAS Forms
Services
5283622
OracleAS Forms
Services
5872676
Oracle Procedure
Builder
6127521
OracleAS Forms
Services
WEBUTIL_FILE.FILE_SAVE_DIALOG returns
NULL even if the file is selected.
Component Name
Release
10.1.2.3
10.1.2.3
Java Authorization
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
2.2.0.0.2b
2.2.0.0.2b
2.2.20.0.0
10.1.2.3
10.1.2.3
155
Release
10.1.2.3
10.1.2.3
Oracle B2B
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
Oracle Discoverer
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
3.4.40.0.0
2.0.8.0.0
10.1.2.3
Oracle InterConnect
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
Oracle JDeveloper
10.1.2.3
156
Release
4.2.34.0.0
Oracle JInitiator
1.3.1.26.0
Oracle LogLoader
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
Oracle UIX
2.2.20.0.0
10.1.2.3
10.1.2.3
10.1.2.3
OracleAS Infrastructure
10.1.2.3
OracleAS MapViewer
10.1.2.3
OracleAS Portal
10.1.4.2
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
10.1.2.3
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
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