Softwares required for Discoverer 10g Installation: 1) Oracle BI tools 10g (10.1.2.0.

2)
2) Oracle Discoverer 10.1.2.3 ### Patch 5983622

3) Discoverer 10g (10.1.2.3) Cumulative Patch 7111842

Here on OTN, not seeing Oracle BI tools 10g (10.1.2.0.2) for Linux x86/x86_64. So we have to request to Oracle for the same to download from their FTP site.

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

Installation of Oracle Discoverer 10.1.2 with Oracle Business Intelligence Server 10g Release 2 on a standalone application tier server node, or in a separate Oracle Business Intelligence Server 10g Release 2 ORACLE_HOME on an existing application tier server node. Creation of the Oracle Discoverer 10.1.2 End User Layer (EUL) on a database tier server node Import of the Oracle E-Business Suite Release 11i Oracle Discoverer content into the Oracle Discoverer 10.1.2 End User Layer

Supported Architectures Oracle Discoverer 10.1.2 must be installed in a separate ORACLE_HOME on an existing application tier server node or on a stand-alone server, accessing an Oracle E-Business Suite Release 11i database. 1) Check for OS Pr-requisite The following packages (or later versions) must be installed on your Linux x86 or Linux x86-64 system: binutils-2.16.91.0.5-23.4 gcc-4.1.0-28.4 gcc-c++-4.1.0-28.4 glibc-devel-2.4-31.2 libgcc-4.1.0-28.4 libstdc++-devel-4.1.0-28.4 libstdc++-4.1.0-28.4 make-3.80-202.2 compat-db 4.1.25-9
openmotif21-2.1.30-11.EL5.i386.rpm libXp xorg-x11-libs-compat-6.8.2-1.EL.33.0.1.i386.rpm # ln -s /usr/lib/libgdbm.so.2.0.0 /usr/lib/libdb.so.2

2)

Install Oracle BI tools 10g Release 2 (10.1.2.0.2)

2.1 Copy Database Connection file

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

Please copy the dbc file <two_task>.dbc from your 11i instance, and save the file on your Discoverer 10.1.2 $ORACLE_HOME/discoverer/secure directory as
<two_task>.dbc.

2.2 Update tnsnames.ora file

On your standalone Oracle Business Intelligence Server 10g Release 2 node, update file $ORACLE_HOME/network/admin/tnsnames.ora and include the tnsnames entry to connect to your Oracle E-Business Suite Release 11i database. Use the same entry as exists in the tnsnames.ora file on your Oracle E-Business Suite Release 11i 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 11i database using sqlplus.

3. Apply the latest certified Discoverer Plus and Viewer Patches Oracle Discoverer 10.1.2.3 ### Patch 5983622
4. Apply Discoverer 10g (10.1.2.3) Cumulative Patch 7111842

Stop opmnctl Services by

-bash-3.00$ cd $ORACLE_HOME/opmn/bin -bash-3.00$ ./opmnctl status -bash-3.00$ ./opmnctl stopall

-bash-3.00$ emctl stop iasconsole Apply Cumulative Patch on Discoverer Home (Detailed in Readme.txt) Check for opatch lsinventory to verify that patch has been applied -bash-3.00$ cd $ORACLE_HOME/opmn/bin -bash-3.00$ ./opmnctl startall -bash-3.00$ ./opmnctl status -bash-3.00$ emctl start iasconsole

5. Upgrade your existing Discoverer End User Layers to Discoverer 10.1.2.

