TREX (in VMS/VELO) - is it working correctly or not?

[Former Member]

Hi all

I have already posted a detailed question about the issue we are having in the SAP Oracle section (https://scn.sap.com/thread/3642137) which has had some discussion and has delved into the workings of Oracle and execution plans.

What I want to do here is go down a different path, and ask here a more generic question about how TREX works, or at least, the way TREX/SES works when activated for VMS/transaction VELO.

My understanding was that when a user runs a search in VELO with TREX set up, that the selection criteria is effectively passed to TREX, which then goes ahead and checks its index and returns vehicle IDs (VGUID) to the transaction. A modified SAP/SQL query is then ran against the SAP system, making use of these vehicle IDs and thus speeding up the search.

So far right?

However, it seems that although the SQL ran does appear to now contain the relevant VGUIDs (from tracing we see that with TREX disabled VGUID does not appear in the SQL) it also contains all (except one) of the original fields/search criteria from the initial search.

Surely it doesn't need this? As TREX has returned the relevant VGUIDs, matching the users selection criteria, the SQL search should purely search on VGUID - right?

As it is, those extra criteria, which includes a huge in-list of material numbers, are slowing down the search - it takes over 8 times longer with TREX enabled!

Is TREX configured incorrectly - can you configure somewhere what exactly TREX returns? Or is this 'hard coded' and it more likely a bug within the code/VELO transaction?

Thanks

Ross

[Sriram2009]

Hi Ross

From the Trex admin tool you can connect all the your SAP systems?

SAP search engine Version & patch level?

BR

SS

[Former Member]

Yes, everything seems to work in TREX. Like I said, it does appear to be going to TREX and obtaining the VGUIDs from it - but the resulting SQL is not efficient.

TREX is version 7.10.48.00 running on Linux.

SAP is 701 EHP4 (SAP_APPL 604 SP8), Basis/ABAP etc Support Package 9, on Oracle 11g, AIX.

[Sriram2009]

Hi

Thanks for your info

Is it custom development? you can enable the trace to check the searching happen with Trex or using DB search?

[Former Member]

There's no custom development, this is SAP standard. It *should* speed up the search - what I'm asking is whether it could be an issue with the config, or whether it's possibly a bug?

We have already ran SQL traces to see the code being ran, and can see the difference with TREX off and on.

I know you can also trace TREX but I don't think that will help - the TREX part is running quickly - it's the SQL that it returns that would appear to be problematic.