Using Discoverer 11.1.1 with Oracle E-Business Suite Release 12 [ID 1074326.1]

Modified 12-AUG-2010     Type WHITE PAPER     Status PUBLISHED

This document contains information for using Oracle Business Intelligence Discoverer 11g Release 1 (11.1.1) with Oracle E-Business Suite Release 12.

The most current version of this document can be obtained on My Oracle Support Knowledge Document 1074326.1.

There is a change log at the end of this document.

Section 1: Overview Section 2: Supported Architectures Section 3: Release Versions Section 4: Preinstallation Tasks Section 5: Installation Tasks Section 6: Postinstallation Tasks Section 7: Available Documentation Section 8: Conventions and Important Directory Locations Section 9: Installation of Additional Discoverer End User Layer patches Section 10: Known Issues and Limitations

Section 1: Overview

Oracle Business Intelligence Discoverer, a key component of Oracle Fusion Middleware, is an integrated business intelligence solution supporting intuitive adhoc query, reporting, analysis, and web publishing. Business users at all levels of the organization can use Discoverer to gain immediate access to information from data marts, data warehouses, and online transaction processing (OLTP) systems. Discoverer enables report builders and analysts to create, modify, and execute ad hoc queries and reports. Casual users can view and navigate through predefined reports and graphs through business views that hide the complexity of the underlying data structures being reported upon.

Discoverer is tightly integrated with Oracle E-Business Suite Release 12. Release 12 users can use Discoverer to analyze data from selected business areas in Financials, Operations, Human Resources, Projects, Purchasing, Process Manufacturing, Marketing, Activity Based Management and more.

This document describes how to install Discoverer 11.1.1 into an existing Oracle E-Business Suite Release 12 environment. Installation of Discoverer 11.1.1 into an Oracle E-Business Suite Release 12 environment consists of:

Installation of Discoverer 11.1.1 on a standalone application tier server node, or in a separate Oracle Business Intelligence Discoverer 11g Release 1 ORACLE_HOME on an existing application tier server node

Creation of the Discoverer 11.1.1 End User Layer (EUL) on a database tier server node Import of the Oracle E-Business Suite Release 12 Discoverer content into the Discoverer

11.1.1 End User Layer (Optional) Installation of Discoverer Administrator 11.1.1 on a Windows-based PC that can be

used to customize Discoverer

The procedures in this document have significant effects on Oracle E-Business Suite Release 12 environments and should be executed only by skilled Oracle E-Business Suite database or systems administrators. Users are strongly advised to make backups of their environments before executing any of the procedures noted, and to test their environments before executing these procedures in production environments. Users must log off the system while these changes are being applied.

Availability of Translations

Discoverer content for Oracle E-Business Suite Release 12 includes workbooks and the End User Layer for both regular Applications modules as well as Business Intelligence System (BIS) products such as Financials Intelligence and Purchasing Intelligence. This content is available only in US English, and there are no translations planned for other languages.

Section 2: Supported Architectures

Oracle Business Intelligence Discoverer 11g Release 1 (11.1.1) must be installed on a standalone server accessing an Oracle E-Business Suite Release 12 database, or in a separate Oracle Business Intelligence Discoverer 11g Release 1ORACLE_HOME on an existing application tier server node.

This configuration does not include integration of Oracle Single-Sign-On, Oracle Internet Directory, or Oracle Portal with Oracle E-Business Suite Release 12 (My Oracle Support Knowledge Document 376811.1).

Section 3: Release Versions

The following components must be used on the stand-alone instance:

Component Name Version

Oracle Business Intelligence Discoverer 11.1.1.2.0,11.1.1.3.0

Oracle Single-Sign-On 10.1.4.3

Oracle Identity Management 10.1.4.3,11.1.1.2.0 and 11.1.1.3.0

The following components must be used on the Oracle E-Business Suite Release 12 instance:

Component Name Version

Oracle E-Business Suite Release 12 12.0.x and higher

Section 4: Preinstallation Tasks

4.1. Read Discoverer 11.1.1 Installation and Configuration Guides

Obtain Oracle Portal, Forms, Reports and Discoverer 11g Release 1 (11.1.1) from the Oracle Technology Network.

The Oracle Fusion Middleware Installation Guide for Oracle Portal, Forms, Reports and Discoverer 11g Release 1 (11.1.1) explains how to install Discoverer. The Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer 11g Release 1 (11.1.1) explains how to run, maintain and support Discoverer. Review these guides and then proceed with installation.

Section 5: Installation Tasks

This section outlines steps required to install Oracle Business Intelligence Discoverer 11g Release 1 (11.1.1), and the Discoverer 11.1.1 End User Layer. See Section 8: Conventions and Important Directory Locations for important information about entering commands listed in this section.

5.1. Install Oracle Business Intelligence Discoverer 11g

5.1.1. Install Oracle Business Intelligence Discoverer 11g Release 1 (11.1.1)

You must install Oracle Fusion Middleware 11g Release 1 components on a standalone server accessing an Oracle E-Business Suite Release 12 database or in a separate ORACLE_HOME on an existing application tier server node. Choose one of the following installation options:

Option A Oracle Internet Directory Installation

Option B Standalone Installation

Install OracleAS Identity Management Infrastructure and Oracle Business Intelligence Discoverer 11g Release 1 (11.1.1)

Install Oracle Business Intelligence Discoverer 11g Release 1 (11.1.1) with no association to OracleAS Identitiy Management.

Step A.1 Install OracleAS Identity Management Infrastructure

If you are not planning to use features Discoverer Connection Management, Discoverer Portlet Provider, and Oracle SSO, you can choose to install Oracle Business Intelligence Discoverer 11g Release 1 (11.1.1) and in the configuration wizard, skip the configuration step that associates Discoverer to OracleAS Identity Management Infrastructure.

It is possible to associate the Oracle Business Intelligence Discoverer 11g installation to OracleAS Identity Management Infrastructure at a later point in time.

Step A.2. Install Oracle Business Intelligence Discoverer 11g Release 1 (11.1.1)

You must install Oracle Business Intelligence Discoverer 11g Release 1 (11.1.1) in a separate ORACLE_HOME from the previously installed OracleAS Infrastructure. The Discoverer installation is associated with an OracleAS Infrastructure during installation. The OracleAS Infrastructure might be on the same machine as the Discoverer installation or on a different machine.

For more information, please refer to section About Oracle BI Discoverer installations in the Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer 11g Release 1 (11.1.1).

