timestamp over-scale issue in 8.5
Posted: Wed Aug 31, 2011 2:38 am
Hi all.
Recently we moved from IBM IS 8.1 to 8.5.
Jobs were migrated and some issues appeared...
Here is one of them:
In 8.1
For the timestamp data type if You set scale higher than in database, engine throws warnings, but timestamp data is OK. Microseconds are available.
In 8.5
For the timestamp data type if You set scale higher than in database, engine throws warnings, but timestamp data is NOT OK. Microseconds are truncated.
Does anybody saw this issue before?
Maybe there is some variable that You can set to 8.5 would behave like 8.1 regarding overscale with timestamp?
This issue is very annoing because we would have to change zillion of stages to correct this...
Regards
Tcheslav
Recently we moved from IBM IS 8.1 to 8.5.
Jobs were migrated and some issues appeared...
Here is one of them:
In 8.1
For the timestamp data type if You set scale higher than in database, engine throws warnings, but timestamp data is OK. Microseconds are available.
In 8.5
For the timestamp data type if You set scale higher than in database, engine throws warnings, but timestamp data is NOT OK. Microseconds are truncated.
Does anybody saw this issue before?
Maybe there is some variable that You can set to 8.5 would behave like 8.1 regarding overscale with timestamp?
This issue is very annoing because we would have to change zillion of stages to correct this...
Regards
Tcheslav