This article is the official release announcement for Teradata Viewpoint 15.10 with an effective release date of April 9th 2015. In addition to providing support for various Teradata products, the Viewpoint 15.10 release offers two new strategic reporting portlets, Query Log and Application Queries.
The primary themes of the Viewpoint 15.10 release are to enhance Teradata DB reporting capabilities and to support various products including Teradata Database 15.10. The highlights of the Viewpoint 15.10 release are:
Two new portlets were added in Viewpoint 15.10 which support Teradata Database 14.10 and newer. These portlets use data from Performance Data Collection and Reporting (PDCR) infrastructure.
The Query Log portlet enables Teradata Database Administrators to view key reports based on the historical DBQL data in the PDCRDATA.DBQLogTbl_Hst table in Teradata Database. In the screenshot below, it shows that 4 applications or 3 users utilized the system named "paper" on May 18th 2015. Next to it the bar chart displays a visual representation of the numbers of queries that fall into each category for the selected metric. The chart provides details such as number queries that had single AMP, two AMP or all AMP steps or number of queries resulted in an error etc.. The trend chart next to the bar chart helps analyze key performance indicators, aggregated by day for a period of time. The trend chart also helps users understand the impact of certain events such as a Teradata version upgrade or a TASM ruleset change on the key metric. Towards the bottom of the screen, the Logged Queries tab provides key metrics for queries logged on the selected date. The Suspect Queries tab displays information for all logged queries that are designated as suspect. Suspect queries are those whose values surpass thresholds defined for the Query Log data collector in the Monitored Systems portlet.
On drill down to Users or Applications displays details about the Users or Applications that were running on the system, such as logged queries or how many queries were classified as suspect queries etc. for a particular user or application. The screen shot below is from a drill down on Users.
Further drill down to a particular user gives summary stats about the user such as number of logged queries, number of queries classified as suspect queries etc.. The queries tab lists all the queries submitted by the user as well as all the queries that were classified as suspect queries. The trend tab can be used to plot multiple trend charts which helps analyze key performance indicators aggregated daily or weekly over a period of time. It also helps in analyzing the impact of certain events such as the Teradata version change or TASM ruleset change on the key metrics for a user. The trend chart for applications also helps analyze impact of an application version change if Teradata recommended QueryBand format is followed, as Viewpoint picks up the application name and version from the QueryBand.
In the queries tab, further drill down to a query gives query level stats as to time spent in delay queue, KPI, workload details etc in the SQL and Query Band tab, one can see SQL and Query Band information.
The Application Queries portlet helps application users understand their application performance. The Application Queries view displays summary information for each application and its different versions that submitted queries on a selected date. Drill down to a particular application gives summary stats about the application such as number of logged queries, number of queries classified as suspect queries etc.. The queries tab lists all the queries submitted by the application and all the queries that were classified as suspect queries. The trend tab allows users to plot multiple trend charts which helps analyze key performance indicators, aggregated daily or weekly over a period of time for the application. Users can also see the impact of certain events such as Teradata version change or TASM ruleset change or application version change.
In the queries tab, further drill down to a query gives query level stats as to time spent in delay queue, KPI, workload details etc, in the SQL and QueryBand tabs, one can see this information.
If the Teradata recommended QueryBand format is followed, Viewpoint automatically generates the application name using QueryBand information, administrator can assign Viewpoint users or roles to those applications in Query Group Setup portlet so that application users can see details about the applications in Application Queries portlet. If the Teradata recommended QueryBand format is not follwed, one can define applications in the Query Group Setup portlet and assign Viewpoint users or roles to them.
PDCR is a Teradata PS offering which collects historical data from various Teradata system tables (ResUsage, QueryLog, AmpUsage, LogonOff, TDWM) and stores within a PDCR database defined on a Teradata system. This database is then used to generate a series of customer performance analysis reports (Excel Toolkit and PS Viewpoint portlets).
The PDCR scheduling portlet allows you to create, monitor and manage PDCR scheduling jobs. You can see when a particular job was last executed, whether a job was successful or failed, if failed what was the error, how many rows were accessed, tables that were loaded etc.. It also allows you to send alerts for failed jobs or when PDCR staging/reporting database reaches space limit thresholds.
Following features in Viewpoint 15.10 requires Teradata Database 15.10 and above.
Teradata Database 15.10 added the Secure Zones feature to support multi-tenancy environment or sandbox environment. This feature restricts user access to set of database objects. Viewpoint 15.10 is built with Secure Zone awareness by assigning zones to a role in the Roles Manager portlet. Once a zone is assigned, Viewpoint users in that role when accessing the listed portlets below will only see details or queries accessing the objects assigned to a particular zone.
In the below screenshot, the "0 of 2" for "WD" system means that out of 2 zones defined on the WD system, no zones are assigned to Administrator role. One can click on the "0 of 2" screen to assign zones to a role.
Teradata Database 15.10 introduced a new locking mechanism to improve partition level access. Viewpoint will display these locks in the Query Monitor and Lock Viewer portlets.
Teradata Database 15.10 added an option to set QueryBands in profile which will be the default queryband for a session. In Viewpoint, the user can view the profile queryband in the QueryBand tab in the Query Monitor portlet.
Viewpoint 15.10 can now differentiate between a SQL that is part of a stored procedure or not. The SQL tab in the Query Monitor drill down will now display the stored procedure name.
Teradata Database 15.10 will allow users to log on as a proxy user and use access rights of that proxy user. Viewpoint 15.10 will show the proxy user details in the Query Monitor overview drill down tab and the Workload Monitor portlet. See the screenshot below.
Viewpoint 15.10 along with Teradata Database 15.10 can now report request level CPU and IO skew in addition to snapshot skew information. For this, the overview tab in the Query Monitor portlet was re-arranged.
Unless stated explicitly all new workload management features require Teradata Database 15.10 and newer. Viewpoint 15.10 supports the following workload management features:
In the Workload Monitor portlet when drilling into the delay request throttle view, there are additional tabs as shown in the screen shot below. This is supported for Teradata Database 13.10 and newer.
The Viewpoint 15.10 release supports Aster Database 6.10. With this release of Viewpoint 15.10 users can cancel any process or queries running on Aster Database 6.10 and above. This is done by having Viewpoint submit an asynchronous abort to the database.
Migrating to a new Viewpoint server or restoring a Viewpoint server has been made easy with minimized downtime. This was accomplished by only taking Viewpoint services offline while configuration data is restored. They system is then made available as the historical data is restored in the background.
Progress of the restore or migration can be monitored in the Viewpoint portal notification area.
Below are three restore/migration options that are now supported:
A list of e-mail addresses can now be configured to receive cluster related e-mail notifications
Hope you like these new changes in Tearadata Viewpoint 15.10. We always look forward to your thoughts and comments.
Yes, very nice article. Is there a developer api for transition of user written portlets from Viewpoint 14 to 15? These would have been developed using tdpdk-14.01.00.01
We officially discontinued PDK and discourage building any new custom portlets using PDK. But if you already have custom built portlets we will support that. Please contact your local CSR and ask them to get in touch with us.
I saw the issue when the system was is busy. But apart from the credentails are wrong fo the ID that you are using, it is also possible to see this error if there are any potential network issues due to which the Viewpoint server could not able to connect OR if the Database is too busy to accept the new connections. I suggest to submit an incident to GSC.
I was trying to access the Query Log portlet, but it is showing No Data Available, after checking the QueryLog Data Collector, I've noticed that there are no enough rights (Error Checking for New query Log data: [Teradata Database] [Teradata JDBC 15.10.00.050][Error 3523] The user does not have SELECT access to PDCRDATA.DBQLOGTBL_HST. )
So I gave the cocern role which provides the READ access to Viewpoint user on PDCRDATA (all tables). But still the data collector showing the Red Triangle (with exclmation) and query portlet with no data available. Am i missing anything here?
It's diffcult to comment without looking at your system on what might be wrong or missing. I would suggest you to open GSC ticket. Do you have PDCR installed in your environment, i.e. does PDCR tables has data in it ?
Yes, we do have PDCR. I will raise this GSC, but before that I just wanted to make sure to the driver supportability in terms of the version. Do we need to have JDBC 15.10?
lock viewer portlet in viewpoint is not showing the lock information. The base table is populating data but it is not reflecting in the viewpoint. Getting below error.
***Unable to get lock information! [Teradata Database] [TeraJDBC 15.00.00.11] [Error 9134] [SQLState HY000] AS_SHRED_BATCH:Error in function AS_SHREDTB: Insufficient memory to complete the XML operation.****
Will the XML_MemoryLimit value increase in the DBS control record - General field solve the issue?
I am not sure why you are getting this error. You can try increasing XML_MemoryLimit value if that doesn't work open a GSC ticket for someone to look at your box.