Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
Per default timestamp types will be created as timestamp(0) which is not usable for our Informatica environment.
We can change the precision parameter by hand (see screenshots below) but after saving the diagram and
reloading it from the file the default values wrongly reappear! You can test this with the attached repository.
To reproduce this issue, create a new diagram and a new table on that diagram. Add a Timestamp column and remove the precision. Save and closet the diagram. Open it again and check the Timestamp precision.
Support Information:
Product: Aqua Data Studio
Version: 19.0.1-2
Build #: 55841
Build Date: 2018-May-18 03:04:57 PM
Operating Environment: Windows 7 (6.1, amd64) / Cp1252 / de / DE / Oracle Corporation 1.8.0_102-b14
Memory: Max=954.728.448; Total=678.428.672; Free=461.361.968; CPUs=4
In-Window Graphics Capabilities
Graphics Vendor: Intel
OpenGL Renderer: Intel(R) HD Graphics 4400
OpenGL Version: 4.3.0 - Build 10.18.14.4432
Double-Buffering: Enabled
Anti-Aliasing: Enabled
Anti-Aliasing Sample Count: 8
Hardware Acceleration: Enabled
Color Bits: Red: 8 Green: 8 Blue: 8 Alpha: 8
Depth Bits: 16
Accumulation Buffer Bits: Red: 0 Green: 0 Blue: 0
Initialization Time: 1847 ms
Offscreen Graphics Capabilities
Graphics Vendor: Brian Paul
OpenGL Renderer: Mesa OffScreen
OpenGL Version: 2.1 Mesa 7.8.2
Double-Buffering: Disabled
Anti-Aliasing: Disabled
Anti-Aliasing Sample Count: 0
Hardware Acceleration: Disabled
Color Bits: Red: 8 Green: 8 Blue: 8 Alpha: 8
Depth Bits: 16
Accumulation Buffer Bits: Red: 16 Green: 16 Blue: 16
Initialization Time: 67 ms
Hardware PBuffer Available: No
Using PBuffer: No
Using Ram Buffer: Yes
Offscreen Rendering: Enabled
Offscreen Buffer Size: 800x600
Hi Alonso,
Screenshots? Infomatica? What database? Attached repository?
Thanks, Tom
I attached the test repository, screenshots. The database they use is HP Vertica.
I attached the test repository, screenshots. The database they use is HP Vertica.
Hi Alonso,
Would you ask the customer if the problem is when they generate the script from the model? I realize that it puts a zero precision in the table properties but that is internal to ADS ERM. What externally is causing the problem? How are they using this with Informatica?
Thanks, Tom
Hi Alonso,
Would you ask the customer if the problem is when they generate the script from the model? I realize that it puts a zero precision in the table properties but that is internal to ADS ERM. What externally is causing the problem? How are they using this with Informatica?
Thanks, Tom
Hey Tom,
Here is the replay from the user:
Yes, we receive the issue when generation from model after we clicked the save button in the ER-Modeller.
As far as I understood our Informatica and Microstrategy developers, they can't handle timestamp(0) types very well.
I believe they are generating the script to be used somewhere else.
Thank you,
Alonso
Hey Tom,
Here is the replay from the user:
Yes, we receive the issue when generation from model after we clicked the save button in the ER-Modeller.
As far as I understood our Informatica and Microstrategy developers, they can't handle timestamp(0) types very well.
I believe they are generating the script to be used somewhere else.
Thank you,
Alonso
Hi Alonso,
Thanks for the info. So, if I can change the ddl scripting from timestamp(0) to timestamp, we should be ok? This will be easier than trying to change erm.
Thanks, Tom
Hi Alonso,
Thanks for the info. So, if I can change the ddl scripting from timestamp(0) to timestamp, we should be ok? This will be easier than trying to change erm.
Thanks, Tom
Hi Tom,
From the information they sent us, yes that would be a fix as it would be the expected behaviour for timestamp data type.
Hi Tom,
From the information they sent us, yes that would be a fix as it would be the expected behaviour for timestamp data type.
Hi Alonso,
As it turns out, I do have to change it in the erm. I have a fix but need to get it tested. The fix should be in the next patch that goes out assuming that it tests ok.
Thanks, Tom
Hi Alonso,
As it turns out, I do have to change it in the erm. I have a fix but need to get it tested. The fix should be in the next patch that goes out assuming that it tests ok.
Thanks, Tom
V19 SVN# 55905
V19.5 SVN# 55906
Test cases are attached.
V19 SVN# 55905
V19.5 SVN# 55906
Test cases are attached.
Issue #15605 |
| Verified |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build ADS 19.0.2 and ADS 19.5.0-dev-5 |
| No time estimate |
Hi Alonso,
Screenshots? Infomatica? What database? Attached repository?
Thanks, Tom