DSXchange

Thanks Ray for the help

ray.wurlod wrote:No.

SCD stage does not perform a true reference lookup in the sense understood and supported by a Lookup File Set. ...

I have a doubt regarding is lookup fileset can be used as a Source In SCD Stage. I have a job which is dumping 4 column in a lookup fileset. In the second job i am Using that lookup fileset as a Source in SCD Stage. Please tell me that lookup fileset can be used a Source to SCD stage or not. I am ge...

Hi,

Plase provide the complete solution

ArndW wrote:That is an odd error - I'Ve just checked and x2019 is the back apostrophe see here and it does not seem to have a ISO8859-1 count ...

Hi Ray, I have directly imported the table definition from oracle & used that it is importing varchar2(60) in datastge but then also it is showing warnings as Implicit conversion from ustring to string. Is it that the atrributes coming from oracle takes it as ustring? Can suggest some waorkaroun...

Hi, I have getting the following warning i am getting:- SOURCE_TABLES,0: Invalid character(s) ([xFFFD]) found converting Unicode string (code point(s): ST PIERRE DE B[xFFFD]UF) to codepage ISO-8859-1, substituting. SOURCE_TABLES,0: Invalid character(s) ([x2019]) found converting Unicode string (code...

Yes in Dataset & sequential file it is the case that you canot update anything & when the job rinsit deletes the file & makes it in new format.
If the jobs gets aborted in between then there will be no file created in server

Hi haisen, Please clarify what is the target stage you are using. For some information i can tell you that for different stages in target what has to be used for the problem specified above:- Write : It will create the new file Truncate : It will delete the records from the table & insert the ne...

Apologies for that...but just to clarify as i am very new to this forum & this was my first post to this site...i made this mistake...from next posts i did in correct forum...

chulett wrote: Next time, let's start off the conversation in the correct forum, gorramit.

Hi keshav, The solution given by you is informative but i have tried this also. For postal code it was varchar (60) in oracle table. & i have tried with that, in datastage. I have given length as 60 in both source & target column. Following is the error i am getting :- "SOURCE_TABLES: W...

Hi Sriram, Actually as per the requirment, solution provided by you can not be used here. I have got the solution as given by Rajesh...for this problem.. The solution provided by you, i have tried it before & it was working fine. Thanks for helping me sriram. hi here if the look up file set name...

The metedata used in the job are as follows:-

Source Oracle , Column : City Varchar2
In source stage it is taken as Varchar(100)

Target Dataset, Column : City Varchar(100)

Please suggest some solution on this.
Plase let me know if some more information is required

Thanks,
Shobhit

ya, SOURCE_SYSTEM_COUNTRY transferred from source to target lookup fileset. & from main data stream input to the lookup stage is the column "CLI" & from lookup file set column is "SOURCE_SYSTEM_COUNTRY". These two column has to be compared & only that record has to be...

Hi, due to some problem i am not able to view your solution completely. I can explain the situation once more. there was a warning coming before for implecit conversion. so i have done explicit conversion from ustring to string. Then there were hundreds of warning started coming Please explain once ...

Hi, I have checked column names used , they are same & also checked in 2nd job. The case is same there also. Plase suggest some other solution to this. The column names used in lookup filesets are fixed, and the key column names used from the main input link to the lookup must also have the same...

There is a job where following was the warning appearing while running it : SOURCE_TABLES: When checking operator: When binding output interface field "postal_code" to field "postal_code": Implicit conversion from source type "ustring[max=60]" to result type "strin...