OpenText Analytics Database 26.2.x – Managing licenses

Admin: Obtaining a license key file

Mon, 01 Jan 0001 00:00:00 +0000

Follow these steps to obtain a license key file:

Log in to the Software Entitlement Key site using your passport login information. If you do not have a passport login, create one.
On the Request Access page, enter your order number and select a role.
Enter your request access reasoning.
Click Submit.
After your request is approved, you will receive a confirmation email. On the site, click the Entitlements tab to see your database software.
Under the Action tab, click Activate. You may select more than one product.
The License Activation page opens. Enter your Target Name.
Select your database version and the quantity you want to activate.
Click Next.
Confirm your activation details and click Submit.
The Activation Results page displays. Follow the instructions in New license installations or License changes to complete your installation or upgrade.

Admin: Understanding licenses

Mon, 01 Jan 0001 00:00:00 +0000

OpenText™ Analytics Database has flexible licensing terms. It can be licensed on the following bases:

Term-based (valid until a specific date).
Size-based (valid to store up to a specified amount of raw data).
Both term- and size-based.
Unlimited duration and data storage.
Node-based with an unlimited number of CPUs and users (one node is a server acting as a single computer system, whether physical or virtual).
A pay-as-you-go model where you pay for only the number of hours you use. This license is available on your cloud provider's marketplace.

Your license key has your licensing bases encoded into it. If you are unsure of your current license, you can view your license information from within the database.

Note

OpenText™ Analytics Database does not support license downgrades.

Trial license

The 30‑day Trial license is the current evaluation option for OpenText™ Analytics Database (Vertica). It provides a supported way to explore the database capabilities in a time‑limited environment before transitioning to a commercial license. For more information about trial entitlements and getting started, see Trial license as the Evaluation Option.

The license cannot be installed co-located in a Hadoop infrastructure and used to query data stored in Hadoop formats.

OpenText™ Analytics Database for SQL on Apache Hadoop license

OpenText™ Analytics Database for SQL on Apache Hadoop is a separate product with its own license. This documentation covers both products. Consult your license agreement for details about available features and limitations.

Admin: Installing or upgrading a license key

Mon, 01 Jan 0001 00:00:00 +0000

The steps you follow to apply your OpenText™ Analytics Database license key vary, depending on the type of license you are applying and whether you are upgrading your license.

Admin: Viewing your license status

Mon, 01 Jan 0001 00:00:00 +0000

You can use several functions to display your license terms and current status.

Examining your license key

Use the DISPLAY_LICENSE SQL function to display the license information. This function displays the dates for which your license is valid (or Perpetual if your license does not expire) and any raw data allowance. For example:

=> SELECT DISPLAY_LICENSE();
                  DISPLAY_LICENSE
---------------------------------------------------
 Vertica Systems, Inc.
2007-08-03
Perpetual
500GB

(1 row)

You can also query the LICENSES system table to view information about your installed licenses. This table displays your license types, the dates for which your licenses are valid, and the size and node limits your licenses impose.

Alternatively, use the LICENSES table in Management Console. On your database Overview page, click the License tab to view information about your installed licenses.

Viewing your license compliance

If your license includes a raw data size allowance, OpenText™ Analytics Database periodically audits your database's size to ensure it remains compliant with the license agreement. If your license has a term limit, the database also periodically checks to see if the license has expired. You can see the result of the latest audits using the GET_COMPLIANCE_STATUS function.


=> select GET_COMPLIANCE_STATUS();
                       GET_COMPLIANCE_STATUS
---------------------------------------------------------------------------------
 Raw Data Size: 2.00GB +/- 0.003GB
 License Size : 4.000GB
 Utilization  : 50%
 Audit Time   : 2011-03-09 09:54:09.538704+00
 Compliance Status : The database is in compliance with respect to raw data size.
 License End Date: 04/06/2011
 Days Remaining: 28.59
(1 row)

To see how your ORC/Parquet data is affecting your license compliance, see Viewing license compliance for Hadoop file formats.

Viewing your license status through MC

Information about license usage is on the Settings page. See Monitoring database size for license compliance.

