1. Oracle Stream Analytics Release Notes
  2. Oracle Stream Analytics Known Issues

1 Oracle Stream Analytics Known Issues

The Known Issues for Oracle Stream Analytics for the release 12.2.1.3.0 are listed in this document.

1.1 Known Issues

Code completion information is not shown when CQL Functions are invoked

Bug Number: 24914485

Impacted Releases: 12.2.1.3.0

Impacted Platforms: Only on Internet Explorer 11 browser

The auto code completion information does not show up while invoking CQL functions within the Expression Editor in the exploration editor.

This is a known issue. A fix for this will be available in the next release.

Workaround: None

Discard operation does not pull Group By data off the published exploration

Bug Number: 24913224

Impacted Releases: 12.2.1.3.0

Impacted Platforms: Only on Edge browser

On an Edge browser, when you apply filter, summary, and Group By to an explorations and then discard the changes, the Group By data changes are not pulled off the published exploration.

This is a known issue. A fix for this will be available in the next release.

Workaround: None

Range Window is not aligned correctly

Bug Number: 26417772

Impacted Releases: 12.2.1.3.0

Impacted Platforms: All

The Range Window is not aligned correctly in the user interface.

This is a known issue. A fix for this will be available in the next release.

Workaround: None

Copyright in New Streams and Explorations is 2016

Bug Number: 26360189

Impacted Releases: 12.2.1.3.0

Impacted Platforms: All

The copyright year in the new streams and explorations screens shows a copyright 2016. It should be 2017..

This is a known issue. A fix for this will be available in the next release.

Workaround: None

1.2 Exported JAR File is not generated when an exploration is exported

Bug Number: 24850242

Impacted Releases: 12.2.1.3.0

Impacted Platforms: Only Firefox and Safari browsers

When you export an exploration from either a Firefox or Safari browser, the exported JAR file of the exploration is not generated.

1.3 EOFEXCEPTION thrown after running a published Twitter Exploration for a longer time

Bug Number: 24761636

Impacted Releases: 12.2.1.3.0

Impacted Platforms: All

If a published Twitter exploration is kept running for a longer time, say more than 12 hours, a Twitter exception Stream closed...TwitterException...caused by java.io.EOFException: Unexpected end of ZLIB input stream is thrown.

1.4 Deployment Error is thrown when an invalid data type is selected for a TwitterShapeProperty

Bug Number: 24761563

Impacted Releases: 12.2.1.3.0

Impacted Platforms: All

For a Twitter stream, do not select any data type in the list for each of the properties except for TwitterShape (which is the default). If you select any other data type, a deployment error is thrown.

1.5 Business Rule Value does not take effect

Bug Number: 24760336

Impacted Releases: 12.2.1.3.0

Impacted Platforms: All

In an exploration with a Kafka stream, when you create a business rule and set a value to the rule, the value does not get applied unless you specifically hit the Enter key on the Keyboard explicitly.

1.6 Local Coherence Cache Schema is not supported

Bug Number: 23597239

Impacted Releases: 12.2.1.3.0

Impacted Platforms: All

If you use a local coherence cache schema in a Coherence Inbound Adapter, messages are not received correctly. This is because local coherence cache schema is not supported. Do not use local coherence cache schema to push data into the adapter.

1.7 Incorrect Expression Generated for Filters with BYTE Property

Bug Number: 23074245

Impacted Releases: 12.2.1.3.0

Impacted Platforms: All

BYTE Property is not supported either in Oracle Event Processing or Spark environments when used in Filters.

Workaround

Use the appropriate conversion functions to convert the BYTE type to string.

1.8 Configuration Exception with LONG Datatype

Bug Number: 24694849

Impacted Releases: 12.2.1.3.0

Impacted Platforms: All

LONG, CLOB, BLOB Oracle Database datatypes are not supported. As a result, references based on Oracle Database table with any of these datatypes cannot be used.

1.9 Spatial Pattern breaks after adding Calculated Fields

Bug Number: 23302666

Impacted Releases: 12.2.1.3.0

Impacted Platforms: All

The spatial pattern exploration breaks when you add calculated fields based on any original column of output.

Workaround

Use calculated fields in the downstream exploration instead of pattern itself.

1.10 Reference Fields of Date Type cannot be used in Filters of immediate exploration

Bug Number: 23718439

Impacted Releases: 12.2.1.3.0

Impacted Platforms: All

You encounter exceptions when you add filter conditions that uses reference field of Date type (Date type is a type of the column of the correspondent Database table).

Workaround

Create chained exploration and add corresponding filter conditions in the downstream exploration.

1.11 Published Patterns changes to Draft State

Bug Number: 23597800

Impacted Releases: 12.2.1.3.0

Impacted Platforms: All

Configured with Oracle database metadata persistence storage, when you publish a pattern and then try to change the properties of the pattern, a draft pattern is created. When you delete the draft pattern, the published pattern moves to a Draft state when you open the published exploration's details page.

1.12 Restrictions with User Defined Shape for Twitter Stream

Bug Number: 23551858

Impacted Releases: 12.2.1.3.0

Impacted Platforms: All

When you configure a shape for a Twitter stream, you should use the pre-defined TwitterShape in the Select Existing Shape drop-down list or choose part of the TwitterShape's properties to create a new shape. Otherwise, a deployment error is thrown when you create an exploration using this stream. Also, you cannot see any user-defined shapes in the existing shape drop-down list a for twitter stream creation.