DSXchange

Are the Teradata Utilities Foundation (TUF) or equivalent client software installed and configured properly on the DataStage Engine?

Is there an entry for localuv in the uvodbc.config file in each project?

Can you import the table definition for UniVerse table EXAMPLE1 in each project?

What's different?

Note: "nothing" is not the correct answer.

What error message(s) do you get in the second project?

Help us to help you.

Is it possible to build your string in a stage variable instead? If it has to be dynamic, perhaps the beginning and end of the range of codepoint values could be passed as parameters (assuming a contiguous range of characters).

Welcome aboard. This is not something you can achieve in a single parallel job.
However a server job may be your solution, as it supports the Connector having both an input and an output link.

What defines "reject" here? You can use a Transformer stage upstream of the XML Output stage. Or, perhaps, you can use the new XML stage, which does support reject links.

I'd start by asking the client what the data type of the target column should be.

They will probably go with BLOB.

Then you respond with the DataStage error message "unsupported data type" and advise them to use some other mechanism.

DB2 has BLOB-loading capabilities from external files.

Why are you using a Microsoft code page (character set) when running your server on UNIX? Try using ISO8859-1 or maybe even UTF-8. Is there any reason not to use NONE?

The single quotes may also be being stripped out. Try it with

That's the proof I requested. Fault type 11 (in UNIX this is signal #11, or SIGSEGV, also known as access violation) which suggests that something in the stored procedure, or in the process of invoking it, has attempted to access an area of memory not accessible to the process. It's really difficult...

The output table referred to is located in the IA database (IADB). It should be created automatically when you test a data rule definition or run a data rule or rule set.

Can you use Manage Tables to determine what tables exist in IADB?

The Change Capture stage takes advantage of the fact that the incoming data are sorted on the change key values, so that it only needs to be processing on change key value at a time in memory. Therefore there is no added detriment to the linear scaling you should see as you increase the number of ro...

Be very careful with terminology. CDC and Change Capture are quite different stage types.

Use a fork-join design to get the row counts, then filter those that have a count > 1 streaming that filtered set into a stage that performs the DELETE (for example an ODBC stage using the text file driver).

How do you know that the problem is in the Stored Procedure stage? Please post any error message that verifies this.