DSXchange

Please ignore this message. For some reason, the days_back parameter was missing in the parameter list. Once included, it worked.
sorry.

below is a snippet of user defined sql in the sql tab of output tab from a source table. NCMATERL.ROW_LAST_UPDT_DT>=CURRENT DATE - #days_back# DAYS; days_back is a parameter. If I use "generated sql query", in the selection tab it will work. But, in this case I must use a user defined sql....

I'm familiar with the constraints, even though I first started using this tool last week. The problem is that my constraint is a field showing the last update that appears only in the first lookup. The rest of the tables lack this field. The only way to use this would be to write sql to link the one...

How then do I use this hash file to constrain the output? In some cases, I only have the tag number available. How do I say, only output the tag numbers that appear in the hash file?

I created a hash file that contained tags (varchar(15)) for the last 10 days. I then created a new job, using the DB2 table and the hash file joined to the transform with an output to an Oracle table. The join did not limit the number of tags placed into the Oracle table. All 7 million rows were ins...

Our Oracle DBA's had a similar problem when they tried to install the 64 bit product on a 32 bit unix machine. Go figure.

Man, I am so temped to say write a PL/SQL procedure to do this. Oracle should outperform DataStage internally every time. But, then you are supporting 2 separate environments and the cost goes way up. You have to have support that is familiar with PL/SQL and DataStage. If you get in a bind, I can wr...

This is great stuff! I deal with a lot of DB2 stuff with records in the 10's of millions. When should I use a hash file and when should I just do a join with a constraint on the tables?

I am unable to limit the output to an Oracle table from a db2 table by creating a join of the db2 table to a hash file. This is what I did. I created a hash file of tags for the last 10 days. I then created a job that included this hash file and the db2 source table both joined to a transform. I joi...

I don't know if this is related but: What I found moving date data from DB2 to Oracle was that I had to type cast the DB2 date field (field1) to char(10) and the Oracle to datestamp(19) (field1:' 00:00:00') in the left determinate? column in the grid window. I added the :' 00:00:00' to tell oracle i...

found the answer: use # around the variable instead of using db2 syntax
ROW_LAST_UPDT_DT >= CURRENT DATE - #days_back# DAYS

I have an DB2 source for a job stage In the output-selection "where clause:" window I want to limit the data with this statement ROW_LAST_UPDT_DT >= CURRENT DATE - :days_back DAYS The days_back is a parameter for this db2 (IBM version 5) stage. I get an error. If I use this statement ROW_L...