Import Hanging-no Error Msg

[Ablakios]

HI EVERY RAVENS, STEELERS,AND GIANT FANS,

The following is a snapshot of my import hanging at the character set.

Export was successful. I was trying to export from db1 and import to db2 on the same server.

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\>SET ORACLE_SID=DB2

C:\>J:

J:\>imp system/manager full=y file=exp_full.dmp recordlength=65535 commit=n analyze=n ignore=y buffer=5000000

Import: Release 8.1.7.0.0 - Production on Thu Oct 31 22:13:04 2002

(c) Copyright 2000 Oracle Corporation. All rights reserved.


Connected to: Oracle8i Release 8.1.7.0.0 - Production
JServer Release 8.1.7.0.0 - Production

Export file created by EXPORT:V08.01.07 via direct path

Warning: the objects were exported by app_user_name, not by you

import done in WE8ISO8859P1 character set and WE8ISO8859P1 NCHAR character set

is there any problem with the character set?

[ggnanaraj]

Originally posted by Ablakios

J:\>imp system/manager full=y file=exp_full.dmp recordlength=65535 commit=n analyze=n ignore=y buffer=5000000

You could do the same with 'commit=y'. You should also check your alert log for any error messages during import.

HTH.

[Mr.Hanky]

Darn Ravens fans!!

You should set commit=Y As ggnanaraj mentioned.
Why specify a buffer if you do not commit?
You are making less sense then our pathetic offense.


Seriously, if you do not use the commit Oracle will attempt to load the entire table before it commits.
If the table is too big and this fails, it will take time to rollback all that was imported.



MH

[Ablakios]

Hey Mr.Hanky the GIANT
If I am not mistaken setting commit=y will tell Oracle to commit after every table and help to avoid ORA-01562 Failed to extend RBS.
What if I have a lot of tables and big ones? In my case I do and I sure don't want Oracle to commit after every table. Does it make sense now?

Below is the same import hanging with COMMIT=Y as you suggested.

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\>SET ORACLE_SID=db2
C:\>J:

J:\>imp system/manager full=y file=exp_full.dmp recordlength=65535 commit=Y ignore=y buffer=5000000

Import: Release 8.1.7.0.0 - Production on Fri Nov 1 10:40:24 2002

(c) Copyright 2000 Oracle Corporation. All rights reserved.

Connected to: Oracle8i Release 8.1.7.0.0 - Production
JServer Release 8.1.7.0.0 - Production

Export file created by EXPORT:V08.01.07 via direct path

Warning: the objects were exported by app_user_name, not by you

import done in WE8ISO8859P1 character set and WE8ISO8859P1 NCHAR character set

What do you say now?

[Mr.Hanky]

COMMIT in conjunction with BUFFER will tell Oracle to commit after ever ??? bytes.

If buffer=4000000, than a commit will be issued after 4 million bytes (3 megs give or take). This way the commit is issued during the table import.
http://technet.oracle.com/docs/produ...76955/ch02.htm

The Oracle default is to try the entire table and if they are big it can blow out your RBS.

How long does this hang for?
Are you sure it has not started and is just reading the .DMP file?
How big is the .DMP file?

MH

[nagarjuna]

what is the configuration of your server??? and dumpfile size?? and howlong did you wait before coming to the conclusion that import is hanging??? It depends on the hardware configuration..