Message-Id: <10745.126968@fatcity.com> From: "DEMANCHE Luc (Cetelem)" Date: Thu, 18 Jan 2001 11:50:05 +0100 Subject: Transportable tablespace This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C0813C.8B3F6082 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi DBAs,=20 Oracle 8.1.6.2=20 Sun solaris 2.6=20 Every month (generally on the 15th) we have to duplicate our production DB on a production-reporting DB. It's not a replication case, it's a copy of one DB to another on a specific date. We did it using "insert as select" through a database link. We have to synchronize all changes (add new datafiles, create new tablespace, and so on) on the production DB to the production-reporting DB before the load. This requires a lot of time. And the load takes about 48 hours. I would like to use transportable tablespaces. I will transfer all my tablespaces (56 tablespaces) on my production-reporting DB. Does someone have a other ideas? Or a bad history about transportable tablespaces. =20 I could do a cold backup, transfer the backup to a production-reporting disk and recreate the control file to change the DB name. What is the better solution?=20 TIA=20 -----------------=20 Luc Demanche=20 CETELEM=20 T=E9l.: 01-46-39-14-49=20 Fax : 01-46-39-59-88=20 ------_=_NextPart_001_01C0813C.8B3F6082 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Transportable tablespace

Hi DBAs,

Oracle 8.1.6.2
Sun solaris 2.6

Every month (generally on the 15th) we = have to duplicate our production DB on a production-reporting DB.  = It's not a replication case, it's a copy of one DB to another on a = specific date.  We did it using "insert as select" = through a database link.  We have to synchronize all changes (add = new datafiles, create new tablespace, and so on) on the production DB = to the production-reporting DB before the load. This requires a lot of = time.  And the load takes about 48 hours.

I would like to use transportable = tablespaces.  I will transfer all my tablespaces (56 tablespaces) = on my production-reporting DB.

Does someone have a other ideas?  = Or a bad history about transportable tablespaces. 
I could do a cold backup, transfer = the backup to a production-reporting disk and recreate the control file = to change the DB name.

What is the better solution?

TIA


-----------------
Luc Demanche
CETELEM
T=E9l.: 01-46-39-14-49
Fax : 01-46-39-59-88