1.1.2.8 Release 19.1.0.0.3 - Known Issues
This section lists the known issues and workarounds for Oracle Stream Analytics release 19.1.0.0.3.
1.1.2.8.1 Duplicate Records seen in case of Pipeline having Multiple Targets
Issue
If you have multiple targets in a pipeline, and one of the targets fails, even before the failure is detected and the pipeline stopped, the data gets written into active targets. When you resolve the failed target and republish the pipeline,there will be duplicate records in the targets that were active.
Workaround
Create a different pipeline with only one target in which duplicate records are not accepted.
1.1.2.8.2 Connection to ADW/ATP fails if Password has Special Characters in it
Issue
If you try to connect to ADW and ATP, and the DB credential has a special character in it, then the test connection and the pipeline deployment will not work.
Workaround
Specify the password between double quotes. For example, "welcome?123".
1.1.2.8.3 Null Pointer Exception when a Reference Table with Interval Data Type is used
Issue
In a Reference table, columns with Year to Month Intervals with year precision greater than 2, are not supported.
Workaround
None.
1.1.2.8.4 Nullpointerexception seen in Driver during a Graceful Shutdown
Issue
If there is some exception with target or reference during graceful shutdown, undeployment of pipeline can take longer, and you will see NullPointerException in the driver logs. However, there will be no data loss.
Workaround
None.
1.1.2.8.5 Clicking on Sign In redirects to Login Page
Issue
At times, entering your OSA instance credentials and clicking Sign In, does not log you in, but redirects you back to the login page.
Workaround
Try one of the following options:
-
Close the window and open the OSA instance in a new window.
-
Clear the cache and cookies in the browser.
-
Clear the JSESSIONID cookie.
To clear the cookies in a Chrome browser, click on the 3 dots at the top right corner. Select More tools -> Developer tools -> Application Tab. Under Storage, expand Cookies. Select your OSA URL and clear JESSIONID cookie.
1.1.2.8.6 Test Connection for JNDI Type does not work on Jetty Server
Issue
If you create a connection of type JNDI and use the JNDI provider as Weblogic, then the Test Connection does not work.
Workaround
Ensure that the JNDI connection details are correct. The pipeline using the JNDI connection works as expected.
1.1.2.8.7 Republish Pipeline while Graceful Shutdown is in progress
Issue
You unpublish a pipeline and republish the same, and encounter the following exception:
OSA-01213 Pipeline deployment has failed. Creating container has failed.
Check if the pipeline with the same name is already running. At times, the graceful shutdown of pipeline takes time to complete, and it is possible that the unpublish action is still underway.
Workaround
You can wait for the pipeline to unpublish gracefully and then deploy the pipeline. You can check the status of the pipeline in the Cluster manager (YARN or Spark standalone) console.
1.1.2.8.8 Republish Pipeline with Reset Offset if Input Topic is Repartitioned
Issue
If you repartition an input topic, you cannot republish a pipeline and start from last processed offsets, because internally created offset topics should have the same number of partitions as the input topic.
Workaround
When you repartition an input topic, republish the pipeline with a reset offset. This will ensure that the earlier offset topic is deleted, and a new one with the correct partition count is created.
1.1.2.8.9 Timestamp with Timezone that has more than 6 Subsecond Precision is not supported
Issue
An input timestamp with a seconds precision greater than 6 digits, and also with a timezone, is not supported. For example, 2020-04-21 12:29:53.998877665 +5:30
, would result in wrong date.
Workaround
Input a timestamp with the seconds precision less than 6 digits.