The process seems to become impossible when the customer does not know a user to use for a restore and we try to...
do a full restore. One issue I run into is that there is a different file structure at which the import fails. Another problem is not knowing objects that need to be precreated, and also, the full restore seems to overwrite the password of default DBA accounts, making the database inaccessible.
There must be a better way. What do you recommend? Must we require specific information or can you give us a list of specific steps and commands that will ensure a good restore?
imp file=my_dump.dmp show=y log=import_show.txt full=y
Make sure you do the entire dump file (FULL=Y). The output will scroll by really fast. After it is done running, open the text file in any text editor. You will be able to see all CREATE commands, etc. This way, you can see what the file structure is and precreate the necessary tablespaces. You will be able to precreate any needed users and roles so that your real import will not fail.
Dig Deeper on Oracle database backup and recovery
Related Q&A from Brian Peasland
Oracle expert Brian Peasland answers one reader's question about common pitfalls when connecting Oracle to outside programs. Continue Reading
One reader asks expert Brian Peasland a question about datafile sizes with the Oracle RMAN duplicate 10g command. Continue Reading
Managing parent table-child table relations in Oracle SQL environments is key to efficient programming. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.