Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Exception occuring when AES queries PEGA0005 alert index



Pega administrator is seeing exceptions in the logs releated to PegaAESRemote

Error Messages

2014-07-25 08:07:46,659 [ http-8080-8] [ STANDARD] [ ] [ PegaRULES:07.10] (l.access.ConnectionManagerImpl) ERROR |HOST|SOAP|PegaAESRemote|IndexInfo|GetIndexInfo|A622F9631B061A79DA5225ACD0BA92D63 - Not returning connection 2461858 for database "pegadata" to the pool as it previously encountered the following error
User ID: (unknown)
org.postgresql.util.PSQLException: ERROR: syntax error at or near "{"
Position: 1
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(
at org.postgresql.core.v3.QueryExecutorImpl.processResults(
at org.postgresql.core.v3.QueryExecutorImpl.execute(
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(

Steps to Reproduce

7.1 AES monitoring on Pega 7.1.5

Root Cause

In  a split schema environment, SPPR_POPULATE_INDEX_DATA stored procedure operates on AES related table PR_INDEX_INFO and is used to get index information. This stored procedure would not work with split schema because the stored procedure is not in the same schema the request is run in. This issue only causes an exception in the log periodically when AES asks for index info.
Stored procedure is not in the same schema because it is not qualified with the schema name and at this moment there is no API support from AES standpoint to schema qualify stored procedure.


HFIX-9781 was provided where
PegaAESRemote does not attempt the call to the stored procedure causing the exception.
Suggest Edit

Published March 14, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us