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?
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
