OpenText Analytics Database 26.2.x – V_MONITOR schema

Sql-Reference: ACTIVE_EVENTS

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

Returns all active events in the cluster. See Monitoring events.

Column Name	Data Type	Description
`NODE_NAME`	VARCHAR	The node name where the event occurred.
`EVENT_CODE`	INTEGER	A numeric ID that indicates the type of event. See Event Types for a list of event type codes.
`EVENT_ID`	INTEGER	A unique numeric ID assigned by the OpenText™ Analytics Database catalog, which identifies the specific event.
`EVENT_SEVERITY`	VARCHAR	The severity of the event from highest to lowest. These events are based on standard syslog severity types. 0—Emergency 1—Alert 2—Critical 3—Error 4—Warning 5—Notice 6—Informational 7—Debug
`EVENT_POSTED_TIMESTAMP`	TIMESTAMP	The year, month, day, and time the event was reported. The time is posted in military time.
`EVENT_EXPIRATION`	VARCHAR	The year, month, day, and time the event expire. The time is posted in military time. If the cause of the event is still active, the event is posted again.
`EVENT_CODE_DESCRIPTION`	VARCHAR	A brief description of the event and details pertinent to the specific situation.
`EVENT_PROBLEM_DESCRIPTION`	VARCHAR	A generic description of the event.
`REPORTING_NODE`	VARCHAR	The name of the node within the cluster that reported the event.
`EVENT_SENT_TO_CHANNELS`	VARCHAR	The event logging mechanisms that are configured for the database. These can include `vertica.log`, (configured by default) syslog, and SNMP.
`EVENT_POSTED_COUNT`	INTEGER	Tracks the number of times an event occurs. Rather than posting the same event multiple times, the database posts the event once and then counts the number of additional instances in which the event occurs.

Sql-Reference: ALLOCATOR_USAGE

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

Provides real-time information on the allocation and reuse of memory pools for a OpenText™ Analytics Database node.

There are two memory pools in the database, global and SAL. The global memory pool is related to the database catalog objects. The SAL memory pool is related to the system storage layer. These memory pools are physical structures from which the database allocates and reuses portions of memory.

Within the memory pools, there are two allocation types. Both global and SAL memory pools include chunk and object memory allocation types.

Chunk allocations are from tiered storage, and are grouped into sizes, in bytes, that are powers of 2.
Object allocations are object types, for example, a table or projection. Each object assumes a set size.

The table provides detailed information on these memory pool allocations.

Column Name	Data Type	Description
`NODE_NAME`	VARCHAR	The name of the node from which the database has collected this allocator information.
`POOL_NAME`	VARCHAR	One of two memory pools: global: Memory pool is related to the database catalog objects. SAL: Memory pool is related to the system storage layer.
`ALLOCATION_TYPE`	VARCHAR	One of two memory allocation types: chunk: Chunk allocations are grouped into sizes that are powers of 2. object: Object allocations assume a set amount of memory based upon the specific object.
`UNIT_SIZE`	INTEGER	The size, in bytes, of the memory allocation. For example, if the allocation type is a table (an object type), the database allots 8 bytes.
`FREE_COUNT`	INTEGER	Indicates the count of blocks of freed memory that the database has reserved for future memory needs. For example, if you delete a table, the database reserves the 8 bytes originally allotted for the table. The 8 bytes freed become 1 unit of memory that the database adds to this column.
`FREE_BYTES`	INTEGER	Indicates the number of freed memory bytes. For example, with a table deletion, the database adds 8 bytes to this column. Note The database does not release memory after originally allocating it, unless the node or database is restarted.
`USED_COUNT`	INTEGER	Indicates the count of in-use blocks for this allocation. For example, if your database includes two table objects, the database adds 2 to this column.
`USED_BYTES`	INTEGER	The number of bytes of in-use blocks of memory. For example, if your database includes two table objects, each of which assume 8 bytes, the database adds 16 to this column.
`TOTAL_SIZE`	INTEGER	Indicates the number of bytes that is the sum of all free and used memory.
`CAPTURE_TIME`	TIMESTAMPTZ	Indicates the current timestamp for when the database collected the data for this table.
`ALLOCATION_NAME`	VARCHAR	Provides the name of the allocation type. If the allocation is an object type, provides the name of the object. For example, `CAT::Schema`. Object types can also have the name `internal`, meaning that the object is an internal data structure. Those object types that are not internal are prefaced with either `CAT` or `SAL`. Those prefaced with `CAT` indicate memory from the global memory pool. `SAL` indicates memory from the system storage memory pool. If the allocation type is chunk, indicates a power of 2 in this field to represent the number of bytes assumed by the chunk. For example, `2^5`.

Sample: how memory pool memory is allotted, retained, and freed

The following table shows sample column values based upon a hypothetical example. The sample illustrates how column values change based upon addition or deletion of a table object.

When you add a table object (t1), the database assumes a UNIT_SIZE of 8 bytes, with a USED_COUNT of 1.
When you add a second table object (t2), the USED_COUNT increases to 2. Since each object assumes 8 bytes, USED_BYTES increases to 16.
When you delete one of the two table objects, the database USED_COUNT decreases to 1, and USED_BYTES decreases to 8. Since the database retains the memory for future use, FREE_BYTES increases to 8, and FREE_COUNT increases to 1.
Finally, when you create a new table object (t3), the database frees the memory for reuse. FREE_COUNT and FREE_BYTES return to 0.

Column Names	Add One Table Object (t1)	Add a Second Table Object (t2)	Delete a Table Object (t2)	Create a New Table Object (t3)
`NODE_NAME`	`v_vmart_node0001`	`v_vmart_node0001`	`v_vmart_node0001`	`v_vmart_node0001`
`POOL_NAME`	`global`	`global`	`global`	`global`
`ALLOCATION_TYPE`	`object`	`object`	`object`	`object`
`UNIT_SIZE`	8	8	8	8
`FREE_COUNT`	0	0	1	0
`FREE_BYTES`	0	0	8	0
`USED_COUNT`	1	2	1	2
`USED_BYTES`	8	16	8	16
`TOTAL_SIZE`	8	16	16	16
`CAPTURE_TIME`	`2017-05-24 13:28:07.83855-04`	`2017-05-24 14:16:04.480953-04`	`2017-05-24 14:16:32.077322-04`	`2017-05-24 14:17:07.320745-04`
`ALLOCATION_NAME`	`CAT::Table`	`CAT::Table`	`CAT::Table`	`CAT::Table`

Examples

The following example shows one sample record for a chunk allocation type, and one for an object type.

=> \x
Expanded display is on.


=> select * from allocator_usage;
-[ RECORD 1 ]---+-----------------------------
node_name       | v_vmart_node0004
pool_name       | global
allocation_type | chunk
unit_size       | 8
free_count      | 1069
free_bytes      | 8552
used_count      | 7327
used_bytes      | 58616
total_size      | 67168
capture_time    | 2017-05-24 13:28:07.83855-04
allocation_name | 2^3
.
.
.
-[ RECORD 105 ]-+------------------------------
node_name       | v_vmart_node0004
pool_name       | SAL
allocation_type | object
unit_size       | 128
free_count      | 0
free_bytes      | 0
used_count      | 2
used_bytes      | 256
total_size      | 256
capture_time    | 2017-05-24 14:44:30.153892-04
allocation_name | SAL::WOSAlloc
.
.
.

Sql-Reference: ARCHIVE_RESTORE_POINTS

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

Eon Mode only

Lists information about In-DB restore points.

Column Name	Column Type	Description
`ID`	INT	Unique object ID of the restore point.
`SAVE_TIME`	DATETIME	Time at which the restore point was saved.
`INDEX`	INT	Index of the restore point in the archive, where 1 specifies the most recent restore point.
`ARCHIVE`	VARCHAR	Name of the archive that contains the restore point.
`STATE`	VARCHAR	Status of the restore points, one of the following: `SAVING` `COMPLETE` `REMOVING`

Examples

List details for all restore points in your database:

=> SELECT * FROM ARCHIVE_RESTORE_POINTS;
                  id                  |         save_time          | index |     archive     |  state 
--------------------------------------+----------------------------+-------+-----------------+----------
 2616f6cd-e98c-472c-8d5c-a7f459dff82b | 2023-11-30 10:19:58.565311 |     1 | vertica-restore | COMPLETE
 116066cc-29cb-4ce5-9a27-170538ba95cf | 2023-11-10 11:02:48.059941 |     2 | vertica-restore | COMPLETE
(2 rows)

Sql-Reference: ARCHIVES

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

Eon Mode only

Lists information about In-DB restore points archives.

Column Name	Column Type	Description
`NAME`	VARCHAR	Archive name.
`LIMIT_COUNT`	INT	Maximum number of restore points stored in the archive.
`OWNER`	VARCHAR	Owner of the archive.
`OBJECT_INCLUSION_RULES`	VARCHAR	Currently, only database-level restore points are supported, so this column is always empty.
`DATA_INCLUSION RULES`	VARCHAR	Currently, only database-level restore points are supported, so this column is always empty.

Examples

List all archives and their attributes:

=> select * from archives;
 name | limit_count | owner | object_inclusion_rules | data_inclusion_rules
------+-------------+-------+------------------------+----------------------
 eon  | 10          | luis  |                        |
(1 row)

Sql-Reference: COLUMN_STORAGE

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

Returns the amount of disk storage used by each column of each projection on each node.

Column Name	Data Type	Description
NODE_NAME	VARCHAR	The node name for which information is listed.
COLUMN_ID	INTEGER	Catalog-assigned integer value that uniquely identifies thecolumn.
COLUMN_NAME	VARCHAR	The column name for which information is listed.
ROW_COUNT	INTEGER	The number of rows in the column.
USED_BYTES	INTEGER	The disk storage allocation of the column in bytes.
ENCODINGS	VARCHAR	The encoding type for the column.
COMPRESSION	VARCHAR	The compression type for the column. You can compare `ENCODINGS` and `COMPRESSION` columns to see how different encoding types affect column storage when optimizing for compression.
ROS_COUNT	INTEGER	The number of ROS containers.
PROJECTION_ID	INTEGER	Catalog-assigned numeric value that uniquely identifies the projection.
PROJECTION_NAME	VARCHAR	The associated projection name for the column.
PROJECTION_SCHEMA	VARCHAR	The name of the schema associated with the projection.
ANCHOR_TABLE_ID	INTEGER	Catalog-assigned integer value that uniquely identifies theanchor table.
ANCHOR_TABLE_NAME	VARCHAR	The associated table name.
ANCHOR_TABLE_SCHEMA	VARCHAR	The associated table's schema name. 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`.
ANCHOR_TABLE_NAMESPACE	VARCHAR	For Eon Mode databases, name of the namespace that contains the table.
ANCHOR_TABLE_COLUMN_ID	VARCHAR	Catalog-assigned VARCHAR value that uniquely identifies a table column.
ANCHOR_TABLE_COLUMN_NAME	VARCHAR	The name of the anchor table.

Sql-Reference: COMMUNAL_CLEANUP_RECORDS

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

Eon Mode only

This system table lists files that OpenText™ Analytics Database considers leaked on an Eon Mode communal storage. Leaked files are files that are detected as needing deletion but were missed by the normal cleanup mechanisms. This information helps you determine how much space on the communal storage you can reclaim or have reclaimed by cleaning up the leaked files.

Column Name	Data Type	Description
detection_timestamp	TIMESTAMPTZ	Timestamp at which the file was detected as leaked.
location_path	VARCHAR	The path of communal storage location.
file_name	VARCHAR	The name of the leaked file.
size_in_bytes	INTEGER	The size of the leaked file in bytes.
queued_for_delete	BOOLEAN	Specifies whether the file was queued for deletion. Files queued for deletion might not be deleted right away. Also, a subsequent call to clean_communal_storage reports these files as leaked if the files hadn't already been deleted.

Examples

=> SELECT clean_communal_storage('true');
                                                                     clean_communal_storage
----------------------------------------------------------------------------------------------------------------------------------------------
 CLEAN COMMUNAL STORAGE
Total leaked files: 10
Total size: 217088
Files have been queued for deletion.
Check communal_cleanup_records for more information.
(1 row)

=> SELECT * FROM communal_cleanup_records;
      detection_timestamp      | location_path     |                       file_name                       | size_in_bytes | queued_for_delete
-------------------------------+-------------------+-------------------------------------------------------+---------------+-------------------
 2018-05-01 17:01:34.045955-04 | s3://chumbucket/  | 020000000000000000000000000000000000000000000003_0.gt |         28672 | t
 2018-05-01 17:01:34.045966-04 | s3://chumbucket/  | 020000000000000000000000000000000000000000000006_0.gt |         28672 | t
 2018-05-01 17:01:34.045952-04 | s3://chumbucket/  | 020000000000000000000000000000000000000000000001_0.gt |         36864 | t
 2018-05-01 17:01:34.045974-04 | s3://chumbucket/  | 020000000000000000000000000000000000000000000008_0.gt |         36864 | t
 2018-05-01 17:01:34.045981-04 | s3://chumbucket/  | 020000000000000000000000000000000000000000000002_0.gt |         12288 | t
 2018-05-01 17:01:34.045986-04 | s3://chumbucket/  | 020000000000000000000000000000000000000000000007_0.gt |          8192 | t
 2018-05-01 17:01:34.045991-04 | s3://chumbucket/  | 020000000000000000000000000000000000000000000010_0.gt |         16384 | t
 2018-05-01 17:01:34.046001-04 | s3://chumbucket/  | 020000000000000000000000000000000000000000000005_0.gt |         24576 | t
 2018-05-01 17:01:34.046026-04 | s3://chumbucket/  | 020000000000000000000000000000000000000000000009_0.gt |          4096 | t
 2018-05-01 17:01:34.046033-04 | s3://chumbucket/  | 020000000000000000000000000000000000000000000004_0.gt |         20480 | t
(10 rows)

Sql-Reference: COMMUNAL_TRUNCATION_STATUS

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

Eon Mode only

Stores information on the state of the cluster in the case of a catalog truncation event.

Column Name	Data Type	Description
`CURRENT_CATALOG_VERSION`	`VARCHAR`	Current value of the catalog truncation version (CTV).
`CLUSTER_TRUNCATION_VERSION`	`VARCHAR`	The value of the CTV from the `cluster_config.json` file.

Examples

=> SELECT * FROM COMMUNAL_TRUNCATION_STATUS;
current_catalog_version  | cluster_truncation_version
-------------------------+----------------------------
                    35   |                        35

