Page 1 of 1
Teradata Connector load using Bulk mode
Posted: Wed Sep 28, 2011 10:48 pm
by swadeep
Hi,
I am trying to load to Teradata using TD Connector Stage.
Job Design
DataSet----Transformer----TD Connector(Access Method - Bulk and Load type - Load)
Job is failing with error
Error tables are invalid OR <tablename> is in an invalid state for Load
Main table is one database and error and log tables are in different database.
No locks on Main table,
Thanks in Advance
Posted: Thu Sep 29, 2011 1:26 am
by iskapalli
Hi,
Please share the exact error message in datastage director.
Re: Teradata Connector load using Bulk mode
Posted: Thu Sep 29, 2011 7:36 am
by chulett
swadeep wrote:Main table is one database and error and log tables are in different database.
This concerns me. If they are truly in "different databases", wouldn't they require different connection details? I'm sure the stage is only asking for one. Is this even supported outside of DataStage?
Posted: Thu Sep 29, 2011 9:27 am
by fridge
On teradata the term database is a bit more like a schema in DB2 / Oracle - i.e same physical database instance - but in a different location within that database.
This is a bad analogy but havent much time - however when querying a table you would type
select * from <database>.<tablename> - and it is the first bit that could be the issue, if omitted it defaults to the 'database' specified in the connector stage
am not on datastage at mo - but maybe worth checking how you have specified the Error table and Log Table names in the connector stage (i.e. have you used the <database>.<errortable> notation - and is it differnet to the main table notation
Posted: Thu Sep 29, 2011 9:32 am
by chulett
No worries, if database = schema then never mind.
![Wink :wink:](./images/smilies/icon_wink.gif)
Posted: Sun Oct 02, 2011 10:17 am
by ppgoml
as far as I know, TD fastload requires an empty target table.
Posted: Sun Oct 02, 2011 4:32 pm
by ray.wurlod
DataStage TD Connector includes some clever code that allows fastload to append.
Posted: Mon Oct 03, 2011 10:19 am
by mandyli
As per fast Load whenever the job aborted you have clean up the ERROR table.
So ask your DBA to clean up the ERROR table and then try to rerun. Before reruns ask DBA to check the proper permission is there for your id or application id.
Thanks
Man