scratch folder filling very fast for a particular table
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 315
- Joined: Tue Oct 31, 2006 3:38 pm
scratch folder filling very fast for a particular table
I am writing an oracle table to a dataset and i am doing this for many tables. But for one particular table it is occupying lot of scratch space and i am running out of my disk space. Can someone let me know the exact reason?
Thanks
Thanks
I think there is some information missing that might explain this behaviour. Are you doing a straight load from table to dataset, and are you doing any sorting (implicit or explicit)?
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Premium Member
- Posts: 315
- Joined: Tue Oct 31, 2006 3:38 pm
thanks Andrw
my job is
oracle stage--->transformer--->join---->transformer--->dataset
In the oracle stage i set as table read and not a select query. As far as i know
i haven't set any sort option. i am using same kind of job for other tables. i don't see any problem with them. Please let me know if you need any particular info
Thanks
my job is
oracle stage--->transformer--->join---->transformer--->dataset
In the oracle stage i set as table read and not a select query. As far as i know
i haven't set any sort option. i am using same kind of job for other tables. i don't see any problem with them. Please let me know if you need any particular info
Thanks
-
- Premium Member
- Posts: 315
- Joined: Tue Oct 31, 2006 3:38 pm
Your design has a join with only one input, that was probably an oversight. The "tsort" files are from that stage.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Premium Member
- Posts: 315
- Joined: Tue Oct 31, 2006 3:38 pm
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Premium Member
- Posts: 783
- Joined: Mon Jan 16, 2006 10:17 pm
- Location: Sydney, Australia
-
- Premium Member
- Posts: 315
- Joined: Tue Oct 31, 2006 3:38 pm
If you using join stage then the procees will create the tsort file. First of all if you need all the column from your source then use read otherwise better to select the fields. Second your lookup table is very very small and the memory usage and performance of lookup stage doesn't depend on the source stream but depends on the lookup stream. So I think its better to use the lookup-stage instead of join.
-
- Premium Member
- Posts: 783
- Joined: Mon Jan 16, 2006 10:17 pm
- Location: Sydney, Australia