-
Importing a schema - Stopped at a table
hi all,
i had exported a schema with around 400 tables from a production database yesterday. Today, I am importing the same into a new (test) database server. And when i do that, everything goes fine except that, at a point it stops and don't go any further at all. The table where it stops has got around 2,00,000 thousand records. Could anybody tell me how I can find out why it is not moving any further from that table, as it is not coming up with any error message and is also not logged into bdump file.
This is the import line:
imp user/pword file='path' full=y log=logfileloc;
I am on 9i, 2000 XP Pro and I am using Oracle Import/Export utility.
Thank you for support in advance.
-
2,00,000 thousand is a lot of records, maybe it still importing them
-
Maybe it's building indexes.
-
hi all,
Can't there be any other reasons beside the ones you've mentioned?
Anyway, I am going to do the import again, let's see what comes up this time.
-
so you cancelled instead of looking at what it was actually doing?
-
Yeah. I had no choice. And also, I couldn't give much time for that. I turned into easy solution by posting my problem. But all in vain. . Anyway, I will be doing the import again within few hours. I will post if anything new comes up. Also, please advice where i can see the progress of an import, so i could trace.
-
Originally Posted by gtcol
Yeah. I had no choice. And also, I couldn't give much time for that. I turned into easy solution by posting my problem. But all in vain. . Anyway, I will be doing the import again within few hours. I will post if anything new comes up. Also, please advice where i can see the progress of an import, so i could trace.
Try using feedback=50000 during the import. This will give you some idea as to how fast it is importing the rows.
-
Could anybody suggest the background events that would make it wait? You know, deadlock situations
-
trace the sessions, see whats happening instead of guessing
deadlocks would be detected and resolved
-
Hi all,
The issue was like this:
The db I was importing into had insuffcient number of redo log files. So while importing, all the redo log files would get filled before they would be archived. So the lgwr would be waiting for a log file to clean up. I add few more redo log file groups. It went fine in the next import.
Thank you all for all your advices.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|