Strange Import problem

I too a full export of a db on Win2K to create another db on the same platform. After creating the db and creating the users, I attempted to import the data with full=y, but it skips all the tables!! Any clues?? Thanx.

Quote:

---

Originally posted by Halo
I too a full export of a db on Win2K to create another db on the same platform. After creating the db and creating the users, I attempted to import the data with full=y, but it skips all the tables!! Any clues?? Thanx.

---

Did you create the tablespaces? If the tablespaces don't exist then the import will attempt to create them. If they already exist then it won't create the tablespace and thus the schema owner who has a default tablespace missing.

Are you getting any errors during the import?

Yes, the tablespaces have been created. I then created the users and assigned the privs. Import does not throw any errors. During import, all I see it doing is skipping all tables. It's a full export that I am importing with full=y, ignore=y.

The import does not have any errors? Did you spool a logfile?
Are you sure the table structures are not there?
Did you save the export logfile? Can you verify that there is data in it?

MH

No errors in the logfile, except for IMP 00046. I have 12 files (2Gb) each to be imported. Export logfile does show data being exported. The tables are not in the db. Imp logfile says:
..skipping table throughout the logfile to the very end.

IMP-00046 using FILESIZE value from export file of string

Cause: Either you did not specify the FILESIZE parameter in your IMPORT command, or you specified FILESIZE=0 and the export file was created with a non-zero value for FILESIZE. Import will use the value specified in the export file.

Action: No action required.

Did you set filesize to zero.

You may want to check the filesize parameter.
Even though Tahiti says that no action is required for the error.

Code:

---

IMP-00046 using FILESIZE value from export file of string

Cause: Either you did not specify the FILESIZE parameter in your
IMPORT command, or you specified FILESIZE=0 and the export file was
created with a non-zero value for FILESIZE. Import will use the value
specified in the export file.

Action: No action required.

---

Quote:

---

Originally posted by Halo
Imp logfile says:
..skipping table

---

This happens when you perform import with ROWS=N.

Ok, maybe he should post the .PAR file?

FILESIZE is an environmental variable, did you SET it?

Just as a sanity check to ensure that the dump file does indeed contain the table create statements this is what I would do.
I don't think this will work because it's on windoz and your dump file may be to big to open but....

copy the .dmp file to something else, do a more on it (in Windoz case open) and see if the table create statements are in it. Don't open the orginal .dmp file cause you'll mess it up. If they're in there but REM'ed out then you'll know you've done a indexfile= or something didn't go right with the export.

Since your export isnt that large, why not export using the parameter owner....owner=(your_scema,my_schema,...)

and import using parameter...fromuser=your_schema touser=yourschema ...

exporting full=y is really not necessary...why all the sys etc. tables?