Skip to main content
UploadLanguage (EN)Support
BusinessMobileSocial MediaMarketingTechnologyArt & PhotosCareerDesignEducationPresentations & Public SpeakingGovernment & NonprofitHealthcareInternetLawLeadership & ManagementAutomotiveEngineeringSoftwareRecruiting & HRRetailSalesServicesScienceSmall Business & EntrepreneurshipFoodEnvironmentEconomy & FinanceData & AnalyticsInvestor RelationsSportsSpiritualNews & PoliticsTravelSelf ImprovementReal EstateEntertainment & HumorHealth & MedicineDevices & HardwareLifestyle
Laura Hood, profile picture
Uploaded byLaura Hood
PDF, PPTX2,008 views

Top 10 DB2 Support Nightmares #8

This document discusses common challenges in managing DB2 diagnostic log files, particularly their growth due to being append-only and strategies to control it, such as using the diagsize parameter and db2diag tool. It emphasizes the importance of keeping DB2 systems up to date with features and support, suggesting regular training and remote DBA support arrangements to ensure organizations do not fall behind. Lastly, it highlights the risk of being on unsupported DB2 versions and provides solutions to maintain system health and updates.

Technology◦
Download as PDF, PPTX
Top 10 DB2 SupportTop 10 DB2 SupportTop 10 DB2 SupportTop 10 DB2 Support Nightmares & How toNightmares & How toNightmares & How toNightmares & How to Avoid ThemAvoid ThemAvoid ThemAvoid Them #8#8#8#8
Part 8 – Keeping Up To Date Image of a junior DBA It’s too large to send Can we access the DB2 diagnostic log file (db2diag.log) ? It’s taking to long to open
Hhhhmmm, this is a common response. This is because the DB2 diagnostic files have been append only since time immemorial, their growth only restricted by the maximum space available in the file system they reside in. The only way to curb this growth if you were using pre-DB2 9.7 versions would be to rename the files which would then force the creation of new ones. Scripts had to be written to automate this process and to delete old files after a certain period.
Image of a junior DBA You have two options: 1 – The DIAGSIZE database manager parameter 2 - DB2DIAG tool with the –A or –archive option
DIAGSIZE database manager parameter • From DB2 9.7 onwards • Allows a DBA to control the maximum sizes of the DB2 diagnostic log and • administration notification log files. • When this parameter is set to a non-zero value, a series 10 rotating diagnostic log files and a series of rotating administration notification log files (only on UNIX and Linux) are used. • Smart enough to clean up the diagnostic log directory of old log files. • When the size of 10th file is full, the oldest file is deleted, and a new file is created. • DIAGSIZE is the value (in MB) of the total size of all the DB2 diagnostic log and administration notification log files on UNIX and Linux. • 90% of the total size is allocated for the 10 diagnostic log files and 10% of the total size is allocated for the 10 administration notification log files. • On Windows, DIAGSIZE is the value (in MB) of the total size of all the 10 DB2 diagnostic log files on Windows.
DB2DIAG tool • DB2DIAG tool with the –A or –archive option. • This archives both single and rotating diagnostic log files. • A timestamp, in the format YYYY-MM-DD-hh.mm.ss, is appended to the file name. • You can specify the name of the file and directory where it is to be archived. If the directory is not specified, the file is archived in the directory where the file is located and the directory name is extracted from the file name. • files on Windows.
Keeping Up To Date It can be difficult for many organisations to keep fully up to date with new features and indeed it is often the case that organisations are forced to stay on out-of-support versions of DB2. This can be a real issue when problems arise and they find that their DB2 systems are no longer supported by IBM. no longer supported by IBM.
The Moral 1. Where possible, try to keep up to date via fixpaks – new features are delivered in DB2 all the time. 2. Have a Remote DBA support arrangement with an expert DB2 organisation who will automatically keep your systems updated with the latest fixpaks. 3. Arrange regular training for DBAs, or take out a Consultancy on Demand agreement which allows you to use consultancy hours on training, database healthchecks or just to answer technical questions no longer supported by IBM.
Find out how our RemoteDBA or Consultancy on Demand services can help you to keep your critical DB2 systems up to date.
www.triton.co.uk/