Re: Export/Import with Physical Standby

  • From: Ian Cary <ian.cary@xxxxxxxxxxxxxx>
  • To: david.barbour1@xxxxxxxxx
  • Date: Fri, 2 Oct 2009 09:57:13 +0100

Just a couple of questions regarding you approach.

1. Why not use the REMAP_TABLESPACE option in datapump rather than having
to extract the DDL and manually recreate the objects.
2. If you do use the DDL approach I'd suggest just creating the tables
first, then import the data only and then create indexes/constraints as
this should quicker.

Another possiblty is also to use the COPY command which will cope with your
LONG columns and then rename the objects afterwards rather than using
expdp/impdp.

Cheers,

Ian



|---------+----------------------------->
|         |           david.barbour1@gma|
|         |           il.com            |
|         |           Sent by:          |
|         |           oracle-l-bounce@fr|
|         |           eelists.org       |
|         |                             |
|         |                             |
|         |           01/10/2009 22:44  |
|         |           Please respond to |
|         |           david.barbour1    |
|         |                             |
|---------+----------------------------->
  
>--------------------------------------------------------------------------------------------------------------|
  |                                                                             
                                 |
  |       To:       oracle-l@xxxxxxxxxxxxx                                      
                                 |
  |       cc:                                                                   
                                 |
  |       Subject:  Export/Import with Physical Standby                         
                                 |
  
>--------------------------------------------------------------------------------------------------------------|




Good Morning,

I've got a requirement to move about 300GB of table and index data from the
current tablespaces into new tablespaces.  There is a physical standby in
place.  The standby is located in another city.  The database is 7TB in
size.  I am running Oracle 10.2.0.4 on AIX 6.1.

The standby is currently mounted with the STANDBY_FILE_MANAGEMENT
initialization parameter is set to AUTO.  We are not using ASM.

I'd like to get a sanity check on the plan I've put together.

Stop the application
Create the new tablespaces and datafiles --> this should propagate to the
standby
Get table and index DDL using dbms_metadata.get_ddl
Export tables using datapump
Drop tables and indexes --> this should propagate to the standby
Edit DDL to recreate tables and indexes in new tablespaces
Run create scripts --> this should propagate to the standby
Import tables using datapump --> this should propagate to the standby

All tables will remain in the same schema.

Comments appreciated.




This email was received from the INTERNET and scanned by the Government
Secure Intranet anti-virus service supplied by Cable&Wireless in
partnership with MessageLabs. (CCTM Certificate Number 2009/09/0052.) In
case of problems, please call your organisation’s IT Helpdesk.
Communications via the GSi may be automatically logged, monitored and/or
recorded for legal purposes.

For the latest data on the economy and society consult National Statistics at 
http://www.statistics.gov.uk

*********************************************************************************


Please Note:  Incoming and outgoing email messages are routinely monitored for 
compliance with our policy on the use of electronic communications
*********************************************************************************


Legal Disclaimer  :  Any views expressed by the sender of this message are not 
necessarily those of the Office for National Statistics
*********************************************************************************


The original of this email was scanned for viruses by the Government Secure 
Intranet virus scanning service supplied by Cable&Wireless in partnership with 
MessageLabs. (CCTM Certificate Number 2009/09/0052.) On leaving the GSi this 
email was certified virus free.
Communications via the GSi may be automatically logged, monitored and/or 
recorded for legal purposes.
��i��0���zX���+��n��{�+i�^

Other related posts: