Select a documentation version: <button class="button button-with-icon cloud-select-dropdown__button button-primary" aria-haspopup="true">18.4.0</button>

- [Current (18.4.0)](https://docs.cloud.google.com/alloydb/omni/kubernetes/current/docs/columnar-engine/troubleshoot-the-columnar-engine.md.txt)
- [18.4.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/18.4.0/docs/columnar-engine/troubleshoot-the-columnar-engine.md.txt)
- [18.3.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/18.3.0/docs/columnar-engine/troubleshoot-the-columnar-engine.md.txt)
- [18.1.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/18.1.0/docs/columnar-engine/troubleshoot-the-columnar-engine.md.txt)
- [17.10.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/17.10.0/docs/columnar-engine/troubleshoot-the-columnar-engine.md.txt)
- [17.9.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/17.9.0/docs/columnar-engine/troubleshoot-the-columnar-engine.md.txt)
- [17.7.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/17.7.0/docs/columnar-engine/troubleshoot-the-columnar-engine.md.txt)
- [17.5.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/17.5.0/docs/columnar-engine/troubleshoot-the-columnar-engine.md.txt)
- [16.14.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/16.14.0/docs/columnar-engine/troubleshoot-the-columnar-engine.md.txt)
- [16.13.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/16.13.0/docs/columnar-engine/troubleshoot-the-columnar-engine.md.txt)
- [16.11.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/16.11.0/docs/columnar-engine/troubleshoot-the-columnar-engine.md.txt)
- [16.9.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/16.9.0/docs/columnar-engine/troubleshoot-the-columnar-engine.md.txt)
- [16.8.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/16.8.0/docs/columnar-engine/troubleshoot-the-columnar-engine.md.txt)
- [16.3.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/16.3.0/docs/columnar-engine/troubleshoot-the-columnar-engine.md.txt)

<br />

This page describes how to troubleshoot issues that you might encounter when you use the AlloyDB Omni columnar engine. For more information about the columnar engine, see [Columnar engine overview](https://docs.cloud.google.com/alloydb/omni/kubernetes/current/docs/columnar-engine/overview.md.txt).

<br />

## Fix the "insufficient shared memory" error

If you run AlloyDB Omni without enough shared memory
for the columnar engine, then you might see the following error:

    Insufficient shared memory for generating the columnar formats.

To address this issue, increase the size of the `/dev/shm` partition on your
Kubernetes nodes or decrease the memory allocated to the columnar engine so that
it doesn't exceed the available `/dev/shm` size. For more information, see
[Configure the columnar engine](https://docs.cloud.google.com/alloydb/omni/kubernetes/current/docs/columnar-engine/configure.md.txt#configure-memory).

## Find the tables that are populated in the columnar engine

In the `g_columnar_relations` view, create queries to find the tables that are
present in the columnar engine.

```sql
SELECT * FROM g_columnar_relations;
```

## Find the overall memory that the columnar engine uses

Use the `google_columnar_engine_memory_available()` SQL function to determine
the amount of memory that the columnar engine uses.

```sql
SELECT google_columnar_engine_memory_available();
```

## Determine if specific columns aren't populated in the columnar engine

Try the following possible solutions:

- Check whether the columnar engine supports the column's data type.
- If you recently added or dropped columns to the base table, verify that you performed the same operation in the columnar engine.

## Verify if a query uses the columnar engine

In the query plan, verify if there's a "Custom Scan (columnar scan)"
planner node.

## Find the maintenance jobs in progress

Query in the `g_columnar_jobs` view to find the jobs in progress.

```sql
SELECT * FROM g_columnar_jobs;
```

## Set the amount of resources that maintenance activities use in the columnar engine

By default, the columnar engine uses up to 20% of the database resources. To
increase or decrease this usage, adjust the
`google_columnar_engine.maintenance_cpu_percentage` (GUC) setting. For more information,
see [Adjust the CPU resources for maintenance tasks](https://docs.cloud.google.com/alloydb/omni/kubernetes/current/docs/columnar-engine/tune-columnar-engine.md.txt#adjust-cpu-resources).