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
gssr
Participant
Posts: 243 Joined: Fri Jan 09, 2009 12:51 am
Location: India
Post
by gssr » Mon Dec 21, 2009 9:46 am
I am merging two dataset to one
I find the error as follows,
<_PEEK_IDENT_> Input dataset does not have field: "sstatus".
Any idea about this....
RAJ
chulett
Charter Member
Posts: 43085 Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO
Post
by chulett » Mon Dec 21, 2009 10:01 am
I don't know... perhaps one of your input datasets does not have the field "sstatus"?
-craig
"You can never have too many knives" -- Logan Nine Fingers
gssr
Participant
Posts: 243 Joined: Fri Jan 09, 2009 12:51 am
Location: India
Post
by gssr » Mon Dec 21, 2009 10:11 am
One Input datset is having that field and i am merging with the other dataset..
The Job run finished ok with this warning....
When i try to use the output dataset as input in another job, the same warning came and the job gets aborted....
Any Suggestions....
RAJ
gssr
Participant
Posts: 243 Joined: Fri Jan 09, 2009 12:51 am
Location: India
Post
by gssr » Mon Dec 21, 2009 10:19 am
Other Warnings related to this are..
.
Code: Select all
When checking operator:The modify operator has a binding for the non-existent output field "sstatus".
When checking operator: The modify operator keeps field "sstatus" which is not present in the output interface
RAJ
chulett
Charter Member
Posts: 43085 Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO
Post
by chulett » Mon Dec 21, 2009 10:21 am
Search for those messages here, you're not the first person to ask about them.
-craig
"You can never have too many knives" -- Logan Nine Fingers
ray.wurlod
Participant
Posts: 54607 Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:
Post
by ray.wurlod » Mon Dec 21, 2009 1:56 pm
Is runtime column propagation (RCP) 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.
gssr
Participant
Posts: 243 Joined: Fri Jan 09, 2009 12:51 am
Location: India
Post
by gssr » Tue Dec 22, 2009 3:16 am
Yes, it was enabeled.....
RAJ
gssr
Participant
Posts: 243 Joined: Fri Jan 09, 2009 12:51 am
Location: India
Post
by gssr » Tue Dec 22, 2009 5:44 am
I tried to develop a new job for the same execution and its now running fine,
I still dont know which was the problem that throws the error..
I am going through it..
Thank you all for your comments,
RAJ