|
Archives of the TeradataForumMessage Posted: Thu, 11 Sep 2003 @ 09:04:44 GMT
On Wed, 10 Sep 2003 11:59:51 -0700, Nancy Shen wrote:
I was unaware of the issue with method (1). Have you opened an Incident with the GSC on this? I will have to test that and get it fixed if it broke. There is nothing different about any of these methods. They all cause the exact same code to be executed. If you issue the RESET you should see an Event in the Windows EventViewer under Application which has the error code 10198 (10196 if you request a DUMP ) which contains the restart comment. Then there will be a series of 2900 Event Log messages as the DBS starts back up. This is regardless of which method above you use. In Fact methods 3 and 4 are just GUI wrappers around method 2. The only way to SHUTDOWN teradata (so that it doesn't automatically restart) is tpareset -x [comment] which is what method 3 issues when you click STOP TERADATA. Tpareset has a couple options. see tpareset -h for a complete list.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||