Skip to Content

How do you trace OData for HANA XSOData?

What is the best way to trace a OData call via PostMan in HANA Studio?

Without getting into the specifics of our environment, we have created OData Services on HANA using XSOData. I use postman to test custom procedures used for create/update and most everything works fine except for two PUTs (Updates) that run until timed out (10 minutes). I would like to know how to trace, to find out IF there is anything I can do about these statements, or if it is a problem with OData itself. The updates work well as stored procedure calls within HANA, but fail to get called from OData before the time out. The reason I know they aren't getting called is because I forced an immediate error at the beginning of the update procedure and it never gets to that statement.

One side question, what takes place when a PUT is issued? Is the process running its own GET to get the "old" information? Is there a way, through PostMan to provide both the old and new data?

We are running HANA 1.0 SPS12 and the OData is v2.0.



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Mar 07, 2018 at 09:51 PM

    in order to trace, see if you can add a user trace.... that way when the user executes it.. it should be logged... alternatively, see if the xsengine trace contains this information.

    I found a few blogs while searching for this topic - try this one:

    make sure you have your table exposed like the syntax on the blog i added here

    service {

    yourTable as tbl

    create using "yourStoredPRoc";


    hope this works - in your stored proc.. make sure your sql procedure has invoker and make sure the user has execute privileges to this stored proc and insert/update privileges to the table

    Add comment
    10|10000 characters needed characters exceeded

    • hi Dan, I only know how to read the xs engine trace --- but i am not sure if it will capture all of the odata calls.

      another option, ask your admin to trace it by the user .. maybe that trace will have additional details