This is a perfect example of why (I always say) you should take more than you need, or THINK you need.
As Jeff pointed out exporting indexes will cost next to nothing since you are only grabbing the DDL to create them.
If you dropped the schema and did not export the indexes you are in a world of shiete.
Can you pull the index DDL from another (developement) environment?
Just confirming
Oracle8i Enterprise Edition Release 8.1.6.1.0 - 64bit Production
so if i do
exp user1/user1 full=Y rows=Y indexes=N file=xyz.dmp
i would not get DDL for index creation when i import
imp file=xyz full=Y ......
now i am just working out how i can create space for export in Unix box .
1) i have to take exp of full database , which is taking 20GB
2) i have just 24 GB free in our Unix box
3) but we have remote server where we can ftp our export dump .
but
can i directly export/import to remote server using exp /imp command
quicker, yes. better, depends. If you want to change something about the index, then no, it is better to pre-create it than to let import create it wrong.
Originally posted by Mr.Hanky I thought import loaded the table then built the index. Isn't that why you get failed to build errors on import from tme to time?
Bookmarks