Query Masking Application Engine EODP_QRYMSK Goes To Error for MICROSOFT SQL SERVER DB
(Doc ID 2733325.1)
Last updated on NOVEMBER 26, 2021
Applies to:
PeopleSoft Enterprise HCM Human Resources - Version 9.2 to 9.2 [Release 9]Information in this document applies to any platform.
Symptoms
Application Engine EODP_QRYMSK goes to Error for Microsoft SQL Server Database.
ERROR
File: e:\pt858p05c_2006261426-retail\peopletools\src\psappeng\aedebug.hSQL error. Stmt #: 1738 Error Position: 0 Return: 8601 - [Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Incorrect syntax near 'A'.
[Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Statement(s) could not be prepared. (SQLSTATE 42000) 8180
Failed SQL stmt: UPDATE PSRECFIELD A SET A.USEEDIT2 = A.USEEDIT2 - 4194304 WHERE A.USEEDIT2 >= 4194304 AND (MOD(TRUNC(A.USEEDIT2/4194304),2)=1) AND EXISTS ( SELECT 'X' FROM PS_EODP_RECFLD_DAT R WHERE R.RECNAME_PARENT= A.RECNAME AND R.FIELDNAME= A.FIELDNAME AND R.EODP_PERS_IDFR = 'Y' AND R.EODP_SNSTV = 'Y' AND R.EODP_LASTUPDDTTM >= '1900-01-01 00:00:00.000' )
File: e:\pt858p05c_2006261426-retail\peopletools\src\psappeng\aedebug.hSQL error. Stmt #: 1738 Error Position: 0 Return: 8601 - [Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Incorrect syntax near 'A'.
[Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Statement(s) could not be prepared. (SQLSTATE 42000) 8180
Failed SQL stmt: UPDATE PSRECFIELD A SET A.USEEDIT2 = A.USEEDIT2 - 4194304 WHERE A.USEEDIT2 >= 4194304 AND (MOD(TRUNC(A.USEEDIT2/4194304),2)=1) AND EXISTS ( SELECT 'X' FROM PS_EODP_RECFLD_DAT R WHERE R.RECNAME_PARENT= A.RECNAME AND R.FIELDNAME= A.FIELDNAME AND R.EODP_PERS_IDFR = 'Y' AND R.EODP_SNSTV = 'Y' AND R.EODP_LASTUPDDTTM >= '1900-01-01 00:00:00.000' )
The issue can be reproduced at will with the following steps:
1. Enterprise Components > Data Privacy Framework > Query Masking > System Settings Then “ Enable Query masking”
2. Enterprise Components > Data Privacy Framework > Query Masking > Run Data Sync
3. App engine EODP_QRYMASK goes to Error
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |