Insufficient Memory ... proc SURVEYREG

[rcrs2]

Hi The,

It eventually turned out that I did not need that much memory, because the line "cluster _psu;" was to be removed. Plus, I got a funding to purchase a laptop with large RAM and fast CPU. Since then, I haven't encountered many problems...

BTW, do you also use the BRFSS data? If so, you may not really need cluster, because each cluster includes only one record, as far as I have checked.

Hope this help.

Rakkoo

[ezequias]

Is this topic about SAS Studio too?

I got the same message as you can evidence on the attached photo.

Regards

Ezequias.

[ChrisNZ]

As a general rule:
1. SAS studio is a front end. The memory issue in on the server. Where is your server? Look at the memory settings there.
2. If your server is 32 bits, you are very limited in terms of accessible memory. 64 bits (both OS and SAS) allows going beyond 3GB and as high as the hardware allows.
3. You must increase REALMEMSIZE (if enough RAM is available) and MEMSIZE (at least to slightly over REALMEMSIZE, and more if you don't mind the process paging). Paging means using disk as if it were RAM, and it make the process slow to a crawl but least be able to complete.

In your case:
2. Since your log looks like a Unix log, you are probably fine
3. These settings must be changed by the system admin as they are SAS startup parameters. For a server, paging is never desirable and the proper way to configure the option is to set MEMSIZE as high as possible and REALMEMSIZE as MAX. This will affect all SAS sessions started after the change in the configuration file.

[ezequias]

Dear @ChrisNZ I am using SAS Studio on the cloud. I have no server to perform those operations.

I didn't understand what you meant.

Sincerely

Ezequias Rocha

[ChrisNZ]

Where your SAS processes run is your SAS server.

Whoever set up SAS for you manages your SAS environment.

That person can increase the amount of memory available to you. 

If the could is managed by SAS Institute, then they would need to be contacted for this modification.

Your contract would presumably point you to the appropriate contact channels.

Does that make sense?

[ezequias]

Thank you for your reply @ChrisNZ unfortunately I have no contract with SAS. I am using the OnDemand modality as a university student.

I hope my evaluation would stop by now after this issue.

Best regards

Ezequias.

[ChrisNZ]

So you are probably stuck the the resources at hand.I would think they limit that to avoid people doing profesional processing on a student licence maybe?

[ezequias]

I can guarantee I do not make work efforts on SAS. I am only evaluating this tool to make any proposition on my company concomitantly with other providers.

Sincerely

Ezequias Rocha.

[ChrisNZ]

Evaluating a tool in an environment made for teaching students may be a good idea, but only if the limitations of that environment are taken into account.

If you don't, you might as well evaluate Usain Bolt's top speed in a sack race.

So do test the features, and there's may of them, but ignoring that you are using a restrained environment given to you freely is strange.

Arguing that the hardware limitations -that you chose by choosing this environment- are somehow to be held against the tool is stranger still.

In other words: the method of evaluation that you have chosen means that you are limiting yourself in terms of sizing, and the only thing you can therefore evaluate are the features.

[paul]

I experienced this problem almost 3 years ago as well.  After many conversations with SAS, they explained that there is a 2GB limit when using Surveyreg on Windows.  I don't know the exact technical details, but It is because Surveyreg has not been rewritten to properly handle Windows memory allocation.  There is nothing you can do on your end to fix this problem except change OS.  I converted our server from Windows to Linux and the same job that failed on Windows works fine on Linux.

[ChrisNZ]

@paul The logs seems to indicate a unix/linux server.

But a student OnDemand version apparently.