OpenText Analytics Database 26.2.x – V_CATALOG schema

Sql-Reference: ACCESS_POLICY

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

Provides information about existing access policies.

Column Name	Data Type	Description
ACCESS_POLICY_OID	INTEGER	The unique identifier for the access policy.
TABLE_NAME	VARCHAR	Name of the table specified in the access policy.
IS_POLICY_ENABLED	BOOLEAN	Whether the access policy is enabled.
POLICY_TYPE	VARCHAR	The type of access policy assigned to the table: Column Policy Row Policy
EXPRESSION	VARCHAR	The expression used when creating the access policy.
COLUMN_NAME	VARCHAR	The column to which the access policy is assigned. Row policies apply to all columns in the table.
TRUST_GRANTS	BOOLEAN	If true, GRANT statements override the access policy when determining whether a user can perform DML operations on the column or row.

Privileges

By default, only the superuser can view this table. Superusers can grant non-superusers access to this table with the following statement. Non-superusers can only see rows for tables that they own:

=> GRANT SELECT ON access_policy TO PUBLIC

Examples

The following query returns all access policies on table public.customer_dimension:

=> \x
=> SELECT policy_type, is_policy_enabled, table_name, column_name, expression FROM access_policy WHERE table_name = 'public.customer_dimension';
-[ RECORD 1 ]-----+----------------------------------------------------------------------------------------
policy_type       | Column Policy
is_policy_enabled | Enabled
table_name        | public.customer_dimension
column_name       | customer_address
expression        | CASE WHEN enabled_role('administrator') THEN customer_address ELSE '**************' END

Sql-Reference: ALL_RESTORE_POINTS

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

Provides information about existing restore points.

Column Name	Data Type	Description
RP_ID	INTEGER	The unique identifier for the restore point.
RP_OID	INTEGER	The current identifier of the restore point. This can change if the cluster is restarted.
ARCHIVE_OID	INTEGER	The identifier for the archive.
STATE	VARCHAR	Can be one of the following states: SAVING COMPLETE REMOVING
SAVE_TIME	VARCHAR	The time at which the restore point was saved.
CATALOG_VERSION	VARCHAR	The catalog version that was saved.
VERTICA_VERSION	VARCHAR	The version of OpenText™ Analytics Database for the restore point.

Sql-Reference: ALL_TABLES

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

Provides summary information about tables in an OpenText™ Analytics Database.

Column Name	Data Type	Description
`SCHEMA_NAME`	VARCHAR	The name of the schema that contains the table.
`TABLE_ID`	INTEGER	Catalog-assigned numeric value that uniquely identifies the table.
`TABLE_NAME`	VARCHAR	The table name.
`TABLE_TYPE`	VARCHAR	The type of table, which can be one of the following: TABLE SYSTEM TABLE VIEW GLOBAL TEMPORARY LOCAL TEMPORARY
`REMARKS`	VARCHAR	A brief comment about the table. You define this field by using the COMMENT ON TABLE and COMMENT ON VIEW commands.

Examples

onenode=> SELECT DISTINCT table_name, table_type FROM all_tables
          WHERE table_name ILIKE 't%';
       table_name       |  table_type
------------------------+--------------
 types                  | SYSTEM TABLE
 trades                 | TABLE
 tuple_mover_operations | SYSTEM TABLE
 tables                 | SYSTEM TABLE
 tuning_recommendations | SYSTEM TABLE
 testid                 | TABLE
 table_constraints      | SYSTEM TABLE
 transactions           | SYSTEM TABLE
(8 rows)
onenode=> SELECT table_name, table_type FROM all_tables
          WHERE table_name ILIKE 'my%';
 table_name | table_type
------------+------------
 mystocks   | VIEW
(1 row)
=> SELECT * FROM all_tables LIMIT 4;
-[ RECORD 1 ]-------------------------------------------
schema_name | v_catalog
table_id    | 10206
table_name  | all_tables
table_type  | SYSTEM TABLE
remarks     | A complete listing of all tables and views
-[ RECORD 2 ]-------------------------------------------
schema_name | v_catalog
table_id    | 10000
table_name  | columns
table_type  | SYSTEM TABLE
remarks     | Table column information
-[ RECORD 3 ]-------------------------------------------
schema_name | v_catalog
table_id    | 10054
table_name  | comments
table_type  | SYSTEM TABLE
remarks     | User comments on catalog objects
-[ RECORD 4 ]-------------------------------------------
schema_name | v_catalog
table_id    | 10134
table_name  | constraint_columns
table_type  | SYSTEM TABLE
remarks     | Table column constraint information

Sql-Reference: AUDIT_MANAGING_USERS_PRIVILEGES

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

Provides summary information about privileges, creating, modifying, and deleting users, and authentication changes. This table is a join of LOG_PARAMS, LOG_QUERIES, and LOG_TABLES filtered on the Managing_Users_Privileges category.

Column Name	Data Type	Description
ISSUED_TIME	VARCHAR	The time at which the query was executed.
USER_NAME	VARCHAR	Name of the user who issued the query at the time OpenText™ Analytics Database recorded the session.
USER_ID	INTEGER	Numeric representation of the user who ran the query.
HOSTNAME	VARCHAR	The hostname, IP address, or URL of the database server.
SESSION_ID	VARCHAR	Identifier for this session. This identifier is unique within the cluster at any point in time but can be reused when the session closes.
AUDIT_TYPE	VARCHAR	The type of operation for the audit: Query Parameter Table
AUDIT_TAG_NAME	VARCHAR	The tag name for the specific parameter, query, or table.
REQUEST_TYPE	VARCHAR	The type of query request. Examples include, but are not limited to: QUERY DDL LOAD UTILITY TRANSACTION PREPARE EXECUTE SET SHOW
REQUEST_ID	INTEGER	The ID of the privilege request.
SUBJECT	VARCHAR	The name of the table or parameter that was queried or the subject of a query.
REQUEST	VARCHAR	Lists the privilege request.
SUCCESS	VARCHAR	Indicates whether or not the operation was successful.
CATEGORY	VARCHAR	The audit parent category, Managing_Users_Privileges.

Sql-Reference: CA_BUNDLES

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

Stores certificate authority (CA) bundles created by CREATE CA BUNDLE.

Column Name	Data Type	Description
OID	INTEGER	The object identifier.
NAME	VARCHAR	The name of the CA bundle.
OWNER	INTEGER	The OID of the owner of the CA bundle.
CERTIFICATES	INTEGER	The OIDs of the CA certificates inside the CA bundle.

Privileges

See CA bundle OID, name, and owner: Superuser or owner of the CA bundle.
See CA bundle contents: Owner of the bundle

Joining with CERTIFICATES

CA_BUNDLES only stores OIDs. Since operations on CA bundles require certificate and owner names, you can use the following query to map bundles to certificate and owner names:

=> SELECT user_name AS owner_name,
       owner     AS owner_oid,
       b.name    AS bundle_name,
       c.name    AS cert_name
FROM   (SELECT name,
               STRING_TO_ARRAY(certificates) :: array[INT] AS certs
        FROM   ca_bundles) b
       LEFT JOIN certificates c
              ON CONTAINS(b.certs, c.oid)
       LEFT JOIN users
              ON user_id = owner
ORDER  BY 1;

 owner_name |     owner_oid     | bundle_name  | cert_name
------------+-------------------+--------------+-----------
 dbadmin    | 45035996273704962 | ca_bundle    | root_ca
 dbadmin    | 45035996273704962 | ca_bundle    | ca_cert
(2 rows)

Sql-Reference: CATALOG_SUBSCRIPTION_CHANGES

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

Lists the changes made to catalog subscriptions.

Column Name	Data Type	Description
`EVENT_TIMESTAMP`	TIMESTAMP	The time a catalog subscription changed.
`SESSION_ID`	VARCHAR	A unique numeric ID assigned by the OpenText™ Analytics Database catalog, which identifies the session for which profiling information is captured. This identifier is unique within the cluster at any point in time but can be reused when the session closes.
`USER_ID`	INTEGER	A unique numeric ID assigned by the database catalog, which identifies the user.
`USER_NAME`	VARCHAR	The user who made changes to the subscriptions.
`TRANSACTION_ID`	INTEGER	Identifier for the transaction within the session, if any. If a session is active but no transaction has begun, TRANSACTION_ID returns NULL.
`SHARD_NAME`	VARCHAR	The name of the shard.
`SHARD_OID`	INTEGER	The OID of the shard.
`SUBSCRIBER_NODE_NAME`	VARCHAR	The node name or names subscribed to the shard.
`SUBSCRIBER_NODE_OID`	INTEGER	The OID of the subscribing node or nodes.
`OLD_STATE`	VARCHAR	The previous state of the node subscription.
`NEW_STATE`	VARCHAR	The current state of the node subscription.
`WAS_PRIMARY`	BOOLEAN	Defines whether the node was the primary subscriber.
`IS_PRIMARY`	BOOLEAN	Defines whether the node is currently the primary subscriber.
`CATALOG_VERSION`	INTEGER	The version of the catalog at the time of the subscription change.

Sql-Reference: CATALOG_SYNC_STATE

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

Shows when an Eon Mode database node synchronized its catalog to communal storage.

Column Name	Data Type	Description
NODE_NAME	VARCHAR	The node name for which information is listed.
SYNC_CATALOG_VERSION	INTEGER	The version number of the catalog being synchronized.
EARLIEST_CHECKPOINT_VERSION	INTEGER	The earliest checkpoint that is maintained in communal storage.
SYNC_TRAILING_INTERVAL	INTEGER	The difference between the global catalog version and the synchronized catalog version for a node.
LAST_SYNC_AT	TIMESTAMPTZ	The date and time the last time the catalog was synchronized.

Sql-Reference: CATALOG_TRUNCATION_STATUS

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

Indicates how up to date the catalog is on communal storage. It is completely up to date when the current catalog version is the same as the catalog truncation version.

The catalog truncation version (CTV) is the version that OpenText™ Analytics Database cluster uses when it revives after a crash, shutdown, or hibernation. A cluster has only one CTV for all nodes in a cluster.

Column Name	Data Type	Description
CURRENT_CATALOG_VERSION	INTEGER	The version number of the catalog currently on the cluster.
TRUNCATION_CATALOG_VERSION	INTEGER	The version number as of the last time the catalog was synced on communal storage.

Sql-Reference: CERTIFICATES

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

Stores certificates created by CREATE CERTIFICATE.

Column Name	Data Type	Description
OID	INTEGER	The object identifier.
NAME	VARCHAR	The name of the certificate.
OWNER	INTEGER	The owner of the object.
SIGNED_BY	INTEGER	The OID of the signing certificate.
PRIVATE_KEY	INTEGER	The OID of the certificate's private key.
START_DATE	TIMESTAMPTZ	When the certificate becomes valid.
EXPIRATION_DATE	TIMESTAMPTZ	When the certificate expires.
ISSUER	VARCHAR	The signing CA.
SUBJECT	VARCHAR	The entity for which the certificate is issued.
SERIAL	VARCHAR	The certificate's serial number.
x509v3_EXTENSIONS	VARCHAR	Lists additional attributes specified during the certificate's creation. For more information on extensions, see the OpenSSL documentation.
CERTIFICATE_TEXT	VARCHAR	The contents of the certificate.

Examples

See Generating TLS certificates and keys.

Sql-Reference: CLIENT_AUTH

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

Provides information about client authentication methods.

Higher values indicate higher priorities. OpenText™ Analytics Database tries to authenticate a user with an authentication method in order of priority from highest to lowest. For example:

A priority of 10 is higher than a priority of 5.
A priority 0 is the lowest possible value.

Column Name	Data Type	Description
AUTH_OID	INTEGER	Unique identifier for the authentication method.
AUTH_NAME	VARCHAR	User-given name of the authentication method.
IS_AUTH_ENABLED	BOOLEAN	Indicates if the authentication method is enabled.
AUTH_HOST_TYPE	VARCHAR	The authentication host type, one of the following: LOCAL HOST HOSTSSL HOSTNOSSL
AUTH_HOST_ADDRESS	VARCHAR	If AUTH_HOST_TYPE is HOST, AUTH_HOST_ADDRESS is the IP address (or address range) of the remote host.
AUTH_METHOD	VARCHAR	Authentication method to be used. Valid values: IDENT GSS HASH LDAP REJECT TLS TRUST
AUTH_PARAMETERS	VARCHAR	The parameter names and values assigned to the authentication method.
AUTH_PRIORITY	INTEGER	The priority specified for the authentication. Authentications with higher values are used first.
METHOD_PRIORITY	INTEGER	The priority of this authentication based on the AUTH_METHOD. The database only considers METHOD_PRIORITY when deciding between multiple authentication methods of equal AUTH_PRIORITY.
ADDRESS_PRIORITY	INTEGER	The priority of this authentication based on the specificity of the AUTH_HOST_ADDRESS, if any. More specific IP addresses (fewer zeros) are used first. The database only considers ADDRESS_PRIORITY when deciding between multiple authentication methods of equal AUTH_PRIORITY and METHOD_PRIORITY.
IS_FALLTHROUGH_ENABLED	Boolean	Whether authentication fallthrough is enabled.

Examples

This example shows how to get information about each client authentication method that you created:

=> SELECT * FROM client_auth;
    auth_oid   |  auth_name  | is_auth_enabled | auth_host_type | auth_host_address | auth_method | auth_parameters | auth_priority | method_priority | address_priority
