1.1.2.10 Release 19.1.0.0.1 - Known Issues
This section lists the known issues and workarounds for Oracle Stream Analytics release 19.1.0.0.1.
1.1.2.10.1 Edit DB Target fails to detect the updated/added columns in a table
Bug Number: 30540965
Issue
If you add a database target with a predefined table and then edit the table manually, the target does not reflect the edited table. This is a known issue.
Workaround
If you alter the table used as target for a OSA pipeline, for the changes to reflect, you should delete the existing target in the pipeline and create the Database target again.
1.1.2.10.2 Adding DB Target Stage fails when underlying Table has a Blob column
Bug Number: 30542368
Impacted Platforms: All
If you add a database target mapped to a table having a 'BLOB' or 'Interval' data type columns, the target does not identify the columns of the two datatypes. This is a known issue.
Workaround
There is no workaround for this issue. You should use only the tables without blob and interval column types as target for their OSA pipelines.
1.1.2.10.3 Pipeline continues to process records even when target is not accessible
Issue
Bug Number: 30531844
pipeline with a Database target gets published and continues to process records even when the Database target is unavailable. This is a known issue.
Workaround
None
1.1.2.10.4 UI allow no mapping for a DB table column with Not Null constraint
Bug Number: 30542553
Issue
While adding a Database target, the UI allows you to map to any field in the target DB table, which has a 'not null' constraint. But when you try to publish a pipeline with a 'not nullable' column mapped to a 'No Mapping' field, you will encounter an exception with error code OSA-01213.
This is a known issue.
Workaround
None.
1.1.2.10.5 Unable to change DB target Property Mapping after Switching to a New Target
Issue
Bug Number: 30566018
You cannot change the target property mapping after changing the target to a newly created one.
Workaround
Delete the target stage and create new target stage pointing to the new target.
1.1.2.10.6 Timestamp seen in Live Data is different from Input Data
Bug Number: 30579122
Issue:
In a live data stream, you cannot properly parse the timestamps having more than 3 digits of precision.
Use a timestamp format from the list of supported formats below:
11/21/2005 11:14:23.111 "MM/dd/yyyy HH:mm:ss.SSS"
11/21/2005 11:14:23.11 "MM/dd/yyyy HH:mm:ss.SS"
11/21/2005 11:14:23.1 "MM/dd/yyyy HH:mm:ss.S"
11/21/2005 11:14:23 "MM/dd/yyyy HH:mm:ss"
11/21/2005 11:14 "MM/dd/yyyy HH:mm"
11/21/2005 11:14 "MM/dd/yyyy HH"
11/21/2005 "MM/dd/yyyy"
11-21-2005 11:14:23.111 "MM-dd-yyyy HH:mm:ss.SSS"
11-21-2005 11:14:23.11 "MM-dd-yyyy HH:mm:ss.SS"
11-21-2005 11:14:23.1 "MM-dd-yyyy HH:mm:ss.S"
11-21-2005 11:14:23 "MM-dd-yyyy HH:mm:ss"
11-21-2005 11:14 "MM-dd-yyyy HH:mm"
11-21-2005 11 "MM-dd-yyyy HH"
11-21-2005 "MM-dd-yyyy"
15-DEC-01 11.14.14.111 AM"dd-MMM-yy hh.mm.ss.SSS"
15-DEC-01 11.14.14.11 "dd-MMM-yy hh.mm.ss.SS"
15-DEC-01 11.14.14.1 "dd-MMM-yy hh.mm.ss.S"
15-DEC-01 11.14.14 "dd-MMM-yy hh.mm.ss"
15-DEC-01 11.14 "dd-MMM-yy hh.mm"
15-DEC-01 11 "dd-MMM-yy hh"
15-DEC-01 "dd-MMM-yy"
15/DEC/01 "dd/MMM/yy"
2013-10-5 15:16:0.756 "yyyy-MM-dd HH:mm:ss.SSS"
2013-10-5 15.16.0.756 "yyyy-MM-dd HH.mm.ss.SSS"
2013-10-5 15:16:0 "yyyy-MM-dd HH:mm:ss"
2013-10-5 15.16.0 "yyyy-MM-dd HH.mm.ss"
2013-10-5 15:16 "yyyy-MM-dd HH:mm"
2013-10-5 15.16 "yyyy-MM-dd HH.mm"
2013-10-5 15 "yyyy-MM-dd HH"
2012-11-10 "yyyy-MM-dd"
11:14:14 "HH:mm:ss"
"yyyy-MM-dd'T'HH:mm:ss'.'SSS"
"yyyy-MM-dd'T'HH:mm:ss"