# Resolve overlapping data import ranges

Coordinator DB does not expose physical-part intersection errors or a command to repair such parts. If an import produces overlapping application data, investigate the source ranges and retry history. Two successful batches can overlap even when each SQL statement is valid.

## Identify the overlap

Record the predicates used by each batch. Prefer explicit half-open ranges such as `id >= 1000 AND id < 2000`; adjoining ranges can then use the same boundary without including it twice. For time ranges, agree on timezone and precision as well as inclusivity.

Query the destination by stable identifiers and compare it with the import manifest. A unique key can reject duplicate identity, but it cannot decide which conflicting payload is correct. Define that rule before replacing data.

## Repair with a reviewed change

Preserve a verified copy before deleting or rebuilding rows. Create a replacement dataset for the affected ranges, validate counts and representative values, then apply the correction with explicit SQL and an appropriate transaction boundary. Test the same overlapping input again to confirm the import policy handles retries.

Do not delete database files or run copied maintenance commands to repair an application-level overlap.

See [INSERT conflict policies](https://coordinatordb.com/docs/reference/statements/insert-into), [transactions](https://coordinatordb.com/docs/concepts/features/operations/insert/transactions) and [database copies](https://coordinatordb.com/docs/concepts/features/backup-restore/overview).