Periodic db restarts
DBAsupport.com Forums - Powered by vBulletin
Page 1 of 2 12 LastLast
Results 1 to 10 of 19

Thread: Periodic db restarts

  1. #1
    Join Date
    Nov 2002
    Location
    Geneva Switzerland
    Posts
    3,142

    Question Periodic db restarts

    A colleague running 9.2 on HP-UX asked Oracle Support if it was a good idea to stop and start his db on a daily basis. Support replied:
    Yes, if the circumstance permit it, shutting down cleanly and restarting an instance once a day will lessen the negative effects of memory fragmentation and in some cases counter the negative effects of any gradual memory leaks.
    Any comments?

  2. #2
    Join Date
    May 2000
    Location
    ATLANTA, GA, USA
    Posts
    3,135
    The oracle support guy might have joined last week after graduating from MIT.

    Tamil

  3. #3
    Join Date
    Jan 2001
    Posts
    3,131
    Sounds more like a windoze response then a Unix response.
    I remember when this place was cool.

  4. #4
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,092
    Insert favorite MCSE joke here

    All kidding aside, taken completely out of context, this statement is absurd. However, if your instance was crashing every 26 hours because of memory leaks, this might be a semi-reasonable suggestion.
    Last edited by marist89; 12-27-2004 at 11:54 AM.
    Jeff Hunter
    marist89@yahoo.com
    http://marist89.blogspot.com/
    Get Firefox!
    "I pledge to stop eating sharks fin soup and will not do so under any circumstances."

  5. #5
    Join Date
    Sep 2002
    Location
    England
    Posts
    7,333
    and one day it wont restart, then you are in trouble

  6. #6
    Join Date
    Aug 2003
    Location
    Virginia
    Posts
    392
    Question: Why would stopping and starting a database on a daily basis be a bad thing. I ask because I do not know the nuances of the database yet.
    Rick

    Sigh.....those were the days my friend, I thought they'd never end.
    I too remember when this place was coo.


  7. #7
    Join Date
    Sep 2002
    Location
    England
    Posts
    7,333
    because chances are it wull be unattended, meaning it might not come back - then you come in at 9.00 am and your users are screaming to high hell.

    Also - you clear you buffer cache meaning a load more pio's
    clear out the shared pool, meaning loads more parsing = loads more latches = loads more cpu = slower queries till it gets warmed up.

    Benefits? none really, unless you have a crash every 26 hours as jeff said - but then you have bigger fish to fry

  8. #8
    Join Date
    Aug 2002
    Location
    Colorado Springs
    Posts
    5,253
    Originally posted by davey23uk
    because chances are it wull be unattended, meaning it might not come back - then you come in at 9.00 am and your users are screaming to high hell.

    Also - you clear you buffer cache meaning a load more pio's
    clear out the shared pool, meaning loads more parsing = loads more latches = loads more cpu = slower queries till it gets warmed up.

    Benefits? none really, unless you have a crash every 26 hours as jeff said - but then you have bigger fish to fry
    Absolutely

    Think of the number of times a car has broken down on you. Chances are it hasn't been while you were driving along at steady speed -- it failed to start in the morning, or after work, or when you engaed reverse. In other words, things usually break when they change.

    This is the kind of asinine advice that gives support a bad name -- not just Oracle, but any support team.
    David Aldridge,
    "The Oracle Sponge"

    Senior Manager, Business Intelligence Development
    XM Satellite Radio
    Washington, DC

    Oracle ACE

  9. #9
    Join Date
    Aug 2003
    Location
    Virginia
    Posts
    392
    Also - you clear you buffer cache meaning a load more pio's
    clear out the shared pool, meaning loads more parsing = loads more latches = loads more cpu = slower queries till it gets warmed up.


    Everything is being thrown at it at once, first thing in the morning, when it was in there from the previous day. Leaving everything cached, as you go along.

    Think of the number of times a car has broken down on you. Chances are it hasn't been while you were driving along at steady speed -- it failed to start in the morning, or after work, or when you engaed reverse. In other words, things usually break when they change.

    If a dba were to clear all caches then stop the database, and IT crashes then the dba is up the proverbial creek without a paddle.

    Thanks.
    Rick

    Sigh.....those were the days my friend, I thought they'd never end.
    I too remember when this place was coo.


  10. #10
    Join Date
    Nov 2000
    Location
    Pittsburgh, PA
    Posts
    3,999
    Originally posted by Alchemy
    If a dba were to clear all caches then stop the database, and IT crashes then the dba is up the proverbial creek without a paddle.
    While shutting down a database might cause it to be slower when it restarts, shutting down and restarting a database will not affect the ability of a DBA to recover that database.

    Are you saying that shutting down a database could cause a database to be unrecoverable?
    this space intentionally left blank

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width