Note: If your target is to install Discoverer 11.1.1.3.0 then no need to apply below one-off patch. You can proceed from 5.1.3

5.1.2 Install required Discoverer 11.1.1 patch

Download and install following required patch on Discoverer 11g Release 1 (11.1.1) for your platform.

One-Off Patch Description Download Location

MLR FOR PORT SPECIFIC 11G CERTIFICATON ISSUES 9387227

Follow the installation instructions provided in the patch README to install the patch on your Discoverer server.

5.1.3.Apply the latest certified FMW 11g Patchset

Description Download Location

Discoverer 11g (11.1.1.3.0) Patchset 9585598

To upgrade Discoverer 11g PS2 (11.1.1.3.0), following the instructions in the Oracle® Fusion Middleware Installation Planning Guide 11g Release 1 (11.1.1).

5.2. Configure Oracle Business Intelligence Discoverer 11g Release 1 (11.1.1)

5.2.1. Copy Database Connection file

Discoverer needs access to the Database Connection (dbc) file for the database you wish to connect to. A dbc file is a text file which stores all the information required to connect to a particular database.

Copy the dbc file from the $FND_SECURE directory of the E-Business Suite Release 12 instance you are setting up Discoverer with to the Discoverer 11.1.1 $ORACLE_INSTANCE/config/Discoverer/Discoverer_asinst_1/ directory.

Save the dbc file in lowercase.

About DBC Files

The default naming convention for the .dbc file for Oracle E-Business Suite Release 12 is <two_task >.dbc

If you are getting error "Could not locate or parse the .dbc file corresponding to the given Oracle Applications instance" when trying to connect to your E-Business Suite Release 12 instance from the OracleBI Discoverer Connections Page, please verify the filename of your dbc file. If your dbc file name does not match above default naming convention due to using virtual names, make a copy of your dbc file in your $ORACLE_INSTANCE/config/Discoverer/Discoverer_asinst_1/ directory that is the default $FND_SECURE directory on your OracleBI Discoverer node, and rename the file to match above default naming convention.

Discoverer will attempt to find the dbc file in following order

1. $FND_SECURE/ <two_task >.dbc2. $FND_SECURE/ <database host name >_ <two_task >.dbc

For more information about dbc files see Appendix 'Setting up and maintaining Oracle Applications' of the Oracle Applications System Administrators Guide.

5.2.2. Update tnsnames.ora file

On your Oracle Business Intelligence Discoverer 11g Release 1 node, include the tnsnames entry to connect to your Oracle E-Business Suite Release 12 database in file $ORACLE_INSTANCE/config/tnsnames.ora. Use the same entry as exists in the tnsnames.ora file on your Oracle E-Business Suite Release 12 application tier server node. The database name must match the two_task entry in the dbc file. Verify you can establish a connection to your Oracle E-Business Suite Release 12 database using sqlplus.

5.2.3. Enable access to the Oracle E-Business Suite Release 12 Database

If SQL*Net Access security is enabled in the E-Business Suite Release 12 database, you need to authorize the Oracle Business Intelligence Discoverer 11g Release 1 node to access the E-Business Suite Release 12 database through SQL*Net. Refer to step "Enable SQL*Net Access to the E-Business Suite Database" in My Oracle Support Knowledge Document Document 376811.1.

Note: If your E-Business Suite is SSL Enabled you must also enable SSL for Discoverer.Please refer to the Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer 11g Release 1 (11.1.1).

5.2.4. Implement Single Sign-On for Discoverer 11.1.1 (Optional)

There are two options for authentication and user credential management for Discoverer 11g users who need access to E-Business Suite workbooks:

Option A Without Single Sign-On integration

Option B With Single Sign-On integration

Integration between E-Business Suite and Oracle Internet Directory and Oracle Single Sign On via My Oracle Support Knowledge Document Document 376811.1 is optional.

Users may access E-Business Suite Discoverer workbooks via E-Business Suite menus.

Drawback: E-Business Suite users whose Applications SSO Login Types profile option is set to SSO, and who invoke E-Business Suite Discoverer workbooks via Discoverer's Connection Manager feature from standalone Discoverer clients will need to have their user credentials dual-maintained in both Oracle Internet Directory and the E-Business Suite FND_USER repository

Integration between the E-Business Suite and Oracle Internet Directory and Oracle Single Sign On via My Oracle Support Knowledge Document Document 376811.1 is mandatory.

Users may access E-Business Suite Discoverer workbooks via E-Business Suite menus.

Users may access E-Business Suite Discoverer workbooks via Discoverer's Connection Manager feature from standalone Discoverer clients, with user credentials managed in Oracle Internet Directory

If you select Option A, proceed directly to Step 5.3

If you select Option B, enable Single Sign-On on your Discoverer node:

5.2.4.1.Verify you have associated your the Oracle Business Intelligence Discoverer 11g installation to Oracle Application Server 10g Infrastructure. Refer to the steps mentioned under 5.1 Install Oracle Business Intelligence Discoverer 11g Release 1 (11.1.1).

5.2.4.2. Open file $ORACLE_INSTANCE/config/OHSComponent/ <ohs-comp-name >/moduleconf/mod_osso.conf in a text editor

Add the following lines before the closing </IfModule > line:

<Location /discoverer/plus >require valid-userAuthType Osso</Location >

<Location /discoverer/viewer >require valid-userAuthType Osso</Location >

<Location /discoverer/app >require valid-userAuthType Osso</Location >

Save the mod_osso.conf file.

5.2.4.3. Re-start Discoverer services using ohs restart.

5.2.4.4. Start Fusion Middleware Control, and navigate to the Discoverer Administration page. Select the 'Allow authenticated Oracle Single Sign-On (SSO) users to create and use private connections to SSO-enabled Oracle Applications databases, without entering a password' check box. Verify attribute enableAppsSSOConnection="true" in <DOMAIN_HOME >/config/fmwconfig/servers/WLS_DISCO/applications/ <discoverer_version >/configuration/configuration.xml

For detailed information on Single Sign-On for the Discoverer node, refer to instructions in the Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer 11g Release 1 (11.1.1).

5.3. Install Discoverer Administrator (Optional)

5.3.1. Install Discoverer Administrator (Optional)

Discoverer Administrator is a Windows-only application used by the Discoverer administrator to create and maintain a business oriented view of relational data. Discoverer Administrator is included in the Microsoft Windows software of the Oracle Portal, Forms, Reports and Discoverer 11g Release 1 (11.1.1).

