COPY Restrictions
Invalid Data
COPY considers the following data invalid:
- Missing columns (an input line has fewer columns than the recipient table).
- Extra columns (an input line has more columns than the recipient table).
- Empty columns for an INTEGER or DATE/TIME data type. If a column is empty for either of these types,
COPYdoes not use the default value that was defined by CREATE TABLE. However, if you do not supply a column option as part of theCOPYstatement, the default value is used. - Incorrect representation of a data type. For example, trying to load a non-numeric value into an INTEGER column is invalid.
Constraint Violations
If any primary key, unique key, or check constraints are enabled for automatic enforcement, Vertica enforces those constraints when you insert values into a table. If a violation occurs, Vertica rolls back the SQL statement and returns an error. This behavior occurs for INSERT, UPDATE, COPY, and MERGE SQL statements.
Note: Automatic constraint enforcement requires that you have SELECT privileges on the table containing the constraint.
Empty Line Handling
When COPY encounters an empty line while loading data, the line is neither inserted nor rejected, but COPY increments the line record number. Consider this behavior when evaluating rejected records. If you return a list of rejected records and COPY encountered an empty row while loading data, the position of rejected records is incremented by one.
Compressed File Errors
When loading compressed files, COPY might abort and report an error, if the file seems to be corrupted. For example, this behavior can occur if reading the header block fails.
