DSXchange

Whoops a spelling mistake - what i meant to say was " i cant see why it WOULDNT work" using a direct insert rather than manual load

Hi. Having thought about this a little more, it now seems easier than i first thought. I have only used this method using the "manual" load, however, and not using a direct insert, i cant see why it would work. As you are already using the "custom" script, you are probably aware ...

Hi How long did this job run for? Did it fall over immediately, or did it process a number of rows (and if so, how many). I had a similar problem (though i forget the exact message, it did involve segmentation violation) when using the TDMLoad stage. In our case (PX 7.01, HP-UX) it was caused by an ...

Hi

Maybe it is too late to ask this question, but are you using the Teradata Multiload stage as the output?

I think it can be done, but it would be a long (ish) explanation, with no point if you arent using a Multiload stage :D

Hi I think this is possibly due to the database name missing - if there is no explicit database named in teradata i think that it looks to the default "user" database. Did you specify the database name in the TD enterprise stage? If not, in the stage, click on "Connection" and yo...

Hi

We experienced a similar error when we used user-generated SQL in a database stage.

Maybe you have a different number of columns defined in the 'Column' tab compared to the number of columns in the SQL select statement (if you ARE using and SQL statement of course )

HTH

L

Hi

May i ask where this problem is happening? I ask because "usually" the pad character becomes an issue in the sequential stage, and there is an option in that stage to over-ride the default padchar. Do you have any value in here? Or maybe you need a value in there?

regards
L

The first warnings, about the partitioning, can be removed by changing the Preserve Partitioning flag on the Stage-Advanced tab. If you set this to Clear then the message should disappear (this flag indicates to following stages that it should try to maintain the partitioning of the previous stage)....

Hi

We had a similar problem a little while ago, and if i remember correctly we just pressed the enter key when asked for the password.

Also, this warning is caused by a preceeding stage having the "Preserve Partitioning" flag set to "Propagate". This is the default value, and tells PX that it should attempt to maintain a partitioning method. Obviously the sequential stage can't preserve the partitioning. If this...