Read-Write connection creates locks on Progress

[sgandhi]

Hello. We are using OpenLink to connect Progress 8.3a with Oracle 9i.
If the ODBC connection is configured as follows
options = -RO
we get a read only connection and we are able to select data from Progress.

If we remove the -RO option, one of two things happens:

1) if no one else is connected, it locks the database ("data dictionary being edited by [openlink user]) for any other user trying to connect
2) if anyone else is connected, the openlink connection fails (the oplrqblog file shows a successful connection)

This leads me to believe we are getting a transaction on the data dictionary from the ODBC link (this is similar to an issue we had with transactions occurring when clients did not use -RO), because this is what Progress does when it sees that.

Can you suggest how to resolve this issue?
Thanks

 

[OpenLink]

If I'm reading your issue correctly, Oracle (via HSODBC) is the data consumer, and Progress is the data source. The rest of this response depends on that...

There are some configuration options which may make sense to adjust, at several layers (Progress startup options, OpenLink Database Agent for Progress configuration options, OpenLink ODBC DSN attributes, HSODBC setup options).

Determining which options should be adjusted (and how!) requires full knowledge of their current settings, and is probably not best done on this board.

One possibility (by no means guaranteed to resolve the issue!) is to make sure the OpenLink Broker Rulebook, oplrqb.ini, settings for the Database Agent for Progress 8.3 do not include "CommandLine = +noautocommit". However, this adjustment may impact other users and applications, so the needed change may be much more than one line of the Rulebook.

There are other ways to blend data from Oracle 9i and Progress 8.3A which may be more suitable to your overall needs and goals. I encourage you to open a support case with OpenLink and provide more details of what you're trying to achieve, so we can both assist with the immediate issue, and hopefully bring you closer to the ultimate solution.

Best regards,

Ted
OpenLink Technical Support