Admin: Viewing license compliance for Hadoop file formats

Mon, 01 Jan 0001 00:00:00 +0000

You can use the EXTERNAL_TABLE_DETAILS system table to gather information about all of your tables based on Hadoop file formats. This information can help you understand how much of your license's data allowance is used by ORC and Parquet-based data.

The database computes the values in this table at query time, so to avoid performance problems, restrict your queries to filter by table_schema, table_name, or source_format. These three columns are the only columns you can use in a predicate, but you may use all of the usual predicate operators.

=> SELECT * FROM EXTERNAL_TABLE_DETAILS
    WHERE source_format = 'PARQUET' OR source_format = 'ORC';
-[ RECORD 1 ]---------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
schema_oid            | 45035996273704978
table_schema          | public
table_oid             | 45035996273760390
table_name            | ORC_demo
source_format         | ORC
total_file_count      | 5
total_file_size_bytes | 789
source_statement      | COPY FROM 'ORC_demo/*' ORC
file_access_error     |
-[ RECORD 2 ]---------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
schema_oid            | 45035196277204374
table_schema          | public
table_oid             | 45035996274460352
table_name            | Parquet_demo
source_format         | PARQUET
total_file_count      | 3
total_file_size_bytes | 498
source_statement      | COPY FROM 'Parquet_demo/*' PARQUET
file_access_error     |

When computing the size of an external table, OpenText™ Analytics Database counts all data found in the location specified by the COPY FROM clause. If you have a directory that contains ORC and delimited files, for example, and you define your external table with "COPY FROM *" instead of "COPY FROM *.orc", this table includes the size of the delimited files. (You would probably also encounter errors when querying that external table.) When you query this table, the database does not validate your table definition; it just uses the path to find files to report.

You can also use the AUDIT function to find the size of a specific table or schema. When using the AUDIT function on ORC or PARQUET external tables, the error tolerance and confidence level parameters are ignored. Instead, the AUDIT always returns the size of the ORC or Parquet files on disk.

=> select AUDIT('customers_orc');
   AUDIT
-----------
 619080883
(1 row)

Admin: Moving a cloud installation from by the hour (BTH) to bring your own license (BYOL)

Mon, 01 Jan 0001 00:00:00 +0000

OpenText™ Analytics Database offers two licensing options for some of the entries in the Amazon Web Services Marketplace and Google Cloud Marketplace:

Bring Your Own License (BYOL): a long-term license that you obtain through an online licensing portal.
Vertica by the Hour (BTH): a pay-as-you-go environment where you are charged an hourly fee for both the use of Vertica and the cost of the instances it runs on. The Vertica by the hour deployment offers an alternative to purchasing a term license. If you want to crunch large volumes of data within a short period of time, this option might work better for you. The BTH license is automatically applied to all clusters you create using a BTH MC instance.

If you start out with an hourly license, you can later decide to use a long-term license for your database. The support for an hourly versus a long-term license is built into the instances running your database. To move your database from an hourly license to a long-term license, you must create a new database cluster with a new set of instances.

To move from an hourly to a long-term license, follow these steps:

Purchase a BYOL license. Follow the process described in Obtaining a license key file.
Apply the new license to your database.
Shut down your database.
Create a new database cluster using a BYOL marketplace entry.
Revive your database onto the new cluster.

The exact steps you must take depend on your database mode and your preferred tool for managing your database:

Eon Mode databases: Use either the command line or Management Console.
Enterprise Mode databases: Use the command line to switch licenses.

Moving an Eon Mode database from BTH to BYOL using the command line

Follow these steps to move an Eon Mode database from an hourly to a long-term license.

Obtain a long-term BYOL license from the online licensing portal, described in Obtaining a license key file.Upload the license file to a node in your database. Note the absolute path in the node's filesystem, as you will need this later when installing the license.Connect to the node you uploaded the license file to in the previous step. Connect to your database using vsql and view the licenses table:

=> SELECT * FROM licenses;

Note the name of the hourly license listed in the NAME column, so you can check if it is still present later.

