About accurate licensing for Oracle
Accurate licensing for Oracle is specific to an policy. The size of the data that is reported does not include the NetBackup for Oracle XML Archiver. This type of licensing collects the front-end data size (FEDS) for any Oracle backup that can be restored, not including transaction logs. Oracle Intelligent Policies define the backup selection on the Instances and Databases tab. The backup selection for script-based Oracle policies is defined based on what the script protects.
Note:
The data size collection does not work properly if OS authentication is disabled.
Licensing data is collected for each database that is protected even if there are multiple databases on a single host or cluster. Licensing uses physical data file characteristics the Oracle database reports, not logical or segment sizes. The reason NetBackup collects data this way is that during a disaster recovery, RMAN needs to restore the full physical data file and not just its logical pieces.
Oracle Data Guard configurations are licensed on a per database basis. Each of the primary or the standby databases needs to be restored individually and FEDS licensing is used for any Oracle backup that can be restored. Each of the primary or the standby databases reports their FEDS data whenever NetBackup protects it during a backup operation.
The following Oracle queries are used to gather file size information:
Get size of database files being backed up
This query retrieves the list of database files and their file sizes (in MB) for an instance:
select NAME, BYTES/1024/1024 from v$datafile;
This query shows the sum of the database file sizes for an instance:
select sum(BYTES/1024/1024) from v$datafile;
Note:
The preceding queries do not have information about the transaction log.
Get the size of the control file
This query retrieves the list of control files and their sizes (in MB), not including the transaction log:
select NAME, BLOCK_SIZE*FILE_SIZE_BLKS/1024/1024 controlfile_size from v$controlfile;