tag:blogger.com,1999:blog-31216575.post2894940145747246657..comments2024-01-27T07:32:53.464+01:00Comments on On The Peoplesoft Road: Peoplesoft database connectivity part 3/3 : Apps/Batch/PiaNicolas Gasparottohttp://www.blogger.com/profile/06634519580752248909noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-31216575.post-70168757401395810422016-02-25T19:30:22.612+01:002016-02-25T19:30:22.612+01:00Hi could you tell mewhere can I find the Query tha...Hi could you tell mewhere can I find the Query that checks the user roles at the login, some WEBLIB or FUNCLIB. Thanks a lotAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-31216575.post-83404305600079094922011-09-28T11:00:51.381+02:002011-09-28T11:00:51.381+02:00Erik,
That's indeed weird, I have no explanati...Erik,<br />That's indeed weird, I have no explanation neither, one pass would be enough, unfortunately this is how it is coded. Probably it is a a legacy of older version...<br />I remember older Peopletools I worked on with a lot of login time issues (<=8.48), that has greatly been improved since then, but we have still that kind of stuff.<br />Just few thoughts : try to keep the lowest as possible the number of roles... You could also investigate a code change on the login to query a MView (containing all required columns - CLASSID and ROLEUSER - and refreshing on change of the underlying tables), but of course, it moves you out of support.<br />Good luck,<br /><br />Nicolas.Nicolas Gasparottohttps://www.blogger.com/profile/06634519580752248909noreply@blogger.comtag:blogger.com,1999:blog-31216575.post-11199638837105750492011-09-28T10:24:37.491+02:002011-09-28T10:24:37.491+02:00Hi,
Stumbled upon your blog about the peoplesoft ...Hi,<br /><br />Stumbled upon your blog about the peoplesoft connects. Interesting stuff. <br />But there is one thing youi never mention an which I (DB tuning expert) find very interesting and strange as well.<br />When logging on there is a query:<br />SELECT COUNT (DISTINCT CLASSID)<br /> FROM PSROLEUSER A, PSROLECLASS B, PSROLEDEFN C<br /> WHERE A.ROLEUSER = :1<br /> AND A.ROLENAME = B.ROLENAME<br /> AND B.ROLENAME = C.ROLENAME<br /> AND A.ROLENAME = C.ROLENAME<br /> AND C.ROLESTATUS = 'A'<br /><br />Strange enough after this the same query is used again and now without the count. This is really weird since it is relatively expensive query in the system I am working on. In my system the query does 96 logical IO's. times 2 makes 192 logical reads. This does not seem very high, but the system I am tuning has a hugh amount of logon's.<br />My question, for which I have not found an answer, is WHY is it doing it twice. I do not see any valid reason for this.Erikhttps://www.blogger.com/profile/06175392280100860579noreply@blogger.com