Install the license in the database using the INSTALL_LICENSE function with the absolute path to the license file you uploaded in step 2:

=> SELECT install_license('absolute path to BYOL license');

View the licenses table again:

=> SELECT * FROM licenses;

If only the new BYOL license appears in the table, skip to step 8. If the hourly license whose name you noted in step 4 is still in the table, copy the name and proceed to step 7.

Call the DROP_LICENSE function to drop the hourly license:

=> SELECT drop_license('hourly license name');

You will need the path for your cluster's communal storage in a later step. If you do not already know the path, you can find this information by executing this query:
```
=> SELECT location_path FROM V_CATALOG.STORAGE_LOCATIONS
   WHERE sharing_type = 'COMMUNAL';
```
Synchronize your database's metadata. See Synchronizing metadata.
Shut down the database by calling the SHUTDOWN function:
```
=> SELECT SHUTDOWN();
```
You now need to create a new BYOL cluster onto which you will revive your database. Deploy a new cluster including a new MC instance using a BYOL entry in the marketplace of your chosen cloud platform. See:
- Deploy MC and AWS resources with a CloudFormation template
- Deploy an MC instance in GCP for Eon Mode
Important
Your new BYOL cluster must have the same number of primary nodes as your existing hourly license cluster.
Revive your database onto the new cluster. For instructions, see Revive with communal storage. Because you created the new cluster using a BYOL entry in the marketplace, the database uses the BYOL you applied earlier.
After reviving the database on your new BYOL cluster, terminate the instances for your hourly license cluster and MC. For instructions, see your cloud provider's documentation.

Moving an Eon Mode database from BTH to BYOL using the MC

Follow this procedure to move to BYOL and revive your database using MC:

Purchase a long-term BYOL license from the online licensing portal, following the steps detailed in Obtaining a license key file. Save the file to a location on your computer.
You now need to install the new license on your database. Log in to MC and click your database in the Recent Databases list.
At the bottom of your database's Overview page, click the License tab.
Under the Installed Licenses list, note the name of the BTH license in the License Name column. You will need this later to check whether it is still present after installing the new long-term license.
In the ribbon at the top of the License History page, click the Install New License button. The Settings: License page opens.
Click the Browse button next to the Upload a new license box.
Locate the license file you obtained in step 1, and click Open.
Click the Apply button on the top right of the page.
Select the checkbox to agree to the EULA terms and click OK.
After the license installs, click the Close button.
Click the License tab at the bottom of the page.
If only the new long-term license appears in the Installed Licenses list, skip to Step 16. If the by-the-hour license also appears in the list, copy down its name from the License Name column.
You must drop the by-the-hour license before you can proceed. At the bottom of the page, click the Query Execution tab.
In the query editor, enter the following statement:
```
SELECT DROP_LICENSE('hourly license name');
```
Click Execute Query. The query should complete indicating that the license has been dropped.
You will need the path for your cluster's communal storage in a later step. If you do not already know the path, you can find this information by executing this query in the Query Execution tab:
```
SELECT location_path FROM V_CATALOG.STORAGE_LOCATIONS
   WHERE sharing_type = 'COMMUNAL';
```
Synchronize your database's metadata. See Synchronizing metadata.
You must now stop your by-the-hour database cluster. At the bottom of the page, click the Manage tab.
In the banner at the top of the page, click Stop Database and then click OK to confirm.
From the Amazon Web Services Marketplace or the Google Cloud Marketplace, deploy a new Vertica Management Console using a BYOL entry. Do not deploy a full cluster. You just need an MC deployment.
Log into your new MC instance and revive the database. See Reviving an Eon Mode database on AWS in MC for detailed instructions.
After reviving the database on your new environment, terminate the instances for your hourly license environment. To do so, on the AWS CloudFormation Stacks page, select the hourly environment's stack (its collection of AWS resources) and click Actions > Delete Stack.

Moving an Enterprise Mode database from hourly to BYOL using backup and restore

Note

Currently, AWS is the only platform supported for Enterprise Mode databases using hourly licenses.

