DSXchange

You can use the DataStage message handler to suppress warnings.

You can't do it with the Teradata API stage, because the Teradata API stage only runs in ANSI transaction mode. Use either the Teradata Connector or the Stored Procedure stage. Both of those stages support Teradata transaction mode. In Teradata transaction mode, any error will rollback the current t...

Check the DDL of the sync table and make sure that it has the following indexes: PRIMARY INDEX ( SyncID ) UNIQUE INDEX ( SyncID ,PartitionNo ,StartTime ) If it doesn't have both indexes, you'll need to get the Teradata Connector patch for JR29504 and drop your old sync tables so that the connector w...

If you are using RCP and truly had no columns defined, then you would not get a warning. The column definitions would be generated at run-time as a result of preparing the SELECT statement and there would be no type mismatch. The warning occurs when you define the column's data type in the Columns t...

When you define a field as NChar or set the Extended attribute of a Char to Unicode, the PX Engine uses a ustring representation for transmitting the data to the next stage. A ustring is in UTF16 format. If you are using ustring, then you should be setting the Teradata Connector's Client character s...

Locks are stored in the XMETALOCKINFO table. When a session terminates cleanly, the locks belonging to that session are removed from the XMETALOCKINFO table. If a session is not terminated cleanly because you killed the Designer client or the whole server went down without shutting down the WAS clea...

The schema reconcilation options won't get rid of that warning. That warning occurs when you specify the SQL yourself without using the Build button. The warning is harmless. You can ignore it.

As you discovered, that warning can occur when the connector's Client character set does not match the job's NLS map. The connector's default Client character set is UTF8, but a job's default NLS map is iso-8859-1. Whenever there is a mismatch in character sets, the connector must convert from the C...

Perhaps the character set in your job NLS map does not match the character set in your ODBC data source. If you have your NLS map set to ibm-1051_P100-1995, make sure your data source in .odbc.ini is set to an equivalent character set.

The only way you can dynamically set the table name in the Teradata Connector or Teradata MultiLoad stage is via a job parameter. And the only way to set a job parameter's value is when starting a job. You cannot change a job parameter's value midstream. If you need to dynamically set a table name m...

Another thing you could try is to have the first connector acquire an exclusive lock on the lookup table in Before SQL, and have it release that lock in After SQL after the surrogate key generation. The second connector's lookup will block until the first connector releases its lock. In order for th...

You cannot use Bulk mode for the reasons you just mentioned: - The connector does not know which rows were successfully inserted until the end of the job when the load completes. - The connector sends the success rows down the reject link before executing any After SQL. Why are you using Bulk mode? ...

What do you mean it doesn't work? That is exactly what the Drop option is for. If it's not working, get patches for Ecases 130419 and 130045.

It should be possible to do what you need using two Teradata Connectors in the same shared container. Have the first Teradata Connector do the Insert and add a reject link. On the reject tab, specify that Success rows should be sent down the reject link. Connect the other end of the reject link to y...

It's likely that those are not valid characters in the ASCII character set. Try using a client character set of UTF8.