Database Instances Using Oracle Database 10g Release 2

Export/Import Process for Oracle E-Business Suite Release 12

Database Instances Using Oracle Database 10g Release 2
November 2009

--------------------------------------------------------------------------------

This document describes the process of re-creating an existing Applications Release 12 database instance using the datapump utilities. The most current version of these notes is document 454616.1 on My Oracle Support. There is a change log at the end of this document.

The datapump utilities allow you to move existing data in Oracle format to and from Oracle databases. For example, datapump export files can archive database data, or move data among different Oracle databases that run on the same or different operating systems. This document assumes that you are already familiar with datapump.

There are special considerations when exporting or importing an Applications Release 12 database instance. This process consists of five discrete steps. Each step is covered in a separate section in this document.


Section 1: Prepare the source system
Tasks that must be performed to prepare the source system for the database export

Section 2: Prepare a target Release 12 database instance
Tasks for creating an empty database instance in preparation for import

Section 3: Export the source Release 12 database instance
Tasks that must be performed to produce a valid export of an Applications Release 12 database instance

Section 4: Import the Release 12 database instance
Tasks for running the import utility

Section 5: Update the imported Release 12 database instance
Tasks that must be performed to restore the imported Applications Release 12 database instance to a fully functional state

The source (export from) and target (import to) ORACLE_HOME directories must be Oracle Database 10g Release 2 (10.2.0).

The export/import process requires the use of both the datapump utilities (expdp/impdp) and the traditional export/import (exp/imp). For more information, read Oracle Database Utilities 10g Release 2 (10.2).

Attention: This document uses UNIX/Linux syntax when describing directory structures. However, it applies to Windows servers as well. Where there is a significant difference in tasks for Windows, specific instructions are given.



Some of the tasks in this document affect the APPL_TOP of one or more application server tiers. Those tasks require that the Applications file system environment be enabled by running the APPSORA.env file (for UNIX or Linux) or the envshell.cmd file (for Windows) prior to performing the tasks. Other tasks affect the Applications database instance. Those tasks require that the Oracle 10g environment be enabled by running the [ORACLE_SID].env/cmd file under the Oracle 10g Oracle home on the database server node prior to performing the tasks. In addition, you may have more than one Oracle home installed on the database server node, so it is important that you run the correct [ORACLE_SID].env/cmd file before performing tasks that affect the database instance. Read the instructions carefully to determine which environment should be enabled for each step.

Attention: This document assumes that the source and target application server tiers are the same. Creating new application server tiers for the target environment has to be done either before starting or after completing all the steps in this document. Then, update and run AutoConfig for the source database and application server tiers to enable the source environment.



Attention: If you are using Oracle Database Vault, refer to Note 822048.1 before performing any step in this document.





--------------------------------------------------------------------------------

Section 1: Prepare the source system
This section describes how to ensure that you have the required patches, create your export file, and capture important information that is required to import your database.


Apply latest AutoConfig patches
Perform steps 3.1 and 3.2.1 of the Using AutoConfig to Manage System Configurations in Oracle Applications Release 12 document. The other steps in 3.2 are not necessary as they will be done at the target side.


Apply the Applications consolidated export/import utility patch
Apply patch 7120092 to the source administration server node. This patch provides several SQL scripts that facilitate exporting and importing an Applications database instance, export and import parameter files, and a perl script, which creates an AD patch driver.


Apply latest Applications database preparation scripts patch (conditional)
If you are using Oracle E-Business Suite Release 12.0, apply patch 6342289 to every application tier server node in the source system.


Create a working directory
Create a working directory named expimp in the source system that will contain all generated files and scripts required to complete this section. As an example,

$ mkdir /u01/expimp


Generate target database instance creation script aucrdb.sql
The target database instance must be created with the same tablespace and file structure as the source database instance. The export/import patch provides the auclondb.sql script which generates the aucrdb.sql script, which you use to create the target database instance with the appropriate tablespace and file structure. The script converts all tablespaces except for SYSTEM to locally managed tablespaces with auto segment space management, if they are not already so.

On the source administration server node, use SQL*Plus to connect to the database as SYSTEM and run the $AU_TOP/patch/115/sql/auclondb.sql script. It creates aucrdb.sql in the current directory.


$ sqlplus system/[system password] \
@$AU_TOP/patch/115/sql/auclondb.sql 10


Record Advanced Queue settings
Advanced Queue settings are not propagated in the target database instance during the export/import process. Therefore, you must record them beforehand and enable them in the target database instance afterwards. The export/import patch contains auque1.sql, which generates a script called auque2.sql. You can use auque2.sql to enable the settings in the target database instance.

Copy the auque1.sql script from the $AU_TOP/patch/115/sql directory on the source administration server node to the working directory in the source database server node. Then, on the source database server node, as the owner of the source database server file system and database instance, use SQL*Plus to connect to the source database as sysdba and run the auque1.sql script. It generates auque2.sql.


$ sqlplus /nolog
SQL> connect / as sysdba;
SQL> @auque1.sql


Create parameter file for tables with long columns
Tables with long columns may not propagate properly in datapump. Therefore, they have to be migrated separately using the traditional export/import utilities.

Copy the aulong.sql script from the $AU_TOP/patch/115/sql directory on the source administration server node to the working directory in the source database server node. Then, on the source database server node, as the owner of the source database server file system and database instance, use SQL*Plus to connect to the source database as sysdba and run the aulong.sql script. It generates aulongexp.dat.

$ sqlplus /nolog
SQL> connect system/[system password];
SQL> @aulong.sql


Remove rebuild index parameter in spatial indexes
Ensure that you do not have the rebuild index parameter in the spatial indexes. To see if you have any rebuild index parameters, on the source database server node, as the owner of the source database server file system and database instance, use SQL*Plus to connect to the source database as sysdba and run the following command:

SQL> select * from dba_indexes where index_type='DOMAIN' and
upper(parameters) like '%REBUILD%';
To remove the rebuild index parameter, use SQL*Plus to connect to the source database as the owner of the index and run the following command: SQL> alter index [index name] rebuild parameters [parameters]
where [parameters] is the original parameter set without the rebuild_index parameter.

Deregister the current database server (conditional)
If you plan to change the database port, host, SID, or database name parameter on the database server, deregister the current database server node by running the following command as the owner of the Oracle RDBMS file system and current database instance:


$ perl $ORACLE_HOME/appsutil/bin/adgentns.pl appspass=apps
contextfile=$CONTEXT_FILE -removeserver



--------------------------------------------------------------------------------

Section 2: Prepare a target Release 12 database instance
This section describes how to create the empty target database and populate it with all of the required system objects prior to running import.

The Oracle home of the target database instance can be the same Oracle home that the source database instance uses, or it can be different (on another machine running a different operating system, for example), as long as it uses Oracle Database 10g Release 2 Enterprise Edition.


Create target Oracle 10g Oracle home (conditional)
If you want the target Oracle 10g Oracle home to be separate from the source Oracle home, you must create it now. Decide whether you want to install the 10.2.0 Oracle home manually, or use the Rapid Install to create it for you.

If you choose to use Rapid Install, you must use Rapid Install Release 12.0.0. As the owner of the Oracle RDBMS file system, start the Rapid Install wizard by typing:

$ rapidwiz -techstack

Choose the "10gR2 RDBMS" option in the techstack components window and provide the details for the new Oracle home. Make sure that the SID environment setting is set to the same value as your existing database instance.

If you choose to manually install the 10.2.0 Oracle home, log in to the database server node as the owner of the Oracle RDBMS file system and database instance and perform the following steps:

Ensure that environment settings, such as ORACLE_HOME, are set for the new Oracle home you are about to create.

Perform all the steps in Chapter 3 of the Oracle Database Installation Guide 10g Release 2 (10.2), for your platform.

In the subsequent windows, click on the Product Languages button and select any languages other than American English that are used by your Applications database instance, choose the Enterprise Edition installation type, and select the options not to upgrade an existing database and to install the database software only.

Perform tasks in section 3.5, "Installing Oracle Database 10g Products" in the Oracle Database Companion CD Installation Guide for your platform. Do not perform the tasks in the "Preparing Oracle Workflow Server for the Oracle Workflow Middle Tier Installation" section.

In the Installation Types window, click on the Product Languages button to select any languages other than American English that are used by your Applications database instance.

Make sure that the following environment variables are set whenever you enable the 10g Oracle home:

ORACLE_HOME points to the new 10.2.0 Oracle home.

PATH includes $ORACLE_HOME/bin and the directory where the new perl executable is located (usually $ORACLE_HOME/perl/bin).

LD_LIBRARY_PATH includes $ORACLE_HOME/lib.

PERL5LIB points to the directories where the new perl libraries are located (usually $ORACLE_HOME/perl/lib/[perl version] and $ORACLE_HOME/perl/lib/site_perl/[perl version])

Run the $ORACLE_HOME/nls/data/old/cr9idata.pl script to create the $ORACLE_HOME/nls/data/9idata directory. After creating the directory, make sure that the ORA_NLS10 environment variable is set to the full path of the 9idata directory whenever you enable the 10g Oracle home.

Attention: Check to make sure the $ORACLE_HOME/nls/data/9idata directory is created and is non-empty.




Attention (for Windows users): Keep track of the database home name used. For Rapidwiz installed Oracle homes, the home name is [SID]_db102_RDBMS. For manually installed Oracle homes, the home name is what you input when creating the Oracle home.




Upgrade to the latest 10.2.0 patch set (conditional)
If you are not on the latest patch set, perform the following steps from the Oracle E-Business Suite Release 12 with Oracle Database 10g Release 2 (10.2.0) Interoperability Notes on My Oracle Support:

Perform 10.2.0.x Patch Set installation tasks

Apply additional 10.2.0.x RDBMS patches

Do not perform any post-installation patch README steps.


Modify sqlnet.ora file (Windows only)
If the target database server node is running Windows, add the following line to the sqlnet.ora file in the %ORACLE_HOME%\network\admin\[SID] directory, if it does not already exist:

SQLNET.AUTHENTICATION_SERVICES=(NTS)


