Yes Jim. It is T24 data and the index is on some LOCAL REF fields. Basically an index on a MV field. But the strange thing is this behavious is seen only in one particular environment. Whereas in other similar environments we dont see any problem. The release/patch levels of Oracle, jBase, JEDI, JDLS are all same in all environments. All tables are of XMLORA type. We even tried dropping those problamatic indexes and recreating them. But to no avail.
Mahesh On Sep 19, 3:34 am, Jim Idle <[email protected]> wrote: > Ate you tryingbto index something awful like an itype or correlative > etc? There are probably limits on what the oracle interface can handle. > > Jim > > On Sep 18, 2009, at 1:59 AM, Mahesh <[email protected]> wrote: > > > > > > > We use Oracle db. Some indexes were created from the jShell. While mos > > of the indexes seem to be active, for some it seems to be inactive. > > > When we send a query from jBase with a "WITH" clause on the indexed > > key, for some the SQL query to Oracle is translated with a "WHERE" > > clause and the performance is fine. But for a few, though there is an > > index available for that key, the translated SQL query does not have > > the "WHERE" clause. Hence the Oracle db returns the entire cursor and > > the filtering happens at jBase end. What could be the reason for this > > behaviour?- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ Please read the posting guidelines at: http://groups.google.com/group/jBASE/web/Posting%20Guidelines IMPORTANT: Type T24: at the start of the subject line for questions specific to Globus/T24 To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en -~----------~----~----~----~------~----~------~--~---
