Find Answers

Filter Search Results

Ask a Question

Example: "Database could not be verified"

Pages [Next]

Results

EM_* tables are not correctly upgraded for Oracle on and then deploy of Event Map fails

Errors similar to below may occur in your server.log at JBOSS startup: 2013-02-11 11:07:11,131 ERROR [main] [com.serena.em.ds.dao.db.HibernateSessionFactory] [::] -- Failed to parse event map. Error: Invalid byte 2 of 3-byte UTF-8 sequence. org.xml.sax.SAXParseException: Invalid byte 2 of 3-byte UTF-8 sequence.

5.7.2.26 - File containing UTF8 characters without BOM increment version with no change

Unicode characters do not appear in the editable grid.

DimCM: GREP command doesn't work properly with UTF-8 encoded files

Unicode Upgrade Utility does not support Oracle 11 client

Running the Unicode Upgrade Utility while upgrading from TeamTrack 6.6.1 to Serena Business Mashups 2009 R1 in combination with Oracle 11g may result in the following error: Connecting to database. Oracle database client must be 9i or 10g.

Dim RM 2009 R2: dbDoctor does not handle UTF8 character set

The recommended character set for RM is AL32UTF8 . However, when you run dbDoctor and examine the database you get: -

Dim RM: XLS export feature doesn't work properly if you import requirements using UTF-8 CSV Import

Search for High ASCII does not work when configured for UTF-8 and Oracle on Windows

When TeamTrack is required to work with multiple character sets their TT database must configure be configured for UTF-8 . With Oracle it is also a requirement for the NLS_LANG parameter to be set on the client to that of the database character set so that the data is correctly written to the database e.g. AL32UTF8.

Knowledgebase

Find Answers

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance