--- In ib-support@yahoogroups.com, Helen Borrie <helebor@t...> wrote:

> At 09:58 AM 6/06/2003 +0000, you wrote:
> >Helen,
> >
> >is there any way to clear all the garbage ?
>
> Yes. Do a backup, and then a restore with the -c(reate) option,

specifying

> a different name.
>
> Then, shut down the original database and rename it. (If you can't

rename

> it, then it isn't stopped - someone is still logged in..)
>
> Zip up the renamed database and save to CD or some other media.
>
> Rename the restored database to the original name and move it to

the

> correct location.
>
> That's it.
>
> But you should definitely find out why your garbage collection is

being

> prevented. Look at your applications and user behaviour, to find

out where

> and why transactions are being left unfinished - otherwise your

problems

> will very soon recur.
>
> Did you drop the index from that binary column

(IsIndyInitialized)? That

> is the *most obvious* reason why your update is slow. You should

NOT index

> that column.
>

I have dropped the index. Actually I don't index it at the beginning.
I have tried by committing it after update. then the subsequent
update process is faster, about 1min30sec. it is still consider slow.
any suggestion to improve it ?

rgds, chooi-ting

> heLen