Date:         Wed, 10 Jan 2007 06:37:50 -0800
Reply-To:     RolandRB <rolandberry@HOTMAIL.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         RolandRB <rolandberry@HOTMAIL.COM>
Organization: http://groups.google.com
Subject:      Re: Copy of dataset corrupted with OS tools
Comments: To: sas-l@uga.edu
In-Reply-To:  <82C4208201BE3645B6840015C9DD2CBAB45E87@bhqroc1ex2.archq.ri.redcross.net>
Content-Type: text/plain; charset="us-ascii"

Ed Notari wrote:
> Hello folks,
>
> We recently had a moderately large dataset that corrupted during a copy.
> We run an Alpha system with Tru64 UNIX v5.1A.  The dataset was just
> created on a RAID 5 volume and was copied ("cp" command) to another RAID
> 5 volume on the same SAN.
>
> The corruption was insidious (19 records out of 80,000,000) and
> clustered, as far as I can tell.  The byte size of the files were
> identical, and a simple PROC CONTENTS doesn't show anything odd (no
> surprise).  None of the logs (binary.errlog, etc) showed any odd
> behavior during the time the file was transferred or afterward.
>
> The upshot of all of this is;
>
> 1) What are SAS folk using to assure that copying datasets has worked?
> 2) Do I need to "touch" each record to verify the starting dataset is
> the same as the ending dataset?
>
>
>
>
> Ed Notari
> Transmissible Diseases Department
> Jerome H. Holland Laboratory
> American Red Cross

Did you run a PROC COMPARE to compare the dataset before and after and
was it this that showed up the problem?