DSXchange

Thanks for all the input. Our IT support are exploring updating the drivers. So far, no luck. I'll report any progress/fix.

Rule definitions are dynamic only within IA. Published definitions that you use in DataStage are not.

Go to Project Properties and check your settings for purging rule output tables.

Revisiting this question... Running on IA 11.3.1.2 Data source: SQL Server We are trying to access an nvarchar field which the data owner advises could be up to 2GB. IA says it 'Cannot Analyze' the data. Every rule that references it fails. I've even tried LEFT(fieldname, 250) but again the mere ref...

Gracias, manito! Sorry I was away from the forum for a while.

Gracias, manito!

I haven't used this approach before. Would you have instructions?

We are on v11.3 and cannot get GLVs to work. Even just creating them, I cannot save a literal value like numeric 1116. It goes thru the motions of saving, but when I reopen the GLV, the value is gone.

Has this happened to you? If so, did you come up with a solution?

Thanks in advance.

Many thanks!

Thanks, guys. We'll be eagerly waiting for the GUI update. Meanwhile, would you have any material on the command line method?

My apologies, Ray. Forgot to update the version. I think we are on 11.3.1.2. Not quite it?

I am trying to create a virtual table that would only select the MAX of a column. I cannot find a way to use a function, e.g., MAX, on the columns that are selected in creating a virtual table.

For example:

EP_ID
300
400
150
277

I only want the row where EP_ID is 400.

Thanks in advance.

Sorry, I cannot dump the job score of the particular run. It seems our job logs are purged constantly. However, I did two things: - put a Transformer between the Data Rule stage and the sequential file - removed length/precision of 38/10 for an integer column I don't know which one fixed the problem...

I'm getting this error AT RUN-TIME. I've searched here and on Google and the search results are only about compilation errors. The job is pretty basic: Oracle source goes to a Data Rule stage where I check for duplicates on a combination of 3 fields and output to a sequential file. Here is the full ...

We ended up with .csv files. I now use DataStage and its Data Rule stage to produce the output. DataStage is way more powerful, less resource-hungry, faster, and parameterized!

We are upgrading to 11.5 very soon so yeah!