Sql-Reference: CONFIGURATION_CHANGES

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

Records the change history of system configuration parameters. This information is useful for identifying:

Who changed the configuration parameter value
When the configuration parameter was changed
Whether nonstandard settings were in effect in the past

Column Name	Data Type	Description
`EVENT_TIMESTAMP`	TIMESTAMPTZ	Time when the row was recorded.
`NODE_NAME`	VARCHAR	Name of the node that is reporting the requested information.
`USER_ID`	INTEGER	Identifier of the user who changed configuration parameters.
`USER_NAME`	VARCHAR	Name of the user who changed configuration parameters at the time OpenText™ Analytics Database recorded the session.
`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.
`PARAMETER`	VARCHAR	Name of the changed parameter. See Configuration parameter management for a detailed list of supported parameters.
`VALUE`	VARCHAR	New value of the configuration parameter.

Privileges

Superuser

Sql-Reference: CONFIGURATION_PARAMETERS

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

Provides information about all configuration parameters that are currently in use by the system.

Column Name	Data Type	Description
NODE_NAME	VARCHAR	Node names of the database cluster. ALL indicates that all nodes have the same value.
PARAMETER_NAME	VARCHAR	The parameter name.
CURRENT_VALUE	VARCHAR	The parameter's current setting.
RESTART_VALUE	VARCHAR	The parameter's value after the next restart.
DATABASE_VALUE	VARCHAR	The value that is set at the database level. If no database-level value is set, the value reflects the default value.
DEFAULT_VALUE	VARCHAR	The parameter's default value.
CURRENT_LEVEL	VARCHAR	Level at which CURRENT_VALUE is set, one of the following: NODE DATABASE SESSION DEFAULT
RESTART_LEVEL	VARCHAR	Level at which the parameter will be set after the next restart, one of the following: NODE DATABASE DEFAULT
IS_MISMATCH	BOOLEAN	Whether CURRENT_VALUE and RESTART_VALUE match.
GROUPS	VARCHAR	A group to which the parameter belongs—for example, OptVOptions. Note Most configuration parameters do not belong to any group.
ALLOWED_LEVELS	VARCHAR	Levels at which the specified parameter can be set, a comma-delimited list of any of the following values: DATABASE NODE SESSION USER
SUPERUSER_VISIBLE_ONLY	BOOLEAN	Whether non-superusers can view all parameter settings. If true, the following columns are masked to non-superusers: CURRENT_VALUE RESTART_VALUE DATABASE_VALUE DEFAULT_VALUE
CHANGE_UNDER_SUPPORT_GUIDANCE	BOOLEAN	Whether the parameter is intended for use only under guidance from customer support.
CHANGE_REQUIRES_RESTART	BOOLEAN	Whether the configuration change requires a restart.
DESCRIPTION	VARCHAR	Describes the parameter's usage.

Examples

The following example shows a case where the parameter requires a restart for the new setting to take effect:

=> SELECT * FROM CONFIGURATION_PARAMETERS WHERE parameter_name = 'RequireFIPS';
-[ RECORD 1 ]-----------------+----------------------
node_name                     | ALL
parameter_name                | RequireFIPS
current_value                 | 0
restart_value                 | 0
database_value                | 0
default_value                 | 0
current_level                 | DEFAULT
restart_level                 | DEFAULT
is_mismatch                   | f
groups                        |
allowed_levels                | DATABASE
superuser_visible_only        | f
change_under_support_guidance | f
change_requires_restart       | t
description                   | Execute in FIPS mode

The following example shows a case where a non-superuser is viewing a parameter with restricted visibility:

=> \c VMart nonSuperuser
You are now connected to database "VMart" as user "nonSuperuser".
=> SELECT * FROM CONFIGURATION_PARAMETERS WHERE superuser_visible_only = 't';
-[ RECORD 1 ]-----------------+-------------------------------------------------------
node_name                     | ALL
parameter_name                | S3BucketCredentials
current_value                 | ********
restart_value                 | ********
database_value                | ********
default_value                 | ********
current_level                 | DEFAULT
restart_level                 | DEFAULT
is_mismatch                   | f
groups                        |
allowed_levels                | SESSION, DATABASE
superuser_visible_only        | t
change_under_support_guidance | f
change_requires_restart       | f
description                   | JSON list mapping S3 buckets to specific credentials.

Sql-Reference: CPU_USAGE

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

Records CPU usage history on the system.

Column Name	Data Type	Description
`NODE_NAME`	VARCHAR	Name of the node that is reporting the requested information.
`START_TIME`	TIMESTAMP	Beginning of history interval.
`END_TIME`	TIMESTAMP	End of history interval.
`AVERAGE_CPU_USAGE_PERCENT`	FLOAT	Average CPU usage in percent of total CPU time (0-100) during history interval.
`PHYSICAL_CORES`	INTEGER	Number of physical cores used by the node.

Privileges

Superuser

Sql-Reference: CRITICAL_HOSTS

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

Lists the critical hosts whose failure would cause the database to become unsafe and force a shutdown.

Column Name	Data Type	Description
`HOST_NAME`	VARCHAR	Name of a critical host

Privileges

None

Sql-Reference: CRITICAL_NODES

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

Lists the critical nodes whose failure would cause the database to become unsafe and force a shutdown.

Column Name	Data Type	Description
`NODE_ID`	INTEGER	Catalog-assigned integer value that uniquely identifies thenode.
`NODE_NAME`	VARCHAR	Name of a critical node.

Sql-Reference: CRITICAL_SUBCLUSTERS

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

Lists the primary subclusters whose loss would cause the database to become unsafe and force it to shutdown. OpenText™ Analytics Database checks this table before stopping a subcluster to ensure it will not trigger a database shutdown. If you attempt to stop or remove a subcluster in this table, the database returns an error message. See Starting and stopping subclusters for more information.

This table only has contents when the database is in Eon Mode and when one or more subclusters are critical.

Column Name	Data Type	Description
SUBCLUSTER_OID	INTEGER	Unique identifier for the subcluster.
SUBCLUSTER_NAME	VARCHAR	The name of the subcluster in a critical state.

Examples

=> SELECT * FROM critical_subclusters;
  subcluster_oid   |  subcluster_name
-------------------+--------------------
 45035996273704996 | default_subcluster
(1 row)

Sql-Reference: CURRENT_SESSION

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

Returns information about the current active session. Use this table to find out the current session's sessionID and get the duration of the previously-run query.

Column Name	Data Type	Description
`NODE_NAME`	`VARCHAR`	Name of the node for which information is listed
`USER_NAME`	`VARCHAR`	Name used to log into the database, NULL if the session is internal
`CLIENT_OS_HOSTNAME`	`VARCHAR`	The hostname of the client as reported by their operating system.
`CLIENT_HOSTNAME`	`VARCHAR`	The IP address and port of the TCP socket from which the client connection was made; NULL if the session is internal. OpenText™ Analytics Database accepts either IPv4 or IPv6 connections from a client machine. If the client machine contains mappings for both IPv4 and IPv6, the server randomly chooses one IP address family to make a connection. This can cause the CLIENT_HOSTNAME column to display either IPv4 or IPv6 values, based on which address family the server chooses.
`TYPE`	`INTEGER`	Identifies the session type, one of the following integer values: 1: Client 2: DBD 3: Merge out 4: Move out 5: Rebalance cluster 6: Recovery 7: Refresh 8: Shutdown 9: License audit 10: Timer service 11: Connection 12: VSpread 13: Sub-session 14: Repartition table
`CLIENT_PID`	`INTEGER`	Process identifier of the client process that issued this connection. This process might be on a different machine than the server.
`LOGIN_TIMESTAMP`	`TIMESTAMP`	When the user logged into the database or the internal session was created. This column can help identify open sessions that are idle.
`SESSION_ID`	`VARCHAR`	Identifier required to close or interrupt a session. This identifier is unique within the cluster at any point in time, but can be reused when the session closes.
`CLIENT_LABEL`	`VARCHAR`	User-specified label for the client connection that can be set when using ODBC. See `Label` in ODBC DSN connection properties.
`TRANSACTION_START`	`TIMESTAMP`	When the current transaction started, NULL if no transaction is running
`TRANSACTION_ID`	`VARCHAR`	Hexadecimal identifier of the current transaction, NULL if no transaction is in progress
`TRANSACTION_DESCRIPTION`	`VARCHAR`	Description of the current transaction
`STATEMENT_START`	`TIMESTAMP`	When the current statement started execution, NULL if no statement is running
`STATEMENT_ID`	`VARCHAR`	Unique numeric ID for the currently-running statement, NULL if no statement is being processed. Combined, `TRANSACTION_ID` and `STATEMENT_ID` uniquely identify a statement within a session.
`LAST_STATEMENT_DURATION_US`	`INTEGER`	Duration in microseconds of the last completed statement
`CURRENT_STATEMENT`	`VARCHAR`	The currently-running statement, if any. NULL indicates that no statement is currently being processed.
`LAST_STATEMENT`	`VARCHAR`	NULL if the user has just logged in, otherwise the currently running statement or most recently completed statement.
`EXECUTION_ENGINE_PROFILING_CONFIGURATION`	`VARCHAR`	See Profiling Settings below.
`QUERY_PROFILING_CONFIGURATION`	`VARCHAR`	See Profiling Settings below.
`SESSION_PROFILING_CONFIGURATION`	`VARCHAR`	See Profiling Settings below.
`CLIENT_TYPE`	`VARCHAR`	Type of client from which the connection was made, one of the following: ADO.NET Driver ODBC Driver JDBC Driver vsql
`CLIENT_VERSION`	`VARCHAR`	Client version
`CLIENT_OS`	`VARCHAR`	Client operating system
`CLIENT_OS_USER_NAME`	`VARCHAR`	Identifies the user that logged into the database, also set for unsuccessful login attempts.
`REQUESTED_PROTOCOL`	`VARCHAR`	Communication protocol version that the ODBC client driver sends to the database server, used to support backward compatibility with earlier server versions.
`EFFECTIVE_PROTOCOL`	`VARCHAR`	Minimum protocol version supported by client and driver.

Profiling settings

The following columns show settings for different profiling categories:

EXECUTION_ENGINE_PROFILING_CONFIGURATION
QUERY_PROFILING_CONFIGURATION
SESSION_PROFILING_CONFIGURATION

These can have the following values:

Empty: No profiling is set
Session: On for current session.
Global: On by default for all sessions.
>Session, Global: On by default for all sessions, including current session.

For information about controlling profiling settings, see Enabling profiling.

Sql-Reference: DATA_COLLECTOR

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

Shows settings for all Data collector components: their current retention policy properties and other data collection statistics.

Data Collector is on by default. To turn it off, set configuration parameter EnableDataCollector to 0.

Column Name	Data Type	Description
NODE_NAME	VARCHAR	Node name on which data is stored.
COMPONENT	VARCHAR	Name of the component.
TABLE_NAME	VARCHAR	The data collector table name for which information is listed.
DESCRIPTION	VARCHAR	Short description about the component.
ACCESS_RESTRICTED	BOOLEAN	Indicates whether access to the table is restricted to the DBADMIN, PSEUDOSUPERUSER, or SYSMONITOR roles.
MEMORY_BUFFER_SIZE_KB	INTEGER	Specifies in kilobytes the maximum amount of data that is buffered in memory before moving it to disk. You can modify this value with SET_DATA_COLLECTOR_POLICY.
DISK_SIZE_KB	INTEGER	Specifies in kilobytes the maximum disk space allocated for this component's Data Collector table. If set to 0, the Data Collector retains only as much component data as it can buffer in memory, as specified by MEMORY_BUFFER_SIZE_KB. You can modify this value with SET_DATA_COLLECTOR_POLICY.
INTERVAL_SET	BOOLEAN	Boolean, specifies whether time-based retention is enabled (INTERVAL_TIME is ≥ 0).
INTERVAL_TIME	INTERVAL	INTERVAL data type that specifies how long data of a given component is retained in that component's Data Collector table. You can modify this value with SET_DATA_COLLECTOR_POLICY or SET_DATA_COLLECTOR_TIME_POLICY. For example, if you specify component TupleMoverEvents and set interval-time to an interval of two days (`'2 days'::interval`), the Data Collector table `dc_tuple_mover_events` retains records of Tuple Mover activity over the last 48 hours. Older Tuple Mover data are automatically dropped from this table. Note Setting a component's policy's interval_time property has no effect on how much data storage the Data Collector retains on disk for that component. Maximum disk storage capacity is determined by the disk_size_kb property. Setting the interval_time property only affects how long data is retained by the component's Data Collector table. For details, see Configuring data retention policies.
RECORD_TOO_BIG_ERRORS	INTEGER	Integer that increments by one each time an error is thrown because data did not fit in memory (based on the data collector retention policy).
LOST_BUFFERS	INTEGER	Number of buffers lost.
LOST_RECORDS	INTEGER	Number of records lost.
RETIRED_FILES	INTEGER	Number of retired files.
RETIRED_RECORDS	INTEGER	Number of retired records.
CURRENT_MEMORY_RECORDS	INTEGER	The current number of rows in memory.
CURRENT_DISK_RECORDS	INTEGER	The current number of rows stored on disk.
CURRENT_MEMORY_BYTES	INTEGER	Total current memory used in kilobytes.
CURRENT_DISK_BYTES	INTEGER	Total current disk space used in kilobytes.
FIRST_TIME	TIMESTAMP	Timestamp of the first record.
LAST_TIME	TIMESTAMP	Timestamp of the last record
KB_PER_DAY	FLOAT	Total kilobytes used per day.

Examples

Get the current status of resource pools:

=> SELECT * FROM data_collector WHERE component = 'ResourcePoolStatus' ORDER BY node_name;
-[ RECORD 1 ]----------+---------------------------------
node_name              | v_vmart_node0001
component              | ResourcePoolStatus
table_name             | dc_resource_pool_status
description            | Resource Pool status information
access_restricted      | t
memory_buffer_size_kb  | 64
disk_size_kb           | 25600
interval_set           | f
interval_time          | 0
record_too_big_errors  | 0
lost_buffers           | 0
lost_records           | 0
retired_files          | 385
retired_records        | 3492335
current_memory_records | 0
current_disk_records   | 30365
current_memory_bytes   | 0
current_disk_bytes     | 21936993
first_time             | 2020-08-14 11:03:28.007894-04
last_time              | 2020-08-14 11:59:41.005675-04
kb_per_day             | 548726.098227313
-[ RECORD 2 ]----------+---------------------------------
node_name              | v_vmart_node0002
component              | ResourcePoolStatus
table_name             | dc_resource_pool_status
description            | Resource Pool status information
access_restricted      | t
memory_buffer_size_kb  | 64
disk_size_kb           | 25600
interval_set           | f
interval_time          | 0
record_too_big_errors  | 0
lost_buffers           | 0
lost_records           | 0
retired_files          | 385
retired_records        | 3492335
current_memory_records | 0
current_disk_records   | 28346
current_memory_bytes   | 0
current_disk_bytes     | 20478345
first_time             | 2020-08-14 11:07:12.006484-04
last_time              | 2020-08-14 11:59:41.004825-04
kb_per_day             | 548675.811828872
-[ RECORD 3 ]----------+---------------------------------
node_name              | v_vmart_node0003
component              | ResourcePoolStatus
table_name             | dc_resource_pool_status
description            | Resource Pool status information
access_restricted      | t
memory_buffer_size_kb  | 64
disk_size_kb           | 25600
interval_set           | f
interval_time          | 0
record_too_big_errors  | 0
lost_buffers           | 0
lost_records           | 0
retired_files          | 385
retired_records        | 3492335
current_memory_records | 0
current_disk_records   | 28337
current_memory_bytes   | 0
current_disk_bytes     | 20471843
first_time             | 2020-08-14 11:07:13.008246-04
last_time              | 2020-08-14 11:59:41.006729-04
kb_per_day             | 548675.63541403

Sql-Reference: DATA_LOADER_EVENTS

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

Lists load events from all data loaders, including the file path, whether the load succeeded, and how many times it has been retried. You must own or have any privilege (EXECUTE, ALTER, or DROP) on a data loader to see its events in this table.

To prevent unbounded growth, records in this table are purged periodically. You can set the purge frequency for individual data loaders when creating or altering the loader. See CREATE DATA LOADER and ALTER DATA LOADER. The default is 14 days.

For SQS errors that precede data load, such as authorization errors or malformed SQS events, see SQS_LISTENER_ERROR_HISTORY.

Column Name	Column Type	Description
`DATA_LOADER_NAMESPACE`	VARCHAR	For Eon Mode databases, namespace of the data loader that performed this load.
`DATA_LOADER_SCHEMA`	VARCHAR	Schema for the data loader that performed this load. 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`.
`DATA_LOADER_NAME`	VARCHAR	Name of the data loader that performed this load.
`TIME_STAMP`	TIMESTAMPTZ	Time when OpenText™ Analytics Database recorded the event.
`FILE_NAME`	VARCHAR	Path that was loaded (or attempted).
`TRANSACTION_ID`	VARCHAR	Unique identifier for the transaction in which the load occurred.
`LOAD_STATUS`	VARCHAR	`OK` if the load succeeded or `FAIL` if it did not.
`ROWS_LOADED`	INTEGER	If a single file was loaded, the number of rows. If more than one file was loaded in a single batch, this value is null. For batch loads, `FILE_SIZE_BYTES` can be helpful in place of row counts.
`FAILURE_REASON`	VARCHAR	If the load failed, an explanatory message.
`RETRY_ATTEMPT`	INTEGER	0 if this was the first attempt to load the file, otherwise the number of retries including this one.
`FILE_SIZE_BYTES`	INTEGER	File size in bytes when the data loader was executed.
`BATCH_ID`	INTEGER	Identifier, unique within the transaction, for the batch this file was part of. If a file was loaded individually, this value is null.
`KAFKA_TOPIC_NAME`	VARCHAR	The name of the Kafka topic from wich the data is loaded.
`KAFKA_PARTITION_ID`	INTEGER	The partition in the Kafka topic.
`KAFKA_LATEST_OFFSET`	INTEGER	The offset where the load ends the last.
`KAFKA_LOADER_TARGET`	VARCHAR	The target table to which the Kafka data is loaded.