Create the target initialization parameter file and CBO parameter file
The initialization parameter file (init[SID>.ora) and cost-based optimizer (CBO) parameter file (ifilecbo.ora) are located in the $ORACLE_HOME/dbs directory on the source database server node. Copy both files to the Oracle 10g $ORACLE_HOME/dbs directory on the target database server node.

Refer to Database Initialization Parameters for Oracle Applications Release 12 and update both the init.ora and ifilecbo.ora files with any necessary changes. You may also need to update initialization parameters involving the db_name, control_files, and directory structures.

Ensure that the undo_tablespace parameter in the initialization parameter file of the target database instance matches with the default undo tablespace set in the aucrdb.sql script.

Ignore the initialization parameters that pertain to the native compilation of PL/SQL code. You will be instructed to add them later, if necessary.


Create a working directory
Create a working directory named expimp in the target system that will contain all generated files and scripts required to complete this section. As an example,

$ mkdir /u01/expimp


Create the target database instance
Copy the aucrdb.sql script, generated in Section 1, from the source administration server node to the working directory in the target database server node. Then update the script on the target database server node with any necessary changes to the directory structures for the log file(s), data file(s), or tablespaces, reflecting the layout of the target database server node. If the target database server node is running Windows, update the directory structure from UNIX/Linux format to Windows format or vice versa.

Attention: Using the source tablespace information does not guarantee that the target tablespaces will be enough. It is highly recommended that you go through the source dba_free_space table to see which of the tablespaces are running out and modify the aucrdb.sql script to ensure ample tablespace size on the target database.



Make sure that the environment of your session on the target database server node is set up properly for the target database instance, especially the ORACLE_HOME, ORACLE_SID, and ORA_NLS10 environment settings. (ORACLE_SID must be set to the same value as the db_name parameter in the init[SID>.ora file.) Then, use the following commands to run aucrdb.sql and create the target database instance:

$ sqlplus /nolog
SQL> connect / as sysdba;
SQL> spool aucrdb.log;

For UNIX or Linux:

SQL> startup nomount;
SQL> @aucrdb.sql
SQL> exit;

For Windows:

SQL> startup nomount pfile=%ORACLE_HOME%\dbs\init%ORACLE_SID%.ora
SQL> @aucrdb.sql
SQL> exit;

If PL/SQL of the source database was natively compiled, see the "Compiling PL/SQL Code for Native Execution" section of Chapter 11 of Oracle Database PL/SQL User's Guide and Reference 10g Release 2 (10.2) for instructions on how to natively compile PL/SQL in the target database. Add the parameters that pertain to the native compilation where specified. Do not use the natively compiled code generated by the source database. Oracle does not support switching the PL/SQL compilation mode from interpreted to native (and vice-versa) for an export/import. Exporting/importing using native mode takes significantly more time than interpreted mode.

When the target database instance has been created, restart the database instance.


Copy database preparation scripts to target Oracle home
The database preparation scripts that you applied to the source administration server node in Section 1 contain four scripts that are needed on the target database server node. Copy the following files from the $APPL_TOP/admin directory of the source administration server node to the working directory in the target database server node: addb1020.sql, adsy1020.sql, adjv1020.sql, and admsc1020.sql (UNIX or Linux) or addb1020_nt.sql, adsy1020_nt.sql, adjv1020_nt.sql, and admsc1020_nt.sql (Windows).

As you run each of the next four steps, note the following:

The remarks section at the beginning of each script contains additional information.

Each script creates a log file in the current directory.


Set up the SYS schema
The addb1020.sql or addb1020_nt.sql script sets up the SYS schema for use with the Applications. On the target database server node, use SQL*Plus to connect to the target database instance as SYSDBA and run addb1020.sql (UNIX/Linux) or addb1020_nt.sql (Windows).

Here is an example on UNIX or Linux:


$ sqlplus "/ as sysdba" @addb1020.sql


Set up the SYSTEM schema
The adsy1020.sql or adsy1020_nt.sql script sets up the SYSTEM schema for use with the Applications. On the target database server node, use SQL*Plus to connect to the target database instance as SYSTEM and run adsy1020.sql (UNIX/Linux) or adsy1020_nt.sql (Windows).

Here is an example on UNIX or Linux:


$ sqlplus system/[system password] @adsy1020.sql


Install Java Virtual Machine
The adjv1020.sql or adjv1020_nt.sql script installs the Java Virtual Machine (JVM) in the database. On the target database server node, use SQL*Plus to connect to the target database instance as SYSTEM and run adjv1020.sql (UNIX/Linux) or adjv1020_nt.sql (Windows).

Here is an example on UNIX or Linux:


$ sqlplus system/[system password] @adjv1020.sql

Attention: This script can be run only once in a given database instance, because the scripts that it calls are not rerunnable.




Install other required components
The admsc1020.sql or admsc1020_nt.sql script installs the following required components in the database: ORD, Spatial, XDB, OLAP, Data Mining, interMedia, and ConText. On the target database server node, use SQL*Plus to connect to the target database instance as SYSTEM and run admsc1020.sql (UNIX/Linux) or admsc1020_nt.sql (Windows). You must pass the following arguments to the script, in the order specified:

Argument Value
remove context? FALSE
SYSAUX tablespace SYSAUX
temporary tablespace TEMP


Here is an example on UNIX or Linux:


$ sqlplus system/[system password] \
@admsc1020.sql FALSE SYSAUX TEMP

Attention: All of the components are created in the SYSAUX tablespace regardless of where it was installed in the source database.




Disable automatic gathering of statistics
Copy $APPL_TOP/admin/adstats.sql from the administration server node to the target database server node. Use SQL*Plus to connect to the database as SYSDBA and use the following commands to restart the database in restricted mode and run adstats.sql:


$ sqlplus "/ as sysdba"
SQL> shutdown normal;
SQL> startup restrict;
SQL> @adstats.sql
SQL> exit;


Back up the target database instance
The target database instance is now prepared for an import of the Applications data. You should perform a backup before starting the import.



--------------------------------------------------------------------------------

Section 3: Export the source Release 12 database instance
This section describes how to ensure that you have the required patches, create your export file, and capture important information that is required to import your database.


Create the export parameter file
A template for the export parameter file has been included as part of the the export/import patch. Copy $AU_TOP/patch/115/import/auexpdp.dat from the source administration server node to the working directory in the source database server node. Use a text editor to modify the file to reflect the source environment and other customized parameters.

The customizable parameters are:

Parameter Description Template Value
directory directory where the export dump files will be created dmpdir
dumpfile export dump file name(s) aexp%U.dmp
filesize export dump file size 1GB
log log file name expdpapps.log


interMedia, OLAP, and Data Mining schemas are not exported. The admsc1020.sql script creates these schemas in the target database. Ensure that the schema names in the exclude parameters reflect those in your database.

Create a directory in the system schema that corresponds to the directory specified in the template. Here is an example of how to create a directory named dmpdir:

$ sqlplus system/[system password]
SQL> create directory dmpdir as '/u01/expimp';

Do not change the other parameters.

The export process uses as many of the listed file names as necessary to hold the exported data. You must ensure that the number of dump files specified, as well as the size of each dump file, is sufficient to contain all the data in your source database instance.


Shut down Applications server processes
Shut down all Applications server processes except the database and the Net8 listener for the database. Users cannot use the Applications until the import is completed.


Grant privilege to source system schema
Grant the exempt access policy privilege to system by using SQL*Plus to connect to the database as SYSDBA and run the following command:


SQL> grant EXEMPT ACCESS POLICY to system;


Export the Applications database instance
Start an export session on the source database server node using the customized export parameter file. Use the following command:


$ expdp system/[system password] parfile=[export parameter file name]

Typically, the export runs for several hours.

Attention: See document 339938.1 on My Oracle Support if you encounter the failure:
EXP-00056: ORACLE error 932 encountered
ORA-00932: inconsistent datatypes: expected BLOB, CLOB got CHAR
EXP-00000: Export terminated unsuccessfully




Export tables with long columns
Start an export session on the source database server node using the customized aulongexp.dat file generated in Section 1. Use the following command:


$ exp parfile=aulongexp.dat


Export tables with XML type columns
Copy $AU_TOP/patch/115/import/auxmlexp.dat from the source administration server to the working directory in the source database server node. Start an export session on the source database server node using the following command:


$ exp parfile=auxmlexp.dat


Revoke privilege from source system schema
Revoke the exempt access policy privilege from system by using SQL*Plus to connect to the database as SYSDBA and run the following command:


SQL> revoke EXEMPT ACCESS POLICY from system;



--------------------------------------------------------------------------------

Section 4: Import the Release 12 database instance
This section describes how to use the import utility to load the Oracle Applications data into the target database.


Create the import parameter files
Copy auimpdp.dat, aufullimp.dat, and auimpusr.dat from the $AU_TOP/patch/115/import directory in the source administration server node to the working directory in the target database server node. Make sure that the directory, dumpfile, and logfile parameters in auimpdp.dat and auimpusr.dat are set properly.

Create a directory in the system schema with the name set to the directory specified in the template and the path set to where the export dump files will reside. Here is an example of how to create a directory named dmpdir:

$ sqlplus system/[system password]
SQL> create directory dmpdir as '/u01/expimp';

Save the changed file.


Copy the export dump files
Copy the export dump files from the source database server node to the working directory in the target database server node.


Import the users into the target database
Start an import session on the target database server node using the customized import parameter file. Use the following command:


$ impdp system/[system password] parfile=auimpusr.dat


Import tables with long columns into the target database
Modify the aufullimp.dat file with the following:

Set userid to "sys/[sys password] as sysdba".

Set file to the dump file containing the long tables (longexp by default).

Set the log file appropriately.

Leave the ignore parameter commented out.

Import the tables using the following command:

$ imp parfile=aufullimp.dat

Attention: You will get failures for the triggers as the dependent tables have not yet been imported.




Import the Applications database instance
Start an import session on the target database server node using the auimpdp.dat parameter file. Use the following command:


$ impdp system/[system password] parfile=auimpdp.dat

Typically, import runs for several hours.


Import triggers into the target database
Modify the aufullimp.dat file with the following:

Set userid to "sys/[sys password] as sysdba".

Set file to the dump file containing the long tables (longexp by default).

Change the log file name.

Uncomment the ignore parameter.

Add a line with the parameter "rows=n".

Start an import session on the target database server node using the customized import parameter file. Use the following command:


$ imp parfile=aufullimp.dat


Revoke privilege from target system schema
Revoke the exempt access policy privilege from system by using SQL*Plus to connect to the database as SYSDBA and run the following command:


SQL> revoke EXEMPT ACCESS POLICY from system;



--------------------------------------------------------------------------------

Section 5: Update the imported Release 12 database instance
This section describes how to recreate the database objects and relationships that are not handled by the export and import utilities.


Reset Advanced Queues
Copy the auque2.sql script that was generated in Section 1 from the working directory in the source database server node to the working directory in the target database server node. Then, on the target database server node, as the owner of the Oracle 10g file system and database instance, use SQL*Plus to connect to the target database as SYSDBA and run the auque2.sql script to enable the Advanced Queue settings that were lost during the export/import process. The script creates a log file in the current directory.

$ sqlplus /nolog
SQL> connect / as sysdba;
SQL> @auque2.sql


Start the new database listener (conditional)
If the Oracle Net listener for the database instance in the new Oracle home has not been started, you must start it now. Since AutoConfig has not yet been implemented, start the listener with the lsnrctl executable (UNIX/Linux) or Services (Windows). See the Oracle Database Net Services Administrator's Guide, 10g Release 2 (10.2) for more information.

Attention: Set the TNS_ADMIN environment variable to the directory where you created your listener.ora and tnsnames.ora files.




Run adgrants.sql
Copy $APPL_TOP/admin/adgrants.sql (adgrants_nt.sql for Windows) from the administration server node to the working directory in the database server node. Use SQL*Plus to connect to the database as SYSDBA and run the script using the following command:

$ sqlplus "/ as sysdba" @adgrants.sql (or adgrants_nt.sql) \
[APPS schema name]

Note: Verify the usage of adgrants.sql in the adgrants.sql script. Older versions of adgrants.sql require the APPLSYS schema name parameter to be passed instead of APPS.



Grant create procedure privilege on CTXSYS
Copy $AD_TOP/patch/115/sql/adctxprv.sql from the administration server node to the database server node. Use SQL*Plus to connect to the database as APPS and run the script using the following command:

$ sqlplus apps/[APPS password] @adctxprv.sql \
[SYSTEM password] CTXSYS


Apply patch 6494466 (conditional)
If the target database is Windows and the source is not, apply patch 6494466 on the target database tier. Create the appsutil directory if needed.


Implement and run AutoConfig
Implement and run AutoConfig in the new Oracle home on the database server node. If the database listener of the new Oracle home is defined differently than the old Oracle home, you must also run AutoConfig on each application tier server node to update the system with the new listener.

See Using AutoConfig to Manage System Configurations in Oracle Applications Release 12 on My Oracle Support, especially section 3.2, for instructions on how to implement and run AutoConfig.

Shut down all processes, including the database and the listener, and restart them to load the new environment settings.


Gather statistics for SYS schema
Use SQL*Plus to connect to the database as SYSDBA and use the following commands to restart the database in restricted mode, run adstats.sql, and restart the database in normal mode:


$ sqlplus "/ as sysdba"
SQL> shutdown normal;
SQL> startup restrict;
SQL> @adstats.sql
SQL> shutdown normal;
SQL> startup;
SQL> exit;

Attention: Make sure that you have at least 1.5 GB of free default temporary tablespace.




Re-create custom database links (conditional)
If the Oracle Net listener in the 10.2.0 Oracle home is defined differently than the one used by the old Oracle home, you must re-create any custom self-referential database links that exist in the Applications database instance. To check for the existence of database links, use SQL*Plus on the database server node to connect to the Applications database instance as APPS and run the following query:


$ sqlplus apps/[apps password]
SQL> select db_link from dba_db_links;

The EDW_APPS_TO_WH and APPS_TO_APPS database links, if they exist, should have been updated with the new port number by AutoConfig in the previous step.

If you have custom self-referential database links in the database instance, use the following commands to drop and re-create them:


$ sqlplus apps/[apps password]
SQL> drop database link [custom database link];
SQL> create database link [custom database link] connect to
[user] identified by [password] using
'(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=[hostname])
(PORT=[port number]))(CONNECT_DATA=(SID=[ORACLE_SID])))';

where [custom database link], [user], [password], [hostname], [port number], and [ORACLE_SID] reflect the new Oracle Net listener for the database instance.


Create ConText and AZ objects
Certain ConText objects and the AZ objects dependent on the tables with XML type columns are not preserved by the import process. The consolidated export/import utility patch that you applied to the source administration server node in Section 1 contains a perl script, dpost_imp.pl, that you can run to generate an AutoPatch driver file. You use this driver file to call the scripts that create these objects. Run the following command:


$ perl $AU_TOP/patch/115/bin/dpost_imp.pl [driver file] 10

Once the driver file has been generated, use AutoPatch to apply it on the target administration server node.


Import tables with XML type columns into the target database
Modify the aufullimp.dat file with the following:

