Archives of the TeradataForum

Message Posted: Tue, 07 Dec 2004 @ 13:25:04 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

/to your point, "Jon Christie responded to your posting and made a couple of statements that confused me somewhat. Jon stated "Until a fix is available I would strongly recommend that you put ALL join indexes in databases strictly reserved for join indexes and NEVER archive any of these databases. This will protect you from the worst problems..." "

I tried Jon's suggestions to no avail. I did not think that it would work, but Jon is the kind of person that you cannot just dismiss. He is usually spot-on.

FYI - The error message description has nothing to do with the real restore error.

I haven't experienced this error in any other circumstance.

Our apps build the join indices while the front-ends (Oracle Express) are down. I suppose that if you are accessing data thorugh an access lock while loading data, you might see the problem. As you point out, given the timing required to meet this condition, the odds of hitting it would be small. Without access locking on the read, I would think that the normal locking mechanism would prevent it. I suspect that the error message is pointing you in the wrong direction.

Sorry that I can't offer any help.

Glen

	<Prev	Next>		<<First	<Prev	Next>	Last>>