After upgrading to PeopleTools 8.54, you may notice that the SES index crawl process keeps running at a scheduled time and fails with the below error. Interesting thing is that you’re likely to find this error in all the applications that have been upgraded to 8.54 irrespective of the fact whether or not it is a 9.1 […]
Continue readingIf you have deployed an index and crawled it, say PTPORTALREGISTRY – when you run a search against it, you receive an error like “No results were returned. Refine your search by entering a different keyword” Go to <SES Home>/logs/crawler/crawler and check the logs. You need to view the log, which has the name like search.crawler.i1ds*.mmdd* […]
Continue readingMonday mornings are usually not great because apart from the weekend being over, there is always something that won’t work and it is usually due to weekend maintenance/upgrade work. Today I found all my SES index jobs showing the same error as shown below: Integration Broker encountered an error (262,1020) PT_SEARCH.SESIMPL.MESSAGE.SESRequest.OnExecute N ame:Send PCPC:688 Statement:16 […]
Continue readingThere are certain scenarios in which you’d like to have a list of PeopleSoft SES tables handy. Some of these scenarios include: PeopleSoft instance/database refresh – When copying a PeopleSoft instance or database, for example – production to test, you may want to exclude the SES tables so that SES server details and index definitions […]
Continue readingThis error usually comes after a database refresh has happened. Root cause of the error is that the application database and the SES database have gone out of sync. The error show up when you try to undeploy a SES index and when you try to do “Report Sync Issue,” nothing happens. The error reads […]
Continue reading