we are using one server for development and another servers, for testing, integeration and production. All installed with Pega 7.1.9 and equal HF, we are using Oracle DB and WebSphere. The stages for dev, testing and production are using NLS_LENGTH_SEMANTICS "CHAR", the stage T is using "BYTE". See attachement pyClassNameOnStageE/T.
Is it possible, that we run into problems? It seems that all VARCHAR2-Columns have different lengths?
dbVisualizer displays the following different column length:
Here are the database parameters (identical on all stages!):
You might have problems if the pyClassname exceeds the 64 bytes. On the other hand I am surprised to see different column size on Test environment only. It might be due to installation procedure since one can set the NLS_LENGTH_SEMANTICS at session level during installation.
thanks. I'am wondering how this could happen.Last Friday we had problems during deployment. The column pyDescription on PR4_RULE_FLOW was too short. I'am increasing the column length to make the deployment possible.
To be on the safe-side: re-install? I fear, that it's possible, that we are running into problems when we install Pega HF, Updates or running into problems with deployment.