| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1344.1 | Little more information | BROKE::BASTINE | | Mon May 19 1997 14:56 | 8 |
| I called the customer today... he said that they have more than 50 fields
that make up the index that caused the conformance errors. Does ODBC have
some limit of how many fields an index can have?? Does SQL/Services???
Thanks,
Renee
|
| 1344.2 | | M5::JBALOGH | | Mon May 19 1997 15:01 | 9 |
| How many segments were in the index? What were the data types? Were any
of these based on date or timestamp fields?
I would guess your customer is using MS Access or VB? I have seen many
cases where these products return a conformance error when the real
problem has nothing to do with conformance to the ODBC spec. We are
probably going to need to chase this down through log files...
John
|
| 1344.3 | | M5::JBALOGH | | Mon May 19 1997 15:03 | 8 |
| re: .1
Sorry, notes collision...
I do not believe ODBC has a limit like this but I would bet the front
end does...
John
|
| 1344.4 | more information | BROKE::BASTINE | | Mon May 19 1997 20:18 | 15 |
| Customer said the index is made up of mostly text, some integer.
Access has a limit of 10 fields for an index, the customer is using access,
however, the customer has other tables with indeces containing more than
10 fields and access doesn't seem to have a problem with those.
The reason I had him drop the index was the client logs showed this index
showing up over and over and over again... gave us an indication that something
was wrong with it, when we dropped the index, it worked. I can request a copy
of that log file, but not so sure I'd be able to pick out the problem...
Can I send it to you, John? :) :)
Thanks!
Renee
|
| 1344.5 | Don't waste your time... | M5::JBALOGH | | Tue May 20 1997 09:14 | 14 |
| If Access is limited to 10 fields in an index and the customer had 50,
it sounds like you have already solved their problem. I wouldn't waste
any time reading logs if they are exceeding limits on the front end.
(MS Access).
I would also suggest they drop some columns out of the other indexes
that are exceeding limits. Chances are good that they will get bit by
these indexes sometime too...
It is rather interesting that Access was complaining about an ODBC
conformance error when the problem was really a limit in Access
itself...
John
|
| 1344.6 | What do those msa limits apply to??? | BROKE::BASTINE | | Tue May 20 1997 09:41 | 7 |
| Do those access limits apply to tables that aren't MSAccess tables, but are
external or imported tables?
I can't help wonder why others work and this one doesn't... can't help it. :)
Renee
|
| 1344.7 | Access limitation... | M5::JBALOGH | | Tue May 20 1997 12:24 | 17 |
| MS Access requires a unique index on the server table to perform
certain operations. To get this, it make a native ODBC call
SQLStatistics. This call returns information about all the indexes in
the table.
MS Access will just use the first unique index it finds and it only
looks for indexes when the table is first attached.
I would suspect the large indexes were added after the table was
attached or Access just picked up a different index. I would suggest he
stay within the limits of Access if he wants to use it. This is NOT an
ODBC or RDB limit...
Does this help?
John
|
| 1344.8 | Conformance errors listing | ataxp1.at.oracle.com::EKREISLE | Erich Kreisler | Mon May 26 1997 11:34 | 8 |
| Just for others running into these conformance errors. UKWWS Support page
http://ww-sup.uk.oracle.com
has a note on the conformance errors and their meaning and here is the one for
-7719 (Search for 'odbc' and '7719'):
-7719 SQLStatistics ==> SQLGetData(COLUMN_NAME) total length of columns for
index > 255 bytes
erich
|