DSXchange

Thanks ArndW and Ray . The issue is resolved . There was a field name L for which datasize was not given.
I have provided the required datasize and now it is working.

Hi ray ,

Please explain what does this means:- ODBC protocol does not allow for an unbounded VarChar .

Kindly see that i am not coding /importing any metadata in this job , i just need making RCP enable and creating a table at RunTime. So while running i am getting this error.

Thanks,
Ankur

Providing more information regarding the problem :- Actually there are 2 jobs :- 1st job create several datasets . Working fine 2n Job is a multiple instance common job which accepts these Dataset name as a paramter and loading into the Oracle Table . Please note RCP is enabled is used so need of wr...

Ankur_KapoorUK - In this case I am under the assumption, arising from the documentation that I was able to find, that Len() function in DataStage will handle the NULL as its argument. If this is a TRIM() function, then I would probably say that we have to explicitly handle the IsNull() condition bef...

I am getting a fatal error as mentioned below :-

TgtCDLTblODBC: [IIS-CONN-DAAPI-000069] Design schema field: L cannot be unbounded. Maximum length must be specified (CC_DBSchemaRules::negotiateDataField, file CC_DBSchemaRules.cpp, line 241)

Kindly provide some inputs.

Thanks,
Ankur

LEN(NULL) != 0 Its pretty often that I run across SQL code that supposed to handle empty or null varchar values. But a lot of the time it doesn't. And usually its because a developer has made the false assumption that null has a length of 0. It doesn't. LEN(NULL) IS NULL. LEN(NULL) does not = anythi...

With 1 node config file , the concept of partitioning will itself will be irrelavent and does not have any importance. So you can keep auto partitioning in both the stages to improve the performance. As APT_NO_PART_INSERTION enviroment variable by default is FALSE. So first it will do the partitinin...

The metadata for the file which i have got was incorrect , it does not actually match the data record length. So after addition of required number of columns in Column Import Stage , no records are rejected . Hence the issue is resolved .
Thanks

Hi craig ,

As suggested by u , I have gone through other post and tried but still it is not working. This warning is coming only for last column of the metadata.
Please guide me

I have coded that column import stage again and the issue is resolved. thanks...

Hi ,

The records are getting rejected because of the following error in Column Import Stage :-

Column_Import_FG,0: Field "AutoGen" with 'delim=end' did not consume entire input, at offset: 299


Kindly prvide ur inputs.

Thanks,
Ankur

Thanks to Everyone .

I want to add some more information here . First I have added 1 column import stage for field name A having suppose 20 columns and then ran the flow it was running fine. Then as per requirement added another column import stage for Field Name B having suppose 24 columns and then ran the job it was f...

I have already changed the Job Default Setting as per the setting that I want in my output .

But Still this is not working out.

Is there any limitation on number of columns that Column Import Stage Supports as i am trying to add more that 50 columns by that stage .