| Oracle® Fusion Applications Installation Guide 11g Release 1 (11.1.2) Part Number E16600-03 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Applications Installation Guide 11g Release 1 (11.1.2) Part Number E16600-03 |
|
|
PDF · Mobi · ePub |
This chapter describes how to install and configure a transaction database for use with an Oracle Fusion Applications environment. It also describes the Oracle Fusion Applications Repository Creation Utility, which creates a repository for applications schemas and tablespaces and loads seed data into the database.
This chapter includes the following sections:
Installing Oracle Database Enterprise Edition with the Wizard
Manually Installing Oracle Database Enterprise Edition or Oracle RAC
Running the Oracle Fusion Applications Repository Creation Utility
A transaction database holds the business transactions generated as you use your Oracle Fusion Applications products offerings. This chapter includes overview information related to installing Oracle Database (11.2.0.2).
You must install Oracle Database Enterprise Edition before you create a provisioning plan. The database must be created using the database template that is shipped with Oracle Fusion Applications software. The template contains the database structure and features, but is not seeded. It is generic for use across platforms.
For a small-scale, single-node database, you can use the Install an Applications Transaction Database option in the Provisioning Wizard to install a single-node instance of Oracle Database Enterprise Edition. Or, you can install the database manually (interactively) if you are creating a production-scale, multiple-node database. Oracle Fusion Applications also supports Oracle Real Application Clusters (Oracle RAC).
To finish any database installation, you must use the Oracle Fusion Applications Repository Creation Utility (Applications RCU) to perform the following actions:
Create Oracle Fusion Middleware schema and tablespace users and define the tables, views, and other artifacts that the schema user owns.
Create empty tablespaces for Oracle Fusion Applications components and the schema owners. The owners do not own any tables or data initially.
Import default seed data values for the schema users using Oracle Data Pump files.
See Section 3.6 for details about running the Applications RCU.
Oracle Data Pump provides high-speed, parallel, bulk data and metadata movement of Oracle Database contents. The Data Pump dump files (.dmp) that contain the table definitions are delivered as part of the provisioning framework installation to make them available to the Applications RCU.
When using Oracle Data Pump to import data and metadata for an Oracle RAC installation, note that the directory that holds the dump files must be accessible from all Oracle RAC nodes. In addition, keep the following considerations in mind:
To use Data Pump or external tables in an Oracle RAC configuration, you must ensure that the directory object path is on a cluster-wide file system.
The directory object must point to shared physical storage that is visible to, and accessible from, all instances where Data Pump and/or external tables processes may run.
The default Data Pump behavior is that worker processes can run on any instance in an Oracle RAC configuration. Therefore, workers on those Oracle RAC instances must have physical access to the location defined by the directory object, such as shared storage media.
Under certain circumstances, Data Pump uses parallel query slaves to load or unload data. In an Oracle RAC environment, Data Pump does not control where these slaves run, and they may run on other instances in the Oracle RAC, regardless of what is specified for CLUSTER and SERVICE_NAME for the Data Pump job. Controls for parallel query operations are independent of Data Pump. When parallel query slaves run on other instances as part of a Data Pump job, they also require access to the physical storage of the dump file set.
A single-node instance of Oracle Database Enterprise Edition is typically used for medium-sized installations, or for training and demonstrations. The Provisioning Wizard database installation interview collects details such as the database listener port and the location of the database home, the database software, the database files, the database password, and the global name of the database. The wizard performs prerequisite validation checks, reports the status of the checks, and summarizes the actions to be performed during the database installation.
The wizard invokes the database build script and performs the following tasks:
Installs database software.
Generates an Oracle Universal Installer (OUI) response file based on the configuration that you specify.
Accesses the provisioning repository and invokes the database installer in silent mode. If the applications environment does not meet the database installation requirements, the wizard terminates the process.
Requests a copy of the nonseeded database template.
Creates an instance of Oracle Database 11.2.0.2 using the configuration settings that you entered in the wizard interview, and the database template.
The wizard performs the database installation in phases and reports progress during the installation:
Installation: Runs the database installer to install only the software.
Preconfigure: Applies patches to the installed database. The patches are located in the repository_location/installers/database/patch directory.
Configure: Creates services used to connect to the database and applies the database template to set system parameters.
Postconfigure: Performs any necessary postconfiguration steps.
Startup: Starts any installed components that are not already started.
Validation: Connects to the database to verify the integrity of the installation.
Oracle Real Application Clusters (Oracle RAC) enables multiple database instances, linked by an interconnect, to share access to Oracle Database. This configuration enables you to increase the scale of your applications environment. This type of database is typically used for production environments.
For information about Oracle RAC, see "Oracle RAC Database Configuration for Oracle Fusion Applications Repositories" in Oracle Fusion Applications Administrator's Guide.
You must read and understand the information in the following sources and perform any tasks outlined there before you begin a database installation:
The expectation is that the installation is performed by the database administrator (DBA) on the database host, and that these requirements are met:
The person who installs the database must have root or sudo user privileges. However, Oracle Database should not be installed as root user.
The Oracle Fusion Applications software packages must have been installed. Provisioning relies on the database installer to determine whether the system is adequate for the base database software.
Note:
It is a good practice to install only one database server on a given host. Each server can manage multiple database instances.Oracle Database installations must meet specifications for Oracle Fusion Applications system requirements and supported platforms documentation. The Provisioning Wizard performs prerequisite validation checks to ensure that those requirements are met.
Oracle Fusion Applications requires Oracle Database Enterprise Edition or Oracle Real Application Clusters Database. If you are installing Oracle Database Enterprise Edition installer manually (not using the provisioning Wizard), the installation requires the enabling of specific components, several of which are selected by default:
Oracle Partitioning (default)
Oracle OLAP (default)
Oracle Label Security (select for runtime requirements)
Oracle Data Mining RDBMS Files (default)
Oracle Real Application Testing (default)
To verify that your system meets all minimum requirements associated with the database, see Oracle Database Installation Guide for your platform for details.
Table 3-1 shows the commonly recommended initialization parameters.
Table 3-1 Recommended Initialization Parameters
| Expected Database Size | Parameter Name | DB Default Value | Recommended Value |
|---|---|---|---|
|
Small and large |
|
DB |
NONE |
|
plsql_code_type |
INTERPRETED |
NATIVE |
|
|
nls_sort |
Derived from NLS_LANGUAGE |
BINARY |
|
|
|
50 |
500 |
|
|
|
50 |
500 |
|
|
|
TRUE |
FALSE |
|
|
Starter |
|
0 |
9 GB |
|
|
0 |
4 GB |
|
|
_fix_control |
0 |
6708183:ON |
|
|
processes |
100 |
5000 |
|
|
undo tablespace |
0 |
12 GB |
|
|
temp tablespace |
0 |
9 GB |
|
|
redo log |
0 |
3 2 GB Groups |
|
|
Single-node, large |
|
0 |
18 GB |
|
|
0 |
8 GB |
|
|
_fix_control |
0 |
6708183:ON |
|
|
processes |
100 |
5000 |
|
|
undo tablespace |
0 |
12 GB |
|
|
temp tablespace |
0 |
9 GB |
|
|
redo log |
0 |
3 2 GB Groups |
|
|
2-node Oracle RAC |
|
0 |
18 GB |
|
|
0 |
8 GB |
|
|
_fix_control |
0 |
6708183:ON |
|
|
processes |
100 |
5000 |
|
|
undo tablespace |
0 |
12 GB |
|
|
temp tablespace |
0 |
9 GB |
|
|
redo log |
0 |
3 2 GB Groups |
As a part of the provisioning process, the Provisioning Wizard performs prerequisite and validation checks. These validations must pass before you create a provisioning plan.
User Input Validations
The Provisioning Wizard:
Validates the service name or global database name.
Validates the installer location. In the preverify phase, validates that the database is present.
Validates that the database password value and the password confirmation match.
Performs specific user ID and password validations for all Oracle Fusion Middleware schema owners.
Preinstallation Validations
The Provisioning Wizard:
Checks to see if the specified database file location has sufficient disk space for the initial database provisioning and performs an Oracle home space check.
Performs a port availability check.
Performs a platform check. There is no validation that specific platform packages have been installed.
Postinstallation Validations
The Provisioning Wizard ensures that a JDBC connection can be established.
You can install a single-node instance of Oracle Database Enterprise Edition using the Provisioning Wizard. The wizard uses the database template delivered with your software. The database is initially empty. After the installation is complete, you must run the Applications RCU to create schemas and tablespaces.
To start the Provisioning Wizard, do the following:
Set the JAVA_HOME environment variable to point to the JDK location in the provisioning repository, for example:
(UNIX)
export JAVA_HOME=repository_location/jdk6
export PATH=$JAVA_HOME/bin:$PATH
(Windows)
set JAVA_HOME=repository_location\jdk6
set PATH=%JAVA_HOME%\bin;%PATH%
Run the following command on the primordial host:
(UNIX)
cd framework_location/provisioning/bin
./provisioningWizard.sh
(Windows)
framework_location\provisioning\bin
provisioningWizard.bat
Table 3-2 shows the steps necessary to install a transaction database. For help with any of the interview screens, see Appendix B or click Help on any interview screen.
Table 3-2 Interview Flow for Database Installation
| Screen | Description and Action Required |
|---|---|
|
Welcome |
No action is required on this read-only screen. Click Next to continue. |
|
Installation Options |
Presents the list of valid installation actions that you can perform using the wizard. Select Install an Applications Transaction Database. Click Next to continue. |
|
Specify Security Updates |
Set up a notification preference for security-related updates and installation-related information from My Oracle Support.
Click Next to continue. |
|
Database Install Configuration |
Specify the configuration details for the database that you want to install. See Section 3.4.3 for details. Click Next to continue. |
|
Prerequisite Checks |
The Prerequisite Checks list shows each prerequisite check performed, and its status:
Click an x or a Restricted symbol to display information about failures. Click the Log file for details about the validation. Fix any issues reported. Click Retry to run the prerequisite checks again. If recovery is necessary, see Section 3.10 for details. When prerequisite checking has finished with no errors, click Next to continue. |
|
Summary |
Click Save to create and save a text file to use as a record of this configuration. Click Install to start the installation. Note: Record the name and location of the file. You must supply these details when you create a provisioning plan. |
|
Database Installation Progress |
The progress of the installation phases is listed. See Section 3.1.3.2 for a description of the phases. A message appears after the installation phase is complete directing you to run The central log file location is displayed below the Progress bar. Click a Log icon to view phase log files. Click Retry if a failure occurs. If recovery is necessary, see Section 3.10 for details. Click Next to continue. |
|
Installation Complete |
Summarizes the actions and validations that were performed for this installation. Click Save to record the database summary information in a text file. Note: Be sure make a note of the name and location of this file. You must supply these details when you create a provisioning plan. Your system administrator may also need this information as they perform maintenance tasks. Click Close to dismiss the screen and exit the wizard. |
On the Database Install Configuration interview screen, specify values for these database configuration parameters.
Database Listener Port: The port number designated for the database server. The default port for Oracle Database is 1521.
Installers Directory Location: Enter the path to the repository_location directory you created when you downloaded the provisioning repository. For Windows, the location must be a symbolically linked directory. See Section 2.2.5 for additional details. Note that the symbolic link is not necessary if the repository and the database are on the same node.
Oracle Base: Enter the top-level directory for Oracle software installations. You can change the path based on your requirements.
Software Location: Accept the default value or enter the Oracle home directory path that points to where you want the data files to reside. The directory path must not contain spaces.
Database File Location: Accept the default value or enter the path to the .dbf, .dtl, and .log files.
OSDBA Group: The UNIX operating system group that the database administrator is a member of. Displayed only if the platform detected by the installer is UNIX.
Global Database Name: Enter a name to distinguish this database instance from other Oracle Database instances running on the same host. The name can be written as database name or database name.domain name. This is the database service name.
Administrative Password: Specify a valid password. Retype the password to Confirm.
Though Oracle Fusion Applications Provisioning automates the installation and configuration of a transaction database for use with Oracle Fusion Applications environments, you can manually install a single-node instance of Oracle Database or Oracle Real Application Clusters to meet your specific requirements.
To manually install and configure a transaction database, you must:
Install Oracle Database or Oracle RAC.
Apply database patches.
If installing an instance of Oracle Database, configure the database listener.
Create transaction database instances using Oracle Database Configuration Assistant (DBCA).
Start the database.
Complete any postinstallation tasks that are required by the database patches, as described in the readme files.
The first step in creating a custom transaction database instance is to install the database software.
If you are installing Oracle Database manually (interactively) instead of using the Provisioning Wizard, see Oracle Database Installation Guide for your platform for instructions.
When performing the installation, ensure that the following components are enabled:
Oracle Partitioning (default)
Oracle OLAP (default)
Oracle Label Security (select for runtime requirements)
Oracle Data Mining RDBMS Files (default)
Oracle Real Application Testing (default)
If these components are not enabled, application functionality will not work.
When performing the installation, choose the Software Only option. You will manually create the database instance and configure the database.
For complete information about installing and configuring Oracle RAC, see Oracle Database Installation Guide for your platform for instructions. This library contains installation guides for Oracle RAC, as well as Oracle Database installations for all platforms.
An installation of Oracle Fusion Applications requires several database patches. When you install a database manually, you must apply these patches to your database before you run the Oracle Fusion Applications Repository Creation Utility. With Oracle Database, you must also apply the patches before you configure the database listener.
You use OPatch to apply patches to Oracle Database. For information about OPatch, see the Oracle Universal Installer and OPatch User's Guide.
Navigate to the database ORACLE_HOME/OPatch directory.
Invoke the OPatch command using the following parameters:
./opatch napply repository_location/installers/database/patch -skip_duplicate -skip_subset
The repository_location is the path to the directory that was created when you unzipped the product media pack.
For information about applying patches to an Oracle RAC database instance, see the Oracle Database 2 Day + Real Application Clusters Guide 11g Release 2.
If you are using Oracle Database, you must configure the database listener as described in the Oracle 11g Release 2 Documentation Library. After you complete the configuration, start the database listener.
You can use the Oracle Database Configuration Assistant (DBCA) to create the transaction database from the database template that is shipped with Oracle Fusion Applications software. This template contains the database structure and features, but is not seeded. It is generic for use across platforms.
Instructions on database installation and configuration can be found in the Oracle 11g Release 2 Documentation Library.
If you choose to not use the database template, you must ensure that your database configuration parameters are aligned with the values specified in Section 3.3.2.
You use DBCA to manually create an instance of Oracle Database from the nonseeded database template that is shipped with Oracle Fusion Applications software.
To create a single-node Oracle Database instance:
Edit the nonseeded database template at PROV_FRMWK_HOME/provisioning/provisioning/template/dbca/empty_database_11.2.dbt and set the process initialization parameter to 3000 as shown in the following text:
<initParam name="processes" value="5000"/>
Navigate to the database ORACLE_HOME/bin directory and execute the following command:
dbca -silent -createDatabase \ -templateName PROV_FRMWK_HOME/provisioning/provisioning/template/dbca/empty_database_11.2.large.dbt \ -gdbName "ORACLE_SID" \ -sid "ORACLE_SID" \ -sysPassword "SYS_PASSWORD" \ -systemPassword "SYSTEM_PASSWORD" \ -emConfiguration "NONE" \ -characterSet "AL32UTF8" - \ -nationalCharacterSet "AL16UTF16" \ -variables ORACLE_BASE=ORACLE_BASE, ORACLE_HOME=ORACLE_HOME \ -initParams audit_trail=NONE \ -datafileDestination DATAFILE_LOC
Replace the following variables with the appropriate values:
PROV_FRMWK_HOME: Home of Fusion Applications Provisioning framework.
ORACLE_SID: Global database name of the Oracle Fusion Applications database.
SYS_PASSWORD: Password for the SYS user. The SYS schema is the location of base tables and views.
SYSTEM_PASSWORD: User SYSTEM password. The user can create additional tables and views.
ORACLE_BASE: Top-level directory for the database installation.
ORACLE_HOME: Oracle home of the database installation.
DATAFILE_LOC: Physical location of the files that store the data of all logical structures in the database.
You use DBCA to manually create a database instance for each Oracle RAC node using the nonseeded database template that is shipped with Oracle Fusion Applications software.
To create an Oracle RAC database instance:
Edit the nonseeded database template at PROV_FRMWK_HOME/provisioning/provisioning/template/dbca/empty_database_11.2.dbt and set the process initialization parameter to 3000 as shown in the following text:
<initParam name="processes" value="3000"/>
For each RAC node, navigate to the database ORACLE_HOME/bin directory of the RAC node and execute the following command:
dbca -silent -createDatabase \ -templateName PROV_FRMWK_HOME/provisioning/provisioning/template/dbca/empty_database_11.2.dbt \ -gdbName "ORACLE_SID" \ -sid "ORACLE_SID" \ -sysPassword "SYS_PASSWORD" \ -systemPassword "SYSTEM_PASSWORD" \ -emConfiguration "NONE" \ -characterSet "AL32UTF8" - \ -nationalCharacterSet "AL16UTF16" \ -variables ORACLE_BASE=ORACLE_BASE, ORACLE_HOME=ORACLE_HOME \ -initParams audit_trail=NONE \ -datafileDestination DATAFILE_LOC \ -nodeinfo node1,node2
Replace the following variables with the appropriate values:
PROV_FRMWK_HOME: Home of Fusion Applications Provisioning framework.
ORACLE_SID: Global database name of the Oracle Fusion Applications database.
SYS_PASSWORD: Password for the SYS user. The SYS schema is the location of base tables and views.
SYSTEM_PASSWORD: User SYSTEM password. The user can create additional tables and views.
ORACLE_BASE: Top-level directory for the database installation.
ORACLE_HOME: Oracle home of the database installation.
DATAFILE_LOC: Physical location of the files that store the data of all logical structures in the database.
Refer to the Oracle 11g Release 2 Documentation Library for instructions on how to start the database.
After you have applied patches and started the database, check the patch readme files to determine whether you need to perform postinstallation tasks. Go to the repository_location/installers/database/patch directory to find the readme files. Any manual steps associated with the patches are typically located in a section called "Post-Install Instructions" or "Postinstallation."
You can aggregate all the readme files by running this script:
cat 'find repository_location/installers/database/patch/ -name "README.txt"' >> repository_location/PATCHES_README_ALL.txt
Use a text editor of your choice to view PATCHES_README_ALL.txt.
The Oracle Fusion Applications Repository Creation Utility (Applications RCU) is a self-sufficient tool that runs from a graphical interface or from the command line. It creates applications-specific schemas and tablespaces for Oracle Database Enterprise Edition or Oracle Real Application Clusters.
The Applications RCU components are included in the zipped Applications RCU file delivered in the provisioning framework. The Applications RCU offers these features:
Integrates Oracle Fusion Middleware and Oracle Fusion Applications schema and storage definitions using declarative XML.
Runs locally or remotely as a standalone tool.
Lets you modify or use custom tablespaces for the default Oracle Fusion Applications schemas.
Performs checks against both global and component-level prerequisites at runtime. If a prerequisite is not met, the Applications RCU may issue a warning and allow the procedure to continue (soft stop), or it may notify you that a prerequisite must be met (hard stop).
The Oracle Fusion Applications Repository Creation Utilities ships with predefined schemas, tablespaces, index tablespaces, temporary tablespaces, and a recommended configuration. It is built with a standard Bali JEWT-based graphical interface, compiled using existing Oracle installers. It is supported on Linux x86-64 and Microsoft Windows x64 (64-Bit) platforms.
The Applications RCU is designed to:
Be completely self-contained. It has all the technical components necessary to perform the operations required (Oracle Client, binaries, scripts, data, and PL/SQL packages).
Support Oracle Database 11.2.0.2 and database configurations such as ASM and Oracle RAC.
Perform a silent execution.
Operate on remote databases.
Connect to an existing database, read existing tablespace definitions, and create schema owners and new tablespaces.
Some limitations of the Applications RCU are as follows:
The database that you run it on must be empty. If applications-related schemas already exist, the option to modify them is grayed out.
The Applications RCU does not provision delta schemas and does not perform database upgrades.
The Applications RCU supports the import of full schemas only.
The Applications RCU does not support the dropping of a component schema. You can, however, drop the entire instance directly through the database, if required.
You use the Oracle Fusion Applications Repository Creation utility to create a repository of applications-specific schemas and tablespaces for Oracle Database.
Internally, the Applications RCU performs actions related to Oracle Fusion Middleware components and Oracle Fusion Applications components. In addition, the utility takes appropriate action to see that the tables are enabled to store repository resources.
Oracle Fusion Middleware Components
The Applications RCU loops through all the middleware components in the component definition file and applies the relevant ones to the database. For each component, the Applications RCU creates the appropriate middleware tablespace and schema user. After creating the schema user, it defines the tables, views, and other artifacts that the schema owner owns.
Oracle Fusion Applications Component
The Applications RCU creates empty tablespaces for the Oracle Fusion Applications components. It then creates the schema owners (for example, FUSION and FUSION RUNTIME). These schema owners are initially empty — they do not own any tables or data.
The Applications RCU employs Oracle Data Pump to import the seed data and the dump files containing tables, views, and other artifact definitions that belong to the schema users it has created. All dump files are packaged with the Applications RCU.
XML Schema Registration
When tables are created as part of an XML schema registration, by default the tables are enabled for hierarchy; that is, repository resources can be stored in the tables. A number of triggers are created for this purpose. If resources are created, updated, or deleted based on the registered XML schema, the corresponding XMLtype rows in the tables are inserted, updated, or deleted.
Tables are disabled for the hierarchy before they are exported in dumpfile mode because some of the special features that make these tables store resources may not be meaningful in the target database. Disabling the hierarchy drops some triggers so that they do not show up in the target database after import of the dump files.
Table 3-3 lists all schema owners for Oracle Fusion Middleware and Oracle Fusion Applications.
Table 3-3 Fusion Middleware and Fusion Applications Schema Owners
| Component | Schema Owners |
|---|---|
|
Fusion Applications |
FUSION_DYNAMIC FUSION_RUNTIME FUSION_APM FUSION_AQ FUSION_BI FUSION_DQ FUSION_ODI_STAGE |
|
AS Common Schemas
|
Include:
|
|
Secure Enterprise Search |
SEARCHSYS |
|
Master and Work Repository |
FUSION_ODI |
|
Enterprise Content Management
|
Includes:
|
|
Oracle Business Intelligence (Platform) |
FUSION_BIPLATFORM |
|
Oracle BI Applications Schemas
|
Include:
|
|
WebLogic Server Communication Services
|
Include:
|
|
SOA and BPM Infrastructure
|
Include:
|
|
WebCenter Suite
|
Includes:
|
Use the information in this section to prepare to run the Applications RCU and complete the wizard screens necessary to create schemas and tablespaces.
In order for Applications RCU to work properly, you must locate three files and place their contents in specific locations:
rcuHome_fusionapps_dbinstall.zip – contains the Applications RCU components needed to run the utility.
export_fusionapps_dbinstall.zip – contains the applications data files that the Applications RCU supplies to the database.
otbi.dmp – contains the Business Intelligence (BI) data that the Applications RCU supplies to the database.
To prepare these files, complete these steps:
If you installed the database manually, apply all the patches located in the repository_location/installers/database/patch directory. See Oracle Universal Installer and OPatch User's Guide for instructions for applying patches to your database.
If you installed the database using the Provisioning Wizard, the database patches were applied during the installation. No further action is required.
Ensure that you have enough disk space to complete the tablespace creation. See the Oracle Database Installation Guide for your platform for details.
Decide on three locations and create directories on the database server for storing Oracle Enterprise Scheduler Service (ESS) log files, Oracle Fusion Applications PL/SLQ log files, and OBIEE dump files. Make a note of these directories. You will need to enter the locations when you specify the values for APPLCP_FILE_DIR, APPLLOG_DIR, and the OBIEE Backup Directory in Section 3.8.5, "Managing Custom Variables."
Go to repository_location/installers/apps_rcu and locate the rcuHome_fusionapps_dbinstall.zip file. This file was staged when you created the installer repository.
Extract the contents of rcuHome_fusionapps_dbinstall.zip to a directory (APPS_RCU_HOME) on the database server. All dependent components that Applications RCU needs are included in this zipped file.
Create a temporary directory on the database server. Make a note of the location. You will need to enter this location when you specify a value for FUSIONAPPS_DBINSTALL_DP_DIR in Section 3.8.5, "Managing Custom Variables."
Locate and copy APPS_RCU_HOME/rcu/integration/fusionapps/export_fusionapps_dbinstall.zip to the directory you specified for FUSIONAPPS_DBINSTALL_DP_DIR.
Unzip export_fusionapps_dbinstall.zip to FUSIONAPPS_DBINSTALL_DP_DIR.
Go to APPS_RCU_HOME/rcu/integration/biapps/schema and locate the otbi.dmp file.
Copy otbi.dmp to FUSIONAPPS_DBINSTALL_DP_DIR (where you unzipped the contents of export_fusionapps_dbinstall.zip).
Once you have completed the steps in the Getting Ready section, run Applications RCU from (UNIX) APPS_RCU_HOME/bin or (Windows) APPS_RCU_HOME\bin with the following command:
(UNIX) ./rcu
(Windows) rcu.bat
Note:
The Applications RCU is available only on Linux and Windows platforms. On Windows systems, do not extract the rcu.zip file to a directory whose name contains spaces.Table 3-4 lists the steps for running the Applications RCU. For help with any of the screens, see Appendix C or click Help on any screen.
Table 3-4 Running the Oracle Fusion Applications Repository Creation Utility
| Screen | Description and Action Required |
|---|---|
|
Welcome |
No action is necessary on this read-only screen. Click Skip this Page Next Time if you do not want to see it the next time you log in to the Applications RCU. Click Next to continue. |
|
Create Repository |
Select Create to create and load component schemas into the database. See Section 3.7.2 for a list of schemas. Click Next to continue. |
|
Database Connection Details |
Specify the database connection details. See Section 3.8.4 for specifics. Click Next to continue. |
|
Select Components |
The Applications RCU retrieves the names of the Oracle Fusion Middleware and the Oracle Fusion Applications components. You cannot change the schema owner names. By default, all components are checked so that they are included in the prerequisite check process. Click Next to begin the process. When the progress bar reports 100 percent complete and all prerequisites report a check mark, click OK. Click Next to continue. |
|
Schema Passwords |
Specify the passwords for main and additional (auxiliary) schemas:
Note the passwords you enter. You must supply them when you create a provisioning plan. Click Next to continue. |
|
Custom Variables |
Each Oracle Database directory object has a value represented by a physical directory on the database server. Custom variables are pre-defined, platform-specific directory objects that the Applications RCU creates. In the Value column, you specify a pre-existing physical directory (located on the database server) for each custom variable. See Section 3.8.5 for a list of variables. Click Next to continue. |
|
Map Tablespaces |
If you want to start the tablespace create process without making any changes, click Next on this screen. A message informs you that any tablespaces that do not already exist will be created. Click OK to continue. The Creating Tablespaces progress screen appears. Click OK when the operation is completed. Or, view default tablespace mappings, change default and temporary tablespaces, view and change additional tablespaces, and manage tablespaces and datafiles (add, modify, or remove) before they are created. See Section 3.8.6. If you make changes, click Next when you are finished, then click OK to create the tablespaces. Click OK when the operation is complete. |
|
Summary |
Review the information and click Create. While the schemas are being created, the utility displays the Repository Creation Utility – Create screen, showing the creation progress. Typically, it takes 1 to 10 minutes to create each schema; however, the process may run for an additional half hour or more. To stop creating the schemas, click Stop. |
|
Completion Summary |
The Logfile column lists log file names. For more information, see Section 3.10.3. If errors are encountered during the Create operation, or if a Create operation fails for any component, the Cleanup for failed components check box appears on this page and is selected by default. If the check box is selected, the Applications RCU will perform cleanup operations for the components that failed. Click Close to dismiss the screen. |
Specify information about the hosts and ports that you want to use for your database.
Database Type: Select the database type.
Host Name: Enter the name of the server where the database is running, for example, myhost.mydomain.com. For Oracle RAC, specify the VIP name or one of the node names.
Port: The database port number. The default port number is 1521.
Service Name: This is the global database name. If you do not know it, see the SERVICE_NAMES parameter in the database initialization file. If it is not there, use the global name in DB_NAME and DB_DOMAIN. For Oracle RAC, specify the service name of one of the nodes, for example, examplehost.exampledomain.com.
User Name: Supply the name of the user with DBA or SYSDBA privileges. The default user name with SYSDBA privileges is SYS.
Password: Enter the password you set up for the database user.
Role: Select Normal or SYSDBA. All schemas installed for Oracle Database require the SYSDBA role. For Oracle Internet Directory (OID) database schemas, use SYS and SYSDBA.
Enter a pre-existing physical directory on the database server where the custom variables for each component should be created.
FUSIONAPPS_DBINSTALL_DP_DIR: The location on the database server where you unzipped export_fusionapps_dbinstall.zip and copied the otbi.dmp file.
APPLCP_FILE_DIR: Used by Oracle Enterprise Scheduler to store the log and output files. Must be valid on the database server with read-write permissions to the database owner. For Oracle RAC, must point to a location that is shared across all nodes.
APPLLOG_DIR: Location of the PL/SQL log files from Oracle Fusion Applications PL/SQL procedures on the database server. Ensure that the database owner has read-write privileges.
KEYFLEXCOMBFILTER: Location of the Filter XMLSchema. This variable is used for reloading components after patching. You can upload the variable to register it to the database. Note: You must specify a value, however, this functionality is obsolete in this release of Oracle Fusion Applications.
OBIEE Backup Directory: Location of the Oracle Business Intelligence Enterprise Edition dump files. These files are used for enabling a restart action.
Secure Enterprise Search
Do you have Advanced Compression Option (ACO) License? Yes (Y) or No (N): Default is No.
Do you have Oracle Partitioning option License? Yes (Y) or No (N): Default is No.
Master and Work Repository
Note: The default values are the ONLY valid values. If you change any of these values, the ODI-related provisioning process will not work.
Master Repository ID: Default = 501
Supervisor Password: Default = None. You must enter the same password you set up as ODI SUPERVISOR in Applications RCU.
Work Repository Type: (D) Development or (R). Default = D
Work Repository ID: Default = 501
Work Repository Name: Default = FUSIONAPPS_WREP
Work Repository Password: Default = None. You must enter the same password you set up as ODI SUPERVISOR in Applications RCU.
Oracle Transactional BI
Directory on the database server where Oracle Transactional Business Intelligence import and export files are stored.
Activity Graph and Analytics
Install Analytics with Partitioning (Y/N): Default is N.
You can perform several operations from the Map Tablespaces screen including view, add, modify, or remove tablespaces. These actions are also available for additional tablespaces or datafiles.
In the Default Tablespace and Temp tablespace columns, click a cell to select from a list of available additional tablespace names. The default tablespaces are as follows:
FUSION_TEMP: For temporary tables.
FUSION_DYN_TS: For dynamically generated PL/SQL statements.
FUSION_IAS_ORASDPM_AQ: For advanced queuing JMS data and indexes.
FUSION_TS_AQ: For advanced queuing JMS data and indexes.
FUSION_TS_DQ: For data quality data and indexes.
FUSION_TS_TOOLS: Associated with Oracle Fusion Middleware data and indexes.
FUSION_TS_QUEUES: For advanced queuing and dependent tables and indexes.
FUSION_TX_TX_DATA: For transactional data.
FUSION_TS_TX_IDX: Indexes for transactional data.
FUSION_TS_SEED: For seed or reference data and indexes.
FUSION_TS_INTERFACE: For temporary or interface data and indexes.
FUSION_TS_SUMMARY: For summary management objects.
FUSION_TS_NOLOGGING: For materialized views and other temporary or scratch pad objects.
FUSION_TS_ARCHIVE: For tables and objects that are no longer used.
FUSION_TS_MEDIA: Contains multimedia objects such as text, video, and graphics.
For tablespaces that need to be created, the datafile defaults to %DATAFILE_LOCATION%\%sid%\%tablespace_name%.dbf. You can select from existing tablespaces if they are already defined in the database.
The default out-of-the-box Oracle Fusion Applications tablespace sizes are not optimal, and larger than is necessary, so that they may take up more disk space than is necessary. You can update the sizes of the tablespace (datafiles) on the Manage Tablespaces screen, accessed from the Map Tablespaces screen in the Applications RCU interface.
Table 3-5 lists the sizes of the optimal and out-of-the-box (OOTB) tablespaces. You must make changes during the running of Oracle Fusion Applications Repository Utility Creation.
Table 3-5 Tablespace Optimal and OOTB Sizes
| Tablespace Name | Optimal Size (MB) | Out-of-the-Box Size (MB) |
|---|---|---|
|
|
20 |
500 |
|
|
20 |
500 |
|
|
6144 |
1024 |
|
|
200 |
500 |
|
|
20 |
1024 |
|
|
20 |
2048 |
|
|
750 |
300 |
|
|
20 |
500 |
|
|
20 |
200 |
|
|
20 |
500 |
|
|
3200 |
2048 |
|
|
20 |
1024 |
|
|
7700 |
1024 |
|
|
4450 |
20480 |
|
|
3400 |
6144 |
To change the default tablespace name for a component, select the name in the Default Tablespace column, and then select the name that you want to use from the list. You can have your components use any number of tablespaces to suit your configuration.
Follow the same procedure to change a temporary tablespace for a component by selecting a tablespace name from the Temp Tablespace list.
Some components have additional tablespaces associated with their schemas. If so, the Additional Tablespaces button is active. Click it to view or modify additional tablespaces. Click the Tablespace Name column to select a tablespace.
Click OK when you are finished.
Click Manage Tablespaces to add, modify, or remove tablespaces. Only tablespaces that have not yet been created can be modified or removed. Existing tablespaces are visible, but cannot be modified or removed.
Only tablespaces used by a component are created. You can specify a new tablespace, but unless it is used by a component, it will not be created.
To edit a tablespace, select it from the navigation tree. Complete the following:
Name: Specify a new name for the tablespace.
Type: Indicate whether this tablespace is temporary or permanent.
Block Size: The block size (in kilobytes) to be used for data retrieval.
Storage Type: Select Use Bigfile Tablespace if you have single large files. Select Use Automatic Segment Space Management to use bitmaps to manage free space within segments.
To Add a tablespace, specify the same details as for modifying one. Select a tablespace from the navigation tree and click Remove to prevent it from being created.
Manage Datafiles
Click the Plus (+) icon and complete the Add Datafile details:
File Name: The name of the datafile.
File Directory: The location where the datafile will reside.
Size: The initial size of the datafile.
Automatically extend datafile when full (AUTOEXTEND): Select this option to extend the datafile size automatically when it becomes full. In the Increment field, select the size by which the datafile should be increased.
To limit maximum size, specify a value in the Maximum Size field.
Select a datafile and click the pencil icon. Modify the information on the Edit Datafile screen. Select a datafile and click the X icon to delete the file.
Edit the Size of a Datafile
To change the size of a tablespace:
Click a tablespace name to select it.
Click the pencil icon to bring up the Edit Datafile screen.
In the Size field, enter a new file size. For tablespaces with multiple data files, such as FUSION_TS_TX_DATA, you may delete the additional data files using the Remove Data File icon (X).
Click OK when you have configured all the tablespaces to return to the Map Tablespaces screen.
Click OK to dismiss the screen.
You can run the Applications RCU from the command line instead of using the graphical interface. This section includes instructions for using command-line operations.
The syntax for the Applications RCU command-line interface is as follows:
(UNIX) rcu [-silent|-interactive] command options
(Windows) rcu.bat [-silent|-interactive] command options
Table 3-6 lists and describes the command-line options.
Table 3-6 Applications RCU Command-Line Interface Syntax
| Option | Description |
|---|---|
|
|
Use this command to create a repository. |
|
|
Location of the ComponentInfo.xmlfile. The default location is |
|
|
Location of the StorageInfo.xmlfile. The default location is |
|
|
Type of database to which you are connecting. |
|
|
Credentials for connecting to the database. For Oracle Database, the syntax is |
|
|
Database user name, for example, |
|
|
Database user role, for example, |
|
|
Options are: Yes|No. Default is |
|
|
Skip the clean up of files if the creation of a component fails. |
|
|
Options are |
|
|
Options are t |
|
|
Comma-separated list in |
|
|
Prefix to be used for the schema. Not used for Oracle Fusion Applications schemas. |
|
|
IDs of the components that you want to add. To specify a single component, use the format: - For example: To specify multiple components, add the components separated by a space. |
|
|
Use only if a tablespace already exists. |
|
|
Use only if a temp tablespace already exists. |
Table 3-7 lists the variables picked up by the Applications RCU from the environment. If an environment variable is not set, it uses the default value.
Table 3-7 Applications RCU Environment Variables
| Variable | Description |
|---|---|
|
|
Location of the Applications RCU log file. Default: |
|
|
Create a timestamped directory. Options are: Default: |
|
|
Name of the Applications RCU log file. Default: |
|
|
Determines the level of the log. Options are: Default: |
An example of the full syntax for creating an schemas and tablespaces from the command line is as follows. It uses UNIX command-line syntax.
$rcu -silent -createRepository -connectString "host:port:sid" -dbUser sys -dbRole sysdba -skipcleanUpOnFailure Yes -component CRM_FUSION_MDS_SOA -component CRM_FUSION_ORABAM -component CRM_FUSION_SOAINFRA -component FIN_FUSION_MDS_SOA -component FIN_FUSION_SOAINFRA -component FSCM_FUSION_ORABAM -component FUSION_ACTIVITIES -component FUSION_BIPLATFORM -component FUSION_DISCUSSIONS -component FUSION_IPM -component FUSION_MDS -component FUSION_MDS_ESS -component FUSION_MDS_SPACES -component FUSION_OCSERVER11G -component FUSION_ORASDPLS -component FUSION_ORASDPM -component FUSION_ORASDPSDS -component FUSION_ORASDPXDMS -component FUSION_ORA_ESS -component FUSION_OTBI -component FUSION_PORTLET -component FUSION_WEBCENTER -component HCM_FUSION_MDS_SOA -component HCM_FUSION_ORABAM -component HCM_FUSION_SOAINFRA -component OIC_FUSION_MDS_SOA -component OIC_FUSION_SOAINFRA -component PRC_FUSION_MDS_SOA -component PRC_FUSION_SOAINFRA -component PRJ_FUSION_MDS_SOA -component PRJ_FUSION_SOAINFRA -component SCM_FUSION_MDS_SOA -component SCM_FUSION_SOAINFRA -component SETUP_FUSION_MDS_SOA -component SETUP_FUSION_SOAINFRA -component SEARCHSYS -component FUSIONAPPS
This section contains troubleshooting tips for database installation and Applications RCU operations. It is divided into sections for general tips and sections about log files and cleanup features.
If you encounter an error during the creation of applications schemas and tablespaces, take note of the following:
Oracle Fusion Applications release notes may contain additional information about this release.
This release of Oracle Fusion Applications relies on certified versions of Oracle Fusion Applications system requirements and supported platforms documentation for details about hardware and software, minimum disk space and memory requirements, required system libraries, packages, or patches, and minimum database requirements.
Ensure that your database is up and running.
If you experience a failure in RCU during the creation of the tablespaces and loading of the Fusion schemas, you must start from the beginning by installing an empty database or using the Database Configuration Assistant. there is no drop option.
Clean up these areas before you redo the installation:
/tmp
old log file directories
/oraInventory folder contents
ORACLE_HOME (or remove the ORACLE_HOME if you need to re-use the directory
If you entered incorrect information on one of the Applications RCU screens, use the navigation pane on the left side of the graphical interface to return to that screen.
If an error occurred while the Applications RCU was running:
Note the error and review the Applications RCU log files.
Correct the issue that caused the error. Depending on the type of error, you can either continue with your operation or restart the Applications RCU.
Continue or restart the Applications RCU to complete the desired operation.
The database installation log file reports what happened during each of the phases in a database installation. Click a log file symbol on the Database Installation Progress screen in the Provisioning Wizard to view the log file for that phase.
Log files describe what happened during the schema and tablespace creation process, including any failures that occurred. The main Applications RCU log file (rcu.log) is written to (Linux) APP_RCU_HOME/rcu/log/logdir.date_timestamp or (Windows) APP_RCU_HOME\rcu\log\logdir.date_timestamp. For example, the log file on a Linux operating system is:
APP_RCU_HOME/rcu/log/logdir.2010-01-02_03-00/rcu.log
The custom_comp_create_tbs.log file lists the PL/SQL statements that created the tablespaces.
In the fusionapps schema, three types of log files are created:
fusionapps.log: Lists the PL/SQL that was run.
fusionapps_runimport.log: The Oracle Data Pump import log file.
fusionapps_verify.log: Lists verification errors if objects created are not what was expected.
In addition to the general log files, each component writes a log file of its own. The file name is in the form of component_name.log. For example, the log file for the BIAPPS_OTBI_RUNIMPORT component is biapps_otbi_runimport.log. All component log files are written to the same directory as the main log file.
Table 3-8 lists the log files in alphabetical order, by component name.
Table 3-8 Applications RCU Log File Names
| Component Log File Name |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
You may encounter the following errors while running the preverification phase on Windows systems:
"C:\repository_location/installers/database/Disk1/setup.exe": CreateProcess error=740, The requested operation requires elevation at java.lang.ProcessBuilder.start(ProcessBuilder.java:460)
If you receive this error, disable User Account Control (UAC) or log in as a Local Administrator to the machine where the Provisioning Wizard is not functioning properly.
If you receive this error when running the preconfigure phase, close the Provisioning Wizard and restart. Select another Oracle Home location.
OPatch failed with error code = 73
UtilSession failed: Prerequisite check "CheckActiveFilesAnd Executables" failed
See http://technet.microsoft.com for more information about UAC.
If there is a failure in creation of the tablespaces or schemas for any component, the Cleanup for failed components check box appears on the Completion Summary screen. Select this option to clean up tablespaces and schemas for the failed components.
If an environment (such as the database server) is running out of space, correct it and rerun the software. Any components that are not applied successfully are still enabled (not grayed out) in the interface. Rerun the Applications RCU as described in Section 3.8.
When you have completed the database installation and the schema and tablespace creation, you are ready to create a provisioning plan for your new applications environment.
Follow the instructions in Chapter 4. You must create a provisioning plan and be ready to supply its location before you can provision an environment.
|
 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
