Oracle Database Licensing challenges depend largely on the installation or use of the various Enterprise Edition options and management packs.
Provided below is a brief understanding of installing Oracle database, its implications on licensing and a few tasks to manage post-installation.
There are generally two modes of installation of Oracle database:
In Interactive Installation, the Oracle Universal Installer allows you to specify the information needed to install and configure a database. In the Database Enterprise Edition, in case the ‘Select Options’ route is not used, the installer chooses automatically the most commonly used options.
In the Automated Installation Methods Using Response Files, you can automate the installation by creating & pointing to a response file. This is useful when you need to make multiple installations.
From a licensing perspective it is important to note that, in either of the two methods, the installer will install licensable database options and management tools. There is also a component list that can be used to enable or disable certain options.
Oracle has provided for multiple post-installation tasks to be carried out after the initial installation of the database. Most of these tasks have to do with downloading & applying patches, creating backups, creating additional operating system accounts, setting environment variables, or upgrading the database.
Apart from the above, from a licensing perspective, the most important post-installation tasks are to do with enabling and disabling options & management packs.
Use Oracle’s ‘chopt’ tool
The chopt tool is a command-line utility that helps enable or disable certain options.
Using the chopt tool you can disable the following options:
Oracle Partitioning
Oracle Database Vault
Oracle Real Application Testing
Oracle Label Security
Oracle Data Mining
OLAP
Given below is an example of how to disable using the chopt utility:
oracle> chopt disable dv
oracle> chopt disable olap
Important Note regarding the chopt utility: This utility is available only from Oracle 11gR2 onwards.
The parameter can be set to the following values:
NONE – Neither pack is licensed or used.
DIAGNOSTIC – Only the DIAGNOSTIC pack is available.
DIAGNOSTIC+TUNING – Both packs are available.
Note: Diagnostic + Tuning is the default value. So, if you have not set the parameter, you will be paying for the packs.
2. The Diagnostic Pack gets enabled in case you are running AWR (apart from many other command line interfaces). Luckily, Oracle has given a script to remove all of AWR.
You can use this script (dbms_awr.plb) available in the Oracle support portal to disable AWR completely.
3. For not accidentally using the Tuning pack, remove all the underlying data structures that might be needed for running the tuning pack. Removing AWR will help as the tuning uses the statistics in this report to run.