Striim® 3.10.1.1 release notes
Requirements
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 11.2.0.3 and 11.2.0.3. You must upgrade to
11g 11.2.0.4, 12c 12.1.0.2, 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.
Changes that may require modification of your TQL code, workflow, or environment
Writing to Cassandra
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.
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.
Reading from Oracle GoldenGate
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.
Google PubSub Writer default property change in 3.9.8.3
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 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 release 3.10.1.1:
- DEV-22048: Import of exported application fails
- DEV-22212: Unsupported adapters appear in Flow Designer
- DEV-22228: GGTrailParser crash
- DEV-22236: GGTrailParser does not send transaction boundaries properly
- DEV-22246: GGTrailParser "Preview on run" errors
- DEV-22249: OracleReader error with 19c
- DEV-22278: BigQueryWriter error with single quote in string
- DEV-22284: Azure Synaps Writer failed when writing more than 10000 Characters to VARCHAR(MAX)
- DEV-22295: High CPU and load average after upgrading to 3.10.1
- DEV-22306: OracleReader hangs
- DEV-22319: External cache issue
- DEV-22331: OracleReader issues with RAC source
- DEV-22334: BigQueryWriter error with LF or CR in string
- DEV-22353: OracleReader does not crash when log is missing
- DEV-22362: Can't change log level
- DEV-22375: OracleReader: some deletes missing in BigQueryWriter target
- DEV-22384: GGTrailParser fails on DDL operation
- DEV-22407: BigQueryWriter: striim.server.log flooded with multiple error messages
- DEV-22410: OracleReader does not crash when log is missing
- DEV-22425: Open processor will not load
- DEV-22545: BigQueryWriter: Striim server crashes
- DEV-22626: BigQueryWriter: checkpoint issue
- DEV-22687: Striim server out of memory errors
Customer-reported issues fixed in release 3.10.1:
- DEV-10820: Oracle Reader startup delay when many tables
- DEV-12023: can't get WActionStore data with REST API
- DEV-16867: file lineage not available for source deployed on Forwarding Agent
- DEV-20557: system health REST API missing some information
- DEV-20929: monitoring: CPU usage value does not match graph
- DEV-21049: MSSQL Reader does not stop and app crashes
- DEV-21064: undocumented: when OracleReader is running, PDB must not be closed
- DEV-21173: BiqQuery Reader crash
- DEV-21209: derbyTool.sh issue
- DEV-21268: memory leak
- DEV-21255: Oracle Reader stops capturing events
- DEV-21326: can't configure debug logs
- DEV-21391: Oracle Reader crashes with ORA-01289 error
- DEV-21413: MetadataRepository.patchPasswordSalts errors at startup
- DEV-21415: Forwarding Agent connection to Google Cloud Platform fails after upgrading to 3.9.8
- DEV-21447: Oracle Reader to BigQuery Writer fails in MERGE mode with
- DEV-21456: some apps are invalid after export and import using tools.sh
- DEV-21482: KafkaReader with XMLparserV2 stops reading data
- DEV-21553: Forwarding Agent does not restart after Windows host is restarted
- DEV-21622: PostgreSQL Reader to BigQuery Writer stops sending data
- DEV-21628: BigQuery Writer fails with false "table not found" error
- DEV-21766: same as DEV-21268
- DEV-21787: Kafka Writer issue with SASL_SSL
- DEV-21804: memory leak
- DEV-21877: Oracle Reader to BigQuery Writer crashes after upgrading to 3.9.8
Resolved issues
The following previously reported known issues were fixed in release 3.10.1:
SnowflakeWriter drops events from MSSQLReader sources (DEV-19058)
After upgrad, applications that use property variables crash (DEV-21263)
Known issues
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)
The 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)
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 import static
.
When DatabaseReader Tables property uses wildcard, views are also read (DEV-19903)
Workaround: use Excluded Tables to exclude the views.