>I have thought trigger that cause the problem. However, the trigger
>is nothing to do with this field. Moreover, the update performance
>does not improve although I remove the trigger.

Well, then we need a lot more information to help you, because this statement

>When I issued the below sql query:
> update HistCurr set IndiInitialized = 1

by itself should execute within second(s) when the table contains only a
few thousand records.

Though there is one thing you haven't answered yet: What is the difference
between next transaction and oldest active transaction (OAT)? Another
question is if you run this statement by itself, or as part of a larger
operation, e.g. following a huge delete.

Set