Operating System - OpenVMS
1829106 Members
2746 Online
109986 Solutions
New Discussion

Re: RDB poor Recovery or Rollback performance.

 
Jean-François Piéronne
Trusted Contributor

Re: RDB poor Recovery or Rollback performance.

Thmoas,
"A $forces does not disconnect the user, but the $delprc does. "

What you can do is a $forcex, waiting a little then $delprc, so this let process time to gracefully rollback his open transaction. (it would be better to monitor the process and do a $delprc when it has finish the rollback).

This is for example what WASD do to stop script process.


Jean-François
David Hammett
New Member

Re: RDB poor Recovery or Rollback performance.

I realisethe thread is a little aged but can anybody advise me of where I should go to get T4 for RDB setup details ?
Hein van den Heuvel
Honored Contributor

Re: RDB poor Recovery or Rollback performance.

David wrote>> I realisethe thread is a little aged but can anybody advise me of where I should go to get T4 for RDB setup details ?

Thomas, may be time to lock up this topic huh?

David, why not just start your own topic? The price is right!

Anyway, just google: openvms rdb t4 kit

Check out: http://www.jcc.com/JCC%20Presentations/Tracking%20Rdb%20Performance%20Using%20T4.pdf

It mentions: PerfT4.C from Metalink Note 282894.1

hth,
Hein.
Art Wiens
Respected Contributor

Re: RDB poor Recovery or Rollback performance.

Thomas, I don't recall following this thread last year, but reading it now, I want to know how the story ended!

Was RDB support/HP able to help and "retain trust"?

Or did Management give up and order IT to run Oracle on an "alternative" platform?

Quite a cliffhanger! ;-)

Cheers,
Art
Robert Gezelter
Honored Contributor

Re: RDB poor Recovery or Rollback performance.

Thomas,

Reading this thread, I will offer a couple of comments.

First, I heartily agree with the recommendation to run T4 and collect utilization statistics. I would also seriously consider implementing application specific data collectors to monitor application (and possibly RDB) metrics. Having these data collectors running on an ongoing basis allows retrospective analysis of what was happening to the system during the slowdown period. (Dislaimer: My firm does this type of project in our consulting practice).

Once the statistics are in hand, the analysis of the problem, whether application, database configuration, RDB (or some combination) can be done in a scientific manner.

For analysis, I would also consider whether it is worth constructing a test system that can create the problem at will (reproduceably) so that changes can be tested. With the ongoing statistic monitoring mentioned earlier, there is also an way of objectively evaluating the changes.

- Bob Gezelter, http://www.rlgsc.com
Wim Van den Wyngaert
Honored Contributor

Re: RDB poor Recovery or Rollback performance.

Thomas (with beautiful hat),

Can you tell how this story ended ?

Wim
Wim