DSXchange

ray.wurlod

There is no such option (as the one you asked for) in Manager client's Export dialog.

ray.wurlod

Which version of the Red Brick ODBC driver are you using, and which version of Red Brick?

ray.wurlod

You have been given a solution. Did you try it?

ray.wurlod

WHERE '' IS NULL will never be true.

A zero-length string ("") is NOT the same as NULL. One has a known value, the other does not.

ray.wurlod

No I didn't, so thanks for the extra info. It's interesting that there is a duplicate name in the USNAME.CLS file, which theoretically at least is read only in version 8. Hmm. Will need to check mine - being in Australia I don't get to use the USNAME rule set all that much. Bireswar, are you using a...

ray.wurlod

Sure, but you can help yourself faster by searching. Essentially what you need to do is as follows (in a job sequence). Determine the current maximum value (use a job). Load this somewhere convenient (a file, or the job's user status area). Retrieve that value. Use that value as a job parameter to p...

ray.wurlod

Code: Select all

Right(InLink.TheString, Len(InLink.TheString) - 1)

ray.wurlod

Select the table definition in Manager and perform a Usage Analysis. This will show you which jobs use that table definition. Scroll to the right of the report and it will show you which columns are used. Note that this assumes you have been rigorous in maintaining the connectivity between jobs and ...

ray.wurlod

No.

You could look at the job sequence log in Director (or using API functions or dsjob command) - from memory a regular run request has "job run requested" while a reset has something different.

ray.wurlod

All you need to find is a third-party ODBC driver for MS Access. Then set up a DSN using this driver and point it at the .MDB file in question.

ray.wurlod

No, that's when the job most recently started. You get the creation date from the DS_AUDIT table.

Code: Select all

SELECT DTC, CREATOR FROM DS_AUDIT WHERE CLASS = '2' AND INSTANCE = '<<Job Name>>';

ray.wurlod

If the inputs are identically hash partitioned and sorted, then it will work. Therefore I must assume that there was some difference between the inputs in your case in how the partition and/or sort keys were specified.

ray.wurlod

Answered in the QualityStage forum.

ray.wurlod

WHat have you tried? It should be a straightforward sorting and filtering specification.

ray.wurlod

Look in your classification table (the .CLS file for the rule set). It appears that there is at least one duplicate entry therein. The file should be sorted. Why not process it with a DataStage job to identify the duplicate(s)?

Search found 53125 matches