Re: Triggers & Data Mirror

["William Washington III" <w.washington3@xxxxxxxxxxxx>]

Hi Angela,

I've found it useful to not handle the file processing directly in the
database trigger, but just use the database trigger to send the file image
(before, after, or both depending on the app) to a data queue.  Then have a
batch process handle any required actions by reading the data queue.

This greatly reduces the risks of running into locks within your trigger and
crashing the application.  You've essentially decoupled the application from
the action you want the trigger to take.

Also, in all of your applications, make sure you're releasing the record
lock when you're finished.

Sorry, I can't speak to what Data Mirror is doing behind the scene.

Hope this helps...

William
===============================
William Washington III
Njia Systems Incorporated
w.washington3@njiasystems.com
===============================


> -----Original Message-----
> From: Angela Wawrzaszek [mailto:awawrzaszek@nucorauburn.com]
> Sent: Wednesday, October 24, 2001 10:37 AM
> To: Midrange Mail List (E-mail)
> Subject: Triggers & Data Mirror
>
>
> We are running Transformation Server from Data Mirror that mirrors AS/400
> data from our AS/400 to a SQL server and back.  The SQL server is pushing
> the data to our web site.  One of the files used is for customers to enter
> claims on the web site.  I set a trigger on this file to run *After
*Insert
> that will invoke a program that generates an email to our inside sales
that
> a claim has been submitted.  However when the trigger fires off I lock up
> the whole Transformation server process.  It is saying the record is
already
> locked to this job.  I have the tech group at Data Mirror looking at this
> but I didn't know if anyone here had any ideas.  I tried even changing the
> trigger job to just submit a job to run so that is didn't even open the
RPG
> program with the file interactively.  But this still locks it up.  Any
> help??
>
> Angela Wawrzaszek
> Nucor Steel Auburn
> IT Department