Query Supervisor gives you the ability to not only monitor for expensive and runaway queries, but to take action while the query is running.
Identifying and managing long-running and resource-intensive queries can be challenging. You can try to identify and fix these queries before they are used in your production environment, but this is not always possible. For example, you may have a user perform a long-running ad hoc query that consumes a lot of resources, or you may have a query suddenly take longer to complete than usual. It is important to be able to detect these long-running, resource-intensive queries so that you can achieve improved systems management.
Query Supervisor provides you with the ability to not only monitor for expensive and runaway queries while a query is running but to take action when a predefined query’s resource-consumption threshold is reached. For example, you can define a threshold of 90 seconds for the total elapsed time for a query to complete. If a query takes longer than 90 second to complete, Query Supervisor will interrupt the query and call a user-defined exit program that can take actions such as sending a notification message, logging details about the long-running query, or even terminating the query.
Other tools allow you to understand your query performance either before or after a query is run. For example, the Db2 for i Predictive Query Governor allows you to stop a query before it is run if the query estimate exceeds a user-specified amount of run time or temporary storage usage, while the SQL Performance Center allows you to study a resource-intensive query after it completes. Query Supervisor, however, allows you to take action while the query is running, based on the actual resources consumed.
Query Supervisor can be configured to monitor for four query resource threshold types. These thresholds are the total CPU time used by the query, the total elapsed time for the query, the temporary storage that the query uses, and the total number of I/O operations. The ADD_QUERY_THRESHOLD and REMOVE_QUERY_THRESHOLD procedures are used to configure the thresholds Query Supervisor uses.
When a query is executed, the SQL Query Engine (SQE) monitors the resource usage. If one of the thresholds that was configured is met or exceeded, the query is interrupted, and the Query Supervisor exit programs are called. The Query Supervisor exit programs are written by you and registered with the Query Supervisor Exit Point, QIBM_QQQ_QRY_SUPER. You determine what actions are taken in the exit program. Information about the query, the job, and the threshold are passed to the exit program. You can use this information to take actions such as logging information, suspending the query, or sending a message to QSYSOPR. You can also choose to terminate the query. If you do not terminate the query, the query execution will resume once the exit program completes. Multiple thresholds can be defined, but a specific threshold is processed only once during the query’s execution.
The Query Supervisor thresholds can be applied to all queries across the system, or you can choose to apply the thresholds to specific users, jobs, and subsystems. The procedure ADD_QUERY_THRESHOLD not only defines the thresholds but also further configures Query Supervisor by including or excluding users from being supervised, specifying which subsystem to supervise, or specifying the minimum time between calls to the Query Supervisor exit program. For example, to set a threshold value for total CPU time of 90 seconds for all jobs except those running with the ‘BATCHUSR’ user profile, run the following call to the procedure:
CALL QSYS2.ADD_QUERY_THRESHOLD(THRESHOLD_NAME => 'Maximum CPU',
THRESHOLD_TYPE => 'CPU TIME',
THRESHOLD_VALUE => 90,
EXCLUDE_USERS => 'BATCHUSR');
You define what the exit program does. The exit program will interrupt the query, so the exit program should be as simple as possible. IBM has provided different example exit programs that you can use to send messages to QSYSOPR, terminate the query, or log information about the query. You can use these examples as a starting point and modify them to meet your unique needs.
It is important to understand and protect your production environment from long-running queries. Query Supervisor gives you the ability to not only monitor for these expensive queries, but also take action while the query is running. Query Supervisor is available with 7.3 TR10, 7.4 TR4, and the 7.5 Base release.
For more information about Query Supervisor, see https://www.ibm.com/docs/en/i/7.4?topic=tools-query-supervisor.
More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.
TRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now! Request Now.
Forms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.
Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online