I am trying to write to a hashfile using "Allow Statge Write Cache" option set. I am facing the following warnings.
djsStgFidelityBackFill_QC_52..hshTmpFidRed.lnkNewColmns: Read link private caching enabled, cache size (128MB)
djsStgFidelityBackFill_QC_52..hshStgFidelityTmp.lnkOtherArrFidelityWrite: add_to_heap() - Unable to allocate memory
Here is it trying to read all data from the source then put it into cache from there trying to write to hahsfile, where the source data is huge compared to cache memory hence throwing the above warning? and what is the heap concept here?
My job has run though with warnings, does it mean that there is a chance that the data might not have loaded accurately?
Unable to allocate memory
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 730
- Joined: Tue Nov 04, 2008 10:14 am
- Location: Bangalore
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Probably not. But it wasn't able to use the read cache, because there was not enough space there for all the data. So it has read the hashed file from disk instead.
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: 730
- Joined: Tue Nov 04, 2008 10:14 am
- Location: Bangalore
Re: Unable to allocate memory
Heap concept.zulfi123786 wrote:what is the heap concept here?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers