DSXchange

i second that.. As a general rule, Datastage Enterprise Edition automatically combines pipelining, partitioning and parallel processing. The concept is hidden from a Datastage programmer. The job developer only chooses a method of data partitioning and the Datastage EE engine will execute the partit...

We have two versions of the code a generic version of the code already developed that applies across all clients (makes use of the generic stage) a traditional method specific for each client I developed. In the existing generic method the sequence job calls the file extraction job, followed by data...

ok found the error...in the target ODBC connector the table name was referencing an old table since this job was copied from an older job. replaced with the current table name. reran the job with no problems.

Still this error from the log is very misleading and inaccurate.

each column to be mentioned in the WHERE clause is identified in the metadata as Key which is the reason i am confused that I am getting this error.

tried replacing the parameter with the actual table name and the error doesn't go away (same error)

this is the sequence job error. Post the abort message from the parallel job. Master failed because one of the jobs it is calling is aborting.

Source stage (Flat File): Target stage (ODBC Connector) Usage: Write mode = Update; Generate SQL = Yes; Table name = #target_table# NO RCP with this job.. I have the primary key I want to update on selected in the target ODBC connector stage which matches the primary key in the database table At run...

two possibilities

it could be related to a problem with your ODBC.ini file setup.
If you are using an ODBC setup then you may want to test the connection to ensure it is good.


it could also be related to the length of the filename. reduce the filename length and try again

try this

TrimLeadingTrailing(Trim(input column, char(13), 'T'))

please check other posts

viewtopic.php?p=358261

Yes have the metadata in the same order.

As craig explained if you have set Generate SQL at runtime then you dont have to worry about it.

any other suggestions??

if lookup doesn't happen then the fields from that link are set to NULL with the Continue option. That is the null i am talking about In Transformer I am checking and if it is null then set the internal error code (300) else 0 before i check the null I am trimming the value coming in the gender fiel...

i am not doing any transformations at this point so no need to convert null to value.

If IsNull(TrimLeadingTrailing(lnk_in_tfm.Gender)) Then 300 Else 0

will my function trim the null is what I need clarification on??

if it does then proper error code wont be outputted.

does TrimLeadingTrailing() remove nulls from lookup?? doing lookup upstream onb gender and if lookup fails then being set as continue. This means if lookup fails then the The fields from that link are set to NULL and Continues processing any further lookups before sending the row to the output link....