In an Enterprise Mode database, follow this procedure to move to BYOL, and then back up and restore your database:

=> SELECT * FROM licenses;

Note the name of the hourly license listed in the NAME column, so you can check if it is still present later.

Install the license in the database using the INSTALL_LICENSE function with the absolute path to the license file you uploaded in step 2:

=> SELECT install_license('absolute path to BYOL license');

View the licenses table again:

=> SELECT * FROM licenses;

If only the new BYOL license appears in the table, skip to step 8. If the hourly license whose name you noted in step 4 is still in the table, copy the name and proceed to step 7.

Call the DROP_LICENSE function to drop the hourly license:

=> SELECT drop_license('hourly license name');

Back up the database. See Backing up and restoring the database.
Deploy a new cluster for your database using one of the BYOL entries in the Amazon Web Services Marketplace.
Restore the database from the backup you created earlier. See Backing up and restoring the database. When you restore the database, it will use the BYOL you loaded earlier.
After restoring the database on your new environment, terminate the instances for your hourly license environment. To do so, on the AWS CloudFormation Stacks page, select the hourly environment's stack (its collection of AWS resources) and click Actions > Delete Stack.

After completing one of these procedures, see Viewing your license status to confirm the license drop and install were successful.

Admin: Auditing database size

Mon, 01 Jan 0001 00:00:00 +0000

You can use your OpenText™ Analytics Database software until columnar data reaches the maximum raw data size that your license agreement allows. The database periodically runs an audit of the columnar data size to verify that your database complies with this agreement. You can also run your own audits of database size with two functions:

AUDIT: Estimates the raw data size of a database, schema, or table.
AUDIT_FLEX: Estimates the size of one or more flexible tables in a database, schema, or projection.

The following two examples audit the database and one schema:

=> SELECT AUDIT('', 'database');
  AUDIT
----------
 76376696
(1 row)

=> SELECT AUDIT('online_sales', 'schema');
  AUDIT
----------
 35716504
(1 row)

Raw data size

AUDIT and AUDIT_FLEX use statistical sampling to estimate the raw data size of data stored in tables—that is, the uncompressed data that the database stores. For most data types, the database evaluates the raw data size as if the data were exported from the database in text format, rather than as compressed data. For details, see Evaluating Data Type Footprint.

By using statistical sampling, the audit minimizes its impact on database performance. The tradeoff between accuracy and performance impact is a small margin of error. Reports on your database size include the margin of error, so you can assess the accuracy of the estimate.

Data in ORC and Parquet-based external tables are also audited whether they are stored locally in the database cluster's file system or remotely in S3 or on a Hadoop cluster. AUDIT always uses the file size of the underlying data files as the amount of data in the table. For example, suppose you have an external table based on 1GB of ORC files stored in HDFS. Then an audit of the table reports it as being 1GB in size.

Note

The database audit does not verify that these files contain actual ORC or Parquet data. It just checks the size of the files that correspond to the external table definition.

Unaudited data

Table data that appears in multiple projections is counted only once. An audit also excludes the following data:

Temporary table data.
Data in SET USING columns.
Non-columnar data accessible through external table definitions. Data in columnar formats such as ORC and Parquet count against your totals.
Data that was deleted but not yet purged.
Data stored in system and work tables such as monitoring tables, Data collector tables, and Database Designer tables.
Delimiter characters.

Evaluating data type footprint

The database evaluates the footprint of different data types as follows:

Strings and binary types—CHAR, VARCHAR, BINARY, VARBINARY—are counted as their actual size in bytes using UTF-8 encoding.
Numeric data types are evaluated as if they were printed. Each digit counts as a byte, as does any decimal point, sign, or scientific notation. For example, -123.456 counts as eight bytes—six digits plus the decimal point and minus sign.
Date/time data types are evaluated as if they were converted to text, including hyphens, spaces, and colons. For example, vsql prints a timestamp value of 2011-07-04 12:00:00 as 19 characters, or 19 bytes.
Complex types are evaluated as the sum of the sizes of their component parts. An array is counted as the total size of all elements, and a ROW is counted as the total size of all fields.

