Re: Programmer forced into DBA Role, Help?

Good questions ::))

My advice ?

1. *Demand* formal training
2. Don't do *anything* that *might* be critical without explicit advice from your support line and 2 (different) backups
3. Make your employer/boss aware that this is not an area where you can 'wing it' The future of the business could be at stake if you make a serious mistake.
4. Request formal authorisation for any critical actions you take.
5. The Oracle-supplied manuals are surprisingly good :)
6. Regularly PROVE that your backup regime works. Only takes some fool to change a file permission to invalidate the lot (I've seen it happen)
7. Ask for a *fat* pay rise to compensate for all your heartache and stress :) Resort to 4. *a lot* if pay rise is denied.

Regards

Glenn Baron

Douglas Whitacre <whitacre_at_imake.com> wrote in article <7bgoji$n2e_at_world1.bellatlantic.net>...
> I have been an application programmer for close to the last 10 years
> revolving around Oracle. Now, I'm being moved into more of a DBA role.
I
> know enough to be dangerous, but the hot topics I need help with are:
> Backup & Restore, and Archiving and Recovery strategies. If anyone out
> there can point me in the direction of tools and/or methodologies I can
look
> at in these areas it would be greatly appreciated. Can you email
> suggestions? Thanks in advance.
>
>
>
Received on Tue Mar 02 1999 - 12:16:19 CST