DSXchange

Craig, I believe that you're correct, that only successful look up rows are shown in the monitor. However, it doesn't show any rows read from the input flat file or written to the output flat file. I'll have to go look and see if any rows were actually written to the output file. As dumb as it sound...

We ran into a problem when running a job, no rows go through or are processed. It appears to happen when using certain database tables as lookups. When it's running, you can look at the job monitor and no rows are read, or are processed by the lookup link. If I enable all the tracing options on the ...

raviyn, I know this doesn't help you, other than to confirm your problem with Excel, but I have also had this problem when exporting data to flat files from Excel. It "forgets" to write anything at the end of the line if there is no data in those columns. Happens after the first 8 rows or ...

Ray,
Will there be any benefit to doing this, then? I hadn't thought this all the way through. If I lose memory caching, then there probably isn't any benefit to doing it this way compared to just looking it up in the Oracle DB. Is this correct?

Thanks again for your help.

Tony

No problem. Sometimes it's hard to see stuff like that in your own code. Glad I could help.

Tony

Steve,
I'll post an answer here if I come up with anything.

Tony

Craig, I thought that you had to use the whole key that that hash file was created with to access it on a lookup (from a hash file stage). I recall some really screwy things happening when I inadvertently had the key defined one way one place and another way someplace else. It would still seem to me...

I'm trying to speed up a lookup and was thinking about reading the DB table into a hash file. The problem is that I'm using the "reference link with multi row result set" option on the ODBC stage that I'm currently using for this lookup stage. Is there a way to create a hash file to allow ...

Shivakumar Looks like you're setting the variables p$17$1 and p$17$2 to the literal values of the variable names because of the quotes around the variable names. Should be: p$17$1 = ETLEndTime err$code = DSSetParam(h$17, "ETLEndTS", p$17$1) and p$17$2 = ETLStartTime err$code = DSSetParam(h...

Raggy, On the Sequential File stage where you are writing the data out, do you have the "Update Action" set to "Overwrite existing file" or "Append to existing file"? Also, you may want to land the data in another sequential file, then delete the original and rename the...

No problem. I'm not sure what the stars mean anyway. Whatever they mean, I probably don't deserve 5 anyway [8D]

Thanks, Vincent.

Sorry to pass along bad information.

TOny

I'm pretty sure that you can just access them as you would variables, e.g. if you had a job param named 'FilePath', you would use FilePath in your routine.

Hope I'm right[;)],

Tony

Jayaram Nallamothu, There are several ways to accomplish what you want... Since it's sorted, you could use a stage variable to hold the current value of A and a stage variable to hold your values that need to be concatenated. A quick and easy way to do it would be to use a hash file with column A as...

Steve, I'm not the expert here, so take what I say with a grain of salt... The help file says that you can use multi-row reference lookup from an ODBC or UniVerse stage. I believe that you can use the UniVerse stage to access a hash file. Am I correct, Ray? If so, you can set up the UniVerse stage t...