- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: RDB poor Recovery or Rollback performance.
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-22-2006 06:13 PM
02-22-2006 06:13 PM
Re: RDB poor Recovery or Rollback performance.
"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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-28-2007 10:35 PM
06-28-2007 10:35 PM
Re: RDB poor Recovery or Rollback performance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-28-2007 11:57 PM
06-28-2007 11:57 PM
Re: RDB poor Recovery or Rollback performance.
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2007 02:26 AM
06-30-2007 02:26 AM
Re: RDB poor Recovery or Rollback performance.
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2007 02:37 AM
06-30-2007 02:37 AM
Re: RDB poor Recovery or Rollback performance.
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-25-2010 05:52 AM
02-25-2010 05:52 AM
Re: RDB poor Recovery or Rollback performance.
Can you tell how this story ended ?
Wim
- « Previous
-
- 1
- 2
- Next »