Sql-Reference: DATA_READS

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

Eon Mode only

Lists each storage location that a query reads in Eon Mode. If the query fetches data from multiple locations, this table provides a row for each location per node that read data. For example, a query might run on three nodes and fetch data from the depot and communal storage. In this case, the table displays six rows for the query: three rows for each node's depot read, and three for each node's communal storage read.

Note

This table is only populated in Eon Mode.

Column Name	Column Type	Description
`START_TIME`	TIMESTAMP	When OpenText™ Analytics Database started reading data from the location.
`NODE_NAME`	VARCHAR	Name of the node that fetched the data
`SESSION_ID`	VARCHAR	Unique numeric ID assigned by the Vertica 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`	INT	Unique numeric ID assigned by the Vertica catalog, which identifies the user.
`USER_NAME`	VARCHAR	Name of the user running the query.
`TRANSACTION_ID`	INT	Identifier for the transaction within the session, if any. If a session is active but no transaction has begun, TRANSACTION_ID returns NULL.
`STATEMENT_ID`	INT	Unique numeric ID for the statement that read the data. NULL indicates that no statement is currently being processed. The combination of TRANSACTION_ID and STATEMENT_ID uniquely identifies a statement within a session; these columns are useful for creating joins with other system tables.
`REQUEST_ID`	INT	ID of the data request.
`LOCATION_ID`	INT	ID of the storage location read.
`LOCATION_PATH`	VARCHAR	Path of the storage container read by the query.
`BYTES_READ`	INT	Number of bytes read by the query from this location.

Examples

=> SELECT * FROM V_MONITOR.DATA_READS WHERE TRANSACTION_ID = 45035996273707457;
-[ RECORD 1 ]--+---------------------------------------------------
start_time     | 2019-02-13 19:43:43.840836+00
node_name      | v_verticadb_node0001
session_id     | v_verticadb_node0001-11828:0x6f3
user_id        | 45035996273704962
user_name      | dbadmin
transaction_id | 45035996273707457
statement_id   | 1
request_id     | 230
location_id    | 45035996273835000
location_path  | /vertica/data/verticadb/v_verticadb_node0001_depot
bytes_read     | 329460142
-[ RECORD 2 ]--+---------------------------------------------------
start_time     | 2019-02-13 19:43:43.8421+00
node_name      | v_verticadb_node0002
session_id     | v_verticadb_node0001-11828:0x6f3
user_id        | 45035996273704962
user_name      | dbadmin
transaction_id | 45035996273707457
statement_id   | 1
request_id     | 0
location_id    | 45035996273835002
location_path  | /vertica/data/verticadb/v_verticadb_node0002_depot
bytes_read     | 329473033
-[ RECORD 3 ]--+---------------------------------------------------
start_time     | 2019-02-13 19:43:43.841845+00
node_name      | v_verticadb_node0003
session_id     | v_verticadb_node0001-11828:0x6f3
user_id        | 45035996273704962
user_name      | dbadmin
transaction_id | 45035996273707457
statement_id   | 1
request_id     | 0
location_id    | 45035996273835004
location_path  | /vertica/data/verticadb/v_verticadb_node0003_depot
bytes_read     | 329677294

Sql-Reference: DATABASE_BACKUPS

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

Lists historical information for each backup that successfully completed after running the vbr utility. This information is useful for determining whether to create a new backup before you advance the AHM. Because this system table displays historical information, its contents do not always reflect the current state of a backup repository. For example, if you delete a backup from a repository, the DATABASE_BACKUPS system table continues to display information about it.

To list existing backups, run vbr as described in Viewing backups.

Column Name	Data Type	Description
`BACKUP_TIMESTAMP`	TIMESTAMP	The timestamp of the backup.
`NODE_NAME`	VARCHAR	The name of the initiator node that performed the backup.
`SNAPSHOT_NAME`	VARCHAR	The name of the backup, as specified in the `snapshotName` parameter of the `vbr` configuration file.
`BACKUP_EPOCH`	INTEGER	The database epoch at which the backup was saved.
`NODE_COUNT`	INTEGER	The number of nodes backed up in the completed backup, and as listed in the `[Mapping`n`]` sections of the configuration file.
`OBJECTS`	VARCHAR	The name of the object(s) contained in an object-level backup. This column is empty if the record is for a full cluster backup.
`FILE_SYSTEM_TYPE`	VARCHAR	The type of file system, such as Linux.

Privileges

Superuser

Sql-Reference: DATABASE_CONNECTIONS

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

Lists the connections to other databases for importing and exporting data. See Moving Data Between Databases.

Column Name	Data Type	Description
`DATABASE`	VARCHAR	The name of the connected database
`USERNAME`	VARCHAR	The username used to create the connection
`HOST`	VARCHAR	The host name used to create the connection
`PORT`	VARCHAR	The port number used to create the connection
`ISVALID`	BOOLEAN	Whether the connection is still open and usable or not

Examples

=> CONNECT TO VERTICA vmart USER dbadmin PASSWORD '' ON '10.10.20.150',5433;
CONNECT
=> SELECT * FROM DATABASE_CONNECTIONS;
 database | username |     host     | port | isvalid
----------+----------+--------------+------+---------
 vmart    | dbadmin  | 10.10.20.150 | 5433 | t
(1 row)

Sql-Reference: DATABASE_MIGRATION_STATUS

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

Provides real-time and historical data on Enterprise-to-Eon database migration attempts.

Column Name	Data Type	Description
NODE_NAME	VARCHAR	Name of a node in the source Enterprise database.
TRANSACTION_ID	VARCHAR	Hexadecimal identifier of the migration process transaction.
PHASE	VARCHAR	A stage of database migration on a given node, one of the following, listed in order of execution: Catalog Conversion: Conversion of enterprise-mode catalog to Eon-compatible catalog. Note No data is transferred during this phase, so BYTES_TO_TRANSFER and BYTES_TRANSFERED are always set to 0. Data Transfer: Transfer of data files and library files to communal storage Catalog Transfer: Includes transfer of checkpoint and transaction log files.
STATUS	VARCHAR	Specifies status of a given phase, one of the following: RUNNING COMPLETED ABORT ABORT indicates a given migration phase was unable to complete—for example, the client disconnected, or a network outage occurred—and the migration returned with an error. In this case, call MIGRATE_ENTERPRISE_TO_EON again to restart migration. For details, see Handling Interrupted Migration.
BYTES_TO_TRANSFER	INTEGER	For each migration phase, the size of data to transfer to communal storage, set when phase status is RUNNING: Catalog Conversion: 0 Data Transfer: Size of data files and library files Catalog Transfer: Size of transaction logs
BYTES_TRANSFERRED	INTEGER	For each migration phase, the size of data transfered to communal storage. This value is updated while phase status is RUNNING, and set to the total number of bytes transferred when status is COMPLETED: Catalog Conversion: 0 Data Transfer: Size of data files and library files Catalog Transfer: Size of transaction logs
COMMUNAL_STORAGE_LOCATION	VARCHAR	URL of targeted communal storage location
START_TIME	TIMESTAMP	Demarcate the start and end of each PHASE-specified migration operation.
END_TIME

Privileges

Superuser

Examples

The following example shows data of a migration that is in progress:

=> SELECT node_name, phase, status, bytes_to_transfer, bytes_transferred, communal_storage_location FROM database_migration_status ORDER BY node_name, start_time;
     node_name    |       phase        |  status   | bytes_to_transfer | bytes_transferred | communal_storage_location
------------------+--------------------+-----------+-------------------+------------------+---------------------------
 v_vmart_node0001 | Catalog Conversion | COMPLETED |                 0 |                0 | s3://verticadbbucket/
 v_vmart_node0001 | Data Transfer      | COMPLETED |              1134 |             1134 | s3://verticadbbucket/
 v_vmart_node0001 | Catalog Transfer   | COMPLETED |              3765 |             3765 | s3://verticadbbucket/
 v_vmart_node0002 | Catalog Conversion | COMPLETED |                 0 |                0 | s3://verticadbbucket/
 v_vmart_node0002 | Data Transfer      | COMPLETED |              1140 |             1140 | s3://verticadbbucket/
 v_vmart_node0002 | Catalog Transfer   | COMPLETED |              3766 |             3766 | s3://verticadbbucket/
 v_vmart_node0003 | Catalog Conversion | COMPLETED |                 0 |                0 | s3://verticadbbucket/
 v_vmart_node0003 | Data Transfer      | RUNNING   |           5272616 |           183955 | s3://verticadbbucket/

Sql-Reference: DELETE_VECTORS

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

Holds information on deleted rows to speed up the delete process.

Column Name	Data Type	Description
NODE_NAME	VARCHAR	The name of the node storing the deleted rows.
NAMESPACE_NAME	VARCHAR	For Eon Mode databases, namespace where the deleted rows are located.
SCHEMA_NAME	VARCHAR	The name of the schema where the deleted rows are located. 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`.
PROJECTION_NAME	VARCHAR	The name of the projection where the deleted rows are located.
DV_OID	INTEGER	The unique numeric ID (OID) that identifies this delete vector.
STORAGE_OID	INTEGER	The unique numeric ID (OID) that identifies the storage container that holds the delete vector.
SAL_STORAGE_ID	VARCHAR	Unique hexadecimal numeric ID assigned by the Vertica catalog, which identifies the storage.
DELETED_ROW_COUNT	INTEGER	The number of rows deleted.
USED_BYTES	INTEGER	The number of bytes used to store the deletion.
START_EPOCH	INTEGER	The start epoch of the data in the delete vector.
END_EPOCH	INTEGER	The end epoch of the data in the delete vector.

Examples

After you delete data from a OpenText™ Analytics Database table, that data is marked for deletion. To see the data that is marked for deletion, query the DELETE_VECTORS system table.

Run PURGE to remove the delete vectors from ROS containers.

=> SELECT * FROM test1;
 number
--------
      3
     12
     33
     87
     43
     99
(6 rows)
=> DELETE FROM test1 WHERE number > 50;
 OUTPUT
--------
      2
(1 row)
=> SELECT * FROM test1;
 number
--------
     43
      3
     12
     33
(4 rows)
=> SELECT node_name, projection_name, deleted_row_count FROM DELETE_VECTORS;
    node_name     | projection_name | deleted_row_count
------------------+-----------------+-------------------
 v_vmart_node0002 | test1_b1        |                 1
 v_vmart_node0001 | test1_b1        |                 1
 v_vmart_node0001 | test1_b0        |                 1
 v_vmart_node0003 | test1_b0        |                 1
(4 rows)
=> SELECT PURGE();
...
(Table: public.test1) (Projection: public.test1_b0)
(Table: public.test1) (Projection: public.test1_b1)
...
(4 rows)

After the ancient history mark (AHM) advances:

=> SELECT * FROM DELETE_VECTORS;
 (No rows)

