Striim® 3.9.8 release notes
For evaluating Striim:
- memory: minimum 4 GB for use by Striim (so the system should have at least 5GB,
preferably 8GB or more)
- free disk space: minimum 10 GB, 20 GB recommended
- operating system:
- for evaluation, development, and production (if you need to run Striim on another operating system or version,
please contact Striim support):
64-bit CentOS 6.7 through 7.6,
64-bit Ubuntu 14.04, 16.04, or 18.04,
64-bit Windows Server 2012
- for evaluation and development only: Mac OS X 10, Windows 8.1 or 10
- 64-bit Oracle Java SE JDK 8 (recommended) or 64-bit OpenJDK 8
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 188.8.131.52 and 184.108.40.206. You must upgrade to
11g 220.127.116.11 (or 12c 18.104.22.168) 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.
Changes that may require modification of your TQL code, workflow, or environment
Writing to Cosmos DB using the Cassandra API
If you have an application that uses DatabaseWriter to write to Cosmos DB using the
Cassandra API, rewrite it to use Cassandra Cosmos DB Writer.
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.
Changes to MSSQLReader properties
Starting with 3.9.7, the default value of Auto Disable Table CDC has been changed
SQL Server JDBC drivers
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.
Customer-reported issues fixed in this release:
- DEV-17104: issue with special characters in column name
- DEV-18431: memory not released
- DEV-18492: crash with unknown exception
- DEV-18680: incorrect status information system heath REST API
- DEV-18681: application alert not working
- DEV-18785: deployment issue
- DEV-18925: SMTP authentication issue
- DEV-18935: directory indexing issue
- DEV-18936: security issue
- DEV-18964: invalid date format with OracleReader
- DEV-19113: exported TQL missing type fields
- DEV-19140: metadata repository issue with Oracle host
- DEV-19205: recovery hangs
- DEV-19212: failure sending HELO command to SMTP server)
- DEV-19222: app does not fail when MySQL is down
- DEV-19288: CPU alert issue
- DEV-19395: ADLSGen2Writer rollover issue
- DEV-19422: alert has wrong application status
- DEV-19477: Open Cursor limit has reached in the target database
- DEV-19482: DatabaseWriter issue
- DEV-19540: java.lang.NumberFormatException: Zero length BigInteger
- DEV-19564: SpannerWriter issue
- DEV-19593: GGTrailParser documentation isue
- DEV-19622: DBReader (Oracle source) to BigQuery - crashed
- DEV-19686: Docker image has expired license
- DEV-19701: SpannerWriter does not crash when target table does not exist
- DEV-19707: app is not checkpointing
- DEV-19751: server heap issues
- DEV-19775: treating MONTH as Ccse-sensitive causing "DateTimeParseException"
- DEV-19864: app not checkpointing when GoldenGate trail has no DML
- DEV-19892: event rate from REST Health API is wrong
- DEV-20011: "com.striim.specialColumnTypes.SpecialColumnTypeHandler.getReplacedUpdateSQLRedo (SpecialColumnTypeHandler.java)" errors
- DEV-20074: 22.214.171.124 Forwarding Agent missing MSSQLReader JAR
The following previously reported known issues have been fixed in this release.
- MySQLReader DDL CREATE and DROP operations not emitted (DEV-18004)
- Authentication failure with Java event publishing API when httpEnabled=False (DEV-19281)
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.
HTTPReader is missing the Parser menu in the UI (DEV-1854)
Workaround: Use the console or import TQL.
MAP settings are not exposed in the UI (DEV-4138)
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.
WActionStore silently discards events with null value for event type key (DEV-5599)
Creating a source using HTTPReader and DSVParser fails with error (DEV-5916)
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"...
Dashboard queries not dropped with the dashboard or overwritten on import (DEV-6068)
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.
SORTER objects do not appear in the UI (DEV-8142)
DatabaseWriter shows no error in UI when MySQL credentials are incorrect (DEV-8933)
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.
DatabaseWriter needs separate checkpoint table for each node when deployed on multiple nodes (DEV-11305)
Flow Designer is unresponsive when a type has a very large number of fields (DEV-11898)
Workaround: Use the console.
GRANT command wildcard does not work for objects (DEV-12146)
Commands such as
GRANT ALL ON * *.* TO ROLE ... will fail.
Workaround: leave out the object element, for example,
GRANT ALL ON *.* TO ROLE ....
Import of custom Java function fails (DEV-17653)
IMPORT STATIC may fail. Workaround: use lowercase
SnowflakeWriter drops events from MSSQLReader sources (DEV-19058)
Workaround: omit the source database name from SnowflakeWriter's Tables property.
For example, instead of
When DatabaseReader Tables property uses wildcard, views are also read (DEV-19903)
Workaround: use Excluded Tables to exclude the views.