Import on a table having insert trigger that updates the inserted record
waited 4 hours before continuing. One second after completion of this Import
db2diag.log tells:
------------------------------------------------
2004-02-11-07.07.17.199000 Instance:IDWH03 Node:000
PID:2256(db2syscs.exe) TID:2132 Appid:*LOCAL.IDWH03.040211020029
data_management sqldFindPageFromFSCR Probe:111 Database:QUELLE01

Page was victimized.fd0d 0000 ý...
------------------------------------------------


This is on DB2 UDB 7.2. Fix 10 on Win2000

Thanks
Klemens

Klemens,

Not the answer you are looking for but:
Why does youe trigger come back to update the same row?
Shouldn't this be a before trigger?

Cheers
Serge



--
Serge Rielau
DB2 SQL Compiler Development
IBM Toronto Lab

I created this trigger years ago. So I don't know if there were such
restrictions on before trigger that time or if I reused triggerdefinitions
created for other more complex solutions. Today I would fill that file with
the complete data for import.
If the problem persists and the trigger may cause the problem, I will
redesign the solution.

Klemens

"Serge Rielau" <srielau@ca.eye-be-em.com> schrieb im Newsbeitrag
news:c0d408$9cl$1@hanover.torolab.ibm.com...[color=blue]
> Klemens,
>
> Not the answer you are looking for but:
> Why does youe trigger come back to update the same row?
> Shouldn't this be a before trigger?
>
> Cheers
> Serge
>
>
>
> --
> Serge Rielau
> DB2 SQL Compiler Development
> IBM Toronto Lab[/color]