PRPC restricts property optimization on class mapped to external db because external db does not have a blob column from where a column needs to be exposed. The property are already an exposed column in an external db.
Thanks for the details. Issue had been fixed. Yes, we have various way of exposing the properties from the Pega and database respectively.
Failed to initialize Property Optimization from Pega. Core reason could be security setting. Means developers are restricted to expose property from Pega.
But issues which we observer was different in our context.
As part of the deployment activities,. The DDL script that had been executed manually from the database side and script that are generated during the import is not in sync. Root cause: Case sensitive issue with Table and column names respectively. Due to this exposing of properties had failed for particular class and property.