Random Cache problems after project migration to a production environment
edited Dec 20, 2012 11:29AM in PeopleTools and Lifecycle Management - PSFT (MOSC) 9 commentsAnswered
Hi dear community members,
I have a situtation with a client. The client´s application is FSCM 8.9, PeopleTools 8.49.19.
The client usually Copy 30 or 40 projects from Test to Production per week. After that they (at random stages) get the known "Data Integrity Error" and cache versioning errors "PeopleCode program version chenaged in Component XXXX".
We solve the error purging cache files, sometimes we need to do it several times to fix the error. I believe its caused by the internal memory cache on the Domain processes.
Anyway, the question is why the problem arise for certain objects on certain projects and not for all the projects that are copied to production?. The problem is not shown for several weeks even when they continuosly move changes from TEST to production, and then after a month they get the erros and have to erase the cache for each project copied to production.
I have a situtation with a client. The client´s application is FSCM 8.9, PeopleTools 8.49.19.
The client usually Copy 30 or 40 projects from Test to Production per week. After that they (at random stages) get the known "Data Integrity Error" and cache versioning errors "PeopleCode program version chenaged in Component XXXX".
We solve the error purging cache files, sometimes we need to do it several times to fix the error. I believe its caused by the internal memory cache on the Domain processes.
Anyway, the question is why the problem arise for certain objects on certain projects and not for all the projects that are copied to production?. The problem is not shown for several weeks even when they continuosly move changes from TEST to production, and then after a month they get the erros and have to erase the cache for each project copied to production.
1