Alcatel Security Management Server (SMS) Release 9.4 Guide d'installation télécharger pdf (Page 51)

Known Issues

Chapter 5: Internationalization and Localization 51

Known Issues

Spectrum Report Manager Database Upgrade

Environment: Windows, Linux, and Solaris

Symptom:

Report Manager database conversion to UTF-8 fails when there are special characters

that are not part of UTF-8 character set. The conversion process stops at the first

occurrence of such special character, and "SchemaChangeException" is logged in the

"stdout.log" (in Windows) and "catlina.out" (in Linux and Solaris) log file.

This issue occurs only during upgrades or migrations from 9.2.2, 9.2.2 H09, 9.2.3, 9.2.3

H11, and 9.2.3 H12.

Solution:

Check the "stdout.log" (in Windows) and "catlina.out" (in Linux and Solaris) log file to

know which database, table, and record number contains that special character. The log

file has all such details. Remove that entry and restart the Tomcat service. The Report

Manager conversion process starts again.

Example

If the log file shows that row 172 of the reporting.event table has a special character as

shown in the following log:

2014-06-17 12:20:53,732 ERROR

com.aprisma.spectrum.app.web.db.schemachange.SchemaChangeUpdater - Error

occurred while applying schema change

Name: 1300 (Product version: 9.3.0) - Conversion of table 'reporting.event' to

InnoDB and UTF-8

Incorrect string value: '\xDE\x06\x0C\x07\x154' for column 'event_msg' at row 172

In this case, remove the entry at row 172 and restart the Tomcat service to start the

conversion process again.

Note: For every occurrence of such special character, see the log file for exact details

and remove that invalid entry from the database and restart the Tomcat.

1 2 ... 46 47 48 49 50 51 52 53

Pas de commentaire

Alcatel Security Management Server (SMS) Release 9.4 Guide d'installation Page 51