Error in "copy" operator

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

Post Reply
Mangesh123
Participant
Posts: 2
Joined: Fri Dec 18, 2009 5:01 am
Location: Oune

Error in "copy" operator

Post by Mangesh123 »

I have a job where am using copy stages , the input to copy stage is dataset..
While running the job I am getting following error
Syntax error: Error in "copy" operator: Error in output redirection: Error in output parameters: Error in modify adapter: Error in binding: Could not find type: "subrec", line 2538

Please help me to resolve this issue,

Thanks
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Did you try an exact search for Could not find type: "subrec" ? There are two other posts that mention that, see if anything there helps.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Mangesh123
Participant
Posts: 2
Joined: Fri Dec 18, 2009 5:01 am
Location: Oune

Post by Mangesh123 »

chulett wrote:Did you try an exact search for Could not find type: "subrec" ? There are two other posts that mention that, see if anything there helps.
I have already checked those two posts.
But they are not explaining much about the issue
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

Remove all stages except your dataset -> copy -> peek stages. Is the error still present? If yes, add "$APT_DUMP_SCORE" and set to "true" and run your job. Examine the score to see if that helps you, otherwise post it here.
ray.wurlod
Participant
Posts: 54595
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

One of your record schemas includes at least one subrecord. Find it and make sure it's being properly dealt with.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply