"Your system is out of memory" for cost histogram.

Alex

Welcome to PP!

You are right, the project needs too much memory, but not due to the number of assignments - my biggest had more than 190000 activities with a huge amount of codes and assignments and it worked. There must be a misusage or a data failure.

I assume the reason for your project is a parameter "Drive activity dates by default" which is as a default for new activities in the view "Projects" --> tab "Resources" and in the view "Assignments" as a column for each assignment. It should be marked.
Make a security copy before marking the assignments.
Then write a Global Change to copy all durations (original, actual, remaining) and the Early Finish into a User Defined Field
then mark the assignments
then copy those values from the UDF into their fields again.

But pay attention: test with a copy before and check if my assumption was right. If not, run Tools --> check project integrity.

Good luck!
Dieter

Dieter,

Thank you very much for your reply. I tried it and I am still having problems.

I tried the method you mentioned (modifying the project) and also went so far as to create a whole new copy of the project and assign the resource with the default settings set as you suggested. I am still running out of memory. The integrity check passed.

I did find that if I simply divide the cost by 10, it will plot. It is slow, but it will plot. So, $374M worth of cost will not plot but 37.4M will plot slowly.

Someone here suggested that it may have something to do with our WBS structure being so large. We have about 1600 item WBS structure. What do you think?

Any other suggestions would be GREATLY appreciated. This is driving me crazy.

Hi Alex,

Dieter must have forgotten but I had a similar "out of memory" problem while producing a report. Try to check if your resource remaining durations fit into the project remaining duration. I had a case that the remaining early finish of a resource was way beyond ( I’m talking about decades!) the project end date.
For some reason P6 took the correct remaining units quantity but divided it by 1 remaining unit per day resulting in a very high number of remaining days.
So if you have a histogram with monthly periods, you end up with a memory demand for hundreds of columns, too much for a decent computer.
Dieters suggestion avoids this situation, it does not solve it.

Marcel

Marcel,

You’re correct. I wish your response came sooner.

I forgot to post the solution here but after about a week on the phone with Primavera, they told me that it had to do with the dates.

I had planned and remaining dates that went very far into the future. Some as far as Year 3623.

In my case, it was easier and more accurate to delete the resource completely, reassign it, and re-import the assignments (excel) instead of running a global change to make the dates correct.

Thank you all for your help. I hope this post and its replies will help someone else with the same problem.

-Alex