To be a good production DB2 DBA, you need an awareness of ALL scheduled processes that connect with your database. In a large organization, this is not an easy task, and requires you to be proactive.
Active Unix DB2 databases generate and store substantial support information outside of the database itself, in flat text files and binary dumps. If as a Unix DBA you do your administration work largely via Unix shell session, you probably have files comprising SQL, data exports, scripts, generated reports and performance monitoring output which need maintenance. We must, in the course of our work, monitor, maintain and prune those files. File maintenance, in my experience, is one of the most commonly neglected parts of a DBA’s work, often because it is not explicitly delegated; we all assume someone else is going to do the work. DB2-related Unix directories comprise part of the collective memory of the DB2 and are valuable as history, documentation, training, team communication and for the reuse of components.
