Skip to main content

Can anyone explain when the ODBC driver returns a DUP_COUNTERS result?

Google very "unhelpful" here :(

Can anyone explain when the ODBC driver returns a DUP_COUNTERS result?

Google very "unhelpful" here :(

Hi Stefano,

My thinking is this is SQL or the ODBC driver having trouble with SQL because of a possible few things:

My understanding is that UNlike mv; SQL maintains an internal unique identifier per table row value; and when updating the value is being duplicated; OR certain columns can be set to unique; and SQL will enforce that. So if there is a value [attribute] in mv which is non-unique across the database and the receiving column is set to unique in SQL, maybe that is the cause?

If that doesn't help; can you provide more background detail of when and how the issue occurs; and what steps you have taken so far to affect that outcome & the results. For example, modify the ODBC SQL table definition and see what happens?

Good luck.

David