Whats in the SPS Database Encoding Patch ?
The Problem: When SPS version 6.0 installers were released, the Master Server installs a version of PostgreSQL database. However due to behavioral changes of Postgres installations, the default encoding with which the database gets created and initialized inherits the encoding settings configured on the system’s locale and in most installations, the PostgreSQL database encoding ended up being SQL_ASCII. On the other hand, SPS 5.2 was by default using UTF-8 as the default encoding regardless of the system locale. The behavior exhibited by 5.2 is desirable and customers using extended ASCII character data have exploited this behavior. As a result the migration process from SPS version 5.2 to 6.0 is impacted. Due to this encoding mismatch between the source and destination databases, there is data loss and corruption during migration. The Solution: In order to fix the above-mentioned problem, customers have to install the database encoding patch. On Solaris, separate patched ID:138996-02(
Related Questions
- I need to upgrade the database and apply a patchset and/or a Critical Patch Update (CPU) after the upgrade. What is the best way to accomplish this?
- How can I tell whether a satellite network in the SPS database is in the Plan, in the List, or is a pending Article 4 network?
- How can i change database encoding for a PostgreSQL database using sql or phpPgAdmin?
