Re: "Import succeded with warnings" and ERRORS!?

"Howard J. Rogers" <howardjr_at_www.com> wrote:

>> I have read that if the paths differ, the tablespaces will have to
>> exist prior to importing the dump. Let me know if you think this is
>> true, because it would mean that there is no sure way to import a dump
>> if some additional information about the exporting DB is missing.
>>
>
>Nope. It creates objects in the same tablespace where possible, or the
>User's default tablespace if not.

You are right, but we don't seem to agree about what we call a "successfull" import. If the objects go to a different tablespace from that where they came from, we have no duplicate DB, and we don't consider the import to be successfull.

>> Well, how could I import a dump as a different user from SYS or SYSTEM
>> if all other users have to be dropped before doing the import?

>You've kerflummoxed me now with the mother of all non sequiteurs!
>Why on earth are you dropping Users from the target at all?

An English dictionary wouldn't help, but I got the point anyway :-) I thought that dropping all users would be an effective way to clean the DB while the tablespaces themselves remain.

>That's what the ignore=y parameter is for. Truncate them if need be, but
>there's no reason to drop them or get rid of their users.

Good point. How can I truncate all objects of a DB without having to investigate its structure in detail and without writing complex scripts? Which objects should be excluded from being truncated? You see, I am learning a lot!

By the way: If I don't drop the users, and the imported DB does not contain some of the users left in the target DB, the resulting DB won't be a duplicate. We are going to keep some users from the old version of the target DB. I consider that even a security issue.

I can't still see a straight, reliable way to import a DB in Oracle and get a copy. Ingres was far easier.

>> The command was:
>> imp sys/syspw file=file.dmp ignore=y log=file.log full=y

>Well, that seems fine. You're certainly doing a full import, and you've got
>ignore on (so no, there is definitely no need to drop previous objects: if
>they already exist, import will simply move on to the 'insert into...'
>statement).

All right, import will move on to the 'insert into..' statement, and it will find records which it sees as duplicates and would eventually violate constraints, so the insert will fail, me being not so sure if the data in the records are really identical. Or the same data will be inserted again - not a solution either.

I don't know if I should emphasize again: I need an exact copy of the exporting DB!

Thanks a lot for this instructing discussion.

Rick Received on Sat Oct 20 2001 - 19:00:06 CDT