Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Import and export question

RE: Import and export question

From: Carel-Jan Engel <cjpengel.dbalert_at_xs4all.nl>
Date: Wed, 21 Apr 2004 08:24:44 +0200 (CEST)
Message-ID: <13302.145.61.28.21.1082528684.squirrel@webmail.xs4all.nl>

> Is there any chance you could set up replication instead? I would be
> concerned with using imports and exports because there are a lot more
> "moving parts" than with a replication-based solution. Your client, for
> example, would need to ensure that they were using the 8.1.7 version of
> the export utility to generate the file. They would have to script some
> sort of file transfer process. You would have to script a file transfer
> process. There would probably be ".lock" files involved so that you
> weren't grabbing a file that they were delivering. You would then have
> to script an import process. There are a lot of potential points for
> problems to occur in this scenario. As one or both of you upgrade your
> systems, there is the potential to break things.

Yes, I support Justin's suggestion that replication might be a better solution. To prevent you from too many dependencies, you could consider to put a database in the middle, where both parties replicate to. I've set up this on an airport between two 24x7 systems. Forwarding to the destination can be done independent of the sending end. This will give you some sort of an asynchronous mechanism, that survives the downtime of the counterpartner. Another advantage is that upgrading/changing one of the systems can be dealt with on the interface database, again preventing the systems unfluencing each other too much.

>
> If you are replicating the data, however, Oracle will take care of most
> of this.
>
> If you were both on 9i, I would suggest transportable tablespaces as a
> possible solution as well.

This will only last as long as you both _stay_ on 9i. As soon as one wants to upgrade, you're in trouble again. It will get even more troublesome when you need to exchange information with other clients as well. All parties need to upgrade at once. This will cause too many dependencies. I wouldn't go for transportable tablespaces.

Regards, Carel-Jan

===
If you think education is expensive, try ignorance. (Derek Bok) ===

>
> Justin Cave
> Distributed Database Consulting, Inc.
> http://www.ddbcinc.com/askDDBC
>
> -----Original Message-----
> From: oracle-l-bounce_at_freelists.org
> [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Alec Macdonell
> Sent: Tuesday, April 20, 2004 3:30 PM
> To: oracle-l_at_freelists.org
> Subject: Import and export question
>
> We have a client that uses Oracle 9i. We are on 8.1.7. We need to
> exchange eligibility information and transaction information between our
> two companies. They are suggesting creating a user and a tablespace on
> each of our platforms. We would then use imports and exports to move the
> data between the two databases.
>
> This seems like a fine solution but I would like input from anyone who
> may have experience with a process like this. Are there any land mines
> that I am not seeing?
>
> Alec Macdonell
> UsScript, Inc.
> (559) 244-3736



Please see the official ORACLE-L FAQ: http://www.orafaq.com

To unsubscribe send email to: oracle-l-request_at_freelists.org put 'unsubscribe' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Received on Wed Apr 21 2004 - 01:21:58 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US