{"id":1890,"date":"2019-12-28T13:38:04","date_gmt":"2019-12-28T13:38:04","guid":{"rendered":"http:\/\/www.theSQLReport.com\/?p=1890"},"modified":"2019-12-28T13:38:04","modified_gmt":"2019-12-28T13:38:04","slug":"node-check-utility-in-teradata","status":"publish","type":"post","link":"https:\/\/www.theSQLReport.com\/?p=1890","title":{"rendered":"node.check Utility in Teradata"},"content":{"rendered":"<p>The &#8220;node.check&#8221; utility has been been around for a while with Teradata.\u00a0 Recently I was working with Teradata&#8217;s Hardware Support team, and watched them use this utility to uncover a hardware issue.\u00a0 In the log file that this utility produces, Teradata support found evidence that a CPU was going bad.<\/p>\n<p>The best information I can find on the &#8220;node.check&#8221; utility is that it &#8220;verify system integrity of Teradata system utilizing PCI based nodes&#8221;.\u00a0\u00a0 The only references I can find to this utility in TAYS (Teradata At Your Service), is reference to the errors this utility uncovers.\u00a0 I was not able to find in TAYS anything about the utility itself or the switches that can be used with it.<\/p>\n<p>Teradata support says this utility is safe to run, but unlike other utilties it must be run from the &#8220;\/home\/support&#8221; directory.<\/p>\n<pre># cd \/home\/support\r\n\r\n# .\/node.check -nc<\/pre>\n<p>Depending on your system, this utility will take a couple of minutes to run.\u00a0 Once it completes, it will display the location of its output log to the screen.\u00a0 If you grep the log for the word in caps &#8220;ERROR&#8221; or &#8220;WARNING&#8221;, you can view all the errors or warnings the utility found.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The &#8220;node.check&#8221; utility has been been around for a while with Teradata.\u00a0 Recently I was working with Teradata&#8217;s Hardware Support team, and watched them use this utility to uncover a &hellip; <a class=\"readmore\" href=\"https:\/\/www.theSQLReport.com\/?p=1890\">Continue Reading &rarr;<\/a><\/p>\n","protected":false},"author":1,"featured_media":1896,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[54],"tags":[178,179],"class_list":["post-1890","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-teradata","tag-node-check","tag-utility"],"_links":{"self":[{"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=\/wp\/v2\/posts\/1890"}],"collection":[{"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1890"}],"version-history":[{"count":7,"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=\/wp\/v2\/posts\/1890\/revisions"}],"predecessor-version":[{"id":1898,"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=\/wp\/v2\/posts\/1890\/revisions\/1898"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=\/wp\/v2\/media\/1896"}],"wp:attachment":[{"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1890"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1890"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1890"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}