Question
Nordea
SE
Last activity: 5 Jun 2019 3:32 EDT
Pega Search Index Unavailable for 8.1.1
Hi,
We have upgraded our application from Pega 7.2.2 to 8.1.1. We have noticed that search is not working and it seems Rule & Data index got corrupted. Please see the attached screenshot for more details.
We checked upgrade guide (https://community.pega.com/knowledgebase/documents/pega-platform-81-upgrade-guide-ibm-websphere-and-oracle) and it's clearly mentioned that we do not need to do anything related to elastic search we are upgrading from 7.2.2. Please see the attached screenshot of Upgrade guide as well
***Edited by Moderator Marissa to update SR Details***
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Accepted Solution
Nordea
SE
Hi,
It seems the search index got corrupted. I have sorted it out by deleting pega search index in temp directory and after the server restart, it works. I will ask GCS guys to note down the solution and close the SR.
Pegasystems Inc.
IN
Can you please check how many records you have in table pr_sys_statusnodes
Nordea
SE
I could see only one record. Attached is the export file from database
Pegasystems Inc.
IN
I suggest you raise Product SR to have this investigated.
Updated: 14 Jan 2019 10:44 EST
Nordea
SE
Raised SR-C85255
Pegasystems Inc.
US
Thanks @AnandP! I updated the Support Request with this PSC link and our Support Engineers have reached out that they'll be working this moving forward.
Please let us know the outcome so that we may update this thread to help others who may have the same question.
Accepted Solution
Nordea
SE
Hi,
It seems the search index got corrupted. I have sorted it out by deleting pega search index in temp directory and after the server restart, it works. I will ask GCS guys to note down the solution and close the SR.
EY
GB
Hi, have the resolution steps been documented for this? We are experiencing a similar issue (albeit not after an upgrade, we were always on v8) and simply clicking re-index does not return any results.
Murex
LB
Hello,
I solved it by going to the admin studio --> API --> and then cleaning the ABA cache and every possible cache that can be cleared
Hope it helps
tx