import failed

All,

My full database import failed due to the following messages:
IMP-00058: Oracle error 3113 encounted
ORA-03113: end of file on communication channel
IMP-00058: Oracle error 1041 encounted
ORA-01041: internal error, hostdef extension doesn't exist
After the import failure, I found my database was done. I started up my database, then ran the full import again, but it failed and the database was shutdown again. Please help me solve the problem. It is a test database 8.0.6 on AIX.


I want to drop two tablespaces and recreate them with bigger database files. I will follow the following steps:
1. Do a full database export(exp system/passwd file=xxx full=y compress=y log=xxx)
2. Take the tablespaces offline, then drop them.
3. Delete all datafiles related to the tbs.
4. Recreate them.
5. Do a full import.
If step 5 failed for any reasons and can be fixed, what is the best solution to get my PROD database back to normal operation? It is running no archive mode on AIX.

Almost sounds like an Oracle bug.

look into Oracle logs: error with symbolic number "1331" is kind of "blue-screen" analog in Windows NT.
Best thing is to push Oracle here.

What is the export file size?

Check on Metalink for this error. There are many known reasons for this error.
-
If I understand you correctly, if you want larger files for the tablespaces, why not just resize them!!??

If what you want is to create bigger datafiles, there is no need to drop it. Just resize the datafile:
ALTER DATABASE DATAFILE 'filename'
RESIZE 4000M;

Halo & xyz2000:
I want to increase the size of datafiles, and reduce # of datafiles. I am not able to access to Metalink because we don't have oracle support.

Tamilselvan:
The export file size is about 400G.

Marist89:
What is a solution for this oracle bug?

LND:
I looked at the Oracle8 error book, but couldn't find any actions. I ran it from x-station.

3113 is Oracle bug which terminates current session. Hopefully not the whole database.

Solutions usually are some workarround or patching Oracle.

Depending on Oracle version, you can manipulate datafile size but not delete it.
To delete datafile you can try to move tables to another tablespace (with 'alter table move' clause).
I would generate a script for all tables, execute it to move tables to another tablespace and ... leave them in new tablespace with correct datafiles.

I think your OS is 32 bit.

If the export file is a single 400GB, then the import will fail.
You need to create multiple export files. The new export parameter FILESIZE can be used to determine the .dmp size.

If the export file is seperated into several smaller files, how to import the data? How to choose the file that is used by imp?

LND: You are right! It also shuts down the database whe 311
error occurs. What is patch name for this oracle bug?

tamslselvan: Sorry the dump file size is 4G not 400G.

anyway, what is in Oracle log and trace files? If you are allowed, post relevant data from logs, it will be much clearer what is going on.
Do it that way: backup and then delete old log/trace files,
do import to get the failure and look what in the logs.

as far I as can find 806 has two patch sets:
8.0.6.1 and 8.0.6.2
The are quite a set of 3113 errors related to import. Usual workarrounds are:

to cancel import of some objects. For example:
grants=no
indexes=no
constraints=no
recalculate_statistics=YES/NO for import and statistics for export

Some errors are related to tables with LOB columns, partitioned tables, views.

If import runs OK, then you can try to import some objects after. Those are constraints, indexes, grants, statistics.
If you now that particular object is causing problems, then can drop it before full export.