Rdb 7.0 and PH 6.10/6.20

[Kevin Gordon]

>> We resolved our problem by setting the logical PHDBKEYSCOPE to
Transaction. <<

I'd forgotten about that one - definitely worth a try. We did this some time
ago and there have been no adverse effects and it seemed to reduce the
incidence of unexplained lock-ups. However, if you do use it, make sure it
applies to all database users, because a single user with a scope of ATTACH
causes all other users to do likewise. If you have non-PH applications
accessing the same database, their default DBKey scope could be different
(SQL defaults to TRANSACTION - can't vouch for anything else).

Regards,

Kevin Gordon
Sea Containers, London.

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.