- What is the user doing, when this exception in the logs in noticed?

- Do you see any corresponding errors on the UI side as well? If yes, can you please provide a screen shot of

the same.

- Does this issue happen every time you do the same thing or is it sporadic?

- From the logs you provided I see the below exception:

2015-03-12 01:59:09,469 [fault (self-tuning)'] [TABTHREAD0] [ PRIME:01.44.01] (

internal.access.DatabaseImpl) ERROR pg-qaapp4|hn-p01-h7-0227.hncorp.healthnet.com Triager - There was a

problem with the database when getting a list:

com.pega.pegarules.pub.database.DatabaseException: There was a database problem when performing an

RDBExecute: code: 12592 SQLState: 66000 Message: ORA-12592: TNS:bad packet

From: (unknown)

SQL: SELECT Count(CASE WHEN ( "PC0".PXGOALEXECUTE IS NULL ) THEN 1 ELSE NULL END) AS

"pySummaryCount(1)" , Count(CASE WHEN ( "PC0".PXGOALEXECUTE IS NOT NULL AND

"PC0".PXDEADLINEEXECUTE IS NULL ) THEN 1 ELSE NULL END) AS "pySummaryCount(2)" , Count

("PC0".PXDEADLINEEXECUTE) AS "pySummaryCount(3)" , count(*) AS "pySummaryCount(4)" ,

"PC0".PXASSIGNEDOPERATORID AS "pxAssignedOperatorID" FROM pc_assign_worklist "PC0" JOIN

pr_operators "Operator" ON "PC0".PXASSIGNEDOPERATORID = "Operator".PYUSERIDENTIFIER AND

( "Operator".PYWORKGROUP = ? ) JOIN PRIME_CASE_VIEW "WO" ON "WO".PYID =

"PC0".PXREFOBJECTINSNAME WHERE ( "PC0".PXASSIGNEDOPERATORID LIKE ? ) AND (

"PC0".pxObjClass = ? ) AND "Operator".pxObjClass LIKE ? GROUP BY "PC0".PXASSIGNEDOPERATORID

ORDER BY count(*) DESC , "PC0".PXASSIGNEDOPERATORID

SQL Inserts: <PrimeOps> <%Triager%> <Assign-Worklist> <Data-Admin-Operator-ID>

Caused by SQL Problems.

Problem #1, SQLState 66000, Error code 12592: java.sql.SQLException: ORA-12592: TNS:bad packet

- Try the above query directly on the database (with help of DBAs) to see if error is replicated.

- Do you have any external databases from which the query gets the info (using DB links)?

-

- Generally, such error is caused due to some database connectivity issue (maybe the network, maybe Oracle).

Have you contacted Oracle Support yet for this issue? The error is actually an Oracle error, so it is

recommended to engage Oracle Support to get to the root cause of it. PRPC is just a client executing the SQL to

the database in this scenario.