Controlling audit accuracy

AUDIT can specify the level of an audit's error tolerance and confidence, by default set to 5 and 99 percent, respectively. For example, you can obtain a high level of audit accuracy by setting error tolerance and confidence level to 0 and 100 percent, respectively. Unlike estimating raw data size with statistical sampling, the database dumps all audited data to a raw format to calculate its size.

Caution

It is discouraged to perform database-wide audits at this level. Doing so can have a significant adverse impact on database performance.

The following example audits the database with 25% error tolerance:

=> SELECT AUDIT('', 25);
  AUDIT
----------
 75797126
(1 row)

The following example audits the database with 25% level of tolerance and 90% confidence level:

=> SELECT AUDIT('',25,90);
  AUDIT
----------
 76402672
(1 row)

Note

These accuracy settings have no effect on audits of external tables based on ORC or Parquet files. Audits of external tables based on these formats always use the file size of ORC or Parquet files.

Admin: Monitoring database size for license compliance

Mon, 01 Jan 0001 00:00:00 +0000

Your OpenText™ Analytics Database license can include a data storage allowance. The allowance can consist of data in columnar tables, flex tables, or both types of data. The AUDIT() function estimates the columnar table data size and any flex table materialized columns. The AUDIT_FLEX() function estimates the amount of __raw__ column data in flex or columnar tables. In regards to license data limits, data in __raw__ columns is calculated at 1/10th the size of structured data. Monitoring data sizes for columnar and flex tables lets you plan either to schedule deleting old data to keep your database in compliance with your license, or to consider a license upgrade for additional data storage.

Note

An audit of columnar data includes flex table real and materialized columns, but not __raw__ column data.

Viewing your license compliance status

The database periodically runs an audit of the columnar data size to verify that your database is compliant with your license terms. You can view the results of the most recent audit by calling the GET_COMPLIANCE_STATUS function.


=> select GET_COMPLIANCE_STATUS();
                       GET_COMPLIANCE_STATUS
---------------------------------------------------------------------------------
 Raw Data Size: 2.00GB +/- 0.003GB
 License Size : 4.000GB
 Utilization  : 50%
 Audit Time   : 2011-03-09 09:54:09.538704+00
 Compliance Status : The database is in compliance with respect to raw data size.
 License End Date: 04/06/2011
 Days Remaining: 28.59
(1 row)

Periodically running GET_COMPLIANCE_STATUS to monitor your database's license status is usually enough to ensure that your database remains compliant with your license. If your database begins to near its columnar data allowance, you can use the other auditing functions described below to determine where your database is growing and how recent deletes affect the database size.

Manually auditing columnar data usage

You can manually check license compliance for all columnar data in your database using the AUDIT_LICENSE_SIZE function. This function performs the same audit that the database periodically performs automatically. The AUDIT_LICENSE_SIZE check runs in the background, so the function returns immediately. You can then query the results using GET_COMPLIANCE_STATUS.

Note

When you audit columnar data, the results include any flex table real and materialized columns, but not data in the __raw__ column. Materialized columns are virtual columns that you have promoted to real columns. Columns that you define when creating a flex table, or which you add with ALTER TABLE...ADD COLUMN statements are real columns. All __raw__ columns are real columns. However, since they consist of unstructured or semi-structured data, they are audited separately.

An alternative to AUDIT_LICENSE_SIZE is to use the AUDIT function to audit the size of the columnar tables in your entire database by passing an empty string to the function. This function operates synchronously, returning when it has estimated the size of the database.

=> SELECT AUDIT('');
  AUDIT
----------
 76376696
(1 row)

The size of the database is reported in bytes. The AUDIT function also allows you to control the accuracy of the estimated database size using additional parameters. See the entry for the AUDIT function for full details. The database does not count the AUDIT function results as an official audit. It takes no license compliance actions based on the results.

Note

The results of the AUDIT function do not include flex table data in __raw__ columns. Use the AUDIT_FLEX function to monitor data usage flex tables.

Manually auditing raw column data

