Live Datamart Known Limitations

This section describes known limitations in the current release of TIBCO® Live Datamart and TIBCO LiveView™ Desktop. Each item includes a tracking number, description, and whenever possible, one or more workarounds.

CQS‑4641 Issuing queries with literal non-printing characters is not supported in query strings.
Description Query strings with literal non-printing characters can cause issues. Non-printing characters are those below 0x20, excepting tab, carriage return, and line feed. Note that tables and query result sets are free to have any characters as values.
Workaround Instead use StreamBase Unicode escape sequences, which looks like \uXXXX. For example, a bell is \u0007.
CQS‑4467 An aggregate query with HAVING clause and LIMIT specified may throw "Query updates exceeded specified limit" when the number of rows returned are less than the specified LIMIT.
Description When issuing an aggregate query with a HAVING clause and LIMIT applied, returned rows may be less that the specified LIMIT (even none). This is because LIMIT is applied to the rows returned before the HAVING predicate filter.
Workaround If the HAVING predicate is expected to filter a large number of rows, use a very large LIMIT or no LIMIT. For non-aggregate queries with a HAVING and LIMIT, the number of rows you get before getting a "Query updates exceeded specified limit" is appropriate.
CQS‑3855 Remote data source tables with sole primary key "CQSInternalID" cannot be opened.
Description When querying a remote data source's tables, all LiveView clients fail to open any remote table that uses a single primary key named CQSInternalID.

This issue affects all LiveView clients, including TIBCO LiveView Desktop, TIBCO LiveView Web, the lv-client command line utility, and any custom client written using LiveView Client APIs.

The issue occurs when querying any remote data source, including: TIBCO StreamBase Query Tables, other LiveView servers, JDBC databases, TIBCO ActiveSpaces tables, and custom table providers.

Workaround You can use one of the following suggestions to enumerate the remote tables that you must avoid. 1. If your client can sort its list of available remote tables, sort it by the Indexes column to isolate the tables that have only CQSInternalID as their primary key. 2. Use the following query to determine the remote tables to avoid opening:
select * from LVTables where Indices=='CQSInternalID'
CQS‑3562 Live Datamart Server 2.1.0, 2.1.1, 2.1.2 uses JVM default garbage collector.
Description In releases 2.1.0, 2.1.1, and 2.1.2, no Java garbage collection options were explicitly specified, which meant that Live Datamart Server used the default collector for the JDK in use. For the default JDK 8, this is the throughput collector.
Workaround Starting with release 2.1.3, the default collector is explicitly specified as the G1 collector. See Java Garbage Collection Settings for a workaround for earlier 2.1.x releases.
CQS‑3383 LiveView Desktop can return results into one column instead of several.
Description Under some circumstances, if a query starts, then ends very quickly in an error condition (such as reaching a row limit almost immediately), LiveView Desktop might display the results using a single, unlabeled column, with every data row showing field values separated by commas, rather than displaying them in individual columns.
Workaround Investigate the cause of the error condition and correct it, if possible, perhaps by increasing the row limit value.
CQS‑3355 LiveView Desktop — Newly added table columns do not appear by default in query grid views.
Description When LiveView Desktop has previously been used to query a Data Table, new columns added to the Data Table after the initial query was performed may not appear automatically in subsequent queries.
Workaround There are two workarounds for this issue. The first is to close all open Query Results views and delete the existing queries from your LiveView Tables view. Locate the Delete Recent Queries function in the context menu of the Recent Queries menu item nested under the desired data table in the Tables view. An alternative workaround is to use the context menu of the existing Query Results view and select Columns. Any newly added columns should be present in the Available list in the Column Chooser dialog and can be added to the Chosen column list.
CQS‑3287 LiveView with multiple count_distinct() expressions in one projection can return invalid results.
Description If a Data Table has any case insensitive fields, and a query has a projection with more than one count_distinct() function with identical parameters, the resulting count_distinct values are likely to be incorrect.
Workaround None. It is expected to be very unusual that a projection would have more then one count_distinct() function with identical parameters.
CQS‑2843 Standalone Help Viewer and sbhelp not provided.
Description Starting with LiveView 2.0.0, the standalone Help Viewer on Windows, and the sbhelp utility on OS X and Linux, no longer function. The move to Eclipse 4.4 as a base for StreamBase Studio caused complications that were solved for Studio, but not for the Help Viewer.
Workaround Use the Eclipse Help provided as part of StreamBase Studio, or the website version of the documentation, as described in Using the Help System
CQS‑2820 Time-windowed predicates not working as expected in author-time aggregation.
Description In author-time aggregation, where you enter a query in an aggregation data table's lvconf definition, the predicate must always start with a simple StreamBase expression that results in a Boolean type. You cannot start with a time-windowed predicate expression such as when transactionTime between now()-minutes(5) and now().
Workaround If you only want a time-windowed expression in the <predicate> element of the lvconf, prefix it with the simple StreamBase expression true. For example:
true when transactionTime between now()-minutes(5) and now()
CQS‑2659 Cannot create destination directory error in LiveView Desktop connection dialog.
Description Start LiveView Desktop. In the initial Connect to LiveView dialog, after selecting a valid LiveView Server's URL, the connection fails with the message Cannot create destination directory.
Workaround The message refers to the local directory used to contain workspaces for LiveView Desktop. Click to open the Advanced Options control, and make sure the Store workspaces in field is not blank. If it is, enter your desired path, or click the Default button. Then try the connection again.
CQS‑2632 Display errors in LiveView Desktop charts.
Description LiveView Desktop charts can show off-by-one-hour errors in locales that observe daylight savings time, and can display some nulls as "n/a".
Workaround None. These issues are expected to be corrected in an upcoming release of the DataWatch libraries used by LiveView Desktop.
CQS‑2453 LiveView 1.6.0 clients do not correctly receive delete messages from LiveView 1.6.1 servers.
Description Queries issued by LiveView 1.6.0 clients do not correctly receive delete messages from LiveView 1.6.1 servers.
Workaround Do not use use 1.6.0 clients with 1.6.1 servers.
CQS‑2395 In LiveView Desktop heat maps, breakdown bar failures.
Description In LiveView releases before 1.6.1, clicking the breakdown bar in a LiveView Desktop heat map should reset a drill down back to its starting point, but has no result. Starting with release 1.6.1, the same action converts the chart to a single large node; you must reset the chart to restore it (click pause then play, or reconfigure the dialog that defines the heat map).
Workaround None.
CQS‑2234 Transform applications must be at the project's root folder.
Description The transform application tag in a table's lvconf file does not allow the subfolder attribute nor can it read a file path in the filename attribute.
Workaround When configuring transform applications for use with LiveView data tables, place the sbapp file in the project's root directory.
CQS‑1692 Referencing a JDBC table that has not been properly loaded prevents LiveView Server from starting.
Description JDBC tables are not automatically started as part of a LiveView Server project start. This means that if you configure a project with a JDBC table, you must load the database before starting LiveView Server.
Workaround Start the JDBC database before starting LiveView Server.