tag:blogger.com,1999:blog-25740336.post114535284086445257..comments2023-08-24T22:26:48.675+01:00Comments on The PeopleSoft DBA Blog: %FirstRows MetaSQL uses FIRST_ROWS instead of FIRST_ROWS(n) hint on OracleDavid Kurtzhttp://www.blogger.com/profile/00468908370233805717noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-25740336.post-69498113091320443862017-06-17T20:28:21.566+01:002017-06-17T20:28:21.566+01:00This blog post is over 11 years old, and things ch...This blog post is over 11 years old, and things change and move on. PeopleTools no longer inserts the FIRST_ROWS hint. The <i>OracleDisableFirstRowsHint</i> parameter to suppress the hinting behaviour has also disappeared from the configuration files. Though I can not now remember when that happened. <br />The FIRST_ROWS* hints effectively force an indexed look up of the data. However, FIRST_ROWS is deprecated, you should use <i>FIRST_ROWS(n)</i>. If you need a hint you will either have to inject it into the code, or use an Oracle SQL profile or SQL patch. David Kurtzhttps://www.blogger.com/profile/00468908370233805717noreply@blogger.comtag:blogger.com,1999:blog-25740336.post-65102337475313139892017-04-26T12:31:39.617+01:002017-04-26T12:31:39.617+01:00Hi David,
We are also facing similar kind of issu...Hi David,<br /><br />We are also facing similar kind of issue in our system.<br />Customer search by name on 360 page and Case is timing out. There are no logs available. Can you please confirm following on your issue:<br /><br />When you used to run those queries manually with /*+ FIRST_ROWS */ Hint then also it used to timeout ?<br /><br />Because in our case when we run these queries in backend manually with /*+ FIRST_ROWS */ hint it executes within fraction of second.<br /><br />ThanksBloggerhttps://www.blogger.com/profile/17784042224910785642noreply@blogger.com