topic Re: Not being able to read SAS dataset using libname in SAS Programming

Not being able to read SAS dataset using libname

abhik_giri — Wed, 09 Mar 2016 06:49:04 GMT

I'm not being able to read a particular SAS dataset (in sas7bdat format) into SAS using libname. Even obs=1 does not work. SAS gets hanged every time I run. I tried few times, but it doesn't work.

Re: Not being able to read SAS dataset using libname

Kurt_Bremser — Wed, 09 Mar 2016 07:29:42 GMT

Please post your libname statement and the log that you get when you execute it.

Then try to run a PROC CONTENTS on the dataset.

Re: Not being able to read SAS dataset using libname

LinusH — Wed, 09 Mar 2016 08:22:38 GMT

What's the origin of the data set? Perhaps it's create on some other host?

Perhaps it's corrupt. Try PROC DATASETS with REPAIR.

Can you create new data sets in the same libname?

Can you read other data sets in the same libname?

Re: Not being able to read SAS dataset using libname

abhik_giri — Wed, 09 Mar 2016 10:48:08 GMT

I tried "proc datasets library=your_lib; repair a; quit;. ". It says index of the dataset is damaged.

In the same libname, I'm being able to create new datasets as well as read other datasets.

Re: Not being able to read SAS dataset using libname

Kurt_Bremser — Wed, 09 Mar 2016 11:05:42 GMT

Then I'd use the hints provided here: http://support.sas.com/documentation/cdl/en/proc/61895/HTML/default/viewer.htm#a000247698.htm

to list, remove and recreate the damaged index(es).

Re: Not being able to read SAS dataset using libname

LinusH — Wed, 09 Mar 2016 11:49:02 GMT

"When you use the REPAIR statement for SAS data sets, it recreates all indexes for the data set"

So is it fixed after the REPAIR?

If not, share the full log from the REPAIR operation.

Re: Not being able to read SAS dataset using libname

ballardw — Wed, 09 Mar 2016 15:37:54 GMT

What version of SAS are you using?

Do you know who made the data set and which version of SAS was used?

SAS 9.4 datasets are not readable by version 9.2 32 bit at least. So if you have an older version of SAS that may be the cause.