Column ... floating point decimal is not fully supported;
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 58
- Joined: Wed Apr 04, 2007 10:02 am
Column ... floating point decimal is not fully supported;
Hello,
i found many entries in the forum regarding this topic, but nothing for my special problem:
We change out environement from HP to AIX, and of course get Oracle new installed.
On the new maschine all jobs reading from oracle now get this messages "Column ... floating point decimal is not fully supported; adjusting the scale."
This was not the case in the old environment.
Well something must be different on the new maschine, but what?
It is a Datastage parameter,
a Unix parameter
or a Oracle paraemter ???
Hope, that anybody can help me. Thanks a lot in advance !!!
Manfred
i found many entries in the forum regarding this topic, but nothing for my special problem:
We change out environement from HP to AIX, and of course get Oracle new installed.
On the new maschine all jobs reading from oracle now get this messages "Column ... floating point decimal is not fully supported; adjusting the scale."
This was not the case in the old environment.
Well something must be different on the new maschine, but what?
It is a Datastage parameter,
a Unix parameter
or a Oracle paraemter ???
Hope, that anybody can help me. Thanks a lot in advance !!!
Manfred
I liked on of Ray's old posts on this subject:
ray.wurlod wrote:It's all Oracle bin Larry's fault for not having a proper Integer data type.
You can not prevent this message without adjusting your metadata precisely to match that of Oracle, and even then you will get a message logged (a slightly different one).
This is one of those alert messages that it is safe to ignore, and therefore I tend to demote it to informational using a message handler. (I never suppress messages from the log.)
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 58
- Joined: Wed Apr 04, 2007 10:02 am
Thanks for your feedback.
But this sounds like to make changes in Datastage on Job level.
As the jobs run properly in the old environment, but now i get in dozends of jobs 100s of warinings, i think there is a very general parameter issue anywhere in Datstage, Unix or Oracle which has to be changed, or?
Manfred
But this sounds like to make changes in Datastage on Job level.
As the jobs run properly in the old environment, but now i get in dozends of jobs 100s of warinings, i think there is a very general parameter issue anywhere in Datstage, Unix or Oracle which has to be changed, or?
Manfred
The recommendation remains to demote this to an informational level message as the message cannot be avoided and is generally not a valid warning.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 58
- Joined: Wed Apr 04, 2007 10:02 am
Migration of the Message Handler
Hello Ray,
well, Datastage Source have been migrated to a new system.
But not the Message-Handler.
How could i do this ???
Manfred
well, Datastage Source have been migrated to a new system.
But not the Message-Handler.
How could i do this ???
Manfred
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
-
- Participant
- Posts: 58
- Joined: Wed Apr 04, 2007 10:02 am
Move Message Handler Files
Hello,
well, meanwhile i have manual demoted many warnings to informational on the new Test-Maschine.
I find now many ".msh" Files there:
dsuser@dwhsie1u /datastage # find . -name *.msh -print
./Ascential/DataStage/Projects/DEV_EDW/RT_SC139/Local.msh
./Ascential/DataStage/Projects/DEV_EDW/RT_SC137/Local.msh
./Ascential/DataStage/Projects/DEV_EDW/RT_SC237/Local.msh
./Ascential/DataStage/Projects/DEV_EDW/RT_SC164/Local.msh
./Ascential/DataStage/Projects/DEV_EDW/RT_SC174/Local.msh
./Ascential/DataStage/Projects/DEV_EDW/RT_SC153/Local.msh
./Ascential/DataStage/Projects/DEV_EDW/RT_SC160/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC730/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC731/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC726/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC725/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC724/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC723/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC719/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC716/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC715/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC711/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC709/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC687/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC681/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC680/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC679/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC678/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC732/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC733/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC734/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC735/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC736/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC737/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC740/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC741/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC742/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC743/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC744/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC745/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC746/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC747/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC751/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC753/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC754/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC755/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC774/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC844/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC845/Local.msh
How can i move this file to the future Produktion system???
Can i concatinate all Content to one file?
If yes, where to put this one big file?
well, meanwhile i have manual demoted many warnings to informational on the new Test-Maschine.
I find now many ".msh" Files there:
dsuser@dwhsie1u /datastage # find . -name *.msh -print
./Ascential/DataStage/Projects/DEV_EDW/RT_SC139/Local.msh
./Ascential/DataStage/Projects/DEV_EDW/RT_SC137/Local.msh
./Ascential/DataStage/Projects/DEV_EDW/RT_SC237/Local.msh
./Ascential/DataStage/Projects/DEV_EDW/RT_SC164/Local.msh
./Ascential/DataStage/Projects/DEV_EDW/RT_SC174/Local.msh
./Ascential/DataStage/Projects/DEV_EDW/RT_SC153/Local.msh
./Ascential/DataStage/Projects/DEV_EDW/RT_SC160/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC730/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC731/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC726/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC725/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC724/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC723/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC719/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC716/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC715/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC711/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC709/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC687/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC681/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC680/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC679/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC678/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC732/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC733/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC734/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC735/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC736/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC737/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC740/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC741/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC742/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC743/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC744/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC745/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC746/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC747/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC751/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC753/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC754/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC755/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC774/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC844/Local.msh
./Ascential/DataStage/Projects/IIP_DEV/RT_SC845/Local.msh
How can i move this file to the future Produktion system???
Can i concatinate all Content to one file?
If yes, where to put this one big file?
Those are "local message handlers", they need to be in the directory for the job they are associated with and thus no "put in one giant file" option. You'd need to find the job number of the job in question and then migrate the msh file from there to whatever job number the job has in production as it will be different.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 58
- Joined: Wed Apr 04, 2007 10:02 am