Re: "unlock" from trigger

From: <alee_at_bsiconsulting.com>
Date: Tue, 16 Jun 1998 14:30:20 GMT
Message-ID: <6m5vht$7ob$1@nnrp1.dejanews.com>

When the trigger kicks in to update the table, the update will set the lock mode to row exclusive which only the query and update are allowed. Since, the cron job is trying to lock the table in exclusive mode, it will experience ora-00054 error message cause by the trigger. My two cents advise is to let the update trigger finishes its query and let the cron job waits.

Hope this helps.

Alan Lee
BSI Consulting

In article <6m2hkj$3gk$1_at_mimir.ifi.uio.no>, ragnvald_at_nta.no (Ragnvald Torgeirsson Blindheim; UiO; V96) wrote:
>
>
> Hi.
>
> I need to be able to LOCK TABLE and unlock this table from a trigger.
> Problem is, the only way I have found to unlock a "LOCK" is to COMMIT.
> However, COMMITs are not allowed in triggers.
>
> Any suggestions?
>
> (the reason I use LOCK TABLE is that the trigger updates a table, and
> once in a while a UNIX cron job LOCKs the update table, exports the data
> and deletes all the data in the table. Using LOCK TAbLE in EXCLUSIVE MODE
> avoids concurrency problems).
>
> Any help appreciated!
>
> Ragnvald
>
> --
> Ragnvald T. Blindheim ragnvald_at_unik.no
>

-----== Posted via Deja News, The Leader in Internet Discussion ==----- http://www.dejanews.com/ Now offering spam-free web-based newsreading Received on Tue Jun 16 1998 - 09:30:20 CDT