EBS Database Parameter Settings Analyzer

All Oracle Apps DBA must have referred below Note id at least once in their career. Most of us refer it  during installation and upgrade of Oracle EBS
application to verify if we have right set if database parameters defined for the optimum performance of EBS application.

Database Initialization Parameters for Oracle E-Business Suite Release 12 (Doc ID 396009.1)

This document has all the required database parameters which are common to all the database release and which are required by EBS application. It also contains release specific database initialization parameters for different releases like 10g, 11g, 12c etc.

Above Note id was always very useful but it required a bit of manual work to compare all the parameters. Oracle has now created another Analyzer tool which makes it much easier to verify if you have the EBS required set of database parameters or not.

EBS Database Parameter Settings Analyzer (Doc ID 1953468.1)

Important points regarding this analyzer tool:

• Just like so many other EBS analyzer, this analyzer tool can also be run as standalone SQL or run as concurrent program.
• This is a non-invasive script – the Analyzer does not perform any INSERTs, UPDATEs or DELETEs to your data; it just reports on it so you can run safely on your production instance.
• This analyzer script is fully compliant with the Historical DOC ID 396009.1. Actually this analyzer provides recommended value of database initialization parameter settings based on that note id only.
• It provides many useful information like details of mandatory parameters which does not exists on your database or the parameter names which should be removed from your database.
• The report is generated in an easy to read HTML format. Report will be named as db_param_analyzer.html and will get generated in same directory from where you executed it. If you run it via concurrent program then it will get saved in $APPLCSF/$APPLOUT.
• This tool only requires one input parameter which is:  Number of possible active users. This parameter is Optional also. You can choose to enter the number of possible active users, or click “Enter” to skip. If you specify 0 or skip to enter this parameter, this script will get the number of active users from fnd_user table who have logged on EBS in last 30 days.

Running the Analyzer via SQL*Plus is a simple process

Example:

$ sqlplus apps/<apps_password>
SQL>@db_param_analyzer.sql
Enter the number of active users: <Enter the value>

For details on running it as concurrent program refer to Note ID 1953468.1

Sample Report

Below is how this report show up: