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 18.104.22.168 and 22.214.171.124. You must upgrade to 11g 126.96.36.199, 12c 188.8.131.52, 18c, or 19c 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.
If you have an application that uses DatabaseWriter to write to Cassandra, rewrite it to use CassandraWriter. This should require only changing the name of the writer from DatabaseWriter to CassandraWriter.
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.
GG Trail Reader can read metadata from GoldenGate trail files. See Change Data Capture (CDC) Guide > Oracle GoldenGate > GG Trail Reader properties for instructions on migrating the properties.
You may continue to use the FileReader + GG Trail Parser combination used in previous releases but it will not read metadata. GG Trail Parser will be deprecated in a future release. Please contact Striim support to plan a transition.File Reader + GG Trail Parser have been deprecated in favor of GG Trail Reader.
The default values for PubSubConfig have changed. The new values should avoid DEADLINE_EXCEEDED errors. Do not change these values unless instructed to by Striim support.
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.
The following previously reported known issues were fixed in release 3.10.1:
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
command denied to user.
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: use Excluded Tables to exclude the views.