-------------------+-------------+-----------------+----------------+-------------------+-------------+-----------------+---------------+-----------------+------------------
 45035996274059694 | v_gss       | True            | HOST           | 0.0.0.0/0         | GSS         |                 |             0 |               5 |               96
 45035996274059696 | v_trust     | True            | LOCAL          |                   | TRUST       |                 |             0 |               0 |                0
 45035996274059698 | v_ldap      | True            | HOST           | 10.19.133.123/    | LDAP        |                 |             0 |               5 |              128
 45035996274059700 | RejectNoSSL | True            | HOSTNOSSL      | 0.0.0.0/0         | REJECT      |                 |             0 |              10 |               96
 45035996274059702 | v_hash      | True            | LOCAL          |                   | HASH        |                 |             0 |               2 |                0
 45035996274059704 | v_tls       | True            | HOSTSSL        | 1.1.1.1/0         | TLS         |                 |             0 |               5 |               96
(6 rows)

Sql-Reference: CLIENT_AUTH_PARAMS

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

Provides information about client authentication methods that have parameter values assigned.

Column Name	Data Type	Description
AUTH_OID	INTEGER	A unique identifier for the authentication method.
AUTH_NAME	VARCHAR	Name that you defined for the authentication method.
AUTH_PARAMETER_NAME	VARCHAR	Parameter name required by the authentication method. Some examples are: system_users binddn_prefix host
AUTH_PARAMETER_VALUE	VARCHAR	Value of the specified parameter.

Examples

This example shows how to retrieve parameter names and values for all authentication methods that you created. The authentication methods that have parameters are:

v_ident
v_ldap
v_ldap1

=> SELECT * FROM CLIENT_AUTH_PARAMS;
     auth_oid      |   auth_name   | auth_parameter_name |    auth_parameter_value
-------------------+---------------+---------------------+------------------------------
 45035996273741304 | v_ident       | system_users        | root
 45035996273741332 | v_gss         |                     |
 45035996273741350 | v_password    |                     |
 45035996273741368 | v_trust       |                     |
 45035996273741388 | v_ldap        | host                | ldap://172.16.65.177
 45035996273741388 | v_ldap        | binddn_prefix       | cn=
 45035996273741388 | v_ldap        | binddn_suffix       | ,dc=qa_domain,dc=com
 45035996273741406 | RejectNoSSL   |                     |
 45035996273741424 | RejectWithSSL |                     |
 45035996273741450 | v_md5         |                     |
 45035996273904044 | l_tls         |                     |
 45035996273906566 | v_hash        |                     |
 45035996273910432 | v_ldap1       | host                | ldap://172.16.65.177
 45035996273910432 | v_ldap1       | basedn              | dc=qa_domain,dc=com
 45035996273910432 | v_ldap1       | binddn              | cn=Manager,dc=qa_domain,dc=com
 45035996273910432 | v_ldap1       | bind_password       | secret
 45035996273910432 | v_ldap1       | search_attribute    | cn
(17 rows)

Sql-Reference: CLUSTER_LAYOUT

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

Shows the relative position of the actual arrangement of the nodes participating in the cluster and the fault groups (in an Enterprise Mode database) or subclusters (in an Eon Mode database) that affect them. Ephemeral nodes are not shown in the cluster layout ring because they hold no resident data.

Column Name	Data Type	Description
CLUSTER_POSITION	INTEGER	Position of the node in the cluster ring, counting forward from 0. Note An output value of 0 has no special meaning other than there are no nodes in position before the node assigned 0.
NODE_ID	INTEGER	A unique numeric ID assigned by the OpenText™ Analytics Database catalog that identifies the node.
NODE_NAME	VARCHAR	The name of the node in the cluster ring. Only permanent nodes participating in database activity appear in the cluster layout. Ephemeral nodes are not shown in the output.
FAULT_GROUP_ID	INTEGER	A unique numeric ID assigned by the database catalog that identifies the fault group. This column can only have a value in an Enterprise Mode database. Note This value matches the `FAULT_GROUP.MEMBER_ID` value, but only if this node is in a fault group; otherwise the value is NULL.
FAULT_GROUP_NAME	VARCHAR	The name of the fault group for the node. This column can only have a value in an Enterprise Mode database.
FAULT_GROUP_TIER	INTEGER	The node's depth in the fault group tree hierarchy. For example if the node: Is not in a fault group, output is null Is in the top level fault group, output is 0 Is in a fault group's child, output is 1 Is a fault group's grandchild, output is 2 This column can only have a value in an Enterprise Mode database.
SUBCLUSTER_ID	INTEGER	Unique identifier for the subcluster. This column only has a value in an Eon Mode database.
SUBCLUSTER_NAME	VARCHAR	The name of the subcluster containing the node. This column only has a value in an Eon Mode database.

Sql-Reference: COLUMNS

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

Provides table column information. For columns of Iceberg external tables, see ICEBERG_COLUMNS.

Column Name	Data Type	Description
`TABLE_ID`	INTEGER	Catalog-assigned numeric value that uniquely identifies the table.
`TABLE_NAMESPACE`	VARCHAR	For Eon Mode databases, name of the namespace that contains the table.
`TABLE_SCHEMA`	VARCHAR	Name of the table's schema. If the schema belongs to a non-default namespace in an Eon Mode database, the schema name is front-qualified with the name of the schema's namespace. For example, `n1.s` refers to schema `s` in namespace `n1`.
`TABLE_NAME`	VARCHAR	Name of the table containing the column.
`IS_SYSTEM_TABLE`	BOOLEAN	Whether the table is a system table.
`COLUMN_ID`	VARCHAR	Catalog-assigned VARCHAR value that uniquely identifies a table column.
`COLUMN_NAME`	VARCHAR	Name of the column.
`DATA_TYPE`	VARCHAR	Column data type. Arrays of primitive types show the name `ARRAY[``type``]`. Other complex types show the inline name of the type, which matches the `type_name` value in the COMPLEX_TYPES table. For example: `_ct_45035996273833610`.
`DATA_TYPE_ID`	INTEGER	Catalog-assigned unique numeric ID of the data type.
`DATA_TYPE_LENGTH`	INTEGER	Maximum allowable length of the data type.
`CHARACTER_MAXIMUM_LENGTH`	VARCHAR	Maximum allowable length of a VARCHAR column.
`NUMERIC_PRECISION`	INTEGER	Number of significant decimal digits for a NUMERIC column.
`NUMERIC_SCALE`	INTEGER	Number of fractional digits for a NUMERIC column.
`DATETIME_PRECISION`	INTEGER	Declared precision for a TIMESTAMP column, or NULL if no precision was declared.
`INTERVAL_PRECISION`	INTEGER	Number of fractional digits retained in the seconds field of an INTERVAL column.
`ORDINAL_POSITION`	INTEGER	Column position respective to other columns in the table.
`IS_NULLABLE`	BOOLEAN	Whether the column can contain NULL values.
`COLUMN_DEFAULT`	VARCHAR	Expression set on a column with the DEFAULT constraint.
`COLUMN_SET_USING`	VARCHAR	Expression set on a column with the SET USING constraint.
`IS_IDENTITY`	BOOLEAN	Whether the column is an IDENTITY column.

Examples

=> SELECT table_schema, table_name, column_name, data_type, is_nullable
   FROM columns WHERE table_schema = 'store'
   AND data_type = 'Date';
 table_schema |    table_name     |      column_name       | data_type | is_nullable
--------------+-------------------+------------------------+-----------+-------------
 store        | store_dimension   | first_open_date        | Date      | f
 store        | store_dimension   | last_remodel_date      | Date      | f
 store        | store_orders_fact | date_ordered           | Date      | f
 store        | store_orders_fact | date_shipped           | Date      | f
 store        | store_orders_fact | expected_delivery_date | Date      | f
 store        | store_orders_fact | date_delivered         | Date      | f
6 rows)

In the following query, datetime_precision is NULL because the table definition declares no precision:

=> CREATE TABLE c (c TIMESTAMP);
CREATE TABLE
=> SELECT table_name, column_name, datetime_precision FROM columns
   WHERE table_name = 'c';
 table_name | column_name | datetime_precision
------------+-------------+--------------------
 c          | c           |
(1 row)

In the following example, timestamp precision is set:

=> DROP TABLE c;
=> CREATE TABLE c (c TIMESTAMP(4));
CREATE TABLE
=> SELECT table_name, column_name, datetime_precision FROM columns
   WHERE table_name = 'c';
 table_name | column_name | datetime_precision
------------+-------------+--------------------
 c          | c           |                  4

An IDENTITY column sequence is defined in a table's DDL. Column values automatically increment as new rows are added. The following query returns identity columns:

=> CREATE TABLE employees (employeeID IDENTITY, fname varchar(36), lname varchar(36));
CREATE TABLE
=> SELECT table_name, column_name, is_identity FROM columns WHERE is_identity = 't';
 table_name | column_name | is_identity
------------+-------------+-------------
 employees  | employeeID  | t
(1 row)

You can query the SEQUENCES table to get detailed information about an IDENTITY column sequence:

=> SELECT sequence_schema, sequence_name, identity_table_name, sequence_id FROM sequences WHERE identity_table_name ='employees';
 sequence_schema |      sequence_name       | identity_table_name |    sequence_id
-----------------+--------------------------+---------------------+-------------------
 public          | employees_employeeID_seq | employees           | 45035996273848816
(1 row)

For details about sequences and IDENTITY columns, see Sequences.

Sql-Reference: COMMENTS

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

Returns information about comments associated with objects in the database.

Note

Queries on this table can be slow because it fetches data at query time from other OpenText™ Analytics Database catalog tables.

Column Name	Data Type	Description
COMMENT_ID	INTEGER	Comment's internal ID number
OBJECT_ID	INTEGER	Internal ID number of the object associated with the comment.
OBJECT_TYPE	VARCHAR	Type of object associated with the comment, one of the following: COLUMN CONSTRAINT FUNCTION LIBRARY NODE PROJECTION SCHEMA SEQUENCE TABLE VIEW
OBJECT_SCHEMA	VARCHAR	Name of the schema containing the object.
OBJECT_NAME	VARCHAR	Name of the top-level object associated with the comment, such as a table or projection.
CHILD_OBJECT	VARCHAR	Name of the specific object associated with the comment, such as a table column. If the comment is associated with a top-level object, this value is NULL.
OWNER_ID	VARCHAR	Internal ID of the object's owner.
OWNER_NAME	VARCHAR	Object owner's name.
CREATION_TIME	TIMESTAMPTZ	When the comment was created.
LAST_MODIFIED_TIME	TIMESTAMPTZ	When the comment was last modified.
COMMENT	VARCHAR	Comment text.

Examples

=> COMMENT ON COLUMN public.t.x1 IS 'Column comment';

=> SELECT * FROM COMMENTS;
-[ RECORD 1 ]------+------------------------------
comment_id | 45035996273838776
object_id | 45035996273838760
object_type | COLUMN
object_schema | public
object_name | t
child_object | x1
owner_id | 45035996273704962
owner_name | dbadmin
creation_time | 2023-02-01 10:47:13.028663+08
last_modified_time | 2023-02-01 10:47:13.028663+08
comment | Column comment

Sql-Reference: COMPLEX_TYPES

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

Contains information about inlined complex types.

Each complex type in each external table has a unique type internally, even if the types are structurally the same (like two different ROW(int,int) cases). This inlined type is created when the table using it is created and is automatically dropped when the table is dropped. Inlined complex types cannot be shared or reused in other tables.

Each row in the COMPLEX_TYPES table represents one component (field) in one complex type. A ROW produces one row per field, an ARRAY produces one, and a MAP produces two.

Arrays of primitive types used in native (ROS) tables are not included in the COMPLEX_TYPES table. They are included instead in the TYPES table.

This table does not include complex types in Iceberg tables.

Column Name	Data Type	Description
`TYPE_ID`	INTEGER	A unique identifier for the inlined complex type.
`TYPE_KIND`	VARCHAR	The specific kind of complex type: row, array, or map.
`TYPE_NAME`	VARCHAR	The generated name of this type. All names begin with _ct_ followed by a number.
`FIELD_ID`	INTEGER	A unique identifier for the field.
`FIELD_NAME`	VARCHAR	The name of the field, if specified in the table definition, or a generated name beginning with "f".
`FIELD_TYPE_NAME`	VARCHAR	The type of the field's value.
`FIELD_POSITION`	INTEGER	The field's position in its containing complex type (0-based).
`FIELD_LENGTH`	INTEGER	Number of bytes in the field value, or -1 if the value is not a scalar type.
`CHARACTER_MAXIMUM_LENGTH`	INTEGER	Maximum allowable length of the column.
`NUMERIC_PRECISION`	INTEGER	Number of significant decimal digits.
`NUMERIC_SCALE`	INTEGER	Number of fractional digits.
`DATETIME_PRECISION`	INTEGER	For `TIMESTAMP` data type, returns the declared precision; returns NULL if no precision was declared.
`INTERVAL_PRECISION`	INTEGER	Number of fractional digits retained in the seconds field.

Examples

The following example shows the type and field values after defining a single external table.

=> CREATE EXTERNAL TABLE warehouse(
    name VARCHAR, id_map MAP<INT,VARCHAR>,
    data row(record INT, total FLOAT, description VARCHAR(100)),
    prices ARRAY[INT], comment VARCHAR(200), sales_total FLOAT, storeID INT)
  AS COPY FROM ... PARQUET;

=> SELECT type_id,type_kind,type_name,field_id,field_name,field_type_name,field_position
    FROM COMPLEX_TYPES ORDER BY type_id,field_name;

      type_id      | type_kind |       type_name       | field_id | field_name  | field_type_name | field_position
