RE: [U2] Locking Error (Maybe SB+, maybe UV)
UV File Triggers originated from UV SQL Table Triggers. Not surprising they enforce this requirement. Basic database programming stuff (I guess!), which is not the norm in PICK-style DBMS applications. ;-) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Charles Barouch Sent: Saturday, May 27, 2006 3:36 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] Locking Error (Maybe SB+, maybe UV) Mark, That appears to work. I'm really not sure why, though. I appreciate the help. -- Charles Barouch [EMAIL PROTECTED] - Consulting [EMAIL PROTECTED] - ETL/Migration/Integration (718) 762-3884x1 Mark Eastwood wrote: | If your Trigger Subroutine is going to Write, it must be first READU the item. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Locking Error (Maybe SB+, maybe UV)
1. Probably obvious but this I-trigger is running within a transaction so all item updates should be update-locked first (recordlocku, matreadu, readvu, etc). 2. Is there more than one i-trigger? 3. Is there an SB+ style index on your file? That may require other locks to be set manually. We have i-triggers on lots of different files that are fired from SB+ and non-SB+ routines alike. The only issue is when there's a basic program which updates one of those files using begin/end transaction and the i-trigger hiccups. I work around it by calling the i-trigger sub from within the transaction to compensate. (Hopefully IBM are working on that one). That's all I can think of off hand. -- Stuart Boydell [EMAIL PROTECTED] wrote: - To: u2-users@listserver.u2ug.org From: Charles Barouch Sent by: [EMAIL PROTECTED] Date: 27/05/2006 01:46 Subject: [U2] Locking Error (Maybe SB+, maybe UV) I'm getting this error and I don't know how to fix it. A full reboot hasn't helped: Program UPDATE.OI.GL.FROM.ORDER: Line 97, FATAL: The locks necessary for database operations at the current isolation level (0) are not held by this process. The program is a basic subroutine which is called by an index (this is an index trigger). I've recompiled the subroutine and rebuilt the index. The error line (97) is the MATWRITE command for the routine. When I trigger it from TCL it still works. When SB+ program triggers it, it fails with this errorr. It used to work everywhere. All help appreciated. -- Charles Barouch [EMAIL PROTECTED] - Consulting [EMAIL PROTECTED] - ETL/Migration/Integration (718) 762-3884x1 --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ * * This email message and any files transmitted with it are confidential and intended solely for the use of addressed recipient(s). If you have received this email in error please notify the Spotless IS Support Centre (+61 3 9269 7555) immediately, who will advise further action. This footnote also confirms that this email message has been scanned for the presence of computer related viruses. * * --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Locking Error (Maybe SB+, maybe UV)
If your Trigger Subroutine is going to Write, it must be first READU the item. Mark -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Charles Barouch Sent: Friday, May 26, 2006 8:47 AM To: u2-users@listserver.u2ug.org Subject: [U2] Locking Error (Maybe SB+, maybe UV) I'm getting this error and I don't know how to fix it. A full reboot hasn't helped: Program UPDATE.OI.GL.FROM.ORDER: Line 97, FATAL: The locks necessary for database operations at the current isolation level (0) are not held by this process. The program is a basic subroutine which is called by an index (this is an index trigger). I've recompiled the subroutine and rebuilt the index. The error line (97) is the MATWRITE command for the routine. When I trigger it from TCL it still works. When SB+ program triggers it, it fails with this errorr. It used to work everywhere. All help appreciated. -- Charles Barouch [EMAIL PROTECTED] - Consulting [EMAIL PROTECTED] - ETL/Migration/Integration (718) 762-3884x1 --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Locking Error (Maybe SB+, maybe UV)
Not too familiar with sb, but if it is re-opening the file, then any record locks are lost. A workaround MIGHT be to issue a RECORDLOCKU in the subroutine prior to the write. j On 5/26/06, Charles Barouch [EMAIL PROTECTED] wrote: I'm getting this error and I don't know how to fix it. A full reboot hasn't helped: Program UPDATE.OI.GL.FROM.ORDER: Line 97, FATAL: The locks necessary for database operations at the current isolation level (0) are not held by this process. The program is a basic subroutine which is called by an index (this is an index trigger). I've recompiled the subroutine and rebuilt the index. The error line (97) is the MATWRITE command for the routine. When I trigger it from TCL it still works. When SB+ program triggers it, it fails with this errorr. It used to work everywhere. All help appreciated. -- Charles Barouch [EMAIL PROTECTED] - Consulting [EMAIL PROTECTED] - ETL/Migration/Integration (718) 762-3884x1 --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ -- john --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Locking Error (Maybe SB+, maybe UV)
Mark, That appears to work. I'm really not sure why, though. I appreciate the help. -- Charles Barouch [EMAIL PROTECTED] - Consulting [EMAIL PROTECTED] - ETL/Migration/Integration (718) 762-3884x1 Mark Eastwood wrote: | If your Trigger Subroutine is going to Write, it must be first READU the item. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
