HOADUG – Quarterly meeting
September 14th, 2015
University of Kansas Edwards Campus
12600 Quivira Road – Overland Park, KS 66213
SEGUS & SOFTWARE ENGINEERING present
There are many reasons to clone DB2 environments, like for development, DR testing, QA, audit or just to set up a new SAP environment.
Cloning procedures aren’t rocket science, but using the right procedure can make it a one knob process that even handles terabytes of data in a fraction of time. This presentation focuses on creating an exact copy of a full subsystem/data sharing group or a subset of objects and shows how to consistently duplicate objects/ without compromising availability. Implementing fast dataset rename steps and your own high speed DSNTIAD can make even a fresh copy of large ERP/CRM systems like SAP available in minutes.
Working on the object level should consider any kind of naming conversion for DB2 objects, working on the subsystem/data sharing group level usually requires to clone into another subsystem or group ID. Non data sharing to data sharing and vice versa can be covered with some extra steps as well as cross DB2 version cloning.
The goal is fully automating cloning scenarios including individual steps. See how easy and flexible cloning can be when exploiting the strengths of XML even for complex scenarios and get introduced to the powerful features your storage technology offers to make it highly efficient and incredibly fast!
1. Cloning basics
What type of cloning is the right choice for a given requirement?
What are the gotchas and where are the shortcuts?
What to take care of – beyond DB2?
2. Cloning details
XML scenario definition – the sky is the limit!
Naming conversion – how do you want to be called today?
The path to DB2 Data Sharing – how many members do you need?
How can I exploit instant copy technology, like Flashcopy?
3. Tips and Tricks
DB2 cross version cloning and system cloning
Cloning costs considerations
Do’s and Don’t’s
Ulf Heinrich is the Director of Solutions Delivery at SOFTWARE ENGINEERING GmbH. Ulf’s specialties are DB2 availability and performance, focusing on the growing requirement for 24×7 operations and cost reduction. As a consultant at large customer sites, he has implemented database maintenance procedures and recovery strategies, and also experienced the pitfalls of recovery scenarios under real world recovery pressure. Ulf’s activities cover EMEA, as well as North America through SE’s U.S. subsidiary, SEGUS Inc.
“Nothing is more expensive than a missed opportunity” (H. Jackson Brown, Jr).
This is especially true when it comes to SQL Tuning!
There are many low-hanging fruits within easy grasp of anyone tasked with tuning their systems. But how do you know what is dangling within reach if you can’t see it?
Find out how a modern DB2 z/OS SQL warehouse can collect and store all executed static and dynamic SQL (plex-wide) with basically no overhead.
By comparing SQL statements side-by-side, the “easy pickings” will immediately become apparent. But why stop there? Experts can effortlessly dig deeper and find the totally hidden gems: Disc Problem Detection, Delay Detection, Never executed SQL, SQL Timeline. Precisely pinpoint specific areas to target and get the most out of your DB2 system – while reducing costs.
1 – Tuning SQL – how we always done it
2 – Single SQL, package, application
3 – Tuning SQL – year 2004 – ACCESS PATH comparison and simulation
4 – Tuning SQL Revisited – A new methodology
5 – Harvesting the low hanging fruit
Roy Boxwell has more than 26 years of experience in MVS, OS/390, and z/OS environments – 21 of those in DB2. He specializes in installation, migration, and performance monitoring and tuning. Roy leads the SEG development team responsible for the real time database maintenance solutions. He is also an active participant, speaker and contributor on the IDUG DB2 Listserv and sends out a monthly DB2 z/OS Newsletter.