Slow databases on a Solaris server after flushing buffer cache of one database [message #631754] |
Mon, 19 January 2015 09:16 ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
orausern
Messages: 826 Registered: December 2005
|
Senior Member |
|
|
Hi,
I have 6 databases on Oracle 10.2.0.3 (didn't get OK to upgrade to 11g yet and that is a seperate and unrelated issue). Today I flushed buffer cache of one of this database. The command just hanged for more than 20 minutes.
Then I killed that session. Since then , all databases on the solaris server are very very slow. It takes like 15 seconds to start a new session. My guess is something related to memory has gone wrong. But I really don't know enough to be sure. CAn someone please review and suggest the needful?
Thanks,
OrauserN
|
|
|
|
|
|
|
|
Re: Slow databases on a Solaris server after flushing buffer cache of one database [message #631773 is a reply to message #631763] |
Mon, 19 January 2015 11:06 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
orausern
Messages: 826 Registered: December 2005
|
Senior Member |
|
|
I used to follow this practice of flushing buffer cache! Now I have burnt my fingers and I am going to check whether this should be done really!
Also this mystery came to an end....the alert log of the db , whose buffer cache I had flushed had this errors...I have export backup so tomorrow I will try to rebuild the db from scratch!!
ORA-00604: error occurred at recursive SQL level 1
ORA-01115: IO error reading block from file 1 (block # 3667)
ORA-01110: data file 1: '/u01/oradata/db1/system1.dbf'
ORA-27091: unable to queue I/O
ORA-27072: File I/O error
SVR4 Error: 5: I/O error
[Updated on: Mon, 19 January 2015 11:06] Report message to a moderator
|
|
|
Re: Slow databases on a Solaris server after flushing buffer cache of one database [message #631774 is a reply to message #631773] |
Mon, 19 January 2015 11:09 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
orausern
Messages: 826 Registered: December 2005
|
Senior Member |
|
|
Also Mike , about this point:
Quote:But your query will never be executed when the buffer cache will be empty, won't it?
Well...what I used to do is to flush the shared pool, buffer cache and wait 3 minutes. This means whatever data nowthe query has to get will come from IO and not from memory. That gives a good idea of how the performance will be - as I thought. Is this wrong and if yes why? I am not clear on it.
|
|
|
|
Re: Slow databases on a Solaris server after flushing buffer cache of one database [message #631780 is a reply to message #631773] |
Mon, 19 January 2015 11:49 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
John Watson
Messages: 8964 Registered: January 2010 Location: Global Village
|
Senior Member |
|
|
orausern wrote on Mon, 19 January 2015 17:06I used to follow this practice of flushing buffer cache! Now I have burnt my fingers and I am going to check whether this should be done really!
Also this mystery came to an end....the alert log of the db , whose buffer cache I had flushed had this errors...I have export backup so tomorrow I will try to rebuild the db from scratch!!
ORA-00604: error occurred at recursive SQL level 1
ORA-01115: IO error reading block from file 1 (block # 3667)
ORA-01110: data file 1: '/u01/oradata/db1/system1.dbf'
ORA-27091: unable to queue I/O
ORA-27072: File I/O error
SVR4 Error: 5: I/O error
This looks like a hardware or operating system issue: Oracle is havig problems with that file. Importing an export dump file is not going to fix that, you'll need to restore from a real backup and then recover it.
Before you do that, you had better take a look at the file and do a few basic checks. Is it the right sort of size? Does it have the right access permissions? Can you read and write any other files on the dsame device? Then run dbv against the file to check for corruptions.
|
|
|
Re: Slow databases on a Solaris server after flushing buffer cache of one database [message #631781 is a reply to message #631778] |
Mon, 19 January 2015 12:36 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
orausern
Messages: 826 Registered: December 2005
|
Senior Member |
|
|
Michel Cadot wrote on Mon, 19 January 2015 17:24
The only way to get a realistic idea of the performances is to execute it in an environment similar to the one it will execute in the end.
Thank you Michel. Here my doubt is that: if you don't flush buffer cache, the data may already be present in buffer cache so next execution may show 'artificially fast response time' which may not happen in real-time. So the chances that our query's data may not be present in buffer cache is far higher than the chance that it is present. Therefore it is more realistic to flush buffer cache -is what I was thinking. Is that wrong?
Thanks,
|
|
|
Re: Slow databases on a Solaris server after flushing buffer cache of one database [message #631782 is a reply to message #631780] |
Mon, 19 January 2015 12:39 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
orausern
Messages: 826 Registered: December 2005
|
Senior Member |
|
|
John Watson wrote on Mon, 19 January 2015 17:49[code]
This looks like a hardware or operating system issue: Oracle is havig problems with that file. Importing an export dump file is not going to fix that, you'll need to restore from a real backup and then recover it.
Before you do that, you had better take a look at the file and do a few basic checks. Is it the right sort of size? Does it have the right access permissions? Can you read and write any other files on the dsame device? Then run dbv against the file to check for corruptions.
Thank you John! What I am thinking to do is to : DROP this database and create the Database back with same name and import with its previous full export file. Hope that will work right?
|
|
|
|
|
|
|