Download Oracle DB Engine

Oracle DB Engine
DOCUMENT:
PUBLISHED BY:
Oracle DB Engine
nova ratio AG
Universitätsstraße 3
56070 Koblenz
Germany
VERSION:
RELEASE DATE:
9.x
January 31st, 2016
Inhaltsverzeichnis
1
2
2.1
2.2
2.3
3
3.1
3.2
3.2.1
3.2.2
3.3
3.4
3.5
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.5.6
4
4.1
4.2
4.3
4.4
4.5
4.5.1
4.5.2
4.5.3
5
6
6.1
6.2
6.3
6.4
6.4.1
6.4.2
6.5
7
7.1
7.2
7.2.1
7.2.2
7.2.3
7.2.4
7.3
7.3.1
7.3.2
7.3.3
Foreword............................................................................................................................................ 1
Introduction....................................................................................................................................... 2
General............................................................................................................................................... 2
Basic understanding........................................................................................................................... 3
Work flow........................................................................................................................................... 4
The Graphical User Interface.............................................................................................................. 5
Overview............................................................................................................................................ 5
Dashboard pages................................................................................................................................ 6
Summary-Dashboards........................................................................................................................ 6
Analyzer-dashboards.......................................................................................................................... 7
Search pages...................................................................................................................................... 8
Object pages....................................................................................................................................... 9
Main menu....................................................................................................................................... 10
Overview main menu....................................................................................................................... 10
Menu entry Database....................................................................................................................... 10
Menu entry System.......................................................................................................................... 11
Menu entry Metric........................................................................................................................... 11
Menu entry Import & Export............................................................................................................ 12
Menu entry Advanced...................................................................................................................... 12
Data import...................................................................................................................................... 13
General............................................................................................................................................. 13
Data import: eOracle........................................................................................................................ 13
Data import: eAssessment................................................................................................................ 13
Import directory............................................................................................................................... 14
Missing import data.......................................................................................................................... 15
Database version.............................................................................................................................. 15
System query.................................................................................................................................... 15
Hardware catalog............................................................................................................................. 15
Data export ...................................................................................................................................... 16
Collecting data via script................................................................................................................... 17
General............................................................................................................................................. 17
Requirements for data collection...................................................................................................... 17
DB-SQL script.................................................................................................................................... 18
System script.................................................................................................................................... 19
System script UNIX........................................................................................................................... 19
System script Windows..................................................................................................................... 19
Virtualization script.......................................................................................................................... 20
Data analysis..................................................................................................................................... 21
Possibilities of data analysis.............................................................................................................. 21
Database drill-down......................................................................................................................... 21
Start................................................................................................................................................. 21
Database level.................................................................................................................................. 22
Options level.................................................................................................................................... 23
Detail level........................................................................................................................................ 24
System drill-down............................................................................................................................. 25
Start................................................................................................................................................. 25
System level...................................................................................................................................... 26
Detail level........................................................................................................................................ 26
Copyright ©2015 nova ratio AG
TOC
Oracle DB Engine
7.4
7.4.1
7.4.2
7.4.3
7.4.4
7.4.5
7.4.6
8
8.1
8.2
8.3
8.4
8.5
Metric drill-down.............................................................................................................................. 27
Start................................................................................................................................................. 27
License count for Standard-Edition (Socket)..................................................................................... 28
License count for Enterprise-Edition (Processor)..............................................................................28
License count for Enterprise-Edition (NUP)....................................................................................... 28
Drill-down at the license result level................................................................................................. 29
Drill-down from the license result level............................................................................................ 30
Plausibility checks............................................................................................................................. 31
Database lists................................................................................................................................... 31
Packs granted and agreed................................................................................................................. 31
Control Management Pack Access.................................................................................................... 31
DBA Feature Usage........................................................................................................................... 31
Standard Edition checks................................................................................................................... 32
Copyright ©2015 nova ratio AG
Inhaltsverzeichnis
Oracle DB Engine
1
Foreword
nova ratio AG is the manufacturer of the IT information platform eRunbook.
eRunbook is a registered trade mark of nova ratio AG.
The usage of the eRunbook software, of thereupon based solutions and all related documents is regulated
by license agreements with nova ratio AG.
The Oracle DB Engine, based on the IT Information Platform eRunbook by nova ratio, is the leading Oracle
DB license state recognition solution.
This document describes the Oracle DB Engine's application and usage and thereby explains the different
functions, features and the essential work flows.
nova ratio AG
Universitätsstraße 3
D-56070 Koblenz
Germany
Phone:
Fax:
Mail:
Web:
+49 261 20 16 58 1 – 0
+49 261 20 16 58 1 – 19
[email protected]
www.nova-ratio.com
Copyright ©2015 nova ratio AG
Page 1
Oracle DB Engine
2
Introduction
2.1
General
The Oracle DB Engine is a license-measurement tool for Oracle databases. All for license-measurement purposes necessary data are being imported (data import) and can be viewed and analyzed (data analysis) afterwards. In addition various export files are generated (data export).
The Oracle DB Engine is included in the following customer products by nova ratio AG:
• Option eOracle
The option eOracle provides an automated license measurement of Oracle databases as an enhancement
to the base product eInventory, in this case the data is provided by the eInventory product.
• Base product eAssessment
The base product eAssessment provides a script-based Oracle database license measurement as an independent solution. The data is gathered via query scripts (Data gathering via script).
• Base product eMetering
The base product eMetering provides a regular Oracle database license measurement with the use of the
Scan Engine of the eRunbook platform. Hereby the data is provided by the Scan Engine.
Picture: Oracle DB Engine for the Oracle database license measurement
Copyright ©2015 nova ratio AG
Page 2
Oracle DB Engine
2.2
Basic understanding
The Oracle DB Engine is a license-measurement tool for Oracle databases. Infrastructure data are processed
and transformed into the license perspective.
The infrastructure view combines system and database information:
• System:
Hardware information
OS information
Virtualization information
Partitioning information
• Database:
Edition
Version
Options and Management Packs
Root-cause analysis
The license view transforms this information from the infrastructure perspective to the license perspective
according to the Oracle license metric standards and rules. Thereby every license entry represents one license relevant entity and the license results form sums out of the different kinds of license entries.
The license entries are composed by the following information:
• Type:
The license entry's type
can be "Edition" or "Option"
• Key:
The Key identifies the Edition or Option
e.g. "EE" for the type "Edition"
• Metric:
The license entry's metric
"Processor" or "NUP" for Enterprise editions,
"Socket" for Standard editions
• Scope:
The Scope describe the license entry's coverage
e.g. "standalone_ko-pc-1" for a database at a standalone system
• Count:
The license entries license counter
e.g. "2.0" for an Enterprise edition with processor metric
Copyright ©2015 nova ratio AG
Page 3
Oracle DB Engine
2.3
Work flow
The Oracle DB Engine's work flow is a three steps workflow, which can be repeated as often as needed:
• Data gathering:
The data gathering happens automated by using the respective nova ratio AG product or manually by applying the provided query scripts and copying the script results to the Oracle DB Engine import folder.
• Data import:
The data import is activated automatically or manually via the related menu entry. The data import conducts several plausibility checks. Afterward the imported data is processed and results are generated. At
the end the data export is performed.
• Data analysis:
The data analysis uses the drill-down navigation and the menu entries provided through the web interface.
Copyright ©2015 nova ratio AG
Page 4
Oracle DB Engine
3
The Graphical User Interface
3.1
Overview
The Oracle DB Engine is used interactively via the web browser. The following image shows the Database
Summary Dashboard as the homepage, displaying the different parts of the user interface and names the
different control elements:
• Logo
Clicking the logo redirects you to the homepage.
• Main menu
The main menu always allows to select a menu entry
• User settings
The user settings switch between user- and expert-mode and enable the change of user specific settings,
for example the GUI language
• Online-help
The question-mark icon opens the related online-help article, as long as an article is available
• Data section
The data section displays the selected information
Picture: Homepage
Copyright ©2015 nova ratio AG
Page 5
Oracle DB Engine
3.2
Dashboard pages
The Oracle DB Engine provides two kinds of dashboards:
• Summary-dashboards
• Analyzer-dashboards
At every dashboard page it is possible to change between the available dashboards via the drop down menu
located under the logo. Certain dashboards can alternatively be selected by using the related menu entries.
All dashboards support the online-help, which is activated by clicking the question mark found at the top
right corner.
3.2.1 Summary-Dashboards
The Summary-dashboards summarize information in tabular form. Different categorizations are displayed in
those dashboards. The drill-down-function can be accessed by selecting the drill-down-arrow. Thereby the
next detail level is displayed.
Picture: "Metric Summary" as example for a summary-dashboard
Copyright ©2015 nova ratio AG
Page 6
Oracle DB Engine
3.2.2 Analyzer-dashboards
The analyzer-dashboards enable the interactive filtering of data by selecting different slices of the pie chart.
The data table below enables the drill-down to the next detail level by selecting an entry in the data table.
Picture: "Database Analyzer" as an example for an analyzer-dashboard
Copyright ©2015 nova ratio AG
Page 7
Oracle DB Engine
3.3
Search pages
The Oracle DB Engine provides a series of search pages. The essential searches are:
• Database searches:
Display database information
• Option searches:
Display Option and Management Pack information
• System searches:
Display system information
The drop down menu below the main menu allows to switch between the available lists, related to the
search, at all search pages. Some search pages can alternatively be accessed via their related menu entries.
The displayed entries can be filtered by entering a filter-criterion in the filter-box, located at the top right
corner. Only entries which include the filter-criterion as a character string are displayed.
The drill-down arrow at the data table's left edge allows to navigate to the next lower detail level. Not all
lists and searches allow to use drill-down-function.
The book-symbol at the data table's left edge allows to navigate to the object page related to the selected
entry.
All database and system searches support the online-help, which is activated by clicking the question mark
found at the top right corner.
Picture: Database list "Database Summary" as an example for a search page
Copyright ©2015 nova ratio AG
Page 8
Oracle DB Engine
3.4
Object pages
The Oracle DB Engine provides a series of project pages. The essential project pages are:
• Database documents
Display database information
• System documents
Display system information
The drop down menu below the main menu allows to switch between the available documents.
Picture: Document "Database Summary" as an example for an object page
Copyright ©2015 nova ratio AG
Page 9
Oracle DB Engine
3.5
Main menu
3.5.1 Overview main menu
The menu consists of different layers. The first layer displays the five main sections, respectively the items
Database, System, Metric, Import/Export and Advanced. Each of those sections possess further subsections
which are displayed on the lower layers.
Picture: Menu "Database" as on of the five main entries
3.5.2 Menu entry Database
The menu entry Database includes all information and data concerning the databases. The subsections are
the following:
•
Menu entry All DB:
All DB shows a listing of all known and found databases in its Overview (to be found in the menu at Database>All DB>Overview). This listing can be adapted by selecting further database subsections. By using the
subsections the listing can be adapted to show only databases with options (DB with options), packs (DB
with packs) or with options and/or packs (DB with options or packs).
•
Menu entry DB with data:
DB with data displays all databases, for which information are available. Just like the All databases subsections, the DB with data subsection is divided into the four subsections overview (Overview), databases with
options (DB with options), packs (DB with packs) and options and/or packs (DB with options or packs). The
menu entries and the drill-down function allow for further and more detailed or adapted information.
If the data is gathered by using the Scan Engine, All databases and DB with data will show the same data.
•
Menu entry Report:
Report shows a listing of all applied database editions (Editions),of all applied options (Options), packs
(Packs) or a combination of all applied options and packs (Options&packs). The drill-down function allows
to gather further information concerning the list items.
Copyright ©2015 nova ratio AG
Page 10
Oracle DB Engine
3.5.3 Menu entry System
The section System includes all information concerning the physical and the virtual systems.
The main section is divided into the following subsections:
• Menu entry All Systems:
All Systems displays a listing of all applied systems (System>All Systems>All Systems). Virtual hosts lists all
systems which are hosting virtual systems . Consequently Virtual clients lists the thereon based virtual
systems. Standalone systems lists all known and applied standalone systems. AIX Details displays all systems using the AIX OS.
• Menu entry Systems with data:
Systems with data displays all systems for which data is available. Just like the All Systems subsection the
Systems with data subsection is divided into the subsections overview (All systems with data), all virtual
hosts (Virtual hosts), all virtual clients (Virtual clients), all standalone (Standalone systems) and all AIX systems(AIX Details). If the data is gathered by using the Scan Engine, All systems and Systems with data will
show the same data.
• Menu entry Systems with DB:
Systems with DB displays listings of all systems running databases. There are three subsections: All database systems lists all systems on which databases are installed and/or applied. The subsections Physical
database systems and Virtual database systems list all physical or virtual database systems.
If the scan engine is used to collect the data, the two menu entries All systems and System with data show
the same data and information.
3.5.4 Menu entry Metric
The section Metric gives an overview of the license structure. Thereby it is focused to connect the physical
systems with the thereon running databases and the license entries.
The Oracle DB Engine data is hereby used to explain to the user which databases and systems belong to
which license entry and which license entries are required for a system.
This can only be achieved by implementing the Oracle licensing rules. Only thereby it can be ensured that
possible special cases will be detected and properly licensed.
An example for this case is the licensing of clusters and virtual systems by which a processor metric license
can comprise various systems without comprising the NUP metric databases running on these systems.
• Menu entry All license entries:
The menu entry All license entries shows all license entries with their related type (Edition, Option), their
category (processor- or user-license), its number and coverage.
• Menu entry Update all license entries:
The menu entry Update all license entries effectuates an update of the data on which the metric is based
on.
Copyright ©2015 nova ratio AG
Page 11
Oracle DB Engine
3.5.5 Menu entry Import & Export
The section Import & Export provides the option to import the gathered data, to access the server-worksheet file and to export the processed data according the requirements.
• Menu entry Export:
Export allows to generate a list of all exported server-worksheets. The list provides the possibility to
download the server-worksheet files to the desktop.
• Menu entry Import State:
Import State displays information concerning the state of the imported data.
• Menu entry Import changed files:
Import changed files provides the possibility to import and update only the outdated data, tagged by the
change detection. The unchanged data will remain and does not need to be updated or imported.
• Menu entry Import all files:
Import all files provides the possibility to import and update all gathered data.
• Menu entry Update dashboard data:
Update dashboard data allows to update the data displayed in the dashboard.
3.5.6 Menu entry Advanced
The section Advanced includes essential functions as well as some advanced features.
• Menu entry Changes:
Changes shows in its subsection Changes Database the changes made to the databases registered by the
change detection and allows for data updates without querying the unchanged systems.
• Menu entry Repositories:
Repositories lists all database repositories (All repositories) which are included in the database information processed during the import process.
• Menu entry Options and Packs:
Options and Packs shows listings of all options (Options), packs (Packs) or all options and packs (All options and packs).
• Menu entry Settings:
Settings illustrates the decision standards and reference data.
Copyright ©2015 nova ratio AG
Page 12
Oracle DB Engine
4
Data import
4.1
General
The Oracle DB Engine processes data located in the import directory ($NOVAIMPORT) with the defined
folder structure. After terminating the data import no further changes or processes are applied to the information.
In order to reflect changes to the data, the data import must be repeated. The data import consists of the
following three steps:
• Preprocessing
The preprocessing transforms the data generated by LMS scripts in the Oracle DB Engine format and
matches databases and repository information. The preprocessed results are stored in the directory:
$NOVAIMPORT/Import_eRunbook.
• Data processing
The data processing imports the data stored in the directory $NOVAIMPORT/Import_eRunbook and
the Oracle DB Engine completely processes the data. After the data is imported it is no longer subject to
changes.
• Data export
The data export generates server-worksheets as XLS files and LMS export-files, which are required for
LMS audits.
The server-worksheets are stored in the directory $NOVAIMPORT/Export_eRunbook.
The LMS export-files are stored in the directory $NOVAIMPORT/Export_LMS.
4.2
Data import: eOracle
The eOracle product uses an automated interface in order to import the data from the products eInventory
and eMetering. Hereby their data is automatically stored in the respective import directory.
4.3
Data import: eAssessment
The import directory has to be manually filled for the product eAssessment. After the provided query
scripts are applied to the systems and databasesm the result files have to be copied in the respective folders
in the import directory. Afterward the data import is started manually by using the menu entries Import
changed files or Import all Files in the Import & Export section.
The product eAssessment supports the import of files which are gathered by the LMS scripts when performing an Oracle audit (Review-Light and CPU-Query). Data from eAssessment query scripts and LMS
scripts can be imported parallel as long as every database and system is only queried once.
When selecting the menu entry Import changed files only the data is updated which have changed data in
the import directory compared to the last import.
When selecting Import all files all files are imported independently of the changes registered since the last
import. Normally the menu entry Import changed files is used.
Copyright ©2015 nova ratio AG
Page 13
Oracle DB Engine
4.4
Import directory
The import directory possesses the following sub-directories which must be filled with data:
Directory
Sub-directory
Description
Datafiles_DB
eRunbook
eAssessment database query script results,
one file per database
Datafiles_DB
LMS
LMS Review-Light files,
one sub-directory per database
Datafiles_System eRunbook
eAssessment system query script results,
one file per system
Datafiles_System LMS
LMS CPU-Query files,
one file per system
Datafiles_VM
eRunbook
eAssessment VM query script results,
one file per VMcenter query
Datafiles_VM
LMS
Not used currently
Besides the data directories there are other import directories:
Directory
Sub-directory
Description
Export_LMS
---
CSV files for the Oracle audit
Export_ eRunbook
---
XLS work-sheets with exported data
Import_ eRunbook
---
internal Oracle DB Engine files
Copyright ©2015 nova ratio AG
Page 14
Oracle DB Engine
4.5
Missing import data
4.5.1 Database version
If no data can be displayed for a database in the database instance overview, this might be due to missing
privileges. In this case the result file of the database SQL script should be reviewed and as the case may be
the privileges might need to be configured before reapplying the database SQL script.
4.5.2 System query
If the system overview in the „Database-System“ list does not display any CPU data (CPU physical, Core
physical) or when the CPU type states "unknown" it might be, that the system-script results are not stored
in the import directory.
If missing information are the case in virtual environments, often the physical host, which runs the virtual
system, has not been queried. The system-script must be run on at those physical hosts.
An exception are VMware environments in which the physical hosts (the ESXi Server) are queried by the
VM script querying the managing vCenter.
4.5.3 Hardware catalog
During the import process the system information is matched with a hardware catalog. If a device type is
not found in the hardware catalog, various parameters like the number of physical CPU sockets cannot be
determined.
The menu entry Advanced>Settings>System>Systems without Model Mapping lists all systems with missing
hardware catalog entry.
Copyright ©2015 nova ratio AG
Page 15
Oracle DB Engine
5
Data export
The data export is automatically enabled after the Oracle DB Engine's data import. Thereby two directories
are filled with data:
Directory
Sub-directory
Description
Export_LMS
---
CSV files for the Oracle audit
Export_ eRunbook
---
XLS work-sheets with exported data
Copyright ©2015 nova ratio AG
Page 16
Oracle DB Engine
6
Collecting data via script
6.1
General
The product eAssessment provides the necessary scripts which have to be run manually on databases and
systems. The script results are then copied into the Oracle DB Engine import directory. Afterwards the
Oracle DB Engine import function can be started.
The following eAssessment scripts will be applied during the eAssessment data collection via script for the
Oracle DB Engine:
• Database SQL script
Queries the Oracle database information
The database SQL script does not read application-specific data!
The database SQL script does not read customer data!
• System script
Queries the technical system information of Windows, Unix and Linux systems
• Virtualization script
Queries the virtualization information for Vmware
6.2
Requirements for data collection
Running the query scripts requires certain privileges at the systems or in the database. Without these privileges the license parameters cannot be determined!
• Database SQL script
If the database SQL script is run as a DBA/SYSDBA user no further privileges must be given in the database instance.
If the database SQL script is not run as privileged database user, this user must be granted certain privileges. This is necessary because systems tables must be queried in order to determine the license state.
Grant scripts are provided which generate the user and the necessary privileges in the database.
• System script
To run the system script administrator- or root-privileges are required.
• Virtualization script
The VMware vSphere CLI must be installed and configured on the vCenter system, or the system which is
querying the vCenter.. In order to run the virtualization script a user and the respective password within
the vCenter is required.
Copyright ©2015 nova ratio AG
Page 17
Oracle DB Engine
6.3
DB-SQL script
The DB-SQL script collects the data required, according to Oracle's guidelines, to ascertain license details
and support a LMS review. The script is executed as DBA/SYSDBA without parameters.
An exemplary query:
@sql_nova_eR_full.sql
The query is also possible from inside the shell. The command therefore is:
sqlplus <username>/<password>@<SID> @sql_nova_eR_full.sql
As result the script run generates a file, which is stored in the directory from which the script was started.
The resulting file is called: result_<SID>.csv
This file must be generated for all database instances for which the license state shall be determined. This
file must be collected for every database and must be stored in the following folder within the import
directory: /opt/eRunbook/import/<instancename>/Datafiles_DB/eRunbook
The query of database instances with active pluggable databases (starting from Oracle V12) is conducted individually for every PDB and the respective CDB$ROOT. A PDB$SEED need not to be queried.
A direct CDB$ROOT query is possible if the log-in is performed via SID:
sqlplus <username>/<password>@<SID>
A PDB can be performed by naming the PDB as call parameter
@sql_nova_eR_full.sql <PDB Name>
or it can be called from an CDB$ROOT Session:
ALTER SESSION SET CONTAINER = <PDB Name>
The script run is then started in the PDB via the following command:
@sql_nova_eR_full.sql
Copyright ©2015 nova ratio AG
Page 18
Oracle DB Engine
6.4
System script
The system script determines the necessary data for the license state like the OS version, CPU data and virtualization information. The system script is provided for the following operation systems:
• MS-Windows
• Unix/Linux (Solaris, HP-UX, IBM-AIX, all essential Linux distributions)
6.4.1 System script UNIX
The system script eRunbook_collect_unix.sh and the query module erunbook_system_short can be stored
in any directory on the queried system.
The system script eRunbook_collect_unix.sh must have executive rights.
Run the following command as user root:
./eRunbook_collect_unix.sh erunbook_system_short
The script run generates a directory/subdirectory output/<System name> in which all resulting files
are stored. Furthermore a tar file (Name: <host name>.tar) is generated, which already includes the
directory/subdirectory Output/<System name> and all resulting files.
This tar file must be collected for every queried server system and must be extracted in the following folder
within the import directory: /opt/eRunbook/import/<instancename>/Datafiles_DB/eRunbook
6.4.2 System script Windows
The system script eRunbook_collect_windows.vbs and the query module erunbook_system_short can be
stored in any directory on the system.
The following command must be applied by a user possessing administrative privileges:
cscript eRunbook_collect_windows.vbs erunbook_system_short
The script run generates files in the directory output within the directory from which the script was executed. This output directory must be collected for every queried server system and must be stored within
the import directory: /opt/eRunbook/import/<instancename>/Datafiles_DB/eRunbook
Copyright ©2015 nova ratio AG
Page 19
Oracle DB Engine
6.5
Virtualization script
The Virtualization script is a special query mechanism for the VMware vCenter in order to determine the
necessary information for the VMware environment. This includes the ESXi system hardware-parameters,
cluster and storage information of the VMware environment as well as the assignment of the virtual systems to the host systems.
Please note:
The information for other virtualization software (for example HyperV or Xenserver) are queried by the system script. This means, that the system script must as well be run on the host systems of those virtual machines in order to provide the Oracle DB Engine with complete information. This translates to Solaris zones
for which the system scripts must be run in the global as well as in the local zones.
The virtualization script can be run on any Windows system having the VMware vSphere CLI configured and
being able to communicate with the vCenter servers.
Store the files Perl_ESXi_Wrapper.bat and get_esxhosts_vm.pl on the querying system and run the following command for every vCenter server to be queried:
Perl_ESXi_Wrapper.bat /u <user name> /p "<password>" /s <vcenter name>
If the script is executed on the VMware vCenter server itself, the following command must be executed:
Perl_ESXi_Wrapper.bat /u <username> /p "<password>"
The script run generates a result file for each vCenter in the folder in which the script was run. This file must
be collected for each vCenter and must be stored in the following folder within the import directory:
/opt/eRunbook/import/<instanzname>/Datafiles_VM/eRunbook
Please note:
The VMware vSphere CLI must be installed on the system querying the vCenter server. The CLI includes the
Perl module. The vCenter server provides the data for all ESXi Server, which are managed by this vCenter.
Copyright ©2015 nova ratio AG
Page 20
Oracle DB Engine
7
Data analysis
7.1
Possibilities of data analysis
The Oracle DB Engine provides different kinds of data analysis. The three following work-flows are typical
for all operational scenarios:
• Database drill-down
• System drill-down
• Metric analysis
7.2
Database drill-down
7.2.1 Start
The database drill-down enables a comprehensive root-cause-analysis for all databases and their Options
and Management Packs. The database drill-down starts in one of the two dashboards
"Database Summary" or "Database Analyzer".
Picture: Dashboard "Database Summary", basis of the database drill-down
Copyright ©2015 nova ratio AG
Page 21
Oracle DB Engine
7.2.2 Database level
The first drill-down navigates to the database level and displays the database search. At the database level
different database search lists can be used or a database's object page can be selected.
Picture: Database search with the "Database-Summary" seach
Copyright ©2015 nova ratio AG
Page 22
Oracle DB Engine
7.2.3 Options level
The second drill-down navigates to the Options and Management Packs level. Only the Options and Management Packs related to the database selected by the drill-down are shown. The Options level provides,
just like the database level, various lists which can be used or an Option's or a Management Pack's object
page can be selected.
Picture: Option search with the "Option Usage-Summary" list
Please note:
If the Dashboard "Database Analyzer" has been chosen as origin of the drill-down, then navigates
the drill-down directly to the Options level.
Copyright ©2015 nova ratio AG
Page 23
Oracle DB Engine
7.2.4 Detail level
The object page is the first to display the "Root Cause Analysis" document in which the complete
Oracle DB Engine decision logic of the selected Option or Management Pack is comprehensively explained.
Picture: Object page with the "Root Cause Analysis" document
Copyright ©2015 nova ratio AG
Page 24
Oracle DB Engine
7.3
System drill-down
7.3.1 Start
The system drill-down enables a comprehensive analysis of the system data. The system drill-down starts in
one of the two dashboards "System Summary" or "System Analyzer".
In the following example the "System Summary" dashboard displays the system count according to three
criteria:
• Virtualization role (VM Role)
• Operating System
• CPU
Picture: Dashboard "System Summary"
Copyright ©2015 nova ratio AG
Page 25
Oracle DB Engine
7.3.2 System level
The drill-down navigates to the system level and activates the system search. At the system level various
system search lists can be used or it is possible to navigate to a system's object page.
Picture: Search page of systems within the "System-Summary" list
7.3.3 Detail level
The object page provides several documents in which the system data is presented.
Picture: A system's object page
Copyright ©2015 nova ratio AG
Page 26
Oracle DB Engine
7.4
Metric drill-down
7.4.1 Start
The metric analysis uses the two dashboards "Metric Summary" and "Metric Analyzer". The drilldown within these dashboards is performed analogously to the system drill-down.
The "Metric Summary" dashboard consists of the project section and the three following sections:
• License count for Standard-Edition (Socket)
• License count for Standard-Edition (Processor)
• License count for Standard-Edition (NUP)
These three sections summarize the license results related to the respective section.
Picture: Dashboard "Metric Summary"
Copyright ©2015 nova ratio AG
Page 27
Oracle DB Engine
7.4.2 License count for Standard-Edition (Socket)
The section License count for Standard-Edition (Socket) displays the license counter total for all
Standard-Edition databases. Thereby every system is analyzed if at least one Standard Edition database exists at this very system. If this is the case, the number of used sockets of this system is used to generate the
sum of all license-relevant sockets according to the license scope.
7.4.3 License count for Enterprise-Edition (Processor)
The section License count for Enterprise-Edition (Processor) displays the processor-license counter totals
for all Enterprise Edition databases. Displayed are the Enterprise Edition alongside all license-relevant Management Packs and Options.
In order to calculate these counters, every system is analyzed if at least one Enterprise Edition database
with processor metric exists at this very system. If this is the case, the system's license scope is determined.
Afterwards Oracle's hard- and soft-partitioning rules for databases are applied. For all systems within one license scope the number of CPU-cores is multiplied with the respective processor factor and then summed
up for all systems within this license scope.
7.4.4 License count for Enterprise-Edition (NUP)
The section License count for Enterprise-Edition (NUP) displays the NUP counter total for all Enterprise Edition databases. Displayed are the Enterprise Edition alongside all license-relevant Management Packs and
Options.
In order to calculate these counters, every database is tested, if this very database underlies the NUP metric. If this the case, the license scope for this database is set and the NUP count is summed up.
Copyright ©2015 nova ratio AG
Page 28
Oracle DB Engine
7.4.5 Drill-down at the license result level
The drill-down from the "Metric Summary" summary's three detail levels leads to the license result level. Every license entry represents one license-relevant entity. The license entries are the basis for the totaling of the license results, which are displayed in the "Metric Summary" dashboard.
The license entries provide the following information:
• Type:
The license entry's type
can be "Edition" or "Option"
• Key:
The Key identifies the Edition or Option
e.g. "EE" for the type "Edition"
• Metric:
The license entry's metric
"Processor" or "NUP" for Enterprise editions,
"Socket" for Standard editions
• Count:
The license entries license counter
e.g. "2.0" for an Enterprise edition with processor metric
• # of systems:
Number of associated systems
• # of databases:
Number of associated databases
• # of scopes:
Number of associated license scopes
Picture: License result level
Copyright ©2015 nova ratio AG
Page 29
Oracle DB Engine
7.4.6 Drill-down from the license result level
The drill-down from the license result level leads to the license entry level.
Every license entry represents one license-relevant entity. The license entries are the basis for the totaling
of the license results, which are displayed in the "Metric Summary" dashboard.
The license entries comprise the following information:
• Type:
The license entry's type
can be "Edition" or "Option"
• Key:
The Key identifies the Edition or Option
e.g. "EE" for the type "Edition"
• Metric:
The license entry's metric
"Processor" or "NUP" for Enterprise editions,
"Socket" for Standard editions
• Scope:
The Scope describe the license entry's coverage
e.g. "standalone_ko-pc-1" for a database at a standalone system
• Count:
The license entries license counter
e.g. "2.0" for an Enterprise edition with processor metric
Picture: License entry level
Copyright ©2015 nova ratio AG
Page 30
Oracle DB Engine
8
Plausibility checks
8.1
Database lists
The database information level can, by selecting the „Database-Check“ list, display three pieces of data,
which may apply as basis for a series of plausibility checks. Pictured below are the three columns
"Packs agreed & granted", "Control Management Pack Access" and "DBA Feature
Usage".
Picture: Database search page with the "Database-Check" list
8.2
Packs granted and agreed
The column "Packs granted & agreed" within the list displays all Management Packs for each
which state Granted as well as Agreed are TRUE.
8.3
Control Management Pack Access
The column "Control Management Pack Access" within the list cites the value of the
control_management_pack_access variable from within the GV$PARAMETER configuration of the
respective database.
This value indicates which of the two Management Packs, Diagnostic Pack or Tuning Pack, can be used in
the database. Possible values are "none", "diagnostic" or "diagnostic+tuning".
8.4
DBA Feature Usage
The column "DBA Feature Usage" within the list displays for each database the Options and Management Packs, for which at least one related feature possesses a value greater than zero in the
DATABASE_FEATURE_USAGE_STATISTICS view in the usage counter.
Please note:
This usage counter's value does not relate directly to to the Option's or Management Pack's license state.
Copyright ©2015 nova ratio AG
Page 31
Oracle DB Engine
8.5
Standard Edition checks
The database search's "Database-Edition" list shows the license-relevant as well as the technical database edition. This list can be accessed by the drill-down link at the "# of edition changes" counter
in one of the summary dashboards.
Initially the Oracle DB Engine determines for every database the technical database edition, this means the
database edition which is reported by the database during the query process.
For Enterprise Edition databases this always equals the license-relevant database edition.
Standard Edition databases can be classified as an Enterprise Edition according to the license regulations, although technically a Standard Edition database had been installed:
• Usage of Options and Management Packs
According to the license regulations Standard Edition databases are not allowed to use Options or Management Packs except the Real Application Cluster Option (RAC).
• Violation of socket limits
According to the license regulations a Standard Edition database is only applicable at systems with a specific maximum CPU-socket count. This count is limited to 4 sockets for The Standard Edition and 2
sockets for The Standard Edition One and The Standard Edition 2.
The database search's " Database-Edition" list shows in the "Edition Decision" column these
deviations and states the reason for the deviation between the technical database edition and the database
edition according to the license regulations.
In the following example the databases are classified as Enterprise Editions according to the license regulations, because Options and Management Packs are used which are non-eligible for the Standard Edition:
Picture: Database search page with "Database-Edition" list
Please note:
In all dashboards the database edition according to the license regulations is used as well as for the calculation of the processor-license counters in the metric dashboards.
Copyright ©2015 nova ratio AG
Page 32
Oracle DB Engine
nova ratio AG
Universitätsstraße 3
D-56070 Koblenz
Germany
Phone:
Fax:
Mail:
Web:
Copyright ©2015 nova ratio AG
Page 33
+49 261 20 16 58 1 – 0
+49 261 20 16 58 1 – 19
[email protected]
www.nova-ratio.com
Oracle DB Engine