Sql-Reference: DEPLOY_STATUS

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

Records the history of deployed Database Designer designs and their deployment steps.

Column Name	Data Type	Description
`EVENT_TIME`	TIMESTAMP	Time when the row recorded the event.
`USER_NAME`	VARCHAR	Name of the user who deployed a design at the time OpenText™ Analytics Database recorded the session.
`DEPLOY_NAME`	VARCHAR	Name the deployment, same as the user-specified design name.
`DEPLOY_STEP`	VARCHAR	Steps in the design deployment.
`DEPLOY_STEP_STATUS`	VARCHAR	Textual status description of the current step in the deploy process.
`DEPLOY_STEP_COMPLETE_PERCENT`	FLOAT	Progress of current step in percentage (0–100).
`DEPLOY_COMPLETE_PERCENT`	FLOAT	Progress of overall deployment in percentage (0–100).
`ERROR_MESSAGE`	VARCHAR	Error or warning message during deployment.

Privileges

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

Sql-Reference: DEPLOYMENT_PROJECTION_STATEMENTS

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

Contains information about CREATE PROJECTION statements used to deploy a database design. Each row contains information about a different CREATE PROJECTION statement. The function DESIGNER_RUN_POPULATE_DESIGN_AND_DEPLOY populates this table.

Column Name	Column Type	Description
`DEPLOYMENT_ID`	INTEGER	Unique ID that Database Designer assigned to the deployment.
`DESIGN_NAME`	VARCHAR	Unique name that the user assigned to the design.
`DEPLOYMENT_PROJECTION_ID`	INTEGER	Unique ID assigned to the output projection by Database Designer.
`STATEMENT_ID`	INTEGER	Unique ID assigned to the statement type that creates the projection.
`STATEMENT`	VARCHAR	Text for the statement that creates the projection.

Sql-Reference: DEPLOYMENT_PROJECTIONS

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

Contains information about projections created and dropped during the design. Each row contains information about a different projection. Database Designer populates this table after the design is deployed.

Column Name	Column Type	Description
`deployment_id`	INTEGER	Unique ID that Database Designer assigned to the deployment.
`deployment_projection_id`	INTEGER	Unique ID that Database Designer assigned to the output projection.
`design_name`	VARCHAR	Name of the design being deployed.
`deployment_projection_name`	VARCHAR	Name that Database Designer assigned to the projection.
`anchor_table_schema`	VARCHAR	Name of the schema that contains the table the projection is based on. 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`.
`anchor_table_name`	VARCHAR	Name of the table the projection is based on.
`deployment_operation`	VARCHAR	Action being taken on the projection, for example, add or drop.
`deployment_projection_type`	VARCHAR	Indicates whether Database Designer has proposed new projections for this design (DBD) or is using the existing catalog design (CATALOG). The REENCODED suffix indicates that the projection sort order and segmentation are the same, but the projection columns have new encodings: DBD CATALOG DBD_REENCODED CATALOG_REENCODED
`deploy_weight`	INTEGER	Weight of this projection in creating the design. This field is always 0 for projections that have been dropped.
`estimated_size_on_disk`	INTEGER	Approximate size of the projection on disk, in MB.

Sql-Reference: DEPOT_EVICTIONS

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

Eon Mode only

Records data on eviction of objects from the depot.

Column Name	Data Type	Description
START_TIME	TIMESTAMP	Demarcate the start and end of each depot eviction operation.
END_TIME
NODE_NAME	VARCHAR	Name of a node where the eviction occurred.
SESSION_ID	VARCHAR	Unique numeric ID assigned by the Vertica 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	Unique numeric ID assigned by the Vertica catalog, which identifies the user.
USER_NAME	VARCHAR	The user who made changes to the depot.
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.
STATEMENT_ID	INTEGER	Unique numeric ID for the statement that caused the eviction. NULL indicates that no statement is currently being processed. The combination of TRANSACTION_ID and STATEMENT_ID uniquely identifies a statement within a session; these columns are useful for creating joins with other system tables.
REQUEST_ID	INTEGER	Unique identifier of the query request in the user session.
STORAGE_ID	VARCHAR	Unique hexadecimal numeric ID assigned by the Vertica catalog, which identifies the storage.
STORAGE_OID	INTEGER	Numeric ID assigned by the Vertica catalog, which identifies the storage.
FILE_SIZE_BYTES	INTEGER	The size of the file in bytes that was evicted.
NUMBER_HITS	INTEGER	The number of times the file was accessed.
LAST_ACCESS_TIME	TIMESTAMP	The last time the file was read.
REASON	VARCHAR	The reason the file was evicted, one of the following: CLEAR DEPOT DEPOT FILL AT STARTUP DEPOT SIZE CHANGE DROP OBJECT DROP SUBSCRIPTION EVICTION DUE TO NEW LOAD PEER TO PEER FILL QUERY
IS_PINNED	BOOLEAN	Whether the object has a pinning policy.
IS_ANTI_PINNED	BOOLEAN	Whether the object has an anti-pinning policy.

Examples

=> SELECT * FROM V_MONITOR.DEPOT_EVICTIONS LIMIT 2;
-[ RECORD 1 ]----+-------------------------------------------------
start_time       | 2019-02-20 15:32:26.765937+00
end_time         | 2019-02-20 15:32:26.766019+00
node_name        | v_verticadb_node0001
session_id       | v_verticadb_node0001-8997:0x3e
user_id          | 45035996273704962
user_name        | dbadmin
transaction_id   | 45035996273705450
statement_id     | 1
request_id       | 406
storage_id       | 0000000000000000000000000000000000a000000001fbf6
storage_oid      | 45035996273842065
file_size_bytes  | 61
number_hits      | 1
last_access_time | 2019-02-20 15:32:26.668094+00
reason           | DROP OBJECT
is_pinned        | f
-[ RECORD 2 ]----+-------------------------------------------------
start_time       | 2019-02-20 15:32:26.812803+00
end_time         | 2019-02-20 15:32:26.812866+00
node_name        | v_verticadb_node0001
session_id       | v_verticadb_node0001-8997:0x3e
user_id          | 45035996273704962
user_name        | dbadmin
transaction_id   | 45035996273705453
statement_id     | 1
request_id       | 409
storage_id       | 0000000000000000000000000000000000a000000001fbf6
storage_oid      | 45035996273842079
file_size_bytes  | 91
number_hits      | 1
last_access_time | 2019-02-20 15:32:26.770807+00
reason           | DROP OBJECT
is_pinned        | f

Sql-Reference: DEPOT_FETCH_QUEUE

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

Eon Mode only

Lists all pending depot requests for queried file data to fetch from communal storage.

Column Name	Data Type	Description
NODE_NAME	VARCHAR	Name of the node that requested the fetch.
SAL_STORAGE_ID	VARCHAR	Unique hexadecimal numeric ID assigned by the Vertica catalog, which identifies the storage.
TRANSACTION_ID	INTEGER	Identifies the transaction that contains the fetch-triggering query.
SOURCE_FILE_NAME	VARCHAR	Full path in communal storage of the file to fetch.
DESTINATION_FILE_NAME	VARCHAR	Destination path of the file to fetch.

Examples

=> \x
Expanded display is on.
=> SELECT * FROM depot_fetch_queue;
-[ RECORD 1 ]----------+-------------------------------------------------------------
node_name              | v_example_db_node0002
sal_storage_id         | 029b6fac864e1982531dcde47d00edc500d000000001d5e7
transaction_id         | 45035996273705983
source_file_name       | s3://mydata/mydb/14a/029b6fac864e1982531dcde47d00edc500d000
                              000001d5e7_0.gt
destination_file_name  | /vertica/example_db/v_example_db_node0002_depot/747/029b6fac
                              864e1982531dcde47d00edc500d000000001d5eb_0.gt
-[ RECORD 2 ]----------+-------------------------------------------------------------
node_name              | v_example_db_node0003
sal_storage_id         | 026635d69719c45e8d2d86f5a4d62c7b00b000000001d5e7
transaction_id         | 45035996273705983
source_file_name       | s3://mydata/mydb/4a5/029b6fac864e1982531dcde47d00edc500d0000
                              00001d5eb_0.gt
destination_file_name  | /vertica/example_db/v_example_db_node0002_depot/751/026635d6
                              9719c45e8d2d86f5a4d62c7b00b000000001d5e7_0.gt

Sql-Reference: DEPOT_FETCHES

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

Eon Mode only

Records data of depot fetch requests.

Note

OpenText™ Analytics Database reports all fetches to this table, including failed fetch attempts and their causes.

Column Name	Data Type	Description
START_TIME	TIMESTAMP	Demarcate the start and end of each depot fetch operation.
END_TIME
NODE_NAME	VARCHAR	Identifies the node that initiated fetch request.
TRANSACTION_ID	INTEGER	Uniquely identifies the transaction of the query that required the fetched file.
STORAGE_ID	VARCHAR	Unique hexadecimal numeric ID assigned by the database catalog to identify the storage.
STORAGE_OID	INTEGER	Numeric ID assigned by the Vertica catalog, which identifies the storage.
FILE_SIZE_BYTES	INTEGER	Fetch size in bytes.
SOURCE_FILE	VARCHAR	Source file path used, set to null if the file was fetched from a peer.
DESTINATION_FILE	VARCHAR	Destination file path
SOURCE_NODE	VARCHAR	Source node from which the file was fetched, set to one of the following: Name of the source node if file was fetched from a peer Null if file was fetched from communal storage
IS_SUCCESSFUL	BOOLEAN	Boolean, specifies whether this fetch succeeded.
REASON	VARCHAR	Reason why the fetch failed, null if IS_SUCCESSFUL is true.

Examples

=> \x
Expanded display is on.

=> SELECT * FROM DEPOT_FETCHES LIMIT 2;
-[ RECORD 1 ]----+-------------------------------------------------------------
start_time       | 2019-08-30 15:16:15.125962+00
end_time         | 2019-08-30 15:16:15.126791+00
node_name        | v_verticadb_node0001
transaction_id   | 45035996273706225
storage_id       | 0239ef74126e70db410b301610f1e5b500b0000000020d65
storage_oid      | 45035996273842065
file_size_bytes  | 53033
source_file      |
destination_file | /vertica/data/verticadb/v_verticadb_node0001_depot/957/0239e
                     f74126e70db410b301610f1e5b500b0000000020d65_0.gt
source_node      | v_verticadb_node0002
is_successful    | t
reason           |
-[ RECORD 2 ]----+-------------------------------------------------------------
start_time       | 2019-08-30 15:16:15.285208+00
end_time         | 2019-08-30 15:16:15.285949+00
node_name        | v_verticadb_node0001
transaction_id   | 45035996273706234
storage_id       | 0239ef74126e70db410b301610f1e5b500b0000000020dc7
storage_oid      | 45035996273842075
file_size_bytes  | 69640
source_file      |
destination_file | /vertica/data/verticadb/v_verticadb_node0001_depot/055/0239e
                     f74126e70db410b301610f1e5b500b0000000020dc7_0.gt
source_node      | v_verticadb_node0002
is_successful    | t
reason           |

=> select node_name,transaction_id,storage_id,is_successful,reason FROM
   depot_fetches WHERE is_successful = 'f' LIMIT 3;
-[ RECORD 1 ]--+-------------------------------------------------
node_name      | v_verticadb_node0001
transaction_id | 45035996273721070
storage_id     | 0289281ac4c1f6580b95096fab25290800b0000000027d09
is_successful  | f
reason         | Could not create space in the depot
-[ RECORD 2 ]--+-------------------------------------------------
node_name      | v_verticadb_node0001
transaction_id | 45035996273721070
storage_id     | 0289281ac4c1f6580b95096fab25290800b0000000027d15
is_successful  | f
reason         | Could not create space in the depot
-[ RECORD 3 ]--+-------------------------------------------------
node_name      | v_verticadb_node0002
transaction_id | 45035996273721070
storage_id     | 02693f1c68266e38461084a840ee42aa00c0000000027d09
is_successful  | f
reason         | Could not create space in the depot

Sql-Reference: DEPOT_FILES

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

Eon Mode only

Lists objects that are currently cached in the database depots.

Column Name	Data Type	Description
NODE_NAME	VARCHAR	Name of the depot node.
SAL_STORAGE_ID	VARCHAR	Unique hexadecimal numeric ID assigned by the Vertica catalog, which identifies the storage.
STORAGE_OID	INTEGER	Numeric ID assigned by the Vertica catalog, which identifies the storage.
COMMUNAL_FILE_PATH	VARCHAR	Communal storage path to the file. On AWS, this is an S3 URI.
DEPOT_FILE_PATH	VARCHAR	Depot path to the file.
SHARD_NAME	VARCHAR	Name of the shard this file is a part of.
STORAGE_TYPE	VARCHAR	Type of system storing this file.
NUMBER_OF_ACCESSES	INTEGER	Number of times this file has been accessed.
FILE_SIZE_BYTES	INTEGER	How large the file is in bytes.
LAST_ACCESS_TIME	TIMESTAMPTZ	When the file was last accessed.
ARRIVAL_TIME	TIMESTAMPTZ	When OpenText™ Analytics Database loaded the file into the depot.
SOURCE	VARCHAR	How the data came to be cached, one of the following: LOAD QUERY PEER TO PEER FILL DEPOT FILL AT STARTUP
IS_PINNED	BOOLEAN	Whether a pinning policy is set on the cached data.
IS_ANTI_PINNED	BOOLEAN	Whether an anti-pinning policy is set on the cached data.

Examples

=> \x
Expanded display is on.
=> SELECT * FROM depot_files LIMIT 2;

-[ RECORD 1 ]------+---------------------------------------------------------------
node_name          | v_verticadb_node0001
sal_storage_id     | 0275d4a7c99795d22948605e5940758900a000000001d1b1
storage_oid        | 45035996273842075
communal_file_path | s3://mybucket/myfolder/mydb/475/0275d4a7c99795d22948605e5940758900a000000001d1
b1/0275d4a7c99795d22948605e5940758900a000000001d1b1_
depot_file_path    | /vertica/data/verticadb/v_verticadb_node0001_depot/177/0275d4a7c99795d229486
05e5940758900a000000001d1b1/0275d4a7c99795d22948605e
shard_name         | replica
storage_type       | DFS
number_of_accesses | 0
file_size_bytes    | 456465645
last_access_time   | 2018-09-05 17:34:30.417274+00
arrival_time       | 2018-09-05 17:34:30.417274+00
source             | DEPOT FILL AT STARTUP
is_pinned          | f
-[ RECORD 2 ]------+---------------------------------------------------------------
node_name          | v_verticadb_node0001
sal_storage_id     | 0275d4a7c99795d22948605e5940758900a000000001d187
storage_oid        | 45035996273842079
communal_file_path | s3://mybucket/myfolder/mydb/664/0275d4a7c99795d22948605e5940758900a000000001d1
87/0275d4a7c99795d22948605e5940758900a000000001d187_
depot_file_path    | /vertica/data/verticadb/v_verticadb_node0001_depot/135/0275d4a7c99795d229486
05e5940758900a000000001d187/0275d4a7c99795d22948605e
shard_name         | replica
storage_type       | DFS
number_of_accesses | 0
file_size_bytes    | 40
last_access_time   | 2018-09-05 17:34:30.417244+00
arrival_time       | 2018-09-05 17:34:30.417244+00
source             | DEPOT FILL AT STARTUP
is_pinned          | f

Sql-Reference: DEPOT_PIN_POLICIES

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

Eon Mode only

Lists all objects —tables, projections, and table partitions—with depot eviction policies.

Column Name	Data Type	Description
NAMPESPACE_NAME	VARCHAR	For Eon Mode databases, object namespace.
SCHEMA_NAME	VARCHAR	Object 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`.
OBJECT_NAME	VARCHAR	Object name.
SUBCLUSTER_NAME	VARCHAR	Name of the subcluster where the pinning policy is set, null if the policy is set on all database depots.
POLICY_DETAILS	VARCHAR	Object type, one of the following: Table Projection Partition
MIN_VAL	VARCHAR	If POLICY_DETAILS is set to Partition, the range of contiguous partition keys specified by this policy.
MAX_VAL
LOCATION_LABEL	VARCHAR	Depot's storage location label.
POLICY_TYPE	VARCHAR	Policy type set on this object (PIN or ANTI-PIN), if any.