Install Discoverer Administrator on a Windows PC if you wish to customize your Discoverer End User Layer. Refer to the Oracle Fusion Middleware Administrator's Guide for Oracle Business Intelligence Discoverer 11g Release 1 (11.1.1).

5.3.2. Set Windows Registry Settings

If you are using Discoverer Administrator on Windows to refresh your End User Layer, please follow the steps below to set necessary registry settings.

This step contains information about modifying the Microsoft Windows registry. Before you modify the Windows registry, back it up and make sure that you understand how to restore it if a problem occurs. For information about how to back up, restore, and edit the registry, see the following article in the Microsoft Knowledge Base:

Q256986 Description of the Microsoft Windows Registry

On the Windows PC running Discoverer Administrator:

5.3.2.1 Back up your current Microsoft Windows Registry

5.3.2.2 Open the Windows Registry editor and create or update the following registry keys:

Registry Key DataType Value

HKEY_CURRENT_USER\Software\Oracle\Discoverer 11\Database\EnableTriggers

REG_DWORD

1

HKEY_CURRENT_USER\Software\Oracle\Discoverer 11\Database\DefaultPreserveDisplayPropertyForRefresh

REG_DWORD

1

5.3.3. Copy Database Connection file

On your Discoverer Administrator node, create a directory where you will copy the dbc files of one or more E-Business Suite Release 12 instances you are setting up Discoverer with, for example D:\secure. Copy the dbc file from the $FND_SECURE directory of the E-Business Suite Release 12 instance you are setting up Discoverer with to the directory you just created. Then create a Windows System Variable FND_SECURE to specify the directory you just created, for example D:\secure.

5.3.4. Update tnsnames.ora file

On your Discoverer Administrator node, update file %ORACLE_HOME%/network/admin/tnsnames.ora and include the tnsnames entry to connect to your Oracle E-Business Suite Release 12 database. Use the same entry as exists in the tnsnames.ora file on your Oracle E-Business Suite Release 12 application tier server node. The database name must match the two_task entry in the dbc file.

5.4. Upgrade from earlier versions of Discoverer

Discoverer Version 11.1.1 uses the same EUL version as Discoverer 10.1.2; therefore, no EUL upgrade is required. The database connection (dbc) file will not be transferred during the upgrade. After the upgrade, please perform Section 5.2.1 "Copy Database Connection file" manually.

If you are using a version of Discoverer earlier than 10.1.2, or if you want to migrate user preferences and customizations from Discoverer 10.1.2 and earlier, please refer to section Upgrading from Earlier Versions of Discoverer in the Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer 11g Release 1 (11.1.1).

5.5. Create new Discoverer 11.1.1 End User Layer

If you do not have an existing Discoverer End User Layer, you must create a new Discoverer 11.1.1 End User Layer. Fresh installations of E-Business Suite Release 12 Production do not contain a pre-installed Discoverer End User Layer. Only the E-Business Suite Release 12 Vision database contains a pre-installed Discoverer End User Layer.

We recommend that you create a new tablespace to store database objects for the Discoverer 11.1.1 End User Layer in your E-Business Suite Release 12 database.

5.5.1. Set Your Environment

Execute this step on your database tier with your environment pointing to your database ORACLE_HOME. To set the environment correctly, source the file:

[DB_ORACLE_HOME]/ <dbname >.env

5.5.2. Create the Discoverer Tablespace

Start SQL*Plus and create a tablespace named 'DISCOVERER' with an initial size of 200 megabytes, using the absolute path to the subdirectory where your datafiles are located:

% sqlplus /NOLOGSQL> connect sys/ <sys_password > as sysdbaSQL> create tablespace DISCOVERER datafile \'[DB_ORACLE_HOME]/dbf/discoverer01.dbf' size 200M reuse \extent management local uniform size 128K;SQL> /Statement Processed

5.5.3. Exit SQL*Plus:

SQL> quit

5.5.4. Create the Discoverer End-User Layer

Before running command line scripts, you must source environment variables.

Edit script $ORACLE_INSTANCE/Discoverer/Discoverer_asinst_1/util/discenv.sh and add following two lines:

export TNS_ADMIN=$ORACLE_INSTANCE/configexport FND_SECURE=$ORACLE_INSTANCE/config/Discoverer/Discoverer_asinst_1

Variable TNS_ADMIN points to the directory that contains the tnsnames.ora file that you edited in Section 5, Step 5.2.2.Variable FND_SECURE points to the directory that you copied the dbc file to in Section 5, Step 5.2.1.

Find the line in $ORACLE_INSTANCE/Discoverer/Discoverer_asinst_1/util/discenv.sh that defines variable NLS_LANG and set it as follows:

NLS_LANG="AMERICAN_AMERICA.UTF8"

Platform specific environment settings

If you are using Discoverer on 64 bit platforms (Oracle Solaris on SPARC 64 bit, HP-UX PA-RISC 64 bit, HP-UX Itanium 64 bit, IBM AIX 64 bit, Linux x86-64), find the line in $ORACLE_INSTANCE/Discoverer/Discoverer_asinst_1/util/discenv.sh that defines variable LIB_PATH and set it as follows:

LIB_PATH=$OH/discoverer/lib:$OH/lib:/usr/lib:$OH/lib32

If you are using Discoverer on 64 bit platform Linux x86-64, find the line that defines variable LD_ASSUME_KERNEL and comment it:

#export LD_ASSUME_KERNEL=2.4.19

A future Discoverer patch will set above values in the environment script automaticaly.

Source the environment script.

. $ORACLE_INSTANCE/Discoverer/Discoverer_asinst_1/util/discenv.sh

Windows users only:

Create a windows system variable FND_SECURE pointing to the directory that holds the dbc file as detailed in Section 5, Step 5.2.1, before executing AD utility scripts $AU_TOP/discover/adupdeul.sh, $AU_TOP/discover/adrfseul.sh

Create the new Discoverer 11.1.1 End User Layer by using the following command syntax, executed on the standalone application server where Oracle Business Intelligence Discoverer 11g Release 1 was installed in Step 5.1.

$ORACLE_HOME/bin/eulapi \-CREATE_EUL \-APPS_MODE \-CONNECT system/ <password >@ <db > \-USER <EUL_User_Prefix >_US \-PASSWORD <password > \-DEFAULT_TABLESPACE <default tablespace > \-TEMPORARY_TABLESPACE <temp tablespace > \-EUL_LANGUAGE US \-APPS_GRANT_DETAILS <FNDNAM >/ <FNDNAM password >

