# Correct an unknown or invalid setting

Coordinator DB rejects unknown configuration elements and unsupported setting names. It does not provide a switch to silently ignore arbitrary incorrect settings. Treat the error as evidence that a name, value or configuration scope needs correction.

## Identify the interface

A server XML option belongs inside the `coordinator` root and is validated at startup, even if a command-line argument overrides it. A persisted database option uses one of the documented SET names. A format option uses `SETTINGS` on a statement, before `FORMAT` on an INSERT.

For example, a CSV delimiter is a statement option rather than a database default:

```sql
SELECT 1 AS id, 'Ada' AS name
SETTINGS csv_separator = ';'
FORMAT csv;
```

## Check names and values

Inspect the relevant reference for spelling, type and accepted range. Do not assume another database's option is an alias. `system.settings` lists effective database values and read-only format defaults, but it omits server-only XML options.

Correct one setting at a time and repeat a minimal request. When a copied configuration contains many unsupported names, remove those names deliberately after reviewing their purpose rather than disabling validation. That avoids silently losing a behavior the operator expected.

See [configuration validation](https://coordinatordb.com/docs/concepts/features/configuration/server-config/configuration-files), [SET](https://coordinatordb.com/docs/reference/statements/set) and [format settings](https://coordinatordb.com/docs/reference/settings/formats).