Sql-Reference: DEPOT_SIZES

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

Eon Mode only

Reports depot caching capacity on OpenText™ Analytics Database nodes.

Column Name	Data Type	Description
`NODE_NAME`	VARCHAR	The name of the node containing the depot.
`LOCATION_OID`	INTEGER	Catalog-assigned integer value that uniquely identifies the storage location storing the depot.
`LOCATION_PATH`	VARCHAR	The path where the depot is stored.
`LOCATION_LABEL`	VARCHAR	The label associated with the depot's storage location.
`MAX_SIZE_BYTES`	INTEGER	The maximum size the depot can contain, in bytes.
`CURRENT_USAGE_BYTES`	INTEGER	The current size of the depot, in bytes.

Examples

=> \x
Expanded display is on.
=> SELECT * FROM Depot_Sizes;

-[ RECORD 1 ]-------+---------------------------------------------------

node_name           | v_verticadb_node0003
location_oid        | 45035996273823200
location_path       | /vertica/data/verticadb/v_verticadb_node0003_depot
location_label      | auto-data-depot
max_size_bytes      | 0
current_usage_bytes | 0

-[ RECORD 2 ]-------+---------------------------------------------------
node_name           | v_verticadb_node0001
location_oid        | 45035996273823196
location_path       | /vertica/data/verticadb/v_verticadb_node0001_depot
location_label      | auto-data-depot
max_size_bytes      | 33686316032
current_usage_bytes | 206801871

-[ RECORD 3 ]-------+---------------------------------------------------
node_name           | v_verticadb_node0002
location_oid        | 45035996273823198
location_path       | /vertica/data/verticadb/v_verticadb_node0002_depot
location_label      | auto-data-depot
max_size_bytes      | 0
current_usage_bytes | 0

Sql-Reference: DEPOT_UPLOADS

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

Eon Mode only

Lists details about depot uploads to communal storage.

Column Name	Data Type	Description
`NODE_NAME`	VARCHAR	The name of the node on which the depot resides.
`PLAN_ID`	VARCHAR	A unique node-specific numeric ID for each plan run by the Optimizer.
`SUBMIT_TIME`	TIMESTAMP	The time the task was submitted to the uploader.
`START_TIME`	TIMESTAMP	The time the upload started.
`END_TIME`	TIMESTAMP	The time the upload ended.
`SOURCE_FILE`	VARCHAR	The source file path used.
`DESTINATION_FILE`	VARCHAR	The destination file path.
`FILE_SIZE_BYTES`	INTEGER	The size of the uploaded file, in bytes.
`MEMORY_USED_KB`	INTEGER	The size of the uploader file buffer for the task. Valid for a task with a RUNNING or COMPLETED status. For a RUNNING status, this shows the current file buffer size, (whatever the uploader is using, which may grow over time for large uploads). For a COMPLETED status, this shows the largest size used in case the buffer grew during the upload.
`STATUS`	VARCHAR	The status of the task, valid values are: COMPLETED - the task has completed QUEUED - the task is still in the queue, but haven't been picked up by the uploader. RUNNING - the task is currently running and the corresponding file is uploading.

Sql-Reference: DESIGN_QUERIES

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

Contains info about design queries for a given design. The following functions populate this table:

Column Name	Column Type	Description
`DESIGN_ID`	INTEGER	Unique id that Database Designer assigned to the design.
`DESIGN_NAME`	VARCHAR	Name that you specified for the design.
`DESIGN_QUERY_ID`	INTEGER	Unique id that Database Designer assigned to the design query.
`DESIGN_QUERY_ID_INDEX`	INTEGER	Database Designer chunks the query text if it exceeds the maximum attribute size before storing it in this table. Database Designer stored all chunks stored under the same value of DESIGN_QUERY_ID. DESIGN_QUERY_ID_INDEX keeps track of the order of the chunks, starting with 0 and ending in n, the index of the final chunk.
`QUERY_TEXT`	VARCHAR	Text of the query chunk, or the entire query text if it does not exceed the maximum attribute size.
`WEIGHT`	FLOAT	A value from 0 to 1 that indicates the importance of that query in creating the design. Assign a higher weight to queries that you run frequently so that Database Designer prioritizes those queries in creating the design. Default: 1.
`DESIGN_QUERY_SEARCH_PATH`	VARCHAR	The search path with which the query is to be parsed.
`DESIGN_QUERY_SIGNATURE`	INTEGER	Categorizes queries that affect the design that Database Designer creates in the same way. Database Designer assigns a signature to each query, weights one query for each signature group, depending on how many queries there are with that signature, and Database Designer considers that query when creating the design.

Example

Add queries to VMART_DESIGN and query the DESIGN_QUERIES table:


=> SELECT DESIGNER_ADD_DESIGN_QUERIES('VMART_DESIGN', '/tmp/examples/vmart_queries.sql','true');
 DESIGNER_ADD_DESIGN_QUERIES
-----------------------------
Number of accepted queries                      =9
Number of queries referencing non-design tables =0
Number of unsupported queries                   =0
Number of illegal queries                       =0
=> \x
Expanded display is on.
=> SELECT * FROM V_MONITOR.DESIGN.QUERIES
-[ RECORD 1 ]------------+-------------------
design_id                | 45035996273705090
design_name              | vmart_design
design_query_id          | 1
design_query_id_index    | 0
query_text               | SELECT fat_content
FROM (
SELECT DISTINCT fat_content
  FROM product_dimension
  WHERE department_description
  IN ('Dairy') ) AS food
  ORDER BY fat_content
  LIMIT 5;
weight                   | 1
design_query_search_path | v_dbd_vmart_design_vmart_design_ltt, "$user", public, v_catalog, v_monitor, v_internal
design_query_signature   | 45035996273724651

-[ RECORD 2]-------------+-------------------
design_query_id          | 2
design_query_id_index    | 0
query_text               | SELECT order_number, date_ordered
        FROM store.store_orders_fact orders
        WHERE orders.store_key IN (
        SELECT store_key
        FROM store.store_dimension
        WHERE store_state = 'MA')
        AND orders.vendor_key NOT IN (
        SELECT vendor_key
        FROM public.vendor_dimension
        WHERE vendor_state = 'MA')
        AND date_ordered < '2012-03-01';

weight                   | 1
design_query_search_path | v_dbd_vmart_design_vmart_design_ltt, "$user", public, v_catalog, v_monitor, v_internal
design_query_signature   | 45035996273724508
-[ RECORD 3]-------------+-------------------
...

Sql-Reference: DESIGN_STATUS

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

Records the progress of a running Database Designer design or history of the last Database Designer design executed by the current user.

Column Name	Data Type	Description
`EVENT_TIME`	TIMESTAMP	Time when the row recorded the event.
`USER_NAME`	VARCHAR	Name of the user who ran a design at the time OpenText™ Analytics Database recorded the session.
`DESIGN_NAME`	VARCHAR	Name of the user-specified design.
`DESIGN_PHASE`	VARCHAR	Phase of the design.
`PHASE_STEP`	VARCHAR	Substep in each design phase
`PHASE_STEP_COMPLETE_PERCENT`	FLOAT	Progress of current substep in percentage (0–100).
`PHASE_COMPLETE_PERCENT`	FLOAT	Progress of current design phase in percentage (0–100).

Privileges

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

Examples

The following example shows the content of the DESIGN_STATUS table of a complete Database Designer run:

=> SELECT event_time, design_name, design_phase, phase_complete_percent
   FROM v_monitor.design_status;
event_time          | design_name | design_phase                                   | phase_complete_percent
--------------------+-------------+------------------------------------------------+------------------------
2012-02-14 10:31:20 | design1     | Design started                                 |
2012-02-14 10:31:21 | design1     | Design in progress: Analyze statistics phase   |
2012-02-14 10:31:21 | design1     | Analyzing data statistics                      | 33.33
2012-02-14 10:31:22 | design1     | Analyzing data statistics                      | 66.67
2012-02-14 10:31:24 | design1     | Analyzing data statistics                      | 100
2012-02-14 10:31:25 | design1     | Design in progress: Query optimization phase   |
2012-02-14 10:31:25 | design1     | Optimizing query performance                   | 37.5
2012-02-14 10:31:31 | design1     | Optimizing query performance                   | 62.5
2012-02-14 10:31:36 | design1     | Optimizing query performance                   | 75
2012-02-14 10:31:39 | design1     | Optimizing query performance                   | 87.5
2012-02-14 10:31:41 | design1     | Optimizing query performance                   | 87.5
2012-02-14 10:31:42 | design1     | Design in progress: Storage optimization phase |
2012-02-14 10:31:44 | design1     | Optimizing storage footprint                   | 4.17
2012-02-14 10:31:44 | design1     | Optimizing storage footprint                   | 16.67
2012-02-14 10:32:04 | design1     | Optimizing storage footprint                   | 29.17
2012-02-14 10:32:04 | design1     | Optimizing storage footprint                   | 31.25
2012-02-14 10:32:05 | design1     | Optimizing storage footprint                   | 33.33
2012-02-14 10:32:05 | design1     | Optimizing storage footprint                   | 35.42
2012-02-14 10:32:05 | design1     | Optimizing storage footprint                   | 37.5
2012-02-14 10:32:05 | design1     | Optimizing storage footprint                   | 62.5
2012-02-14 10:32:39 | design1     | Optimizing storage footprint                   | 87.5
2012-02-14 10:32:39 | design1     | Optimizing storage footprint                   | 87.5
2012-02-14 10:32:41 | design1     | Optimizing storage footprint                   | 100
2012-02-14 10:33:12 | design1     | Design completed successfully                  |
(24 rows)

Sql-Reference: DESIGN_TABLES

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

Contains information about all the design tables for all the designs for which you are the owner. Each row contains information about a different design table. OpenText™ Analytics Database creates this table when you run DESIGNER_CREATE_DESIGN.

Column Name	Column Type	Description
`DESIGN_NAME`	VARCHAR	Unique name that the user specified for the design.
`DESIGN_TABLE_ID`	INTEGER	Unique ID that Database Designer assigned to the design table.
`TABLE_SCHEMA`	VARCHAR	Name of the schema that contains the design 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	System object identifier (OID) assigned to the design table.
`TABLE_NAME`	VARCHAR	Name of the design table.

Example

Add all the tables from the VMart database to the design VMART_DESIGN. This operation populates the DESIGN_TABLES table:


=> SELECT DESIGNER_ADD_DESIGN_TABLES('VMART_DESIGN','online_sales.*');
DESIGNER_ADD_DESIGN_TABLES
----------------------------
 3
(1 row)
=> SELECT DESIGNER_ADD_DESIGN_TABLES('VMART_DESIGN','public.*');
DESIGNER_ADD_DESIGN_TABLES
----------------------------
 9
(1 row)
=> SELECT DESIGNER_ADD_DESIGN_TABLES('VMART_DESIGN','store.*');
DESIGNER_ADD_DESIGN_TABLES
----------------------------
 3
(1 row)
=> SELECT * FROM DESIGN_TABLES;
design_name  | design_table_id | table_schema |     table_id      |      table_name
-------------+-----------------+--------------+-------------------+-----------------------
VMART_DESIGN |               1 | online_sales | 45035996373718754 | online_page_dimension
VMART_DESIGN |               2 | online_sales | 45035996373718758 | call_center_dimension
VMART_DESIGN |               3 | online_sales | 45035996373718762 | online_sales_fact
VMART_DESIGN |               4 | public       | 45035996373718766 | customer_dimension
VMART_DESIGN |               5 | public       | 45035996373718770 | product_dimension
VMART_DESIGN |               6 | public       | 45035996373718774 | promotion_dimension
VMART_DESIGN |               7 | public       | 45035996373718778 | date_dimension
VMART_DESIGN |               8 | public       | 45035996373718782 | vendor_dimension
VMART_DESIGN |               9 | public       | 45035996373718786 | employee_dimension
VMART_DESIGN |              10 | public       | 45035996373718822 | shipping_dimension
VMART_DESIGN |              11 | public       | 45035996373718826 | warehouse_dimension
VMART_DESIGN |              12 | public       | 45035996373718830 | inventory_face
VMART_DESIGN |              13 | store        | 45035996373718794 | store_dimension
VMART_DESIGN |              14 | store        | 45035996373718798 | store_sales_fact
VMART_DESIGN |              15 | store        | 45035996373718812 | store_orders_fact
        (15 rows)

Sql-Reference: DESIGNS

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

Contains information about a Database Designer design. After you create a design and specify certain parameters for Database Designer, DESIGNER_CREATE_DESIGN creates this table in the V_MONITOR schema.

