My Oracle Support Banner

E-PG: Unable To Access The Underlying Query Datasource. (268,54) PT_PGPACKAGE.PT_PGInformation.OnExecute (Doc ID 2753299.1)

Last updated on FEBRUARY 23, 2021

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.57 and later
Information in this document applies to any platform.

Symptoms

The issue is that in production Pivot Grid viewer and using AR_DB_CUST_AGING works fine until filters are used.
 
From application server log:

Unable to access the underlying Query Datasource. (268,54)
PT_PGPACKAGE.PT_PGInformation.OnExecute Name:InitializeFromDB PCPC:3219
Statement:119
Called from:PTPG_API.Model.OnExecute Name:Model Statement:50
Called from:PTS_SEARCH.PivotGridSearch.OnExecute Name:Initiate Statement:109
Called from:PTPG_NUI_VWR.Activate Statement:144
...
PSAPPSRV.26788 (424) [2021-02-03T16:26:16.773 d$sskalka@localhost (CHROME 88.0.4324.104; WIN10) ICPanel] Eq7ds9IPiFw/bw 4362836054224209921 d$sskalka (0) PeopleCode program version changed in component PTPG_NUI. Max version was 1, now 280
PSAPPSRV.26788 (424) [2021-02-03T16:26:16.774 d$sskalka@localhost (CHROME 88.0.4324.104; WIN10) ICPanel] Eq7ds9IPiFw/bw 4362836054224209921 d$sskalka (0) Data Integrity Error (124,85)
PSAPPSRV.26788 (424) [2021-02-03T16:26:19.361 d$sskalka@localhost (CHROME 88.0.4324.104; WIN10) ICPanel] Eq7ds9IPiFw/bw 4362836054224209921 d$sskalka (0) Unable to access the datasource for the model
PSAPPSRV.26788 (424) [2021-02-03T16:26:19.361 d$sskalka@localhost (CHROME 88.0.4324.104; WIN10) ICPanel] Eq7ds9IPiFw/bw 4362836054224209921 d$sskalka (0) Error while loading datasource definition for the model
PSAPPSRV.26788 (427) [2021-02-03T16:26:27.705 GetCertificate] fMuxam5vRJQRxw 7265334861750739969 - (0) Ignoring UPM signon statement

It is some type of data corruption with PTPG_NUI_VWR and with component PTPG_NUI.

Error can be created by running a Pivot Grid via Pivot Grid Wizard. Navigation => Reporting Tools > Pivot Grid > Pivot Grid Wizard.

 

Changes

 It was reported that an Object FUNCLIB_PORTAL was migrated to production the day that the issue started and the version of this object was 16247 which was customized with a workaround from Oracle for a separate issue in ePro.

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


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