Bug Number: 27759679

Impacted Releases: 18.1.0.0.0

Impacted Platforms: All

A Pipeline is broken. Please fix all invalid stages. message appears when you try to add a filter in a join stage. This is a known issue.

Workaround

No workaround available

Bug Number: 27759532

Impacted Releases: 18.1.0.0.0

Impacted Platforms: All

While publishing a pipeline, if you enable HA you can see that the batch scheduling is delayed. This is a known issue.

Workaround

No workaround available

Bug Number: 27162360

Impacted Releases: 18.1.0.0.0

Impacted Platforms: All

Multiple logins from different browser instances using the same user id is not supported in Oracle Stream Analytics. Even though you are not working on the same artifacts, logging in to the application using the same user credentials from multiple places is not allowed.

Workaround

No workaround available

Bug Number: 27339675

Impacted Releases: 18.1.0.0.0

Impacted Platforms: All

When any of the previous stages are updated, the changes are not propagated to the target stage. The live output table in the target stage does not show any events. This is a known issue.

Workaround

Re-configure the target by selecting No Target in the target configuration section.

Bug Number: 27474785

Impacted Releases: 18.1.0.0.0

Impacted Platforms: All

Full values within the drop-down list are not seen when the live output table has a single row. This is a known issue.

Workaround

Pull the horizontal splitter up so that more of the table is visible.

Issue

Bug Number: 27466147

Impacted Releases: 18.1.0.0.0

Impacted Platforms: All

The metadata export functionality for dashboards is not supported in this release of Oracle Stream Analytics. This is a limitation.

Workaround

No workaround available

Bug Number: 27515146

Impacted Releases: 18.1.0.0.0

Impacted Platforms: All

The metadata export functionality for pipelines that contain custom stages is not supported in this release of Oracle Stream Analytics.

Workaround

No workaround available

Bug Number: 27466177

Impacted Releases: 18.1.0.0.0

Impacted Platforms: All

The metadata export functionality of a cube is not supported in this release of Oracle Stream Analytics.

Workaround

No workaround available

Bug Number: 27594028

Impacted Releases: 18.1.0.0.0

Impacted Platforms: All

The metadata export functionality for pipelines that contain scoring stages is not supported in this release of Oracle Stream Analytics.

Workaround

No workaround available

Issue

Impacted Platforms: All

The metadata export functionality of predictive models is not supported in this release of Oracle Stream Analytics. This is a limitation.

Workaround

No workaround available

Issue

Impacted Releases: 18.1.0.0.0

Impacted Platforms: All

The metadata export functionality for visualizations is not supported in this release of Oracle Stream Analytics. This is a limitation.

Workaround

No workaround available

Issue

Bug Number: 27511853

Impacted Releases: 18.1.0.0.0

Impacted Platforms: All

Jetty slows down because of an improper connection pooling size. You must allocate more size for pooling if not explicitly specified.

Workaround

Add the connection pool size in the configuration. The sample JDBC configuration looks like the following:

<New id="osads" class="org.eclipse.jetty.plus.jndi.Resource">          
	<Arg>              
		<Ref refid="wac"/>          
	</Arg>          
	<Arg>jdbc/OSADataSource</Arg>          
	<Arg>              
		<New class="oracle.jdbc.pool.OracleDataSource">                  
			<Set name="URL">jdbc:oracle:thin:@myhost.example.com:1521:OSADB</Set>                  
			<Set name="User">{OSA_USER}</Set>                  
			<Set name="Password">{OSA_USER_PWD}</Set>                 
			<Set name="connectionCachingEnabled">true</Set>                 
			<Set name="connectionCacheProperties">                     
				<New class="java.util.Properties">                         
					<Call name="setProperty"><Arg>MinLimit</Arg><Arg>1</Arg></Call>                         
					<Call name="setProperty"><Arg>MaxLimit</Arg><Arg>15</Arg></Call>                         
					<Call name="setProperty"><Arg>InitialLimit</Arg><Arg>1</Arg></Call>                     
				</New>                 
			</Set>              
		</New>          
	</Arg>      
</New>

Issue

Bug Number: 27587750

Impacted Releases: 18.1.0.0.0

Impacted Platforms: All

Sometimes no data is seen in the target stage of the live output when you publish the pipeline.

Workaround

Exit the pipeline editor and come back to the pipeline.

Issue

Bug Number: 27480822

Impacted Releases: 18.1.0.0.0

Impacted Platforms: All

In coherence cache, data type conversion to SDO_GEOMETRY is not supported. This is a limitation.

Workaround

No workaround available

Issue

Bug Number: 25132943

Impacted Releases: 18.1.0.0.0

Impacted Platforms: All

When you have configured the batch duration as 1 second for underlying Spark Streaming, the pattern match clause cannot detect events sequence correctly happening within an interval of less than or equal to 1 second. This is a limitation.

Workaround

No workaround available

Issue

Bug Number: 27578142

Impacted Releases: 18.1.0.0.0

Impacted Platforms: All

When you create a file stream with Read whole content option enabled, the pipeline is stuck at the message “Listening for Events” and no data appears in the live output table.

Workaround

Turn off the Read whole content option to see the events streaming in the live output table.

Bug Number: 27701535

Impacted Releases: 18.1.0.0.0

Impacted Platforms: All

There is a limitation on the size of text fields in pipelines: events with text fields exceeding 1024 characters will not be processed.

The menu commands for creating Predictive Models and Scoring Stages are marked Beta, for example, Predictive Model (Beta). The Beta label indicates that the functionality has been tested, but is not fully supported. The import and scoring of Predictive Models might contain undocumented limitations and you should use them as is.