 |
 |
Archives of the TeradataForum
Message Posted: Fri, 28 Jan 2005 @ 16:54:49 GMT
Subj: | | Re: Maximum Limits of Users in Warehouse |
|
From: | | Dieter Noeth |
McBride, Michael wrote:
| The reference David made was to only restore the DBC and not the actual restore of the userdbs. In order for a true re-creation of an
entire instance of Teradata, you need to restore both the DBC AND all the databases (including users databases). | |
The databases/users are recreated by a dbc restore, but they're empty. You just have to restore the tables.
But a problem would be any views/macros within a user: if they're not backed up and restored there will be some entries within the
dbc.accessrights for those missing objects.
| Note: I see a problem if you only restore the dbc and not the users in from the archive. You may have a problem with a create user
statement, if the dbc thinks that user already exist. | |
IMHO dbc doesn't *think* it exists, it *really* exists after the dbc restore ;-)
| I have never tried to create a user after a restore of the DBC without a restore of the users databases as well. | |
I never restored dbc, but maybe i should try it once ;-)
Dieter
| |