On 10/14/2018 4:07 PM, Jonathan Ball wrote:
We are in the process of partitioning some large tables because they
soon will reach the limits for a single partition. In testing, we have
a program that is writing a row/record (native RPG write) that should go
to the third partition based on the range key. The write attempt is
trying to put it into the first partition, and it is throwing a check constraint violation CPF502F: "Check constraint violation on member PART000001."
I would have expected the DB2 database manager would take care of
ensuring the row was written to the correct partition. I can't find anything in the programming reference manuals addressing how to ensure
that the row is written to the correct partition. Changing the programs
to use SQL inserts rather than native language writes is not an option.
Any thoughts?
To do typical native I/O on a partitioned table requires a
non-partitioned index that spans all of the partitions in the table. A
write to the index in a HLL program will be put into the correct
partition by the database manager.
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)