Installing TRIRIGA 3.4.2 or 3.5.0 on a non-US English database


Disclaimer: TRIRIGA encourages using the latest platform release when installing new TRIRIGA databases. This ensures that you have the latest platform with fixes to known issues. However, if you need to stay at 3.4.2.x or 3.5.0.x and are installing into a non-US English database, review the following as you might encounter issues.

An issue has been found during the create table and/or use of the REP_TEMPLATE_HDR table when using a non-US English database. How the issue exposes itself and how to resolve it are dependent on the database type you are using. See the following instructions for how to resolve this issue for 3.4.2.x or 3.5.0.x.

Oracle Database

On a non-US English database, you might not be able to install. You might see an exception similar to following in your ant.log file although the words in red will be in the language of the Oracle server. The SQLDataException will be ORA-01858…

Microsoft SQL Server Database

On a non-US English database, you should not run into the database installation issue encountered by Oracle, but you might get an exception when creating a new report or query or possibly when starting up your application server. If the exception looks similar to the following example, follow the steps below to resolve the issue… The exception in red will be in the server language. The English translation is approximately “Failed to convert the date and / or time from a string”…

IBM DB2 Database

IBM was unable to reproduce the issues in an IBM DB2 non-US English database. However, if you do encounter issues, follow these steps…

Continue reading

2 thoughts on “Installing TRIRIGA 3.4.2 or 3.5.0 on a non-US English database

  1. Pingback: Installing TRIRIGA 3.4.2 on Microsoft SQL Server database | TRIRIGAFEEDIA

  2. Pingback: IV86058: Cannot save report if on non-English SQL Server database | TRIRIGAFEEDIA

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s