For example:

$ORACLE_HOME/bin/eulapi -CREATE_EUL -APPS_MODE \-CONNECT system/manager@cus120 -USER EUL_US -PASSWORD EUL_US \

-DEFAULT_TABLESPACE discoverer -TEMPORARY_TABLESPACE temp \-EUL_LANGUAGE US -APPS_GRANT_DETAILS apps/apps

Alternatively, you may also use the equivalent Discoverer Administrator command line on Windows. Use the following syntax to create the End-User Layer using Discoverer Administrator:

%ORACLE_HOME%/bin/dis51adm.exe /CREATE_EUL /APPS_MODE \/CONNECT system/manager@cus120 /USER EUL_US /PASSWORD EUL_US \/DEFAULT_TABLESPACE discoverer /TEMPORARY_TABLESPACE temp \/EUL_LANGUAGE US /APPS_GRANT_DETAILS apps/apps /SHOW_PROGRESS

5.6. Specify Java Virtual Machine for Discoverer Plus

Chapter 'About running Discoverer Plus with different Java Virtual Machines' of the Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer 11g Release 1 (11.1.1) explains how to run Discoverer Plus with different Java Virtual Machines. You must configure OracleBI Discoverer Plus to use the same Plug-in version as being used for E-Business Suite Release 12. Please also refer to My Oracle Support Knowledge Document Document 393931.1 titled "Upgrading Sun J2SE (Native Plug-in) with Oracle Applications 12.0 for Windows Clients".

Section 6: Post-Installation Tasks

This section describes steps for configuring Oracle E-Business Suite Release 12 to use Discoverer 11.1.1, and for loading the E-Business Suite-specific content and workbooks into the Discoverer 11.1.1 End User Layer.

6.1. Apply the latest AutoConfig patch

Follow My Oracle Support Knowledge Document Document 387859.1 titled Using AutoConfig to Manage System Configurations with Oracle E-Business Suite Release 12 and apply the latest available AutoConfig Patch to your system.

6.2. Apply AD Patch containing adupdeul.sh and adrfseul.sh

E-Business Suite Version

One-off Patch

12.0.x 9384228

12.1.x 9394002

Download the appropriate patch and follow the instructions provided in the patch readme to apply the patch to your E-Business Suite installation.

6.3. Set Applications Profile Options for Discoverer using AutoConfig

Proceed with the following steps to allow AutoConfig to switch profile options for your remote, standalone Oracle Business Intelligence Discoverer 11g Release 1 server.

Login to Oracle Applications Manager and navigate to Site Map > AutoConfig > Edit Parameters.

Specify following variable:

TitleVariable Name

Description Value

Discoverer URL

s_disco_url Set the value of this variable to

<protocol >:// <machine.domain >: <port >

the base URL where Discoverer is available.

for example: http://mybi.company.com:7780

Run AutoConfig to generate all configuration files for the APPL_TOP and the ORACLE_HOMEs in its supporting technology stack:

% <ADMIN_SCRIPTS_HOME >/adautocfg.sh

6.4. Set Applications profile options in Oracle E-Business Suite

Log into E-Business Suite Release 12 with the System Administrator responsibility

Navigate to the Profile > System form

Query the %Discoverer% profile options.

Ensure the following ICX profile options in Oracle E-Business Suite are set to:

Profile Description Value

ICX: Discoverer Launcher

URL that points to Discoverer Plus Servlet.

http:// <HTTP Server >: <Port >/discoverer/plus

?Connect=[APPS_SECURE]

ICX: Discoverer Viewer Launcher

URL that points to Discoverer Viewer Servlet

http:// <HTTP Server >: <Port >/discoverer/viewer

?Connect=[APPS_SECURE]

ICX: Discoverer use Viewer

Specify whether Discoverer Viewer should be launched instead of Discoverer Plus (default).

Yes | No

ICX: Discoverer Default End User Layer Schema Prefix

The EUL prefix in combination with the Language code make up the EUL owner at runtime. For example EUL owner EUL_US has EUL prefix EUL.

You may switch the ICX_DEFAULT_EUL profile at the responsibility level if you are planning to implement multiple End User Layers.

EUL

ICX: Discoverer End User Layer Language Override

Since the End User Layer content is currently available in US English only, it is possible to override the user's general language preference for the

American English

Discoverer End User Layer using this profile option. The specified End User Layer language will be used regardless of the individual user's language preferences.

This profile does not affect the National Language Support parameters passed to Discoverer. The Discoverer User Interface will still appear according to the users ICX_LANGUAGE and ICX_TERRITORY profiles. The User Interface language will only change for valid combinations of ICX_LANGUAGE and ICX_TERRITORY.

ICX: Discoverer Release

Single number specifying the Discoverer release.

Leave this at default value <NULL > as there is no difference in invocation of the two supported Discoverer releases 10g and 11g for E-Business Suite Release 12.

11

ICX: Discoverer Parameters

This profile can be used to optionally pass additional URL parameters to Discoverer.

exitURL= <E-Business Suite Home Page >

For Example

exitURL=http:// <HTTP Server >: <Port >

/OA_HTML/OA.jsp?OAFunc=OAHOMEPAGE

Discoverer DBC filename override

This profile can be used to specify the DBC Filename Discoverer should be using to connect to the E-Business Suite database.

By default, this profile should remain NULL, in which case Discoverer will use the default dbc file for your E-Business Suite database.

<NULL >

The remaining steps in this section include patching your End User Layer to the latest level and are required only if you received new .eex files. For example, you need to complete the following steps only if you are upgrading from E-Business Suite Release 11i to E-Business Suite Release 12, or if you implement the Discoverer End User Layer for the first time.

If you have only migrated your existing End User Layers to Discoverer 11.1.1 without patching new eex files, you can skip the remaining steps in this section.

If you are uncertain as to whether you have received any new eex files, you may continue with the following steps. These steps can be reapplied any time to synchronize your End User Layer with your latest eex file patchlevel.

6.5. Regenerate your Business Views (Conditional)

Most of the Discoverer folders delivered as part of the Oracle E-Business Suite Release 12 Discoverer content are based on Business Views. Business Views hide the complexity of the underlying Release 12 data model from non-technical users. Before you import or refresh the Discoverer .eex files you must regenerate all Business Views. This will enable the Discoverer import and refresh process to pull in the translated prompts for Key and Descriptive Flex Fields of your Business Views into your End User Layer. Make sure that every flexfield structure has at least one valid segment, and that all flexfields are frozen and compiled.

6.5.1. Run the "Generate Business Views by Application" Concurrent Program

Regenerate your Business Views by running the "Generate Business Views by Application" concurrent program using the Business View Setup responsibility:

Logon to Oracle E-Business Suite as SYSADMIN Choose the "Business Views Setup" responsibility Navigate to Reports > Run > Pick Single Request > "Generate ALL Business Views"

In case you don't have "Business Views Setup" responsibility assigned to SYSADMIN user, please do the following:

Logon to Oracle E-Business Suite as SYSADMIN Choose the "System Administrator" responsibility. Navigate to Security > User > Define and add responsibility "Business Views Setup"

to user SYSADMIN.

For additional details and background, refer to the Oracle Applications Flexfields Guide .

6.5.2. Check for Errors

After regeneration of the Business Views has been completed, check the Business View Generator output file. It should not contain any errors.

6.5.3. Recompile APPS objects

Recompile all objects in the APPS schema using adadmin.

6.5.4. Check Business Intelligence System Views

Ensure that the Business Intelligence System views exist and all Business Intelligence System views are valid by issuing the following command in SQL*Plus:

% sqlplus apps/ <password >@ <db >SQL> select object_name from user_objectswhere object_type = 'VIEW' andstatus = 'INVALID' and( object_name like '%FV_%' or object_name like '%FG_%' orobject_name like '%BV_%' or object_name like '%BG_%' )and object_name in (select sobj_ext_table from eul_us.eul5_objs);

Replace "eul_us" with the actual eul schema being used.

If necessary, recompile those objects so that all views are valid. The Discoverer refresh process may stop if a select statement from a invalid Business Intelligence System View causes the following error:

ORA-04063: view "APPS. <View Name >"

All invalid objects and errors must be resolved before you can proceed with the next steps, including import and refresh of the Discoverer End User Layer. Discoverer Administrator will drop End User Layer objects with dependencies on invalid E-Business Suite objects during the refresh process.

6.6. Set up E-Business Suite User/Responsibility for EUL Administration: SYSADMIN/System Administrator

The E-Business Suite Release 12 System Administrator account must be granted permission to update and alter Discoverer 11.1.1 content.

6.6.1. Grant End User Layer Administration Privileges

Grant the End User Layer Administration privileges for user SYSADMIN using the following command, executed on the standalone application server where Oracle Business Intelligence Discoverer 11g Release 1 was installed in Step 5.1 .

$ORACLE_HOME/bin/eulapi \-CONNECT <EUL schema >/ <password >@ <db > \-GRANT_PRIVILEGE \-USER SYSADMIN \-PRIVILEGE administration \-PRIVILEGE all_admin_privs \-LOG <log file name >

For all further End User Layer Administration activities you must use the Oracle E-Business Suite User with the System Administrator responsibility (e.g. SYSADMIN). This E-Business Suite user must import and own the Workbooks and Business Areas of all future Discoverer patches and share them as applicable with other E-Business Suite users and responsibilities.

6.6.2. Make sure user SYSADMIN has full security access to all Business Areas

This step is not necessary for the first import into a new End User Layer because the End User Layer does not contain any Business Areas at this point. But for all subsequent future imports, ensure that the user SYSADMIN has full access to all Business Areas.

Execute the following command on the standalone application server where Oracle Business Intelligence Discoverer 11g Release 1 was installed in Step 5.1 .

$ORACLE_HOME/bin/eulapi \-CONNECT <EUL schema >/ <password >@ <db > \-GRANT_PRIVILEGE \-USER SYSADMIN \-BUSINESS_AREA_ADMIN_ACCESS % \

-WILDCARD \-LOG <log file name >

6.7. Access directory $AU_TOP/discover on your E-Business Suite Release 12 instance from your Oracle Business Intelligence Discoverer 11g BI instance

Discoverer .eex files are patched to your E-Bussiness Suite Release 12 instance, directory $AU_TOP/discover. Those files must be accessible from the standalone application server where Oracle Business Intelligence Discoverer 11g Release 1 was installed.

Please mount your applications tier server node, directory $AU_TOP/discover on your standalone application server where Oracle Business Intelligence Discoverer 11g Release 1 was installed.

If you are unable to mount this directory, you can also zip and ftp the entire $AU_TOP/discover directory. In this case, make sure that you include the directory structure (ie. use zip -r) when you create the zip, and preserve the directory structure when you unzip the file on the standalone application server where Oracle Business Intelligence Discoverer 11g Release 1 was installed. The directory structure will include the import shell scripts $AU_TOP/discover/adupdeul.sh, $AU_TOP/discover/adrfseul.sh and the language specific subdirectories containing the set of .eex files.

6.8. Import Discoverer Content for E-Business Suite Release 12 using adupdeul.sh mode=complete

In this step, you will run AD utility adupdeul.sh on the standalone application server where Oracle Business Intelligence Discoverer 11g Release 1 was installed to import the Discoverer loader files (.eex files) for Oracle E-Business Suite Release 12 into the Discoverer End User Layer. If you are using a E-Business Suite Release 12 Vision database, you can skip this step. E-Business Suite Release 12 Vision database already contains a pre-installed Discoverer 11.1.1 End User Layer.

6.8.1. Check Your Location

On the standalone application server where Oracle Business Intelligence Discoverer 11g Release 1 was installed, move to the mounted or copied ... /discover/ directory where adupdeul.sh is located

6.8.2. Source Environment Variables

Before running command line scripts adupdeul.sh or adrfseul.sh, you must source environment variables.

Source the environment script.

. $ORACLE_INSTANCE/Discoverer/Discoverer_asinst_1/util/discenv.sh

6.8.3. Improving the Speed of the Import Process

Performance of the import process greatly depends on:

Network latency between the Oracle Business Intelligence Discoverer 11g node and the database

Available resources on your Oracle Business Intelligence Discoverer 11g node

Depending on these factors, the import process may take less than one hour or up to several hours to complete for the entire set of Discoverer baseline .eex files. To minimize overhead from network latency during the import process, it is strongly recommended that Oracle Business Intelligence

Discoverer 11g be installed on a machine that is close to the database server and has a fast network connection.

6.8.4. Start the Import Process

Start the import process of the Discoverer loader files (.eex files) using the shell script adupdeul.sh.

Use the following syntax for the adupdeul.sh script:

