Dmitry Yemanov wrote:

> Jaison Joseph wrote:
>
>>> How wide are records of trg_trg?
>>>
>> CREATE TABLE TRG_TRG
>> (
>> TRG_ID Integer,
>> TRG_EMP_ID Integer,
>> TRG_DTTM Timestamp,
>> TRG_CODE Integer,
>> TRG_PRSD Smallint DEFAULT 0,
>> TRG_TRD_ID Integer,
>> TRG_DOR_CODE Varchar(16),
>> TRG_DEV_ID Integer,
>> CONSTRAINT PK_TRG_TRG PRIMARY KEY (TRG_ID)
>> );
>>
>
> Hmmm. Not wide at all, I'd say.
>
> Out of curiosity, how many record versions does this table have?
>

Sorry, I don't know how to retrieve that value (I spent some time
searching this in the net). Someone please help me.

If you want, I shall email the test db (privately) to you, for further
investigation. It is less than 2 MB when zipped.

> Regardless, you have to find a workaround on your side, I doubt any
> server side optimization is possible in this case.
>
>
> Dmitry
>

Thank you very much for your time. We decided to move the second update
outside the transaction with a little modification in the design.

Thanks,
Jaison Joseph