RE: imp index create monitoring
Date: Tue, 25 Sep 2012 15:43:10 -0400
Message-ID: <C95D75DD2E01DD4D81124D104D317ACA1C75A8CFA7_at_JAXMSG01.crowley.com>
I do not use export/import so much anymore -- since RMAN duplication is working for me now, but importing or rebuilding the indexes last is faster.
Sometimes it is better to import all the data and everything, and then the indexes, or rebuild the indexes.
I'm inferring that you are using 'imp' based on the Subject of this email -- which say use constraints = no, indexes = now etc, and then do a second pass with indexes = yes, constraints = yes etc....
Hope that helps... Same idea using impdp
Joel Patterson
Database Administrator
904 727-2546
-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Orlando L
Sent: Tuesday, September 25, 2012 2:57 PM
To: oracle-l_at_freelists.org
Subject: imp index create monitoring
All,
I was importing a small database into a 11.2 database. It took a while, I realized it was taking too long to build the indexes after importing the rows of some big tables. I remember in older versions we used to query the dba_segments for type temporary segments during index build which later got converted to permanent segments. This time I queried the dba_segments for temp segments during index build but did not see temp segments. However, the index count of the table would increase with time. I am wondering if anything has changed in 11g or if I should be looking at a different view.
As an aside, I think I will use a bigger sort area size/pga_ag_tgt to speed up index build process. I know I can rebuild the indexes at the end of import.
Orlando.
--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l
Received on Tue Sep 25 2012 - 14:43:10 CDT