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

Search functionality not working due to ORA-04030 error

SA-5311
SUMMARY

Users were not able to search any work objects even through System Indexer and System Work Indexer were configured and running only on the indexing server. Users have System Pulse running in all the three JVMs.

ERROR MESSAGES

[  STANDARD] [Demo:03.15] (  async.agent.QueueManagerImpl) ERROR   - Problem with browse of System-Queue-ExecutionRequest-Connect-Default
com.pega.pegarules.pub.database.ConnectionException: There was a problem getting a list: code: 4030 SQLState: 61000 Message: ORA-04030: out of process memory when trying to allocate 8528 bytes (pga heap,kgh stack)
ORA-06512: at "PEGA_ADMIN.SPPR_SYS_RESERVEQUEUEITEM_B", line 127
ORA-06512: at line 1

STEPS TO REPRODUCE

In a multi-node environment, work object search functionality was not working.

ROOT CAUSE


During investigations, following observations were made -
 1. SPPR_SYS_RESERVEQUEUEITEM_B Stored Procedure which is used by agent to retrieve data from the PR_SYS_WORKINDEXER_QUEUE table as soon as a record gets processed from the table their entry will be removed from the it. In this case, this Stored Procedure was failing and system was not able to index any Work-Objects further.
 
 2. Root cause of Stored Procedure failue was the Oracle error (ORA-04030 - memory issues while trying to perform Database operations).

RESOLUTION

Suggested user to tune Oracle memory using SGA parameters which has helped resolve the issue.
Suggest Edit

Published January 31, 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