Hi

Hope someone can assist
While doing release outbound OR even sales order data entry, we get
"Error 107 (Record is locked) on tiitm001770 (Max retries (10) exceeded )
Why is that so? How can we resolve this?
Pls advice
Thank you and have a nice day

Yours in service
dhnish

Hi Dhnish,

Change ora_timeout setting in db_resource. Error 107 means you have to wait until the other processes finished. So increase ora_timeout in db_resource.

Also restart you database and check for application lock

Refer to the Tools manual -
BaanERP Programmers Guide

107 ELOCKED - Record locked
--------------------------------------------------------------------------------
Description:
This error indicates that the record you are trying to retrieve is locked. You can either wait until the lock is released or remove the lock yourself.
Solution:
Wait until the lock on table is released or remove the lock.
or check for the Application Locks (ttadv9598m000) as Manoj suggested.
Also restart you database and check for application lock
Since you are on Oracle, check if there are any blocking locks, if so, then identify and kill them (if you have DBA previleges else ask your DBAs to do it).
Manoj, you do not restart/shutdown the database until its a critical/fatal issue in the business hours.

Hi

Released lock from Oracle level.
Thank you and have a nice day

Yours in service
dhnish
:)

hi,
I am getting the same error,
"Error 107 (Record is locked) on whinh270830 (Max retries (10) exceeded )"
My database is sql. Kindly help to solve this.

Thanks.

Regards,
Rajeshwari

Rajeshwari,

As mentioned in the thread -
check if there are any blocking locks, if so, then identify and kill them (if you have DBA previleges else ask your DBAs to do it).

How to identify blocking in SQL Server (https://www.mssqltips.com/sqlservertip/2429/how-to-identify-blocking-in-sql-server/)

Identify the cause of SQL Server blocking (https://www.mssqltips.com/sqlservertip/2927/identify-the-cause-of-sql-server-blocking/)

SQL SERVER – Quickest Way to Identify Blocking Query and Resolution – Dirty Solution (https://blog.sqlauthority.com/2010/10/06/sql-server-quickest-way-to-identify-blocking-query-and-resolution-dirty-solution/)

The DBA as Detective: Troubleshooting Locking and Blocking (https://www.red-gate.com/simple-talk/sql/database-administration/the-dba-as-detective-troubleshooting-locking-and-blocking/)

I'm sure you can Google search for the SQL server options based on the version.