Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.
Moderators: chulett , rschirm , roy
keshav0307
Premium Member
Posts: 783 Joined: Mon Jan 16, 2006 10:17 pm
Location: Sydney, Australia
Post
by keshav0307 » Tue Sep 19, 2006 1:04 am
i am getting this error while inserting into a teradata table..
any idea what is causing this problem?
ray.wurlod
Participant
Posts: 54607 Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:
Post
by ray.wurlod » Tue Sep 19, 2006 1:07 am
The number of columns referred to in the INSERT statement is not the same as the number of columns in your DataStage job (or record schema).
Do you have runtime column propagation enabled?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
keshav0307
Premium Member
Posts: 783 Joined: Mon Jan 16, 2006 10:17 pm
Location: Sydney, Australia
Post
by keshav0307 » Tue Sep 19, 2006 1:42 am
Its exactly same as the target table schema, infact i import the table metadata only.
the runtime column propagation is disabled.
kumar_s
Charter Member
Posts: 5245 Joined: Thu Jun 16, 2005 11:00 pm
Post
by kumar_s » Tue Sep 19, 2006 6:22 pm
DS Metadata might match the table metadata, but check if the number of column given in the insert query is in equal number.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
keshav0307
Premium Member
Posts: 783 Joined: Mon Jan 16, 2006 10:17 pm
Location: Sydney, Australia
Post
by keshav0307 » Tue Sep 19, 2006 8:20 pm
Thanks Ray/kumar , your your suggestion.
i found the problem,there was a white space in the datastase name(i am paasing database name through parameter).
but i would like to know, the runtime column propagation should be enabled or disbaled?
kumar_s
Charter Member
Posts: 5245 Joined: Thu Jun 16, 2005 11:00 pm
Post
by kumar_s » Tue Sep 19, 2006 10:33 pm
Untill you have the same set of columns been propagated from the source till target, RCP shouldnt make any difference.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
ray.wurlod
Participant
Posts: 54607 Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:
Post
by ray.wurlod » Wed Sep 20, 2006 12:39 am
Disabled. RCP may aid developer productivity, but leads to a situation where lineage analysis can not be performed.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.