Oracle Server Worksheet for Oracle Database Report

FlexNet Manager Suite 2019 R1 (On-Premises Edition)

The Oracle Server Worksheet for Oracle Database report provides details of your Oracle deployment. Each record in the report represents one Oracle database instance. The report provides you with the information that you must provide to Oracle during a license true-up or whenever you are audited. You can export this report and use the information to populate the Server information, Database information, and Hardware information sections of the Oracle Server Worksheet.

Note: Data for the Application information section of the OWS is not included in this report.

Generating the report

Navigate to License Compliance > Compliance > Oracle Server Worksheet for Oracle Database.
Click Run report to display the results for all Oracle deployments.

Limiting the report results

The following filters are available to further limit the results:

Filter by one or more Product version
Filter by one or more Product edition
Filter by one or more Environment usage, such as a Staging environment
Filter by one or more Enterprise group. (For help with the search, see To Use a Fly-Down.)

Reading the report

The following columns (listed alphabetically) are available.

Column name (2019 r1)	Description
Cores per processor	The number of physical or virtual cores per processor. This value is calculated by dividing the Total no. of processors/sockets by the number of physical or virtual cores. This read-only field is calculated by FlexNet Manager Suite.
DB instance name	The name of the Oracle database instance, for example `orcl`. If the database is a container (or root) database which contains one or more pluggable databases, then the value which displays here is concatenated <instance name>~CDB_ROOT. For example, if the container database instance is `orcl`, then the container database displays as `orcl~CDB_ROOT`. Continuing with this example, if the pluggable databases within this container database are named `MPDB1`, `MPDB2`, `MPDB3` and `PDBORCL`, then each would be listed as `orcl~MPDB1`, `orcl~MPDB2`, `orcl~MPDB3`, and `orcl~PDBORCL` respectively. Database instance names will only display when they satisfy the following conditions: They link to a license where they are not supplementary applications and counted for consumption They link to a license from which they or their device (Including VM Ware/Hyper V) consume a license They are not on ignored devices They are installed and in use. Editable in the Name field on General tab of the Oracle instance properties.
Environment usage	The deployment environment to which this Oracle instance belongs to. An organization divides the software and hardware infrastructure into multiple deployment environments and assigns a role (primary, backup) to each device within an environment. For example, the infrastructure (application and database servers, storage, networking devices) required for the development is mostly a part of the Development environment. The following options are available: `Development`, `Other`, `Production`, `Staging`, and `Test`. Selectable in the Environment field in the General tab of the Oracle instance properties.
License metric (NUP/Processor)	Indicates the type of license which this Oracle database instance is consuming from. The following options are available: `NUP` — Oracle Named User Plus license `Processor` — Oracle Processor license.
Notes	A blank field which enables you to add any notes to the exported report.
Number of licenses in use	The number of licenses being consumed by this Oracle database instance. This value differs depending on the license metric as follows: If the database is consuming from an Oracle Named User Plus (`NUP`) license, then this value is the number of users connecting to the database. If the database is consuming from an Oracle Processor license (`Processor`) then this value is based on the properties of the physical server such as the number of cores and processor type. For cases where the physical server is hosting multiple virtual servers, the number of licenses in use will be equal to the number of virtual servers. In this case, a value only displays for one result for this physical server and the remaining results display a zero value. Multiple instances on a physical server can cause many rows in the OSW. An instance will consume Oracle database licenses in this report (for example, if the number of licenses in use id greater than zero (0) for at least instance on the server) if the Oracle database software: Is installed Links to a license from which it, its physical host, or its virtualization context (such as vCenter), consumes a license entitlement Link to a license where it is not a supplementary application exempted from consumption Is not on an ignored device Note: These rules apply to the Oracle options and management packs, and to the DB instance itself.
Operating system	The operating system running on this device. This value is collected from the device inventory record. Editable in the Hardware tab of the inventory device properties (for manually-created records).
Options & Mgmt packs in use	The name of each Oracle option and each Oracle management pack which is installed, is in use, and is licensable on this Oracle database instance. Options and Management packs only display if they: Are installed and in use Link to a license from which they, or their device (including VM Ware/Hyper V), consume a license Link to a license where they are not supplementary applications exempted from consumption Are not on an ignored device. Not directly editable, however the Licensable check box in the General tab of the Oracle instance properties can be cleared to set an option or management pack as not licensable. The list of options and management packs which are installed on an Oracle database instance is visible in the Options tab of the Oracle instance properties.
Physical cores	The total number of processor cores available in a physical inventory device; or the number of cores assigned to an inventory device that is a virtual machine. Populated and (by default) updated by inventory imports, the number of Cores can be manually overridden in the Hardware tab of the inventory device properties (see Hardware Tab).
Physical server name	The name of the physical server or, if the device is located on a virtual server, the host server name. Editable in the Name field of the General tab of the inventory device properties (if mapped to an inventory device). The compliance calculation updates this field with the machine name returned in inventory (matched by serial number).
Pluggable DB name (PDB)	This field display one of the following options: The name of each pluggable database within this container database instance. For example, the name of the four pluggable databases within this container listed by name could be `MPDB1`,`MPDB2`,`MPDB3`,`PDBORCL` The name of this single pluggable database which exists within a container database. For example, `MPDB1` The field is blank for standalone database instances.
Proc. speed (MHz)	The maximum clock speed (in MHz) of the processor that is installed in the inventory device. Editable in the Hardware tab of the inventory device properties (for manually-created records). If the value is gathered from inventory, it cannot be edited; however, it can be overridden.
Processor model	The type of processor installed in the inventory device. Populated and (by default) updated by inventory imports, this value can be manually overwritten in the Hardware tab of the inventory device properties (see Hardware Tab).
Product edition	The Oracle database edition, as specified by the publisher. Visible on the Applications tab of the inventory device properties.
Product version	The release number (or release identifier) of the Oracle database. Editable in the Version field in General tab of the application's properties, but only for those application records that were created within your enterprise. For applications from Application Recognition Library, it is not editable.
Server model	The manufacturer’s model name or number for this device. Editable in the Model field in the General tab of the inventory device properties (for manually-created records). If the value is gathered from inventory, it cannot be edited, however it can be overridden by entering a new value in the Overridden field in General tab of the inventory device properties. The original value continues to display on the General tab, alongside the overridden value, and may be restored at any time.
Software installation date	The date when the Oracle software was installed. This read-only value is generated from incoming inventory.
Total no. of processors/sockets	The total number of processors installed in a physical inventory device, or logical processors assigned to a `Virtual machine`. Populated and (by default) updated by inventory imports, this field in the Hardware tab of the inventory device properties can be overridden with a manually entered value (see Hardware Tab). Overridden values are no longer updated by incoming inventory.
Virtual server name	The name of the virtual server which is hosted on the physical server (Physical server name).
Virtualization/Partitioning technology	The technology used to create the virtual machine or partition, such as IBM LPAR, Solaris Zone, VMWare, OVM Server for x86, Oracle Trusted Partitions, Exadata Capacity-On-Demand, and so on. This data will be the same for all virtual servers which are located on the same physical server. Editable in the VM Type field in the VM Properties tab of the inventory device properties.