Check License

This article explains how check the limits and validity of an uploaded license.

This procedure is carried out using ConfD and Exasol Deployment Tool (c4).

Connect to COS

  1. Get the play ID of the deployment using c4 ps. For example:

    Example:
    Copy 
    c4 ps
          
          N  PLAY_ID   NODE  MEDIUM  INSTANCE     DB_VERSION  EXTERNAL_IP     INTERNAL_IP  STAGE  STATE    UPTIME    TTL
      ┌─  1  c3275f84  11    awscf   r5d.large    8.34.0      203.0.113.11    10.0.0.11    d      running  03:50:12  +∞
      │   1  c3275f84  12    awscf   r5d.large    8.34.0      203.0.113.12    10.0.0.12    d      running  03:50:13  +∞
      │   1  c3275f84  13    awscf   r5d.large    8.34.0      203.0.113.13    10.0.0.13    d      running  03:50:13  +∞
      └─  1  c3275f84  14    awscf   r5d.large    8.34.0      203.0.113.14    10.0.0.14    d      running  03:50:13  +∞

  2. Connect to the cluster operating system (COS) using c4 connect -i PLAY_ID -s cos.

    Example:
    Copy 
    ./c4 connect -i c3275f84 -s cos

View license details

To view details about the currently installed license, use the ConfD job license_info.

Example:
Copy 
confd_client license_info

Contract:
  comment: Test license with an expiration date.
  company_name: My Company
  distributor: Exasol
  distributor_id: 1
  expiration_date: '2026-11-05'
  license_id: 1234567890
  schema_version: 1
Limits:
  max_db_mem_size_in_gb: 1500
  max_db_raw_data_size_in_gb: 2000
  max_nodes_per_cluster: 48
  max_num_clusters: 3

Contract:

comment

An optional comment describing the license. This field can be empty.

company_name

The licensee company name.

distributor

The distributor of the license. This is currently always Exasol.

distributor_id

This is currently always 1.

expiration_date

Expiration date for the license in the format YYYY-MM-DD. Unlimited or inf means the license does not expire.

license_id

A unique ID number for the license.

Limits:

max_db_mem_size_in_gb

Used for licenses based on database RAM. This value limits the maximum configurable total database RAM across all databases in the cluster. The limit value is checked against the configured DB RAM at database startup.

This parameter should not be confused with the Database mem size (GiB) limit in an Exasol 7.1 license, which refers to the limit of compressed data that can be stored in a cluster.

To check the configured DB RAM for the database, use the ConfD job db_info.

Example:
Copy 
confd_client db_info db_name: MY_DATABASE
...
  mem_size: 131072
...

max_db_raw_data_size_in_gb

The maximum size of raw (uncompressed) data in GiB that you can store across all databases in the cluster. The raw data volume corresponds to the data volume that is comparable to the size the data would have if stored as CSV files.

Audit data is not counted towards the raw data license limit.

For more details about how raw data size is determined, see Sizing for Data Types and Object Types.

max_num_clusters

The maximum number of running clusters allowed by the license.

Clusters are counted per database. This means that n databases will count as n clusters, even if all databases run on the same set of nodes. For native cloud AWS deployments with multi-cluster support, each main cluster or worker cluster counts as one cluster.

For more details about main and worker clusters, see Database Essentials and Cluster Management.

max_nodes_per_cluster

The maximum number of active nodes on a running cluster. Access node and standby nodes are not counted towards this limit.

Check license limits

To verify that the databases currently running in the cluster do not exceed the limits in the license, use the ConfD job license_run_check. If the command returns OK, the limits of the license are not exceeded.

Copy 
confd_client license_run_check
OK