Re: Import bug

"Sybrand Bakker" <postbus_at_sybrandb.demon.nl> wrote in message news:ph6phuclj4smkv9vj5mndrbppru7ev9n6e_at_4ax.com...
> Apparently your procedures are relying on the unlimited tablespace
> privilege and you didn't recreate the user with appropiate privileges.
> Instead of sorting that out you immediately resort to gross and
> exaggerated statements. There are millions of people that *can* work
> with import without any problem. Doesn't that tell you anything?

No but what your attitude tells me quite clearly is what a pompous ass you are.

I didn't recreate the user at all! That's imp's job! Do *you* understand that? Did you read the entire post before you answered? Did you know that a full import creates the users as well as their objects? You seem to know everything I would expect you to know this Mr "Sr. DBA"

The problem is that oracle is treating a full import as a normal database operation and not a special case when it comes to tablespace quotas. It should be special case. A reasonable person would expect an import of a full database export to restore the database to the exact same condition as when the export was taken. Import is not doing that in this case.

Think about the other things that a full import has to treat as a special case and circumvent normal database retrictions before replying. Like database privileges for example. I as the DBA doing the import do NOT have the right to grant permissions on someone elses tables, but when I do a full import it sure as hell happens. Received on Fri Jun 28 2002 - 14:56:00 CDT