viral_a
28th December 2017, 06:52
We are getting Error 206 (Record is not locked) on tfgld417 in db_update.
Here’s the background:
1. Session Post integration transactions tfgld4201m000 is setup in a job (selection criteria is full range). The job is scheduled to run every 15 mins.
2. We also have another customized session. When the user performs a certain transaction using this session, tfgld4201m000 is automatically called for the appropriate Transaction Origin and Financial Transaction.
While the process runs smoothly, it does result in a 206 at times.
I am trying to understand the reason for 206 here. Could the issue be inherent with tfgld4201m000 itself or does the error arise because we have 2 instances of tfgld4201m000 which could running at the same point of time? Please suggest any pointers for me to investigate this further. Thanks!
Regards,
Viral.
Here’s the background:
1. Session Post integration transactions tfgld4201m000 is setup in a job (selection criteria is full range). The job is scheduled to run every 15 mins.
2. We also have another customized session. When the user performs a certain transaction using this session, tfgld4201m000 is automatically called for the appropriate Transaction Origin and Financial Transaction.
While the process runs smoothly, it does result in a 206 at times.
I am trying to understand the reason for 206 here. Could the issue be inherent with tfgld4201m000 itself or does the error arise because we have 2 instances of tfgld4201m000 which could running at the same point of time? Please suggest any pointers for me to investigate this further. Thanks!
Regards,
Viral.