> ## Documentation Index
> Fetch the complete documentation index at: https://cockroachlabs.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# SHOW INSPECT ERRORS
export const InternalLink = ({version, path = "", children, ...props}) => {
let detectedVersion = version || "stable";
if (typeof window !== 'undefined' && !version) {
const match = window.location.pathname.match(/\/docs\/([^/]+)/);
if (match) {
detectedVersion = match[1];
}
}
const normalizedPath = path.startsWith("/") ? path.slice(1) : path;
return
{children}
;
};
The `SHOW INSPECT ERRORS` statement displays errors recorded by an `INSPECT` job.
`SHOW INSPECT ERRORS` shows results for a single `INSPECT` job at a time; it does not aggregate results across jobs. By default, it returns errors from the most recent completed, successful `INSPECT` job for the specified table. To view errors from a specific job, use `SHOW INSPECT ERRORS FOR JOB {job_id}`.
## Required privileges
To run `SHOW INSPECT ERRORS`, the user must have:
* The `INSPECT` system-level privilege, which is required to run the `INSPECT` statement.
## Synopsis
## Parameters
| Parameter | Syntax | Description |
| ------------------------- | ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| `opt\_for\_table\_clause` | `FOR TABLE {table\_name}` | Optional. Show errors for the specified table. |
| `opt\_for\_job\_clause` | `FOR JOB {job\_id}` | Optional. Show errors produced by the job ID returned by the `INSPECT` statement. |
| `opt\_with\_details` | `WITH DETAILS` | Optional. Include structured error metadata from the `details` column (JSON) in the results. |
## Response
`SHOW INSPECT ERRORS` returns the following columns, with one row per issue detected.
| Field | Description |
| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `job\_id` | The ID of the `INSPECT` job that detected the issue. |
| `error\_type` | The type of inconsistency detected. For more information, see [Error types](#error-types). |
| `aost` | The `AS OF SYSTEM TIME` timestamp used by the validation job (if any). |
| `database\_name` | The database containing the schema object with an issue. |
| `schema\_name` | The schema containing the object with an issue. |
| `object\_name` | The table or index with an issue. |
| `primary\_key` | The primary key of the row involved in the issue, if applicable. |
| `details` | This column is present only if `WITH DETAILS` is specified. It contains structured metadata (JSON) describing the issue. |
### Error types
The `INSPECT` implementation reports the following `error_type` values:
| Error type | Meaning |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `missing\_secondary\_index\_entry` | A row in the primary index is missing a corresponding entry in a secondary index. If you see this error, contact Support. |
| `dangling\_secondary\_index\_entry` | A secondary index entry exists, but the referenced primary index row does not. If you see this error, contact Support. |
| `internal\_error` | An error occurred while `INSPECT` was running its validation queries (for example, an MVCC GC timeout). The cause of this error type is usually not related to data validity. Investigate the underlying job error details and cluster logs to determine the cause before deciding whether to contact Support. |
## Examples
### Show the latest errors for a table
To see the errors found by the most recent `INSPECT` job, issue the following statement:
```sql theme={"theme":{"light":"catppuccin-mocha","dark":"catppuccin-mocha"}}
SHOW INSPECT ERRORS FOR TABLE movr.public.users;
```
### Show errors for a specific inspection job
When you issue the `INSPECT` statement, a `NOTICE` message is returned to the client showing the job ID, e.g.,
```sql theme={"theme":{"light":"catppuccin-mocha","dark":"catppuccin-mocha"}}
INSPECT TABLE movr.public.users AS OF SYSTEM TIME '-10s';
```
```text theme={"theme":{"light":"catppuccin-mocha","dark":"catppuccin-mocha"}}
NOTICE: waiting for INSPECT job to complete: 1141477013029322753
If the statement is canceled, the job will continue in the background.
```
To show errors for a job, issue the following statement:
```sql theme={"theme":{"light":"catppuccin-mocha","dark":"catppuccin-mocha"}}
SHOW INSPECT ERRORS FOR JOB 1141477013029322753;
```
If there are no errors associated with that job ID, the output is:
```text theme={"theme":{"light":"catppuccin-mocha","dark":"catppuccin-mocha"}}
SHOW INSPECT ERRORS 0
```
Note that if you issue a job ID for a nonexistent job, you will see the same output as for a job with no errors:
```sql theme={"theme":{"light":"catppuccin-mocha","dark":"catppuccin-mocha"}}
SHOW INSPECT ERRORS FOR JOB 0;
```
```text theme={"theme":{"light":"catppuccin-mocha","dark":"catppuccin-mocha"}}
SHOW INSPECT ERRORS 0
```
### Show errors with details
```sql theme={"theme":{"light":"catppuccin-mocha","dark":"catppuccin-mocha"}}
SHOW INSPECT ERRORS FOR TABLE movr.public.users WITH DETAILS;
```
## See also
* `INSPECT`
* `SHOW JOBS`
* Jobs page in DB Console
* Authorization