Column Name	Column Type	Description
`DESIGN_ID`	INTEGER	Unique ID that Database Designer assigns to this design.
`DESIGN_NAME`	VARCHAR	Name that the user specifies for the design.
`KSAFETY_LEVEL`	INTEGER	K-safety level for the design. Database Designer assigns a K-safety value of 0 for clusters with 1 or 2 nodes, and assigns a value of 1 for clusters with 3 or more nodes.
`OPTIMIZATION_OBJECTIVE`	VARCHAR	Name of the optimization objective for the design. Valid values are: `QUERY` `LOAD` `BALANCED` (default)
`DESIGN_TYPE`	VARCHAR	Name of the design type. Valid values are: `COMPREHENSIVE` (default) `INCREMENTAL`
`PROPOSE_SUPER_FIRST`	BOOLEAN	Specifies to propose superprojections before projections, by default `f`. If `DESIGN_MODE` is `COMPREHENSIVE`, this field has no impact.
`DESIGN_AVAILABLE`	BOOLEAN	`t` if the design is currently available, otherwise, `f` (default).
`COLLECTED_STATISTICS`	BOOLEAN	`t` if statistics are to be collected when creating the design, otherwise, `f` (default).
`POPULATE_DESIGN_TABLES_FROM_QUERIES`	BOOLEAN	`t` if you want to populate the design tables from the design queries, otherwise, `f` (default).
`ENCODING_DESIGN`	BOOLEAN	`t` if the design is an encoding optimization design on pre-existing projections, otherwise, `f` (default).
`DEPLOYMENT_PARALLELISM`	INTEGER	Number of tables to be deployed in parallel when the design is complete. Default: 0
`UNSEGMENTED_PROJECTIONS`	BOOLEAN	`t` if you specify unsegmented projections, otherwise, `f` (default).
`ANALYZE_CORRELATIONS_MODE`	INTEGER	Specifies how Database Designer should handle existing column correlations in a design and whether or not Database Designer should reanalyze existing column correlations. 0: (default) Ignore column correlations when creating the design. 1: Consider the existing correlations in the tables when creating the design. 2: Analyze column correlations if not previously performed, and consider the column correlations when creating the design. 3: Analyze all column correlations in the tables and consider them when creating the design, even if they have been analyzed previously.

Sql-Reference: DIRECTED_QUERY_STATUS

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

Returns information about executions of directed queries.

Column Name	Data Type	Description
NODE_NAME	VARCHAR	Node on which the directed query ran.
OID	INTEGER	Unique numeric ID assigned by the OpenText™ Analytics Database catalog, which identifies the specific directed query.
QUERY_NAME	VARCHAR	Directed query's unique identifier, used by statements such as ACTIVATE DIRECTED QUERY.
DIGEST	INTEGER	Hash of the saved query plan data, used by the optimizer to map identical input queries to the same active directed query.
HITS	INTEGER	Number of times this query has been executed since the last reset. Use CLEAR_DIRECTED_QUERY_USAGE to reset this counter to 0.

Privileges

Superuser

Sql-Reference: DISK_QUOTA_USAGES

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

Provides information about schemas and tables that have disk quotas. Schemas and tables without quotas are not included.

Column Name	Data Type	Description
OBJECT_OID	INTEGER	Unique identifier for a schema or table.
OBJECT_NAME	VARCHAR	Name of the schema or table. Table names include the schema prefix.
IS_SCHEMA	BOOLEAN	Whether the object is a schema. If false, the object is a table.
TOTAL_DISK_USAGE_IN_BYTES	INTEGER	Current usage of the object. For information about what is counted, see Disk quotas.
DISK_QUOTA_IN_BYTES	INTEGER	Current quota for the object.

Examples

=> SELECT * FROM DISK_QUOTA_USAGES;
    object_oid     | object_name | is_schema | total_disk_usage_in_bytes | disk_quota_in_bytes
-------------------+-------------+-----------+---------------------+---------------------
 45035996273705100 | s           | t         |                 307 |               10240
 45035996273705104 | public.t    | f         |                 614 |                1024
 45035996273705108 | s.t         | f         |                 307 |                2048
(3 rows)

Sql-Reference: DISK_RESOURCE_REJECTIONS

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

Returns requests for resources that are rejected due to disk space shortages. Output is aggregated by both RESOURCE_TYPE and REJECTED_REASON to provide more comprehensive information.

Column Name	Data Type	Description
`NODE_NAME`	VARCHAR	The node name for which information is listed.
`RESOURCE_TYPE`	VARCHAR	The resource request requester (example: Temp files).
`REJECTED_REASON`	VARCHAR	One of the following: `Insufficient disk space` `Failed volume`
`REJECTED_COUNT`	INTEGER	Number of times this `REJECTED_REASON` has been given for this `RESOURCE_TYPE`.
`FIRST_REJECTED_TIMESTAMP`	TIMESTAMP	The time of the first rejection for this `REJECTED_REASON` and RESOURCE_TYPE.
`LAST_REJECTED_TIMESTAMP`	TIMESTAMP	The time of the most recent rejection for this `REJECTED_REASON` and `RESOURCE_TYPE`.
`LAST_REJECTED_VALUE`	INTEGER	The value of the most recent rejection for this `REJECTED_REASON` and `RESOURCE_TYPE`.

Sql-Reference: DISK_STORAGE

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

Returns the amount of disk storage used by the database on each node. Each node can have one or more storage locations, and the locations can be on different disks with separate properties, such as free space, used space, and block size. The information in this system table is useful in determining where data files reside.

All returned values for this system table are in the context of the file system of the host operating system, and are not specific to OpenText™ Analytics Database-specific space.

The storage usage annotation called CATALOG indicates that the location is used to store the catalog. Each CATALOG location is specified only when creating a new database. You cannot add a CATALOG location annotation using CREATE LOCATION, nor remove an existing CATALOG annotation.

Storage location performance

The performance of a storage location is measured with two values:

Throughput in MB/sec
Latency in seeks/sec

These two values are converted to a single number (Speed) with the following formula:

read-time = (1/throughput) + (1/latency)

read-time: Time to read 1MB of data
1/throughput: Time to read 1MB of data
1/latency: Time to seek to the data.

A disk is faster than another disk if its read-time is less.

Column Name	Data Type	Description
NODE_NAME	VARCHAR	Node name for which information is listed.
STORAGE_PATH	VARCHAR	Path where the storage location is mounted.
STORAGE_USAGE	VARCHAR	Type of information stored in the location, one of the following: `DATA`: Only data is stored in the location. `TEMP`: Only temporary files that are created during loads or queries are stored in the location. `DATA,TEMP`: Both types of files are stored in the location. `USER`: The storage location can be used by non-dbadmin users, who are granted access to the storage location `CATALOG`: The area is used for the database catalog. This usage is set internally and cannot be removed or changed.
RANK	INTEGER	Integer rank assigned to the storage location based on its performance. Ranks are used to create a storage locations on which projections, columns, and partitions are stored on different disks based on predicted or measured access patterns. See Managing storage locations.
THROUGHPUT	INTEGER	Integer that measures a storage location's performance in MB/sec. `1/``throughput` is the time taken to read 1MB of data.
LATENCY	INTEGER	Integer that measures a storage location's performance in seeks/sec. `1/``latency` is the time taken to seek to the data.
STORAGE_STATUS	VARCHAR	Status of the storage location, one of the following: `active` `retired`
DISK_BLOCK_SIZE_BYTES	INTEGER	Block size of the disk in bytes
DISK_SPACE_USED_BLOCKS	INTEGER	Number of disk blocks in use
DISK_SPACE_USED_MB	INTEGER	Number of megabytes of disk storage in use
DISK_SPACE_FREE_BLOCKS	INTEGER	Number of free disk blocks available
DISK_SPACE_FREE_MB	INTEGER	Number of megabytes of free storage available
DISK_SPACE_FREE_PERCENT	VARCHAR	Percentage of free disk space remaining

Sql-Reference: DRAINING_STATUS

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

Returns the draining status of each node in a database. The table also provides aggregate user session counts and information about the oldest user session connected to each node. For more information about the user sessions connected to a database, see SESSIONS.

Note

If you aren't a superuser, the OLDEST_SESSION columns contain only information about sessions for which you have privileges. Unprivileged users do not see session details, but they do see the node draining status and the user session aggregate count.

Column Name	Data Type	Description
`NODE_NAME`	VARCHAR	Name of the node for which information is listed.
`SUBCLUSTER_NAME`	VARCHAR	Name of the subcluster that contains the node.
`IS_DRAINING`	BOOLEAN	True if the node is draining; otherwise, false.
`COUNT_CLIENT_USER_SESSIONS`	INTEGER	Number of user client sessions connected to the node.
`OLDEST_SESSION_USER`	VARCHAR	Name of the user with the oldest live session connected to the node. NULL if no users are connected.
`OLDEST_SESSION_ID`	VARCHAR	Identifier associated with `OLDEST_SESSION_USER`. This is required to close or interrupt a session. NULL if no users are connected.
`OLDEST_SESSION_LOGIN_TIMESTAMP`	TIMESTAMP	Date and time the `OLDEST_SESSION_USER` logged into the database. NULL if no users are connected.

Sql-Reference: ERROR_MESSAGES

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

Lists system error messages and warnings OpenText™ Analytics Database encounters while processing queries. Some errors occur when no transaction is in progress, so the transaction identifier or statement identifier columns might return NULL.

