This content has been marked as final. Show 6 replies
Hi Lucas, if you activate the proxy query trace on the log4jAdmin web page, you see the worklist SQL printed in the log file.
Or, you can try to catch it using v$ views.
You can then try to execute and see if DB response is an issue.
Theoretically this is possible though the Query works fine returning the same number of rows, since don't forget this is a different SQL statement.
If DB reponse is the issue, the rest is DBA routine, execution plan, statistics, parameters, we all know that.
On the other hand if you run the SQL from e.g. SQL*Plus and it executes in no time, then your issue is something else.
In which case I would recommend to raise an SR.
Try this and post you findings back if you will.
it´s as you said. I turned on the "com.mslv.oms.dataaccesslayer.QueryProxy" in the Log4JAdmin GUI and saw the SQL in the .out log.
When I execute the SQL directly on the DB, it´s working fine.
So it looks like another issue than the DB.
Edited by: LucasT on Jul 19, 2012 4:10 PM