Kbase P90895: ODBC DataServer is not pulling any indexes and sequences from the AS/400 DB2 database
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
9/17/2008 |
|
Status: Verified
SYMPTOM(s):
ODBC DataServer is not pulling any indexes and sequences from the AS/400 DB2 database
ODBC DataServer is not pulling any Keyed Physical indexes from the DB2/400 database
FACT(s) (Environment):
The ODBC driver is DB2/400 Wire Protocol
ODBC DataServer
OpenEdge 10.x
Windows NT 32 Intel/Windows 2000
CAUSE:
Bug# OE00096861
FIX:
There are a few workarounds:
1. Manually modify schema holder to add the indexes. In practice creating logical files on iSeries doesn't require creating it in the schema holder because schema holder is only used by DataServer to build proper SQL statements. I5/OS SQL Engine doesn't accept hints and will choose the best index (or perform a table scan, or an index scan with a table probe, or an index probe with a table probe, etc) to retrieve requested result set. It sometimes rewrites SQL statements as well. In other words newly created index may be used even when there's no information for it in the schema holder. So, customers can ignore this fact if the index is created for their native RPG/COBOL application.
2. Create a corresponding index using SQL tools (like iSeries Navigator) and then re-pull the table to the schema holder. It will be recognized as long as Logical File is created as a SQL index. Note that creating SQL index even though the native one exists (with the same set or subset of key fields) wouldn't affect their RPG/COBOL Application. IBM even suggests creating SQL index first and then native DDS LF to get a wider access path.