Discoverer 10.1.2 For R12
Discoverer 10.1.2 For R12
Discoverer 10.1.2 For R12
Installation of 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 Discoverer 10.1.2 End User Layer (EUL) on a database tier server node Import of the Oracle E-Business Suite Release 12 Discoverer content into the Discoverer 10.1.2 End User Layer (Optional) Installation of Discoverer Administration Edition 10.1.2 on a Windows-based PC that can be used to customize Discoverer For current Discoverer users, it also describes how to upgrade an existing Discoverer End User Layer from Discoverer 3i, 4i or 9.0.4 to Discoverer 10.1.2. 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.
Section 1: Overview
Oracle Business Intelligence 10g Release 2, a key component of Oracle Application Server 10g Release 2, is an integrated business intelligence solution supporting intuitive ad hoc query, reporting, analysis, and web publishing. Business users at all levels of the organization can use Discoverer 10.1.2 to gain immediate access to information from data marts, data warehouses, and online transaction processing (OLTP) systems. Discoverer 10.1.2 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 10.1.2 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, Purchasing, Process Manufacturing, Activity Based Management, and more. This document describes how to install Discoverer 10.1.2 into an existing Oracle E-Business Suite Release 12 environment. Installation of Discoverer 10.1.2 into an Oracle E-Business Suite Release 12 environment consists of:
Page 1 of 36
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.
The following components must be used on the stand-alone instance: Component Name Oracle Application Server Oracle Business Intelligence Version 10.1.2.2.0 10.1.2.2.0
The following components must be used on the Oracle E-Business Suite Release 12 instance: Component Name Oracle E-Business Suite Release 12 Version 12.0
Step A.1 Install OracleAS If you are not planning to use Identity Management features Discoverer Infrastructure 10g (10.1.4.0.1) Connection Management, Discoverer Portlet Provider, Step A.2. Install Oracle and Oracle SSO, you can Application Server 10g choose to install Oracle Release 2 (10.1.2.0.2) type Business Intelligence Server
Page 4 of 36
Option A Business Intelligence and Forms You must install Oracle Application Server 10g Release 2 (10.1.2.0.2) installation type Business Intelligence and Forms in a separate ORACLE_HOME from the previously installed OracleAS Infrastructure. The Business Intelligence and Forms type installation is associated with an OracleAS Infrastructure during installation. The OracleAS Infrastructure might be on the same machine as the Business Intelligence and Forms type installation or on a different machine.
Option B 10g Release 2 (10.1.2.0.2). This installation type does not require installation and association to OracleAS Identity Management Infrastructure 10g (10.1.4.0.1). Oracle Business Intelligence Server 10g Release 2 (10.1.2.0.2) is available on a separate standalone CD and includes: Discoverer Server 10g Discoverer Plus 10g Discoverer Viewer 10g
2.1.2 Download the appropriate platform-specific one-off patch 6146747 for your Discoverer Server node from Oracle Support. Follow the installation instructions provided in the patch README to install the patch on your Discoverer Server.
It is possible to associate the Oracle Business Intelligence Server 10g installation to Infrastructure at a later point This installation type includes: in time, using Oracle Enterprise Manager. Please Discoverer Server 10g refer to section 2.2 How to Discoverer Plus 10g associate an OracleBI Discoverer Viewer 10g. installation with an OracleAS Infrastructure in the Discoverer Configuration Guide 10g Release 2.
2. Configure Oracle Discoverer 10g Release 2 (10.1.2.0.2) 2.1. Apply the latest certified Discoverer Plus and Viewer Patches
2.1.1 Apply OracleAS 10g Release 2 patchset 2(10.1.2.2.0) delivered via patch 4960210 available on OracleMetalink for download.
Note : For ALL Operating Systems Except Windows and Sparc Solaris
Before applying one-off patches, install the Patch 5861907 on top of Orace 10g Application Server Patch set 2 (10.1.2.2). Refer OracleMetalink Note: 413788.1, for more details.
Page 5 of 36
For more information about dbc files see Appendix 'Setting up and maintaining Oracle Applications' of the Oracle Applications System Administrators Guide.
Page 6 of 36
Option A
Option B
Applications Navigator and Applications Navigator and Applications Favorites portlets Applications Favorites portlets 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 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 3 If you select Option B, enable Single Sign-On on your Discoverer mode: 2.5.1. Verify you have associated your the Oracle Business Intelligence Server 10g installation to Oracle Application Server 10g Infrastructure. Refer to the steps mentioned under Section 5, 1. Install Oracle Application Server 10g Release 2 (10.1.2.0.2). 2.5.2. Open file $ORACLE_HOME/Apache/Apache/conf/mod_osso.conf in a text editor Add the following text to the end of the file:
<Location /discoverer/plus> require valid-user AuthType Basic </Location> <Location /discoverer/viewer> require valid-user AuthType Basic </Location> <Location /discoverer/app> require valid-user
Page 8 of 36
If you are using Discoverer Administration Edition 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 10.1.2 Administration Edition: 3.3.1 Back up your current Microsoft Windows Registry
Save the mod_osso.conf file. 2.5.3. Re-start Discoverer services using opmn. 2.5.4. Start Application Server Control, display the Administration page, select the Private Connections link, and select the 'Allow authenticated OracleAS 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 the <viewer> element of
$ORACLE_HOME/discoverer/config/configuration.xml.
For detailed information on Single Sign-On for the Discoverer node, refer to instructions in the Oracle Business Intelligence Discoverer Configuration Guide Release 10.1.2 (part number B13918-03): 14.7.1: Using Discoverer with OracleAS Single Sign-On 15.1 : About Discoverer private connections, OracleAS Single Sign-On and Oracle e-Business Suite users
3.3.2 Open the Windows Registry editor and create or update the following registry keys: Valu e
1
Registry Key
HKEY_CURRENT_USER\Software\Oracle\Discoverer 10\Database\EnableTriggers HKEY_CURRENT_USER\Software\Oracle\Discoverer 10\Database\DefaultPreserveDisplayPropertyForRe fresh
DataType
REG_DWOR D REG_DWOR D
3. Install Internet Developer Suite 10g (Optional) 3.1. Install Discoverer Administration Edition (Optional)
Install Internet Developer Suite 10g containing Discoverer 10.1.2 Administration Edition on a Windows PC if you wish to use Discoverer Administration Edition to customize your Discoverer End User Layer. Refer to Oracle Business Intelligence Discoverer Administration Guide 10g Release 2 (10.1.2).
Page 9 of 36
Database User contains functional End-User Layers for both Discoverer 4i and 10g. After verifying that the upgrade was successful, you may drop the 4i End-User Layer. If you are migrating your Discoverer 9.0.4 End User Layer, the upgrade process migrates the existing End User Layer to Discoverer 10.1.2. After successful migration you cannot connect to the Discoverer 10.1.2 End User Layer using Discoverer 9.0.4 Server.
You must migrate your End User Layer to 10.1.2 if either of the following are true: If ver_min_code_ver is lower than 10.1.2 If the table eul5_versions does not exist in your End User Layer, but the equivalent table eul4_versions does exist (this is a Discoverer 4i End User Layer) Migrate your existing Discoverer 4i or Discoverer 9.0.4 End User Layer to Discoverer 10.1.2 by using the following command on the standalone application server where Oracle Business Intelligence Server 10g Release 2 was installed in Step 1 . For UNIX:
If you are migrating your Discoverer 4i End User Layer, the upgrade process creates a new Discoverer 10.1.2 End User Layer based the existing Discoverer 4i End User Layer. The existing Discoverer 4i End User Layer remains unchanged. A new schema containing the Discoverer 10.1.2 End User Layer will be created under the same Database User. After migration, the
Page 11 of 36
Page 12 of 36
Virtual Machines. You must configure OracleBI Discoverer Plus to use the same Plug-in version as being used for E-Business Suite R12. Perform the steps in this section to configure OracleBI Discoverer Plus to use the Sun Java Plugin 1.5.0_10 by default.
7.1. Copy the Sun Java Plug-in 6.4. Create the Discoverer End-User Layer
Create the new Discoverer 10.1.2 End User Layer by using the following command syntax, executed on the standalone application server where Oracle Business Intelligence Server 10g Release 2 was installed in Step 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 Administration Edition command line on Windows. Use the following syntax to create the End-User Layer using Discoverer Administration Edition: %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 Copy the Sun Java Plug-in 1.5.0_10 executable from your E-Business Suite R12 instance at location:
http://machine.domain:port/OA_HTML/oaj2se.exe
and save the executable to your Oracle Business Intelligence 10g Release 2 filesystem as:
$ORACLE_HOME/jpi/bin/oaj2se.exe.
Find the plugin attribute within the <plus> element. This will show possible values "sun" or "jinitiator". Set the value to "sun":
<plus laf="plastic" lafJar="" lafClass="" logLevel="error" plugin="sun" helpSet="help">
Update the line as follows to specify usage of Sun Plugin Version 1.5.0_10:
<jvm name="sun" classid="clsid:CAFEEFAC-0015-0000-0010-ABCDEFFEDCBA" plugin_setup="http://mybi.company.com:7780/jpi/oaj2se.exe" version="1.5" versionie="1,5,0_10,mn"
Page 14 of 36
Page 13 of 36
Follow MetaLink Note 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.
2. Apply AD Patch 6459796 7.3. Save Your Changes and Restart Discoverer
This patch contains the latest version for adrfseul.sh. Save the updated configuration.xml file Restart the Discoverer services using opmn. Download the Patch 6459796 from Oracle Metalink. Follow the instructions in the README to apply the patch. 3. Set Applications Profile Options for Discoverer using AutoConfig Verify that Discoverer Plus is now using Sun Plugin 1.5.0_10 by navigating to the following URL:
http://mybi.company.com:7780/discoverer/plus
Proceed with the following steps to allow AutoConfig to switch profile options for your remote, standalone Oracle Business Intelligence 10g Release 2 server. Login to Oracle Applications Manager and navigate to Site Map > AutoConfig > Edit Parameters. Specify following variable: Variable Name
Title
Description
Value
For Discoverer Plus invocation from E-Business Suite Release 12 functions, you can specify the _jvm_name parameter with the profile option ICX: Discoverer Parameters at the Site/App/Resp/User level to selectively use the Sun Plug-in or JInitiator for given user groups. For more information, see MetaLink Note 393931.1 titled "Upgrading Sun J2SE (Native Plug-in) with Oracle Applications 12.0 for Windows Clients".
Discoverer s_disco_url Set the <protocol>:// URL value of this <machine.domain>:<port> variable to for example: http://mybi.company.com:7780 the base URL where Discoverer is available. 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
Ensure the following ICX profile options in Oracle Applications are set to: Profile ICX: Discoverer Launcher ICX: Discoverer Viewer Launcher ICX: Discoverer Release Description URL that points to Discoverer Plus Servlet. URL that points to Discoverer Viewer Servlet Single number specifying the Discoverer release Specify whether Discoverer Viewer should be launched instead of Discoverer Plus (default). Value
http://<HTTP Server>:<Port> /discoverer/plus ?Connect=[APPS_SECURE] http://<HTTP Server>:<Port> /discoverer/viewer ?Connect=[APPS_SECURE]
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
10
Yes | No
The EUL prefix in combination with ICX: the Language code Discoverer make up the EUL Default End owner at runtime. User Layer For example EUL Schema owner EUL_US Prefix has EUL prefix EUL. 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 Discoverer End User Layer using this profile option. The specified End
Page 17 of 36
profiles. The User Interface language will only change for valid combinations of ICX_LANGUAGE and ICX_TERRITORY. This profile can be used to optionally pass additional ICX: URL parameters to Discoverer Discoverer. Parameters Compare Note 186120.1 on Oracle MetaLink. 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
Page 18 of 36
EUL
<NULL>
American English
<NULL>
profile should remain NULL, in which case Discoverer will use the default dbc file for your E-Business Suite database.
You may switch the ICX_DEFAULT_EUL profile at the responsibility level if you are planning to implement multiple End User Layers. For example:
EUL_US for Business Intelligence System content EULEDW_US for Embedded Data Warehouse content
Then you can set ICX_DEFAULT_EUL to EULEDW for Embedded Data Warehouse responsibilities like "Financials Intelligence - Enterprise Data Warehouse". Those responsibilities will then use the Embedded Data Warehouse End User Layer.
Page 19 of 36
Page 20 of 36
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>"
Execute the following command on the standalone application server where Oracle Business Intelligence Server 10g Release 2 was installed in Step 1 . $ORACLE_HOME/bin/eulapi \ -CONNECT <EUL schema>/<password>@<db> \ -GRANT_PRIVILEGE \ -USER SYSADMIN \ -BUSINESS_AREA_ADMIN_ACCESS % \ -WILDCARD \ -LOG <log file 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 Administration Edition will drop End User Layer objects with dependencies on invalid Applications objects during the refresh process.
7. Access directory $AU_TOP/discover on your E-Business Suite Release 12 instance from your Oracle Business Intelligence 10g BI instance
Discoverer .eex files are patched to your application tier server node, directory $AU_TOP/discover . Those files must be accessible from the standalone application server where Oracle Business Intelligence Server 10g Release 2 was installed. Please mount your applications tier server node, directory $AU_TOP/discover on your standalone application server where Oracle Business Intelligence Server 10g Release 2 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 Server 10g Release 2 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. Linux users Only : Replace the line LD_ASSUME_KERNEL= 2.4.19 with following lines in $ORACLE_HOME/discoverer/discwb.sh before Import/Refreshing the EUL. KERNEL_VERSION=`/bin/uname -r | cut -d "-" -f1`
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.
Page 21 of 36
fi Note : Do not set LD_ASSUME_KERNEL for Operating Systems RHEL5,OEL5,SLES10. And for RHAS 2.1 set its value as 2.2.5
fndnam=<APPS FNDNAM> secgroup=<secgroup> topdir=<topdir> language=US eulprefix=<eulprefix> iashome=<iashome> [eultype=<eultype>] [mode=<mode>] [driver=<driver>] [filelist=<filelist>] [logfile=<logfile>] [parfile=<parfile>]
APPS responsibility security group Top level directory where Discoverer files are available Oracle Application Server 10g / Business Intelligence 10g Oracle Home directory.
eulprefix EUL schema prefix. For example, use eulprefix=EUL for schema EUL_US eultype OLTP - default, for standard Applications 12
Discoverer content
EDW - for Enterprise Data Warehouse Discoverer
content Use eultype=OLTP to import the Discoverer 10.1.2 content for Oracle E-Business Suite Release 12
mode COMPLETE - import all Discoverer content. DRIVER - default, import specific subset of files FILELIST - import specific subset of files
For the initial full import of the Discoverer 10.1.2 baseline files, use mode=complete. This mode will upload all .eex files (*o.eex) from the .../discover/ directory into the Discoverer End User Layer.
Page 24 of 36
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.
Notes: 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
This messages provides information that <file>.eex is an empty obsolete file and does not modify any data during import.
<topdir>\<language>\<file>.eex: The identifier for ... contains one or more of the characters ! ~ - * ( ) ' which will be de-supported for use in identifiers in future releases of Discoverer - see release notes for more details.
You can safely ignore this message using Discoverer 10.1.2. See release notes for more details. Refer to Section 10 for additional known import warnings captured in the log file during import of the full set of eex into an E-Business Suite R12 Vision Database.
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 \
Page 25 of 36
On Unix platforms you may run the refresh process on the standalone application server where Oracle Business Intelligence Server 10g Release 2 was installed. Alternatively on Windows platforms you may run the refresh process on the machine where Discoverer Administration Edition is installed.
twotask
Database name as specified in your tnsnames.ora file. Oracle Application Server 10g / Business Intelligence 10g Oracle Home directory. Log file where the adupdeul.sh script logs the result of the import process. Default filename is
adrfseul.log
iashome
logfile
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
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
Where: Parameter
eulschema
Page 27 of 36
Page 28 of 36
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.
Example 2: Grant security access for business area "General Ledger" to responsibility "Financials Intelligence"
$ORACLE_HOME/bin/eulapi -CONNECT <EUL schema>/<password>@<db> \ -GRANT_PRIVILEGE \ -ROLE "Financials Intelligence" \ -BUSINESS_AREA_ACCESS "General Ledger"
10.2. Grant Security and Privileges using Discoverer Administration Edition on Windows
If you have already granted security and privileges using the Discoverer 10.1.2 eulapi command-line utility, you may skip this step. Log in to the Discoverer Administration Edition 10.1.2 as the Applications User which was granted full Administration Privileges and Security:
<OracleHome>\bin\dis5adm.exe /CONNECT "SYSADMIN:System Administrator/<password>@<db>" /EUL <EULprefix>_<Lang>
Use the Help -> About Discoverer... dialog to make sure you are connected to the correct End User Layer (<EULprefix>_<Lang>; compare the import options used above). You can change the EUL in the dialog Tools ->
Options -> Default EUL.
Using Tools -> Privileges Check "User Edition" privileges for all Applications Users and Responsibilities who should be allowed to open workbooks. Using Tools -> Security Grant Business Area access to Applications Users and Responsibilities who should be allowed to query the various Business Areas.
Page 30 of 36
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 Represents command line text. Type this text exactly as text 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 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
Page 32 of 36
the content patch, you may need to refresh the Business Areas for the product affected by the additonal patch.
Start the import for just the eex files for the Discoverer patch. Syntax for the adupdeul script in driver mode: sh adupdeul.sh connect=sysadmin/sysadmin-password@db resp="System Administrator" gwyuid=APPLSYSPUB/PUB fndnam=APPS secgroup="Standard" topdir=D:/au_top/discover language=US eulprefix=EUL eultype=OLTP mode=driver driver=c1234567.drv
iashome=/oracle/iAS/bi
Start the full import of all .eex files in topdir/US, where topdir is specified as a parameter. For example:
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
logfile=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.
Start the import for just the eex files of a given patch 1234567 with parameter file oltpeul4.lst sh adupdeul.sh connect=sysadmin/sysadmin-password@db language=US mode=driver driver=c1234567.drv parfile=oltpeul.lst logfile=import_c1234567_eul_us_cust120.log
/SLOTS/slot06/appmgr/apps/apps_st/appl/au/12.0.0/discover/US/f iiarbilwbo.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/p oapoaprchsngbao.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/f iiarnrndrv01flo.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/p jipaprsntypeflo.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
1.3. Save the updated pref.txt file. 1.4. Run the script
<ORACLE_HOME>/discoverer/util/applypreferences.sh
Import of the full set of eex files into a E-Business Suite Release 12 Vision Database completes successfully with the following warnings written to the import log file. These warnings 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/i scwshshptlctflo.eex:Duplicate element definition: Date Hierarchy with identifier 'ISC_DEFAULT_DATE_HIERARCHY'
Page 35 of 36
Page 36 of 36