DSXchange

Can't think of one. On the other hand, profiling empty table doesn't take very long!

Set the Lookup Failed rule to Continue. In the Transformer stage detect success or failure of the lookup with an IsNull() function. If the lookup fails, your new record goes to an Insert link. If the lookup succeeds, your new record goes to an Insert link and the columns returned from the Lookup go ...

In this case I proposed removal only within the scope of the comparison.

Probably easier to execute the command from the Administrator client Command window, but from the DataStage shell on the server in the project would also work. But it's not "the UniVerse database". Hasn't been for years.

You can tweak the READONLY field in DS_JOBS. When you want the job to be editable again, set this to 'NRO' (not read only).

Indeed it can fail even on a medium sized Cognos model.

One way we have had to implement is to replace the 32-bit JVM that installs with the product with a 64-bit JVM provided by IBM support. No more java.lang.OutOfMemory errors (thus far)!

Convert all the unwanted characters to "" prior to performing the comparison. A single Convert() function on each input shall suffice.

Yes, basically using Lookup and Transformer stages. The logic is contained within the Transformer stage.

Still waiting for pragb to post the exact error message...

There's no such thing as a default format for Oracle. You set your own date picture (or the DBA may have done it for you). Let's assume it's YYYY-MM-DD, which is also the ISO 8601 standard. You now have two problems - how to correctly add the century to your two digit years, and how to reorder the c...

The SQL Server Enterprise stage may have been exported from the Windows system and imported into the UNIX system. However it will not work there.

After you've imported the Cognos BI report definitions, does perhaps the bi2bg utility pick up terms defined in tooltips?

This has been posted a number of times, with the consensus seeming to be that you can't make a list a parameter. However, you can make the entire SQL statement (with its list) a parameter.

If you deleted the VOC file you have completely invalidated your project. It will be almost impossible to get it working again. The project must have a VOC, and it is specific to that project. Hashed files have two parts, name and D_name. (There may be more if the hashed file is indexed.) Account-ba...

That data wouldn't generate those errors unless the metadata incorrectly specifies the field widths. Can you please post the record schema associated with those data?