insert into LETD.OBJ_OSN_INF (OBJ_OSN_ID, V_OBJ_ID, OKATO_ID, DOP_RAZM, VNAME, NAME, OBJ_OSN_N, OBJ_OSN_K, ACTIV) values ( 1015623 ,  2 , null, '', 'пфеб-аюкр : лекхунбн', 'пфеб-аюкр : лекхунбн',  1183 ,  1185 , 'N')
DB21034E  The command was processed as an SQL statement because it was not a 
valid Command Line Processor command.  During SQL processing it returned:
SQL0803N  One or more values in the INSERT statement, UPDATE statement, or 
foreign key update caused by a DELETE statement are not valid because the 
primary key, unique constraint or unique index identified by "OBJROSNR" 
constrains table "000000C31D" from having duplicate values for the index key.  
SQLSTATE= 23505 

SQL0803N  One or more values in the INSERT statement, UPDATE statement, or foreign key update caused by a DELETE statement are not valid because the primary key, unique constraint or unique index identified by "OBJROSNR" constrains table "000000C31D" from having duplicate values for the index key.

Explanation: 

The INSERT or UPDATE object table "<table-name>" is constrained by one
or more UNIQUE indexes to have unique values in certain columns or
groups of columns. Alternatively, a DELETE statement on a parent table
caused the update of a foreign key in a dependent table "<table-name>"
that is constrained by one or more UNIQUE indexes. Unique indexes might
support primary keys or unique constraints defined on a table. The
statement cannot be processed because completing the requested INSERT,
UPDATE or DELETE statement would result in duplicate column values. If
the index is on an XML column, the duplicate values for the index key
may be generated from within a single XML document.

Alternatively, if a view is the object of the INSERT or UPDATE
statement, it is the table "<table-name>" on which the view is defined
that is constrained.

If "<index-id>" is an integer value, the index name can be obtained from
SYSCAT.INDEXES by issuing the following query: 

SELECT INDNAME, INDSCHEMA
  FROM SYSCAT.INDEXES
  WHERE IID = <index-id>
  AND TABSCHEMA = 'schema'
  AND TABNAME = 'table'

where schema represents the schema portion of "<table-name>" and table
represents the table name portion of "<table-name>".

The statement cannot be processed. The table remains unchanged.

User response: 

Examine the definition for the index identified by "<index-id>".

For an UPDATE statement, ensure that the specified operation is not
itself inconsistent with the uniqueness constraint. If this does not
show the error, examine the object table content to determine the cause
of the problem.

For an INSERT statement, examine the object table content to determine
which of the values in the specified value list violates the uniqueness
constraint. Alternatively, if the INSERT statement contains a subquery,
the object table contents addressed by that subquery must be matched
against the object table contents to determine the cause of the problem.
Note that if the table is protected using a security policy, your LBAC
credentials may not allow you to see the rows that are causing the
error.

If the index is on an XML column and the statement is either INSERT or
UPDATE, consider whether the XML document would result in duplicate
values from within the single XML document.

For a DELETE statement, examine the identified dependent table for
unique constraints on foreign keys that are defined with the rule ON
DELETE SET NULL. This table has a foreign key column included in the
identified unique index that cannot be set to null since there is
already a null in the column for that table.

Federated system users: isolate the problem to the data source failing
the request (refer to the Troubleshooting Guide to determine which data
source is failing to process the SQL statement) and examine the index
definitions and data for the conditions listed previously.
 sqlcode: - 803 

 sqlstate:  23505 

SQLCODE: - 803