How to get the Full Statement_String from Expensive Statements

[kirankumar440]

Hi All,

In the M_EXPENSIVE_STATEMENTS view , I can see statement_string as below & its occupying more memory.

But, I wanted to know the exact SQL code which is being executed & causing the higher memory consumption.

Could you please confirm if there any way to decode & get the underlying SQL code for it  ?

Example : STATEMENT_STRING = CALL SYS.TREXviaDBSL ( ?, ?, ? )

Br

Kiran K

[XaviPolo]

Hi @kirankumar440 

What you see here is the log of the parameterised call to the text search service.

I don't think you will be able to see the parameters as they are usually hidden for security reasons, as they may contain sensitive information.

You might try increasing the log level in the traces to see if you can see some more detail.
Or maybe there is the execution plan in the cache, look in the M_SQL_PLAN_CACHE view for the STATEMENT_STRING field to see if there is something with TREXviaDBSL.

Regards, 

[kirankumar440]

Hi @XaviPolo - Okay. There are some readymade SQL's in this note. Will any of the SQL's in this note helps to get more details based on HashID of that Expense Statement ? Note:1969700 - SQL Statement Collection for SAP HANA

[XaviPolo]

Sorry I've never used it.

[kirankumar440]

Checked the M_SQL_PLAN_CACHE with that Plan ID , But getting this not supported Err : "SAP DBTech JDBC: [7]: feature not supported: cannot find plan cache entry for call statement "