Set userid to "az/[az password]"

Set file to the dump file containing the tables with XML types (xmlexp by default).

Change the log file name.

Comment out the ignore and rows parameters.

Start an import session on the target database server node using the customized import parameter file. Use the following command:


$ imp parfile=aufullimp.dat

Once the import is complete, you can delete the export dump files, as well as the export and import parameter files, from the source and target database server nodes.


Populate CTXSYS.DR$SQE table
To populate the CTXSYS.DR$SQE table, use SQL*Plus on the database server node to connect to the Applications database instance as APPS and run the following command:


$ sqlplus apps/[apps password]
SQL> exec icx_cat_sqe_pvt.sync_sqes_for_all_zones;


Compile invalid objects
On the target database server node, as the owner of the Oracle 10g file system and database instance, use SQL*Plus to connect to the target database as SYS and run the $ORACLE_HOME/rdbms/admin/utlrp.sql script to compile invalid objects.


$ sqlplus "/ as sysdba" @$ORACLE_HOME/rdbms/admin/utlrp.sql


Maintain Applications database objects
Run AD Administration on the target administration server node. From the Maintain Applications Database Objects menu, perform the following tasks:


Compile flexfield data in AOL tables

Recreate grants and synonyms for APPS schema


Start Applications server processes
Start all the server processes on the target Applications system. You can allow users to access the system at this time.


Create DQM indexes
Create DQM indexes by following these steps:

Log on to Oracle Applications with the "Trading Community Manager" responsibility

Click Control > Request > Run

Select "Single Request" option

Enter "DQM Staging Program" name

Enter the following parameters:

Number of Parallel Staging Workers: 4

Staging Command: CREATE_INDEXES

Continue Previous Execution: NO

Index Creation: SERIAL

Click "Submit"



--------------------------------------------------------------------------------

Change Record
The following sections were changed in this document.

Date Summary of Changes
10-Dec-2007 Initial release
11-Jan-2008 Changed export/import patch 6258200 to 6723741
3-Jul-2008 Modified AutoConfig related instructions
Added step to populate CTXSYS.DR$SQE table
Added patch 6494466
Updated export/import patch to 6924477
Added instructions related to the exempt access policy grant.
Added aucrdb.sql attention box

25-May-2009 Added attention statement to see 339938.1 when encountering ORA-932
11-Sep-2009 Added Database Vault information
Added revoke exempt access policy for target system

16-Nov-2009 Modified OracleMetaLink to My Oracle Support
Modified AutoConfig step numbers as step numbers in AutoConfig has changed
Modified adgrants.sql to run with APPS parameter
Modified export/import patch to 7120092
Incorporating 12.1 into the document
Modified step to create 9idata directory to ensure directory exists
Replaced Interoperability note links from 454750.1 to 812362.1



Note 454616.1 by Oracle Applications Development
Copyright 2007 Oracle USA
Last modified: Monday, Nov 16, 2009

Frequently Asked Questions: Oracle E-Business Suite Support on x86-64

Frequently Asked Questions: Oracle E-Business Suite Support on x86-64
Last updated July 8, 2008
View Change Record


--------------------------------------------------------------------------------

Questions addressed in this document

What is x86-64?
What operating systems are supported on x86-64?
Is Oracle E-Business Suite supported on x86-64?
What are the benefits of running Oracle E-Business Suite on x86-64?
How do I install Oracle E-Business Suite database on x86-64?
Why are there two installation packages for E-Business Suite Release 12 for Linux?
How do I migrate an existing Oracle E-Business Suite database to x86-64?
Is RAC supported with the database tier on x86-64?
Is cloning supported on an E-Business Suite system with an x86-64 database?
How do I clone the database on platforms that do not support Rapid Clone?

--------------------------------------------------------------------------------

Questions and Answers
What is x86-64?
Answer:
x86-64 (also called x64) refers to both AMD Opteron (AMD64) and Intel Extended Memory (EM64T) processors. AMD64 and EM64T are x86-compatible chip sets with 64-bit extensions. x86-64 based servers can run either a 32-bit or a 64-bit operating system.

Refer to the Intel web site for more information on EM64T and to to the AMD web site for more information on AMD64.

[top]



What operating systems are supported on x86-64?
Answer:
Apple Macintosh, Linux, Microsoft Windows, Solaris and other operating systems are supported on x86-64. Each combination of an operating system and chip architecture is refered to as a platform. Not all these platforms are certified with Oracle E-Business Suite.

[top]



Is Oracle E-Business Suite supported on x86-64?
Answer:
The answer has three parts:

1. 32-bit Operating Systems for Oracle E-Business Suite Release 12 and 11i:
When Linux or Windows 32-bit operating systems are installed, x86-64 servers can be used for Oracle E-Business Suite application and database tiers; "Linux x86" and "Windows 32-bit" platform certification criteria apply. The following 32-bit operating systems are supported:

Microsoft Windows Server 2003
Oracle Enterprise Linux
Red Hat Enterprise Linux
SUSE Linux Enterprise Server
2. Some 64-bit platforms for Oracle E-Business Suite Release 12: the following 64-bit operating systems are supported for both application and database tiers on x86-64 servers:

Oracle Enterprise Linux
Red Hat Enterprise Linux
SUSE Linux Enterprise Server
3. Remaining 64-bit platforms for Release 12 and all 64-bit platforms for Release 11i : when Oracle E-Business Suite Release 11i or 12 application tier is installed on a certified platform, additional platforms may be used for a 64-bit database tier on x86-64 servers. This is an example of a mixed platform architecture. In Release 11i this was known as Split Configuration.

The following 64-bit operating systems are supported on x86-64 servers for E-Business Suite database tier only:

Microsoft Windows Server x64
Oracle Enterprise Linux
Red Hat Enterprise Linux
SUSE Linux Enterprise Server
Sun Solaris x64
For up-to-date information on mixed platform architecture, refer to "Database Tier Only " in Certify -> "View Certifications by Platform", choose "Database Tier Only " in the platform list.


See OracleMetaLink's Certify for more information on certified platforms and specific software versions.

[top]



What are the benefits of running Oracle E-Business Suite on x86-64?
Answer:
When a 32-bit OS is installed on x86-64, the maximum 64 GB of main memory (using Physical Address Extension) provides scalability and stability advantages over x86 (32-bit) processor systems, which are limited to 4 GB. Each process is still limited to a 32-bit memory space (4 GB for Linux, and up to 3 GB for Windows) when running a 32-bit OS on x86-64 processor systems.

When a 64-bit OS is installed on x86-64, the limits on physical and process memory significantly exceed today's manufacturing capabilities.

When larger amounts (upward of 16 GB) of memory are installed, running a 64-bit Linux OS is more stable than running a 32-bit Linux OS.

[top]



How do I install Oracle E-Business Suite database on x86-64?
Answer:
For new installations of Oracle E-Business Suite Release 12 on supported 64-bit Linux operating systems, you can use Rapid Install as directed in "Oracle Applications Installation Guide: Using Rapid Install" to install the database and application tiers.

For Database Tier Only platforms in a mixed platform architecture, you can use Rapid Install as directed in "Oracle Applications Installation Guide: Using Rapid Install" to install the database and application tiers on supported platforms, and then migrate the database tier to a certified 64-bit operating system (see references).

[top]



Why are there two installation packages for E-Business Suite Release 12 for Linux?
Answer:
The Oracle E-Business Suite Applications Release 12.0 Media Pack for Linux x86 is used to install on x86 or x86-64 servers with a supported 32-bit Linux operating system. The Oracle E-Business Suite Applications Release 12.0 Media Pack for Linux x86-64-bit is used to install on x86-64 servers with a supported 64-bit operating system. For the Installation and Upgrade Notes specific to each installation package, refer to the documentation in the references

[top]



How do I migrate an existing Oracle E-Business Suite database to x86-64?
Answer:
To migrate the database to a certified operating system on x86-64, refer to the documentation in the references.

[top]



Is RAC supported with the database tier on x86-64?
Answer:

Yes, it is. RAC certifications are generic and apply to all platforms unless otherwise specified.

Using Oracle 10g Release 2 Real Application Clusters and Automatic Storage Management with Oracle E-Business Suite Release 12 (OracleMetaLink Note 388577.1) contains Oracle E-Business Suite Release 12 with RAC implementation details.

A list of the supported Release 11i versions with RAC is available in Oracle E-Business Suite 11i and Database FAQ (OracleMetaLink Note 285267.1). In addition, the following documents contain Oracle E-Business Suite 11i with RAC implementation details:

Oracle E-Business Suite Release 11i with 9i RAC; Installation & Configuration Using AutoConfig (OracleMetaLink Note 279956.1)
Configuring Oracle Applications Release 11i with 10g Real Application Clusters and Automatic Storage Management (OracleMetaLink Note 312731.1)
If you use parallel concurrent processing (PCP) with Oracle E-Business Suite 11i, we recommend applying ATG Family Pack 11i.ATG_PF.H RUP3 or higher (patch 4334965).

The use of RAC on Solaris 10 Containers (a feature that allows partitioning of an OS into separate virtual hosts) is restricted to global (non-local) containers - please see MetaLink Note 317257.1 for the best practices document for deploying Oracle databases in Solaris 10 Containers.

[top]



Is cloning supported on an E-Business Suite system with an x86-64 database?
Answer:

Yes, it is. For Oracle E-Business Suite systems with database tiers on 64-bit Linux operating systems, use Rapid Clone.

For Oracle E-Business Suite systems with database tiers on Windows x64, use Rapid Clone to clone the application tier and the Oracle database utilities to clone the database tier.

Note: Rapid Clone is not supported on Windows Server 2003 x64

More information about Rapid Clone is available in the references. See the next question to clone the database tier on platforms that do not support Rapid Clone.



How do I clone the database on platforms that do not support Rapid Clone?
Answer:

Cloning the E-Business Suite database tier using the Oracle database utilities is a process of cloning the database Oracle home and creating a duplicate database.

To clone the database Oracle home, use the Oracle Universal Installer (OUI). This process allows you to configure inventory information for the new target Oracle home. See the Oracle Universal Installer and OPatch User's Guide, 10g Release 2 for additional information.

To create a duplicate database, use Recovery Manager (RMAN). See the Oracle Database Backup and Recovery Advanced User's Guide, 10g Release 2 for additional information.




--------------------------------------------------------------------------------

References
Oracle E-Business Suite Release 12
Cloning Oracle Applications Release 12 with Rapid Clone (OracleMetaLink Note 406982.1)

Oracle Applications Installation and Upgrade Notes Release 12 (12.0) for Linux (32-bit) (OracleMetaLink Note 402310.1)

Oracle Applications Installation and Upgrade Notes Release 12 (12.0) for Linux (64-bit) (OracleMetaLink Note 416305.1)

Oracle E-Business Suite 11i
Split Configuration Database Tier documentation:

Using Oracle Applications with a Split Configuration Database Tier on Oracle 10g Release 2 (OracleMetaLink Note 369693.1)

Using Oracle Applications with a Split Configuration Database Tier on Oracle 10g Release 1 (OracleMetaLink Note 356839.1).

Using Oracle Applications with a Split Configuration Database Tier on Oracle 9i Release 2 (OracleMetaLink Note 304489.1)

Cloning Oracle Applications Release 11i with Rapid Clone (OracleMetaLink Note 230672.1)

Recommended Browsers for Oracle E-Business Suite Release 12

Recommended Browsers for Oracle E-Business Suite Release 12

In This Document
Section 1: Overview
Section 2: Internet Explorer for Windows Users
Section 3: Firefox for Windows Users
Section 4: Safari for Mac Users
The most current version of this document can be obtained in note 389422.1

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

Section 1: Overview
This document outlines the requirements for browsers that are certified for use with the Oracle E-Business Suite 12.

To check certification information please examine the Certifications page from https://support.oracle.com by entering the following values;.

Product Line - 'Oracle E-Business Suite'
Product Family - 'Applications Technology'
Product Area - 'Lifecycle Management'
Product - 'Application Install'
Product release - 'as required'
Tier - 'Client'
Click the 'Search' button.
Section 2: Internet Explorer for Windows Users
Prerequisite Patch Requirements
Internet Explorer 8 on Windows XP, Windows Vista and Windows 7
Internet Explorer 8 is certified as a client browser on Windows XP SP2 & SP3, Windows Vista SP1 & SP2 and Windows 7 with the following patch requirements;

Oracle E-Business Suite Release 12.1.1 or higher.
Oracle E-Business Suite Release 12.0 with R12.ATG_PF.A.DELTA.6 (patch 7237006) or higher
Oracle forms 10.1.2.3 or higher
Internet Explorer 7 with Windows Vista
Internet Explorer 7 is certified as a client browser on Windows Vista, SP1 & SP2 with the following patch requirements:-

