Rdb 7.0 and PH 6.10/6.20

[Kevin Gordon]

As my name has been bandied around I thought I'd better chip in here. This
has evolved into what I believe are two totally separate issues. The issue
with the change in locking behaviour between PowerHouse 6.00 and 6.10 was
well documented at the time and caused much grief to lots of sites. We never
used the PRE_610_COMMIT parameter, but you may find that defining your
transaction model as OPTIMISTIC in the dictionary helps (SYSTEM screen,
action TRAN, option 1 - needs recompile to take effect). This feature was
introduced in 6.10E to help resolve the mayhem caused by the change in the
default behaviour in between 6.00C and 6.10C.

As far as RDM$BIND_SNAP_QUIET_POINT (yes that is the right name for OpenVMS)
is concerned - that was specifically to do with RMU on-line backups stalling
after upgrading to Rdb 7.0, not general PowerHouse locking problems.
Unfortunately there was not enough information in the original post from
John Webster about the nature of his problems. I can't see that it is
relevant in Wanda Ravenscroft's case (what does "lock up the database"
mean?) because her Rdb version is 6.1.

And as for the hijacking of this thread to talk about Impromptu and
Peoplesoft - please will you start your own! Thank you.

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.