Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Section 1, "Introduction"
1 Introduction
This document accompanies Oracle Application Server and Oracle Developer
Suite 10g Release 2 (10.1.2) Patch Set 2 (10.1.2.2.0) (OracleAS 10g Release 2 Patch
Set 2). This patch set is applicable for the following releases only:
Note:
The OracleAS 10g Release 2 Patch Set 2 updates the software on all applicable
Oracle Application Server installations (refer to the top of Section 1,
"Introduction" for a list of applicable releases). If you have a Portal and Wireless
installation, you must also use this patch set to update your OracleAS Metadata
Repository.
This patch set is not a complete software distribution. You must install this patch
set over one of the releases identified in Section 1, "Introduction".
Refer to the installation guide and release notes for the base requirements for
your Oracle product, and to 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 username 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
The following sections provide further information about the OracleAS 10g
Release 2 Patch Set 2:
For a list of products included in this patch set, see the Section 10, "Patch Set
Components".
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 2 is applied.
If you have previously installed Oracle Application Server 10g Release 2
(10.1.2) with Oracle Database version 9.2.0.6, you must first upgrade to
Oracle Database version 9.2.0.7.
If your database version is 9.2.0.7 or 10.2, then the Oracle Database 10.1.0.5
database patch is not required. Also, the Metadata update for upgrading the
Metadata Repository should be run from the middle tier.
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 2
Metadata Repository Update to the Metadata Repository used by each of the
existing middle-tiers.
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 computers 1 and
2.
2.
3.
4.
Oracle Application Server and Oracle Developer Suite Patch Set Notes 10g Release
2 (10.1.2) Patch Set 2 (10.1.2.2.0) for Linux x86 and Linux x86-64 (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 2 (10.1.2.2.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.
This document is contained in the file
/Disk1/doc/bugsfixed.html in the patch set distribution.
2.
Note:
Oracle Application
Oracle Application
Section 5.1, "Stop all Oracle Developer Suite Processes and Programs"
Section 5.2, "OracleAS Infrastructure Must be Running During Software
Update"
Section 5.3, "Setting and Unsetting Environment Variables"
Section 5.4, "Configure Virtual Server Names and Ports for the Load Balancer
in a High Availability Environment."
Section 5.5, "Applying the Oracle Database 10g Release 1 (10.1.0.5) Patch Set"
Section 5.6, "Installing the Patch Set to a Distributed Configuration
Management Cluster"
Section 5.7, "Software Update to a File-based Repository"
Section 5.8, "OracleAS Wireless Developer Kit does not Work with XHTML
MP Devices"
5.4 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 OID node (for example, 1030 for
non-SSL and 1040 for SSL), you must change the physical LDAP ports on the
OID nodes to match the LDAP ports configured on the LDAP load balancer
before you install OracleAS 10g Release 2 Patch Set 2.
To do this:
1.
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.5 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
install type and Metadata Repository only install type) before OracleAS 10g
Release 2 Patch Set 2 is applied.
For more information about supported databases with OracleAS 10g Release 2
Patch Set 2, see Section 2.1, "Supported Database Versions".
5.8 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 2:
Solaris:
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.
Solaris:
ORACLE_HOME/j2ee/OC4J_Wireless/applications/wdk/wdk-web/repository
10
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.
11
OracleAS Web Cache plug-in may fail. The workaround is to use Oracle9i
Application Server (Oracle9iAS) 9.0.2 webcache.dtd to replace the Oracle9i
Application Server (Oracle9iAS) 9.0.3 webcache.dtd. The dtd file is located
in the ORACLE_HOME/webcache/dtds directory (for both 9.0.2 and 9.0.3).
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:
12
(
sname =>'ORASSO',
oname => 'WWSEC_PERSON$',
type => 'TABLE',
drop_objects => false
);
END;
/
Note:
node.
For more information, refer to Oracle Application Server High
Availability Guide 10g Release 2 (10.1.2.0.2) available on Oracle
Technology Network at
http://www.oracle.com/technology
2.
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.
5.
13
b.
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.myco.
com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=oradb.us.myco.com)))
You can change the entry either by manually editing the file, or by using the
network configuration tool.
14
Section 7.1.3, "Apply the OracleAS 10g Release 2 Patch Set 2 Software
Update"
Section 7.1.4, "Apply the Metadata Repository Update"
Section 7.1.5, "Update OracleAS Portal Repositories that Reside in Oracle
RAC Manually"
15
Note:
ORACLE_HOME/rdbms/notes
1.
2.
Set the display for the local system using the following command, if you are
not installing the software on the local system.
C shell:
% setenv DISPLAY local_host:0.0
Stop all listener, agent and processes running in or against the Oracle home
as follows:
4.
16
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 based systems, 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:
150 MB, if using a server parameter file. Log in as the sys user and use the
following command to check the parameter:
SQL> show parameter SHARED_POOL_SIZE
If the parameter is not at least 150 MB, then use the following command to
set it:
SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M' SCOPE=spfile;
16. 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 not at least 150 MB, then use the following command to
set the parameter:
SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='150M' SCOPE=spfile;
17. Shut down the database using the following command:
SQL> SHUTDOWN
18. Enter the following SQL*Plus commands:
SQL> STARTUP UPGRADE
SQL> SPOOL patch.log
SQL> @/ORACLE_HOME/rdbms/admin/catpatch.sql
17
is displayed at the end of the catpatch.sql script. This list provides the
version and status of each SERVER component in the database.
20. If necessary, re-run the catpatch.sql script to correct any problems.
21. Restart the database as follows:
SQL> SHUTDOWN
SQL> STARTUP
22. Run the utlrp.sql script as the sys user to recompile all invalid PL/SQL
7.1.3 Apply the OracleAS 10g Release 2 Patch Set 2 Software Update
The Software Update updates the software and configuration files contained in
the Oracle home.
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:
Note:
2.
3.
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.
18
Table 1
1.
Screen
Action
Welcome
2.
Specify File
Locations
19
3.
Screen
Action
Select a Product to
Install
Click Next.
4.
Instance Password
(Oracle Application
Server only)
20
5.
Screen
Action
Oracle Internet
Directory Login
6.
OracleAS Certificate
Authority
Administrator
21
7.
Screen
Action
Enter Metadata
Repository SYS
Password
Warning
8.
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
9.
10.
Install Progress
11.
Configuration
Assistants
12.
End of Installation
2.
22
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:
To stop the Application Server Control Console:
ORACLE_HOME/opmn/bin/opmnctl stopall
Oracle Universal Installer is used to install the OracleAS 10g Release 2 Patch
Set 2 Metadata Repository Update. Start the Oracle Universal Installer that
came with the OracleAS 10g Release 2 Patch Set 2, as follows:
> ./runInstaller
5.
Table 2 describes the steps and screens you will encounter during update of
an OracleAS Metadata Repository.
Table 2
Screen
Action
1.
Welcome
2.
Specify File
Locations
23
3.
Screen
Action
Select a Product to
Install
Click Next.
4.
Applying Metadata
Repository Update
5.
Application Server
Instance Password
6.
Oracle Internet
Directory Login
7.
Select OracleAS
Metadata Repository
8.
9.
Enter Metadata
Repository SYS
Password
24
Action
10.
Warning
11.
Summary
12.
Install Progress
13.
Configuration
Assistants
14.
End of Installation
6.
7.1.5 Update OracleAS Portal Repositories that Reside in Oracle RAC Manually
If you are manually updating an OracleAS Portal repository (Section 7.1.6) 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.
25
Note:
Perform the following steps to manually update your OracleAS Portal repository:
1.
Apply the Software Update as detailed in Section 7.1.3, "Apply the OracleAS
10g Release 2 Patch Set 2 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.
3.
Note:
26
4.
Set your ORACLE HOME environment variable to the Oracle home where
the Metadata Repository Update was applied.
5.
6.
b.
c.
cn=OracleContext
cn=Products
cn=IAS
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/ACOxlc22@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:
Verify the Oracle Internet Directory associated with the OracleAS Portal
schema is up and running.
9.
27
portal/upg/plsql
The directory was created during the Metadata Repository update. If the
directory does not exist in your Oracle home, then either the update has not
been applied or the update was applied to a different Oracle home.
10. Run the upgrade script in precheck mode until there are no errors in the log.
The script generates the upgrade.log file and the upgrade directory, tmp,
in the current directory. The syntax is as follows:
ORACLE_HOME/portal/upg/plsql/patch.sh -precheck
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.
11. Run the upgrade script without parameters after resolving all warnings and
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
28
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:
29
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 Thu Jun 30 04:28:18 2005.
Example 3 Standard Termination, but with Errors
###
### Show errors and warnings
###
Upgrade step started at Fri Jul 1 03:52:56 2005
###
### 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 Fri Jul 1 04:28:08 2005
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:
Apply the Software Update as detailed in Section 7.1.3, "Apply the OracleAS
10g Release 2 Patch Set 2 Software Update" to all middle-tier Oracle homes
that are associated with your OracleAS Wireless repository, if it has not
already been done.
2.
30
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 Solaris:
$ORACLE_HOME/wireless/upgrade_infra/bin/patchinfra.sh -P password
-C tnsname
For example:
$ORACLE_HOME/wireless/upgrade_infra/install/patchinfra.sh -P
YXYhR16V -C "(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)
(HOST=rhine985.us.myco.com)(PORT=1521)))
(CONNECT_DATA=(SERVICE_NAME = asdb.us.myco.com)))"
For Windows:
ORACLE_HOME\wireless\upgrade_infra\bin\patchinfra.bat -P password
-C tnsname
For example:
ORACLE_HOME\wireless\upgrade_infra\install\patchinfra.bat -P
YXYhR16V -C "(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)
(HOST=rhine985.us.myco.com)(PORT=1521)))
(CONNECT_DATA=(SERVICE_NAME = asdb.us.myco.com)))"
31
Note:
The following steps describe how to apply OracleAS 10g Release 2 Patch Set 2 to
OracleAS Cluster (Identity Management) environments.
1.
Note:
2.
Select one Identity Management node for installation of the patch set, such as
IM_Node1.
3.
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.
32
Apply OracleAS 10g Release 2 Patch Set 2 on the first node, IM_Node1,
according to the instructions in Section 7.1, "Applying OracleAS 10g Release
2 Patch Set 2".
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 2 to the second node, IM_Node2,
according to the instructions in Section 7.1, "Applying OracleAS 10g Release
2 Patch Set 2".
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
33
1.
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 2 on the Oracle Internet Directory
node, OID_Node1, according to the instructions in Section 7.1, "Applying
OracleAS 10g Release 2 Patch Set 2".
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.
34
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 2 to the second node, SSO_
Node2, according to the instructions in Section 7.1, "Applying OracleAS
10g Release 2 Patch Set 2". 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.
h.
i.
j.
Start the Oracle Internet Directory instance on the second Oracle Internet
Directory node, OIDNode2.
k.
Apply OracleAS 10g Release 2 Patch Set 2 to the second Oracle Internet
Directory node, OID_Node2, according to the instructions in Section 7.1,
"Applying OracleAS 10g Release 2 Patch Set 2".
The Oracle Internet Directory instance will be up and running after
applying the patch Leave it up and running.
l.
35
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 2 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 2 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 2 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.
l.
36
If you have upgraded the OracleAS Portal repository to 10.1.2.2 from 10.1.2.x and
later you want to upgrade to OracleAS Portal 10.1.4.1, you must do the
following:
1.
2.
Follow the instructions in Section 7.1.4, "Apply the Metadata Repository Update"
to apply the OracleAS Portal 10.1.4.1.0 patch.
If you are manually upgrading OracleAS Portal in a customer database, refer to
the instructions in Section 7.1.6, "Update OracleAS Portal Repository Manually".
1.
Screen
Action
Welcome
37
Table 4 (Cont.) Steps for Applying Oracle Application Server Patch Against Oracle
Developer Suite
2.
Screen
Action
Specify File
Locations
Select a Product to
Install
Summary
5.
Install Progress
6.
End of Installation
38
values in the response file to provide answers to some or all of the installer
prompts.
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:
FROM_LOCATION="../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_GROUP_NAME=<Value Unspecified>
39
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 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 2 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:
*
40
oracle.iappserver.st_infrastructure:szlSpecifyOIDLogin=<Value
Unspecified>
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 installation,
also specify the silent parameter.
Examples:
4.
Check the log files in your inventory directory for any errors.The log files are
located in the following directory:
/oracle_inventory_path/logs/installActiontodays_date_time.log
41
If you have no backup installation available and want to retry application of the
Software Update after a failure, then try the following steps:
1.
Correct the issue that caused the original failure during application of the
Software Update.
2.
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 2. It contains the following topics:
Section 8.3, "Re-application of the OracleAS 10g Release 2 Patch Set 2"
42
2.
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
43
To
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 2:
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
OracleMetaLink Notes
Component
Oracle Enterprise
Manager 10g
44
9 Known Issues
This section contains known issues in the product and documentation for
OracleAS 10g Release 2 Patch Set 2. 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"
Note:
45
Section 9.1.1.15, "Start All Button does not Start OC4J Components Created
by User"
Section 9.1.1.16, "Inactive Oracle Application Server Instance does not Show
Start Time"
Section 9.1.1.17, "Application Server Control Allows the Creation of a JAZN
User with a Null Password"
Section 9.1.1.18, "Upgrading to Oracle Identity Management 10.1.4 leaves
app_registry Entry for Oracle Internet Directory invalid"
Section 9.1.1.19, "OracleBI Discoverer Fails to Discover RAC Database"
Section 9.1.1.20, "Application of OracleAS 10g Release 2 Patch Set 2 Over
Oracle Collaboration Suite 10.1.2.2 may be Blocked on the Middle Tier"
Section 9.1.1.21, "Application Server Guard Required for Database Oracle
Home"
Section 9.1.1.22, "Using the "Back" Button on the Summary Screen Causes
Validation to Fail"
Section 9.1.1.23, "JDK 1.4.2 is not Bundled with UNIX"
46
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 Missing Oracle Management Agent Configuration Files
Bug 4861052
Oracle Management Agent included in this patch set is missing some
configuration fixes. All customers using this product should download the fix for
the issue.
To obtain a fix for this issue, contact Oracle Support. You can access information
about technical support at:
http://www.oracle.com/support
9.1.1.6 Central Agent Not Displayed in Oracle Application Server Control Console
Bugs 4778948 and 4714026
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.
2.
47
After applying OracleAS 10g Release 2 Patch Set 2 to the instance that is hosting
the repository, the dcmctl whichfarm command does not return the correct farm
name.
To obtain a fix for this issue, contact Oracle Support. You can access information
about technical support at:
http://www.oracle.com/support
9.1.1.8 Visigenics ORB3.4.0.0.0 Appears Under "New Installations"
When the Software Update is applied against a J2EE standalone version 9.0.4,
Visigenics ORB3.4.0.0.0, which is part of RDBMS, appears on the Summary Page
under "New Installations." This is a known issue and does not adversely affect
product functionality.
9.1.1.9 Command Line Options Documented Incorrectly
Bug 5395456
In the Oracle Application Server High Availability Guide and Oracle Application
Server Containers for J2EE User's Guide, command line options such as Java
options, OC4J options, and Java executables are defined as instance-specific
parameters, and are basically excluded from the common configuration in a
DCM-managed OracleAS cluster. However, this does not work by default so
these command line options need to be configured manually in the
instspec.xmlfile:
1.
2.
9.1.1.10 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, the emctl set password command will
prompt (without echo) the user for the password, which can then be entered
from the command line.
9.1.1.11 Silent Upgrade is not Supported if OID is Configured to use Port 389
48
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 listed on port 389.
9.1.1.12 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.2.0. For
example:
If you install J2EE and Web Cache, then upgrade this middle tier with
Business Intellegence and Forms, then you can apply OracleAS 10g Patch Set
2 on this middle tier.
If you install J2EE and Web Cache, then upgrade it to 10.1.2.2.0, then upgrade
this middle tier with Business Intellegence and Forms, OracleAS 10g Patch
Set 2 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.
49
9.1.1.15 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 work around is to access and start the OC4J components from Enterprise
Manager.
9.1.1.16 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, 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.17 Application Server Control Allows the Creation of a JAZN User with a Null
Password
Bug 5583837
Application Server Control allows you to create a JAZN user with a null
password. You should exercise extra caution when creating a JAZN user.
In the event a JAZN user with a null password is created, you should delete that
user and create a new one.
9.1.1.18 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 2 to Oracle Identity
Management 10.1.4, the status of the PL/SQL package RIDELPLG and app_
registry entry for OID will show as invalid.
The work around is to run the RDBMS utility utlrp.sql immediately after
upgrading. This will validate the RIDELPLG package; however, the app_registry
entry for OID will still show as invalid.
9.1.1.19 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 work around this problem, use the add instance command to manually
add this database instance to the topology.
9.1.1.20 Application of OracleAS 10g Release 2 Patch Set 2 Over Oracle Collaboration Suite
10.1.2.2 may be Blocked on the Middle Tier
Bug 5606858
50
If you installed Oracle Collaboration Suite 10.1.2.2 and then try to install
OracleAS 10g Release 2 Patch Set 2 over its middle tier, then installation may be
blocked and you may see an error message like the following:
OC4J Home instance must be started.
To work around this problem, you must enable the "OC4H home" instance in
Oracle Enterprise Manager before installing OracleAS 10g Release 2 Patch Set 2
over the Oracle Collaboration Suite middle tier.
9.1.1.21 Application Server Guard Required for Database Oracle Home
Bug 5610659
The 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.22 Using the "Back" Button on the Summary Screen Causes Validation to Fail
Bug 5597727
Once you have reached the Summary screen during the patch installation
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 (Oracle Internet Directory, database, etc.) so that the validation
succeeds.
9.1.1.23 JDK 1.4.2 is not Bundled with UNIX
Bug 5574203
After applying OracleAS 10g Release 2 Patch Set 2 to a Developer Suite
installation, you will see the following message when you invoke Oracle
JDeveloper:
This version of Jdeveloper is certified on JDK 1.4.2. You are
attempting to run on JDK 1.4.0_00. Jdeveloper may not run correctly on this
version of JDK.
This is because JDK 1.4.2 is bundled with Microsoft Windows but not with UNIX.
If you are using UNIX platforms, you must install JDK 1.4.2 separately and
configure Oracle JDeveloper to JDK 1.4.2 after it is installed.
51
Section 9.2.2, "Error Messages after Applying OracleAS 10g Release 2 Patch
Set 2"
Section 9.2.10, "Error Message When Applying OracleAS 10g Release 2 Patch
Set 2 over Portal 10.1.4.0.0"
Section 9.2.11, "Error Message When Re-Applying OracleAS 10g Release 2
Patch Set 2"
Section 9.2.12, "Error Message from Portal Targets in Enterprise Manager"
Section 9.2.13, "Error Message From ASG Clone Instance Operation When
Performing a Node Backup"
Section 9.2.14, "Error Message When Running Reports Request with
destype=oracleportal"
9.2.2 Error Messages after Applying OracleAS 10g Release 2 Patch Set 2
Bugs 5452850 and 5474565
After applying OracleAS 10g Release 2 Patch Set 2 to one of the following
existing Oracle Application Servers:
The following error message is written to error file in the inventory directory:
52
After applying OracleAS 10g Release 2 Patch Set 2 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]
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 2 to the incremented installation.
You will be prompted to click OK. After clicking OK, the deinstallation process
continues and is successful.
See Also: Oracle Application Server Installation Guide for more
information about performing a complete deinstallation
53
To avoid this problem, make sure you exit out of all sqlplus sessions in this
Oracle Home before you attempt to install the patch.
54
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).
To obtain a fix for this issue, contact Oracle Support. You can access information
about technical support at:
http://www.oracle.com/support
9.2.10 Error Message When Applying OracleAS 10g Release 2 Patch Set 2 over
Portal 10.1.4.0.0
Bug 5502911
After applying OracleAS 10g Release 2 Patch Set 2 over Portal 10.1.4.0.0, the
following error appears in the log files:
NOTE : Portal Configuration Assistant (OPCA) has detected that the version of
Portal repository to which the language install was targeted is different
than the version of the Portal midtier. Portal language install between
different versions is not supported. OPCA has skipped this language install.
The work around is to install all your required languages before applying
OracleAS 10g Release 2 Patch Set 2.
9.2.11 Error Message When Re-Applying OracleAS 10g Release 2 Patch Set 2
Bug 5488356
The following error will appear if you re-apply OracleAS 10g Release 2 Patch Set
2 over an Oracle Application Server Infrastructure that has already been updated
with OracleAS 10g Release 2 Patch Set 2:
error in writing to file "$ORACLE_HOME/bin/extjob" permission denied.
The work around 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.
55
The work around 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 work around 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" />
To work around this issue, you must apply ARU patch 7769689.
56
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:
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 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 each
site.
Table 8
Standby Site
Physical hostnames
prodnode1, prodnode2
standbynode1, standbynode2
Virtual hostnames
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
57
prodnode1.domain.com
prodnode1
vracnode1.domain.com
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 via 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.
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.
4.
Start up the database on prodnode1 only. Ensure that the database instances
on the other Real Application Clusters nodes are down.
> DBHOME/bin/sqlplus / as sysdba
SQL> startup
5.
58
b.
c.
Make sure that the standby database mentioned in the remote entry is
pingable using TNS.
> tnsping orcl_remote1
7.
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.
59
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.
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.
60
a.
b.
c.
d.
e.
to:
*.service_names=orcl2
*.instance_name=orcl2
5.
b.
c.
Make sure that the standby database mentioned in the remote entry is
pingable using TNS.
> tnsping orcl_remote1
6.
On standbynode2, start up the database, create an spfile, and shut down the
database.
SQL> startup;
SQL> create spfile='<ORADATASHAREDLOCATION>/orcl/spfileorcl.ora'
from pfile='<DBHOME>/dbs/initORCL2.ora';
SQL> shutdown immediate;
7.
61
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.
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 via 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.
> srvctl stop database -d orcl
> srvctl disable database -d orcl
> DBHOME/bin/sqlplus / as sysdba
SQL> startup
4.
62
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
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>
ASGCTL> set primary database sys/<passwd>@orcl
ASGCTL> set new primary database sys/<passwd>@orcl
On the standby site, shut down the database and start it up using CRS:
> 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:
63
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 9 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 9
Standby Site
Physical hostnames
prodnode1, prodnode2
standbynode1
Virtual hostnames
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
On the standby site, edit the same hosts file to add an entry similar to the
following:
ip_address
vracnode1
standbynode1.domain.com
64
standbynode1
vracnode1.domain.com
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.
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.
4.
Start up the database on prodnode1 only. Ensure that the database instances
on the other Real Application Clusters nodes are down.
> DBHOME/bin/sqlplus / as sysdba
SQL> startup
5.
65
6.
b.
c.
Make sure that the standby database mentioned in the remote entry is
pingable using TNS.
> tnsping orcl_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.
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.
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.
66
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 via CRS.
> DBHOME/bin/srvctl stop database -d orcl
> DBHOME/bin/srvctl disable database -d orcl
67
3.
On prodnode1, shut down the single database instance and start up all the
Real Application Clusters instances using CRS. All the instances need to be
up for the "sync topology" command.
> 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>
ASGCTL> set primary database sys/<passwd>@orcl
ASGCTL> set new primary database sys/<passwd>@orcl
68
9.4.4 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
69
Guard; however, the remaining Oracle RAC instances on the primary site must
be started up manually.
9.4.5 OracleAS Guard Is Unable to Shutdown the Database Because More Than
One Instance of Oracle RAC is Running
Bug 5455252
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.
70
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.
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:
http://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.
71
Use the following commands to extract each file from the jar file to a
local directory. Enter each command on a single line.
jar -xf d4o.jar
oracle/dss/persistence/storagemanager/bi/scripts/bibcores.pls
jar -xf d4o.jar
oracle/dss/persistence/storagemanager/bi/scripts/bibcoreb.pls
jar -xf d4o.jar
oracle/dss/persistence/storagemanager/bi/scripts/biberrcs.pls
If the jar command does not run successfully, then either verify that the
directory that contains the java file is in the path environment variable
or enter the complete path name for the file, such as BI_
Home/jdk/bin/jar.
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
72
Table 10
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
73
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:
74
User access: You must ensure that users who need to write back to the
analytic workspaces have the appropriate privileges.
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:
-
75
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 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:
-
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.
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:
-
76
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:
-
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.
77
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.
3.
4.
a.
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.
7.
78
End Sub
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.
How do I Create an OLAP DML Program?
Use the following procedure to create an OLAP DML program:
1.
In Analytic Workspace Manager, locate and make note of the object names
that you need to reference in the program.
These objects include the name of the measure for which users are writing
values and the dimensions and dimension values of that measure. For
example, users might select the Sales measure in OracleBI Spreadsheet
Add-In. In Analytic Workspace Manager, you might find that the object
name for the Sales measure is WB_DEMO.SH_AW!SALES.
2.
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.
79
9.5.5.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.5.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.5.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.5.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)
80
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 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.5.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.5.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
text
values
" from the write-back engine for all cells.
81
vrb _value
vrb _retcode
text
text
vrb
vrb
vrb
qdr
vrb
vrb
text
text
" Must be set to full measure ID from first part of _
_numeric
_text
measID text
ProdID text
_ProdQDRValue
text
value.
vrb GeogID text
vrb _GeogQDRValue text
value.
vrb ChanID text
vrb _ChanQDRValue text
value.
vrb TimeID text
vrb _TimeQDRValue text
82
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
"
"
"
"
83
'REVENUE' TIME
'REVENUE' TIME
'REVENUE' TIME
'REVENUE' TIME
Section 9.5.6.7, "What Command Syntax Conventions Does This Guide Use?"
84
analysis' that is created for the OracleAS Single Sign-On user jchan is only
accessible to the user jchan.
9.5.6.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 via the OracleBI Discoverer Administration tab in
Application Server Control. For information about managing public
connections, see Oracle Business Intelligence Discoverer Configuration Guide.
85
2.
86
<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>
87
<class>
oracle.ias.repository.schemaimpl.CheckRepositoryPermission
</class>
<name>connectAs</name>
</permission>
</permissions>
</grant>
3.
4.
9.5.6.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.6.8 What is the Syntax for Commands? Use the following syntax for OracleBI
Discoverer Connections API commands:
Notes:
88
9.5.6.9 How to Run OracleBI Discoverer Connections API Commands? You can run
anOracleBI Discoverer Connections API command in two ways:
9.5.6.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.6.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 UNIX *.sh file
that is stored in the util directory on the Oracle Business Intelligence middle-tier
machine.
You enter OracleBI Discoverer Connections API commands in a command file
(one command per line) as follows:
89
2.
Enter (or copy) the OracleBI Discoverer Connections API commands into the
command file.
3.
9.5.6.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:
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.6.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.
90
1.
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.
91
"true" | "false" -type "private" -olap "false" -apps "true" -dbuser <"Database
user name"> [-dbpasswd <"Database password">] -dbname <"Database name">
-eul <"End User Layer name"> -resp <"Oracle Applications Responsibility"> -sg
<"Oracle Applications Security Group"> [-showdetails <"true" | "false">]
[-locale <"Locale">]
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.
92
-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.
Information
Details
Syntax:
Examples:
-connect orcladmin/tiger
For more command examples, see Section 9.5.6.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.
93
Information
Details
Syntax:
Command modifiers:
Examples:
-delete_conn
Use this command to permanently remove an existing OracleBI Discoverer
connection.
Information
Details
Syntax:
Command modifiers:
Examples:
9.5.6.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
94
-dbuser
-eul
-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.
95
Information
Details
Syntax:
Optional or Mandatory:
Optional
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
96
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:
97
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
98
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:
99
-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.6.1, "What is an OracleBI
Discoverer Connection?".
Information
Details
Syntax:
Optional or Mandatory:
Mandatory
Notes:
Examples:
-type "public"
100
You can access the file for the schema via the following URL:
http://download.oracle.com/otndocs/products/bi/samples/bi_
10_1_2_2_samples.zip
101
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 via the following URL:
http://download.oracle.com/otndocs/products/bi/samples
/bi_10_1_2_v2_samples.zip
9.6.4 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.
102
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.5 OracleBI Discoverer Plus AppletNot 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.
103
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-01 - Oracle Business Intelligence Release Notes 10g Release
2 (10.1.2.1) for Linux x86
Part No. B19312-03 - Oracle Application Server Release Notes 10g Release 2
(10.1.2) for Linux x86
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. B19316-01
Section number in
OracleAS release notes
Part No. B19312-03
Account Details:
Username and
Password page Help
topic
3.8.4
13.1.14.4
3.8.5
13.1.14.5
13.1.14.6
Corrections to the
Oracle Business
Intelligence Discoverer
Configuration Guide
3.9
13.1.15
Discoverer
Administration page
Help topic
3.10.8
13.1.16.8
Section Title
104
13.2.4.2
Note:
105
during an Excel session. After you exit and restart Excel, you will find that,
unlike other Excel toolbars, the OracleBI toolbar has returned to its default
location. To work around this issue, move the toolbar back to the desired position
each time that you start Excel.
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.
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.
106
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:
107
Use care when renaming a worksheet that contains an OLAP query in the
following situations:
-
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.
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"
108
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 work around.
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">
109
Is rewritten as:
<portlet logKey="disco.portlet.fatal" logLevel="error"
pickerCompatibleVersions="10.1.2" maxDataRows="1000"
viewerURLForPublicUser="normalViewer">
2.
110
pickerCompatibleVersions="10.1.2" maxDataRows="1000">
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.
111
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: Before setting this parameter, ensure the HTTPS listen port is
configured to require client-side certificates.
112
4.
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"
113
Restart OracleAS Web Cache for the changes to take effect. You can use the
following command:
opmnctl restartproc ias-component=WebCache
Note 1:
Note 2:
9.12.2 Oracle Application Server Wireless and Oracle Directory Integration and
Provisioning User Data
Bug 4884709
114
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.13.5, "Change File Permissions for jlib Directory and infratool.jar
File for Cloned Instance"
115
9.13.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.
Component Name
Release
10.1.2.2
10.1.2.2
Java Authorization
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
OracleAS Infrastructure
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
116
Release
10.1.2.2
10.1.2.2
OracleAS MapViewer
10.1.2.2
10.1.2.2
OracleAS Portal
10.1.4.1
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
2.2.20.0.0
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
Oracle Discoverer
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
117
Release
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
3.4.40.0.0
2.0.8.0.0
1.3.31.0.0a
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
10.1.2.2
4.2.34.0.0
Oracle LogLoader
10.1.2.2
10.1.2.2
10.1.2.2
2.2.0.0.2b
2.2.0.0.2b
10.1.2.2
Oracle UIX
2.2.20.0.0
SQLJ Runtime
10.1.2.2
118
The latest Oracle Business Intelligence Beans plug-in for Oracle JDeveloper is not
included in this patch set. It can be downloaded from Oracle Technology
Network at:
http://www.oracle.com/technology/products/bib/index.html
The latest release of Oracle JDeveloper is available at:
http://www.oracle.com/technology/software/products/jdev/inde
x.html
11 Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation
accessible, with good usability, to the disabled community. To that end, our
documentation includes features that make information available to users of
assistive technology. This documentation is available in HTML format, and
contains markup to facilitate access by the disabled community. Accessibility
standards will continue to evolve over time, and Oracle is actively engaged with
other market-leading technology vendors to address technical obstacles so that
our documentation can be accessible to all of our customers. For more
information, visit the Oracle Accessibility Program Web site at
http://www.oracle.com/accessibility/.
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this
document. The conventions for writing code require that closing braces should
appear on an otherwise empty line; however, some screen readers may not
always read a line of text that consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or
organizations that Oracle does not own or control. Oracle neither evaluates nor
makes any representations regarding the accessibility of these Web sites.
TTY Access to Oracle Support Services
Oracle provides dedicated Text Telephone (TTY) access to Oracle Support
Services within the United States of America 24 hours a day, seven days a week.
For TTY support, call 800.446.2398.
Oracle Application Server and Oracle Developer Suite Patch Set Notes, 10g Release 2 (10.1.2) Patch Set 2 (10.1.2.2.0) for Linux x86 and
Linux x86-64
Copyright 2005, 2006, 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 Corporation, 500 Oracle Parkway, Redwood City, CA 94065
119
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall
be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such
applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be
trademarks of their respective owners.
The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible
for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you
choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not
responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party,
including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for
any loss or damage of any sort that you may incur from dealing with any third party.
120