 |
 |
Archives of the TeradataForum
Message Posted: Wed, 30 Aug 2000 @ 08:30:57 GMT
Subj: | | Re: DBC.ACCESSRIGHTS error |
|
From: | | Julie Sorrell |
| To answer some other points raised in this thread; - you may need to bypass accessrights in order to ins or delete (I think bydefault
DBC doesn't have this privilege, but yours wouldn't be the first system I've seen where this has been added) | |
Bypassing accessrights definitely worked OK under the DBC logon last time, yes.
| you may well get away with no problems during normal processing - it all depends on whether those extra index entries are for
tvm's which actually exist or not. - dbc.accessrights can be skewed (well, usually 'lumpy' rather than skewed)but I doubt whether it's a
major issue. | |
Cheers for this Dave, I'm just going to make sure my backups are up to date and let it sit and fester until I've got more staff available
and more time to address the problem.
--
Julie Sorrell
| |