Oracle E-Business Suite Release 12.1.1 or higher.
Oracle E-Business Suite Release 12.0, with R12.ATG_PF.A.DELTA.3 (patch 6077669) or higher.
Certification Matrix for Internet Explorer (IE)
The table below outlines the currently certified Browser, Operating System and JRE streams with minimum versions, where applicable:

Browser
Version Windows 7 Windows Vista SP1 & SP2 Windows XP SP2 & SP3 Windows 2000
IE 8 JRE 1.6.0_03 or higher JRE 1.6.0_03 or higher JRE 1.6.0_03 or higher Not Certified
JRE 1.5.0_10-erdist or higher JRE 1.5.0_10-erdist or higher JRE 1.5.0_10-erdist or higher
IE 7 Not Certified JRE 1.6.0_03 or higher JRE 1.6.0_03 or higher Not Certified
JRE 1.5.0_10-erdist or higher JRE 1.5.0_10-erdist or higher
IE 6 Not Certified Not Certified JRE 1.6.0_03 or higher JRE 1.6.0_03 or higher
JRE 1.5.0_10-erdist or higher JRE 1.5.0_10-erdist or higher

Compatibility with Higher Sun JRE releases
Oracle has certified the Oracle E-Business Suite with the minimum Sun JRE releases noted above on the JRE 1.6 and JRE 1.5 streams. Oracle E-Business Suite end-users may use or upgrade to later production releases of the Sun JRE plug-in on, either stream, at their discretion. It is recommended to upgrade to the latest certified JRE releases to uptake the latest security and functional fixes. For further information on upgrading JRE and it's requirements and known issues, please reference note 393931.1 titled, 'Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite Release 12'.

Oracle will continue to test and certify the Oracle E-Business Suite with selected future versions of Sun JRE releases in advance of their general availability to the public. Oracle will update this documentation with known compatibility issues or workarounds as needed.

3rd Party Software Support Lifecycle
Oracle's certification of the various third party client operating system and browsers aligns with the respective vendor's support lifecycle. You may find Microsoft's support timelines for OS and browsers at http://support.microsoft.com

Recommended Internet Explorer Browser Settings
Security Zones
Microsoft Internet Explorer offers four different security zones to run your application through. Which zone is used is dependant how you are accessing your site (Internet or Local Intranet) and set up within the zones themselves (Trusted sites & Restricted sites).

It is advisable to have the security setting at Medium for run-time use.

The Security Internet Options on Microsoft Internet Explorer can be accessed by going to;

Tools -> Internet Options -> Security tab from the Internet Explorer Menu Bar.

Each zone carries its own default security level that may need to be adjusted when accessing Oracle E-Business Suite through it. The defaults are as follows;

Zone Usage Default for IE8 & IE7 Default for IE6
Internet Web sites not placed in other zones Medium-high Medium
Local Intranet Web sites on your organization's intranet Medium-low Medium-low
Trusted Sites Web sites you trust not to damage your computer Medium Low
Restricted Sites Web sites that could potentially damage your computer High High

It is recommended that Oracle E-Business Suite is run through the 'Trusted Sites' zone, with a 'Medium' Security Setting.

Setting up Oracle E-Business Suite to run through the 'Trusted Sites' zone, with a 'Medium' Security Setting. (If Required)
Step 1: Select Tools -> Internet Options -> Security tab -> Trusted Sites icon -> Sites button from the Internet Explorer Menu Bar.
Step 2: Set the 'Security Level for this Zone' to 'Medium' if it is not set already.
Step 3: In the 'Add this Web site to the zone:' field, enter the 'hostname and domain' of the environment you are running the Oracle E-Business Suite from; i.e. https://., then click the 'Add' button. Alternatively you can simply add the domain name preceded by '*', so that all sites under that domain go through this zone. i.e. *.

