This article is the official release announcement of Teradata Viewpoint 14.10 with an effective release date of May 6th 2013. With new enhancements in Alerting, Workload Management and Monitoring areas, this release of Viewpoint 14.10 continues to expand its scope and provide ability to monitor Hadoop systems along with Aster and Teradata systems.
The primary themes of the Viewpoint 14.10 release are to provide front end and visualization for new Teradata Database 14.10 features and Hadoop system monitoring. There are enhancements in Alerting, Monitoring and Management areas. Following are the highlights of Viewpoint 14.10:
Browser support has also been updated to reflect support for Firefox 18, Chrome 24, Safari 5.1, IE 8.x and 9.x.
The Stats Manager portlet complements the Auto Stats feature of Teradata Database 14.10 and will work with relaese 14.10 and later. Stats Manager allows DBAs/Users to efficiently manage their stats collection process. It is a new Tool option in Add Content | Tools menu.
Before we go into details of this new feature, let’s discuss why this is needed. Accurate cardinality and cost helps Teradata optimizer to decide an optimal plan. Statistics provides cardinality information to Teradata optimizer. Cardinality changes significantly with bulk load jobs making stats stale and inaccurate. Some times it is even challenging for an experienced DBA to understand which object stats would be beneficial which can result in collecting extra stats or missing collections of critical stats. Collect stats jobs usually are resource intensive jobs as they have many collect stats statements; it is always good to know what is needed and what is not and save some CPU cycles. Due to scheduling issues the user may not have enough time to complete the collect stats job and there is a need to prioritize and run collect stats for important or stale stats first. Stats Manager tool simplifies some of these tasks and help users automate the stats collection process. The Stats Manager portlet can be used to:
There are two main tabs in Stats Manager – Statistics and Job.
Statistics tab shows all objects (e.g. databases and tables) on the system, that have at least one statistic or that has at least one outstanding recommendation. The user can drill down on the data grid to navigate between the database, tables and Column. Figure 1 is example of Statistics by Database view.
Actions has three options -
Automate enables statistics to be collected by collect jobs.
Deautomate stops statistics from being collected by collect jobs.
Edit Collect Settings allows the user to edit thresholds, sampling, and histogram settings. The information bar displays the percentage of statistics that are approved for automation, allowing the user to determine if more statistics need to be approved for automation. Percentage of automated stats have collect jobs allows the user to determine if additional collect jobs are needed. Recommendations display a list of the recommendations by an analyze job. By clicking the link the user has an option to approve or reject recommendations given by analyze job. Statistics Table displays all objects with at least one statistic, or one recommendation that has not been approved or rejected. The table is configured using Configure Columns from the Table Actions menu. The user can automate any objects for stats collection process in this tab. This allows the user to approve statistics for collection by collect jobs. The user can also view Statistics detail reports by drilling down to stats object, see Figure 2.
Job tab displays the list of user-defined collect and analyze job definitions. From this view, the user can create collect stats and analyze jobs, manage existing jobs, and review job reports. Figure 3 represents the top Job tab layout.
Actions has three option -
New Collect Job enables user to define a job to collect statistics,
New Analyse Job enables user to define a job to evaluate statistic use and make recommendations and
View History lists the run status and reports for collect and analyze jobs over time.
Job Definitions Table displays summary information about jobs and allows drill down to show the details. Job Schedule displays a nine-day view of jobs that are running, scheduled to run, or have already run. Mouse over a date to have it show the list of jobs.
A Collect job generates and submits COLLECT STATISTICS statements to the Teradata Database for objects that were approved for automation in Statistic Tab. The user can assign a priority to individual COLLECT STATISTICS statements. see Figure 4.
The user can schedule a job to run for limited time and then have a new schedule to resume the job at a different time of the day (See Figure 5).
An Analyze jobs option allows the user to evaluate statistics status and get statistic-related recommendations. Analyzing objects enables the user to determine where additional statistics might be useful and identify existing statistics that are used frequently or are stale. Once the recommendation are generated the user can review and automate the object for stats collection process in Tab. See Figure 6 for various functions that Analyze job can perform.
The Viewpoint Log Table Clean Up feature can be used to cleanup job results stored in DBS TDStats database.
Teradata Viewpoint 14.10 supports Hadoop system monitoring for Hortonworks provided Hadoop solutions packaged as part of Aster 3 Big Analytic Appliance. A new Hadoop Services portlet allows users to monitor status of various services running on the Hadoop systems. Using expandable service view on MapReduce, HDFS and HBase users can view key metrics details for the selected services (See Figure 7).
The Aster Node Monitor portlet has been renamed to Node Monitor as it now monitors both Aster and Hadoop systems. Using the Node monitor portlet for Hadoop systems, users can view node level metrics, available Hadoop services, and the status of services for each node on the system. User can also view hardware statistics details such as CPU usage, memory usage and network activity. Navigating through the Hadoop system topology, users can also view detailed service component and JVM metrics for the HDFS and MapReduce services. (See Figure 8)
Like Aster system monitoring, Hadoop systems monitoring was also integrated with existing portlets. The usability, look and feel of the portlets were maintained but underlying data and metrics corresponded to the monitored Hadoop system. Below are the existing portlets that were modified to support Hadoop system monitoring:
In Viewpoint 14.10 we added three new reports in Query Monitor.
By Utility|By Jobwas added to display all the utility jobs that are running with drill down capabilities for individual sessions logged on by a particular Utility Job and the ability to further drill down to see session details. (See Figure 10)
By Vproc|By Skewed AMPdisplays AMPs with most skewed sessions that exceeded the CPU skew threshold set in the
PREFERENCESview. (See Fig 10)
By Vproc|By PEdisplays total number of sessions logged on to the PE and CPU value for the PE. (See Fig 10)
Teradata Viewpoint 14.10 introduced group throttles where a user can define throttle on a group of workloads. We also added new classifications by UDF, UDM, memory usage and collect stats. These features are dependent on Teradata 14.10. In Teradata Viewpoint 14.10 user can now unlock any ruleset if they have the appropriate permissions. Users can now also model a system Ruleset this is useful for comparing the Workload management features for different platforms (Appliance v/s EDW) or for different versions of Teradata.
Various new Alert options and Alert type were added in this release of Viewpoint.
In Viewpoint 14.10 we modified the Lock Logger architecture for Teradata Database14.10 and follow-on releases. When Viewpoint 14.10 is used with Teradata Database 14.10 the Lock Info collector uses the data written to the DBQL Lock Log table to capture lock information therefore DBQL query logging must be enabled with the “WITH LOCK” option.
We continue to have a voluminous release with copious features across a number of strategic areas. Hope you avail the new additions and improvements in Teradata Viewpoint 14.10. We always look forward to your thoughts and comments.
in Stats manager is entering stats job information all manual (i.e. is there a way to initialize the list from say DBQLog)?
Not very sure if I understood your question correctly. If you are saying how can I auotmatically generate collect list. You can choose to generate the list automatically by selecting the "Automatically generate the collect list" option in Collect list tab when you do new collect job. If you are saying how can I automate collect stats for entire system, in the Stats tab -> Action you can choose to Automate at the entire system and then create a collect job using Job tab. Let me know if this is not what you are looking for.
There is no change with regards to utility limits from 14.0 to 14.10. Are you trying to set up workloads instead of utility limits? You can set up workloads with request source and utility limits classification criteria, and then adjust the throttles per state. In this release release you can define throttles on group of workload.
Great article Shrity.
We are going to upgrade to 14.10 DBMS (and Viewpoint is already upgraded to 14.10) in next couple of weeks. I am eager to make use of this. But i do have my concern interms of impact. As Stats Manager make use of the DBQL options especially XMLPLAN, STATSUSAGE, and USECOUNT options for the objects being analyzed, are there any downsides of using Stats Manager by multiple people?
And is it a good idea to open the stats manager access to other teams apart from a DBA team. And is this portlet falls in to High/Medium/Low impact set of portlets?
To answer your questions..
If you referring to managing stats for same objects by multiple people, then there is no downside of using Stats Manager by multiple people. You enable XMLPLAN, STATSUSAGE, and USECOUNT once for the table/object.
Stats manager is a tool for managing and scheduling your system Stats collection process. This is usually done by specific individuals like DBAs so my recommendation is to limit it to the DBAs or whoever is in charge of looking after system stats collection process in your shop. If you are looking for opening up stats recommendation/analysis type of functionality to developers wait for next release of Teradata Studio.
Stats Manager portlets are Medium-low impact portlets...
As per TASM availability is concern, EDW platform has complete TASM features where as Appliance platform has restrictive features (no exceptions, WLs (category 3)). I heard about IWM option for SLES11 and SLES10. As per my understanding,
the SLES 11 IWM system has no options for ruleset exceptions or non-tactical workload exceptions. IWM systems only use tactical workload exceptions.
The SLES 10 IWM system has no options for exceptions.
What is special about the IWM feature? I can fee it is almost like Appliance platform features. Please help me with the difference b/w IWM feature for EDW platform and IWM feature for Appliance platform?