Previous Topic: Failover Does Not Work as Expected on Oracle RACNext Topic: Default Ruleset Not Created for an Organization That Was Created When RiskMinder was Down


Defects Fixed

This section contains the following topics:

No Support for Microsoft SQL Server Replication

RiskMinder Server Did Not Start Correctly If a Large Number of Organizations were Defined in the System

UNIX Installation Behavior Inconsistent in GUI Mode

Default Ruleset Not Created for an Organization That Was Created When RiskMinder was Down

Refreshing RiskMinder Resulted in Performance Issues

RiskMinder Occasionally Unable to Switch to Backup Database

Rule Mnemonic Length was Not Restricted to 25 Characters

Two Levels of Cache Refresh Required After Updating Default Organization Configuration

Filtering By Rule When Analyzing Transactions in Case Management Did Not Work for Microsoft SQL Server

Organizations Created Before RiskMinder Deployment Not Read by RiskMinder

Incoming Transactions Processed Even When the Server was Stopped

No Support for Microsoft SQL Server Replication

Symptom:

Microsoft SQL Server replication was not supported in earlier releases of RiskMinder.

Solution:

In this release, primary keys have been added in all tables to support database replication.

RiskMinder Server Did Not Start Correctly If a Large Number of Organizations were Defined in the System

Symptom:

RiskMinder Server did not start correctly if there were more than 100 organizations defined in the system.

Solution:

This issue has now been resolved.

UNIX Installation Behavior Inconsistent in GUI Mode

Symptom:

In the earlier releases, GUI mode was enabled as the default mode of installation. As GUI installation is not supported in Linux or Solaris, the UNIX installation experience was not consistent.

Solution:

The GUI mode is not available in the Linux and Solaris installers any more.