What could be the reason for a locking problem in pro2sql on Windows sql side?
Lock wait timeout of 1800 seconds expired (8812)
That is what we found in the log file replproc20180213-1.log
How could we find which database this error is from?
I assume replication agent does not lock any records in the main Progress database.
Then it should be either pro2sqldsb or SQL schema holder....
Thank you Mike. We do not have any indexes at all on MSSQL side, other than the ones pro2sql has.
Do you know if there is a way to list ISOLATION LEVEL of all connected clients on SQL server database side?
1) "Lock wait timeout of 1800 seconds expired (8812)" - This error is from MSSQL
To control wait for initial lock , Keep below connection parameter in .pf file
-Dsrv PRGRS_NATIVE_LOCKWAIT,<n> # Controls wait for initial lock. Time in milliseconds.
2)To enable isolation level for connected clients, Keep below connection parameter in .pf file
-Dsrv TXN_ISOLATION,1 # Sets the default level to Read Uncommitted
4)Below wiki page might help
vprasad: pro2sql product comes from PSC with those parameters:
Mike, our MSSQL clients do not use ODBC. I can either check clients connection type on MSSQL side or I guess I can check _Lock on OE DataServer for MSSQL side....
Thanks Mike. I understand all of that and already start working with our MS folks to press them with ISOLATION LEVEL :)
I also set up a batch job on pro2sql Windows side to check _Lock table every 5 min. So far I did not catch any locks. Do you think that approach will work with fdm4repsh database? If not I will think of an other way to catch big fish. Obviously no one will confess here of using the wrong ISOLATION LEVEL.
I am looking for locks on MSSQL database of course. When I query _lock on our_db_name_repsh ( Schema Holder ), will I see anything interesting. I mean will I see any locks on MSSQL database? I can probably test it by locking something in MSSQL and checking _lock in Schema Holder....
Thanks. That is what I am looking for.