provides several capabilities to check on the quality of data on a node and to quarantine segment groups that are problematic for any reason. Also, you can manage pages by converting them to segments. Related to data integrity is the ability to rebuild tasks. For details, see Distributed Tasks.Documentation Index
Fetch the complete documentation index at: https://docs.ocient.com/llms.txt
Use this file to discover all available pages before exploring further.
ALTER SEGMENT QUARANTINE
ALTER SEGMENT QUARANTINE isolates segment groups from segment generation or queries. Use this SQL statement if segments are causing unexpected results or crashes. The segments can be un-quarantined by setting quarantine_level to none.
Syntax
SQL
| Parameter | Data type | Description |
|---|---|---|
seg_id | numeric | The identification numbers for segment groups. Depending on your ALTER SEGMENT QUARANTINE statement, the Ocient System quarantines the specified segment groups for having an existing quarantine removed. For details about finding abnormal segments, see the Guide to Rebuilding Segments. |
Using Quarantine Levels ( <quarantine_level> )
You can place quarantines at these segment levels.
| Level | Description |
|---|---|
segment_generation | Isolates the specified segments from segment generation. This statement prevents corrupt data from causing problems while still leaving the data available for future analysis. |
query | Isolates segment groups from subsequent queries. Data that is quarantined at the query level is not returned by database queries. This can be useful to prevent corrupt data from causing query problems while leaving it available for future analysis. |
all | Isolates the specified segments from segment generation and subsequent queries. |
none | Removes any quarantines from the specified segments. |
segment_generation.
SQL
segment_generation.
SQL
SQL
SQL
query level.
SQL
query level.
SQL
SQL
DRAIN PAGES
TheDRAIN PAGES SQL statement instructs the Ocient System to immediately convert buffered pages into segments on one or more Loader Nodes. During normal operation, the system converts pages to segments automatically based on internal thresholds and timeouts, so the DRAIN PAGES statement is usually needed only in special circumstances. For example, draining pages can be useful before performing planned maintenance on Loader Nodes.
The SQL statement targets all Loader Nodes by default. You can optionally scope the operation to a specific storage scope or table, and you can restrict it to a subset of Loader Nodes.
Required Privileges
- To drain all pages or drain pages for a specific storage scope, you must have
UPDATEprivileges on the system. - To drain pages for a specific table, you must have
UPDATEprivileges on the system orDELETEprivileges on the database that contains the table.
SQL
| Parameter | Type | Description |
|---|---|---|
scope_uuid | string | The Universally Unique IDentifier (UUID) of a storage scope. When you specify this value, the system converts only pages that belong to this storage scope. This value is mutually exclusive with the table_uuid value. To find storage scope UUIDs, query the sys.storage_scopes system catalog table. |
table_uuid | string | The UUID of a table. When you specify this value, the system converts only pages that belong to this table. This value is mutually exclusive with the scope_uuid value. To find table UUIDs, query the sys.tables system catalog table. |
loader_name | string | The name of a Loader Node. When you specify one or more loader names, the system sends the drain request only to those nodes. By default, the system sends the request to all Loader Nodes. |
SQL
a1b2c3d4-e5f6-7890-abcd-ef1234567890.
SQL
12345678-abcd-ef01-2345-6789abcdef01.
SQL
loader-node-1 and loader-node-2 Loader Nodes.
SQL
12345678-abcd-ef01-2345-6789abcdef01 on the loader-node-1 Loader Node.
SQL

