[EMAIL PROTECTED]
> 04/02/2003 12:48 PM
> Please respond to ORACLE-L
>
>
> To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
> cc:
> Subject:Re: daily clone
>
> Bill,
>
> Kind of curiosity, I don't know
;
> Joan Hsieh <[EMAIL PROTECTED]>
> Sent by: [EMAIL PROTECTED]
> 04/02/2003 12:48 PM
> Please respond to ORACLE-L
>
>
> To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
> cc:
> Subject:Re: daily clone
>
&
cle returns an error.
So it would seem a valid syntax.
Jared
Joan Hsieh <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
04/02/2003 12:48 PM
Please respond to ORACLE-L
To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
cc:
Subject:
early enough.
>
> Niall
>
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
> > [EMAIL PROTECTED]
> > Sent: 26 March 2003 19:59
> > To: Multiple recipients of list ORACLE-L
> > Subject: daily clone
> >
ECTED]
> Sent: 26 March 2003 19:59
> To: Multiple recipients of list ORACLE-L
> Subject: daily clone
>
>
>
> Hello,
>
> Env: Oracle 9.2.0.2.0 on Solaris 9 (2 machines)
>
> I'm trying to set up a daily cloning process between 2 Oracle
> instances (SIDA is source
Bill
If a tablespace is read-only, it should recover fine, nothing to write.
I don't think you can recover a tablespace from another database. I think
they will have different SCN numbers. I think only read-only tablespaces are
allowed with different SCN numbers. However, before backup, you c
Hello,
Env: Oracle 9.2.0.2.0 on Solaris 9 (2 machines)
I'm trying to set up a daily cloning process between 2 Oracle
instances (SIDA is source, SIDB is target) using the CREATE CONTROLFILE
REUSE SET DATABASE SIDB ... method. The steps are:
1) Shutdown immediate SIDB
2) Shutdown immediate SIDA,
