Error No Disk Space Is Available For The Write Operation
turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean Find a Community Communities Welcome Getting Started Community Memo Community Matters Community Suggestion Box Have Your Say SAS Programming Base SAS Programming SAS Procedures ODS and Base Reporting SAS/GRAPH and ODS Graphics General SAS Programming SAS Studio Data Management SAS Data Management Analytics SAS Statistical Procedures SAS/IML Software and Matrix Computations SAS Data Mining SAS Text and Content Analytics SAS Forecasting and Econometrics Mathematical Optimization, Discrete-Event Simulation, and OR Business Intelligence SAS Enterprise Guide Integration with Microsoft Office SAS Visual Analytics SAS Web Report Studio SAS Stored Processes Administration Administration and Deployment SAS Hot Fix Announcements SAS ITRM Learn SAS SAS Analytics U SAS Certification Customer Intelligence SAS Customer Intelligence SAS Intelligent Advertising Risk Management SAS Risk Management SAS Viya About SAS Viya SAS Visual Data Mining and Machine Learning Coding on SAS Viya SAS Visual Investigator Health Care and Pharma SAS in Health Care Related Fields SAS Drug Development SASware Ballot Ideas Regional Groups Special Interest Groups SAS Community Denmark SANZOC CoDe SAS German SAS Visual Analytics Nederland Singapore SAS Global Forum 2017 SAS Communities Library Home / SAS Programming / SAS Procedures / Getting ERROR of "No disk space is available for w... Getting ERROR of "No disk space is available for write operation" for utl table, although there are still a lot of space in the work library while running SAS in batch mode Solved Reply Topic Options Subscribe to RSS Feed Mark Topic as Ne
a database in excess of 56gb I repeatedly received this error message "ERROR: No disk space is available for the write operation". When working in SAS all procedures take place wherever the temp folder is located, which is true even if youreferencea different librarywith alibname statement. The library is the final resting ground for the data, yet all procedures are performed in that temp folder. The problem I encountered was because my computer's hard drive was ~110 https://communities.sas.com/t5/SAS-Procedures/Getting-ERROR-of-quot-No-disk-space-is-available-for-write/td-p/138466 gb and the file was ~56gb. I have a network folder that is 250gb, but first I needed to figure out how to designate that drive for my SAS temp folder. I was unable to find a solution online, so I wanted to share my ultimate solution. The temp drive and folder I wished to use was "M:\SAS temp" http://sasbeginner.blogspot.com/2011/02/error-no-disk-space-is-available-for.html 1.) Locate the config file called "SASV9.CFG" 1a.) My location was "C:\Program Files\SAS\SASFoundation\9.2\nls\en" 2.) Create a back-up config file, just in case. 3.) Open SASV9.CFG 3a.) Under the warning box, about 5 lines down it states /*setup the default SAS System user work folder */ 3b.) You will want to change this path to wherever you want your new temp file, so it should read: /*setup the default SAS System user work folder */ -WORK "M:\SAS temp" 4.) Save and close this file 5.) Open sas.exe in "C:\Program Files\SAS\SASFoundation\9.2" The problem should be solved and all temporary files, including the work library, will now be saved in this location. A final note, network drives may run significantly slower. Therefore, it may be wise to switch back your temp folder once you have completed running this larger file. Good Luck! Posted by SASguru at 7:11 AM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: Error messages No comments: Post a Comment Older Post Home Subscribe to: Post Comments (Atom) SAS Labels Error messages (1
201006091830.o59Aumau004980 () malibu ! cc ! uga ! edu [Download message RAW] That should be no problem between 9.1 http://marc.info/?l=sas-l&m=127610825818498 and 9.2. However you might have your work-directory on another disk which is smaller (or already full) that the 9.1 one. Have a look where saswork is located and check the disk-space. It seems to be on c:, normally a local disk. Most installations I know have rather small partitions for system files on c: and error no have a big one (or more) for data, sometimes d: or e: or... If you are on the same hardware with 9.1 AND 9.2, maybe you kept the 9.1 installation alive (or dead) and added 9.2. That might be a show-stopper. Or you removed 9.1 and 9.2 simply needs more space for the installation? A solution might error no disk be to buy a new harddisk. Disk space is not expensive. Gerhard On Wed, 9 Jun 2010 14:20:13 -0400, Subscribe Sas-L Jkr