Time Out waiting for mutex
Moderators: chulett, rschirm, roy
Time Out waiting for mutex
Hi everyone,
I searched through all the posted of mutex issues in this forum.
But it doesn't help to fix my jobs.
I have a job using IPC stage and getting this 'ds_ipcput() - timeout waiting for mutex'. I used default buffer size (128) and time out (10) previously and increased buffer size like 258 , 1000 and tested again.
Tried to increased the waiting time as well. But still have this error.
May I know how I can calculate buffer size and time out to overcome this?
Note: The job is running successfully with 1 million of records, but come to 2.3 million of records and then gave above problem.
Following is my job design:
ODBC --> IPC --> Agg -->Agg--> Seq file
|
Tranformer -->Agg--> Seq file
Thanks a lot,
sansan
I searched through all the posted of mutex issues in this forum.
But it doesn't help to fix my jobs.
I have a job using IPC stage and getting this 'ds_ipcput() - timeout waiting for mutex'. I used default buffer size (128) and time out (10) previously and increased buffer size like 258 , 1000 and tested again.
Tried to increased the waiting time as well. But still have this error.
May I know how I can calculate buffer size and time out to overcome this?
Note: The job is running successfully with 1 million of records, but come to 2.3 million of records and then gave above problem.
Following is my job design:
ODBC --> IPC --> Agg -->Agg--> Seq file
|
Tranformer -->Agg--> Seq file
Thanks a lot,
sansan
Re: Time Out waiting for mutex
What Aggregation are you using?sansan wrote:Hi everyone,
I have a job using IPC stage and getting this 'ds_ipcput() - timeout waiting for mutex'. I used default buffer size (128) and time out (10) previously and increased buffer size like 258 , 1000 and tested again.
Tried to increased the waiting time as well. But still have this error.
Note: The job is running successfully with 1 million of records, but come to 2.3 million of records and then gave above problem.
sansan
If it is other than count(*) then, try the same with sorted data (you can use order by in other caluse), based on the columns which are grouped by in the Aggregator.
May be this will help you solve your problem.
Success consists of getting up just one more time than you fall.
Could you please explain to me where the sort needs to be added? Is it in the Aggregator stage? Or in the Transformer?sansan wrote: Columns were grouped by ODBC stage are different from Agg stage and so I will try to use same columns used in agg stage to group by in ODBC stage.
I haven't used DataStage for a while and I'm very rusty.
The job has the following sequence:
Oracle Stage --> Transformer --> Aggregator --> Transformer --> ODBC
Thanks for your help.
Yes, in your first OCI stage, in your select, you need to add 'order by' clause to sort the data. Its upto you to sort by as many columns as you want. The sort order must be the order of group by's in the aggregator.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
I need more help with some basics. In the Aggregator, under Inputs --> Columns, there are two columns Sort and Sort Order. Do I need to enter anything into Sort column? There is a dropdown box in the Sort Order column. The options are ignore, descending, ascending. No matter what I select, it dispappears as soon as I move to the next field/row. What am I doing incorrectly.DSguru2B wrote: Let the aggregator know what keys the incoming data is sorted on.
Thanks.
You need to supply the order of sort. Which depends upon your order by's.
For eg. if in your sql you have
order by col a, col b, col c
Then in your aggregator you need to specify for
if you dont supply the sort num, the sort will dissappear no matter what you select from the drop down. For more info, read about the aggregator stage in your dsbooks.
For eg. if in your sql you have
order by col a, col b, col c
Then in your aggregator you need to specify for
Code: Select all
column name sort sort num
col a ascending 1
col b ascending 2
col c ascending 3
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
-
- Premium Member
- Posts: 209
- Joined: Fri Jan 09, 2004 1:14 pm
- Location: Toronto, Canada
- Contact:
If you can do the sort as part of your database read, do it there! The database will be much, much faster then DataStage.
Then the sort in the aggregator, while it won't hurt, will be incidental, as suggested by Guru (or is that Chuck? )
Just make sure the order by clause in your SQL is the same as the grouping in your aggregator!
Rob
Then the sort in the aggregator, while it won't hurt, will be incidental, as suggested by Guru (or is that Chuck? )
Just make sure the order by clause in your SQL is the same as the grouping in your aggregator!
Rob
Rob Wierdsma
Toronto, Canada
bartonbishop.com
Toronto, Canada
bartonbishop.com