For evaluating Striim:
A production environment will require more memory and disk space.
Java SE JDK 7 and OpenJDK 7 are no longer supported. You must upgrade to version 8.
The web client has been tested on Chrome. Other web browsers should work, but if you encounter bugs, try Chrome.
See Enabling Database Writer support for identity columns in Sybase targets.
The DDL support docuemnted in Including DDL operations in Oracle Reader output has been deprecated in this release. Applications created in earlier releases that use this feature are still supported but schema evolution cannot be enabled for those applications and reating new applications is not supported. Oracle Reader's DDL Capture Mode property does not appear in the UI.
If you wish to migrate from the old feature to schema evolution, you must create a new application.
The new HALT status indicates that an application failure is due to an external cause, such as a source or target database being offline. If you have any alerts on application Crash, you should create additional alerts for Halt. For more in formation, see Administrator's Guide > Sending alerts about servers and applications.
To preserve this data, use the export-import method instead. See Installation Guide > Upgrading Striim > In-place upgrade.
By default, starting in 4.0, BigQuery expects target tables to be partitioned by ingestion time or DATE, DATETIME, or TIMESTAMP columns. See Adapters Guide > Writers > BigQuery Writer > Improving performance by partitioning BigQuery tables.
By default, Oracle Reader now automatically buffers transactions larger than 100MB to disk. See Change Data Capture (CDC) Guide > Oracle Database > Oracle Reader properties > Change Transaction Buffer Type.
SQL Server 2008 requires an older version of Microsoft's JDBC driver that is not compatible with the most recent SQL Server versions. See the Installation and Configuration Guide > Configuring Striim > Insalling third-party drivers > Installing the Microsoft JDBC driver for more information.
No previously reported known issues were fixed in this release.
The following issues have been identified but not yet fixed as of this release. Additional known issues are mentioned in the relevant topics in the documentation.
Workaround: Use the console or import TQL.
Workaround: Have the sender include type=dsv in the URI. For example:
curl -X POST "http://192.168.1.107:9090?type=dsv&charset=utf-8"...
When you drop a dashboard, its queries are not dropped. If you drop and re-import a dashboard, the queries in the JSON file do not overwrite those already in Striim.
Workaround: drop the namespace.
If your DatabaseWriter Username or Password values are correct, you will see no error
in the UI but no data will be written to MySQL. You will see errors in
webaction.server.log regarding DatabaseWriter containing
Failure in Processing
command denied to user.
IMPORT STATIC may fail. Workaround: use lowercase
Workaround: use Excluded Tables to exclude the views.