You can use the AUDIT_FLEX function to manually audit data usage for flex or columnar tables with a __raw__ column. The function calculates the encoded, compressed data stored in ROS containers for any __raw__ columns. Materialized columns in flex tables are calculated by the AUDIT function. The AUDIT_FLEX results do not include data in the __raw__ columns of temporary flex tables.

Targeted auditing

If audits determine that the columnar table estimates are unexpectedly large, consider schemas, tables, or partitions that are using the most storage. You can use the AUDIT function to perform targeted audits of schemas, tables, or partitions by supplying the name of the entity whose size you want to find. For example, to find the size of the online_sales schema in the VMart example database, run the following command:

=> SELECT AUDIT('online_sales');
  AUDIT
----------
 35716504
(1 row)

You can also change the granularity of an audit to report the size of each object in a larger entity (for example, each table in a schema) by using the granularity argument of the AUDIT function. See the AUDIT function.

Using Management Console to monitor license compliance

You can also get information about data storage of columnar data (for columnar tables and for materialized columns in flex tables) through the Management Console. This information is available in the database Overview page, which displays a grid view of the database's overall health.

The needle in the license meter adjusts to reflect the amount used in megabytes.
The grace period represents the term portion of the license.
The Audit button returns the same information as the AUDIT() function in a graphical representation.
The Details link within the License grid (next to the Audit button) provides historical information about license usage. This page also shows a progress meter of percent used toward your license limit.

Admin: Managing license warnings and limits

Mon, 01 Jan 0001 00:00:00 +0000

Term license warnings and expiration

The term portion of an OpenText™ Analytics Database license is easy to manage—you are licensed to use the database until a specific date. If the term of your license expires, you are alerted with messages appearing in the Administration tools and vsql. For example:

=> CREATE TABLE T (A INT);
NOTICE 8723: Vertica license 432d8e57-5a13-4266-a60d-759275416eb2 is in its grace period; grace period expires in 28 days
HINT: Renew at https://softwaresupport.softwaregrp.com/
CREATE TABLE

Contact OpenText at https://softwaresupport.softwaregrp.com/ as soon as possible to renew your license, and then install the new license. After the grace period expires, the database stops processing DML queries and allows DDL queries with a warning message. If a license expires and one or more valid alternative licenses are installed, the database uses the alternative licenses.

Data size license warnings and remedies

If your database columnar license includes a raw data size allowance, the database periodically audits the size of your database to ensure it remains compliant with the license agreement. For details of this audit, see Auditing database size. You should also monitor your database size to know when it will approach licensed usage. Monitoring the database size helps you plan to either upgrade your license to allow for continued database growth or delete data from the database so you remain compliant with your license. See Monitoring database size for license compliance for details.

If your database's size approaches your licensed usage allowance (above 75% of license limits), you will see warnings in the Administration tools , vsql, and Management Console. You have two options to eliminate these warnings:

Upgrade your license to a larger data size allowance.
Delete data from your database to remain under your licensed raw data size allowance. The warnings disappear after the next audit of the database size shows that it is no longer close to or over the licensed amount. You can also manually run a database audit (see Monitoring database size for license compliance for details).

If your database continues to grow after you receive warnings that its size is approaching your licensed size allowance, additional warnings are displayed in more parts of the system after a grace period passes. Use the GET_COMPLIANCE_STATUS function to check the status of your license.

If your premium edition database size exceeds your licensed limits

If your Premium Edition database size exceeds your licensed data allowance, all successful queries from ODBC and JDBC clients return with a status of SUCCESS_WITH_INFO instead of the usual SUCCESS. The message sent with the results contains a warning about the database size. Your ODBC and JDBC clients should be prepared to handle these messages instead of assuming that successful requests always return SUCCESS.

Note

These warnings for Premium Edition are in addition to any warnings you see in Administration Tools, vsql, and Management Console.

If your Trial license database size exceeds 1 terabyte

If your Trial license database size exceeds the limit of 1 terabyte, the database stops processing queries.

To bring your database under compliance, you can choose to:

