Use of indexfile in import....

Question

Hi All,
Today I read somewhere to use of indexfile which will imporve in performance of import.
I do as mentioned below:
1) exp scott/tiger full=y file=scott.dmp( take 2ndoption USER for export)
2) imp test/test file=scott.dmp full=y indexfile=index.sql
--- imp skip the table with message eg. skiping table during imp
--- once imp finish, open index.sql file and add password at connect statment and remove all comments for create and alter table...
--- run this index.sql on sql prompt ...gives msg as table created and alterd but there is not any data in table.
So what to do now if I want table's record also ?
That might be impact on performance on big database but what about data?
Can any one suggest me?
Thanks...

Answer 1

--- imp skip the table with message eg. skiping table during imp
--- once imp finish, open index.sql file and add password at connect statment and remove all comments for create and alter table...
--- run this index.sql on sql prompt ...gives msg as table created and alterd but there is not any data in table.indexfile is useful when you need to get the metadata information in a SQL script format or used for rebuild indexes.
If the tables and indexes that you have exported are from different tablespace than where you import them. you can use show=y and indexfile to generate the ddl script and edit them with the respective tablespaces for tables and indexes.
create the tables using the ddl sql from indexfile.
import just the data using indexes=n and ignore=y constraints=n in imp command line.
Now, create the indexes either using the script from indexfile or use imp to import them using rows=n which will import the indexes.
I see you wanted to speed up the index creation process. use the sql file generated from indexfile and create the indexes using PARALLEL and NOLOGGING which would speed up the index creation process. For Larger indexes, this would really help.
HTH
Anantha.