DBA Role

In <1994Jul12.135728.11821@lmpsbbs.comm.mot.com> hartnett@dub-fdev.dub.comm.mot.com (Denis Hartnett) writes: > I am the new DBA in Motorola in Dublin. I am looking after the INFORMIX and > ORACLE databases on site. > I am looking for a document on the role of the DBA : > What his respobsibilities are > The minimium requirements for accepting software to be released > Hardware requirements. > Coding standards - Table and Field names naming conventions. > > My email address is hartnett@comm.mot.com. > Any answers I get I will merge them together and put them on the newsnet. > > Thanks in advance. > Our DBA has rather broadly defined responsibilities, something like "Everything that has to do with the database." A description looks something like: Tune databases -set appropriate extent sizes for tables -define tables large enough to fit inside 8 extents (max) -monitor dbspace -adjust purges and db size IAW company requirements -adjust locks, logs, high-water marks, buffers, etc -move logs from same dbspace as main data -map db usage for each db (chunks, mirrors, sizes) -reduce test db resources -maintain DBA logs of tuning & adjustments -maintain backup copies of schemas, tbconfigs, startup, backup, and shutdown scripts, crontab entries -update statistics periodically Keep abreast -keep abreast of informix newsgroup on internet -attend user conferences Maintain databases -maintain user permissions at table level (systabauth table) -provide backup of raw dbspace (do_ol_backup.sh) -institute "watcher" program (from internet) to automatically monitor database numbers -install new informix software -migrate PDCS database to new platforms New Development -integrate all shop floor systems into "distributed db" -upgrade systems to latest versions System Administration -provide backup of user space, source code, etc -monitor and control user disk space usage -create new accounts -create/modify printer queues -work with System Administrator on these tasks to-do list -adapt backup routines on to account for the changing data stored there (as systems move) -re-build tables, allow for x months of data and no more. create new indices as needed -use the watcher program from the internet to monitor dbspaces -plan for migration to OnLine v5, then to OnLine v6. Fix user mistakes Fileserver -maintain upload services on each node Codes -adjust code validation tables at each system to only accept valid codes. -maintain a copy of appropriate corporate manual pages -work with DP to ensure new bogus codes not downloaded Maintain system for tracking SPRs for all shop floor systems Centralize source code -form a team to establish a central source code repository on the development node. -use common modules between systems to-do list -develop download services on each node -train users on network fundamentals (i.e. difference in terminal, computer, terminal server, network wires vs terminal wires vs power cables) -develop mail routine to call whenever there's a problem with a download, upload, update, etc. to replace alarms -Develop lesson plans for SQL classes for IEs, metallurgists and other users of query utilities. At our shop the DBA doesn't set coding standards, these are arrived at "by concensus" during group discussions. One way to define it is that the DBA does anything discussed in the OnLine Administrator's Guide. The low-down is that the DBA (or any position) will continue to accept more and more responsibility until the "Peter Principle" kicks in. Good luck, __________________________________________________________________ | Clem Akins Standard Disclaimers Apply | | Reynolds Metals Co. "Climb High, Cave Deep!" | | Muscle Shoals, Alabama USA cwakins@leia.rmc.com | |________________________________________________________________|