Drop database tables. You can also consider truncating a table or dropping a partition. See TRUNCATE TABLE or DROP_PARTITIONS.
Upgrade to Commercial license.

Admin: Exporting license audit results to CSV

Mon, 01 Jan 0001 00:00:00 +0000

You can use admintools to audit a database for license compliance and export the results in CSV format, as follows:

admintools -t license_audit [--password=password] --database=database] [--file=csv-file] [--quiet]

where:

database must be a running database. If the database is password protected, you must also supply the password.
--file csv-file directs output to the specified file. If csv-file already exists, the tool returns an error message. If this option is unspecified, output is directed to stdout.
--quiet specifies that the tool should run in quiet mode; if unspecified, status messages are sent to stdout.

Running the license_audit tool is equivalent to invoking the following SQL statements:


select audit('');
select audit_flex('');
select * from dc_features_used;
select * from v_catalog.license_audits;
select * from v_catalog.user_audits;

Audit results include the following information:

Log of used database features
Estimated database size
Raw data size allowed by your database license
Percentage of licensed allowance that the database currently uses
Audit timestamps

The following truncated example shows the raw CSV output that license_audit generates:


FEATURES_USED
features_used,feature,date,sum
features_used,metafunction::get_compliance_status,2014-08-04,1
features_used,metafunction::bootstrap_license,2014-08-04,1
...

LICENSE_AUDITS
license_audits,database_size_bytes,license_size_bytes,usage_percent,audit_start_timestamp,audit_end_timestamp,confidence_level_percent,error_tolerance_percent,used_sampling,confidence_interval_lower_bound_bytes,confidence_interval_upper_bound_bytes,sample_count,cell_count,license_name
license_audits,808117909,536870912000,0.00150523690320551,2014-08-04 23:59:00.024874-04,2014-08-04 23:59:00.578419-04,99,5,t,785472097,830763721,10000,174754646,vertica
...

USER_AUDITS
user_audits,size_bytes,user_id,user_name,object_id,object_type,object_schema,object_name,audit_start_timestamp,audit_end_timestamp,confidence_level_percent,error_tolerance_percent,used_sampling,confidence_interval_lower_bound_bytes,confidence_interval_upper_bound_bytes,sample_count,cell_count
user_audits,812489249,45035996273704962,dbadmin,45035996273704974,DATABASE,,VMart,2014-10-14 11:50:13.230669-04,2014-10-14 11:50:14.069057-04,99,5,t,789022736,835955762,10000,174755178

AUDIT_SIZE_BYTES
audit_size_bytes,now,audit
audit_size_bytes,2014-10-14 11:52:14.015231-04,810584417

FLEX_SIZE_BYTES
flex_size_bytes,now,audit_flex
flex_size_bytes,2014-10-14 11:52:15.117036-04,11850

OpenText Analytics Database 26.2.x – Managing licenses

Admin: Obtaining a license key file

Admin: Understanding licenses

Note

Trial license

OpenText™ Analytics Database for SQL on Apache Hadoop license

Admin: Installing or upgrading a license key

Admin: Viewing your license status

Examining your license key

Viewing your license compliance

Viewing your license status through MC

Admin: Viewing license compliance for Hadoop file formats

Admin: Moving a cloud installation from by the hour (BTH) to bring your own license (BYOL)

Moving an Eon Mode database from BTH to BYOL using the command line

Important

Moving an Eon Mode database from BTH to BYOL using the MC

Moving an Enterprise Mode database from hourly to BYOL using backup and restore

Note

Admin: Auditing database size

Raw data size

Note

Unaudited data

Evaluating data type footprint

Controlling audit accuracy

Caution

Note

Admin: Monitoring database size for license compliance

Note

Viewing your license compliance status

Manually auditing columnar data usage

Note

Note

Manually auditing __raw__ column data

Targeted auditing

Using Management Console to monitor license compliance

Admin: Managing license warnings and limits

Term license warnings and expiration

Data size license warnings and remedies

If your premium edition database size exceeds your licensed limits

Note

If your Trial license database size exceeds 1 terabyte

Admin: Exporting license audit results to CSV

Manually auditing raw column data