Fatal Error: sortRec
Moderators: chulett, rschirm, roy
Fatal Error: sortRec
I have a job which aborts immediately and the error shown in the log is:
main_program: Fatal Error: The input interface does not contain component "sortRec".
Any idea why this could be happening ?
Thanks in advance
main_program: Fatal Error: The input interface does not contain component "sortRec".
Any idea why this could be happening ?
Thanks in advance
Do you expect a column called "sortRec" in your input stream? What stages do you have? Have you tried to disable combination to see if you get a stage name that is causing the error?
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Please describe your job fully, including the stage types used and how they are connected. Post the generated OSH if you think that will help.
There should be an event in the log indicating which Orchestrate modules were loaded. Does orchsort appear in that list?
There should be an event in the log indicating which Orchestrate modules were loaded. Does orchsort appear in that list?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Premium Member
- Posts: 17
- Joined: Wed Dec 05, 2007 5:47 pm
Re: Fatal Error: sortRec
I am also facin this issue.
Please suggest your valuable comment on this.
Please suggest your valuable comment on this.
-
- Premium Member
- Posts: 17
- Joined: Wed Dec 05, 2007 5:47 pm
Re: Fatal Error: sortRec
I am also facin this issue.
Please suggest your valuable comment on this.
Please suggest your valuable comment on this.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Answer the questions that Havoc deigned not to.
Last edited by ray.wurlod on Sat Jul 29, 2017 4:03 am, edited 1 time in total.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Premium Member
- Posts: 783
- Joined: Mon Jan 16, 2006 10:17 pm
- Location: Sydney, Australia
-
- Premium Member
- Posts: 17
- Joined: Wed Dec 05, 2007 5:47 pm
Patch details?
Hi Keshav,
Do you have the patch details? Specific version#s?
Thanks
Do you have the patch details? Specific version#s?
Thanks
-
- Premium Member
- Posts: 67
- Joined: Thu Aug 09, 2007 7:51 pm
Re: Patch details?
I realize that this post is somewhat dated. I faced a similar issue in the recent past.
The job schematic (pertaining to the issue) is as below
The job used "Same" partitioning on both input links for the JOIN stage. In the aggregator stage that feeds to the JOIN stage, the colums were sorted as "case-insensitive" whereas the columns emanating from the Modify stage had the sorting based on case-sensitive option (default).
The job compiled fine at design time, but at run-time, the dreaded error message "The input interface does not contain component "sortRec"" was emitted.
IBM Engineering support was quite helpful in resolving this issue and came back with the following comment:
Although there's not a DataStage defect here, we're aware that the error message that's emitted, 'Fatal Error: The input interface does not contain component "sortRec"', is not very useful in identifying the cause of the failure. While it's not feasible to detect every erroneous job specification, instances such as the one in <stage_name> could be caught at design time; this is something we hope to address in a future release.
I think, when faced with this error, essentially it boils down to being meticulous about looking into each of the stages and hunting down the root cause of the issue. In my case, it was the "case", but could be different for others.
The job schematic (pertaining to the issue) is as below
Code: Select all
Modify Stage --------
Join Stage ------- Output
Aggregator Stage --------
The job compiled fine at design time, but at run-time, the dreaded error message "The input interface does not contain component "sortRec"" was emitted.
IBM Engineering support was quite helpful in resolving this issue and came back with the following comment:
Although there's not a DataStage defect here, we're aware that the error message that's emitted, 'Fatal Error: The input interface does not contain component "sortRec"', is not very useful in identifying the cause of the failure. While it's not feasible to detect every erroneous job specification, instances such as the one in <stage_name> could be caught at design time; this is something we hope to address in a future release.
I think, when faced with this error, essentially it boils down to being meticulous about looking into each of the stages and hunting down the root cause of the issue. In my case, it was the "case", but could be different for others.
-
- Participant
- Posts: 1
- Joined: Wed May 08, 2019 9:53 pm