Search found 79 matches
- Tue Apr 10, 2012 10:06 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: teradata connection delete issue
- Replies: 3
- Views: 3032
- Tue Nov 18, 2008 12:41 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Multiple update statment in teradata API stage.
- Replies: 1
- Views: 2352
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...
- Tue Nov 11, 2008 2:05 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: TPT(teradata parallel transporter) error
- Replies: 4
- Views: 3801
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...
- Mon Nov 10, 2008 1:37 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Teradata String conversion Warnings
- Replies: 10
- Views: 14538
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...
- Fri Nov 07, 2008 12:25 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Teradata String conversion Warnings
- Replies: 10
- Views: 14538
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...
- Thu Nov 06, 2008 12:38 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Unable to unlock jobs in v8
- Replies: 16
- Views: 11098
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...
- Thu Nov 06, 2008 12:28 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: teradata connection delete issue
- Replies: 3
- Views: 3032
- Thu Nov 06, 2008 12:23 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Teradata String conversion Warnings
- Replies: 10
- Views: 14538
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...
- Thu Nov 06, 2008 12:14 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Invalid Character warnig in datastage
- Replies: 4
- Views: 6678
- Thu Nov 06, 2008 12:07 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Adding New Job Parameter from PX routine
- Replies: 9
- Views: 4746
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...
- Thu Oct 30, 2008 12:41 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Teradata Connector Read/Write issue
- Replies: 7
- Views: 8672
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...
- Thu Oct 30, 2008 12:27 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Teradata Connector Read/Write issue
- Replies: 7
- Views: 8672
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? ...
- Thu Oct 30, 2008 11:20 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: TD Enterprise stage replaced with TD connector stage issue
- Replies: 3
- Views: 2160
- Thu Oct 30, 2008 11:03 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Teradata Connector Read/Write issue
- Replies: 7
- Views: 8672
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...
- Thu Oct 23, 2008 1:51 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Issues with exporting characters from Teradata connector
- Replies: 2
- Views: 2453