Import bug

From: Norman Dunbar <Norman.Dunbar_at_lfs.co.uk>
Date: Mon, 1 Jul 2002 09:47:48 +0100
Message-ID: <E2F6A70FE45242488C865C3BC1245DA7024D7F3D@lnewton.leeds.lfs.co.uk>

Morning all,

I've been lurking on this one, and have surfaced now to point out something that no-one else has done yet (I hope - I seem to be missing some postings in this NG - firewall troubles again ?)

Chuck things that Import is a 'special case' - why ? He thinks that running it as a DBA user should impart special privs - again, why ?
Check out a dmp file and one of the commands in it is CONNECT <user_bieng_imported>
followed by a load of create table, insert into table, create index, alter table add constraint commands. All of which are run as the user being imported.

Therefore, it follows, that if the user being imported has no quota, then it cannot do any of the above.

Cheers,
Norman.

PS. If you really want to do a restore procedure that makes the new database identical to the old one, exp/imp do a LOGICAL copy and not a physical copy. Use a cold backup/restore instead.

Norman Dunbar
Database/Unix administrator
Lynx Financial Systems Ltd.
mailto:Norman.Dunbar_at_LFS.co.uk

Tel: 0113 289 6265
Fax: 0113 289 3146
URL: http://www.Lynx-FS.com


-------------------------------------

Received on Mon Jul 01 2002 - 03:47:48 CDT