Steven Chan has an interesting set of observations on patching, taken together they form an interesting argument for regular and scheduled patching.  Steven offers 5 common 'myths' that might influence a conservative patching policy. These are

1. It requires too much downtime
2. Testing is too expensive for end-users
3. It's too complicated
4. We don't have enough staff
5. It ain't broken; why fix it?

 While there undoubtedly is truth in what Steven says I still don't buy them quite yet, or perhaps I do but come to a different conclusion as a practitioner rather than a supplier.

Doug quite rightly commented on this page and it's numerous errors, which start I should warn you with a security certificate from the wrong domain.

It doesn't get better really, it's a FAQ which addresses some issues. Included are

Q:

How do I backup my database.

Im proud to announce that I rejoice in membership number 9 of the BAAG party Unlike the Oaktable membership this new initiative is open to all, and I encourage you to join the comrades - quite why a Russian would choose this collective noun is be

Windows DBAs will wish to download and test Patchset 8 patch 6038279, which is now available and addresses a critical recoverability flaw on Windows 32 bit platforms. Professional DBAs will know that it is important to keep software updated regularly in order to address security and stability concerns as well as post release bug fixes.Consequently a commonly accepted 'best practice' for Oracle databases might consist of the following;