it's strenge to me !! HELP

I try to do the folowing statement : alter fragment on table <tabname> init in <dbsname>after filled 5 logical logs I have a long transaction error. But I have 20 logical logs and my LTXHWM and LTXEHWM environnement variables are equal respectevly to 50 and 60, so I expected that I can go to 10 logical logs. other stringe thingth is that I have the flag U-B to all my logical logs (exept the logs with the actual check point: U---C-L), I have tried to get the status F to all my logical logs so I have take the online to quiscent mode, but the flags are still U--B. my LTAPEDEV is /dev/null. so plaese help me to resolve this problem and enderstand what's going on !! ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com

samir BADAOUI wrote: > > I try to do the folowing statement : > alter fragment on table <tabname> init in <dbsname>> after filled 5 logical logs I have a long transaction error. But I have 20 > logical logs and my LTXHWM and LTXEHWM environnement variables are equal > respectevly to 50 and 60, so I expected that I can go to 10 logical logs. > other stringe thingth is that I have the flag U-B to all my logical logs > (exept the logs with the actual check point: U---C-L), I have tried to get > the status F to all my logical logs so I have take the online to quiscent > mode, but the flags are still U--B. > my LTAPEDEV is /dev/null. > so plaese help me to resolve this problem and enderstand what's going on !! First, it is rare for the logs to actually be marked status F, but that is OK if status is U--B and the checkpoint (L) is beyond that log (ie in a log with a higher uniqid) then the log can be reused. Your problem is probably that the checkpoint was already 5 logs behind the current log when the ALTER began or that there was an open transaction already in one of the prior 5 logs before the ALTER began. Are you backing up logs continuously or through the ALARMPROGRAM? This can help somewhat. Otherwise you will just have to add more logical logs. Art S. Kagel

In article <37F90B1B.BC31BBAA@bloomberg.net>, kagel@bloomberg.net wrote: > samir BADAOUI wrote: > > > > I try to do the folowing statement : > > alter fragment on table <tabname> init in <dbsname>> > after filled 5 logical logs I have a long transaction error. But I have 20 > > logical logs and my LTXHWM and LTXEHWM environnement variables are equal > > respectevly to 50 and 60, so I expected that I can go to 10 logical logs. > > other stringe thingth is that I have the flag U-B to all my logical logs > > (exept the logs with the actual check point: U---C-L), I have tried to get > > the status F to all my logical logs so I have take the online to quiscent > > mode, but the flags are still U--B. > > my LTAPEDEV is /dev/null. > > so plaese help me to resolve this problem and enderstand what's going on !! > > First, it is rare for the logs to actually be marked status F, but that is > OK if status is U--B and the checkpoint (L) is beyond that log (ie in a log > with a higher uniqid) then the log can be reused. > > Your problem is probably that the checkpoint was already 5 logs behind the > current log when the ALTER began or that there was an open transaction > already in one of the prior 5 logs before the ALTER began. Are you backing > up logs continuously or through the ALARMPROGRAM? This can help somewhat. > > Otherwise you will just have to add more logical logs. > > Art S. Kagel > I have to admit, this isn't making sense to me either... If your LTAPEDEV is /dev/null, then as soon as a logfile fills, as long as the last checkpoint isn't in that logfile, or a transaction isn't still open, that logfile is marked as "backed up". That's why all of your logs seem to be backed up ("U-B"). Is it possible that you have changed your LTXHWM and LTXEHWM parameters, and not bounced the engine? If so, you will have to bounce it for the changes to take effect. Other than that, I'm perplexed. It doesn't sound like you're filling your logs, since they indicate that they've been backed up already. Let us know if you have any success. -- Dan Michaelis Database Administrator dan@kax.com Sent via Deja.com http://www.deja.com/ Before you buy.

In article <7td0c0$ucl$1@nnrp1.deja.com>, Dan Michaelis <dan_michaelis@my-deja.com> writes >Other than that, I'm perplexed. It doesn't sound like you're filling >your logs, since they indicate that they've been backed up already. >Let us know if you have any success. > They may have been backedup but they cannot be reused until they do not contain any open transactions. SO more smaller logical logs is better (you can have up to 32767 logical logs, 250Kb is the minimum size). >-- >Dan Michaelis >Database Administrator >dan@kax.com > > >Sent via Deja.com http://www.deja.com/ >Before you buy. -- David Williams