Column Name	Data Type	Description
`EVENT_TIMESTAMP`	TIMESTAMPTZ	Time when the row recorded the event
`NODE_NAME`	VARCHAR	Name of the node that is reporting the requested information
`USER_ID`	INTEGER	Identifier of the user who received the error message
`USER_NAME`	VARCHAR	Name of the user who received the error message when the database recorded the session
`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.
`REQUEST_ID`	INTEGER	Unique identifier of the query request in the user session
`TRANSACTION_ID`	INTEGER	Identifier for the transaction within the session, if any; otherwise `NULL`
`STATEMENT_ID`	INTEGER	Unique numeric ID for the currently-running statement. NULL indicates that no statement is currently being processed. The combination of TRANSACTION_ID, STATEMENT_ID, and REQUEST_ID uniquely identifies a statement within a session.
`ERROR_LEVEL`	VARCHAR	Severity of the error, one of the following: LOG INFO NOTICE WARNING ERROR ROLLBACK INTERNAL FATAL PANIC
`ERROR_CODE`	INTEGER	Error code that the database reports
`MESSAGE`	VARCHAR	Textual output of the error message
`DETAIL`	VARCHAR	Additional information about the error message, in greater detail
`HINT`	VARCHAR	Actionable hint about the error. For example: `HINT: Set the locale in this session to en_US@collation=binary using the command "\locale en_US@collation=binary"`

Privileges

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

Sql-Reference: EVENT_CONFIGURATIONS

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

Monitors the configuration of events.

Column Name	Data Type	Description
`EVENT_ID`	VARCHAR	The name of the event.
`EVENT_DELIVERY_CHANNELS`	VARCHAR	The delivery channel on which the event occurred.

Sql-Reference: EXECUTION_ENGINE_PROFILES

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

Provides profiling information about runtime query execution. The hierarchy of IDs, from highest level to actual execution, is:

PATH_ID
BASEPLAN_ID
LOCALPLAN_ID
OPERATOR_ID

Counters (output from the COUNTER_NAME column) are collected for each actual Execution Engine (EE) operator instance.

The following columns combine to form a unique key:

TRANSACTION_ID
STATEMENT_ID
NODE_NAME
OPERATOR_ID
COUNTER_NAME
COUNTER_TAG

Column Name	Data Type	Description
`NODE_NAME`	VARCHAR	Node name for which information is listed.
`USER_ID`	INTEGER	Unique numeric ID assigned by the OpenText™ Analytics Database catalog, which identifies the user.
`USER_NAME`	VARCHAR	User name for which query profile information is listed.
`SESSION_ID`	VARCHAR	Identifier of 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.
`TRANSACTION_ID`	INTEGER	Identifier for the transaction within the session if any; otherwise `NULL`.
`STATEMENT_ID`	INTEGER	Unique numeric ID for the currently-running statement. `NULL` indicates that no statement is currently being processed.
`OPERATOR_NAME`	VARCHAR	Name of the Execution Engine (EE) component; for example, `NetworkSend`.
`OPERATOR_ID`	INTEGER	Identifier assigned by the EE operator instance that performs the work. `OPERATOR_ID` is different from `LOCALPLAN_ID` because each logical operator, such as `Scan`, may be executed by multiple threads concurrently. Each thread operates on a different operator instance, which has its own ID.
`BASEPLAN_ID`	INTEGER	Assigned by the optimizer on the initiator to EE operators in the original base (EXPLAIN) plan. Each EE operator in the base plan gets a unique ID.
`PATH_ID`	INTEGER	Identifier that the database assigns to a query operation or path; for example to a logical grouping operation that might be performed by multiple execution engine operators. For each path, the same PATH ID is shared between the query plan (using EXPLAIN output) and in error messages that refer to joins.
`LOCALPLAN_ID`	INTEGER	Identifier assigned by each local executor while preparing for plan execution (local planning). Some operators in the base plan, such as the `Root` operator, which is connected to the client, do not run on all nodes. Similarly, certain operators, such as `ExprEval`, are added and removed during local planning due to implementation details.
`ACTIVITY_ID`	INTEGER	Identifier of the plan activity.
`RESOURCE_ID`	INTEGER	Identifier of the plan resource.
`COUNTER_NAME`	VARCHAR	Name of the counter (see Counter Names below). The counter counts events for one statement.
`COUNTER_TAG`	VARCHAR	String that uniquely identifies the counter for operators that might need to distinguish between different instances. For example, `COUNTER_TAG` is used to identify to which of the node bytes are being sent to or received from the `NetworkSend` operator.
`COUNTER_VALUE`	INTEGER	Value of the counter.
`IS_EXECUTING`	BOOLEAN	Indicates whether the profile is active or completed.

Privileges

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

Counter names

The value of COUNTER_NAME can be any of the following:

active threads

A counter of the LoadUnion operator, indicates the number of input threads (Load operators) that are currently processing input.

blocks analyzed by SIPs expression

Number of data blocks (for scan operations) or files (for load operations) analyzed by SIPS expression.

blocks filtered by SIPs expression

Number of data blocks (for scan operations) or files (for load operations) filtered by SIPS expression.

blocks filtered by SIPs value lists

Number of data blocks (for scan operations) or files (for load operations) filtered by SIPS sorted value lists.

buffers spilled

[NetworkSend] Buffers spilled to disk by NetworkSend.

bytes read from disk

[Scan] Amount of data read (locally or remotely) from ROS containers on disk.

bytes read from disk cache

[Scan] Amount of data read from cache.

bytes received

Number of bytes received over the network for query execution.

bytes sent

[NetworkSend] Size of data after encoding and compression sent over the network (actual network bytes).

bytes spilled

[NetworkSend] Bytes spilled to disk by NetworkSend.

bytes total

[SendFiles] (recover-by-container plan): Total number of bytes to send/receive.

cached storages cumulative size (bytes)

[StorageMerge] Total amount of temp space used by operator for caching.

cached storages current size (bytes)

[StorageMerge] Current amount of temp space used for caching.

cached storages peak size (bytes)

[StorageMerge] Peak amount of temp space an operator used for caching.

clock time (µs)

Real-time clock time spent processing the query, in microseconds.

clock time (µs) of UDChunker

Real-time clock time spent in the UDChunker phase of a load operation, in microseconds. Use the COUNTER_TAG column to distinguish among load sources.

clock time (µs) of UDFilter(s)

Real-time clock time spent in all UDFilter phases of a load operation, in microseconds. Use the COUNTER_TAG column to distinguish among load sources.

clock time (µs) of UDParser

Real-time clock time spent in the UDParser phase of a load operation, in microseconds. Use the COUNTER_TAG column to distinguish among load sources.

clock time (µs) of UDSource

Real-time clock time spent in the UDSource phase of a load operation, in microseconds. Use the COUNTER_TAG column to distinguish among load sources.

completed merge phases

Number of merge phases already completed by an LSort or DataTarget operator. Compare to the total merge phases. Variants on this value include join inner completed merge phases.

cumulative size of raw temp data (bytes)

Total amount of temporary data the operator has written to files. Compare to cumulative size of temp files (bytes) to understand impact of encoding and compression in an externalizing operator. Variants on this value include join inner cumulative size of raw temp files (bytes).

cumulative size of temp files (bytes)

For externalizing operators only, the total number of encoded and compressed temp data the operator has written to files. A sort operator might go through multiple merge phases, where at each pass sorted chunks of data are merged into fewer chunks. This counter remembers the cumulative size of all temp files past and present. Variants on this value include join inner cumulative size of temp files (bytes).

current allocated rid memory (bytes)

Per-rid memory tracking: current allocation amount under this rid.

current file handles

Number of files open.

current memory allocations (count)

Number of actual allocator calls made.

current memory capacity (bytes)

Amount of system memory held, which includes chunks that are only partially consumed.

current memory overhead (bytes)

Memory consumed, for example, by debug headers. (Normally no overhead.)

current memory padding (bytes)

Memory padding for free list tiers (2^n bytes).

current memory requested (bytes)

Memory actually requested by the caller.

current size of temp files (bytes)

For externalizing operators only, the current size of the encoded and compressed temp data that the operator has written to files. Variants on this value include join inner current size of temp files (bytes).

current threads

Unused.

current unbalanced memory allocations (count)

current unbalanced memory capacity (bytes)

current unbalanced memory overhead (bytes)

current unbalanced memory requested (bytes)

Pooled version of "current memory XXX" counters.

distinct value estimation time (µs)

[Analyze Statistics] Time (in microcseconds) spent to estimate number of distinct values from the sample after data is read off disk and into the statistical sample.

encoded bytes received

[NetworkRecv] Size of received data after decompressed (but still encoded) received over the network.

encoded bytes sent

[NetworkSend] Size of data sent over the network after encoding.

end time

Time (timestamp) when the database stopped processing the operation

estimated rows produced

Number of rows that the optimizer estimated would be produced. See rows produced for the actual number of rows that are produced.

exceptions cumulative size of raw temp data (bytes)

exceptions rows cumulative size of temp files (bytes)

exceptions rows current size of temp files (bytes)

Counters that store the total or current size of exception data.

execution time (µs)

CPU clock time spent processing the query, in microseconds.

fast aggregated rows

Number of rows being processed by fast aggregations in the hash groupby operator (no group/aggregation).

files completed

Relevant only to SendFiles/RecvFiles operators (that is, recover-by-container plan) number of files sent/received.

files total

Relevant only to SendFiles/RecvFiles operators (that is, recover-by-container plan) total number of files to send/receive.

Hadoop FS bytes read through webhdfs

[Scan, Load] Number of bytes read from a webhdfs source.

Hadoop FS bytes written through webhdfs

[DataTarget] Number of bytes written to webhdfs storage.

Hadoop FS hdfs:// operations that used webhdfs calls

[Scan, Load, DataTarget] Number of times the database opened a file with an hdfs:// URL and used the webhdfs protocol

Hadoop FS read operations through webhdfs failure count

[Scan, Load] Number of times a webhdfs source encountered an error and gave up

Hadoop FS read operations through webhdfs retry count

[Scan, Load] Number of times a webhdfs source encountered an error and retried

Hadoop FS write operations through webhdfs failure count

[DataTarget] Number of times a webhdfs write encountered an error and gave up

Hadoop FS write operations through webhdfs retry count

[DataTarget] Number of times a webhdfs write encountered an error and retried

histogram creation time(µs)

[Analyze Statistics] Time spent estimating the number of distinct values from the sample after data is read off disk and into the statistical sample.

initialization time (µs)

Time in microseconds spent initializing an operator during the CompilePlan step of query processing. For example, initialization time could include the time spent compiling expressions and gathering resources.

input queue wait (µs)

Time in microseconds that an operator spends waiting for upstream operators.

input rows

Actual number of rows that were read into the operator.

input size (bytes)

Total number of bytes of the Load operator's input source, where NULL is unknown (read from FIFO).

inputs processed

Number of sources processed by a Load operator.

intermediate rows to process

Number of rows to process in a phase as determined by a sort or GROUP BY (HASH).

join inner clock time (µs)

Real clock time spent on processing the inner input of the join operator.

join inner completed mergephases

join inner cumulative size of raw temp data (bytes)

join inner cumulative size of temp files (bytes)

join inner current size of temp files (bytes)

See the completed merge phases counter.

join inner execution time (µs)

The CPU clock time spent on processing the inner input of the join operator.

join inner hash table building time (µs)

Time spent for building the hash table for the inner input of the join operator.

join inner hash table collisions

Number of hash table collisions that occurred when building the hash table for the inner input of the join operator.

join inner hash table entries

Number of hash table entries for the inner input of the join operator.

join inner total merge phases

See the completed merge phases counter.

join outer clock time (µs)

Real clock time spent on processing the outer input of the join operator (including doing the join).

join outer execution time (µs)

CPU clock time spent on processing the outer input of the join operator (including doing the join).

max sample size (rows)

[Analyze Statistics] Maximum number of rows that will be stored in the statistical sample.

memory reserved (bytes)

Memory reserved by this operator. Deprecated.

network wait (µs)

[NetworkSend, NetworkRecv] Time in microseconds spent waiting on the network.

number of bytes read from persistent storage

Estimated number of bytes read from persistent storage to process this query.

number of bytes read from depot storage

Estimated number of bytes read from the depot to process this query.

number of cancel requests received

Number of cancel requests received (per operator) when cancelling a call to the execution engine.

number of invocations

Number of times a UDSF function was invoked.

number of storage containers opened

[Scan] Number of containers opened by the operator, at least 1. If the scan operator switches containers, this counter increases accordingly. See Local caching of storage containers for details.

output queue wait (µs)

Time in microseconds that an operator spends waiting for the output buffer to be consumed by a downstream operator.

peak allocated rid memory (bytes)

Per-rid memory tracking: peak allocation amount under this rid.

peak cooperating threads

Peak number of threads which parsed (in parallel) a single load source, using "cooperative parse." counter_tag indicates the source when joining with dc_load_events.

peak file handles

peak memory allocations (count)

peak memory capacity (bytes)

peak memory overhead (bytes)

peak memory padding (bytes)

peak memory requested (bytes)

peak temp space

peak threads

peak unbalanced memory allocations (count)

peak unbalanced memory capacity (bytes)

peak unbalanced memory overhead (bytes)

peak unbalanced memory padding (bytes)

peak unbalanced memory requested (bytes)

Peak value of the corresponding "current XXX" counters.

portion offset

Offset value of a portion descriptor in an apportioned load. counter_tag indicates the source when joining with dc_load_events.

portion size

Size value of a portion descriptor in an apportioned load. counter_tag indicates the source when joining with dc_load_events.

producer stall (µs)

[NetworkSend] Time in microseconds spent by NetworkSend when stalled waiting for network buffers to clear.

producer wait (µs)

[NetworkSend] Time in microseconds spent by the input operator making rows to send.

read (bytes)

Number of bytes read from the input source by the Load operator.

receive time (µs)

Time in microseconds that a Recv operator spends reading data from its socket.

rejected data cumulative size of raw temp data (bytes)

rejected data cumulative size of temp files (bytes)

rejected data current sizeof temp files (bytes)

rejected rows cumulative size of raw temp data (bytes)

rejected rows cumulative size of temp files (bytes)

rejected rows current size of temp files (bytes)

Counters that store total or current size of rejected row numbers. Are variants of:

cumulative size of raw temp data (bytes)

cumulative size of temp files (bytes)

current size of temp files (bytes)

reserved rid memory (bytes)

Per-rid memory tracking: total memory reservation under this rid.

rle rows produced

Number of physical tuples produced by an operator. Complements the rows produced counter, which shows the number of logical rows produced by an operator. For example, if a value occurs 1000 rows consecutively and is RLE encoded, it counts as 1000 rows produced not only 1 rle rows produced.

ROS blocks bounded

[DataTarget] Number of ROS blocks created, due to boundary alignment with RLE prefix columns, when an EE DataTarget operator is writing to ROS containers.

ROS blocks encoded

[DataTarget] Number of ROS blocks created when an EE DataTarget operator is writing to ROS containers.

ROS bytes written

[DataTarget] Number of bytes written to disk when an EE DataTarget operator is writing to ROS containers.

rows added by predicate analysis

Number of rows in the query results that were added without individual evaluation, based on the predicate and range of possible results in a block.

rows filtered by SIPs expression

Number of rows filtered by the SIPS expression from the Scan operator.

rows filtered by query predicate

Number of rows excluded from query results because they failed a condition (predicate), for example in a WHERE clause.

rows in sample

[Analyze Statistics] Actual number of rows that will be stored in the statistical sample.

rows output by sort

[DataTarget] Number of rows sorted when an EE DataTarget operator is writing to ROS containers.

rows processed

[DataSource] Number of rows processed when an EE DataSource operator is reading from ROS containers.

rows processed by SIPs expression

Number of rows processed by the SIPS expression in the Scan operator.

rows produced

Number of logical rows produced by an operator. See also the rle rows produced counter.

rows pruned by query predicates

Number of rows discarded from query results because, based on predicates and value ranges, no row in the block could satisfy the predicate.

rows pruned by valindex

[DataSource] Number of rows it skips direct scanning with help of valindex when an EE DataSource operator is writing to ROS containers. This counter's value is not greater than "rows processed" counter.

rows read in sort

See the counter total rows read in sort.

rows received

[NetworkRecv] Number of received sent over the network.

rows rejected

Number of rows rejected by the Load operator.

rows sent

[NetworkSend] Number of rows sent over the network.

rows to process

Total number of rows to be processed in a phase, based upon the number of table accesses. Compare to the counter, rows processed. Divide the rows processed value by the rows to process value for percent completion.

rows written in join sort

Total number of rows being read out of the sort facility in Join.

rows written in sort

Number of rows read out of the sort by the SortManager. This counter and the counter total rows read from sort are typically equal.

send time (µs)

Time in microseconds that a Send operator spends writing data to its socket.

start time

Time (timestamp) when the database started to process the operation.

total merge phases

Number of merge phases an LSort or DataTarget operator must complete to finish sorting its data. NULL until the operator can compute this value (all data must first be ingested by the operator). Variants on this value include join inner total merge phases.

total rows read in join sort

Total number of rows being put into the sort facility in Join.

total rows read in sort total

Total number of rows ingested into the sort by the SortManager. This counter and the counter rows written in sort are typically equal.

total rows written in sort

See the counter, rows written in sort.

total sources

Total number of distinct input sources processed in a load.

unpacked (bytes)

Number of bytes produced by a compressed source in a load (for example, for a gzip file, the size of the file when decompressed).

wait clock time (µs)

StorageUnion wait time in microseconds.

written rows

[DataTarget] Number of rows written when an EE DataTarget operator writes to ROS containers

Examples

The two queries below show the contents of the EXECUTION_ENGINE_PROFILES table:

=> SELECT operator_name, operator_id, counter_name, counter_value
    FROM EXECUTION_ENGINE_PROFILES WHERE operator_name = 'Scan'
    ORDER BY counter_value DESC;
 operator_name | operator_id | counter_name |  counter_value
---------------+-------------+--------------+------------------
 Scan          |          20 | end time     | 1559929719983785
 Scan          |          20 | start time   | 1559929719983737
 Scan          |          18 | end time     | 1559929719983358
 Scan          |          18 | start time   | 1559929718069860
 Scan          |          16 | end time     | 1559929718069319
 Scan          |          16 | start time   | 1559929718069188
 Scan          |          14 | end time     | 1559929718068611
 Scan          |          18 | end time     | 1559929717579145
 Scan          |          18 | start time   | 1559929717579083
 Scan          |          16 | end time     | 1559929717578509
 Scan          |          18 | end time     | 1559929717379346
 Scan          |          18 | start time   | 1559929717379307
 Scan          |          16 | end time     | 1559929717378879
 Scan          |          16 | start time   | 1559929716894312
 Scan          |          14 | end time     | 1559929716893599
 Scan          |          14 | start time   | 1559929716893501
 Scan          |          12 | end time     | 1559929716892721
 Scan          |          16 | start time   | 1559929716666110
...

=> SELECT DISTINCT counter_name FROM execution_engine_profiles;
                    counter_name
-----------------------------------------------------
 reserved rid memory (bytes)
 rows filtered by SIPs expression
 rows output by sort
 chunk rows scanned squared
 join inner execution time (us)
 current unbalanced memory requested (bytes)
 clock time (us)
 join outer clock time (us)
 exception handling execution time (us)
 peak memory capacity (bytes)
 bytes received
 peak memory requested (bytes)
 send time (us)
 ROS blocks encoded
 current size of temp files (bytes)
 peak memory allocations (count)
 current unbalanced memory overhead (bytes)
 rows segmented
...

The following query includes the path_id column, which links the path that the query optimizer takes (via the EXPLAIN command's textual output) with join error messages.

=> SELECT operator_name, path_id, counter_name, counter_value FROM execution_engine_profiles where operator_name = 'Join';
 operator_name | path_id |                    counter_name                     |  counter_value
---------------+---------+-----------------------------------------------------+------------------
 Join          |      64 | current memory allocations (count)                  |                0
 Join          |      64 | peak memory allocations (count)                     |               57
 Join          |      64 | current memory requested (bytes)                    |                0
 Join          |      64 | peak memory requested (bytes)                       |          1698240
 Join          |      64 | current memory overhead (bytes)                     |                0
 Join          |      64 | peak memory overhead (bytes)                        |                0
 Join          |      64 | current memory padding (bytes)                      |                0
 Join          |      64 | peak memory padding (bytes)                         |           249840
 Join          |      64 | current memory capacity (bytes)                     |                0
 Join          |      64 | peak memory capacity (bytes)                        |           294912
 Join          |      64 | current unbalanced memory allocations (count)       |              145
 Join          |      64 | peak unbalanced memory allocations (count)          |              146
 Join          |      64 | current unbalanced memory requested (bytes)         |           116506
 Join          |      64 | peak unbalanced memory requested (bytes)            |          1059111
 Join          |      64 | current unbalanced memory overhead (bytes)          |             3120
 Join          |      64 | peak unbalanced memory overhead (bytes)             |             3120
...

Sql-Reference: EXTERNAL_TABLE_DETAILS

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

Returns the amount of disk storage used by the source files backing external tables in the database. The information in this system table is useful in determining Hadoop license compliance.

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

Restrict your queries to filter by schema, table, or format to avoid expensive queries. the database calculates the values in this table at query time, so "SELECT *" accesses every input file contributing to every external table.

Predicates in queries may use only the TABLE_SCHEMA, TABLE_NAME, and SOURCE_FORMAT columns. Values are case-sensitive.

This table includes TEMP external tables.

This table reports only data that the current user can read. To include all the data backing external tables, either query this table as a user that has access to all HDFS data or use a session delegation token that grants this access. For more information about using delegation tokens, see Accessing kerberized HDFS data.

Column Name	Data Type	Description
`SCHEMA_OID`	INTEGER	The unique identification number of the schema in which the external table resides.
`TABLE_NAMESPACE`	VARCHAR	For Eon Mode databases, namespace that contains the external table.
`TABLE_SCHEMA`	VARCHAR	The name of the schema in which the external table resides. 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_OID`	INTEGER	A unique numeric ID assigned by the database catalog that identifies the table.
`TABLE_NAME`	VARCHAR	The table name.
`SOURCE_FORMAT`	VARCHAR	The data format the source file used, one of ORC, PARQUET, DELIMITED, USER DEFINED, or NULL if another format.
`TOTAL_FILE_COUNT`	INTEGER	The number of files used to store this table's data, expanding globs and partitions.
`TOTAL_FILE_SIZE_BYTES`	INTEGER	Total number of bytes used by all of this table's data files.
`SOURCE_STATEMENT`	VARCHAR	The load statement used to copy data from the source files.
`FILE_ACCESS_ERROR`	VARCHAR	The access error returned during the source statement. NULL, if there was no access error during the source statement.

