The root cause of this problem might be defect/misconfiguration in the PRPC operating environment.and OS User running the application server does not have proper file permission to create/delete files in the file system. Can you check those and provide all the permission
Sorry for the late response! My team was trying some options to bring our environment back but unfortunately it is still an issue!
As you said "OS User running the application server does not have proper file permission to create/delete files in the file system" Can you help me to find the permissions of the os user on files please? Do we need to check the log files?
As per the logs, it indicates that the blob data corruption and hence PRPC is not starting up when it reads the data from the p4_* tables;
As per our suggestions on the SR-B56197, since you have a DB back up taken 2 weeks back. Kindly restore the same.
We are able to find the issue where the pr_data_admin table in our non-working environment Env 2 has the BLOB column showing a value of NULL for all 307 records. Just by restoring the single table we are able to bring the servers up.
But do you have any idea why the BLOB column become null.
Posted: 5 years ago
Posted: 27 Jun 2017 10:32 EDT
Basavaraj Kadakol (BASAVARAJ)
Senior Manager, Technical Support - Runtime Engine and Search