Re: Freeing Logical Log with Status U

what do you mean logical logs in a round robin fashion? I don't see any advantage on having logical logs 1,3,5 on one disk and 2,4,6 on another. Wouldn't be the same as having 1,2,3 on disk 1 and 4,5,6 on disk 2? Am I missing something? "David MacAllister" wrote in message <64f498$en2@cssun.mathcs.emory.edu>... >Hello Clever Folks > >I'm looking for a little assistance. I've created new dbspace for physical >and logical logs, and have indeed created 2 spaces for logical logs on >separate disks, in order to reduce contention in rootdbs. > >After doing a level 0 archive I managed to move the physical log to the >dbspace I've set up and have moved 5 of my logical logs into their >respective spaces in a round-robin fashion. > >Here's the problem, after doing onlog -l to move to the next logical log >in the new dbspace, I'm left with one logical log in rootdbs, with a status >U, and when I try to drop this error message appears stating that logical >log with status U cannot be dropped. >I've since done another level 0 archive, and still the status of the log >remains unchanged as status U. I then did a quiescent backup and the >status is still U. > >Can anyone help me drop them !!!!! > >Cheers > >David >Sorry I forgot to mention > >Informix OnLine 7.12.UC4 INDIVIDUAL LOGICAL LOGS > >Number Uniqid Flags Pages Used % Used Dbspace > > 1 31 U---C-L 250 48 19.20 logical_space_1 > 2 0 F------ 250 0 0.00 logical_space_2 > 3 0 F------ 250 0 0.00 logical_space_1 > 4 0 F------ 250 0 0.00 logical_space_2 > 5 0 A------ 250 0 0.00 logical_space_1 > 6 30 U------ 250 59 23.60 rootdbs