Re: Cooked dbspace...

Will Hartung - Master Rallyeist writes: > A client of of ours was playing with OnLine, and created a chunk on the > cooked file system. When he was done, he decided "Okay, I'm through." > and did an "rm mychunk" from. Note that he didn't bother to drop the dbspace > inside of OnLine. So now he has a dbspace that OnLine thinks it knows about, > but which doesn't exist. > Any ideas on how to drop it from OnLine? We've tried the quickie > cat /dev/null > mychunk > and tried to drop it, but OnLine complains that it's not empty. Isn't the problem that, once you've added a chunk, you can't drop it ? I added a cooked chunk to one of our test db's a while back, to verify that one of the guys in the field could add more db space easily. Only problem was that I couldn't find any simple way of getting rid of the cooked chunk on my test db afterwards. Very embarrassing, took about 3 hours to unload, reinitialize (without the cooked chunk :-) and reload. If there is a much better way, I'd be delighted to hear about it ... Cheers - Tony. PS. Sorry that this doesn't help ! __________________________________________________________________________ Tony Heskett th@bnr.co.uk Voice: (+44) 279 429531 x 2637 BNR, London Road, Harlow, Essex, CM17 9NA Fax: (+44) 279 454187