Load fails with SQL3526N Reason Code: "5".

Technote (FAQ)


Question

Why does the load command fail with SQL3526N The modifier clause "IDENTITYOVERRIDE" is inconsistent with the current load command. Reason code: "5"

Cause

The identityoverride modifier is used for loading user-supplied values into a table with a GENERATED ALWAYS identity column. Use the db2look option to see if the column was created with GENERATED ALWAYS in it. An example of a db2look command would be:

db2look -d <dbname> -a -e -l -x -f -o db2look_<dbname>.ddl

Where dbname is at put the name of the database in question. Once done review the ddl file for the problem column, lile:

cat db2look_sample.ddl | grep col1
""COL1" BIGINT NOT NULL GENERATED BY DEFAULT AS IDENTITY


Answer

Make sure that your column is defined as GENERATED ALWAYS and *not* as GENERATED DEFAULT. An example with GENERATED ALWAYS in the create statement would be:


db2 "CREATE TABLE test(col1 BIGINT NOT NULL GENERATED ALWAYS AS IDENTITY (START WITH 1 INCREMENT BY 1 MINVALUE 1 MAXVALUE 100))";


Related information

Identity column load considerations
SQL3526N
db2look - DB2 statistics and DDL extraction tool comman

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 for Linux, UNIX and Windows

Software version:

9.5, 9.7, 9.8, 10.1

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Software edition:

Advanced Enterprise Server, Enterprise Server, Workgroup Server

Reference #:

1638391

Modified date:

2013-05-24

Translate my page

Machine Translation

Content navigation