Unless the database is really small, and/or very low load, hugepages is a must. My opinion of hugepages: http://markjbobak.wordpress.com/2014/01/21/if-youre-not-using-hugepages-youre-doing-it-wrong/ On Tue, Jul 29, 2014 at 8:33 AM, Mark W. Farnham <mwf@xxxxxxxx> wrote: > 1) Use of the couplet “Best Practice(s)” is harmful. > > > > eot < > > > > mwf > > > > *From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto: > oracle-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *Justin Mungal > *Sent:* Monday, July 28, 2014 4:17 AM > *To:* oracle-l-freelists > *Subject:* Oracle DB Best Practices on Linux x86_64 > > > > I have an interesting request from a customer to review the Oracle > configuration on a couple servers for best practices. I've been checking > things over; I haven't had a chance to talk to the customer yet, but seeing > from the load I'm guessing they aren't in production yet. > > > > Right now I've just looked at the very basic things that tend to come back > and bite later on, or are just good things to configure in general: > backups, multiplexed control/redo logs, memory settings, patch levels, log > rotation, etc... but then again not all of them may be necessary, depending > on the customer's needs. > > > > Has anyone created some kind of generic best practices document, or a > checklist of some kind? Arup Nanda's document from 2007 has some good > points, so I would be looking for something like that I suppose. > > > > Thanks, > > Justin >