(If you are entering an http://... or '*.' domain address, you must ensure that the 'Require server verification (https:) for all sites in this zone' is not checked).

Internet Explorer Browser Settings for User Download of oaj2se.exe
Oracle recommends that customers running Oracle E-Business Suite through Internet Explorer (IE) should use a 'Medium' security setting through the 'Trusted Sites' zone in the browser at runtime. This setting does not automatically download the oaj2se.exe file from the middle tier if the user does not already have the appropriate version installed on their desktop.

The JRE plug-in will download and install from the webserver on a medium security setting. After clicking on a 'forms link', a message similar to the following will appear at the top of the browser window;

'The website wants to install the following add-on: 'J2SE Runtime Environment 6 Update 3' from 'Sun Microsystems, Inc.'. If you trust this website and the add-on and want to install it, click here...'

To install the plug-in:-

Click on the message above and select 'Install ActiveX Control...'
Once the browser has stopped processing, click on the 'forms link' again, and the oaj2se.exe file should start to download
Once the download has completed, a security warning pop-up window will ask, 'Do you want to install this software?'
Click on the 'Install' button and follow the on screen instructions
Alternatively, to enable the download of this file, the user should temporarily alter the security settings within their browser using one of the two methods below:
Method A: Change Security Setting to Medium-low
Select 'Tools' -> 'Internet Options -> 'Security' (Tab)' from the browser menu.
Select 'Trusted Sites' -> 'Custom Level' (button)
From the 'Reset custom settings' drop down select 'Medium-low'
Click the 'Reset...' button and accept the changes.
Press the 'okay' buttons to close the window.
Close the browser and start a new browser session for the settings to take effect.
After launching Oracle E-Business Suite and downloading the oaj2se.exe file onto your desktop, please reset the security setting back to 'Medium'
Method B: Change Individual Parameter Settings
Select 'Tools' -> 'Internet Options -> 'Security' (Tab)' from the browser menu.
Select 'Trusted Sites' -> 'Custom Level' (button)
Under 'Settings' -> 'ActiveX controls and Plug-ins'
Change 'Automatic prompting for ActiveX controls' to 'Enable'
Change 'Download unsigned ActiveX controls' to 'Prompt'
Click the 'OK' button and accept the changes and click the 'OK' buttons to close the window
Close the browser and start a new browser session for the settings to take effect.
After launching Oracle E-Business Suite and downloading the oaj2se.exe file onto your desktop, please reset
'Automatic prompting for ActiveX controls' to 'Disable' and
'Download unsigned ActiveX controls' to 'Disable'.
Use of Excel with WebADI
To create an excel spreadsheet on your desktop through WebADI, the 'Initialize and script Active X controls not marked as safe' setting must be set to 'Prompt'. This is only defaulted to this value on a 'Low' security setting', therefore you will probably need to alter this setting through Internet Explorers Custom Settings. From the browser menu;

Select Tools -> Internet Options -> Security tab.
Select the zone that you are running Oracle E-Business Suite through and click the 'Custom Level' button.
Set the 'Initialize and script Active X controls not marked as safe' option to 'Prompt'.
Page Refresh
When using Oracle Self-Service products it is important to ensure that the most current data is being viewed. You may check if the page has been updated since your last visit by manually refreshing the page, however it is desirable for this to be done automatically through IE by setting the following parameter from the browser menu as follows;

IE7 and IE8 Users

Select Tools -> Internet Options -> General tab -> Browsing History -> Settings button.
Select 'Every time I visit the webpage'.
With this option set Internet Explorer will check if the page has changed since it was last viewed.
IE6 Users

Select Tools -> Internet Options -> General tab -> Settings button.
Select 'Every visit to the page'.
With this option set Internet Explorer will check if the page has changed since it was last viewed.
Shared Desktop Security
If multiple users share the same desktop, they may be able to view a previous users browser content by pressing the 'Back' button on the browser. To avoid this issue please set the 'Force Page Refresh' profile option to 'Yes' at Site level in your Oracle E-Business Suite 12 instance.

For security reasons, if a PC is shared by multiple users it is also advisable not to save encrypted pages onto the drive. To set this option please go to Tools -> Internet Options -> Advanced tab -> Security settings and tick 'Do not save encrypted pages to Disk'.

Exception: SSL users who export Discoverer Workbooks to excel must leave this parameter unchecked.
AutoComplete in Internet Explorer
IE can automatically show previous values entered in the same form field. For privacy and security reasons this feature should be disabled as follows;

Go to Tools - > Internet Options -> Content
Click the AutoComplete 'Settings' button
Uncheck the 'Forms' and 'User names and passwords on forms' check boxes.
HTTP 1.1/Keep Alive Settings
Users should have the HTTP 1.1/Keep Alive option enabled.

To set this option, from the browser menu select;

Tools -> Internet Options -> Advanced tab -> HTTP 1.1 Settings.
Please ensure 'Use HTTP 1.1' and Use HTTP 1.1 through proxy connections' are both ticked
Importing an SSL Certificate into Internet Explorer on Windows Vista and Windows 7
Connecting to a Secure Socket Layer (SSL) enabled environment requires the certificate to be 'Trusted'. If the certificate is not from a trusted authority or has not previously been trusted on the client, it must be verified at runtime. When accessing such an environment it will return the following warning message: 'There is a problem with this website's security certificate'. Using the automatic default install button can cause the certificate to be added to the browser's 'Intermediate Certification Authorities' folder and not the required 'Trusted Root Certification Authorities' folder. Therefore the security message will still display.

Installing an SSL certificate into the Browsers Trusted Certificates folder requires the browser's security option 'Enable Protected Mode' to be turned off, which is the default setting in the 'Trusted Sites' zone. This feature is available in Internet Explorer for Vista and Windows 7, and does not exist in the XP version of the browser. ('Enable Protected Mode' may be turned on after the certificate has been installed for runtime use).

To trust the certificate authority thus stopping this error page appearing on future logins;

Enter the URL in the browser
From the browser menu select; Tools -> Internet Options -> Security -> Trusted Sites icon. Security setting should be 'Medium' by default
Make sure the 'Enable Protected Mode' option is off (not checked)
Click the 'Sites' button and add the url if it is not there already (or add *.oracle.com to cover all Oracle environments, you must uncheck the 'Require Server Verification....' option first to allow you to add it)
Save the changes and close the browser window
Enter the URL in a new browser window
You will again see a message saying There is a problem with this website's security certificate'. Click on, 'Continue to this website (not recommended)
In the taskbar click on the Red certificate error
An Untrusted Certificate Window Pops, click on 'View Certificates'
Click on Certification Path 'Tab'
Highlight the Root certificate (will probably have a white cross in a red background next to it) and press 'View Certificate'
Click on Install Certificate 'button' and press next
Select 'Place all the certificates in the following store'
Click 'Browse' and tick the 'Show physical Stores' box.
Click the + next to 'Trusted Root Certification Authorities' folder
If a folder exists called 'Local Computer' Click on it and select 'Okay'
If that folder does not exist, highlight 'Trusted Root Certification Authorities' folder and select 'Okay'
Press 'Next' followed by 'Finish'
When the Security Window pops asking if you wish to install it, say 'Yes' then hit the 'finish' button
Close the pop-up and the browser, when you next login, it should be fine.
If the install button is not active when trying to install the certificate, it may have been installed previously using the automatic facility (Into the 'Intermediate Certification Authorities' zone). To remove the certificate;
Open the browser and go to Tools -> Internet Options -> Content -> Certificates -> Intermediate Certificate Authorities
Highlight the appropriate certificate for the instance you are trying to access, press the 'Remove' button then close down the browser
Open a new browser session and follow the steps above to install the certificate into the 'Trusted Certificates' folder
Known Issues for Internet Explorer Users
Internet Explorer 8
Windows Vista and Windows 7 for Internet Explorer
General Internet Explorer Issues
Internet Explorer 8 (IE8)
Cross-Site Scripting Error
Oracle E-Business Suite 12.0 and 12.1.1 users may see the following error in the browser window when launching a forms based application;

'Internet Explorer has modified this page to prevent a possible cross-site scripting attack'

The required Forms 10.1.2.3 servlet components may not have been deployed properly when Forms 10.1.2.3 was first installed in your Oracle E-Business Suite Release 12 environment (Bug 8608695).

If your IE 8 end-users encounter this error when attempting to launch a Forms-based E-Business Suite product, redeploy the Forms 10.1.2.3 formsapp.ear file by following Note 397174.1 titled, 'Deploying a New Forms .ear File in Oracle Applications Release 12'.

Multiple Java Console Windows Open
With the 'Show Console' option set in the Java Control Panel, launching a forms based application through IE8 may cause two separate 'Java Console' windows to open. Accessing further applets from the same Oracle E-Business Suite session may also cause further 'Java Console' windows to appear. This is expected behavior due to the Loosely-Coupled IE (LCIE) functionality within IE8. This functionality splits the browsers frame and its tabs into separate processes on the desktop to improve performance and browser recovery if a tab crashes. This will not always be seen because not every tab will necessarily be started in its own process as LCIE will attempt to balance reliability with performance. Therefore the issue of multiple java console windows is most likely to be seen if running from a high specification multi-core processor desktop.

If required you can prevent the java console from appearing by running the following from your desktop client;

Control Panel -> Java icon -> Advanced tab -> Java Console -> select the 'Hide Console' radio button

Windows Vista and Windows 7 with Internet Explorer
The following issues are applicable for users running on Windows Vista through IE7 or IE8, and Windows 7 through IE8.

Balanced Scorecard Users
The VB client is not supported on Windows Vista or Windows 7.

Discoverer Users
Discoverer (10g) 10.1.2.3 is certified with Windows Vista. For further information please see note 456426.1.

Discoverer 10.1.2.2 and earlier are not certified with Windows Vista or Windows 7.

Financial Analyzer and Sales Analyzer Users
Financial Analyzer and Sales Analyzer client versions (6.4) are not supported on Windows Vista or Windows 7. Please use the OFA and OSA web versions, see note 470992.1.

XML Reports (RTF file extensions)
Windows Vista and Windows 7 users cannot open *.rtf format files through the browser. When clicking the 'OK' button on the 'Opening *.rtf' modal window the file will not open and the modal window will come up again. To correct the problem, associate a different program such as Wordpad, OpenOffice.org etc. with the .rtf extension on the desktop.

Control Panel -> Default Programs -> Associate a file type or protocol with a program
Select .rtf under the Name column from the list
Click the 'Change Program' button.
Select an appropriate program i.e. Wordpad
Click the 'OK' button
General Internet Explorer Issues
Discoverer Viewer Users
After clicking the drill icon on a worksheet the drill items are not listed when running Discoverer Viewer through IE7 and higher. To fix this issue;

Discoverer Viewer 10.1.2.0.2 and 10.1.2.1 and 10.1.2.2 users should apply patch 5673463. Please contact support to request this patch.
Discoverer Viewer 10.1.2.2 Cumulative Patch (CP7) and lower users should apply patch 5673463. Please contact support to request this patch.
This issue is fixed in Discoverer 10.1.2.2 Cumulative Patch (CP8) and Discoverer 10.1.2.3 and higher.

Tabbed Browsing in IE 7 and IE 8
Forms Windows
IE7 and higher provides a tabbed browsing facility, which can be enabled from the browser menu through Tools -> Internet Options -> General Tabs -> Settings. Forms in Oracle E-Business Suite are supported and launched through a separate frame. Therefore, even with tabs enabled, the forms navigator and the forms windows will continue to open in a new window and not in a new tab. This is intended functionality and is not a bug.

Web Based LOV's
If the 'Always Open Pop-Ups in a New Tab' option within IE 7 or IE 8 is selected, Web based LOV's can lose focus. To regain focus within the pop-up window press 'Ctrl & Tab'. This option is set through Tools -> Internet Options -> Tabs -> Settings -> Always Open Pop-Ups in a New Tab.

For further information please see bug 6242250

Exporting Data and Opening Attachments
The file type that you wish to export from the Oracle E-Business Suite must be associated with the browser. If the file type is not associated, the Window will not open or will briefly open and then close immediately. This may occur for example, when using 'File -> Export' to an excel spreadsheet or when opening an attachment from the Oracle E-Business Suite.

To fix this issue, using the 'Trusted Sites' zone as an example, (which is recommended for running the Oracle E-Business Suite through);

Select 'Tools' -> 'Internet Options' -> 'Security' (tab) -> 'Trusted Sites' -> 'Custom Level' (button) -> 'Downloads' from the browser menu.
Set 'Automatic prompting for file downloads' to 'Enable'.
Save the setting and close the browser window.
Start a new browser session and login to the Oracle E-Business Suite.
This time, when trying to open the attachment or export data you should see a pop up windows titled 'File Download'.
Uncheck the checkbox labeled, 'Always ask before opening this type of file' and click the 'open' button.
The file should now display correctly.
After this has been done, the file extension type is registered and you may set the 'Automatic prompting for file downloads' back to 'disable', accessing such files in future will now work correctly with that setting.
Browser Helpers and Toolbars
The use of certain browser helpers and Toolbars may cause the browser to crash when trying to login to Oracle E-Business Suite due to their incompatibility with older plug-in versions. To remove a toolbar;

On the Start menu, click Control Panel
Double-click Add or Remove Programs
Select the appropriate toolbar
Click the Remove button
To disable an add-on;

From the bowser menu, Tools -> Manage Add-ons -> Enable or Disable Add-ons
Select the appropriate add-on
Under 'Settings' click the 'disable radio' button
Restart the browser
Section 3: Firefox for Windows Users
Prerequisite Patch Requirements
Firefox 3.0, Firefox 3.5 and Firefox 3.6
Firefox 3.0, Firefox 3.5 and Firefox 3.6 are certified as client browsers on Windows XP SP2 & SP3, Windows Vista SP1 & SP2 and Windows 7 with the following minimum requirements:-

Oracle E-Business Suite Release 12.1.1 or higher.
Oracle E-Business Suite Release 12.0.x with;
Oracle Applications Technology R12.ATG_PF.A.delta.6 (patch 7237006) or higher
Applications Framework Patch 7602616
It is also strongly recommended to apply patch 7567840 which removes the use of the jpi-version parameter and switches Firefox to a non-static versioning model. For further information see Multiple Desktop JRE Plug-in Versions with Firefox 3.0.x
Certification Matrix for Firefox Browser
The table below outlines the currently certified Browser, Operating System and JRE streams with minimum versions, where applicable:

Browser Version Windows 7 Windows Vista, SP1 & SP2 Windows XP SP2 & SP3 Windows XP & Windows 2000

Firefox 3.6.x JRE1.6.0_10 and higher JRE1.6.0_10 and higher JRE1.6.0_10 and higher Not Certified
Firefox 3.5.x JRE1.6.0_03 and higher JRE1.6.0_03 and higher JRE1.6.0_03 and higher Not Certified
JRE1.5.0_10-erdist to JRE1.5.0_22 JRE1.5.0_10-erdist to JRE1.5.0_22 JRE1.5.0_10-erdist to JRE1.5.0_22
Firefox 3.0.x Not Certified JRE1.6.0_03 and higher JRE1.6.0_03 and higher Not Certified
JRE1.5.0_10-erdist to JRE1.5.0_22 JRE1.5.0_10-erdist to JRE1.5.0_22

Firefox 3.6.x Users
Firefox 3.6.x only supports next-generation java plug-in releases (JRE 1.6.0_10 or higher). Forms based products cannot be launched using 'classic java' versions (JRE 1.6.0_07 or earlier or JRE 1.5.x).

If a 'next generation java' plug-in version is not available on the desktop client the browser will display the message, 'Additional plugins are required to display all the media on this page'.

If an appropriate version is available from the Oracle E-Business Suite web server it can be downloaded and installed in the usual way. Alternatively, clicking the 'Install Missing Plugins' button or the 'Click here to download plugin' box will activate the Firefox 'Plugin Finder Service' which will offer the latest available version of the JRE 1.6.x plug-in for download and install.

Compatibility with Higher Sun JRE releases
Oracle has certified the Oracle E-Business Suite with the minimum Sun JRE releases noted above on the JRE 6 (1.6.0.x) stream. Oracle E-Business Suite end-users may use or upgrade to later production releases of the Sun JRE 6 plug-in at their discretion. For further information on upgrading JRE and it's requirements, please reference note 393931.1 entitled 'Upgrading Sun JRE (Native Plug-in) with Oracle E-Business Suite 12 for Windows Clients'.

Oracle will continue to test and certify the Oracle E-Business Suite with selected future versions of Sun JRE releases in advance of their general availability to the public. Oracle will update this documentation with known compatibility issues or workarounds as needed. All current JRE production versions equal to or higher than the minimum versions stated above are compatible with Oracle E-Business Suite 12.

3rd Party Software Support Lifecycle

Oracle's certification of the various third party client operating system and browsers aligns with the respective vendor's support lifecycle. You may find Mozilla/Firefox support timelines at http://www.mozilla.org/projects/firefox/roadmap.html

NOTE: Firefox 2.0.x is no longer supported by the vendor. It is recommended that any users still running Firefox 2.0.x upgrade to Firefox 3.0.x or higher. Oracle will continue to offer support for Firefox 2.0.x with Oracle E-Business Suite Release 12 on a 'Best Effort' basis only. Consequently, where issues are due to problems with the browser, we may, where necessary, require customers to upgrade or change their browser to resolve the issue.

Recommended Firefox Browser Settings
Shared Desktop Security
If multiple users share the same desktop, they may be able to view a previous users browser content by pressing the 'Back' button on the browser. To avoid this issue please set the 'Force Page Refresh' profile option to 'Yes' at Site level in your Oracle E-Business Suite 12 instance.

Importing an SSL Certificate into Firefox 3
Connecting to a Secure Socket Layer (SSL) enabled environment requires the certificate to be 'Trusted' within the browser. If the certificate is not from a trusted authority or has not previously been trusted on the client, it must be verified at runtime. When accessing such an environment a warning message will display:

Secure Connection Failed

(Error code: sec_error_ca_cert_invalid)

This could be a problem with the server's configuration, or it could be someone trying to impersonate the server.
If you have connected to this server successfully in the past, the error may be temporary, and you can try again later.
Or you can add an exception...

To trust the certificate authority and to stop this error page appearing on future logins, add an exception;

Click on 'Or you can add an exception...' link.
Click ' Add Exception...' button.
Check 'Permanently store this exception'.
Click 'Confirm Security Exception' button.
Known Issues for Firefox Users
General Firefox Issues
Windows Vista and Windows 7 with Firefox
General Firefox Issues
JRE Plug-in Download Using Firefox (oaj2se.exe)
Oracle E-Business Suite 12.0.x Users

If using a non-static versioning model (patch 7567840 has not been applied) and the correct 'JRE Plug-in' version is not already installed on the client it will not automatically download from the web server when using a Firefox browser. This is due to bug 5855986.

To workaround this problem, the user can either download and install the JRE Plug-in, before launching the Oracle E-Business Suite, or can still download it from the server as follows.

Clicking on a forms link through Firefox will activate the 'Plug-in Finder Service'. The user will then see the message 'Additional plug-ins are required to display all the media on this page' in the taskbar.

Click on the 'Install Missing Plug-ins' button. (This will open a new window, search for the plug-in but will not find it)
Click on the 'Manual Install' button, which should open another window saying;
Forbidden
You don't have permissions to access /OA_JAVA/ on this server.

In the URL line on this window change http://:/OA_JAVA to http://:/OA_HTML/oaj2se.exe.
When asked if you wish save the oaj2se.exe file. Click the 'Save File' button and install the file onto your desktop
Once it has installed successfully, close down the firefox window and start a new session to access the Oracle E-Business Suite.
Multiple Sessions
You may only access a single Oracle E-Business Suite instance from a single desktop session when using the Firefox browser. Currently 'Internet Explorer' is the only browser that allows you to access multiple instances or multiple Application Responsibilities concurrently from the same desktop session, through the use of multiple browser sessions.

Multiple Desktop JRE Plug-in Versions
Multiple Desktop JRE Plug-in Versions with Firefox 3.x
Firefox 3.0.x supports 'Next-Generation JRE Plug-in' technology which is enabled by default when running JRE 1.6.0_10 and higher.

Oracle E-Business Suite 12.0.x Users

It is strongly recommended Oracle E-Business Suite 12.0.x users running Firefox 3.0 users apply patch 7567840. Without this patch the latest jre plug-in version on the desktop would have to match the jre plug-in version being called from the web server to successfully load a form. See Multiple Desktop JRE Plug-in Versions with Firefox (Static Versioning)

Whilst there is limited backward compatiblity, using the jpi-version attribute of the MIME type to select a particular JRE version is no longer supported by Sun when using the next-generation JRE plug-in (JRE 1.6.0_10 and higher). This patch changes the behavior within Oracle E-Business Suite Release 12 by removing the jpi-version parameter to overload the usage of the application/x-java-applet MIME type and implement the java_version parameter for JRE version selection. Further information is available from; https://jdk6.dev.java.net/plugin2/version-selection/#JPI_VERSION.

This patch changes the behavior of Firefox 3.0 to a 'non-static versioning' model. Earlier 'classic' java versions can also be run on this new architecture and they will also then adhere to a the non-static versioning model.

Oracle E-Business 12.1.1 Users

Oracle E-Business 12.1.1 users do not require patch 7567840. This architectural change is included by default making Firefox 3.0 adhere to the non-static versioning model.

For further information on static and non-static versioning please see Appendix A: Static vs Non-Static Versioning and Set Up Options in note, 393931.1, titled, 'Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite Release 12'.

(Return to Prerequisite Patch Requirements section if required.)

Multiple Desktop JRE Plug-in Versions with Firefox (Static Versioning)
By default, Firefox only uses the latest version of the plug-in that it finds on the desktop client. Unless Oracle E-Business Suite is set to use the latest available version of the plug-in, users may not be able to connect using earlier versions of the plug-in.

To enable Firefox to use multiple versions of the plug-in from the desktop client, (thus allowing the use of jre plug-ins on the desktop that are not the latest version installed on that desktop) the following workaround can be used;

Copy '\bin\npjpi.dll' to '\plugins'.
(Using JRE 1.6.0_03 as an example in a default installation, this would be) -

Copy C:\Program Files\Java\jre1.6.0_03\bin\npjpi160_03.dll to C:\Program Files\Mozilla Firefox\plugins

To check which versions are available within Firefox type, 'about:plugins' in the address bar.
Note: This workaround is not valid when running Firefox 3.0 with JRE 1.6.0_10 or higher installed on the desktop client.
Tab functionality in the Firefox Browser
Firefox uses tabbed browsing by default. Forms in Oracle E-Business Suite are supported and launched through a separate frame. Therefore, even with tabs enabled, the forms navigator and the forms windows will continue to open in a new window and not in a new tab. This is intended functionality and is not a bug.

Personal Homepage Setting
The ICX 'Personal Homepage' setting is not supported with the Firefox browser.

Rich Text Editing
The Cut, Copy and Paste buttons within the Rich text Editor on Oracle Applications Framework do not work by default when using a Firefox browser. This is due to a security feature within Firefox. We recommend that the keyboard shortcut keys, which do still work by default are used for this functionality. If you still wish to use the buttons, this can be enabled by editing the users Firefox preference file. Further information is available at, http://www.mozilla.org/editor/midasdemo and http://www.mozilla.org/editor/midasdemo/securityprefs.html.

BIDI Language Users
BIDI Languages are not supported with Self Service Applications using the Firefox Browser.

Oracle Report Manager
Oracle Report Manager interaction with Excel will not work when using the Firefox browser. This functionality requires the interaction of ActiveX through VbScript which is not supported in Firefox. Oracle Report Manager users should run Internet Explorer for full functionality. Full support through Firefox is being investigated through enhancement request 7832639 titled, 'Support downloading of FSG reports and templates in excel for Firefox browser'.

Windows Vista with Firefox
Windows Vista and Windows 7 with Firefox
Balanced Scorecard Users
The VB client is not supported on Windows Vista or Windows 7.

Discoverer Users
Discoverer 10.1.2.3 is certified on Windows Vista. For further information please see note 456426.1.

Discoverer 10.1.2.2 and earlier are not certified on Windows Vista or Windows 7.

Financial Analyzer and Sales Analyzer Users
Financial Analyzer and Sales Analyzer client versions (6.4) are not supported on Windows Vista or Windows 7. Please use the OFA and OSA web versions, see note 470992.1.

XML Reports (RTF file extensions)
Windows Vista and Windows 7 users cannot open *.rtf format files through the browser. When clicking the 'OK' button on the 'Opening *.rtf' modal window the file will not open and the modal window will come up again. To correct the problem, associate a different program such as Wordpad, OpenOffice.org etc. with the .rtf extension on the desktop.

Control Panel -> Default Programs -> Associate a file type or protocol with a program
Select .rtf under the Name column from the list
Click the 'Change Program' button.
Select an appropriate program i.e. Wordpad
Click the 'OK' button
Section 4: Safari for Mac Users
Certification Matrix for Safari Browser
The table below outlines the currently certified Browser, Operating System and the certified JRE versions.

Browser Version OS X v10.4.7 or higher OS X v10.5 or higher
Safari 2.0.x (where x = 4 or higher) JRE 1.5.0_06 and higher n/a
Safari 3.2.x (where x = 1 or higher) JRE 1.5.0_13 and higher JRE 1.5.0_13 and higher

For further information and patch requirements for Apple Macintosh OS X version 10.4, please see Document id: 402138.1, titled 'Oracle Applications Release Notes Release 12 for Apple Macintosh OS X version 10.4'.

For further information and patch requirements for Apple Macintosh OS X version 10.5, please see Document id: 864552.1, titled 'Oracle Applications Release Notes Release 12 for Apple Macintosh OS X version 10.5'.



Recommended Safari Browser Settings
Performance
From the Safari Menu, go to 'Preferences -> Security -> Web Content' and select; 'Enable Plug-ins', 'Enable Java' and 'Enable JavaScript'. Do not select 'Block Pop-Up Windows'. (Selecting this will cause the Oracle E-Business Suite not to open).

From the Safari Menu go to 'Preferences -> Advanced' and select 'Press Tab to highlight each item on a webpage'.

Related Notes
Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite Release 12 (Note 393931.1)
Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite 11i (Note 290807.1)
Recommended Browsers for Oracle E-Business Suite 11i (Note 285218.1)
Change Log
Date Description
Jan 21, 2010 Added Firefox 3.6 as a certified browser.
Dec 22, 2009 Added multibyte language support for Windows 7 desktop client operating system.
Dec 17, 2009 Added Windows 7 as a certified desktop client operating system.
Sep 18, 2009 Added Firefox 3.5 as a certified browser.
Sep 11, 2009 Added Internet Explorer 8 certification with Oracle E-Business Suite R12. In particular please see Prerequisite Patch Requirements and Known Issues for Internet Explorer Users
Aug 3, 2009 Added Safari 3.2.1 with OS X v10.5 certification with Oracle E-Business Suite R12.
Jun 26, 2009 Added Windows Vista SP2 as a certified patchset.
Jun 12, 2009 Removed FF 2.0 information.
May 1, 2009 Added Oracle E-Business Suite 12.1.1 information.
Feb 27, 2009 Added Firefox 3.0.x as a certified browser.
Jul 24, 2008 Added Vista SP1.
Jun 6, 2008 Added information for using multiple jre plug-in versions in Firefox known issues section.
May 16, 2008 Added certification of Windows XP SP3.
Jan 24 , 2007 Initial document created.

Database Initialization Parameters for Oracle Applications Release 12

Database Initialization Parameters for Oracle Applications Release 12 [ID 396009.1]

--------------------------------------------------------------------------------

Modified 14-APR-2010 Type WHITE PAPER Status PUBLISHED

This document describes the database initialization parameter settings required for Oracle E-Business Suite Release 12.

In This Document
Section 1: Common Database Initialization Parameters For All Releases
Section 2: Release-Specific Database Initialization Parameters For Oracle 10g Release 2
Section 3: Release-Specific Database Initialization Parameters For Oracle 11g Release 1
Section 4: Release-Specific Database Initialization Parameters For Oracle 11g Release 2
Section 5: Using System Managed Undo (SMU)
Section 6: Temporary Tablespace Setup
Section 7: Database Initialization Parameter Sizing
The most current version of this document can be obtained in My Oracle Support Knowledge Document 396009.1.

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

Key Points
The document consists of a common section, which provides a common set of database initialization parameters used for all releases of the Oracle Database, followed by several release-specific sections, which list parameters and settings required for a particular release of the Oracle Database.
Put together, the parameters from the common section and appropriate release-specific section formulate a complete set of database initialization parameters.
Parameters may appear on a removal list either because they are obsolete, or because the default value is required and no other value may be set.
In the various parameter lists, check for comments giving any platform-specific exceptions. Such comments will apply only to the exact platform mentioned: for example, a reference to HP-UX (PA-RISC) will not apply to HP-UX (Itanium IA-64).
The "X" notation used in the release-specific section denotes all patchset releases within that major version. For example, "10.2.0.X" refers to all releases of 10.2.0, such as 10.2.0.2 and 10.2.0.3.
Oracle E-Business Suite Release 12 requires Oracle Database 10g Release 2 (10.2.0.2) Enterprise Edition as a minimum release level and edition. No earlier releases, or other editions of any release, may be used.
Section 1: Common Database Initialization Parameters For All Releases
This section lists the database initialization parameters that are common across releases of the Oracle Database. You should refer to it in conjunction with the relevant release-specific section.

Note: All parameters listed in this section should be set as stated, unless your particular release-specific section instructs otherwise.

The parameter values provided in this document reflect a small instance configuration (see Section 7). You should adjust the relevant parameters based on the number of active Oracle E-Business Suite users. In addition, you should investigate any parameters that are set but not mentioned in this note.

##############################################################################
#
# Oracle E-Business Suite Release 12
# Common Database Initialization Parameters
#
# The following represents the common database initialization
# parameters file for Oracle E-Business Suite Release 12.
# Release-specific parameters are included in the respective release
# section. The release-specific parameters should be appended to the
# common database initialization parameter file.
#
# There are numerous mandatory database initialization parameters.
# Their settings must not be altered. The use of values other than
# those provided in this document will not be supported unless Oracle
# Support has specifically instructed you to alter these parameters
# from their mandatory settings.
#
# Mandatory parameters are denoted with the (MP) symbol as a
# comment. This includes parameters such as NLS and optimizer
# related parameters.
#
# The remaining (non-mandatory) parameters relate to either sizing or
# configuration requirements that are specific to customer environments
# or system capacity. A sizing table provides recommendations and
# guidelines based on the number of deployed and active Oracle E-Business Suite
# users. Customers can adjust these parameters as per their
# environment and system resource capacity.
#
##############################################################################


##########
#
# Database identification parameters
#
# The database identification parameters define the name of the
# database and the names of the database control files.
#
# The database name is established when the database is built, and
# for most customers it matches the instance name. It should not
# normally be necessary to change the database name, except for
# the purposes of database cloning.
#
# There should be at least two control files, preferably three,
# located on different volumes in case one of the volumes fails.
# Control files can expand, hence you should allow at least 20M
# per file for growth.
#
#########

db_name = prodr12
control_files = ('/disk1/prodr12_DB/cntrlprodr12_1.dbf',
'/disk2/prodr12_DB/cntrlprodr12_2.dbf',
'/disk3/prodr12_DB/cntrlprodr12_3.dbf')


#########
#
# Database block size parameter
#
# The required block size for Oracle E-Business Suite is 8K. No other value may be used.
#
#########

db_block_size = 8192 (#MP)


#########
#
# Compatibility parameter
#
# See the appropriate release-specific section of this document for details of setting compatibility.
#
#########


#########
#
# _system_trig_enabled
#
# The _system_trig_enabled parameter must be set to TRUE.
# If _system_trig_enabled parameter is set to FALSE it will
# prevent system triggers from being executed.
#
#########

_system_trig_enabled = true (#MP)


#########
#
# o7_dictionary_accessibility parameter
#
# This parameter must be set to FALSE for Oracle E-Business Suite Release 12.
#
########

o7_dictionary_accessibility = FALSE (#MP)


#########
#
# NLS and character set parameters
#
# Some NLS parameter values are marked as being mandatory settings.
# These are the only supported settings for these parameters for
# Oracle E-Business Suite Release 12. They must not be changed to other values.
# Other NLS parameters have been given default values, which can
# be changed as required.
#
#########

nls_language = american
nls_territory = america
nls_date_format = DD-MON-RR (#MP)
nls_numeric_characters = ".,"
nls_sort = binary (#MP)
nls_comp = binary (#MP)
nls_length_semantics = BYTE (#MP)


#########
#
# Multi-Threaded Server (MTS) parameters
#
# Most Oracle E-Business Suite customers do not need to use MTS,
# and the default configuration disables MTS.
#
# If MTS is used, it can have a dramatic effect on the SGA, as
# session memory, including sort and cursor areas, resides in the
# SGA.
#
#########


#########
#
# Auditing parameter
#
# There is a performance overhead for enabling the audit_trail
# parameter. In addition, the database administrator will need
# to implement a purge policy for the SYS.AUD$ table.
#
# Statement-level auditing should not be used.
#
#########

#audit_trail = true # Uncomment if you want to enable audit_trail.


########
#
# Dump parameters
#
# The main dump parameters specify the location of the trace and core
# files, and will normally point to the appropriate trace directories.
# The max_dump_file_size parameter can be used to specify the maximum
# size of a dump file, to prevent a trace file using an excessive
# amount of disk space. (This can also be changed at session level.)
#
########

user_dump_dest = /ebiz/prodr12/udump
background_dump_dest = /ebiz/prodr12/bdump
core_dump_dest = /ebiz/prodr12/cdump
max_dump_file_size = 20480 #Limit default trace file size to 10 MB.


########
#
# Timed statistics
#
# On most platforms, enabling timed statistics has minimal effect
# on performance. It can be enabled or disabled dynamically at
# both system and session level.
#
# Timed statistics is required for use of SQL Trace and Statspack.
#
########
#
timed_statistics = true


########
# Trace file accessibility parameter
#
# As the database machine should be in a secure environment,
# setting this parameter to TRUE is recommended in order to
# facilitate trace file analysis.
#
########

_trace_files_public = TRUE


#########
#
# Processes and sessions parameters
#
# A database process can be associated with one or more database
# sessions. For all technology stack components other than Oracle
# Forms, there is a one-to-one mapping between sessions and processes.
#
# For Forms processes, there will be one database session per
# open form, with a minimum of two sessions per Forms user (one
# for the navigator form, and one for the active form).
#
# The sessions parameter should be set to twice the value of the
# processes parameter.
#
#########

processes = 200 # Max. no. of users.
sessions = 400 # 2 x no. of processes.
db_files = 512 # Max. no. of database files.
dml_locks = 10000 # Database locks.


########
#
# Cursor-related parameters
#
########

cursor_sharing = EXACT (#MP)
open_cursors = 600
session_cached_cursors = 500


########
#
# Cache parameters
#
# For Oracle 10g and 11g, the automatic SGA tuning option (sga_target)
# is required. This avoids the need for individual tuning of the different
# caches, such as the buffer cache, shared pool, and large pool. Use
# of the automatic SGA tuning option also improves manageability and
# overall performance.
#
# sga_target refers to the total size of the SGA. This includes
# all the sub-caches, such as the buffer cache, log buffer,
# shared pool, and large pool. The sizing table in the
# section Database Initialization Parameter Sizing contains
# sizing recommendations for sga_target.
#
# # When the automatic SGA tuning option is used to dynamically size
# the individual caches, it is recommended to use a Server Parameter
# file (SPFILE) to store the initialization parameter values.
# Using an SPFILE allows the dynamically-adjusted values to persist
# across restarts. Refer to the Oracle Database Administrator's
# Guide for information on how to create and maintain an SPFILE.

sga_target = 2G
db_block_checking = FALSE
db_block_checksum = TRUE


########
#
# Log Writer parameters
#
# The log writer parameters control the size of the log buffer
# within the SGA, and how frequently the redo logs are checkpointed
# (when all dirty buffers written to disk and a new recovery point
# is created).
#
# A size of 10MB for the log buffer is a reasonable value for
# Oracle E-Business Suite. This represents a balance between
# concurrent programs and online users. The value of log_buffer
# must be a multiple of redo block size (normally 512 bytes).
#
# The checkpoint interval and timeout control the frequency of
# checkpoints.
#
########

log_checkpoint_timeout = 1200 # Checkpoint at least every 20 mins.
log_checkpoint_interval = 100000
log_buffer = 10485760
log_checkpoints_to_alert = TRUE


#########
#
# Shared pool parameters
#
# The shared pool should be tuned to minimize contention for SQL
# and PL/SQL objects. For Release 12, a reasonable starting point
# is a size of 600M and a 60M reserved area (10%).
#
########

shared_pool_size = 600M
shared_pool_reserved_size = 60M
_shared_pool_reserved_min_alloc = 4100


########
#
# cursor_space_for_time parameter
#
# Cursor space for time is an optimization which essentially
# results in holding pins on cursors and their associated
# frames/buffers for longer periods of time. The pins are held
# until the cursor is closed, instead of at the end-of-fetch
# (normal behavior). This reduces library cache pin traffic
# which reduces library cache latch gets. Cursor space for time
# is useful for large Oracle E-Business Suite environments whereby library
# cache latch contention, specifically due to pin gets, is an
# issue in terms of performance.
#
# Cursor space for time requires at least a 50% increase in the
# size of the shared pool because of the frames/buffers. If AWR
# or Statspack reports show that the waits for library cache latch
# gets are significant, and the latch gets are due to pin
# requests, then cursor space for time can be used to improve
# performance.
#
# It is important to note that library cache latch contention can
# be caused by numerous different factors, including the use of
# non-sharable SQL (i.e. literals), lack of space, frequent
# loads/unloads, invalidation, patching, gathering statistics
# frequently and during peak periods, and pin requests.
# Cursor space for time is designed to optimize the pin requests
# only, and will not reduce latch contention for other issues.
#
########

# cursor_space_for_time = FALSE # Disabled by default.


#########
#
# PL/SQL parameters
#
# The utl_file_dir parameter must be set as:
# utl_file_dir = ;gt; ...
#
########

utl_file_dir = /ebiz/prodr12/utl_file_dir


########
#
# Advanced Queuing (AQ) and Job Queue parameters
#
# AQ requires the TM process to handle delayed messages. A number
# of Application modules use AQ, including Workflow. Job Queues
# enable advanced queue to submit background jobs.
#
# Starting from 10gR1, aq_tm_processes is auto-tuned and no longer
# required. Omitting this parameter has not, however, been tested with
# Oracle E-Business Suite. For good performance, the minimum required
# value is 1. This can be changed to meet customer needs. For example,
# a value of 2 can help resolve lengthy queues.
#
# job_queue_processes should typically be be set to a value of 2 for
# optimal performance. However, the value can be tuned to meet the
# specific requirements of the Workflow module and customer needs,
# based on the number of job queue processes needed to handle AQ
# event messages and for Workflow notification mailers.
#
########

aq_tm_processes = 1
job_queue_processes = 2


########
#
# Archiving parameters
#
# Archiving parameters, including destination (optionally,
# multiple destinations in 10gR2 or 11g) may be specified.
#
########

# log_archive_start = true # Uncomment if you want automatic archiving.


########
#
# Parallel execution parameters
#
# Parallel execution is used by some Oracle E-Business Suite concurrent programs,
# including DBI programs and Gathering Statistics. AD will also use parallel
# execution when creating large indexes.
#
########

parallel_max_servers = 8 # Max. value should be 2 x no. of CPUs.
parallel_min_servers = 0


########
#
# Events parameters
#
# Events should only be set when explicitly requested by Oracle Support or Development.
# Refer to the appropriate release-specific section for events that may be set.
#
########


#########
#
# Optimizer parameters
#
# The following optimizer parameters must be set as below, and may
# not be changed. No other values are supported.
#
# Refer also to the release-specific section for any additional
# optimizer parameters which must be set.
#
#########

_sort_elimination_cost_ratio =5 (#MP)
_like_with_bind_as_equality = TRUE (#MP)
_fast_full_scan_enabled = FALSE (#MP)
_b_tree_bitmap_plans = FALSE (#MP)
optimizer_secure_view_merging = FALSE (#MP)
_sqlexec_progression_cost = 2147483647 (#MP)


#########
#
# Oracle Real Application Clusters (Oracle RAC) parameters
#
# The following Oracle RAC related parameters should be set when running
# E-Business Suite in an Oracle RAC environment.
#
#########

max_commit_propagation_delay = 0 (#MP)
cluster_database = TRUE (#MP)


#########
#
# Parallel Execution and Oracle RAC parameters
#
# It is recommended to set the parameters instance_groups and
# parallel_instance_group on each instance, to ensure that parallel
# requests do not span instances.
# For example, on instance1, set instance_groups=apps1 and
# parallel_instance_group=apps1. On instance2, set
# instance_groups=apps2 and parallel_instance_group=apps2, and so on.
#
#########


#########
#
Private memory area parameters
#
# The automatic memory manager is used to manage the PGA memory. This
# avoids the need to manually tune the settings of sort_area_size and
# hash_area_size.
# The automatic memory manager also improves performance and scalability,
# as memory is released back to the operating system.
#
#########

pga_aggregate_target = 1G
workarea_size_policy = AUTO (#MP)
olap_page_pool_size = 4194304


###############################################################################
#
# End of Common Database Initialization Parameters Section
#
###############################################################################

Section 2: Release-Specific Database Initialization Parameters For Oracle 10g Release 2
This section discusses database initialization parameters and specific releases of Oracle Database 10g Release 2, first describing required parameters, then listing any parameters that should not be used.

2.1 Required Parameters
The following list describes database initialization parameters required for this specific release of the Oracle Database. These parameters should be added to the common database initialization parameters provided in Section 1, so that the final database initialization parameters file includes the common section plus the contents of this release-specific section.

#############################################################################
#
# Oracle E-Business Suite Release 12
# Release-Specific Database Initialization Parameters for 10gR2
#
#############################################################################

#########
#
# Compatibility parameter
#
# Compatibility should be set to the current release.
#
##########

compatible = 10.2.0 (#MP)


#########
#
# System-managed undo parameters
#
# Oracle E-Business Suite Release 12 requires the use of system managed undo.
# This is much more efficient than rollback segments, and reduces the chances
# of snapshot too old errors. In addition, it is much easier to manage and
# administer system managed undo than manually managing rollback segments.
#
########

undo_management = AUTO (#MP)
undo_tablespace = APPS_UNDOTS1


#########
#
# PL/SQL parameters
#
# The following parameters are used to enable the PL/SQL global
# optimizer as well as native compilation.
#
# PL/SQL native compilation is recommended for Oracle Database 10g-based
# Oracle E-Business Suite environments such as Release 12. Interpreted mode is supported,
# and can be used with Oracle E-Business Suite. However, native compilation is
# recommended in order to maximize runtime performance and scalability.
# Compiling PL/SQL units with native compilation takes longer than using
# interpreted mode, because of the need to generate and compile the native
# shared libraries.
#
#########

plsql_optimize_level = 2 (#MP)
plsql_code_type = native
plsql_native_library_dir = /ebiz/prodr12/plsql_nativelib
plsql_native_library_subdir_count = 149


#########
#
# Other parameters
#
# _kks_use_mutex_pin
#
# 10gR2 facilitates the use of mutexes to lock resources in a lightweight
# fashion with higher granularity.
#
# On the HP-UX (PA-RISC) platform only, this parameter must be set to FALSE if using 10gR2.
#
#########

_kks_use_mutex_pin=FALSE # Set to FALSE on HP-UX (PA-RISC) only; otherwise, remove this parameter.


###############################################################################
#
# End of Release-Specific Database Initialization Parameters Section for 10gR2
#
###############################################################################

2.2 Parameter Removal List for Oracle Database 10g Release 2
If they exist, you should remove the following parameters from your database initialization parameters file for Oracle Database 10g Release 2.

_always_anti_join
_always_semi_join
_complex_view_merging
_index_join_enabled
_kks_use_mutex_pin # Unless using HP-UX (PA-RISC) - see "Other parameters" section above.
_new_initial_join_orders
_optimizer_cost_based_transformation
_optimizer_cost_model
_optimizer_mode_force
_optimizer_undo_changes
_or_expand_nvl_predicate
_ordered_nested_loop
_push_join_predicate
_push_join_union_view
_shared_pool_reserved_min_alloc
_sortmerge_inequality_join_off
_table_scan_cost_plus_one
_unnest_subquery
_use_column_stats_for_function
always_anti_join
always_semi_join
db_block_buffers
db_file_multiblock_read_count
db_cache_size
enqueue_resources
event="10932 trace name context level 32768"
event="10933 trace name context level 512"
event="10943 trace name context forever, level 2"
event="10943 trace name context level 16384"
event="38004 trace name context forever, level 1"
hash_area_size
java_pool_size
job_queue_interval
large_pool_size
max_enabled_roles
optimizer_dynamic_sampling
optimizer_features_enable
optimizer_index_caching
optimizer_index_cost_adj
optimizer_max_permutations
optimizer_mode
optimizer_percent_parallel
plsql_compiler_flags
query_rewrite_enabled
row_locking
sort_area_size
undo_retention
undo_suppress_errors
Section 3: Release-Specific Database Initialization Parameters for Oracle 11g Release 1
3.1 Required Parameters
The following list describes database initialization parameters required for this specific release of the Oracle Database. These parameters should be added to the common database initialization parameters provided in Section 1, so that the final database initialization parameters file includes the common section plus the contents of this release-specific section.

####################################################################
#
# Oracle E-Business Suite Release 12
# Release-Specific Database Initialization Parameters for 11gR1
#
####################################################################

#########
#
# Compatible
#
# Set compatibility to the current release.
#
#########

compatible = 11.1.0


#######
#
# Diagnostic Parameters
#
# As of Oracle Database 11g Release 1, the diagnostics for each database
# instance are located in a dedicated directory that can be specified
# via the DIAGNOSTIC_DEST initialization parameter. The format of
# the directory specified by DIAGNOSTIC_DEST is as follows:
#
#
# Diagnostic files are located in their own subdirectories of the
# DIAGNOSTIC_DEST directory, according to type:
#
# Trace files - /diag/rdbms///trace
# Alert logs - /diag/rdbms///alert
# Core files - /diag/rdbms///cdumd
# Incident dump files - /diag/rdbms///incident/

diagnostic_dest = ?/prod12

# System-Managed Undo Parameters
#
# Oracle E-Business Suite requires the use of System Managed Undo (SMU).
# This is more efficient than manually managed rollback segments,
# and reduces the chances of "snapshot too old" errors. It is also
# easier to manage SMU than the rollback segments it replaces.
#
# ########

undo_management=AUTO (#MP)
undo_tablespace=APPS_UNDOTS1


#########
# PL/SQL parameters
#
# The following parameters are used to enable the PL/SQL global
# optimizer as well as native compilation.
#
# PL/SQL native compilation is recommended for Oracle Database 10g or 11g based
# Oracle E-Business Suite environments such as Release 12. Interpreted mode is supported,
# and can be used with Oracle E-Business Suite. However, native compilation is
# recommended in order to maximize runtime performance and scalability.
# Compiling PL/SQL units with native compilation takes longer than using
# interpreted mode, because of the need to generate and compile the native
# shared libraries.
#
# If native compilation is to be used, uncomment the plsql_code_type = NATIVE
# line below. Note that in 11g, the parameters plsql_native_library_dir and
# plsql_native_library_subdir_count have no effect and are not needed, as
# natively compiled code is now stored in the database, not a filesystem.
#
##########

#plsql_code_type = NATIVE #Uncomment if you want to use NATIVE compilation.


#########
#
# Optimizer Parameters
#
# Release 12 uses the Cost Based Optimizer (CBO). The following optimizer
# parameters must be set as shown, and should not be changed.
#
#########

_optimizer_autostats_job=false (#MP) Turn off automatic statistics.


#########
#
# Database Password Case Sensitivity
#
# Oracle E-Business Suite does not currently integrate with this feature,
# so the parameter must be set to FALSE.
#
#########

sec_case_sensitive_logon = FALSE (#MP)


###############################################################################
#
# End of Release-Specific Database Initialization Parameters Section for 11gR1
#
###############################################################################


3.2 Parameter Removal List for Oracle Database 11g Release 1
If they exist, you should remove the following parameters from your database initialization parameters file for Oracle Database 11g Release 1 (11.1.X).

_always_anti_join
_always_semi_join
_complex_view_merging
_index_join_enabled
_kks_use_mutex_pin
_new_initial_join_orders
_optimizer_cost_based_transformation
_optimizer_cost_model
_optimizer_mode_force
_optimizer_undo_changes
_or_expand_nvl_predicate
_ordered_nested_loop
_push_join_predicate
_push_join_union_view
_shared_pool_reserved_min_alloc
_sortmerge_inequality_join_off
_sqlexec_progression_cost
_table_scan_cost_plus_one
_unnest_subquery
_use_column_stats_for_function
always_anti_join
always_semi_join
background_dump_dest
core_dump_dest
db_block_buffers
db_cache_size
db_file_multiblock_read_count
enqueue_resources
event="10932 trace name context level 32768"
event="10933 trace name context level 512"
event="10943 trace name context forever, level 2"
event="10943 trace name context level 16384"
event="38004 trace name context forever, level 1"
hash_area_size
java_pool_size
job_queue_interval
large_pool_size
max_enabled_roles
nls_language
optimizer_dynamic_sampling
optimizer_features_enable
optimizer_index_caching
optimizer_index_cost_adj
optimizer_max_permutations
optimizer_mode
optimizer_percent_parallel
plsql_compiler_flags
plsql_native_library_dir
plsql_native_library_subdir_count
plsql_optimize_level
query_rewrite_enabled
rollback_segments
row_locking
sort_area_size
sql_trace
timed_statistics
undo_retention
undo_suppress_errors
user_dump_dest
Section 4: Release-Specific Database Initialization Parameters for Oracle 11g Release 2
4.1 Required Parameters
The following list describes database initialization parameters required for this specific release of the Oracle Database. These parameters should be added to the common database initialization parameters provided in Section 1, so that the final database initialization parameters file includes the common section plus the contents of this release-specific section.

####################################################################
#
# Oracle E-Business Suite Release 12
# Release-Specific Database Initialization Parameters for 11gR2
#
####################################################################

#########
#
# Compatible
#
# Compatibility should be set to the current release.
#
#########

compatible = 11.2.0


#######
#
# Diagnostic Parameters
#
# As of Oracle Database 11g Release 1, the diagnostics for each database
# instance are located in a dedicated directory that can be specified
# via the DIAGNOSTIC_DEST initialization parameter. The format of
# the directory specified by DIAGNOSTIC_DEST is as follows:
#
# /diag/rdbms//
#
# Diagnostic files are located in their own subdirectories of the
# DIAGNOSTIC_DEST directory, according to type:
#
# Trace files - /diag/rdbms///trace
# Alert logs - /diag/rdbms///alert
# Core files - /diag/rdbms///cdumd
# Incident dump files - /diag/rdbms///incident/

diagnostic_dest = ?/prod12


#########
#
# System-Managed Undo Parameters
#
# Oracle E-Business Suite requires the use of System Managed Undo (SMU).
# This is more efficient than manually managed rollback segments,
# and reduces the chances of "snapshot too old" errors. It is also
# easier to manage SMU than the rollback segments it replaces.

# ########

undo_management=AUTO (#MP)
undo_tablespace=APPS_UNDOTS1


#########
# PL/SQL parameters
#
# The following parameters are used to enable the PL/SQL global
# optimizer as well as native compilation.
#
# PL/SQL native compilation is recommended for Oracle Database 10g or 11g based
# Oracle E-Business Suite environments such as Release 12. Interpreted mode is supported,
# and can be used with Oracle E-Business Suite. However, native compilation is
# recommended in order to maximize runtime performance and scalability.
# Compiling PL/SQL units with native compilation takes longer than using
# interpreted mode, because of the need to generate and compile the native
# shared libraries.
#
# If native compilation is to be used, uncomment the plsql_code_type = NATIVE
# line below. Note that in 11g, the parameters plsql_native_library_dir and
# plsql_native_library_subdir_count have no effect and are are not needed, as
# natively compiled code is now stored in the database, not a filesystem.
#
#########

#plsql_code_type = NATIVE #Uncomment if you want to use NATIVE compilation.


#########
#
# Optimizer Parameters
#
# Release 12 uses cost based optimization. The following optimizer
# parameters must be set as shown, and should not be changed.
#
#########

_optimizer_autostats_job=false (#MP) Turn off automatic statistics.


#########
#
# Database Password Case Sensitivity
#
# Oracle E-Business Suite does not currently integrate with this feature,
# so the parameter must be set to FALSE.
#
#########

sec_case_sensitive_logon = FALSE (#MP)


###############################################################################
#
# End of Release-Specific Database Initialization Parameters Section for 11gR2
#
###############################################################################

4.2 Parameter Removal List for Oracle Database 11g Release 2
If they exist, you should remove the following parameters from your database initialization parameters file for Oracle Database 11g Release 2 (11.2.X).

_always_anti_join
_always_semi_join
_complex_view_merging
_index_join_enabled
_kks_use_mutex_pin
_new_initial_join_orders
_optimizer_cost_based_transformation
_optimizer_cost_model
_optimizer_mode_force
_optimizer_undo_changes
_or_expand_nvl_predicate
_ordered_nested_loop
_push_join_predicate
_push_join_union_view
_shared_pool_reserved_min_alloc
_sortmerge_inequality_join_off
_sqlexec_progression_cost
_table_scan_cost_plus_one
_unnest_subquery
_use_column_stats_for_function
always_anti_join
always_semi_join
background_dump_dest
core_dump_dest
db_block_buffers
db_cache_size
db_file_multiblock_read_count
DRS_START
enqueue_resources
event="10932 trace name context level 32768"
event="10933 trace name context level 512"
event="10943 trace name context forever, level 2"
event="10943 trace name context level 16384"
event="38004 trace name context forever, level 1"
hash_area_size
java_pool_size
job_queue_interval
large_pool_size
max_enabled_roles
nls_language
optimizer_dynamic_sampling
optimizer_features_enable
optimizer_index_caching
optimizer_index_cost_adj
optimizer_max_permutations
optimizer_mode
optimizer_percent_parallel
plsql_compiler_flags
plsql_native_library_dir
plsql_native_library_subdir_count
plsql_optimize_level
query_rewrite_enabled
rollback_segments
row_locking
sort_area_size
sql_trace
SQL_VERSION
timed_statistics
undo_retention
undo_suppress_errors
user_dump_dest
Section 5: Using System Managed Undo (SMU)
As mentioned for the parameters related to system undo, the database releases certified for use with Oracle E-Business Suite Release 12 only support the use of system managed undo (SMU). SMU is more efficient than traditional rollback segments and reduces the possibility of snapshot too old (ORA-1555) errors.

Note the following points about the undo_retention parameter:

The values given for undo_retention are for guidance only. This parameter should be adjusted according to the elapse times of the concurrent jobs, and corresponding commit windows.
There is no need to specify a value for undo_retention on Oracle 10g or 11g based systems, because it is set automatically as part of automatic undo tuning.
This parameter may be safely removed if you are using a value of 900 or less.
Setting this parameter to a value higher than 900 (the default) is recommended if you experience "ORA-1555: Snapshot too old" errors.
Automatic undo is not supported for LOBS.
Section 6: Temporary Tablespace Setup
It is recommended that the temporary tablespace for Oracle E-Business Suite users be created using locally managed temp files with uniform extent sizes of 128K. The 128K extent size is recommended because numerous modules, such as Pricing and Planning, make extensive use of global temporary tables which also reside in the temporary tablespace. Since each user instantiates a temporary segment for these tables, large extent sizes may result in space allocation failures.

The following is an example of creating a locally managed temporary tablespace with temp files:

SQL> drop tablespace temp;
SQL> create temporary tablespace temp
tempfile '/d2/prodr12/dbf/temp01.dbf' size 2000M reuse
extent management local
uniform size 128K;
Section 7: Database Initialization Parameter Sizing
This section provides sizing recommendations based on the active Oracle E-Business Suite user counts. The following table should be used to size the relevant parameters:

Parameter Name Development or Test Instance 11-100 Users 101-500 Users 501-1000 Users 1001-2000 Users
processes 200 200 800 1200 2500
sessions 400 400 1600 2400 5000
sga_target Footnote 1 1G 1G 2G 3G 14G
shared_pool_size (csp) N/A N/A N/A 1800M 3000M
shared_pool_reserved_size (csp) N/A N/A N/A 180M 300M
shared_pool_size (no csp) 400M 600M 800M 1000M 2000M
shared_pool_reserved_size (no csp) 40M 60M 80M 100M 100M
pga_aggregate_target 1G 2G 4G 10G 20G
Total Memory Required Footnote 2 ~ 2 GB ~ 3 GB ~ 6 GB ~ 13 GB ~ 25 GB

Specific Notes on Table
Footnote 1 The parameter sga_target should be used for Oracle 10g or 11g based environments such as Release 12. This replaces the parameter db_cache_size, which was used in Oracle i based environments. Also, it is not necessary to set the parameter undo_retention for 10g or 11g-based systems, since undo retention is set automatically as part of automatic undo tuning.


Footnote 2 The total memory required refers to the amount of memory required for the database instance and associated memory, including the SGA and the PGA. You should ensure that your system has sufficient available memory in order to support the values provided above. The values provided above should be adjusted based on available memory so as to prevent paging and swapping.
General Notes on Table
"Development or Test instance" refers to a small instance used only for development or testing, with no more than 10 users.


The range of user counts provided above refers to active Oracle E-Business Suite users, not total or named users. For example, if you plan to support a maximum of 500 active Oracle E-Business Suite users, then you should use the sizing as per the range 101-500 users.


The parameter values provided in this document reflect a small instance configuration, and you should adjust the relevant parameters based on the Oracle E-Business Suite user counts as listed in the table above.

The "csp" and "no csp" options of the shared pool parameters refer to the use of cursor_space_for_time, which is documented in the common database initialization parameters section.


Note: Enabling cursor_space_for_time can result in significantly larger shared pool requirements.

Change Log