Datasets Created With Direct Database Connection Don't Update Column Data Type In Case Of Data Model Change
(Doc ID 2941120.1)
Last updated on NOVEMBER 03, 2023
Applies to:
Oracle Analytics Cloud - Version January 2023 and laterInformation in this document applies to any platform.
Symptoms
Column datatype is not getting updated in the Datasets created with direct database connection when there is datatype change in the database.
Steps Followed :
- Create dataset based on direct database connection and use "Manual Query" option. Preview and Profile data and the results will appear without issues.
- Make database change to one of the columns datatype used in the dataset. ex: (change column datatype from Number to Varchar.)
- Open the dataset and notice that the updated column data type will not be reflected in the dataset and when you try to use "Edit definition" and try refreshing the SQL , the preview data will fail and the profiling will fail .
- Below error will be noticed:
QueryFailed:[nQSError:46035]Datatype(VARCHAR) nullable(0) unicode(1) external char(0) conversion to datatype(NUMERIC) nullable(0) unicode(0) external char(0) is not supported.
- Edit of the existing dataset with changed datatype is not possible and a new dataset should be created as a workaround.
Changes
Issue is noticed with dataset using "Manual Query" option, any change in datatype of database column will create an issue with existing dataset.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |