No I was thinking more along the lines of O/S level file permisisons. Which is why I had *you* create a new file, that way your permissions and its permissions would be known to match.
-----Original Message----- From: Jeffrey Butera <jbut...@hampshire.edu> To: u2-users <u2-users@listserver.u2ug.org> Sent: Tue, Apr 23, 2013 10:27 am Subject: Re: [U2] Unidata RESIZE CONCURRENT On 04/23/2013 12:04 PM, Wjhonson wrote: > Try a different file, that A) you have just created and B) you know certainly is not being used. Same result. Created brand new file from scratch, copied 2000 records into it and attempted to resize: :CREATE.FILE JVB.RSZ 1029,1 :SELECT PERSON SAMPLE 2000 :COPY FROM PERSON TO JVB.RSZ :RESIZE JVB.RSZ 1237,1 CONCURRENT Resize Concurrent Continue/Restore failed because the RESIZE_CONCURRENT bit was not set on the file. Nobody could've been accessing this file other than me. To be clear - we're not running RFS or replication in our database. > I don't think the "bit" is the issue here. I think that's just a message > like "can't GET the file...." OK, but I guess I'm confused. I thought that was the whole point of CONCURRENT - it could resize the file while others were accessing it. Are you claiming that RESIZE CONCURRENT must (initially) have exclusive access and then, while resizing, it's OK if others happen to access it? -- Jeffrey Butera, PhD Associate Director for Applications and Web Services Information Technology Hampshire College 413-559-5556 http://www.hampshire.edu http://www.facebook.com/hampshirecollegeit _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
