E-SEC: Can the Updates on the PSOPRDEFN and PSACCESSLOG tables be Avoided?
Last updated on SEPTEMBER 09, 2015
Applies to:PeopleSoft Enterprise PT PeopleTools - Version 8.4 and later
Information in this document applies to any platform.
***Checked for Relevance 19/12/2012***
In PT 8.4x, when a User logs in, there are updates are taking place to the PSOPRDEFN and PSACCESSLOG tables. See below for an exerpt from a trace file during a login:
UPDATE PSOPRDEFN SET LASTSIGNONDTTM = :1 WHERE OPRID = :2
INSERT INTO PSACCESSLOG (OPRID, LOGIPADDRESS, LOGINDTTM, LOGOUTDTTM) VALUES (:1, :2, :3, :4)
UPDATE PSACCESSLOG SET LOGOUTDTTM = :1 WHERE OPRID = :2 AND LOGIPADDRESS = :3 AND LOGINDTTM = :4
Is there any way to avoid these updates? We do not use the PSACCESSLOG for login information and we do not care to update the PSOPRDEFN table with the Last Signon Date/Time.
Here we need ability to prevent these additional update and insert SQL statements during Signon and Signout process which would result in less database processing and improve response time.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms