|
Cloning of DB2 databases and tablespaces is a sophisticated and error prone process. Lots of input statements for the utilities must be tailored, jobs have to be scheduled and if you want to refresh an existing environment you have to be sure that the structures of the objects are compatible. But the biggest pain is the runtime. Conventional methods like UNLOAD/LOAD require a lot of CPU time and IO. The copy process takes hours and days. This implicates that the copy process cannot be done in the limited batch window. The constantly increasing amount of data makes it more difficult to do copies in a regular way.
|
|
Read more...
|
|
|
The goal of buffer pool tuning is to enable DB2 to make the best possible use of the available memory. Properly adjusted buffer pools save valuable resources as memory, DASD IO, and CPU. Tuned buffer pools are the basis of any system tuning, adapted pools help to avoid bottlenecks and last but not least save money.
|
|
Read more...
|
|
ULT is a powerful log analysis tool that makes it easy to observe changes to DB2 tables. Whether you want to propagate data to different tables, undo faulty changes that were made to a production table, or populate an auditing table with a detailed list of changes that have been made, ULT makes it easy for you to make the most of your DB2 log. |
|
Read more...
|
|
When using conventional methods like UNLOAD/LOAD or DSN1COPY to copy DB2 data you have the restriction to stop your source environment otherwise you will dare inconsistent data in your target environment which is not acceptable in most situations. Many shops must guarantee a continues availability of DB2 data and cannot afford to stop a production database.
|
|
Read more...
|
|
BCV5 allows for hi-speed copies of DB2 data-bases and table spaces. However, you may not always want or even be allowed to copy sensitive data from a production system to a testing or QA system. You have to adhere to data privacy regulations.
|
|
Read more...
|
|
|
Subsystem cloning no longer requires tying up valuable DB2 experts with a time consuming, tedious job that takes many hours or even days to complete. Get a zero RC every time and enjoy the luxury of having an automated and scheduler driven process. BCV4 makes “push button cloning” a reality. And best of all, go from start to finish in minutes not days.
|
|
Read more...
|
|
DB2 maintenance tasks include backup, reorg and statistics collection. TUC automates the generation and triggering of maintenance jobs. Real Time Statistics and thresholds are used to trigger utilities only when needed. TUC identifies any new object and refreshes the maintenance jobs automatically. Customization options allows the administrator to easily control utilities, objects and resources.
|
|
Read more...
|
|
XM4DB2 continuously inspects each mission critical DB2 system. It proactively looks for indicators for current or potential future problems, so called “exceptions”. An exception is an unacceptable situation that DB2 or another z/OS component cannot automatically solve. XM4DB2 alerts DBA staff and optionally can take action to rectify the situation. Working in the background it continually checks for availability of DB2 objects and the operational readiness of utilities, plans and packages.
|
|
Read more...
|
|
Why copy and entire table when a smaller and more manageable subset will get the job done? Depending on the stage of testing, a full copy of a table may not be necessary. If a particular test scenario only requires customers from a certain zip code area, why copy an entire table with thousands or millions of unwanted rows?
|
|
Read more...
|
|
|
