Archives of the TeradataForum
Message Posted: Fri, 09 Nov 2001 @ 17:01:46 GMT
This is somewhat off the wall, but is it possible that last year, you changed your hashing algorithm? In DBSControl, there is a parameter called HashFuncDBC. About a year ago, I know there was a DR that required the site I was at to change that flag to a setting of '5'. As a result, any archive we performed prior to the flag change was done under the prior hashing algorithm. If we attempted to restore data onto the system with the new hash algorithm, we would see the same message you mentioned, "NEED TO RE-HASH ROWS".
Perhaps that's why you got the message when you restored after the sysinit last year????
FYI, there is also another flag in DBSControl called CorrectTimeStampHash which addresses a prior problem with hashing a primary index with a TimeStamp as part of the PI. I believe this was cause a situation similar to the one described above.
Thomas F. Stanek
|Copyright 2016 - All Rights Reserved|
|Last Modified: 28 Jun 2020|