Sql-Reference: HEALTH_WATCHDOG_BLOCKED_TRANSACTIONS

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

Provides detailed information about transactions blocked by the Heath Watchdog.

Column Name	Data Type	Description
`NODE_NAME`	VARCHAR	Name of the node.
`BLOCK_START_TIME`	TIMESTAMP	Time when the transaction was blocked.
`TRANSACTION_DESCRIPTION`	VARCHAR	The description of the transaction that was blocked.
`BLOCK_TYPE`	VARCHAR	Lists the health metric that initiated the block.

Privileges

None

Example

verticadb21249=> select * from health_watchdog_blocked_transactions;
 node_name |       block_start_time        |                          transaction_description                          |    block_type   
-----------+-------------------+-------------------------------+---------------------------------------------------------------------------+------------------
 initiator | 2024-06-17 22:24:08.636447-04 | Txn: a00000000000de 'create table table_t2(b int, c varchar(10), a int);' | GCLX QUEUE BLOAT
 initiator | 2024-06-17 22:28:43.340537-04 | Txn: a00000000000e9 'create table table_t3(b int, c varchar(10), a int);' | GCLX QUEUE BLOAT
(2 rows)

Sql-Reference: HIVE_CUSTOM_PARTITIONS_ACCESSED

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

This table provides information about all custom locations for Hive partition data that OpenText™ Analytics Database has accessed. It applies when Hive uses a non-default location for partition data, the HCatalog Connector is used to access that data, and the CREATE HCATALOG SCHEMA statement for the schema sets the CUSTOM_PARTITIONS parameter.

Column Name	Data Type	Description
`ACCESS_TIME`	TIMESTAMPTZ	Time when the database accessed the partition data.
`ACCESS_NODE`	VARCHAR(128)	Name of the node that performed the access.
`TRANSACTION_ID`	INTEGER	Identifier for the query that produced the access.
`FILESYSTEM`	VARCHAR(128)	File system of the partition data. This value is the scheme portion of the URL.
`AUTHORITY`	VARCHAR(128)	If the file system is HDFS, this value is the nameservice. If the file system is S3, it is the name of the bucket.
`URL`	VARCHAR(6400)	Full path to the partition.

Privileges

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

Sql-Reference: HOST_RESOURCES

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

Provides a snapshot of the node. This is useful for regularly polling the node with automated tools or scripts.

Column Name	Data Type	Description
`HOST_NAME`	VARCHAR	The host name for which information is listed.
`OPEN_FILES_LIMIT`	INTEGER	The maximum number of files that can be open at one time on the node.
`THREADS_LIMIT`	INTEGER	The maximum number of threads that can coexist on the node.
`CORE_FILE_LIMIT_MAX_SIZE_BYTES`	INTEGER	The maximum core file size allowed on the node.
`PROCESSOR_COUNT`	INTEGER	The number of system processors.
`PROCESSOR_CORE_COUNT`	INTEGER	The number of processor cores in the system.
`PROCESSOR_DESCRIPTION`	VARCHAR	A description of the processor. For example: Inter(R) Core(TM)2 Duo CPU T8100 @2.10GHz (1 row)
`OPENED_FILE_COUNT`	INTEGER	The total number of open files on the node.
`OPENED_SOCKET_COUNT`	INTEGER	The total number of open sockets on the node.
`OPENED_NONFILE_NONSOCKET_COUNT`	INTEGER	The total number of other file descriptions open in which 'other' could be a directory or FIFO. It is not an open file or socket.
`TOTAL_MEMORY_BYTES`	INTEGER	The total amount of physical RAM, in bytes, available on the system.
`TOTAL_MEMORY_FREE_BYTES`	INTEGER	The amount of physical RAM, in bytes, left unused by the system.
`TOTAL_BUFFER_MEMORY_BYTES`	INTEGER	The amount of physical RAM, in bytes, used for file buffers on the system
`TOTAL_MEMORY_CACHE_BYTES`	INTEGER	The amount of physical RAM, in bytes, used as cache memory on the system.
`TOTAL_SWAP_MEMORY_BYTES`	INTEGER	The total amount of swap memory available, in bytes, on the system.
`TOTAL_SWAP_MEMORY_FREE_BYTES`	INTEGER	The total amount of swap memory free, in bytes, on the system.
`DISK_SPACE_FREE_MB`	INTEGER	The free disk space available, in megabytes, for all storage location file systems (data directories).
`DISK_SPACE_USED_MB`	INTEGER	The disk space used, in megabytes, for all storage location file systems.
`DISK_SPACE_TOTAL_MB`	INTEGER	The total free disk space available, in megabytes, for all storage location file systems.

Examples

=> SELECT * FROM HOST_RESOURCES;
-[ RECORD 1 ]------------------+------------------------------------------
host_name                      | 10.20.100.247
open_files_limit               | 65536
threads_limit                  | 3833
core_file_limit_max_size_bytes | 0
processor_count                | 2
processor_core_count           | 2
processor_description          | Intel(R) Xeon(R) CPU E5-2695 v2 @ 2.40GHz
opened_file_count              | 8
opened_socket_count            | 15
opened_nonfile_nonsocket_count | 7
total_memory_bytes             | 4018823168
total_memory_free_bytes        | 126550016
total_buffer_memory_bytes      | 191803392
total_memory_cache_bytes       | 2418753536
total_swap_memory_bytes        | 2147479552
total_swap_memory_free_bytes   | 2145771520
disk_space_free_mb             | 18238
disk_space_used_mb             | 30013
disk_space_total_mb            | 48251
-[ RECORD 2 ]------------------+------------------------------------------
host_name                      | 10.20.100.248
open_files_limit               | 65536
threads_limit                  | 3833
core_file_limit_max_size_bytes | 0
processor_count                | 2
processor_core_count           | 2
processor_description          | Intel(R) Xeon(R) CPU E5-2695 v2 @ 2.40GHz
opened_file_count              | 8
opened_socket_count            | 9
opened_nonfile_nonsocket_count | 7
total_memory_bytes             | 4018823168
total_memory_free_bytes        | 356466688
total_buffer_memory_bytes      | 327278592
total_memory_cache_bytes       | 2744279040
total_swap_memory_bytes        | 2147479552
total_swap_memory_free_bytes   | 2147479552
disk_space_free_mb             | 37102
disk_space_used_mb             | 11149
disk_space_total_mb            | 48251
-[ RECORD 3 ]------------------+------------------------------------------
host_name                      | 10.20.100.249
open_files_limit               | 65536
threads_limit                  | 3833
core_file_limit_max_size_bytes | 0
processor_count                | 2
processor_core_count           | 2
processor_description          | Intel(R) Xeon(R) CPU E5-2695 v2 @ 2.40GHz
opened_file_count              | 8
opened_socket_count            | 9
opened_nonfile_nonsocket_count | 7
total_memory_bytes             | 4018823168
total_memory_free_bytes        | 241610752
total_buffer_memory_bytes      | 309395456
total_memory_cache_bytes       | 2881675264
total_swap_memory_bytes        | 2147479552
total_swap_memory_free_bytes   | 2147479552
disk_space_free_mb             | 37430
disk_space_used_mb             | 10821
disk_space_total_mb            | 48251

Sql-Reference: IO_USAGE

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

Provides disk I/O bandwidth usage history for the system.

Column Name	Data Type	Description
`NODE_NAME`	VARCHAR	Name of the node that is reporting the requested information.
`START_TIME`	TIMESTAMP	Beginning of history interval.
`END_TIME`	TIMESTAMP	End of history interval.
`READ_KBYTES_PER_SEC`	FLOAT	Counter history of the number of bytes read measured in kilobytes per second.
`WRITTEN_KBYTES_PER_SEC`	FLOAT	Counter history of the number of bytes written measured in kilobytes per second.

Privileges

Superuser

Sql-Reference: LDAP_LINK_DRYRUN_EVENTS

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

Collects the results from LDAP dry run meta-functions:

For detailed instructions on using these meta-functions, see Configuring LDAP link with dry runs.

Column Name	Data Type	Description
EVENT_TIMESTAMP	TIMESTAMP	The date and time of an LDAP server and OpenText™ Analytics Database LDAP Link interaction.
NODE_NAME	VARCHAR	The clerk node.
SESSION_ID	VARCHAR	The identification number of the LDAP Link session.
USER_ID	INTEGER	The unique, system-generated user identification number.
USER_NAME	VARCHAR	The name of the user for which the information is listed.
TRANSACTION_ID	INTEGER	The system-generated transaction identification number. Is NULL if a transaction id does not exist.
EVENT_TYPE	VARCHAR	The result of a dry run.
ENTRY_NAME	VARCHAR	The name of the object on which the event occurred, if applicable. For example, the event SYNC-STARTED does not use an object.
ROLE_NAME	VARCHAR	The name of a role.
LDAPURIHASH	INTEGER	The URI hash number for the LDAP user.
LDAP_URI	VARCHAR	The URI for the LDAP server.
BIND_DN	VARCHAR	The Distinguished Name used for the dry run bind.
FILTER_GROUP	VARCHAR	The group attribute passed to the dry run meta-functions as LDAPLinkFilterGroup.
FILTER_USER	VARCHAR	The user attribute passed to the dry run meta-functions as LDAPLinkFilterUser.
LINK_SCOPE	VARCHAR	The DN level to replicate, passed to the dry run meta-functions as LDAPLinkScope.
SEARCH_BASE	VARCHAR	The DN level from which LDAP Link begins the search, passed to the dry run meta-functions as LDAPLinkSearchBase.
GROUP_MEMBER	VARCHAR	Identifies the members of an LDAP group, passed to the dry run meta-functions as LDAPLinkGroupMembers.
GROUP_NAME	VARCHAR	The LDAP field to use when creating a role name in the database, passed to the dry run meta-functions as LDAPLinkGroupName.
LDAP_USER_NAME	VARCHAR	The attribute that identifies individual users, passed to the dry run meta-functions as LDAPLinkUserName.
TLS_REC_CERT	VARCHAR	The connection policy used for the dry run connection for certificate management. This connection policy is set through the LDAPLink TLS Configuration.
TLS_CA_CERT	VARCHAR	The CA certificate used for the dry run connection specified by the LDAPLink TLS Configuration.

Sql-Reference: LDAP_LINK_EVENTS

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

Monitors events that occurred during an LDAP Link synchronization.

Column Name	Data Type	Description
`EVENT_TIMESTAMP`	TIMESTAMP	The time the event occurred.
`NODE_NAME`	VARCHAR	The name of the node or nodes for which the information is listed.
`SESSION_ID`	VARCHAR	The identification number of the LDAP Link session.
`USER_ID`	INTEGER	The unique, system-generated user identification number.
`USER_NAME`	VARCHAR	The name of the user for which the information is listed.
`TRANSACTION_ID`	INTEGER	The system-generated transaction identification number. Is NULL if a transaction id does not exist.
`EVENT_TYPE`	VARCHAR	The type of event being logged, for example USER_CREATED and PROCESSING_STARTED.
`ENTRY_NAME`	VARCHAR	The name of the object on which the event occurred, if applicable. For example, the event SYNC-STARTED does not use an object.
`ENTRY_OID`	INTEGER	The unique identification number for the object on which the event occurred, if applicable.
`LDAPURIHASH`	INTEGER	The URI hash number for the LDAP user.