| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Dealing with 3rd Party Applications
IME, I've found that the reason they say not to use features like that is
because they don't know them and are therefore not able to support them.
One of our 3PV's applications that used Oracle had many features of Oracle performance (and recovery!!!) disabled because it was the least common denominator for their customers. Some of their customers have DBAs, but most do not. The problem with this approach is that it caused the 3PV's app to benchmark very poorly as the DB grew as well as require manual daily cold backups and/or exports (one of their developers told me not to do hotbacks because they would be useless due to some files being stored external to the DB -- I believe that we've since proved them wrong for our environment).
So, we spent weeks perf tuning our production DB for this app, at the cost of uptime to our users (I hope my perf tuning methodology has improved since then!). The DB has been up, been stable, and has been performing reasonably for 289 days now.
I know that there has been some discussion on this List before regarding tuning 3PV apps, but has anyone written up their methodology for dealing with this? On every Oracle perf tuning methodology I can remember seeing, the first item is "Tune SQL". With 3PV apps, that's usually not possible. I've got my own 3PV app tuning methods, but I know they need much improvement.
Rich
Rich Jesse System/Database Administrator rich.jesse_at_qtiworld.com Quad/Tech International, Sussex, WI USA
-----Original Message-----
Sent: Wednesday, February 26, 2003 6:44 PM
To: Multiple recipients of list ORACLE-L
Yes, read the vendor documentation, then scrutinize it. One serious thing
to look for is the documentation up to date. We're implementing a new
application right now, which includes a healthy amount of docs from the
vendor regarding Oracle. Their docs said I cannot use LMT. Their docs said
I cannot use partitioning. The docs said I cannot use newer Oracle than
8.1.7.1.
After I counted to 100 (or 1000, I lost count) and got more coffee, I wrote
a firm, but nice e-mail to the project manager asking him to confirm with
the vendor just what they were trying to prove. No, seriously, I wanted to
know specifically what problems they encountered with LMT and partitioning
in their testing. I suggested that without specific results, I would use
LMT anyway. Their reply was that the documention was outdated and that we
could use 8.1.7.4, could use LMT, and could use partitioning.
This case was easy.
Another such circumstance has a vendor telling us that we cannot use
archivelog mode because it will kill performance. They didn't say it might
affect performance if not configured properly, they said (more than once) it
will kill performance.
It's still early, this too shall pass.
The point is not to bash vendor documentation, but to encourage folks to read it. Read it for what it says and for what it doesn't say.
Darrell Landrum
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Jesse, Rich
INET: Rich.Jesse_at_qtiworld.com
Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services ---------------------------------------------------------------------To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). Received on Thu Feb 27 2003 - 09:39:33 CST
 |
 |