RE: Transportable tablespace

From: Martin Kendall <Martin.Kendall_at_Rubus.com>
Date: Thu, 18 Jan 2001 12:07:16 -0000
Message-Id: <10745.126972@fatcity.com>

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_01C08147.32BD6CF0
Content-Type: text/plain;

charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,
=20
Given the circumstances, I would opt for the Cold Bup approach. = Reason:
much simpler, safer and quicker than the DML/DDL based option that you mention.
=20
Martin

-----Original Message-----
From: DEMANCHE Luc (Cetelem) [mailto:luc.demanche_at_cetelem.fr] Sent: 18 January 2001 10:52
To: Multiple recipients of list ORACLE-L Subject: Transportable tablespace

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_01C08147.32BD6CF0
Content-Type: text/html;

charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>Transportable tablespace</TITLE>

<META content=3D"MSHTML 5.50.4522.1800" name=3DGENERATOR></HEAD>
<BODY>
<DIV>Hi,</DIV>
<DIV> </DIV>
<DIV>Given=20
the circumstances, I would opt for the Cold Bup approach.  = Reason: =20
much simpler, safer and quicker than the DML/DDL</DIV>
<DIV>based=20
option that you mention.</DIV>
<DIV> </DIV>
<DIV>Martin</DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
 <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft>-----Original Message----- From: DEMANCHE Luc = (Cetelem)=20
 [mailto:luc.demanche_at_cetelem.fr] Sent: 18 January 2001=20 10:52 To: Multiple recipients of list = ORACLE-L Subject:=20
 Transportable tablespace </DIV> Hi DBAs, Oracle 8.1.6.2 Sun solaris 2.6 
 Every month (generally on the 15th) we = have to=20
 duplicate our production DB on a production-reporting DB.  It's = not a=20
 replication case, it's a copy of one DB to another on a specific = date. =20
 We did it using "insert as select" through a database link.  We = have to=20
 synchronize all changes (add new datafiles, create new tablespace, = and so on)=20
 on the production DB to the production-reporting DB before the load. = This=20
 requires a lot of time.  And the load takes about 48 = hours.
 I would like to use transportable=20 tablespaces.  I will transfer all my tablespaces (56 = tablespaces) on my=20
 production-reporting DB.
 Does someone have a other ideas?  = Or a bad=20
 history about transportable tablespaces.  I could do a cold backup, transfer the backup to a = production-reporting=20
 disk and recreate the control file to change the DB name. What is the better solution? =


 TIA

  <P><FONT face=3DArial size=3D2>-----------------</FONT> <BR><FONT =

face=3DArial=20
size=3D2>Luc Demanche CETELEM=20
 T=E9l.: 01-46-39-14-49 =
 <FONT face=3DArial=20
Received on Thu Jan 18 2001 - 06:07:16 CST