Multi-byte characters are saved incorrectly in DPA

10/22/2018 10:56 AM

10/22/2018 10:56 AM

You entered and saved multi-byte characters, but the characters display incorrectly when you re-access DPA.

Database Performance Analyzer

By default, DPA does not support special characters using a specific character set such as multi-byte, double-byte, and so on. Generally this happens when the DPA repository is set to a single-byte character set, but the monitored instance is set to a multi-byte character set. Java can handle this correctly, but when trying to insert the multi-byte character set into the repository, it will usually fail.

In order to support a multi-byte language, the DPA server, repository, and monitored instances must be configured with the same character set.

Use the following steps to change that default behavior to support single-, double-, or triple-byte. DPA does not support four-byte character sets.

These steps include recreating the repository database. You will lose your historical data.

1. In the operating system settings on the DPA server, change the Language and Region settings to the language with the same character set.
2. Make sure that your system supports the appropriate fonts.
3. In your DPA database repository, change the default language to match the operating system language.
4. Stop the DPA service.
   • Windows: Stop the Ignite PI Server service.
   • UNIX or Linux: Run installDir\shutdown.sh.
5. Go to the following directory on the DPA server:

   installDir\iwc\tomcat\ignite_config\idc

6. Open the system.properties file, and edit the following property by deleting the number sign (#) and setting to true:

   com.confio.doublebyte=true

7. Open the repo.properties file, and edit the following property by setting to no:

   repo.created=no

8. Save and close both files.
9. Start the DPA service.
   • Windows: Start the Ignite PI Server service.
   • UNIX or Linux: Run installDir\startup.sh.
10. Access DPA in a browser, and create the database repository again.