EXECUTIVE SUMMARY

• 9 Years of experience in managing mission critical DB2 Database Systems for John Deere, GlaxoSmithKline, State of New Hampshire, IBM Financial Systems and First Data in Z/OS and AIX environments. Currently working as Senior SAP Basis DB2 Database Administrator for John Deere at Moline, IL.
• 4+ Years of technical leadership experience in projects like DB2 V9 Index Compression, SAP BI Best Practices Implementation and Monthly Archiving Metrics for John Deere.SAP-DB2 support, Partitioning large objects for GSK.
• 4 Years of experience as SAP Basis Administrator with John Deere and GSK. Expertise in projects like SRM 7.0 Build, SAP BW support, DB2 UDB HADR and SA MP Implementation, Solution Manager Unicode migration.
• PMI certified Project Management Professional (PMP © certified on 18-Oct-2010)
• “BEST OF IBM” Certificate from IBM for Database Administration Activities.
• “Certificate of Appreciation” from The State of NH DHHS for implementing TANF Project and NH EASY fed funded critical projects.

TECHNICAL AND MANAGEMENT SKILLS

• Projects Managed for Confidential,
• DB2 V9 Index Compression implementation for John Deere
• Monthly Archiving Metrics Preparation for John Deere SAP ILM Division
• SAP BI Best Practices Implementation for John Deere
• Offline Partitioning of very large SAP tables for GlaxoSmithKline
• DB2 DBA System Administration Support on Confidential,
• DB2 V9 Migration, PTF Installations, Apply DB2 maintenance, ETRs with IBM
• Backup technology using DB2 Backup System and also native FRBackup
• Restore System expertise for Database Refresh and Disaster recovery testing
• DB2 DASD Space Monitoring (ISMF), Monitoring Large object growth
• Performance Monitoring and Tuning (Bufferpool, GBP, EDM pool)
• Disaster Recovery planning and periodic testing
• Database Administration for DB2 UDB on Confidential,
• HADR implementation
• DB2 thin client installation project currently in progress for John Deere
• DB2 UDB V9 HACMP setup
• DB2 UDB V9 on AIX Installation
• Unicode migration for Solution Manager landscape
• Adding tablespace containers and auto-resize on tablespaces
• Extending file systems, working with storage to add disks to volume groups
• Restoring system to backup sync points for test systems on weekly basis
• SAP Basis Administration:
• Daily, weekly and monthly basis administration activities
• Transport management for indexes
• Setting up connect.ini file for new systems
• Archiving Support and administration
• SAP performance tuning, special parameter settings for BW & APO landscapes
• Opening SAP messages for issues and also opening connections for SAP
• Server Builds for SAP SRM 7.0 Implementation

Projects for Confidential, at Moline, IL

SAP DB2 Support for Confidential,

Duration

Nov 2008 – Till Date

Role

Senior SAP Basis DB2 DBA

Description: Confidential,SAP worldwide system comprises of 25 landscapes. The SAP North American Ag Landscape is the largest of all the landscapes and uses all the functionality of SAP R/3.The database size currently is closing to 4TB.There are 15 application servers hosting the NAaG landscape. Also Ag Europe, John Deere Power Systems, Ag Latin America, Ag China, Ag and Turf, Business Warehouse are some of the other larger landscapes.

Roles & Responsibility:

System DB2 DBA Z/OS support

• DB2 V9 upgrade
• Open and follow-up problems with IBM ETRs and SAP messages
• Partitioning very large tables - ICNV and also offline partitioning
• Executing Reorgs for partitioned tables during non-business hours (DB2 V8)
• Reorg System enhancements, scheduling drain, partitioned table reorgs
• DB2 backup system native FRBACKUP utility for backing up SAP systems
• Executing offline backups of SAP systems and restore system for db refresh
• Co-ordinate Storage tasks for MOD54 migration, FDRMOVE and FDRRPAS
• New System builds - prework and refresh related activities

DB2 UDB DBA support

• DB2 Connect V9 AIX Runtime Client Installation and migration
• DB2 thin client installation project currently in progress
• DB2 UDB V9 HACMP setup
• R3trans setup and also troubleshooting connectivity problems
• Adding and re-balancing tablespace containers and auto-resize on tablespaces
• Extending file systems, working with storage to add disks to volume groups
• Restoring system to backup sync points for test systems on weekly basis
• IBM License Management Tool Installation
• Taking special backups and also scheduling special backups
• UDB responsibilities for J2EE installation

SAP Basis support

• Daily, weekly and monthly basis administration activities
• Transport management for indexes
• Applying OSS notes for special projects like Unicode migration
• Archiving Support and administration
• SAP performance tuning, special parameter settings for BW & APO landscapes
• Opening SAP messages for issues and also opening connections for SAP

Performance Monitoring and Tuning

• Analyze statement cache, Explain long running queries, Capture traces
• Propose new indexes
• Bufferpool and EDM pool tuning
• Suggesting SAP parameter changes for performance enhancements
• BDLS enhancements for Basis Post Processing during DB refresh

Tools and Technologies:

SAP : SAP ECC 6.0
ZSeries Software: DB2 V9.1, Omegamon, ISMF, Active Datasharing, Netview,
SMP/E, DB2 Backup System, FRBackup for back up
pSeries Software: DB2 UDB V9.5 fp1, AIX5.3 TL08 SP4, HADR, SA MP,HACMP
Third Party tools: Omegamon, Neon

Project Title

Confidential,

Duration

Aug 2010 – Till Date

Role

Implementation of HADR and SA MP

Project Summary: The project involved installation and configuration of HADR and SAMP
for SAP PI landscape. This included moving the primary PPI database to another DB server located in a DR facility and creating the standby database on another DB server. As pre-work DB2 UDB software was installed to build the \'would be-primary\' PPI database in the DR facility. Deere Parts and Enterprise Warranty applications have low Recovery Time Objective OF 3 days and they use SAP PI. So HADR and SA MP with ACR were implemented to leverage two locations for recoverability.

Roles and Responsibility:

• Pre-work - build PI database on the new LPAR and do other DBA steps
• Pre-work - co-ordination with Basis team for basis pre-work steps
• Additionally as part of this project HACMP was re-configured for PI
• Co-ordination with basis and AIX team for the infrastructure changes
• Implement HADR and SA MP on the primary and standby database servers
• Perform post HADR work
• Note : There have been some issues (split brain) with SA MP and we are

in the process of uninstalling SA MP from the HADR systems

Project Title

Confidential,

Duration

May 2010 – Till Date

Role

DBA Support for multiple landscapes

Project Summary: The project involved installation and configuration of HADR and SA MP
for PI landscape. This included moving the primary PPI database to another DB server located in a DR facility and creating the standby database on another DB server. As pre-work DB2 UDB software was installed to build the \'would be-primary\' PPI database in the DR facility. Deere Parts and Enterprise Warranty applications have low Recovery Time Objective OF 3 days and they use SAP PI. So HADR and SA MP with ACR was implemented to leverage two locations for recoverability.

Roles and Responsibility:

• Pre-work - build PI database on the new LPAR and do other DBA steps
• Pre-work - co-ordination with Basis team for basis pre-work steps
• Additionally as part of this project HACMP was re-configured for PI
• Co-ordination with basis and AIX team for the infrastructure changes

Project Title

Confidential,

Duration

Sep 2009 – Till Date

Role

Technical Lead and Project management

Project Summary: Some of the large non-partitioning indexes in SAP AG-Europe
SAP NA-AG, SAP-BW production environments are reaching the critical upper limit of 64 GB. As part of risk mitigation Index Compression feature of DB2 V9 was tested and is being implemented across the mentioned SAP landscapes.

Roles and Responsibility:

• Project Management Plan preparation
• Communication management with performance, senior management team
• Send DSN1COMP reports to performance team for BPOOL recommendations
• Researching related SAP Notes (1336036 as the base), IBM PTFs
• Change task creations ,allocate resources, automate the process by REXX
• Change Implementations for Bufferpool (local and group)
• Change Implementations for Index Compression
• Outcome – Business outage risks have been eliminated.

Project Title

Confidential,

Duration

July 2009 – Sep 2009

Role

Technical Lead and Project management

Project Summary: Confidential,management division of SAP practice used to run TANAA for a monthly report to identify the top 30 tables for a system. This used to run for about 12 hours, CPU cost was 12k USD/year and there were man hours for the process. SAP DB2 team was involved to come up with a reporting procedure.

Roles and Responsibility:

• Identify stakeholder requirements for the monthly metrics
• Design the SQL that would pull top30 tables, rowcount, size and partitions
• Design job streams to execute the SQL across all the production landscapes, format, merge the reports and e-mail the weekly report to stakeholders
• Set up ESP events to execute the job streams on monthly basis
• Work with contracted vendor resources to setup tasks, implementation etc
• Outcome – Process cost lowered by 9000$/year and automated process.

Project Title

Confidential,

Duration

May 2009 – Oct 2009

Location

Moline,IL

Role

Technical Lead and Project management

Project Summary: SAP BW team partnered with SAP DB2 support to work more closely to identify special SAP parameters, ZPARMS and implement the best practices for SAP BI.

Roles and Responsibility:

• Work with SAP performance to identify long running SQLs and propose indexes
• While migration to DB2 V9, adjusting the ZPARMS as described in SAP note 1032273
• Educating users to select RUNSTATS option after dataloads
• Keep track of current PTFs through SAP note 81737 and build maintenance rounds
• Work with SAP BW team to partition E-Fact and F- fact tables
• Applying SAP note 894045 for fast deletion of table partitions for PSA and F-fact
• Enforcing periodic commits while doing mass deletes
• Outcome – Better visibility for handling the special systems like SAP BW, SAP SCM

Project Title

Confidential,

Duration

April 2009 – Jan 2010

Role

SAP SRM Support

Project Summary: Confidential,is installing SAP SRM 7.0.The project started with the Define Phase in Jan-2010 and go-live happened in Nov-2010. The build phase of the project involved SAP Functional and technical consultants to complete configuration, custom development, identify batch jobs, restart procedures, develop reports and interfaces, conduct code review, create new security roles, create disaster recovery plan, build test plan. Once the above were complete Installation is being done in the test systems. This involves SAP Basis and SAP DB2 team for server and new database system builds for Sandbox, Config and Quality.

Roles and Responsibility:

• Work as part of the core architecture team to understand requirements, timelines
• Complete pre-work for new system builds
• New system builds – db2 system builds (datasharing and non-datasharing)
• DB2 connect installation on the application servers

Projects for GlaxoSmithKline

Project Title

Confidential,

Duration

January 2007 – Oct 2008

Location

Durham,NC

Roles

• SAP Basis Support
• SAP BASIS DB2 Lead (Satyam)

Description:

Confidential,provides integrated processes, systems and data based on best practice ERP principles. GSK is committed to using SAP R/3 software in manufacturing. The DB size is around 1.7TB.

Roles & Responsibilities:

SAP Basis Support

• Perform the daily SAP Basis administration activities
• System and work process overview : SM51,SM50
• Check system log - sm21 (errors ,warning, security, database events)
• Review and resolve ABAP Dump analysis - st22
• Maintain Logon groups – SMLG
• CCMS Monitoring and addressing the alerts – RZ20
• Look for any failed updates – SM13 (proceeding according to GSOP)
• Check for old locks – SM12
• Monitoring critical jobs and also address the cancelled jobs – SM37
• Local and Remote operating system monitoring – OS06 and OS07
• Review workload statistics – ST03
• Tune summary instance –ST02
• Check for spool that are in request for over an hour - SP01
• Perform the weekly SAP Basis administration activities
• DB backup monitor to ensure proper backup - DB12
• Monitoring the output controller – SP01
• TemSe administration – SP12
• Monitoring the weekly critical jobs – SM37
• Transport Organizer activities – SE01
• Other Important SAP Basis Administration Activities
• Client maintenance including client creation, local client copy, remote client copy
• Created, Managed and Release Change Requests for transports using

Transaction codes SE01, SE03, SE09 and SE10.Resolved TMS problems
(STMS, SE03).

• 46D_EX2 kernel upgrade Project successfully executed
• Applying support packages to maintain the system up-to-date
• Applying SAP Notes
• Perform Monthly Data Archiving and Post archiving activities

SAP Basis DB2 DBA Support

DB2 System Administration Activities

• Put Level Maintenance to apply PTFs, Maintaining ZPARMs
• Maintenance of DB2 Catalogue and Directory
• DB2 Log monitoring during heavy periods of activities, migrating archive log datasets if needed during archiving activities
• Raising ETRs with IBM on DB2 issues, follow-up and closure of the ETRs

Capacity Planning and DASD Administration

• ISMF Reporting on a weekly basis for the Tablespace and Index volumes
• Monitoring the temporary pool volumes (Imagecopy / Reorg) Allocations/distribution of log datasets

Partitioning VBIG tables during the monthly maintenance windows

• Partitioning VB Tables like SOC3, CDHDR, VEKP, VEVW during 4 hr MW
• Normally SE14 used to identify the limit keys but for some very VBIG tables technique of unloading Keys/DFSORT is used
• Timesaving technique like creating NPSIs with DEFER YES and then parallel rebuilding using the two LPARs are employed
• SAP Note 83335 used to determine the RUNSTATS option

Performance Monitoring and Tuning
Bottom up Approach:

• Bufferpool data collected during peak activities
• Using ST04 – Dynamic Statement Cache

Top down Approach:

• SE30 is used to do Runtime Analysis for reported slow transactions/jobs
• ST05 used sometimes if specific SQLs are known to be causing problems

Parameter Adjustments:

• Adjusting BP Thresholds, size, proper allocation of tablespaces and index

Archiving Support

• SARA, SARI, DB15 - Monitoring archival jobs, checking ADMI_FILES table for the archival size. REORG/ Alter the space / REORG to reclaim space.

Disaster Recovery Testing

• Disaster Recovery Planning and Participation in Quarterly Testing
• System and Application Recovery

24X7 Oncall Support – Remedy

• Daily Imagecopy jobs, weekend support for the reorg and Runstats jobs
• Support for Log Shortages, Maximum extent reaches etc

Technology and Tools

SAP: SAP R/3 4.6C, SAP R/3 Basis, SAP R/3 Database Server, SAP R/3 Enqueue server, SAP R/3 Gateway, SAP R/3 ICLI, SAP R/3 message server
ZSeries Hardware: IBM 9672-Z47 Server (2), IBM 9672-R06 Coupling Facility, IBM 9037 Sysplex Timer, IBM 2105 Storage Subsystem (2 ESS “Sharks”).
ZSeries Software: DB2 V7.2, DB2 PM, ISMF, Datasharing, GDPS, XRC, Parallel Sysplex, Netview, SA/390, TWS, SMS, UNIX System Services
DB2 Tools : BMC QUEST (TOAD), DB2 Connect, DB2 PE
SAP add-on tools : REDWOOD scheduler, Interscope (WILY)
REMEDY : Centralized tool for incident/problem management

Educational : Production Engineering