SA-25424

SUMMARY Following a migration of our system from one database to another; we are experiencing various problems, in particular:

• Corruption of text on screen (for instance ‘username’, ‘password’ on login form).
• Corruption of some Designer Studio Menus (for instance Resources | Profile).
• Errors when using testing Class to Database Mappings from Designer Studio (and in other places in the UI).
• Some menu UI components (for instance Tree View in Designer Studio) don’t function without forcibly refreshing the browser.

Error Messages

Examples of corrupt text:

Example of Corrupt Menus in Designer Studio:

Example of Class Mapping Error:

Class *P1 bad parameter!* is mapped to table *P3 bad parameter!* in database *P2 bad parameter!*, which has column *P4 bad parameter!* of unsupported type *P5 bad parameter!*

STEPS TO REPRODUCE
Not Applicable.
ROOT CAUSE Running a Fiddler revealed that even text which appeared not to be corrupt on the screen, is in fact corrupt also (it appears to be ‘double-spaced’ : in fact further inspection showed that the characters within the text were interleaved with ASCII NUL (00) characters; like this:




The table ‘PR4_FIELDVALUE’ contains the column ‘pylocalizedvalue’ which is of type CLOB.
Running the following SQL showed that the source of the corruption was in the data in this column:

SELECT pylocalizedvalue
FROM pr4_fieldvalue
WHERE pzinskey LIKE 'RULE-OBJ-FIELDVALUE @BASECLASS PYCAPTION!COPYRIGHT%'


The pzinskey above corresponds to the ‘Copyright’ text that is shown (not visibly corrupt in fact) on the Login Screen:



The result of the SQL showed the corruption in the Column:


RESOLUTION
The Migration process included a change to the Database Characterset; this should not have been done.

The Migration process was repeated without this change to the Database Characterset; all the issues seen above are eliminated.