Query Entity: Effect of Adding /*+FIRST_ROWS(10)*/ Hint in View

Hi All,

We have added /*+FIRST_ROWS(10)*/ Hint in one of our oracle views for the optimization. We are fetching the data from Appian into batches of 200 from this view.

I am curious to know whether this hint will have any effect on the data being fetched from Appian (In terms of actual data). In terms of performance yes definitely it improved the performance but I am observing below issue:

I am using batch size as 200

From Start Index 601 data i not getting changed and I am getting the same data every time. Is this "Hint" the culprit or there is some other issue. (Maybe this issue was already there)

(Our Query Entity is simple without any filter just with Paging Info where I am passing Start Index and Batch Size as ri!

  Discussion posts and replies are publicly visible

Parents
  • Please trace the sql being called inside from Appian on that view. For instance if you are displaying this view data in a report, set the SQL trace property in appian_log4j.properties file located in appian/ear/suite.ear/resources folder. Then tail the jboss log and click on the report and see what kind of sql is being executed by appian from inside. Consider evaluating that sql with an Oracle DBA to troubleshoot the issue especially when you reach batchsize of 600
Reply
  • Please trace the sql being called inside from Appian on that view. For instance if you are displaying this view data in a report, set the SQL trace property in appian_log4j.properties file located in appian/ear/suite.ear/resources folder. Then tail the jboss log and click on the report and see what kind of sql is being executed by appian from inside. Consider evaluating that sql with an Oracle DBA to troubleshoot the issue especially when you reach batchsize of 600
Children
No Data