% sh adupdeul.sh \connect= <APPS admin user >/ <password >@ <two_task >resp= <APPS administrator responsibility >gwyuid= <APPS GWYUID >fndnam= <APPS FNDNAM >secgroup= <secgroup >topdir= <topdir >language=USeulprefix= <eulprefix >iashome= <iashome >[eultype= <eultype >][mode= <mode >][driver= <driver >][filelist= <filelist >][logfile= <logfile >][parfile= <parfile >]

Where:

Parameter Description

secgroup APPS responsibility security group

topdir Top level directory where Discoverer files are available

iashome Oracle Business Intelligence Discoverer 11g Oracle Home directory

eulprefix EUL schema prefix. For example, use eulprefix=EUL for schema EUL_US

eultype OLTP - default, for standard E-Business Suite Release 12 Discoverer contentEDW - for Enterprise Data Warehouse Discoverer content

Use eultype=OLTP to import the Discoverer content for Oracle E-Business Suite Release 12

mode COMPLETE - import all Discoverer content.DRIVER - default, import specific subset of filesFILELIST - import specific subset of files

For the initial full import of the Discoverer baseline files, use mode=complete. This mode will upload all .eex files (*o.eex) from the .../discover/ directory into the Discoverer End User Layer.

driver Specifies a comma-separated list of driver files to be loaded. This parameter is required if mode=DRIVER

filelist Specifies the filename of a file containing a list of files to be loaded. This parameter is required if mode=FILELIST

logfile Log file where the adupdeul.sh script logs the result of the import process. Default filename is adupdeul.log

parfile Filename of a command-line parameter file containing entries of the form PARAMETER=VALUE. Parameters specified at the command line take precedence over those specified in the parameter file.

All parameters must be specified on a single command line or in a parameter file. Name-value pairs must not contain spaces. For example:

PARAMETER=VALUE is acceptable

PARAMETER = VALUE will generate errors

For example:

Mount or copy the directory $AU_TOP/discover as /user1/au_top/discover

cd /user1/au_top/discover (where adupdeul.sh is located)

Start the full import of all .eex files in topdir/US, where topdir is specified as a parameter

sh adupdeul.sh \connect=sysadmin/sysadmin-password@db \resp="System Administrator" \gwyuid=APPLSYSPUB/PUB \fndnam=APPS \secgroup="Standard" \topdir=/user1/au_top/discover \language=US \eulprefix=EUL \eultype=OLTP \mode=complete \iashome=/oracle/iAS/bi \logfile=import_complete_eul_us_cust120.log

Windows users only:

