Striim® 4.0.4.3 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.
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
Sybase identity column support
See Enabling Database Writer support for identity columns in Sybase targets.
Oracle Reader's DDL support has been deprecated in favor of schema evolution
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.
New Halt state & alerts
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.
An in-place upgrade from Striim 3.x will delete all data persisted to Elasticsearch.
To preserve this data, use the export-import method instead. See Installation Guide >
Upgrading Striim > In-place upgrade.
BigQuery expects time-partitioned tables by default
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.
Oracle Reader transaction buffer defaults have changed
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.
Kafka SASL configuration has changed
Starting in Striim 4.0, SASL properties are specified in the Kafka Config property
of Kafka Reader and Kafka Writer. If you connect to a Kafka cluster that uses SASL, see
Installation and Configuration Guide > Configuring Kafka for details.
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 4.0.4.3:
- DEV-26220: BigQuery Writer connection retry issue
- DEV-27102: custom Java function load issue
- DEV-27153: custom Java function exception handling issue
- DEV-27272: Azure Synapse Writer: connection failure
- see notes for Connection Retry Policy in Striim 4.0.4 Documentation > Adapters Guide > Writers > Azure Synapse Writer
- DEV-27342: MS SQL Reader > Azure Synapse Reader "type mismatch or invalid character
for the specified codepage"
- DEV-27522: application crashes after upgrade to 4.0
Customer-reported issues fixed in release 4.0.4.2:
- DEV-25594: MS SQL Reader > Database Writer Sybase wrong mapping for money types
- DEV-27333: MS SQL Reader > Database Writer Sybase crash when updating identity column
- DEV-27347: MS SQL Reader > Database Writer Sybase crash on insert to table with an identity column that is not the primary key
- Edit or alter the Database Writer properties (see
ALTER and RECOPMPILE) and add the following
(if using Flow Designer, omit the quotes):
VendorConfiguration: 'EnableiDentityinsert=true;EnableiDentityupdate=true'
If a value for Vendor Configuration is already specified, add a semicolon to the end and
append EnableiDentityinsert=true;EnableiDentityupdate=true
.
- Create the checkpoint table in the target.
CREATE TABLE CHKPOINT (
id VARCHAR(100) PRIMARY KEY NOT NULL,
sourceposition IMAGE,
pendingddl NUMERIC,
ddl TEXT);
- Install the JTDS driver.
- Download
jtds-1.3.1-dist.zip
from
sourceforge.net/projects/jtds/files/jtds/1.3.1
and unzip it.
- Copy
jtds-1.3.1.jar
to the striim/lib
directory of every Striim server that will
write to Sybase and restart the servers (see
Starting and stopping Striim).
- Copy
jtds-1.3.1.jar
to the agent/lib
directory of every Striim Forwarding Agent that will
write to Sybase and restart the agents (see
Starting and stopping Striim).
Customer-reported issues fixed in release 4.0.4.1:
- DEV-25594: MS SQL Reader> Database Writer Sybase wrong mapping for money types
- DEV-27333: MS SQL Reader> Database Writer Sybase crash when updating identity column
- DEV-27347: MS SQL Reader> Database Writer Sybase crash on insert to table with an identity column that is not the primary key
Customer-reported issue fixed in release 4.0.4:
DEV-26406: MongoDB Writer crashes when target is Cosmos DB using the Azure Cosmos DB API
for MongoDB. This is supported by the new MongoDB Cosmos DB Writer.
Customer-reported issues fixed in release 4.0.3:
- DEV-21629: MS SQL Reader fails to start when tablename contains space and '$', as well as TransactionSupport=true
- DEV-21774: Oracle > Snowflake initial load: RAW value causes crash
- DEV-22010: Cannot drop admin.LDAP1 property set
- DEV-22534: MS SQL Reader: should exclude system table and views when wild card is used for TABLES
- DEV-22643: MySQL Reader > Cloud SQL for MySQL: mapping failed for Bit data type
- DEV-22964: MSSQL Reader > BigQuery Writer: mapping failed for Bit to Boolean
- DEV-23375: GG Trail Parser: if there is no new data to process, app hangs at RECOVERING_SOURCES state
- DEV-24146: Cannot drop component
- DEV-24462: App crashes with low disk space error when 34% free disk space
- DEV-24489: GG Trail Reader & Avro formatter: data type mismatch
- DEV-24497: cash not loaded
- DEV-24563: MON: "Could not initialize class com.webaction.runtime.monitor.MonitorModel" error
- DEV-24652: Database Reader with MariaDB: false "You have an error in your SQL syntax" error
- DEV-24733: Application takes too long to deploy/start/stop/undeploy/quiesce
- DEV-24999: File Reader > Kudu Writer: fails with "{[Ljava.lang.Object;} to TargetType {STRING(12)} is not supported for target" error
- DEV-25033: "Couldnot monitor table level metric since TableName donot exist in events metadata" in server log
- DEV-25238: MySQL Reader: fails with false "Unable to connect to the binlog file" error
- DEV-25240: SQL Server > Azure Blob Writer: crash with "Unknown datum type java.lang.Short" error
- DEV-25289: Kafka: cleartext SQSL password in logs
- DEV-25336: Azure Blob Writer with Parquet Formatter: fails with "Not in union ["null","long"]" error
- DEV-25380: Oracle Reader > PostgreSQL: fails with ":ERROR: "syntax error at end of input" error
- DEV-25451: KafkaReader: connection fails when using propertyvariable
- DEV-25452: REST API POST /tungsten: 'describe user' is not allowed for non-admin user
- DEV-25490: Oracle Reader: supplemental logging was not enabled, not caught by adapter
- DEV-25518: GG Trail Reader > Spanner: data missing in target after agent failover and switch back to original agent
- DEV-25526: MSS SQL Reader: does not preserve case of column names in type created
- DEV-25541: GG Trail Reader: View File LineAge missing from UI
- DEV-25694: Oracle Reader > Azure Synapse Writer: failed with false "Table not found" error
- DEV-25715: GG Trail Reader > BigQuery Writer: application in Stopping state for over 24 hours
- DEV-25775: End-to End Lag: incorrect unit label in web UI
- DEV-25796: Database Reader > Azure Blob Writer: excessive memory use, server shut down
- DEV-25816: Oracle Reader: gap in file sequence
- DEV-25824: End-to End Lag: not handling discarded events correctly
- DEV-25868: MySQL Reader: binlog connection issue
- DEV-25869: MariaDB > MySQL: "ClassCastException: java.lang.Integer cannot be cast to java.lang.Short" error
- DEV-25956: Oracle Reader: corrupt and trimmed CLOB data
- DEV-25957: Oracle Reader: crash with "Unable to enrich the following partial WAEvent" error/li>
- DEV-26017: LDAP configuration error cannot be resolved
- DEV-26151: MySQL Reader: starts from BinlogFileName although checkpoint position is higher
- DEV-26332: MS SQL Reader: bad numeric conversion
- DEV-26569: Oracle Reader: fails with "File seems to be missing for starting SCN" error
- DEV-26572: Database Reader MySQL > Database Writer MySQL: app in Starting status for up to 24 hours
- DEV-26582: MS SQL Reader > Azure Synapse: data type conversion error
- DEV-26779: Oracle Reader: crash with "Unable to enrich the following partial WAEvent" error/li>
Resolved issues
The following previously reported known issues were fixed in this release.
GRANT command wildcard does not work for objects (DEV-12146)
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.
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)
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.