$ORACLE_HOME/bin/eulapi -CONNECT <EUL User>/<Password>@<db> -AUTO_UPGRADE log (log file name>

OR Create new Discoverer 10.1.2 End User Layer Execute this step on your database tier with your environment pointing to your database ORACLE_HOME. Create a tablespace named 'DISCOVERER' with an initial size of 200 megabytes Create the new Discoverer 10.1.2 End User Layer by using the following command
$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@cus115 -USER EUL_US -PASSWORD EUL_US \ -DEFAULT_TABLESPACE discoverer -TEMPORARY_TABLESPACE temp \ -EUL_LANGUAGE US -APPS_GRANT_DETAILS apps/apps

The import and the refresh processes for the entire Applications 11i End User Layer - the complete set of .eex files - are large database transactions. Check that the default rollback segment

where the Discoverer End User Layer is to be installed is large enough to support rolling back a 70 MB transaction at minimum
SQL> select SEGMENT_NAME, TABLESPACE_NAME, BYTES, BLOCKS, EXTENTS \ from DBA_SEGMENTS where SEGMENT_TYPE = 'ROLLBACK';

6. Post-Installation Tasks 6.1 Apply necessary Oracle Applications interoperability patches using AutoPatch 1.1 1.2 1.3 Apply AD patches 5765314 and 6459796 Apply ICX patch 3133021 Apply AOL patch 6430269

6.2 Change the CONTEXT_FILE & run Autoconfig. s_disco_standalone --> true Description: Set the value of this variable to 'true' if E-business suite 11i is configured to use a standalone discoverer server s_disco_machine --> <machine.domain> for example: ap6162rt.us.oracle.com Description: Set the value of this variable to the machine configured to run Discoverer services s_disco_port --> <port number> for example: 7779 Description: Set the value of this variable to the base URL where Discoverer is available. Make sure the value of the port is set to Webcache SSL or Non-SSL port appropriately s_disco_protocol --> http | https Description: Set the value of this variable to the appropriate protocol used for accessing discoverer. Acceptable values for this parameter are http or https s_disco_ver_comma --> 10,1,2 Description: Disco Version s_disco_eul_prefix --> EUL Description: Discovery EUL prefix

6.3 Run AutoConfig to generate all configuration files for the APPL_TOP and the ORACLE_HOMEs in its supporting technology stack:
% <COMMON_TOP>/admin/scripts/<CONTEXT_NAME>/adautocfg.sh

6.4 Verify Applications profile options in Oracle Applications Log into Release 11i with the System Administrator responsibility Navigate to the Profile > System form Query the %Discoverer% profile options. Verify the following ICX profile options in Oracle Applications:
ICX_DISCOVERER_LAUNCHER --> http://<HTTP Server>:<Port>/discoverer/plus?Connect=[APPS_SECURE] Description: URL that points to Discoverer Server Launch page

ICX_DISCOVERER_VIEWER_LAUNCHER --> http://<HTTP Server>:<Port>/discoverer/viewer?Connect=[APPS_SECURE] Description: URL that points to Discoverer Viewer Servlet

ICX_DISCOVERER_RELEASE --> 10 Description: 1 digit number specifying the Discoverer release

ICX_DISCOVERER_USE_VIEWER --> Y | N Description: Specify whether Discoverer Viewer should be launched instead of Discoverer Plus (default).

ICX_DEFAULT_EUL --> EUL Description: ICX: Discoverer End User Layer Schema Prefix

ICX_DISCOVERER_EUL_LANGUAGE --> US Description: Since the End User Layer content is currently available in US

ICX_DISCOVERER_PARAMETERS --> exitURL=http://<HTTP Server>:<Port>/OA_HTML/OA.jsp?OAFunc=OAHOMEPAGE Description: This profile can be used to configure the Exit URL.

6.5 Regenerate your Business Views

Most of the Discoverer folders delivered as part of the Oracle E-Business Suite Release 11i Discoverer content are based on Business Views. Regenerate your Business Views by running the "Generate Business Views by Application" concurrent program using the Business View Setup responsibility: Logon to Oracle Applications as SYSADMIN Choose the "Business Views Setup" responsibility Navigate to Reports > Run > Pick Single Request > "Generate ALL Business Views" In case you dont have "Business Views Setup" responsibility assigned to SYSADMIN user, please do the following: Logon to Oracle Applications as SYSADMIN Choose the "System Administrator" responsibility Navigate to Security > User > Define and add responsibility "Business Views Setup" to user SYSADMIN. After regeneration of the Business Views has been completed, check the Business View Generator output file. It should not contain any errors. Recompile all objects in the APPS schema using adadmin. 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_objects where object_type = 'VIEW' and status = 'INVALID' and ( object_name like '%FV_%' or object_name like '%FG_%' or object_name like '%BV_%' or object_name like '%BG_%' );

If necessary, recompile those objects so that all views are valid.

6.6 Set up Applications User/Responsibility for EUL Administration: SYSADMIN/System Administrator The Release 11i System Administrator account must be granted permission to update and alter Discoverer 10.1.2 content. Grant End User Layer Administration Privileges

Execute below command on the standalone application server where Oracle Business Intelligence Server 10g Release 2 was installed
$ORACLE_HOME/bin/eulapi \ -CONNECT <EUL schema>/<password>@<db> \ -GRANT_PRIVILEGE \ -USER SYSADMIN \ -PRIVILEGE administration \ -PRIVILEGE all_admin_privs \ -LOG <log file name>

Make sure user SYSADMIN has full security access to all Business Areas Execute the following command on the standalone application server where Oracle Business Intelligence Server 10g Release 2 was installed
$ORACLE_HOME/bin/eulapi \ -CONNECT <EUL schema>/<password>@<db> \ -GRANT_PRIVILEGE \ -USER SYSADMIN \ -BUSINESS_AREA_ADMIN_ACCESS % \ -WILDCARD \ -LOG <log file name>

Document Referred: Using Discoverer 10.1.2 with Oracle E-Business Suite 11i [ID 313418.1]