When executing AD utility scripts $AU_TOP/discover/adupdeul.sh or $AU_TOP/discover/adrfseul.sh, you must use Unix syntax to specify the path seperator instead of Windows syntax. Use the forward slash ("/") instead of back slash ("\") as the separator.

For example, use:topdir=C:/user1/au_top/discover

6.8.5. Check for Import Errors

Check the logfile after import. This should be a clean import logfile. You should be able to see that the import utility exited with status 0 and the logfile contains the message Import completed successfully.

You can safely ignore the following messages in the import log:

<topdir >\ <language >\ <file >.eex: The import process did not import or modify any data.

This messages provides information that <file >.eex is an empty obsolete file and does not modify any data during import.

Refer to Section 10.2 for additional known import warnings captured in the log file during import of the full set of eex into an E-Business Suite Release 12 Vision Database.

6.8.6. Post-Install Patching Considerations

As E-Business Suite Release 12 products continually update and improve support for Discoverer in subsequent releases, it will be necessary to install additional Discoverer loader files after this initial installation. Please refer to Section 9 for details on importing subsequent patches using mode=driver.

6.9. Refresh the Discoverer 11.1.1 End User Layer

After the Discoverer content for E-Business Suite Release 12 has been imported into the Discoverer End User Layer on the database tier, the End User Layer must be refreshed against the Release 12 data model. This ensures that all references between business areas, folders, workbooks, business views, flexfields, and Release 12 database objects are valid.

On Unix platforms you may run the refresh process on the standalone application server where Oracle Business Intelligence Discoverer 11g Release 1 was installed.

Alternatively on Windows platforms you may run the refresh process on the machine where Discoverer Administrator is installed.

6.9.1. Check Your Location

Move to the ... /discover/ directory where adrfseul.sh is located.

6.9.2. Source Environment Variables

Before running command line scripts adupdeul.sh or adrfseul.sh, you must source environment variables.

Source the environment script.

. $ORACLE_INSTANCE/Discoverer/Discoverer_asinst_1/util/discenv.sh

6.9.3. Start the Refresh Process

Start the refresh process against the database using the shell script adrfseul.sh.

For the refresh process you must use the E-Business Suite User/Responsibility SYSADMIN:System Administrator to logon rather than the End User Layer database schema owner. The End User Layer database schema owner doesn't have the necessary grants for the APPS schema and the refresh process would drop Discoverer folders! Using adrfseul.sh for the refresh enforces using E-Business Suite User/Responsibility in the connect string.

Syntax for the adrfseul.sh script:

% sh adrfseul.sh connect= <APPS admin user >/ <password >@ <twotask >resp= <APPS administrator responsibility >gwyuid= <APPS GWYUID >fndnam= <APPS FNDNAM >secgroup= <APPS security group >eulschema= <eul schema >eulpassword= <eulpassword >twotask= <twotask >iashome= <iashome >[logfile= <logfile >][parfile= <parfile >]

Where:

Parameter Description

eulschema Full EUL schema name, for example eulschema=EUL_US

eulpassword EUL schema password.

twotask Database name as specified in your tnsnames.ora file.

iashome Oracle Business Intelligence Discoverer 11g Oracle Home directory

logfile Log file where the adupdeul.sh script logs the result of the import process. Default filename is adrfseul.log

parfile Filename of a command-line parameter file containing entries of the form PARAMETER=VALUE. Parameters specified at the command line take precedence over those specified in the parameter file.

All parameters must be specified on a single command line or in a parameter file. Name-value pairs must not contain spaces. For example:

PARAMETER=VALUE is acceptable

PARAMETER = VALUE will generate errors

For example, change your directory to the location of adrfseul.sh:

cd /user1/au_top/discover

Start the refresh process of all existing eul folders against the database

sh adrfseul.sh \connect=sysadmin/sysadmin-password@mydb \resp="System Administrator" \gwyuid=APPLSYSPUB/PUB \fndnam=APPS \secgroup="Standard" \eulschema=EUL_US \eulpassword=EUL123 \twotask=mydb \iashome=/oracle/iAS/bi \logfile=refresh_eul_us_mydb.log

Expect several hours for the refresh process for all Business Areas to complete, depending on your flex structure. The refresh utility will refresh all folders in your End User Layer one by one and should exit with status 0.

Once completed, your End User Layer is now refreshed. Flex columns have been pulled in to the folders using the flex prompts in the language of the End User Layer as Item Display Names.

6.10. Grant Access to Responsibilities, Users, and Workbooks (Optional)

Individual Discoverer users may be granted access to specific Release 12 responsibilities, which in turn provide access to Discoverer business areas and workbooks. Either the Discoverer eulapi command-line utility or Discoverer Administrator can be used to associate business area access with Release 12 responsibilities, and to identify workbook access privileges for responsibilities and users.

The procedures described in this step may be used as guidelines for planning your Discoverer reporting security. Your Discoverer reporting strategy may be defined to reflect your corporate data security strategy, policies, and business requirements. Discoverer security is flexible and highly granular, and you may wish to provide broader access for specific individuals who need to be able to see data enterprise-wide, i.e. across organizational boundaries.

Example: You may wish some HRMS Administrator to have access to HRMS - Administration business areas, such as the Oracle Human Resources and Oracle iRecruitment. To do this, grant access to all of the HRMS - Administration business areas to a new or existing responsibility for ex. 'Human Resources Intelligence - Administrator (OLTP)'. This responsibility may then be granted to the individual HRMS Administrators who should have access to those areas.

6.10.1 Grant Privileges, Security and Workbook Access on Unix

You must grant security access to the Oracle E-Business Suite Release 12 responsibilities you would like to use for each Business Area.

You may use the Discoverer eulapi command line utility on the standalone application server where Oracle Business Intelligence Discoverer 11g Release 1 was installed in Step 5.1 to grant privileges, business area security and workbook access.

For help on usage of the eulapi command-line utility, type:

$ORACLE_HOME/bin/eulapi -help grant_privilege

Example 1: Grant Discoverer User privileges to responsibility "Human Resources Intelligence - Administrator (OLTP)"

$ORACLE_HOME/bin/eulapi \-CONNECT <EUL schema >/ <password >@ <db > \-GRANT_PRIVILEGE \-ROLE "Human Resources Intelligence - Administrator (OLTP)" \-PRIVILEGE all_user_privs

Example 2: Grant security access for business area "General Ledger" to responsibility "Human Resources Intelligence - Administrator (OLTP)"

$ORACLE_HOME/bin/eulapi-CONNECT <EUL schema >/ <password >@ <db > \-GRANT_PRIVILEGE \-ROLE "Human Resources Intelligence - Administrator (OLTP)" \-BUSINESS_AREA_ACCESS "General Ledger"

6.10.2. Share Workbooks using Discoverer User or Plus Edition

You must grant shared workbook access to the Oracle E-Business Suite responsibilities to be used for workbook analysis.

Log in to the Discoverer Desktop or Plus Edition as the E-Business Suite Administrator user who imported the eex files in Section 6.8.

Use the Help -> About Discoverer... dialog to confirm that you are connected to the correct End User Layer ( <EULprefix >_ <Lang >; compare the import options used in above). You can change the End User Layer in the dialog Tools -> Options -> Default EUL.

Using the Tools -> Manage Workbooks -> Select a workbook -> Share

Share the workbooks to the E-Business Suite Users and Responsibilities that should be allowed to open the various workbooks.

6.10.3. Test Discoverer Responsibilities and Workbooks

Log in to Oracle E-Business Suite Release 12 with a userid that has been granted one of the responsibilities defined above.

Open the Release 12 workbooks assigned to that responsibility and verify that they can retrieve and display data.

Repeat for each responsibility that has been defined.

Congratulations!

You have completed your Oracle Business Intelligence Discoverer Release 11g (11.1.1) implementation and your Discoverer content for Oracle E-Business Suite Release 12 is ready for use.

Section 7: Available Documentation

Oracle Portal, Forms, Reports and Discoverer 11g Release 1 (11.1.1) Documentation Installing Oracle Application Server 10g with Oracle E-Business Suite Release R12 Using Oracle Internet Directory 11gR1 Patchset 1 (11.1.1.2.0) and Oracle Single Sign-on with

Oracle E-Business Suite

Section 8: Conventions and Important Directory Locations

Conventions

The following typographical conventions are used in this document:

Convention Meaning

\In examples of commands you type online, a backward slash at the end of a line signifies that you must type the entire command on one line. Do not type the backslash.

Mono space text Represents command line text. Type this text exactly as shown.

<> or [] Text enclosed in angled or square brackets represents a variable. Substitute an appropriate value for the variable text. Do not type the brackets.

Directory Paths

Directory paths in this document are relative to the top level installation directory for the Oracle E-Business Suite. e.g. if you installed the Oracle E-Business Suite under a directory named /my/appsinstall and are pointing to an Oracle E-Business Suite Release 12 database named mytestdb, then <dbname >ora/iAS/Apache in this document will mean the fully qualified path: /my/appsinstall/mytestdbora/iAS/Apache

Section 9: Installation of Additional Discoverer End User Layer patches

After you have successfully installed or migrated your Discoverer End User Layer by following the above steps, you may need to install and import additional patches for your End User Layer at a later date. This section explains how to use adupdeul.sh for installing patches to the End User Layer.

Essentially the steps are the same as described above for the interoperability patch, with the key difference that you import only those .eex files included in the later Discoverer content patch. Check the readme of the Discoverer content patch for any necessary required prerequisite patches to be applied. Apply the required prerequisite patches before applying the patch to the Discoverer End User Layer.

You may need to regenerate some or all of the Business Intelligence System Views for the product updated by the additional content patch. After importing the content patch, you may need to refresh the Business Areas for the product affected by the additional patch.

9.1. Import using adupdeul.sh mode=complete

When importing all of the Discoverer content for Release 12 for the first time, the adupdeul.sh script was run with the command line parameter

mode=complete

Mount or copy the directory $AU_TOP/discover as /user1/au_top/discover

cd /user1/au_top/discover (where adupdeul.sh is located)

Start the full import of all .eex files in topdir/US, where topdir is specified as a parameter.

For example:

sh adupdeul.shconnect=sysadmin/sysadmin-password@dbresp="System Administrator"gwyuid=APPLSYSPUB/PUBfndnam=APPSsecgroup="Standard"topdir=/user1/au_top/discoverlanguage=USeulprefix=EULeultype=OLTPmode=completeiashome=/oracle/iAS/bilogfile=import_complete_eul_us_cust120.log

9.2. Import using adupdeul.sh mode=driver

When importing an individual content patch for an existing Discoverer End User Layer, run the adupdeul.sh script with the command line parameter

mode=driver

Example for import of eex files from patch 1234567:

Mount or copy the directory $AU_TOP/discover as /user1/au_top/discover

cd /user1/au_top/discover (where adupdeul.sh is located)

Start the import for just the eex files for the Discoverer patch. Syntax for the adupdeul script in driver mode:

sh adupdeul.shconnect=sysadmin/sysadmin-password@dbresp="System Administrator"gwyuid=APPLSYSPUB/PUBfndnam=APPSsecgroup="Standard"topdir=D:/au_top/discoverlanguage=USeulprefix=EULeultype=OLTP

mode=driverdriver=c1234567.drviashome=/oracle/iAS/bilogfile=import_c1234567_eul_us_cust120.log

Check the logfile after import. This should be a clean import logfile. Verify that the import utility exited with status 0 and the logfile contains the message Import completed successfully.

Refresh the Business Areas for the product affected by the patch.

9.3. Use a Parameter File for adupdeul.sh

Optionally you can create a parameter file in the same directory where adupdeul.sh is located using a text editor. You can save parameters which are likely to stay the same for any patch. Instead of specifying those parameters for each patch you can then just specify the parameter file.

Example for import of the eex files from patch 1234567 using a parameter file:

Specify parameter values in a parameter file, for example oltpeul.lst

resp="System Administrator"gwyuid=APPLSYSPUB/PUBfndnam=APPSsecgroup="Standard"topdir=D:/au_top/discovereulprefix=EULeultype=OLTPiashome=/oracle/iAS/bi

Start the import for just the eex files of a given patch 1234567 with parameter file oltpeul4.lst

sh adupdeul.shconnect=sysadmin/sysadmin-password@dblanguage=USmode=driverdriver=c1234567.drvparfile=oltpeul.lstlogfile=import_c1234567_eul_us_cust120.log

Section 10: Known Issues and Limitations

10.1. Marketing Online List Generation feature

Marketing Online List Generation feature relies on the format of the sql generated by Discoverer. Marketing Online customers must set following server preference.

10.1.1. Open the file <ORACLE_INSTANCE >/config/PreferenceServer/Discoverer_ <instance-name >/pref.txt in a text editor

10.1.2. Add following preference setting to the Database section of the pref.txt file:

[Database]

SQLType = 3

10.1.3. Save the updated pref.txt file.

10.1.4. Run the script <ORACLE_INSTANCE >/Discoverer/Discoverer_ <instance-name >/util/applypreferences.sh

10.2. Warnings in the End User Layer import log file

Following warnings that you may see in the import log file on import of the full set of eex files into a E-Business Suite Release 12 Database are not considered critical and are expected to be addressed by a future patchset.

/SLOTS/slot06/appmgr/apps/apps_st/appl/au/12.0.0/discover/US/iscwshshptlctflo.eex:Duplicate element definition: Date Hierarchy with identifier 'ISC_DEFAULT_DATE_HIERARCHY'

/SLOTS/slot06/appmgr/apps/apps_st/appl/au/12.0.0/discover/US/fiiarbilwbo.eex:Could not locate the Eul User with name 'EUL_US' in the target End User Layer

/SLOTS/slot06/appmgr/apps/apps_st/appl/au/12.0.0/discover/US/poapoaprchsngbao.eex:A Business Area Grant has not been imported because it depends on the Eul User with name 'Purchasing Intelligence'

/SLOTS/slot06/appmgr/apps/apps_st/appl/au/12.0.0/discover/US/fiiarnrndrv01flo.eex:An imported Item Class had display name 'Unbilled Receivable Distributions: Transaction Number' renamed to 'Unbilled Receivable Distributions: Transaction Number 1'

/SLOTS/slot06/appmgr/apps/apps_st/appl/au/12.0.0/discover/US/pjipaprsntypeflo.eex:An imported Item Class had display name 'Person Type' renamed to 'Person Type 1'

A folder named 'School District Tax Information' was created or modified during the import but is not in a business area.

A folder named 'CE IDA Sources' was created or modified during the import but is not in a business area

10.3. Windows specific "afenv: can't open registry key." errors

This error may be seen during EUL import and refresh process. These errors can be safely ignored.

10.4. Warnings during opatch application

During patch application with opatch release 11.1.0.6.9, you might encounter below message which can be safely ignored.

OPatch/opatch[420]: -d64: not found.

10.5. Discoverer version is displayed as '11.1.1.2.0' in Enterprise Manager Fusion Middleware Control 11g

After upgrading to Discoverer 11gR1 PS2 (11.1.1.3.0), the version displayed for Discoverer in EM Fusion Middleware Control is '11.1.1.2.0', this is expected behaviour, see Bug 9826973. To verify that you are running Discoverer version 11.1.1.3.0, check the link at the bottom of the Discoverer Plus or Discoverer Viewer connect page - 'About Oracle BI Discoverer Viewer/Discoverer Plus Version 11.1.1.3.0.'

 

Change Log

Date Description

Jul 15, 2009 Initial document created.

Jan 12, 2010 Added line to source discenv.sh before running adupdeul.sh.

Feh 25, 2010 Added required one-off patch.

Apr 29, 2010 Added windows specific known Issue.

Apr 29, 2010 Added LIB_PATH env setting for 64 bit platforms.

Jun 04, 2010 Added sub-section for 11.1.1.3.0 patchset.

Jun 30, 2010 Added Note boxes for certification clarification.

Jul 26, 2010 Added 10.5 in Known issues

Aug 11, 2010 Removed note from the header as all platforms are now certified

My Oracle Support Knowledge Document 1074326.1 by Oracle Applications DevelopmentCopyright 2010 Oracle CorporationLast updated: Aug 11, 2010

Related

Products

Oracle E-Business Suite > Applications Technology > Technology Components > Oracle Applications Technology Stack

Errors

ORA-4063

Back to top

Rate this document  

Article RatingRate this document

Excellent

Good

Poor

Did this document help you?

Yes

No

Just browsing

How easy was it to find this document?

Very easy

Somewhat easy

Comments

1074326.1

Not easy

Cancel

Provide some feedback