-------------------+-----------+-----------------------+----------+-------------+-----------------+----------------
 45035996274278280 | Map       | _ct_45035996274278280 |        6 | key         | int             |              0
 45035996274278280 | Map       | _ct_45035996274278280 |        9 | value       | varchar(80)     |              1
 45035996274278282 | Row       | _ct_45035996274278282 |        9 | description | varchar(80)     |              2
 45035996274278282 | Row       | _ct_45035996274278282 |        6 | record      | int             |              0
 45035996274278282 | Row       | _ct_45035996274278282 |        7 | total       | float           |              1
 45035996274278284 | Array     | _ct_45035996274278284 |        6 |             | int             |              0
(6 rows)

Sql-Reference: CONSTRAINT_COLUMNS

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

Records information about table column constraints.

Column Name	Data Type	Description
`CONSTRAINT_ID`	INTEGER	Unique numeric ID assigned by the OpenText™ Analytics Database catalog that identifies the constraint.
`TABLE_NAMESPACE`	VARCHAR	For Eon Mode databases, name of the namespace that contains the table.
`TABLE_SCHEMA`	VARCHAR	Name of the schema that contains this table. If the schema belongs to a non-default namespace in an Eon Mode database, the schema name is front-qualified with the name of the schema's namespace. For example, `n1.s` refers to schema `s` in namespace `n1`.
`TABLE_ID`	INTEGER	Unique numeric ID assigned by the database catalog that identifies the table.
`TABLE_NAME`	VARCHAR	Name of the table in which the column resides.
`COLUMN_NAME`	VARCHAR	Name of the column that is constrained. For check constraints, if more than one column is referenced, each appears as a separate row.
`CONSTRAINT_NAME`	VARCHAR	Constraint name for which information is listed.
`CONSTRAINT_TYPE`	CHAR	The constraint type, one of the following: `c`: check `f`: foreign `n`: not null `p`: primary `u`: unique
`IS_ENABLED`	BOOLEAN	Indicates whether a constraint for a primary key, unique key, or check constraint is currently enabled.
`REFERENCE_TABLE_ID`	INTEGER	Catalog-assigned integer value that uniquely identifies the referenced table
`REFERENCE_TABLE_NAMESPACE`	VARCHAR	For Eon Mode databases, references the TABLE_NAMESPACE column in the PRIMARY_KEYS table.
`REFERENCE_TABLE_SCHEMA`	VARCHAR	Schema name for which information is listed. If the schema belongs to a non-default namespace in an Eon Mode database, the schema name is front-qualified with the name of the schema's namespace. For example, `n1.s` refers to schema `s` in namespace `n1`.
`REFERENCE_TABLE_NAME`	VARCHAR	References the TABLE_NAME column in the PRIMARY_KEYS table.
`REFERENCE_COLUMN_NAME`	VARCHAR	References the COLUMN_NAME column in the PRIMARY_KEYS table.

Privileges

Non-superuser: No explicit privileges required. You only see records for tables that you have privileges to view.

Sql-Reference: CRYPTOGRAPHIC_KEYS

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

Stores private keys created by CREATE KEY.

Column Name	Data Type	Description
OID	INTEGER	The object identifier.
NAME	VARCHAR	Name of the key.
OWNER	INTEGER	The owner of the object.
TYPE	INTEGER	The type of key. 0 = `AES` 1 = `RSA`
LENGTH	INTEGER	The size of the key in bits.
HAS_PASSWORD	BOOLEAN	Whether the key has a password.
KEY	VARCHAR	The private key.

Examples

See Generating TLS certificates and keys.

Sql-Reference: DATA_LOADERS

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

Lists all defined data loaders.

Column Name	Column Type	Description
`NAME`	VARCHAR	Loader name.
`NAMESPACENAME`	VARCHAR	For Eon Mode databases, namespace in which the loader is defined.
`SCHEMANAME`	VARCHAR	Schema in which the loader is defined. If the schema belongs to a non-default namespace in an Eon Mode database, the schema name is front-qualified with the name of the schema's namespace. For example, `n1.s` refers to schema `s` in namespace `n1`.
`OWNER`	VARCHAR	OpenText™ Analytics Database user who created the loader.
`COPYSTMT`	VARCHAR	COPY statement used by this loader.
`RETRYLIMIT`	INT	Number of times to retry a failed file load. For loaders that do not specify an explicit value, this value is updated if the value of the DataLoaderDefaultRetryLimit configuration parameter changes.
`HISTORYRETENTIONINTERVAL`	INTERVAL	How long to wait before purging rows in the loader's monitoring table. See CREATE DATA LOADER.
`TRIGGER`	VARCHAR	External trigger for this data loader, if any.
`ENABLED`	BOOLEAN	Whether the data loader is enabled. EXECUTE DATA LOADER does not run a disabled data loader.
`iskafka`	BOOLEAN	Indicates whether it is a Kafka data loader.
`CREATE_TIME`	TIMESTAMPTZ	Time when the data loader was created.

Examples

=> SELECT * FROM DATA_LOADERS;
 name | namespacename | schemaname |  owner  |             copystmt              | retrylimit | historyretentioninterval | trigger |enabled | iskafka  |  create_time  
------+------------+---------+-----------------------------------+------------+---------------------------|--------+---------
 dl   |               | public     | dbadmin | copy sales from 's3://data/*.dat' |    3       |           14 days        |         |   t    |     f    | 2025-05-28 03:32:12.867798-04
(1 row)

Sql-Reference: DATABASES

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

Provides information about the databases in this OpenText™ Analytics Database installation.

Column Name	Data Type	Description
`DATABASE_ID`	INTEGER	The database's internal ID number
`DATABASE_NAME`	VARCHAR	The database's name
`OWNER_ID`	INTEGER	The database owner's ID
`OWNER_NAME`	INTEGER	The database owner's name
`START_TIME`	TIMESTAMPTZ	The date and time the database last started
`COMPLIANCE_MESSAGE`	VARCHAR	Message describing the current state of the database's license compliance
`EXPORT_SUBNET`	VARCHAR	Can be either of the following: The subnet (on the public network) used by the database for import/export The public address of the subnet that the database native load balancing uses for load balancing
`LOAD_BALANCE_POLICY`	VARCHAR	The current native connection load balance policy, which controls whether client connection requests are redirected to other hosts in the database. See About native connection load balancing.
BACKEND_ADDRESS_FAMILY	VARCHAR	The Internet Protocol (IP) addressing standard used for internode communications. This value is either ipv4 or ipv6.
BRANCH_NAME	VARCHAR	This column is no longer used.

Examples

This example queries the databases table from a master database.

=> SELECT * FROM DATABASES;
-[ RECORD 1 ]----------+-------------------------------------------------------------
database_id            | 45035996273704976
database_name          | VMart
owner_id               | 45035996273704962
owner_name             | dbadmin
start_time             | 2017-10-22 05:16:22.066961-04
compliance_message     | The database is in compliance with respect to raw data size.
export_subnet          | 0
load_balance_policy    | none
backend_address_family | ipv4
branch_name            |

Sql-Reference: DIRECTED_QUERIES

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

Returns information about directed queries.

Column Name	Data Type	Description
QUERY_NAME	VARCHAR	Directed query's unique identifier, used by statements such as ACTIVATE DIRECTED QUERY. How this identifier is set depends on how it was created: Direct call to CREATE DIRECTED QUERY: Set by the user-supplied `query-name` argument. Call to SAVE_PLANS: Concatenated from the following strings: `save_plans_query-label_query-number_save-plans-version` where: `query-label` is a LABEL hint embedded in the input query associated with this directed query. If theinput query contains no label, then this string is set to `nolabel`. `query-number` is an integer in a continuous sequence between 0 and `budget-query`, which uniquely identifies this directed query from others in the same SAVE_PLANS-generated set. [save-plans-version](/en/sql-reference/system-tables/v-catalog-schema/directed-queries/#SAVE_PLANS_VERSION) identifies the set of directed queries to which this directed query belongs.
IS_ACTIVE	BOOLEAN	Whether the directed query is active
VERTICA_VERSION	VARCHAR	OpenText™ Analytics Database version installed when this directed query was created.
COMMENT	VARCHAR	User-supplied or optimizer-generated comment on a directed query, up to 128 characters.
SAVE_PLANS_VERSION	INTEGER	One of the following: 0: Generated by a direct call to CREATE DIRECTED QUERY. >0: Identifies a set of directed queries that were generated by the same call to SAVE_PLANS. All directed queries of the set share the same `SAVE_PLANS_VERSION` integer, which increments by 1 the previous highest `SAVE_PLANS_VERSION` setting. Use this identifier to activate, deactivate, and drop a set of directed queries.
USERNAME	VARCHAR	User that created this directed query.
CREATION_DATE	VARCHAR	When the directed query was created.
SINCE_DATE	VARCHAR	Populated by SAVE_PLANS-generated directed queries, the earliest timestamp of input queries eligible to be saved as directed queries.
INPUT_QUERY	VARCHAR	Input query associated with this directed query. Multiple directed queries can map to the same input query.
ANNOTATED_QUERY	VARCHAR	Query with embedded hints that was paired with the input query of this directed query, where the hints encapsulated the query plan saved with CREATE DIRECTED QUERY.
DIGEST	INTEGER	Hash of saved query plan data, used by the optimizer to map identical input queries to the same active directed query.

Privileges

Superuser

Truncated query results

Query results for the fields INPUT_QUERY and ANNOTATED_QUERY are truncated after ~32K characters. You can get the full content of both fields in two ways:

Use the statement GET DIRECTED QUERY.
Use EXPORT_CATALOG to export directed queries.

Sql-Reference: DUAL

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

DUAL is a single-column "dummy" table with one record whose value is X; for example:

=> SELECT * FROM DUAL;
 dummy
-------
 X
(1 row)

You can write the following types of queries:

=> SELECT 1 FROM dual;
 ?column?
----------
        1
(1 row)
=> SELECT current_timestamp, current_user FROM dual;
           ?column?            | current_user
-------------------------------+--------------
 2010-03-08 12:57:32.065841-05 | release
(1 row)
=> CREATE TABLE t1(col1 VARCHAR(20), col2 VARCHAR(2));
=> INSERT INTO T1(SELECT 'hello' AS col1, 1 AS col2 FROM dual);)
=> SELECT * FROM t1;
 col1  | col2
-------+------
 hello | 1
