With a 4GL dev license you should be able to use the data dictionary to dump the tables to files or write 4GL code to export the tables to CSV files and then load into MS SQL server. There are multiple examples on 4GL code to export to csv files.
Generate a protrace file on the user holding the lock and you will see what code is being executed. Our lock monitor would generate a protrace file on a user holding a lock when there was another user Q'd waiting. In Linux the protrace file goes to the Current Working Directory and has the PID...
seems like when reverting back to OEM 10 something is still pointing at OE 11.
"Invalid Progress version string"
Suggest turning the logging up and see what additional information is produced from running proadsv
Uggg. Even if you are stuck on Progress 9, run a dump and load to move from a 1kb block size to 4 or 8kb.
Next step would be to look at the structure file and see if everything is in the schema area...
quickly read through your previous post, guessing there is an issue with Q'd record locks.
There are a few posts on ProgressTalk that talk about scanning the _Lock table to find the connection holding a lock that has other connections Q'd behind it. There should be a few warnings sprinkled in...
Does your live system already support ODBC connections ?
Configuring ODBC connections to a live db and then running update stats on a regular basis is a noticeable amount of work.
After that is setup, I haven't seen much of an impact on read only ODBC connections. I have not had to support ODBC...
Depending on your version of OE and the parameter "allowruntimeupdates" in the ubroker.properties file, you might be able to lower the logging level online.
I don't recall if cat /dev/null > log will actually release the space without having to stop the app server.
you could tell them that those permissions don't meet your company's security standards.
Usually saying something about their setup fails our company's security audit is the best motivation I have with vendors.
I have been around a couple applications that used the Oracle DataServer.
The application can be updated to make the reads perform acceptable, but we weren't able to get large updates to process quickly.
If there were 100 records to update, the Oracle DataServer would send them to Oracle as...
OpenEdge Communities have some chatter. Seems like most of the posts relating to databases are coming from the Asia region.
We tried to start / revive the Progress User Group for the Midwest region in the U.S.A., but it didn't last.