06-04-2014 03:46 AM
Currently I am using SAS Data Integrator Studio......I have created a simple SAS job.
Just I am joining two tables with around 22 lakh records each by using SQL join transformation, but I am getting the following error :
ERROR: Sort execution failure.
I have searched this error in google...and used these cmds
proc options group=memory; run;
proc options option=utilloc; run;
proc options option=threads; run;
options fullstimer msglevel=i ;
proc options option=workperms; run;
But still I am getting the same error.And in some site, they asked to incresease the sortsize and memsize....
Where to increase these size?
Kindly help.......Thanks in advance!!!!!!!
06-04-2014 04:08 AM
You may run out of disk space in your UTILLOC. If UTILLOC is not specified in your sasv9.cfg, then look at the free space in your WORK location.
Also consider to join the tables by using PROC SORT individually on each table and then do a merge in a DATA step; this is usually less intensive in disk space requirements.
You may also have a problem with permissions, see
06-04-2014 09:45 AM
Thanks KurtBremser for your reply....
But in sasv9 config file....I have this message
" Do NOT modify this file. Any additions or changes should be made in sasv9_usermods.cfg."
Can I edit in sasv9_usermods.cfg file? And Can I use the below cmd in my config file
"sas -memsize 1G -sortsize 512M " . Please help.
06-05-2014 01:31 AM
Yes, you can and should put your modifications in the sasv9_usermods.cfg, as that will not be overwritten if you apply a hotfix or similar.
Be sure to identify exactly which .cfg is the one for the server that DI Studio is using, there are several in your configuration tree.
Do not enter "sas -memsize 1G -sortsize 512M" in your config file, because that would be the complete commandline. Instead enter "-memsize 1G" and "-sortsize 512M" (without the quotes) on separate lines in the sasv9_usermods.cfg file.
If you still have problems, take a look at where the WORK library is created (SAS creates a new directory dynamically during startup and deletes it with all its contents at regular shutdown). You may run out of disk space there. If your tables are larger than your sortsize (which will happen sooner or later), SAS will need to create a utility file, and you always have a utility file with SQL.
06-05-2014 02:08 AM
As you are using DI there is a server installation (BI/DI).
That whole thing is having a metadata-server and more services.
Do not change the config or usermod files at the Foundation tree (installation).
These are system wide and should thought of settings related to the whole (virtual) machine.
For each appserver (SASApp) there is configuration tree with all kind of configuration-files
The structure has been a logical construct of nesting on autoexec's config's and scritpting. The implementation errors by SAS-inst can be ignored in your case.
The best place for adjustment of a user related config-file is the ../Levx/SASApp config_usermod file.
If you uses this name SASApp that will be easy to be found otherwise use the name appserver name you are using instead.
Ask your platform admin to do that change (if that is no you) as it is part of the installation/configuration.
08-12-2014 07:24 PM
What is your current MEMSIZE setting? With SAS 9.3 I have found that the SAS default insufficient, so increased it to 2GB. This value would need to be tested based on your own needs and environment though.
Also if you apply this change to your sasv9_usermods.cfg file in your SASApp folder, it will then apply to any SAS jobs running on this server, regardless of their type (batch, stored process, workspace etc)