August 11, 2009 at 12:42 pm
I'm not too familiar with that error. I found a thread that may have a solution:
http://forums.oracle.com/forums/thread.jspa?threadID=326832.
If you are using OEM, I would instead use the command line import.
You may also want to open a thread in an Oracle Support site such as DBASupport.com at: http://www.dbasupport.com/forums/forumdisplay.php?f=1
August 12, 2009 at 10:55 am
rlondon (8/11/2009)
If you are using OEM, I would instead use the command line import.
I agree that it would be simpler to use the command line. Alter the database from mounted to open and try this:
imp.exe userid=sys@test file=h26b_full.Mar04 log=h26b_full.Mar04.txt show=y rows=n
(You will be prompted for the "SYS" user's password.) This will not actually import data, but it will create a text file showing you what it is in the export. The filename implies that it is a full database export - you might not want all of the users/schemas (in Oracle these are the same thing) that are in it.
If it is a full export you will need to create the user account(s) aka schema(s) in Test before import. Say you only want the "ACCOUNTS" user/schema, you could then import it like this:
imp.exe userid=sys@test file=h26b_full.Mar04 log=accounts.imp.txt fromuser=accounts
("imp.exe" is in "c:\oracle\product\10.2.0\client_1\bin" or similar, depending on your installation.)
This link might be helpful: http://download.oracle.com/docs/cd/B19306_01/server.102/b14215/exp_imp.htm#sthref2573
HTH
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply