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 before installing or upgrading to Striim 3.8 or later.
Using Striim with MySQL requires the MySQL Connector/J JDBC driver 5.1.46. If you are using an earlier version, you must upgrade it. See "Installing the MySQL JDBC driver" in the Installation and Configuration Guide.
Striim 3.9 has been verified with Oracle JDBC driver ojdbc8.jar. If you are using an earlier version, remove it and install ojdbc8.jar. See "Installing the Oracle JDBC driver" in the Installation and Configuration Guide.
Oracle has ended patch fixes for Oracle 11g 220.127.116.11 and 18.104.22.168. You must upgrade to 11g 22.214.171.124 (or 12c 126.96.36.199) to use OracleReader with this release.
The web client has been tested on Chrome. Other web browsers should work, but if you encounter bugs, try Chrome.
Starting with 3.9.7, Striim includes a separate reader for MariaDB. If you have been using MySQLReader to read from MariaDB, we recommend switching to MariaDBReader.
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.
Starting with 3.9.7, the default value of Auto Disable Table CDC has been changed to False.
The following previously reported known issue has been 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.
MAP clause of
CREATE SOURCE ... OUTPUT TO is not
exposed in the UI, though it can be created with the App Wizard.
Workaround: in the console, use
DESCRIBE to view settings,
ALTER to change them.
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 query and
command denied to user.
Workaround: Use the console.
Commands such as
GRANT ALL ON * *.* TO ROLE ... will fail.
Workaround: leave out the object element, for example,
GRANT ALL ON *.* TO ROLE ....
IMPORT STATIC may fail. Workaround: use lowercase
Workaround: omit the source database name from SnowflakeWriter's Tables property.
For example, instead of