Job abort during AGG OR SORT
Moderators: chulett, rschirm, roy
Here is the settings i am using.
Rows coming in 1.2 million rows
Max Rows in VM = 49000
Max Open Files = 20
Temp File = explicit Full Path mentioned(i can also see files getting created therr)
tracing level = 0
Stable sort = no
esc char= \
column seperator = ,
Sort spec = Col1 ASC,COl2 ASC,Col3 ASC ...so on
Rows coming in 1.2 million rows
Max Rows in VM = 49000
Max Open Files = 20
Temp File = explicit Full Path mentioned(i can also see files getting created therr)
tracing level = 0
Stable sort = no
esc char= \
column seperator = ,
Sort spec = Col1 ASC,COl2 ASC,Col3 ASC ...so on
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You will never get any rows output from a Sort stage until all the input rows have been consumed. This is common sense - it does not know where the final row will be in the sorted order until it has been processed.
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.
Don't confuse my advice about how a properly configured Aggregator will run with what you see in the Sort stage, it must take in everything first. And the Server sort stage is pretty slow, in my experience I found an O/S level sort to be approximately 10x faster. YMMV.Nagaraj wrote:Okay the input link to the SORT stage has processed all the rows but the output link doesnt show any rows processed from a long time, does this mean it is not configured correctly????
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers