RE: Hit Ratio fallen through the floor at 31% since a db crash ye
How about hiring a consultant? -Original Message- Sent: Thursday, February 08, 2001 4:41 PM To: Multiple recipients of list ORACLE-L It had only been up for a few weeks. It could be the buffer cache. -Original Message- mailto:[EMAIL PROTECTED] ] Sent: Thursday, February 08, 2001 1:03 PM To: Multiple recipients of list ORACLE-L ye Just wondering...how long was the instance up before the crash? Could it be that your buffer cache just hasn't built up to where it was before the crash? Rich Jesse System/Database Administrator [EMAIL PROTECTED] Quad/Tech International, Sussex, WI USA -Original Message- Sent: Thursday, February 08, 2001 13:02 To: Multiple recipients of list ORACLE-L We are running 8.1.5 on Solaris. We can't seem to find the cause - everything is up and running fine, just extremely slow. What should we be looking at? TIA, Barb This message has been scanned for viruses with Trend Micro's Interscan VirusWall. -- Please see the official ORACLE-L FAQ: http://www.orafaq.com http://www.orafaq.com -- Author: Jesse, Rich INET: [EMAIL PROTECTED] Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 San Diego, California-- Public Internet access / Mailing Lists To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (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). -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Gogala, Mladen INET: [EMAIL PROTECTED] Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 San Diego, California-- Public Internet access / Mailing Lists To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (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).
RE: Hit Ratio fallen through the floor at 31% since a db crash ye
Title: Hit Ratio fallen through the floor at 31% since a db crash yesterday I tried that one already!! -Original Message-From: Kimberly Smith [mailto:[EMAIL PROTECTED]]Sent: Thursday, February 08, 2001 12:19 PMTo: Multiple recipients of list ORACLE-LSubject: RE: Hit Ratio fallen through the floor at 31% since a db crash ye Here we like to blame the network on all problems, irregardless of what it is (mostly to bug the network guy). -Original Message-From: Barbra Hale [mailto:[EMAIL PROTECTED]]Sent: Thursday, February 08, 2001 11:02 AMTo: Multiple recipients of list ORACLE-LSubject: Hit Ratio fallen through the floor at 31% since a db crash yester We are running 8.1.5 on Solaris. We can't seem to find the cause - everything is up and running fine, just extremely slow. What should we be looking at? TIA, Barb
RE: Hit Ratio fallen through the floor at 31% since a db crash ye
Title: Hit Ratio fallen through the floor at 31% since a db crash yesterday Checkforlostorinvalidindexes -Original Message-From: Barbra Hale [mailto:[EMAIL PROTECTED]]Sent: Thursday, February 08, 2001 12:02 PMTo: Multiple recipients of list ORACLE-LSubject: Hit Ratio fallen through the floor at 31% since a db crash yester We are running 8.1.5 on Solaris. We can't seem to find the cause - everything is up and running fine, just extremely slow. What should we be looking at? TIA, Barb
RE: Hit Ratio fallen through the floor at 31% since a db crash ye
Just wondering...how long was the instance up before the crash? Could it be that your buffer cache just hasn't built up to where it was before the crash? Rich Jesse System/Database Administrator [EMAIL PROTECTED] Quad/Tech International, Sussex, WI USA -Original Message- Sent: Thursday, February 08, 2001 13:02 To: Multiple recipients of list ORACLE-L We are running 8.1.5 on Solaris. We can't seem to find the cause - everything is up and running fine, just extremely slow. What should we be looking at? TIA, Barb This message has been scanned for viruses with Trend Micro's Interscan VirusWall. -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Jesse, Rich INET: [EMAIL PROTECTED] Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 San Diego, California-- Public Internet access / Mailing Lists To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (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).
RE: Hit Ratio fallen through the floor at 31% since a db crash ye
Barb, pick the slowest application and examine it for the waits. What is the application waiting for? Take a look at v$session_event (cumulative) and v$session_wait (current wait). If you see things like "scattered db file read' or 'sequential db file read', then you have a problem with access path (optimizer). If that is the case, you'll need to pull a few tricks with the optimizer. The best thing that can be done with the optimizer on 8.1.5 is the upgrade to 8.1.7. If you have 'enqueue wait', examine your ITL, (initrans/maxtrans) and lock related parameters. If you have "log space waits", increase your log buffer. If you have "free buffer waits", increase your buffer cache. Next, examine your alert log and examine the frequency of checkpoints. If that is more then once every 10 minutes or so, increase your logfiles in size numbers. Size does matter! When this is done, examine your v$librarycache and v$rowcache, pin the frequently used procedures and adjust the size of your shared pool. Next, consider using MTS and defining the large pool to separate your sorts and hash actions from your PL/SQL objects. After that, examine your tables and see how are they used. Put the big reference tables in hash clusters, the small ones in the "KEEP" buffer pool and put the transaction and the history tables in the "RECYCLE" buffer pool. consider using the partitioning option for your largest tables and consider moving all your objects to locally managed tablespaces. do not forget to spread your IO across several controllers. With a little luck, you will be done just in time to perform the next major upgrade, when the process will start all over again. Enjoy! -Original Message- Sent: Thursday, February 08, 2001 3:45 PM To: Multiple recipients of list ORACLE-L I tried that one already!! -Original Message- Sent: Thursday, February 08, 2001 12:19 PM To: Multiple recipients of list ORACLE-L Here we like to blame the network on all problems, irregardless of what it is (mostly to bug the network guy). -Original Message- Sent: Thursday, February 08, 2001 11:02 AM To: Multiple recipients of list ORACLE-L We are running 8.1.5 on Solaris. We can't seem to find the cause - everything is up and running fine, just extremely slow. What should we be looking at? TIA, Barb -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Gogala, Mladen INET: [EMAIL PROTECTED] Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 San Diego, California-- Public Internet access / Mailing Lists To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (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).
RE: Hit Ratio fallen through the floor at 31% since a db crash ye
Title: RE: Hit Ratio fallen through the floor at 31% since a db crash ye It had only been up for a few weeks. It could be the buffer cache. -Original Message- From: Jesse, Rich [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 08, 2001 1:03 PM To: Multiple recipients of list ORACLE-L Subject: RE: Hit Ratio fallen through the floor at 31% since a db crash ye Just wondering...how long was the instance up before the crash? Could it be that your buffer cache just hasn't built up to where it was before the crash? Rich Jesse System/Database Administrator [EMAIL PROTECTED] Quad/Tech International, Sussex, WI USA -Original Message- Sent: Thursday, February 08, 2001 13:02 To: Multiple recipients of list ORACLE-L We are running 8.1.5 on Solaris. We can't seem to find the cause - everything is up and running fine, just extremely slow. What should we be looking at? TIA, Barb This message has been scanned for viruses with Trend Micro's Interscan VirusWall. -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Jesse, Rich INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (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).
