Dear all
Pls help look at this issue i met during migrating job from DS 7.5 to 8.7
The error message like this
No default type conversion from type "raw[8]" to type "string[8]
Context:
1. We copied the DS project /DDL/data in DB from existing DS7.5 environment
2. We are using DB2EE stage to extract data from table
3. In DS 7.5 the job is working well, but the job in DS 8.7 aborted due to above error
4.The value of this field is generated in mainframe, we load data from source to staging table, during the load, we are using column import stage to do a convert that is from binary to char, but when we are using DB2EE stage to extract data from staging table, the error appeared
5. this field is defined as char for bit in DDL
Pls let me know whether i need to provide other information
Data conversion issue happened during DS upgrade
Moderators: chulett, rschirm, roy
Re: Data conversion issue happened during DS upgrade
nimix9ig wrote:1. we copied the DS project /DDL/data in DB from existing DS7.5 environment
This is problematic. You copied over the entire Project at the O/S level after you set up the 8.7 server? You didn't export the old projects and then import them into the new environment?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Re: Data conversion issue happened during DS upgrade
actually we did the copy by normal export/import DS utility
Ok... that's good but it's nothing I would label as "copying" hence my concern. Never mind.
The Column Import stage takes a record as a string and parses it out into individual columns, it doesn't effect any conversion in the process that I recall. I would think you should effect an explicit conversion elsewhere, say after parsing out the column rather than thinking it would happen automagically during the Import.
Of course, I could be completely off-base with that line of thought but that's my two cents on this.
The Column Import stage takes a record as a string and parses it out into individual columns, it doesn't effect any conversion in the process that I recall. I would think you should effect an explicit conversion elsewhere, say after parsing out the column rather than thinking it would happen automagically during the Import.
Of course, I could be completely off-base with that line of thought but that's my two cents on this.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
