On 09/21/2009 07:48 PM, துக்ளக் wrote: > 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. Clearly something is different in this envioronment ;-) > 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. > Check the following:
1) Are the Oracle drivers at the same level; 2) Is this a different Oracle Database or different view? Perhaps you don't have permissions on this in some manner; 3) Ensure that the jEDI stub is exaclty the same (subject to any required environmental differences); 4) Call TEMENOS help desk if you have not yet done so; 5) Turn on any trace/debug options for the jEDI driver and see if you can see what it is doing. Somehow it is deciding that that index does not exist in Oracle and so it is reverting to local selection. It probably isn't anything wrong with the index per se, but that the jEDI isn;t seeing it as compatible with the query; 6) Check that the dictionary entry is exactly the same on all environments - this would be my first check actually. Jim --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