(1 row

Restrictions

You cannot create projections for DUAL.

Sql-Reference: ELASTIC_CLUSTER

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

Returns information about cluster elasticity, such as whether Elastic cluster is running.

Column Name	Data Type	Description
`SCALING_FACTOR`	INTEGER	This value is only meaningful when you enable local segments. `SCALING_FACTOR` influences the number of local segments on each node. Initially—before a rebalance runs—there are scaling_factor number of local segments per node. A large `SCALING_FACTOR` is good for rebalancing a potentially wide range of cluster configurations quickly. However, too large a value might lead to ROS pushback, particularly in a database with a table with a large number of partitions. See SET_SCALING_FACTOR for more details.
`MAXIMUM_SKEW_PERCENT`	INTEGER	This value is only meaningful when you enable local segments. `MAXIMUM_SKEW_PERCENT` is the maximum amount of skew a rebalance operation tolerates, which preferentially redistributes local segments; however, if after doing so the segment ranges of any two nodes differs by more than this amount, rebalance will separate and distribute storage to even the distribution.
`SEGMENT_LAYOUT`	VARCHAR	Current, offset=0, segment layout. New segmented projections will be created with this layout, with segments rotated by the corresponding offset. Existing segmented projections will be rebalanced into an offset of this layout.
`LOCAL_SEGMENT_LAYOUT`	VARCHAR	Similar to SEGMENT_LAYOUT but includes details that indicate the number of local segments, their relative size and node assignment.
`VERSION`	INTEGER	Number that gets incremented each time the cluster topology changes (nodes added, marked ephemeral, marked permanent, etc). Useful for monitoring active and past rebalance operations.
`IS_ENABLED`	BOOLEAN	True if Elastic Cluster is enabled, otherwise false.
`IS_LOCAL_SEGMENT_ENABLED`	BOOLEAN	True if local segments are enabled, otherwise false.
`IS_REBALANCE_RUNNING`	BOOLEAN	True if rebalance is currently running, otherwise false.

Privileges

Superuser

Sql-Reference: EPOCHS

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

For the most recently closed epochs, lists the date and time of the close and the corresponding epoch number of the closed epoch. The EPOCHS table may return a varying number of rows depending on current commit activities.

Column Name	Data Type	Description
`EPOCH_CLOSE_TIME`	DATETIME	The date and time that the epoch closed.
`EPOCH_NUMBER`	INTEGER	The epoch number of the closed epoch.

Examples

=> SELECT * FROM EPOCHS;
       epoch_close_time        | epoch_number
-------------------------------+--------------
 2018-11-12 16:05:15.552571-05 |           16
(1 row)

Querying for historical data

If you need historical data about epochs and corresponding date information, query the DC_TRANSACTION_ENDS table.

=> select dc.end_epoch,min(dc.time),max(dc.time) from dc_transaction_ends dc group by end_epoch;
 end_epoch |             min               | max
-----------+-------------------------------+-------------------------------
       214 |  2018-10-12 08:05:47.02075-04 | 2018-10-15 10:22:24.015292-04
       215 | 2018-10-15 10:22:47.015172-04 | 2018-10-15 13:00:44.888984-04
                          ...
       226 | 2018-10-15 15:03:47.015235-04 | 2018-10-15 20:37:34.346667-04
       227 | 2018-10-15 20:37:47.008137-04 | 2018-10-16 07:39:00.29917-04
       228 | 2018-10-16 07:39:47.012411-04 | 2018-10-16 08:16:01.470232-04
       229 | 2018-10-16 08:16:47.018899-04 | 2018-10-16 08:21:13.854348-04
       230 | 2018-10-16 08:21:47.013767-04 | 2018-10-17 12:21:09.224094-04
       231 |  2018-10-17 12:21:09.23193-04 | 2018-10-17 15:11:59.338777-04

Sql-Reference: FAULT_GROUPS

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

View the fault groups and their hierarchy in the cluster.

Column Name	Data Type	Description
`MEMBER_ID`	INTEGER	A unique numeric ID assigned by the OpenText™ Analytics Database catalog that identifies the fault group.
`MEMBER_TYPE`	VARCHAR	The type of fault group. Values can be either `NODE` or `FAULT GROUP`.
`MEMBER_NAME`	VARCHAR	Name associated with this fault group. Values will be the node name or the fault group name.
`PARENT_ID`	INTEGER	A unique numeric ID assigned by the database catalog that identifies the parent fault group. The parent fault group can contain: Nodes Other fault groups Nodes and other fault groups
`PARENT_TYPE`	VARCHAR	The type of parent fault group, where the default/root parent is the DATABASE object. Can be one of the following objects: FAULT GROUP DATABASE
`PARENT_NAME`	VARCHAR	The name of the fault group that contains nodes or other fault groups or both nodes and fault groups.
`IS_AUTOMATICALLY_GENERATED`	BOOLEAN	If true, denotes whether OpenText™ Analytics Database created fault groups for you to manage the fault tolerance of control nodes in large cluster configurations. If false, denotes that you created fault groups manually. See Fault Groups for more information

Examples

Show the current hierarchy of fault groups in the cluster:

vmartdb=> SELECT member_type, member_name, parent_type, CASE
          WHEN parent_type = 'DATABASE' THEN ''
          ELSE parent_name END FROM fault_groups
          ORDER BY member_name;
 member_type | member_name           | parent_type | parent_name
-------------+-----------------------+-------------+-------------
 NODE        | v_vmart_node0001      | FAULT GROUP | two
 NODE        | v_vmart_node0002      | FAULT GROUP | two
 NODE        | v_vmart_node0003      | FAULT GROUP | three
 FAULT GROUP | one                   | DATABASE    |
 FAULT GROUP | three                 | DATABASE    |
 FAULT GROUP | two                   | FAULT GROUP | one

View the distribution of the segment layout:

vmartdb=> SELECT segment_layout from elastic_cluster;
                           segment_layout
-------------------------------------------------------------------------
 v_vmart_node0001[33.3%] v_vmart_node0003[33.3%] v_vmart_node0004[33.3%]
(1 row)

Sql-Reference: FOREIGN_KEYS

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

Provides foreign key information.

Column Name	Data Type	Description
`CONSTRAINT_ID`	INTEGER	A unique numeric ID assigned by the OpenText™ Analytics Database catalog, which identifies the constraint.
`CONSTRAINT_NAME`	VARCHAR	The constraint name for which information is listed.
`COLUMN_NAME`	VARCHAR	The name of the column that is constrained.
`ORDINAL_POSITION`	VARCHAR	The position of the column within the key. The numbering of columns starts at 1.
`TABLE_NAME`	VARCHAR	The table name for which information is listed.
`REFERENCE_TABLE_NAME`	VARCHAR	References the TABLE_NAME column in the PRIMARY_KEYS table.
`CONSTRAINT_TYPE`	VARCHAR	The constraint type, `f`, for foreign key.
`REFERENCE_COLUMN_NAME`	VARCHAR	References the COLUMN_NAME column in the PRIMARY_KEY table.
`TABLE_NAMESPACE_ID`	VARCHAR	Unique numeric identifier for the table namespace.
`TABLE_NAMESPACE`	VARCHAR	For Eon Mode databases, namespace that contains the table for which information is listed.
`TABLE_SCHEMA`	VARCHAR	The schema name for which information is listed. If the schema belongs to a non-default namespace in an Eon Mode database, the schema name is front-qualified with the name of the schema's namespace. For example, `n1.s` refers to schema `s` in namespace `n1`.
`REFERENCE_TABLE_NAMESPACE_ID`	VARCHAR	For Eon Mode databases, references the TABLE_NAMESPACE_ID column in the PRIMARY_KEYS table.
`REFERENCE_TABLE_NAMESPACE`	VARCHAR	For Eon Mode databases, references the TABLE_NAMESPACE column in the PRIMARY_KEYS table.
`REFERENCE_TABLE_SCHEMA`	VARCHAR	References the TABLE_SCHEMA column in the PRIMARY_KEYS table. If the schema belongs to a non-default namespace in an Eon Mode database, the schema name is front-qualified with the name of the schema's namespace. For example, `n1.s` refers to schema `s` in namespace `n1`.

Examples

mydb=> SELECT
          constraint_name,
          table_name,
          ordinal_position,
          reference_table_name
       FROM foreign_keys ORDER BY 3;
      constraint_name      |    table_name     | ordinal_position | reference_table_name
---------------------------+-------------------+------------------+-----------------------
 fk_store_sales_date       | store_sales_fact  |                1 | date_dimension
 fk_online_sales_saledate  | online_sales_fact |                1 | date_dimension
 fk_store_orders_product   | store_orders_fact |                1 | product_dimension
 fk_inventory_date         | inventory_fact    |                1 | date_dimension
 fk_inventory_product      | inventory_fact    |                2 | product_dimension
 fk_store_sales_product    | store_sales_fact  |                2 | product_dimension
 fk_online_sales_shipdate  | online_sales_fact |                2 | date_dimension
 fk_store_orders_product   | store_orders_fact |                2 | product_dimension
 fk_inventory_product      | inventory_fact    |                3 | product_dimension
 fk_store_sales_product    | store_sales_fact  |                3 | product_dimension
 fk_online_sales_product   | online_sales_fact |                3 | product_dimension
 fk_store_orders_store     | store_orders_fact |                3 | store_dimension
 fk_online_sales_product   | online_sales_fact |                4 | product_dimension
 fk_inventory_warehouse    | inventory_fact    |                4 | warehouse_dimension
 fk_store_orders_vendor    | store_orders_fact |                4 | vendor_dimension
 fk_store_sales_store      | store_sales_fact  |                4 | store_dimension
 fk_store_orders_employee  | store_orders_fact |                5 | employee_dimension
 fk_store_sales_promotion  | store_sales_fact  |                5 | promotion_dimension
 fk_online_sales_customer  | online_sales_fact |                5 | customer_dimension
 fk_store_sales_customer   | store_sales_fact  |                6 | customer_dimension
 fk_online_sales_cc        | online_sales_fact |                6 | call_center_dimension
 fk_store_sales_employee   | store_sales_fact  |                7 | employee_dimension
 fk_online_sales_op        | online_sales_fact |                7 | online_page_dimension
 fk_online_sales_shipping  | online_sales_fact |                8 | shipping_dimension
 fk_online_sales_warehouse | online_sales_fact |                9 | warehouse_dimension
 fk_online_sales_promotion | online_sales_fact |               10 | promotion_dimension
(26 rows)

Sql-Reference: GRANTS

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

Returns information about privileges that are explicitly granted on database objects. Information about inherited privileges is not included.

Note

While an ADMIN OPTION granted to users through roles is not viewable directly from this table, you can view it and a summary of privileges data with vsql meta-commands \z and \dp.

Column Name	Data Type	Description
GRANTEE	VARCHAR	The user being granted permission.
GRANTEE_ID	INTEGER	Catalog-assigned integer value that uniquely identifies theuser granted permissions.
GRANT_ID	INTEGER	Catalog-assigned integer value that uniquely identifies thegrant operation.
GRANTOR	VARCHAR	The user granting the permission.
GRANTOR_ID	INTEGER	Catalog-assigned integer value that uniquely identifies theuser who performed the grant operation.
OBJECT_ID	INTEGER	Catalog-assigned integer value that uniquely identifies theobject granted.
OBJECT_NAME	VARCHAR	The name of the object that is being granted privileges. Note that for schema privileges, the schema name appears in the `OBJECT_NAME` column instead of the `OBJECT_SCHEMA` column.
OBJECT_NAMESPACE	VARCHAR	For Eon Mode databases, namespace of the object that is being granted privileges.
OBJECT_SCHEMA	VARCHAR	Schema of the object that is being granted privileges. If the schema belongs to a non-default namespace in an Eon Mode database, the schema name is front-qualified with the name of the schema's namespace. For example, `n1.s` refers to schema `s` in namespace `n1`.
OBJECT_TYPE	VARCHAR	The object type on which the grant was applied—for example, ROLE, SCHEMA, DATABASE, RESOURCEPOOL.
PRIVILEGES_DESCRIPTION	VARCHAR	Lists the privileges granted on an object—for example INSERT, SELECT. An asterisk in `PRIVILEGES_DESCRIPTION` output shows that the privilege grant included `WITH GRANT OPTION`.

Examples

The following query shows the privileges that are granted to user Rob or role R1. An asterisk (*) appended to a privilege indicates that the user can grant the privilege to other users:

=> SELECT grantor,privileges_description,object_name,object_type,grantee FROM grants WHERE grantee='Rob' OR grantee='R1';
 grantor |  privileges_description   | object_name | object_type  | grantee
 --------+---------------------------+-------------+--------------+---------
 dbadmin | USAGE                     | general     | RESOURCEPOOL | Rob
 dbadmin | USAGE, CREATE             | s1          | SCHEMA       | Rob
 dbadmin | INSERT*, SELECT*, UPDATE* | t1          | TABLE        | Rob
 dbadmin | SELECT                    | t1          | TABLE        | R1
 dbadmin | USAGE                     | s1          | SCHEMA       | R1
 dbadmin |                           | R1          | ROLE         | Rob
 (6 rows)

Sql-Reference: HCATALOG_COLUMNS

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

Describes the columns of all tables available through the HCatalog Connector. Each row in this table corresponds to to a column in a table accessible through the HCatalog Connector. See Using the HCatalog Connector for more information.

Column Name	Data Type	Description
`TABLE_SCHEMA`	VARCHAR(128)	The name of the OpenText™ Analytics Database schema that contains the table containing this column
`HCATALOG_SCHEMA`	VARCHAR(128)	The name of the Hive schema or database that contains the table containing this column
`TABLE_NAME`	VARCHAR(128)	The name of the table that contains the column
`IS_PARTITION_COLUMN`	BOOLEAN	Whether the table is partitioned on this column
`COLUMN_NAME`	VARCHAR(128)	The name of the column
`HCATALOG_DATA_TYPE`	VARCHAR(128)	The Hive data type of this column
`DATA_TYPE`	VARCHAR(128)	The OpenText™ Analytics Database data type of this column
`DATA_TYPE_ID`	INTEGER	Numeric ID of the column's OpenText™ Analytics Database data type
`DATA_TYPE_LENGTH`	INTEGER	The number of bytes used to store this data type
`CHARACTER_MAXIMUM_LENGTH`	INTEGER	For string data types, the maximum number of characters it can hold
`NUMERIC_PRECISION`	INTEGER	For numeric types, the precision of the values in the column
`NUMERIC_SCALE`	INTEGER	For numeric data types, the scale of the values in the column
`DATETIME_PRECISION`	INTEGER	For datetime data types, the precision of the values in the column
`INTERVAL_PRECISION`	INTEGER	For interval data types, the precision of the values in the column
`ORDINAL_POSITION`	INTEGER	The position of the column within the table

Privileges

No explicit permissions are required; however, users see only the records that correspond to schemas they have permissions to access.

Notes

If you are using WebHCat instead of HiveServer2, querying this table results in one web service call to the WebHCat server for each table in each HCatalog schema. If you need to perform multiple queries on this table in a short period of time, consider creating a copy of the table using a CREATE TABLE AS statement to improve performance. The copy does not reflect any changes made to the schema of the Hive tables after it was created, but it is much faster to query.

Examples

The following example demonstrates finding the column information for a specific table:

=> SELECT * FROM HCATALOG_COLUMNS WHERE table_name = 'hcatalogtypes'
-> ORDER BY ordinal_position;
-[ RECORD 1 ]------------+-----------------
table_schema             | hcat
hcatalog_schema          | default
table_name               | hcatalogtypes
is_partition_column      | f
column_name              | intcol
hcatalog_data_type       | int
data_type                | int
data_type_id             | 6
data_type_length         | 8
character_maximum_length |
numeric_precision        |
numeric_scale            |
datetime_precision       |
interval_precision       |
ordinal_position         | 1
-[ RECORD 2 ]------------+-----------------
table_schema             | hcat
hcatalog_schema          | default
table_name               | hcatalogtypes
is_partition_column      | f
column_name              | floatcol
hcatalog_data_type       | float
data_type                | float
data_type_id             | 7
data_type_length         | 8
character_maximum_length |
numeric_precision        |
numeric_scale            |
datetime_precision       |
interval_precision       |
ordinal_position         | 2
-[ RECORD 3 ]------------+-----------------
table_schema             | hcat
hcatalog_schema          | default
table_name               | hcatalogtypes
is_partition_column      | f
column_name              | doublecol
hcatalog_data_type       | double
data_type                | float
data_type_id             | 7
data_type_length         | 8
character_maximum_length |
numeric_precision        |
numeric_scale            |
datetime_precision       |
interval_precision       |
ordinal_position         | 3
-[ RECORD 4 ]------------+-----------------
table_schema             | hcat
hcatalog_schema          | default
table_name               | hcatalogtypes
is_partition_column      | f
column_name              | charcol
hcatalog_data_type       | string
data_type                | varchar(65000)
data_type_id             | 9
data_type_length         | 65000
character_maximum_length | 65000
numeric_precision        |
numeric_scale            |
datetime_precision       |
interval_precision       |
ordinal_position         | 4
-[ RECORD 5 ]------------+-----------------
table_schema             | hcat
hcatalog_schema          | default
table_name               | hcatalogtypes
is_partition_column      | f
column_name              | varcharcol
hcatalog_data_type       | string
data_type                | varchar(65000)
data_type_id             | 9
data_type_length         | 65000
character_maximum_length | 65000
numeric_precision        |
numeric_scale            |
datetime_precision       |
interval_precision       |
ordinal_position         | 5
-[ RECORD 6 ]------------+-----------------
table_schema             | hcat
hcatalog_schema          | default
table_name               | hcatalogtypes
is_partition_column      | f
column_name              | boolcol
hcatalog_data_type       | boolean
data_type                | boolean
data_type_id             | 5
data_type_length         | 1
character_maximum_length |
numeric_precision        |
numeric_scale            |
datetime_precision       |
interval_precision       |
ordinal_position         | 6
-[ RECORD 7 ]------------+-----------------
table_schema             | hcat
hcatalog_schema          | default
table_name               | hcatalogtypes
is_partition_column      | f
column_name              | timestampcol
hcatalog_data_type       | string
data_type                | varchar(65000)
data_type_id             | 9
data_type_length         | 65000
character_maximum_length | 65000
numeric_precision        |
numeric_scale            |
datetime_precision       |
interval_precision       |
ordinal_position         | 7
-[ RECORD 8 ]------------+-----------------
table_schema             | hcat
hcatalog_schema          | default
table_name               | hcatalogtypes
is_partition_column      | f
column_name              | varbincol
hcatalog_data_type       | binary
data_type                | varbinary(65000)
data_type_id             | 17
data_type_length         | 65000
character_maximum_length | 65000
numeric_precision        |
numeric_scale            |
datetime_precision       |
interval_precision       |
ordinal_position         | 8
-[ RECORD 9 ]------------+-----------------
table_schema             | hcat
hcatalog_schema          | default
table_name               | hcatalogtypes
is_partition_column      | f
column_name              | bincol
hcatalog_data_type       | binary
data_type                | varbinary(65000)
data_type_id             | 17
data_type_length         | 65000
character_maximum_length | 65000
numeric_precision        |
numeric_scale            |
datetime_precision       |
interval_precision       |
ordinal_position         | 9

Sql-Reference: HCATALOG_SCHEMATA

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

Lists all of the schemas defined using the HCatalog Connector. See Using the HCatalog Connector.

Unlike other HCatalog Connector-related system tables, this table makes no calls to Hive, so querying incurs very little overhead.

Column Name	Data Type	Description
`SCHEMA_ID`	INTEGER	The OpenText™ Analytics Database ID number for the schema
`SCHEMA_NAME`	VARCHAR(128)	The name of the schema defined in the database catalog
`SCHEMA_OWNER_ID`	INTEGER	The ID number of the user who owns the database schema
`SCHEMA_OWNER`	VARCHAR(128)	The username of the database schema's owner
`CREATE_TIME`	TIMESTAMPTZ	The date and time the schema as created
`HOSTNAME`	VARCHAR(128)	The host name or IP address of the database server that holds the Hive metadata
`PORT`	INTEGER	The port number on which the metastore database listens for connections
`HIVESERVER2_HOSTNAME`	VARCHAR(128)	The host name or IP address of the HiveServer2 server for the Hive database
`WEBSERVICE_HOSTNAME`	VARCHAR(128)	The host name or IP address of the WebHCat server for the Hive database, if used
`WEBSERVICE_PORT`	INTEGER	The port number on which the WebHCat server listens for connections
`WEBHDFS_ADDRESS`	VARCHAR (128)	The host and port ("host:port") for the WebHDFS service, used for reading ORC and Parquet files
`HCATALOG_SCHEMA_NAME`	VARCHAR(128)	The name of the schema or database in Hive to which the database schema is mapped
`HCATALOG_USER_NAME`	VARCHAR(128)	The username the HCatalog Connector uses to authenticate itself to the Hive database.
`HCATALOG_CONNECTION_TIMEOUT`	INTEGER	The number of seconds the HCatalog Connector waits for a successful connection to the HiveServer or WebHCat server. A value of 0 means wait indefinitely.
`HCATALOG_SLOW_TRANSFER_LIMIT`	INTEGER	The lowest data transfer rate (in bytes per second) from the HiveServer2 or WebHCat server that the HCatalog Connector accepts.
`HCATALOG_SLOW_TRANSFER_TIME`	INTEGER	The number of seconds the HCatalog Connector waits before enforcing the data transfer rate lower limit by breaking the connection and terminating the query.
`SSL_CONFIG`	VARCHAR(128)	The path of the Hadoop ssl-client.xml configuration file, if using HiveServer2 with SSL wire encryption.
`CUSTOM_PARTITIONS`	BOOLEAN	Whether the Hive schema uses custom partition locations.

Privileges

No explicit permissions are required; however, users see only the records that correspond to schemas they have permissions to access.

Sql-Reference: HCATALOG_TABLE_LIST

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

A concise list of all tables contained in all Hive schemas and databases available through the HCatalog Connector. See Using the HCatalog Connector.

Column Name	Data Type	Description
TABLE_SCHEMA_ID	INTEGER	Internal ID number for the schema containing the table
TABLE_SCHEMA	VARCHAR(128)	Name of the OpenText™ Analytics Database schema through which the table is available
HCATALOG_SCHEMA	VARCHAR(128)	Name of the Hive schema or database containing the table
TABLE_NAME	VARCHAR(128)	The name of the table
HCATALOG_USER_NAME	VARCHAR(128)	Name of Hive user used to access the table

Privileges

No explicit permissions are required; however, users see only the records that correspond to schemas they have permissions to access.

Notes

Querying this table results in one call to HiveServer2 for each Hive schema defined using the HCatalog Connector. This means that the query usually takes longer than querying other system tables.
Querying this table is faster than querying HCATALOG_TABLES. Querying HCATALOG_TABLE_LIST only makes one HiveServer2 call per HCatalog schema versus one call per table for HCATALOG_TABLES.

Examples

The following example demonstrates defining a new HCatalog schema then querying HCATALOG_TABLE_LIST. Note that one table defined in a different HCatalog schema also appears. HCATALOG_TABLE_LIST lists all of the tables available in any of the HCatalog schemas:

=> CREATE HCATALOG SCHEMA hcat WITH hostname='hcathost'
-> HCATALOG_SCHEMA='default' HCATALOG_DB='default' HCATALOG_USER='hcatuser';
CREATE SCHEMA
=> \x
Expanded display is on.
=> SELECT * FROM v_catalog.hcatalog_table_list;
-[ RECORD 1 ]------+------------------
table_schema_id    | 45035996273748980
table_schema       | hcat
hcatalog_schema    | default
table_name         | weblogs
hcatalog_user_name | hcatuser
-[ RECORD 2 ]------+------------------
table_schema_id    | 45035996273748980
table_schema       | hcat
hcatalog_schema    | default
table_name         | tweets
hcatalog_user_name | hcatuser
-[ RECORD 3 ]------+------------------
table_schema_id    | 45035996273748980
table_schema       | hcat
hcatalog_schema    | default
table_name         | messages
hcatalog_user_name | hcatuser
-[ RECORD 4 ]------+------------------
table_schema_id    | 45035996273864948
table_schema       | hiveschema
hcatalog_schema    | default
table_name         | weblogs
hcatalog_user_name | hcatuser

Sql-Reference: HCATALOG_TABLES

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

Returns a detailed list of all tables made available through the HCatalog Connector. See Using the HCatalog Connector.

Column Name	Data Type	Description
`TABLE_SCHEMA_ID`	INTEGER	ID number of the schema
`TABLE_SCHEMA`	VARCHAR(128)	The name of the OpenText™ Analytics Database schema through which the table is available
`HCATALOG_SCHEMA`	VARCHAR(128)	The name of the Hive schema or database that contains the table
`TABLE_NAME`	VARCHAR(128)	The name of the table
`HCATALOG_USER_NAME`	VARCHAR(128)	The name of the HCatalog user whose credentials are used to access the table's data
`MIN_FILE_SIZE_BYTES`	INTEGER	The file size of the table's smallest data file, if using WebHCat; null if using HiveServer2
`TOTAL_NUMBER_FILES`	INTEGER	The number of files used to store this table's data in HDFS
`LOCATION`	VARCHAR(8192)	The URI for the directory containing this table's data, normally an HDFS URI
`LAST_UPDATE_TIME`	TIMESTAMPTZ	The last time data in this table was updated, if using WebHCat; null if using HiveServer2
`OUTPUT_FORMAT`	VARCHAR(128)	The Hive SerDe class used to output data from this table
`LAST_ACCESS_TIME`	TIMESTAMPTZ	The last time data in this table was accessed, if using WebHCat; null if using HiveServer2
`MAX_FILE_SIZE_BYTES`	INTEGER	The size of the largest data file for this table, if using WebHCat; null if using HiveServer2
`IS_PARTITIONED`	BOOLEAN	Whether this table is partitioned
`PARTITION_EXPRESSION`	VARCHAR(128)	The expression used to partition this table
`TABLE_OWNER`	VARCHAR(128)	The Hive user that owns this table in the Hive database, if using WebHCat; null if using HiveServer2
`INPUT_FORMAT`	VARCHAR(128)	The SerDe class used to read the data from this table
`TOTAL_FILE_SIZE_BYTES`	INTEGER	Total number of bytes used by all of this table's data files
`HCATALOG_GROUP`	VARCHAR(128)	The permission group assigned to this table, if using WebHCat; null if using HiveServer2
`PERMISSION`	VARCHAR(128)	The Unix file permissions for this group, as shown by the `ls -l` command, if using WebHCat; null if using HiveServer2

Privileges

No explicit permissions are required; however, users see only the records that correspond to schemas they have permissions to access.

Sql-Reference: ICEBERG_COLUMNS

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

Provides column information for Iceberg external tables. The information in this table is drawn from the Iceberg metadata files at query time.

Column Name	Data Type	Description
`TABLE_ID`	INTEGER	Catalog-assigned numeric value that uniquely identifies the table.
`TABLE_SCHEMA`	VARCHAR	Name of the table's schema. If the schema belongs to a non-default namespace in an Eon Mode database, the schema name is front-qualified with the name of the schema's namespace. For example, `n1.s` refers to schema `s` in namespace `n1`.
`TABLE_NAME`	VARCHAR	Name of the table containing the column.
`COLUMN_ID`	VARCHAR	Catalog-assigned VARCHAR value that uniquely identifies a table column.
`COLUMN_NAME`	VARCHAR	Name of the column.
`DATA_TYPE`	VARCHAR	Column data type.
`DATA_TYPE_ID`	INTEGER	Catalog-assigned unique numeric ID of the data type.
`DATA_TYPE_LENGTH`	INTEGER	Maximum allowable length of the data type.
`CHARACTER_MAXIMUM_LENGTH`	VARCHAR	Maximum allowable length of a VARCHAR column.
`NUMERIC_PRECISION`	INTEGER	Number of significant decimal digits for a NUMERIC column.
`NUMERIC_SCALE`	INTEGER	Number of fractional digits for a NUMERIC column.
`DATETIME_PRECISION`	INTEGER	Declared precision for a TIMESTAMP column, or NULL if no precision was declared.
`INTERVAL_PRECISION`	INTEGER	Number of fractional digits retained in the seconds field of an INTERVAL column.
`IS_NULLABLE`	BOOLEAN	Whether the column can contain NULL values.
`WRITE_DEFAULT`	VARCHAR	Field value for any records written after the field was added to the schema, if the writer does not supply the field’s value.
`INITIAL_DEFAULT`	VARCHAR	Field value for all records that were written before the field was added to the schema.

Sql-Reference: ICEBERG_NAMESPACES

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

Lists details about the namespaces created using Iceberg in an Eon Mode database.

Column Name	Data Type	Description
`NAMESPACE_ID`	INTEGER	The ID number for the namespace.
`NAMESPACE_NAME`	VARCHAR(128)	The name of the namespace.
`CATALOG`	VARCHAR(128)	The name of the catalog used in the Iceberg namespace. The supported catalog types are filesystem, glue, hive, and rest.
`LOCATION`	VARCHAR(128)	The location of the Iceberg namespace.
`rest_auth`	VARCHAR(128)	The authentication method for the REST catalog which supports either bearerToken or OAuth2 authentication. Applicable only when CATALOG is rest.

Privileges

Only superuser has permissions. However, regular users can access Iceberg data if they have permissions on the underlying storage.

Examples

To list all the namespaces created using Iceberg in an Eon Mode database, run the following query:

=> SELECT * from v_catalog.iceberg_namespaces;
  namespace_id  | namespace_name    | catalog   | location                                  | rest_auth
-------------------+----------------+-----------------------------------------------------------------------
                | default_namespace |           |                                           |  
                | analytics         | glue      | s3://vertica-perpetual/user/iceberg_new   |
                | finance           | rest      | http://localhost:19120/iceberg/v1/main    | {"bearerToken":"token"} 
(3 rows)

Sql-Reference: INHERITED_PRIVILEGES

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

Provides summary information about privileges inherited by objects from GRANT statements on parent schemas, excluding inherited grant options.

For information about explicitly granted permissions, see system table GRANTS.

Note

Inherited privileges are not displayed if privilege inheritance is disabled at the database level with DisableInheritedPrivileges.

Column Name	Data Type	Description
OBJECT_ID	INTEGER	Catalog-assigned integer value that uniquely identifies theobject inheriting the privileges.
SCHEMA_ID	INTEGER	Catalog-assigned integer value that uniquely identifies theparent schema.
OBJECT_NAMESPACE	VARCHAR	For Eon Mode databases, namespace of the table or view.
OBJECT_SCHEMA	VARCHAR	Name of the parent schema of a table or view. If the schema belongs to a non-default namespace in an Eon Mode database, the schema name is front-qualified with the name of the schema's namespace. For example, `n1.s` refers to schema `s` in namespace `n1`.
OBJECT_NAME	VARCHAR	Name of the table or view.
OBJECT_TYPE	VARCHAR	The object type, one of the following: Table View Model
PRIVILEGES_DESCRIPTION	VARCHAR	Lists the privileges inherited on an object. An asterisk (*) appended to a privilege indicates that the user can grant the privilege to other users by granting the privilege on the parent schema.
PRINCIPAL	VARCHAR	Name of the role or user inheriting the privileges in the row.
PRINCIPAL_ID	INTEGER	Catalog-assigned integer value that uniquely identifies theuser inheriting the privileges.
GRANTOR	VARCHAR	User that granted the privileges on the parent schema to the principal.
GRANTOR_ID	INTEGER	Catalog-assigned integer value that uniquely identifies theuser who performed the grant operation.
GRANT_ID	INTEGER	Catalog-assigned integer value that uniquely identifies thegrant operation.

Examples

The following query returns the privileges that the tables and views inherit from their parent schema, customers.

=> SELECT object_schema,object_name,object_type,privileges_description,principal,grantor FROM inherited_privileges WHERE object_schema='customers';
 object_schema |  object_name    | object_type |                          privileges_description                           | principal | grantor
 --------------+-----------------+-------------+---------------------------------------------------------------------------+-----------+---------
 customers     | cust_info       | Table       | INSERT, SELECT, UPDATE, DELETE, ALTER, REFERENCES, DROP, TRUNCATE         | dbadmin   | dbadmin
 customers     | shipping_info   | Table       | INSERT, SELECT, UPDATE, DELETE, ALTER, REFERENCES, DROP, TRUNCATE         | dbadmin   | dbadmin
 customers     | cust_set        | View        | SELECT, ALTER, DROP                                                       | dbadmin   | dbadmin
 customers     | cust_info       | Table       | SELECT                                                                    | Val       | dbadmin
 customers     | shipping_info   | Table       | SELECT                                                                    | Val       | dbadmin
 customers     | cust_set        | View        | SELECT                                                                    | Val       | dbadmin
 customers     | sales_model     | Model       | USAGE, ALTER, DROP                                                        | Pooja     | dbadmin
 customers     | shipping_info   | Table       | INSERT                                                                    | Pooja     | dbadmin
 (8 rows)

Sql-Reference: INHERITING_OBJECTS

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

Provides information about the objects (table, view, or model) that inherit privileges from their parent schemas.

For information about the particular privileges inherited from schemas and their associated GRANT statements, see the INHERITED_PRIVILEGES table.

Column Name	Data Type	Description
OBJECT_ID	INTEGER	Catalog-assigned integer value that uniquely identifies theobject inheriting the privileges.
SCHEMA_ID	INTEGER	Catalog-assigned integer value that uniquely identifies theparent schema.
OBJECT_SCHEMA	VARCHAR	Name of the parent schema.
OBJECT_NAME	VARCHAR	Name of the object.
OBJECT_TYPE	VARCHAR	The object type, one of the following: Table View Model

Examples

The following query returns the tables and views that inherit their privileges from their parent schema, customers.

=> SELECT * FROM inheriting_objects WHERE object_schema='customers';
     object_id     |     schema_id     | object_schema |  object_name      | object_type
 ------------------+-------------------+---------------+-------------------+-------------
 45035996273980908 | 45035996273980902 | customers     | cust_info         | table
 45035996273980984 | 45035996273980902 | customers     | shipping_info     | table
 45035996273980980 | 45035996273980902 | customers     | cust_set          | view
 45035996273980983 | 45035996273980901 | ml_models     | clustering_model  | model
 (3 rows)

Sql-Reference: KEYWORDS

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

Identifies OpenText™ Analytics Database reserved and non-reserved keywords.

Column Name Data Type Description

KEYWORD VARCHAR OpenText™ Analytics Database-reserved or non-reserved keyword.

Column Name	Data Type	Description
`KEYWORD`	VARCHAR	OpenText™ Analytics Database-reserved or non-reserved keyword.
`RESERVED`	VARCHAR	Indicates whether a keyword is reserved or non-reserved: R: reserved N: non-reserved

RESERVED

VARCHAR

Indicates whether a keyword is reserved or non-reserved:

R: reserved
N: non-reserved

Examples

The following query gets all reserved keywords that begin with B:

=> SELECT * FROM keywords WHERE reserved = 'R' AND keyword ilike 'B%';
 keyword | reserved
---------+----------
 BETWEEN | R
 BIGINT  | R
 BINARY  | R
 BIT     | R
 BOOLEAN | R
 BOTH    | R
(6 rows)

Sql-Reference: LARGE_CLUSTER_CONFIGURATION_STATUS

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

Shows the current cluster nodes and control node (spread hosts) designations in the Catalog so you can see if they match.

Column Name	Data Type	Description
`NODE_NAME`	VARCHAR	The name of the node in the cluster.
`SPREAD_HOST_NAME`	VARCHAR	The host name of the control node (the host that manages control message responsibilities)
`CONTROL_NODE_NAME`	VARCHAR	The name of the control node

Sql-Reference: LICENSE_AUDITS

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

Lists the results of OpenText™ Analytics Database's license automatic compliance audits. See How Database Calculates Database Size.

Column Name	Data Type	Description
`DATABASE_SIZE_BYTES`	`INTEGER`	The estimated raw data size of the database
`LICENSE_SIZE_BYTES`	`INTEGER`	The licensed data allowance
`USAGE_PERCENT`	`FLOAT`	Percentage of the licensed allowance used
`AUDIT_START_TIMESTAMP`	`TIMESTAMPTZ`	When the audit started
`AUDIT_END_TIMESTAMP`	`TIMESTAMPTZ`	When the audit finished
`CONFIDENCE_LEVEL_PERCENT`	`FLOAT`	The confidence level of the size estimate
`ERROR_TOLERANCE_PERCENT`	`FLOAT`	The error tolerance used for the size estimate
`USED_SAMPLING`	`BOOLEAN`	Whether data was randomly sampled (if false, all of the data was analyzed)
`CONFIDENCE_INTERVAL_LOWER_BOUND_BYTES`	`INTEGER`	The lower bound of the data size estimate within the confidence level
`CONFIDENCE_INTERVAL_UPPER_BOUND_BYTES`	`INTEGER`	The upper bound of the data size estimate within the confidence level
`SAMPLE_COUNT`	`INTEGER`	The number of data samples used to generate the estimate
`CELL_COUNT`	`INTEGER`	The number of cells in the database
`AUDITED_DATA`	`VARCHAR`	The type of data audited, which includes regular (non-flex), flex, external, and total data

Sql-Reference: LICENSES

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

For all licenses, provides information on license types, the dates for which licenses are valid, and the limits the licenses impose.

Column Name	Data Type	Description
`LICENSE_ID`	INTEGER	Unique numeric ID assigned by the OpenText™ Analytics Database catalog, which identifies the license.
`NAME`	VARCHAR	The license’s name. (The license name in this column could be represented by a long license key.)
`LICENSEE`	VARCHAR	The entity to which the product is licensed.
`START_DATE`	VARCHAR	The start date for which the license is valid.
`END_DATE`	VARCHAR	The end date until which the license is valid (or "Perpetual" if the license has no expiration).
`LICENSETYPE`	VARCHAR	The type of the license (for example, Premium Edition).
`PARENT`	VARCHAR	The parent license (field is blank if there is no parent).
`SIZE`	VARCHAR	The size limit for data on the license.
`IS_SIZE_LIMIT_ENFORCED`	BOOLEAN	Indicates whether the license includes enforcement of data and node limits, where t is true and f is false.
`NODE_RESTRICTION`	VARCHAR	The node limit the license imposes.
`CONFIGURED_ID`	INTEGER	A long license key.

Sql-Reference: LOAD_BALANCE_GROUPS

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

Lists the objects contained by all load balance groups. Each row in this table represents a single object that is a member of a load balance group. If a load balance group does not contain any objects, it appears once in this table with its type column set to 'Empty Group.'

Column Name	Data Type	Description
NAME	VARCHAR	The name of the load balance group
POLICY	VARCHAR	The policy that sets how the group chooses the node for a connection. Contains one of the following: ROUNDROBIN RANDOM NONE
FILTER	VARCHAR	The IP address range in CIDR format to select the members of a fault group that are included in the load balance group. This column only has a value if the TYPE column is 'Fault Group' or 'Subcluster.'
TYPE	VARCHAR	The type of object contained in the load balance group. Contains one of: Fault Group Subcluster Network Address Group Empty Group
OBJECT_NAME	VARCHAR	The name of the fault group or network address included in the load balance group. This column is NULL if the group contains no objects.

Examples

=> SELECT * FROM LOAD_BALANCE_GROUPS;
     name      |   policy   |  filter   |         type          | object_name
---------------+------------+-----------+-----------------------+-------------
 group_1       | ROUNDROBIN |           | Network Address Group | node01
 group_1       | ROUNDROBIN |           | Network Address Group | node02
 group_2       | ROUNDROBIN |           | Empty Group           |
 group_all     | ROUNDROBIN |           | Network Address Group | node01
 group_all     | ROUNDROBIN |           | Network Address Group | node02
 group_all     | ROUNDROBIN |           | Network Address Group | node03
 group_fault_1 | RANDOM     | 0.0.0.0/0 | Fault Group           | fault_1
(7 rows)

Sql-Reference: LOG_PARAMS

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

Provides summary information about changes to configuration parameters related to authentication and security run in your database.

Column Name	Data Type	Description
ISSUED_TIME	VARCHAR	The time at which the query was executed.
USER_NAME	VARCHAR	Name of the user who issued the query at the time OpenText™ Analytics Database recorded the session.
USER_ID	INTEGER	Numeric representation of the user who ran the query.
HOSTNAME	VARCHAR	The hostname, IP address, or URL of the database server.
SESSION_ID	VARCHAR	Identifier for this session. This identifier is unique within the cluster at any point in time but can be reused when the session closes.
AUDIT_TYPE	VARCHAR	The type of operation for the audit, in this case, Parameter.
AUDIT_TAG_NAME	VARCHAR	The tag for the specific parameter.
REQUEST_TYPE	VARCHAR	The type of query request.
REQUEST_ID	INTEGER	Unique identifier of the query request in the user session.
SUBJECT	VARCHAR	The new value of the parameter.
REQUEST	VARCHAR	Lists the query request.
SUCCESS	VARCHAR	Indicates whether or not the operation was successful.
CATEGORY	VARCHAR	The audit parent category, such as Authentication.

Examples

The following example queries the LOG_PARAMS system table and shows only the most recent configuration parameter for this user under the Authentication category:

=> SELECT * FROM log_params limit 1;

--------------------------------------------------------------------------------------------------------

issued_time   | 2018-02-12 13:41:20.837452-05
user_name     | dbadmin
user_id       | 45035996273704962
hostname      | ::1:50690
session_id    | v_vmart_node0001-341751:0x13878
audit_type    | Param
audit_tag_name| SecurityAlgorithm
request_type  | UTILITY
request_id    | 8
subject       | MD5
request       | select set_config_parameter('SecurityAlgorithm','MD5',null);
success       | t
category      | Authentication
(1 row)

Sql-Reference: LOG_QUERIES

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

Provides summary information about some queries related to authentication and security run in your database.

Column Name	Data Type	Description
ISSUED_TIME	VARCHAR	The time at which the query was executed.
USER_NAME	VARCHAR	Name of the user who issued the query at the time OpenText™ Analytics Database recorded the session.
USER_ID	INTEGER	Numeric representation of the user who ran the query.
HOSTNAME	VARCHAR	The hostname, IP address, or URL of the database server.
SESSION_ID	VARCHAR	Identifier for this session. This identifier is unique within the cluster at any point in time but can be reused when the session closes.
AUDIT_TYPE	VARCHAR	The type of operation for the audit, in this case, Query.
AUDIT_TAG_NAME	VARCHAR	The tag for the specific query.
REQUEST_TYPE	VARCHAR	The type of query request. Examples include, but are not limited to: QUERY DDL LOAD UTILITY TRANSACTION PREPARE EXECUTE SET SHOW
REQUEST_ID	INTEGER	The ID of the query request.
SUBJECT	VARCHAR	The subject of the query.
REQUEST	VARCHAR	Lists the query request.
SUCCESS	VARCHAR	Indicates whether or not the operation was successful.
CATEGORY	VARCHAR	The audit parent category, such as Managing_Users_Privileges.

Examples

The following example queries the LOG_QUERIES system table and shows only the most recent query for this user under the Managing_Users_Privileges category:

=> SELECT * FROM log_queries limit 1;
---------------------------------------------------------------------------

issued_time   | 2018-01-22 10:36:55.634349-05
user_name     | dbadmin
user_id       | 45035996273704962
hostname      |
session_id    | v_vmart_node0001-237210:0x37e1d
audit_type    | Query
audit_tag_name| REVOKE ROLE
request_type  | DDL
request_id    | 2
subject       |
request       | revoke all privileges from Joe;
success       | f
category      | Managing_Users_Privileges
(1 row)

Sql-Reference: LOG_TABLES

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

Provides summary information about queries on system tables.

Column Name	Data Type	Description
ISSUED_TIME	VARCHAR	Time of query execution.
USER_NAME	VARCHAR	Name of user who issued the query at the time OpenText™ Analytics Database recorded the session.
USER_ID	INTEGER	Numeric representation of the user who ran the query.
HOSTNAME	VARCHAR	The hostname, IP address, or URL of the database server.
SESSION_ID	VARCHAR	Identifier for this session. This identifier is unique within the cluster at any point in time but can be reused when the session closes.
AUDIT_TYPE	VARCHAR	The type of operation for the audit, in this case, Table.
AUDIT_TAG_NAME	VARCHAR	The tag for the specific table.
REQUEST_TYPE	VARCHAR	The type of query request. In this case, QUERY.
REQUEST_ID	INTEGER	Unique identifier of the query request in the user session.
SUBJECT	VARCHAR	The name of the table that was queried.
REQUEST	VARCHAR	Lists the query request.
SUCCESS	VARCHAR	Indicates whether or not the operation was successful.
CATEGORY	VARCHAR	The audit parent category—for example, `Views`, `Security`, and `Managing_Users_Privileges`.

Examples

The following example shows recent queries on configuration parameters:

dbadmin=> SELECT issued_time, audit_type, request_type, subject, request, category FROM log_tables
   WHERE category ilike '%Managing_Config_Parameters%' ORDER BY issued_time DESC LIMIT 4;
-[ RECORD 1 ]+-------------------------------------------------------------------------------------
issued_time  | 2020-05-14 14:14:53.453552-04
audit_type   | Table
request_type | QUERY
subject      | vs_nodes
request      | SELECT * from vs_nodes order by name  limit 1;
category     | Managing_Config_Parameters
-[ RECORD 2 ]+-------------------------------------------------------------------------------------
issued_time  | 2020-05-14 14:14:27.546474-04
audit_type   | Table
request_type | QUERY
subject      | vs_nodes
request      | SELECT * from vs_nodes order by name ;
category     | Managing_Config_Parameters
-[ RECORD 3 ]+-------------------------------------------------------------------------------------
issued_time  | 2020-05-14 08:54:32.86881-04
audit_type   | Table
request_type | QUERY
subject      | vs_parameters_mismatch
request      | select * from configuration_parameters where parameter_name = 'MaxDepotSizePercent';
category     | Managing_Config_Parameters
-[ RECORD 4 ]+-------------------------------------------------------------------------------------
issued_time  | 2020-05-14 08:54:32.86881-04
audit_type   | Table
request_type | QUERY
subject      | vs_nodes
request      | select * from configuration_parameters where parameter_name = 'MaxDepotSizePercent';
category     | Managing_Config_Parameters

Sql-Reference: MATERIALIZE_FLEXTABLE_COLUMNS_RESULTS

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

Contains the results of running the MATERIALIZE_FLEXTABLE_COLUMNS function. The table contains information about keys that the function evaluated. It does not contain information about all keys.

Column Name	Data Type	Description
`TABLE_ID`	INTEGER	Unique numeric ID assigned by the OpenText™ Analytics Database catalog, which identifies the table.
`TABLE_SCHEMA`	VARCHAR	The schema name for which information is listed.
`TABLE_NAME`	VARCHAR	The table name for which information is listed.
`CREATION_TIME`	VARCHAR	Timestamp when the key was materialized.
`KEY_NAME`	VARCHAR	Name of the key from the VMap column that was materialized.
`STATUS`	VARCHAR	Status of the materialized column, one of the following: `ADDED` `EXISTS` `ERROR`
`MESSAGE`	BOOLEAN	Message associated with the status in the previous column, one of the following: `Added successfully` `Column of same name already exists in table definition` `Add operation failed` `No data type guess provided to add column`

Examples

=> \x
Expanded display is on.
=> SELECT table_id, table_schema, table_name, key_name, status, message FROM MATERIALIZE_FLEXTABLE_COLUMNS_RESULTS
WHERE table_name = 'mountains_hybrid';
-[ RECORD 1 ]+-------------------------------------------------------
table_id     | 45035996273708192
table_schema | public
table_name   | mountains_hybrid
key_name     | type
status       | ADDED
message      | Added successfully
-[ RECORD 2 ]+-------------------------------------------------------
table_id     | 45035996273708192
table_schema | public
table_name   | mountains_hybrid
key_name     | height
status       | ADDED
message      | Added successfully
-[ RECORD 3 ]+-------------------------------------------------------
table_id     | 45035996273708192
table_schema | public
table_name   | mountains_hybrid
key_name     | name
status       | EXISTS
message      | Column of same name already exists in table definition

Sql-Reference: MODELS

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

Lists details about the machine-learning models in the database.

Column Name	Data Type	Description
`MODEL_ID`	INTEGER	The model's internal ID.
`MODEL_NAME`	VARCHAR(128)	The name of the model.
`SCHEMA_ID`	INTEGER	The schema's internal ID.
`SCHEMA_NAME`	VARCHAR(128)	The name of the schema.
`OWNER_ID`	INTEGER	The model owner's ID.
`OWNER_NAME`	VARCHAR(128)	The user who created the model.
`CATEGORY`	VARCHAR(128)	The type of model. By default, models created in OpenText™ Analytics Database are assigned to the Vertica_Models category.
`MODEL_TYPE`	VARCHAR(128)	The type of algorithm used to create the model.
`IS_COMPLETE`	VARCHAR(128)	Denotes whether the model is complete and ready for use in machine learning functions. This field is usually false when the model is being trained. Once the training is complete, the field is set to true.
`CREATE_TIME`	TIMESTAMPTZ	The time the model was created.
`SIZE`	INTEGER	The size of the model in bytes.
`IS_INHERIT_PRIVILEGES`	BOOLEAN	Whether the model inherits the privileges of its parent schema.

Examples

=> SELECT * FROM models;
-[ RECORD 1 ]---------+------------------------------
model_id              | 45035996273850350
model_name            | xgb_iris
schema_id             | 45035996273704984
schema_name           | public
owner_id              | 45035996273704962
owner_name            | dbadmin
category              | VERTICA_MODELS
model_type            | XGB_CLASSIFIER
is_complete           | t
create_time           | 2022-11-29 13:38:59.259531-05
size                  | 11018
is_inherit_privileges | f
-[ RECORD 2 ]---------+------------------------------
model_id              | 45035996273866816
model_name            | arima_weather
schema_id             | 45035996273704984
schema_name           | public
owner_id              | 45035996273704962
owner_name            | dbadmin
category              | VERTICA_MODELS
model_type            | ARIMA
is_complete           | t
create_time           | 2023-03-31 13:13:06.342661-05
size                  | 2770
is_inherit_privileges | f

Sql-Reference: NAMESPACES

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

Lists details about the namespaces in an Eon Mode database.

Column Name	Data Type	Description
NAMESPACE_OID	INTEGER	Catalog-assigned numeric value that uniquely identifies the namesapce.
NAMESPACE_NAME	VARCHAR	Name of the namespace
IS_DEFAULT	BOOLEAN	Whether the namespace is the default namespace of the database.
DEFAULT_SHARD_COUNT	VARCHAR	Shard count of the namespace.

Example

List the details of all namespaces in your database:

=> SELECT * FROM NAMESPACES;
   namespace_oid   |  namespace_name   | is_default | default_shard_count
-------------------+-------------------+------------+---------------------
 45035996273704988 | default_namespace | t          |                   9
 32582959204859183 | analytics         | f          |                  12
(2 rows)

Sql-Reference: NETWORK_ADDRESSES

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

Lists information about the network addresses defined in your database using the CREATE NETWORK ADDRESS statement.

Column Name	Data Type	Description
NAME	VARCHAR	The name of the network address.
NODE	VARCHAR	The name of the node that owns the network address.
ADDRESS	VARCHAR	The network address's IP address. This address can be either in IPv4 or IPv6 format.
PORT	INT	The network address's port number.
ADDRESS_FAMILY	VARCHAR	The format of the network address's IP address. This values is either 'ipv4' or 'ipv6'.
IS_ENABLED	BOOLEAN	Whether the network address is enabled. You can disable network addresses to prevent their use. If the address is disabled, the value in this column is False.
IS_AUTO_DETECTED	BOOLEAN	Whether OpenText™ Analytics Database created the network address automatically.

Examples

=> \x
Expanded display is on.

=> SELECT * FROM v_catalog.network_addresses;
-[ RECORD 1 ]----+-----------------
name             | node01
node             | v_vmart_node0001
address          | 10.20.100.247
port             | 5433
address_family   | ipv4
is_enabled       | t
is_auto_detected | f
-[ RECORD 2 ]----+-----------------
name             | node02
node             | v_vmart_node0002
address          | 10.20.100.248
port             | 5433
address_family   | ipv4
is_enabled       | t
is_auto_detected | f
-[ RECORD 3 ]----+-----------------
name             | node03
node             | v_vmart_node0003
address          | 10.20.100.249
port             | 5433
address_family   | ipv4
is_enabled       | t
is_auto_detected | f

Sql-Reference: NODE_SUBSCRIPTION_CHANGE_PHASES

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

In an Eon Mode database, stores information about changes to node's shard subscriptions.

Column Name	Data Type	Description
node_name	VARCHAR	Name of the node
subscription_change_type	VARCHAR	The change being made to the subscription
session_id	INTEGER	ID of the session in which the change was initiated
transaction_id	INTEGER	ID of the transaction in which the change was initiated
user_id	INTEGER	ID of user that initiated the change
user_name	VARCHAR	Name of user that initiated the change
subscription_oid	INTEGER	Session object ID
subscriber_node_oid	INTEGER	Object ID of node that requested the subscription
subscriber_node_name	VARCHAR	Name of the node that requested the subscription
shard_oid	INTEGER	Object ID of the shard to which the node is subscribed
shard_name	VARCHAR	Name of the shard to which the node is subscribed
min_time	TIMESTAMPTZ	Start time of the subscription change
max_time	TIMESTAMPTZ	Completion time of the subscription change
source_node_oid	INTEGER	Object ID of the node from which catalog objects were fetched
source_node_name	VARCHAR	Name of the node from which catalog objects were fetched
num_objs_affected	INTEGER	Number of catalog objects affected by the subscription change
action	VARCHAR	Description of the action taken
new_content_size	INTEGER	Total size of the catalog objects that were fetched for the subscription change
phase_limit_reached	BOOLEAN	Reached maximum number of retries?
START_TIME	TIMESTAMPTZ	When the subscription change started
END_TIME	TIMESTAMPTZ	When the subscription change was finished
retried	BOOLEAN	Retry of subscription phase?
phase_result	VARCHAR	Outcome of the subscription change, one of the following: Success Failure

Examples

=> SELECT NODE_NAME, SUBSCRIPTION_CHANGE_TYPE, SHARD_NAME,
   ACTION  FROM node_subscription_change_phases
   ORDER BY start_time ASC LIMIT 10;

      NODE_NAME       | SUBSCRIPTION_CHANGE_TYPE | SHARD_NAME  |         ACTION
----------------------+--------------------------+-------------+------------------------
 v_verticadb_node0001 | CREATE SUBSCRIPTION      | segment0007 | COLLECT SHARD METADATA
 v_verticadb_node0001 | CREATE SUBSCRIPTION      | segment0010 | COLLECT SHARD METADATA
 v_verticadb_node0001 | CREATE SUBSCRIPTION      | segment0004 | COLLECT SHARD METADATA
 v_verticadb_node0001 | CREATE SUBSCRIPTION      | segment0005 | COLLECT SHARD METADATA
 v_verticadb_node0001 | CREATE SUBSCRIPTION      | replica     | COLLECT SHARD METADATA
 v_verticadb_node0001 | CREATE SUBSCRIPTION      | segment0005 | COLLECT SHARD METADATA
 v_verticadb_node0001 | CREATE SUBSCRIPTION      | segment0006 | COLLECT SHARD METADATA
 v_verticadb_node0001 | CREATE SUBSCRIPTION      | segment0008 | COLLECT SHARD METADATA
 v_verticadb_node0001 | CREATE SUBSCRIPTION      | segment0011 | COLLECT SHARD METADATA
 v_verticadb_node0001 | CREATE SUBSCRIPTION      | segment0002 | COLLECT SHARD METADATA

Sql-Reference: NODE_SUBSCRIPTIONS

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

Eon Mode only

Lists information about database node subscriptions to shards.

Column Name	Data Type	Description
SUBSCRIPTION_OID	INTEGER	Subscription OID
NODE_OID	INTEGER	Subscribed node OID
NODE_NAME	VARCHAR	Name of the node
SHARD_OID	INTEGER	OID of the shard to which the node is subscribed
SHARD_NAME	VARCHAR	Name of the shard to which the node is subscribed
SUBSCRIPTION_STATE	VARCHAR	Node's current subscription state
FROM _VERSION	INTEGER	Deprecated
IS_PRIMARY	BOOLEAN	Specifies whether the node is currently the primary subscriber.
IS_RESUBSCRIBING	BOOLEAN	Indicates whether a subscription is resubscribing to a node: `t` (true): A subscription is resubscribing, only applies to PENDING subscriptions created during the cluster or node startup. `f` (false): A subscription is not resubscribing, applies to PENDING subscriptions created with REBALANCE_SHARDS that transitioned to an ACTIVE state.
CREATOR_TID	INTEGER	ID of transaction that created this subscription
SUBSCRIBED_TO_METADATA_AT	INTEGER	Deprecated
IS_PARTICIPATING_PRIMARY	BOOLEAN	Whether this node is the participating primary subscriber for the shard. If true, the node listed in NODE_NAME is the only one that reads from and writes to communal storage for this shard in the subcluster. Other nodes in the subcluster that subscribe to the same shard receive data from this node via peer-to-peer transfers.

Examples

The following example queries the NODE_SUBSCRIPTIONS table in a database with two three-node subclusters (a primary and a secondary) in a 12-shard database.

=> SELECT node_name, shard_name, subscription_state, is_primary,
          is_participating_primary AS is_p_primary
       FROM NODE_SUBSCRIPTIONS ORDER BY node_name, shard_name;

      node_name       | shard_name  | subscription_state | is_primary | is_p_primary
----------------------+-------------+--------------------+------------+--------------
 v_verticadb_node0001 | replica     | ACTIVE             | t          | t
 v_verticadb_node0001 | segment0001 | ACTIVE             | t          | t
 v_verticadb_node0001 | segment0003 | ACTIVE             | f          | f
 v_verticadb_node0001 | segment0004 | ACTIVE             | t          | t
 v_verticadb_node0001 | segment0006 | ACTIVE             | f          | f
 v_verticadb_node0001 | segment0007 | ACTIVE             | t          | t
 v_verticadb_node0001 | segment0009 | ACTIVE             | f          | f
 v_verticadb_node0001 | segment0010 | ACTIVE             | t          | t
 v_verticadb_node0001 | segment0012 | ACTIVE             | f          | f
 v_verticadb_node0002 | replica     | ACTIVE             | f          | t
 v_verticadb_node0002 | segment0001 | ACTIVE             | f          | f
 v_verticadb_node0002 | segment0002 | ACTIVE             | t          | t
 v_verticadb_node0002 | segment0004 | ACTIVE             | f          | f
 v_verticadb_node0002 | segment0005 | ACTIVE             | t          | t
 v_verticadb_node0002 | segment0007 | ACTIVE             | f          | f
 v_verticadb_node0002 | segment0008 | ACTIVE             | t          | t
 v_verticadb_node0002 | segment0010 | ACTIVE             | f          | f
 v_verticadb_node0002 | segment0011 | ACTIVE             | t          | t
 v_verticadb_node0003 | replica     | ACTIVE             | f          | t
 v_verticadb_node0003 | segment0002 | ACTIVE             | f          | f
 v_verticadb_node0003 | segment0003 | ACTIVE             | t          | t
 v_verticadb_node0003 | segment0005 | ACTIVE             | f          | f
 v_verticadb_node0003 | segment0006 | ACTIVE             | t          | t
 v_verticadb_node0003 | segment0008 | ACTIVE             | f          | f
 v_verticadb_node0003 | segment0009 | ACTIVE             | t          | t
 v_verticadb_node0003 | segment0011 | ACTIVE             | f          | f
 v_verticadb_node0003 | segment0012 | ACTIVE             | t          | t
 v_verticadb_node0004 | replica     | ACTIVE             | f          | t
 v_verticadb_node0004 | segment0001 | ACTIVE             | f          | t
 v_verticadb_node0004 | segment0003 | ACTIVE             | f          | f
 v_verticadb_node0004 | segment0004 | ACTIVE             | f          | t
 v_verticadb_node0004 | segment0006 | ACTIVE             | f          | f
 v_verticadb_node0004 | segment0007 | ACTIVE             | f          | t
 v_verticadb_node0004 | segment0009 | ACTIVE             | f          | f
 v_verticadb_node0004 | segment0010 | ACTIVE             | f          | t
 v_verticadb_node0004 | segment0012 | ACTIVE             | f          | f
 v_verticadb_node0005 | replica     | ACTIVE             | f          | t
 v_verticadb_node0005 | segment0001 | ACTIVE             | f          | f
 v_verticadb_node0005 | segment0002 | ACTIVE             | f          | t
 v_verticadb_node0005 | segment0004 | ACTIVE             | f          | f
 v_verticadb_node0005 | segment0005 | ACTIVE             | f          | t
 v_verticadb_node0005 | segment0007 | ACTIVE             | f          | f
 v_verticadb_node0005 | segment0008 | ACTIVE             | f          | t
 v_verticadb_node0005 | segment0010 | ACTIVE             | f          | f
 v_verticadb_node0005 | segment0011 | ACTIVE             | f          | t
 v_verticadb_node0006 | replica     | ACTIVE             | f          | t
 v_verticadb_node0006 | segment0002 | ACTIVE             | f          | f
 v_verticadb_node0006 | segment0003 | ACTIVE             | f          | t
 v_verticadb_node0006 | segment0005 | ACTIVE             | f          | f
 v_verticadb_node0006 | segment0006 | ACTIVE             | f          | t
 v_verticadb_node0006 | segment0008 | ACTIVE             | f          | f
 v_verticadb_node0006 | segment0009 | ACTIVE             | f          | t
 v_verticadb_node0006 | segment0011 | ACTIVE             | f          | f
 v_verticadb_node0006 | segment0012 | ACTIVE             | f          | t
(54 rows)

Sql-Reference: NODES

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

Lists details about the nodes in the database.

Column Name	Data Type	Description
NODE_NAME	VARCHAR(128)	The name of the node.
NODE_ID	INTEGER	Catalog-assigned integer value that uniquely identifies the node.
NODE_STATE	VARCHAR(128)	The node's current state, one of the following: UP DOWN READY UNSAFE SHUTDOWN SHUTDOWN_ERROR RECOVERING RECOVER_ERROR RECOVERED INITIALIZING STANDBY NEEDS_CATCHUP
IS_PRIMARY	BOOLEAN	Whether the node is a primary or secondary node. Primary nodes are the only ones OpenText™ Analytics Database considers when determining the K-Safety of an Eon Mode database. The node inherits this property from the subcluster that contains it.
IS_READONLY	BOOLEAN	Whether the node is in read-only mode or not. This column is TRUE if the Eon Mode database is read-only due to the loss of quorum or primary shard coverage. See Database Read-Only Mode.
NODE_ADDRESS	VARCHAR(80)	The host address of the node.
NODE_ADDRESS_FAMILY	VARCHAR(10)	The IP Version of the `node_address`. For example, `ipv4`.
EXPORT_ADDRESS	VARCHAR(8192)	The IP address of the node (on the public network) used for import/export operations and native load-balancing.
EXPORT_ADDRESS_FAMILY	VARCHAR(10)	The IP Version of the `export_address`. For example, `ipv4`.
CATALOG_PATH	VARCHAR(8192)	The absolute path to the catalog on the node.
NODE_TYPE	VARCHAR(9)	The type of the node. For more information on the types of nodes, refer to Setting node type.
IS_EPHEMERAL	BOOLEAN	(Deprecated) True if this node has been marked as ephemeral. (in preparation for removing it from the cluster).
STANDING_IN_FOR	VARCHAR(128)	The name of the node that this node is currently replacing.
SUBCLUSTER_NAME	VARCHAR(128)	In an Eon Mode database, the name of the subcluster that contains the node. Nodes belong to exactly one subcluster.
SANDBOX	VARCHAR(128)	In an Eon Mode database, the name, if any, of the sandbox to which the node belongs. NULL if the node is not a member of an active sandbox.
LAST_MSG_FROM_NODE_AT	TIMESTAMPTZ	The date and time the last message was received from this node.
NODE_DOWN_SINCE	TIMESTAMPTZ	The amount of time that the replaced node has been unavailable.
BUILD_INFO	VARCHAR(128)	The version of the database server binary the node is running.

Example

=> SELECT NODE_NAME, NODE_STATE, IS_PRIMARY, IS_READONLY, NODE_TYPE,
          SUBCLUSTER_NAME FROM NODES ORDER BY NODE_NAME ASC;
      NODE_NAME       | NODE_STATE | IS_PRIMARY | IS_READONLY | NODE_TYPE |  SUBCLUSTER_NAME
----------------------+------------+------------+-------------+-----------+--------------------
 v_verticadb_node0001 | UP         | t          | f           | PERMANENT | default_subcluster
 v_verticadb_node0002 | UP         | t          | f           | PERMANENT | default_subcluster
 v_verticadb_node0003 | UP         | t          | f           | PERMANENT | default_subcluster
 v_verticadb_node0004 | UP         | f          | f           | PERMANENT | analytics
 v_verticadb_node0005 | UP         | f          | f           | PERMANENT | analytics
 v_verticadb_node0006 | UP         | f          | f           | PERMANENT | analytics
(6 rows)

Sql-Reference: ODBC_COLUMNS

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

Provides table column information. The format is defined by the ODBC standard for the ODBC SQLColumns metadata. Details on the ODBC SQLColumns format are available in the ODBC specification: http://msdn.microsoft.com/en-us/library/windows/desktop/ms711683%28v=vs.85%29.aspx.

Column Name	Data Type	Description
`SCHEMA_NAME`	VARCHAR	Name of the schema in which the column resides. If the column does not reside in a schema, this field is empty.
`TABLE_NAME`	VARCHAR	Name of the table in which the column resides.
`COLUMN_NAME`	VARCHAR	Name of the column.
`DATA_TYPE`	INTEGER	Data type of the column. This can be an ODBC SQL data type or a driver-specific SQL data type. This column corresponds to the ODBC_TYPE column in the TYPES table.
`DATA_TYPE_NAME`	VARCHAR	Driver-specific data type name.
`COLUMN_SIZE`	INTEGER	ODBC-defined data size of the column.
`BUFFER_LENGTH`	INTEGER	Transfer octet length of a column is the maximum number of bytes returned to the application when data is transferred to its default C data type. See http://msdn.microsoft.com/en-us/library/windows/desktop/ms713979%28v=vs.85%29.aspx
`DECIMAL_DIGITS`	INTEGER	Total number of significant digits to the right of the decimal point. This value has no meaning for non-decimal data types.
`NUM_PREC_RADIX`	INTEGER	Radix OpenText™ Analytics Database reports decimal_digits and columns_size as. This value is always 10, because it refers to a number of decimal digits, rather than a number of bits.
`NULLABLE`	BOOLEAN	Whether the column can contain null values.
`REMARKS`	VARCHAR	Textual remarks for the column.
`COLUMN_DEFAULT`	VARCHAR	Default value of the column.
`SQL_TYPE_ID`	INTEGER	SQL data type of the column.
`SQL_DATETIME_SUB`	VARCHAR	Subtype for a datetime data type. This value has no meaning for non-datetime data types.
`CHAR_OCTET_LENGTH`	INTEGER	Maximum length of a string or binary data column.
`ORDINAL_POSITION`	INTEGER	Position of the column in the table definition.
`IS_NULLABLE`	VARCHAR	Values can be YES or NO, determined by the value of the NULLABLE column.
`IS_IDENTITY`	BOOLEAN	Whether the column is an IDENTITY column.

OpenText Analytics Database 26.2.x – V_CATALOG schema

Sql-Reference: ACCESS_POLICY

Privileges

Examples

Sql-Reference: ALL_RESTORE_POINTS

Sql-Reference: ALL_TABLES

Examples

Sql-Reference: AUDIT_MANAGING_USERS_PRIVILEGES

Sql-Reference: CA_BUNDLES

Privileges

Joining with CERTIFICATES

See also

Sql-Reference: CATALOG_SUBSCRIPTION_CHANGES

Sql-Reference: CATALOG_SYNC_STATE

Sql-Reference: CATALOG_TRUNCATION_STATUS

Sql-Reference: CERTIFICATES

Examples

Sql-Reference: CLIENT_AUTH

Examples

See also

Sql-Reference: CLIENT_AUTH_PARAMS

Examples

Sql-Reference: CLUSTER_LAYOUT

Note

Note

See also

Sql-Reference: COLUMNS

Examples

Sql-Reference: COMMENTS

Note

Examples

Sql-Reference: COMPLEX_TYPES

Examples

Sql-Reference: CONSTRAINT_COLUMNS

Privileges

Sql-Reference: CRYPTOGRAPHIC_KEYS

Examples

Sql-Reference: DATA_LOADERS

Examples

Sql-Reference: DATABASES

Examples

Sql-Reference: DIRECTED_QUERIES

Privileges

Truncated query results

Sql-Reference: DUAL

Restrictions

Sql-Reference: ELASTIC_CLUSTER

Privileges

See also

Sql-Reference: EPOCHS

Examples

Querying for historical data

See also

Sql-Reference: FAULT_GROUPS

Examples

See also

Sql-Reference: FOREIGN_KEYS

Examples

Sql-Reference: GRANTS

Note

Examples

See also

Sql-Reference: HCATALOG_COLUMNS

Privileges

Notes

Examples

See also

Sql-Reference: HCATALOG_SCHEMATA

Privileges

See also

Sql-Reference: HCATALOG_TABLE_LIST

Privileges

Notes

Examples

See also

Sql-Reference: HCATALOG_TABLES

Privileges

See also

Sql-Reference: ICEBERG_COLUMNS

Sql-Reference: ICEBERG_NAMESPACES