Page 1 of 1

OpenLink][ODBC][Progress Server]Failure getting record lock

Posted: Wed Jun 11, 2008 12:28 am
by G SHIVARANJANI
Hi,

I am getting the following error

OpenLink][ODBC][Progress Server]Failure getting record lock on a record from table PUB.Client.

when another online application has locked the table 'client' for update or delete.

And this happens even when i read i.e even when i do select records from the table

Is it possible that both the ETL and the other online applications run simultaniously whithout abort.

Please suggest.

Re: OpenLink][ODBC][Progress Server]Failure getting record l

Posted: Wed Jun 11, 2008 3:07 am
by G SHIVARANJANI
G SHIVARANJANI wrote:Hi,

I am getting the following error

OpenLink][ODBC][Progress Server]Failure getting record lock on a record from table PUB.Client.

when another online application has locked the table 'client' for update or delete.

And this happens even when i read i.e even when i do select records from the table

Is it possible that both the ETL and the other online applications run simultaniously whithout abort.

Please suggest.

Re: OpenLink][ODBC][Progress Server]Failure getting record l

Posted: Wed Jun 11, 2008 8:13 am
by G SHIVARANJANI
Any suggestions..

Posted: Wed Jun 11, 2008 8:39 am
by chulett
If anyone did, they would post them.

Have you talked to your Progress DBA about this? My Progress days are way behind me so can't really offer any concrete advice except to see if there's any way to do a 'dirty' or 'uncommitted' read over ODBC. That's a 'standard' way to get around record locks but not sure it will help with table locks, you may be out of luck there.

Talk to your DBA.

Posted: Wed Jun 11, 2008 9:18 am
by G SHIVARANJANI
Hi,

Could you please throw light on ' 'uncommitted' read over ODBC. '
chulett wrote:If anyone did, they would post them.

Have you talked to your Progress DBA about this? My Progress days are way behind me so can't really offer any concrete advice except to see if there's any way to do a 'dirty' or 'uncommitted' read over ODBC. That's a 'standard' way to get around record locks but not sure it will help with table locks, you may be out of luck there.

Talk to your DBA.

Posted: Wed Jun 11, 2008 9:57 am
by chulett
Google should turn up a ton of links on the subject, for example this one. The concepts are similar across all databases.

Again, questions like this really need to either go to your DBA for Progress specific answers or through your official support provider back to the vendor for guidance, unless (of course) someone here as done this and posts a solution for you.

Posted: Wed Jun 11, 2008 10:31 am
by G SHIVARANJANI
Thanks Craig
chulett wrote:Google should turn up a ton of links on the subject, for example this one. The concepts are similar across all databases.

Again, questions like this really need to either go to your DBA for Progress specific answers or through your official support provider back to the vendor for guidance, unless (of course) someone here as done this and posts a solution for you.