| imp-00021 error [message #70021] |
Wed, 03 April 2002 14:23  |
Chuck
Messages: 9
Registered: January 2002
|
Junior Member |
|
|
Hello,
I'm imp to a 8.0.4 database locally on the server. it always fails with the following msg. I'm using a full export file and fromuser, touser mode. I can connect to the database before and after the imp failed. and also I can do 'GRANT DELETE ON BASE_COVERAGE_VIEW to RIS_DML' in sqlplus without any problem after the imp failed. Anyone knows what is wrong?
Thanks in advance.
Chuck
IMP-00017: following statement failed with ORACLE error 3113:
"GRANT DELETE ON "BASE_COVERAGE_VIEW" TO "RIS_DML""
IMP-00003: ORACLE error 3113 encountered
ORA-03113: end-of-file on communication channel
IMP-00021: operating system error - error code (dec 9, hex 0x9)
IMP-00000: Import terminated unsuccessfully
IMP-00021: operating system error - error code (dec 9, hex 0x9)
|
|
|
|
| Re: imp-00021 error [message #70034 is a reply to message #70021] |
Thu, 04 April 2002 05:28  |
Grant
Messages: 578
Registered: January 2002
|
Senior Member |
|
|
|
Are you using a database link to to access this view? Are you importing from/to the same version of oracle? If you are using a DB Link then pre-create the DB Link. If not post your import command.
|
|
|
|
| Re: imp-00021 error [message #70038 is a reply to message #70021] |
Thu, 04 April 2002 09:07 |
Chuck
Messages: 9
Registered: January 2002
|
Junior Member |
|
|
I'm not using db-link to access this view. and yes the database version of exp and imp are same. and I even have the same problem when I exp/imp against the same database. this imp used to work fine daily, the problem happened since someone used a older cold backup restored the database. eveything works fine after the restore of the database but not this imp.
imp command is the simpliest (the export is full export):
imp system/xxx file=xxx.dmp fromuser=user1 touser=user1 log=xxx.log touser=user1
Thanks.
|
|
|
|
| Re: imp-00021 error [message #71117 is a reply to message #70021] |
Wed, 11 September 2002 00:45 |
Harps
Messages: 1
Registered: September 2002
|
Junior Member |
|
|
I just got this same error recently.
Oracle 8.0.6.2.0, Solaris 2.7
Import of FULL export, resulting in the same error, though on importing large tables (>100,000 rows).
I tried it a number of times, but it failed on different tables. Great.
I changed the import script to specifically say "full=n" and it worked fine.
Anybody look on Metalink for an explanation?
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
