TECHNICAL SKILLS:

• Oracle 8i - 12c Database Management Systems
• Oracle Enterprise Manager 12c Cloud Control
• Oracle Data Guard
• Oracle Real Application Clusters (RAC)
• SQL and SQL*PLUS Database Query Languages
• HP-UX 11, RHEL 5- 6, MS-DOS, and Microsoft Windows 9x-7
• TOAD and SQL Developer
• SQL Developer Data Modeler
• Confluence
• Oracle Discoverer Business Intelligence Software
• PL/SQL, C/C++, and Ada Programming Languages
• DISA STIG Compliance

PROFESSIONAL EXPERIENCE:

Confidential

Database Administrator

Responsibilities:

• Responsible for 21 primary databases and three logical standby databases. These consist primarily of single-instance 11.2.0.4 databases, running on RHEL 6. We also support a few legacy RAC databases and a single 12c database. These databases range in size from a 225GB development database to a 2.5TB production database.
• Primary responsibility is to provide database administration and engineering support for the infrastructure engineering team during the development of a next-generation biometrics management system.
• Use Enterprise Manager Cloud Control 12c to monitor the system, making sure that all components of the database infrastructure are functioning properly for development and testing. Configure monitoring and incident notification for non-production and production environments.
• Create and configure new databases using both dbca and shell scripts. Create new databases using RMAN backups of the production environment. Use RMAN active duplication and backup-based duplication to clone databases.
• Create and configure physical and logical standby databases.
• Install and configure Oracle Server Enterprise Edition software. Install and configure Oracle Enterprise Manager Cloud Control 12c software. Deploy Enterprise Manager agents to necessary hosts.
• Perform upgrades, quarterly patch set updates, and one-off patches to both the database and Enterprise Manager infrastructure.
• Create and implement the incremental backup strategy, using RMAN to perform inconsistent (hot) backups of our operational environment. Currently working with System Administrators and Storage Administrators to implement an off-host backup solution, which will use RMAN backups of Veritas snapshots, done on a separate backup server.
• Migrate operational environment databases from one physical location to another, by creating a physical standby database and performing a switchover.
• Use Transportable Tablespaces export to migrate schemas to different databases.
• Migrate our RAC deployments into multiple single-instance deployments.
• Develop PL/SQL programs and SQL scripts to make necessary schema changes, and to more efficiently administer databases.
• Use DISA Security Technical Implementation Guides (STIGs) to discover security vulnerabilities within database deployments and remediate those deficiencies.
• Use the JIRA issue tracking product to track system changes, as part of our change management process.
• Assess Information Assurance Vulnerability Alerts (IAVA) to determine applicability to our database and Enterprise Manager deployments. Research, plan, and implement mitigation steps for these IAVA, typically by implementing Oracle SPUs or PSUs, using the Opatch utility.
• Create and maintain documentation including Database Design Document, database diagrams, standard operating procedures and build deployment guides. Maintain database-related Confluence pages.

Confidential

Database Engineer

Responsibilities:

• Responsible for eleven primary databases and two physical standby databases, ranging from a 30GB functional testing database to a 600GB operational environment database. Also manage individual schemas for each of our thirteen application developers, so that he or she can do development and unit testing in his or her personal environment. These databases are used principally for processing background checks for a large government project and generating reports and statistics based upon these checks.
• Primary responsibility, working on this operations and maintenance contract, is to ensure that 24/7 operational environment databases are online and that our system is performing within a mandated set of performance parameters. All operational environment and non-operation environment databases are Oracle 11.2.0.2, residing on HP Superdomes running HP-UX 11.31. Migrated nine of these databases from 9.2.0.4 to 10.2.0.4 and two from 9.2.0.5 to 10.2.0.4. Migrated all databases from 10.2.0.4 to 11.2.0.2. Install and configure Oracle Server software on HP-UX servers as well as Oracle Client and the Oracle Business Intelligence Discoverer product on Windows XP workstations.
• As the manager of the DBA team for my systems, supervise less experienced DBAs, including performing performance evaluations, delegation of tasks, interviewing prospective employees, training, and timecard validation.
• Monitor both tablespace usage and growth, using custom-written SQL scripts and PL/SQL programs. Work with System Administrators and the Enterprise Storage Team to plan storage expansion based upon past usage growth, and the anticipated needs based upon the functionality that will be added or modified in the near future.
• Use RMAN to perform hot backups of our operational environment database. Use the Oracle Data Pump utility to export data that we are not required, by law, to destroy within 24 hours, to provide an added level of protection. Use RMAN or Data Pump exports to recover from operational issues. Use RMAN to perform cold backups of our non-operational environment databases and to restore the database during the various stages of testing, to support our test team.
• Develop PL/SQL programs and SQL scripts to more efficiently administer databases. These range from simple scripts, such as generating an explain plan from a SQL statement stored in AWR to more complex PL/SQL programs that dynamically generate all of the SQL code for generating partitions for the upcoming year, for each of the partitioned objects stored in the various schemas of our database.
• Use ADDM, AWR, and the DBMS SQLTUNE package as part of the performance tuning process. Use the information generated by these utilities to tune database parameters, generate necessary indexes, and to recommend optimizer hints or code changes to our software development team. Also, using the aforementioned utilities and Compiler (10046) and Optimizer (10053) trace files, determine areas where the automated GATHER STATS JOB is not sufficient for real-world use, and automate the gathering of statistics and histograms on these objects.
• Provide our customer with a denormalized schema, used by the end-user layer of Oracle Discoverer. By setting up the objects and joins in this product, the customer’s statisticians and management staff are given the ability to perform ad-hoc reporting, as well as the ability to save, schedule, and share reports. This allows them to gather some of the data that they need without the need for DBA intervention. Custom code has also been written to provide the customer with summary data, accessible through the Discoverer program, so that they can access figures that they need, without needing to store the personally identifying information that must be destroyed within 24 hours.
• Write SQL scripts and PL/SQL programs to provide the customer with reports that cannot be generated through the Discoverer program. Many of these reports have to be guaranteed to be run before our nightly purge process commences. As the customer is both disallowed and lacking the technical expertise to write the scripts necessary to do this, these reports and scripts are maintained by our DBAs. Develop and maintain reports that are used to track either system performance or the reports used to track the performance of individual employees. The queries needed to generate these reports either use features not supported by Discoverer or are too complex for the Discoverer program to interpret.
• Write bash shell scripts, primarily used for scheduling reports that need to be printed, stored in external folders, or mailed to the customer, through the HP-UX crontab. Shell scripts are also created and maintained for database administration activities that are executed frequently and/or need to be performed in a consistent fashion. Other than reporting, some of these shell scripts are used for the various types of RMAN backups and restores, data pump imports and exports, physical standby creation, and the execution of stored PL/SQL programs.
• Apply change requests to each schema and database and make sure all are changes are captured in backups, for each stage of the four major builds that we do per year. These change requests can range from as simple as adding a constraint to a column to as complex as a total redesign of the business process, used by the customer, that needs to be implemented into our software product. Use Rational Clearquest to track these change requests.
• Create the build deployment documentation used when applying all changes for our builds, so that a consistent process is followed in each environment. Create and maintain standard operating procedures for database administration tasks.
• Use the Opatch utility to apply the quarterly Critical Patch Updates as well as the occasional one-off patch.
• Interface with the customer, on a daily basis, to better support its business needs. Work with the customer to come up with requirements for future builds and to prioritize the work that will be done.
• Use My Oracle Support (formerly Metalink) to interface with Oracle support staff when needed.
• Provide 24/7 on-call support to our customer.
• Assist software developers by providing the objects used by their code and helping them with writing/optimizing core application code.
• Assist test team with database-related issues, during the testing phase of our build process. Provide the test team with SQL scripts and PL/SQL programs to increase testing efficiency.
• Manage PII data by controlling access to sensitive information, and ensure the purging of sensitive information in accordance with federal law.
• Work with the external contractor that is in the process of designing a “Next Generation” version of our system, including reviewing and commenting on various design documents and participating in regularly scheduled design review meetings to share our system knowledge with the contractor.