My Oracle Support Banner

Microsoft SQL Server Error: When Running the Refresh Groups (SCRTY_GB_REF) AE, Error occurs: "Failed SQL stmt: DELETE FROM PS_SCRTY_GBRES_TBL" (Doc ID 3037511.1)

Last updated on NOVEMBER 20, 2024

Applies to:

PeopleSoft Enterprise HCM Human Resources - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

After a group is registered from the Group Build Feature, use the Refresh Groups run control page in order to run SCRTY_GB_REF App Engine, however, it runs to No Success with the following Error message captured in the Application Engine Message Log:

File: C:\PT860P07B_2306280500-retail\peopletools\src\psappeng\aedebug.hSQL error. Stmt #: 1851 Error Position: 0 Return: 8601 - [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Incorrect syntax near 'A'.
[Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Statement(s) could not be prepared. (SQLSTATE 42000) 8180
Failed SQL stmt: DELETE FROM PS_SCRTY_GBRES_TBL A WHERE NOT EXISTS ( SELECT 1 FROM PS_SCRTY_GBREG_TBL B WHERE A.GB_GROUP_ID = B.GB_GROUP_ID)

Process 1600292 ABENDED at Step SCRTY_GB_REF.MAIN.Step00 (SQL) -- RC = 8601 (108,524)

Process %s ABENDED at Step %s.%s.%s (Action %s) -- RC = %s

PSAESRV completed service request at 17.44.15 2024-01-17


Steps to replicate the issue:
1. Navigate to Set Up HCM > Common Definitions > Group Build > Group Build Definition > Group Profile: Create Group Build Query
First Record is GB_QRY_LINK_VW returning the four fields in this record.
2. Add a Security Access Type 47, Set Up HCM > Core Row Level Security > Security Access Type
3. Set Up HCM > Common Definitions > Group Build Definition: Create Group Build Definition
4. Set Up HCM > Common Definitions > Secure Group Build by Group
5. Set Up HCM > Common Definitions > Group Build Membership
6. Set Up HCM > Core Row Level Security > Security by Permission List
7. Set Up HCM > Core Row Level Security > Group Registration
8. Navigate to Set Up HCM > Core Row Level Security > Refresh Groups: Run the AE SCRTY_GB_REF runs to status “No Success” with the above Error Message.

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
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.