RE: More Rman q's
Jack,
The auxiliary database is the clone of the target database (Oracle really should
have called this parameter SOURCE instead of TARGET). It (the auxiliary) is the one
you are creating.
The auxiliary database should be started nomount. The only files needed for the
auxiliary are the init.ora and password file.
Jay
>>> [EMAIL PROTECTED] 01/25/02 05:10AM >>>
Hi,
Am I misreading all this, but should the auxiliary database be in existence
before I can Clone to it?
I created the init.ora and all directories and started TEST3 in nomount. I
created the password file and can connect to it with a connect string no
problem.
Another point is. Did you mean that the auxilliary database is the database
that needs to be cloned (source)?
Jack
"Jay Hostetter" <[EMAIL PROTECTED]> on 23-01-2002 15:41:35
To: <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>
cc:
John and Jack,
I guess I didn't read Jack's info closely enough, since he states that
his auxiliary database is already started nomount. I wonder if the three
separate connect statements are the issue? When I duplicate a database, I
use the following commands from the OS:
>rman target internal/xxx@original catalog rman/xxx@rman1 auxiliary /
rman>@prod_to_test
rman>exit
My ORACLE_HOME and SID are set for the auxiliary database. I have started
the auxiliary database NOMOUNT, which basically just starts the background
processes.Password files are required for the remote login (this is on
a different server). I don't use db_file_name_convert or
log_file_name_convert, because I group the data files differently on this
server (I don't have the exact same number of file systems as production).
After I have RMAN started, I do the following:
run {
#set until time "to_date('0108200220','mmddhh24miss')";
set until scn 316498395;
#set until logseq 1389 thread 1;
allocate auxiliary channel ch1 type disk;
set newname for datafile 1 to '/u03/oradata/BSCST/system01.dbf';
set newname for datafile 2 to '/u03/oradata/BSCST/rbs01.dbf';
...
...yadda yadda yadda...
...
set newname for datafile 49 to '/u04/oradata/BSCST/bill_image_data06.dbf';
set newname for datafile 50 to '/u04/oradata/BSCST/process_data03.dbf';
duplicate target database to BSCST
logfile
group 1 ('/u03/oradata/BSCST/redo1a.log','/u04/oradata/BSCST/redo1b.log')
size 2m,
group 2 ('/u03/oradata/BSCST/redo2a.log','/u04/oradata/BSCST/redo2b.log')
size 2m,
group 3 ('/u03/oradata/BSCST/redo3a.log','/u04/oradata/BSCST/redo3b.log')
size 2m;
}
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Jay Hostetter
INET: [EMAIL PROTECTED]
Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051
San Diego, California-- Public Internet access / Mailing Lists
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
RE: More Rman q's /SOLVED dunno how
Hi ,
I must have made a really big mess of the catalog or something.
I reinstalled the catalog, recreated TEST2 and ran the clone script again.
Guess what.?
Thx J&J
Jack
[EMAIL PROTECTED]@fatcity.com on 25-01-2002 11:10:19
Please respond to [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
cc:(bcc: Jack van Zanen/nlzanen1/External/MEY/NL)
Hi,
Am I misreading all this, but should the auxiliary database be in existence
before I can Clone to it?
I created the init.ora and all directories and started TEST3 in nomount. I
created the password file and can connect to it with a connect string no
problem.
Another point is. Did you mean that the auxilliary database is the database
that needs to be cloned (source)?
Jack
"Jay Hostetter" <[EMAIL PROTECTED]> on 23-01-2002 15:41:35
To: <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>
cc:
John and Jack,
I guess I didn't read Jack's info closely enough, since he states that
his auxiliary database is already started nomount. I wonder if the three
separate connect statements are the issue? When I duplicate a database, I
use the following commands from the OS:
>rman target internal/xxx@original catalog rman/xxx@rman1 auxiliary /
rman>@prod_to_test
rman>exit
My ORACLE_HOME and SID are set for the auxiliary database. I have started
the auxiliary database NOMOUNT, which basically just starts the background
processes.Password files are required for the remote login (this is on
a different server). I don't use db_file_name_convert or
log_file_name_convert, because I group the data files differently on this
server (I don't have the exact same number of file systems as production).
After I have RMAN started, I do the following:
run {
#set until time "to_date('0108200220','mmddhh24miss')";
set until scn 316498395;
#set until logseq 1389 thread 1;
allocate auxiliary channel ch1 type disk;
set newname for datafile 1 to '/u03/oradata/BSCST/system01.dbf';
set newname for datafile 2 to '/u03/oradata/BSCST/rbs01.dbf';
...
...yadda yadda yadda...
...
set newname for datafile 49 to '/u04/oradata/BSCST/bill_image_data06.dbf';
set newname for datafile 50 to '/u04/oradata/BSCST/process_data03.dbf';
duplicate target database to BSCST
logfile
group 1 ('/u03/oradata/BSCST/redo1a.log','/u04/oradata/BSCST/redo1b.log')
size 2m,
group 2 ('/u03/oradata/BSCST/redo2a.log','/u04/oradata/BSCST/redo2b.log')
size 2m,
group 3 ('/u03/oradata/BSCST/redo3a.log','/u04/oradata/BSCST/redo3b.log')
size 2m;
}
Jay Hostetter
Oracle DBA
D. & E. Communications
Ephrata, PA USA
>>> [EMAIL PROTECTED] 01/23/02 03:20AM >>>
Jay,Jack
I don't understand here how RMAN connects to auxilliary when Jack seems to
be saying that the database does not exist it all.
When I tested a duplicate database session I made the following notes which
indicated I need a remote_login_password file setting up. I assume you
didn't do this then Jack as the database was not created at this point in
time
Please correct me if I have misunderstood
John
My notes follow
+++
To allow this connection a remote_login_password file needs to be in place.
This can be created running the orapwd command
$ORACLE_HOME/bin/orapwd file$ORACLE_HOME/dbs/ orapwSID password = xx
entries=10
Then add the line remote_login_passwordfile=exclusive to the init.ora and
start the database in exclusive mode (using the initSID_excl.ora file in
the
pfile directory).
Ensure that this works by performing a sqlplus internal @tnsnames_alias
with
the correct password and ensuring that a connection has been made.
This needs to be set up on the target environment as well as on the
auxillary server. Ensure that a connection can be made both locally and
remotely
sqlplus internal/password@tnsnames_alias
===
De informatie verzonden in dit e-mailbericht is vertrouwelijk en is
uitsluitend bestemd voor de geadresseerde. Openbaarmaking,
vermenigvuldiging, verspreiding en/of verstrekking van deze informatie aan
derden is, behoudens voorafgaande schriftelijke toestemming van Ernst &
Young, niet toegestaan. Ernst & Young staat niet in voor de juiste en
volledige overbrenging van de inhoud van een verzonden e-mailbericht, noch
voor tijdige ontvangst daarvan. Ernst & Young kan niet garanderen dat een
verzonden e-mailbericht vrij is van virussen, noch dat e-mailberichten
worden overgebracht zonder inbreuk of tussenkomst van onbevoegde derden.
Indien bovenstaand e-mailbericht niet aan u is gericht, verzoeken wij u
vriendelijk doch dringend het e-mailbericht te retourneren aan de verzender
en het origineel en eventuele kopieën te verwijderen en te vernietigen.
Ernst & Young hanteert bij de uitoefening van haar werkzaamheden algemene
voorwaarden, waarin een beperking van aansprakelijkheid is opgenomen. De
algemene voorwaarden worden u op verzoek kosteloos toegezonden.
=
RE: More Rman q's
Title: RE: More Rman q's
Jack,
TEST3 instance should be exactly as you stated, an Oracle instance with no datafiles as yet.
What I think I was meaning regarding the names of the objects is that the format is
Rman catalogue = catalogue
Source database = target
new database = auxilliary.
To my mind that is wrong and the new database should be target. It is of no importance but I do think it can be confusing.
What is even odder is requirement to connect to the target database in the first place. A live database has been copied to disk/tape. We want to make a new copy on a development server. But we still have to connect to the original live database. I once had a reason from Oracle for this in a tar dialogue however it did not sound very convincing to me at the time.
John
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 25 January 2002 10:10
To: Multiple recipients of list ORACLE-L
Subject: RE: More Rman q's
Hi,
Am I misreading all this, but should the auxiliary database be in existence
before I can Clone to it?
I created the init.ora and all directories and started TEST3 in nomount. I
created the password file and can connect to it with a connect string no
problem.
Another point is. Did you mean that the auxilliary database is the database
that needs to be cloned (source)?
Jack
"Jay Hostetter" <[EMAIL PROTECTED]> on 23-01-2002 15:41:35
To: <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>
cc:
John and Jack,
I guess I didn't read Jack's info closely enough, since he states that
his auxiliary database is already started nomount. I wonder if the three
separate connect statements are the issue? When I duplicate a database, I
use the following commands from the OS:
>rman target internal/xxx@original catalog rman/xxx@rman1 auxiliary /
rman>@prod_to_test
rman>exit
My ORACLE_HOME and SID are set for the auxiliary database. I have started
the auxiliary database NOMOUNT, which basically just starts the background
processes. Password files are required for the remote login (this is on
a different server). I don't use db_file_name_convert or
log_file_name_convert, because I group the data files differently on this
server (I don't have the exact same number of file systems as production).
After I have RMAN started, I do the following:
run {
#set until time "to_date('0108200220','mmddhh24miss')";
set until scn 316498395;
#set until logseq 1389 thread 1;
allocate auxiliary channel ch1 type disk;
set newname for datafile 1 to '/u03/oradata/BSCST/system01.dbf';
set newname for datafile 2 to '/u03/oradata/BSCST/rbs01.dbf';
...
...yadda yadda yadda...
...
set newname for datafile 49 to '/u04/oradata/BSCST/bill_image_data06.dbf';
set newname for datafile 50 to '/u04/oradata/BSCST/process_data03.dbf';
duplicate target database to BSCST
logfile
group 1 ('/u03/oradata/BSCST/redo1a.log','/u04/oradata/BSCST/redo1b.log')
size 2m,
group 2 ('/u03/oradata/BSCST/redo2a.log','/u04/oradata/BSCST/redo2b.log')
size 2m,
group 3 ('/u03/oradata/BSCST/redo3a.log','/u04/oradata/BSCST/redo3b.log')
size 2m;
}
Jay Hostetter
Oracle DBA
D. & E. Communications
Ephrata, PA USA
>>> [EMAIL PROTECTED] 01/23/02 03:20AM >>>
Jay,Jack
I don't understand here how RMAN connects to auxilliary when Jack seems to
be saying that the database does not exist it all.
When I tested a duplicate database session I made the following notes which
indicated I need a remote_login_password file setting up. I assume you
didn't do this then Jack as the database was not created at this point in
time
Please correct me if I have misunderstood
John
My notes follow
+++
To allow this connection a remote_login_password file needs to be in place.
This can be created running the orapwd command
$ORACLE_HOME/bin/orapwd file$ORACLE_HOME/dbs/ orapwSID password = xx
entries=10
Then add the line remote_login_passwordfile=exclusive to the init.ora and
start the database in exclusive mode (using the initSID_excl.ora file in
the
pfile directory).
Ensure that this works by performing a sqlplus internal @tnsnames_alias
with
the correct password and ensuring that a connection has been made.
This needs to be set up on the target environment as well as on the
auxillary server. Ensure that a connection can be made both locally and
remotely
sqlplus internal/password@tnsnames_alias
===
De informatie verzonden in dit e-mailbericht is vertrouwelijk en is
uitsluitend bestemd voor de geadresseerde. Openbaarmaking,
vermenigvuldiging, verspreiding en/of verstrekking van deze informatie aan
derden is, behoudens voorafgaande schriftelijke toestemming van Ern
RE: More Rman q's
Hi,
Am I misreading all this, but should the auxiliary database be in existence
before I can Clone to it?
I created the init.ora and all directories and started TEST3 in nomount. I
created the password file and can connect to it with a connect string no
problem.
Another point is. Did you mean that the auxilliary database is the database
that needs to be cloned (source)?
Jack
"Jay Hostetter" <[EMAIL PROTECTED]> on 23-01-2002 15:41:35
To: <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>
cc:
John and Jack,
I guess I didn't read Jack's info closely enough, since he states that
his auxiliary database is already started nomount. I wonder if the three
separate connect statements are the issue? When I duplicate a database, I
use the following commands from the OS:
>rman target internal/xxx@original catalog rman/xxx@rman1 auxiliary /
rman>@prod_to_test
rman>exit
My ORACLE_HOME and SID are set for the auxiliary database. I have started
the auxiliary database NOMOUNT, which basically just starts the background
processes.Password files are required for the remote login (this is on
a different server). I don't use db_file_name_convert or
log_file_name_convert, because I group the data files differently on this
server (I don't have the exact same number of file systems as production).
After I have RMAN started, I do the following:
run {
#set until time "to_date('0108200220','mmddhh24miss')";
set until scn 316498395;
#set until logseq 1389 thread 1;
allocate auxiliary channel ch1 type disk;
set newname for datafile 1 to '/u03/oradata/BSCST/system01.dbf';
set newname for datafile 2 to '/u03/oradata/BSCST/rbs01.dbf';
...
...yadda yadda yadda...
...
set newname for datafile 49 to '/u04/oradata/BSCST/bill_image_data06.dbf';
set newname for datafile 50 to '/u04/oradata/BSCST/process_data03.dbf';
duplicate target database to BSCST
logfile
group 1 ('/u03/oradata/BSCST/redo1a.log','/u04/oradata/BSCST/redo1b.log')
size 2m,
group 2 ('/u03/oradata/BSCST/redo2a.log','/u04/oradata/BSCST/redo2b.log')
size 2m,
group 3 ('/u03/oradata/BSCST/redo3a.log','/u04/oradata/BSCST/redo3b.log')
size 2m;
}
Jay Hostetter
Oracle DBA
D. & E. Communications
Ephrata, PA USA
>>> [EMAIL PROTECTED] 01/23/02 03:20AM >>>
Jay,Jack
I don't understand here how RMAN connects to auxilliary when Jack seems to
be saying that the database does not exist it all.
When I tested a duplicate database session I made the following notes which
indicated I need a remote_login_password file setting up. I assume you
didn't do this then Jack as the database was not created at this point in
time
Please correct me if I have misunderstood
John
My notes follow
+++
To allow this connection a remote_login_password file needs to be in place.
This can be created running the orapwd command
$ORACLE_HOME/bin/orapwd file$ORACLE_HOME/dbs/ orapwSID password = xx
entries=10
Then add the line remote_login_passwordfile=exclusive to the init.ora and
start the database in exclusive mode (using the initSID_excl.ora file in
the
pfile directory).
Ensure that this works by performing a sqlplus internal @tnsnames_alias
with
the correct password and ensuring that a connection has been made.
This needs to be set up on the target environment as well as on the
auxillary server. Ensure that a connection can be made both locally and
remotely
sqlplus internal/password@tnsnames_alias
===
De informatie verzonden in dit e-mailbericht is vertrouwelijk en is
uitsluitend bestemd voor de geadresseerde. Openbaarmaking,
vermenigvuldiging, verspreiding en/of verstrekking van deze informatie aan
derden is, behoudens voorafgaande schriftelijke toestemming van Ernst &
Young, niet toegestaan. Ernst & Young staat niet in voor de juiste en
volledige overbrenging van de inhoud van een verzonden e-mailbericht, noch
voor tijdige ontvangst daarvan. Ernst & Young kan niet garanderen dat een
verzonden e-mailbericht vrij is van virussen, noch dat e-mailberichten
worden overgebracht zonder inbreuk of tussenkomst van onbevoegde derden.
Indien bovenstaand e-mailbericht niet aan u is gericht, verzoeken wij u
vriendelijk doch dringend het e-mailbericht te retourneren aan de verzender
en het origineel en eventuele kopieën te verwijderen en te vernietigen.
Ernst & Young hanteert bij de uitoefening van haar werkzaamheden algemene
voorwaarden, waarin een beperking van aansprakelijkheid is opgenomen. De
algemene voorwaarden worden u op verzoek kosteloos toegezonden.
=
The information contained in this communication is confidential and is
intended solely for the use of the individual or entity to whom it is
addressed. You should not copy, disclose or distribute this communication
without the authority of Ernst & Young. Ernst & Young is neither liable for
the proper and complete transmission of the information contained in
Re: More Rman q's
You need to have the auxiliary database started nomount. All you need is the init.ora
to do this. The duplicate will create the control, data, and redo log files.
Jay Hostetter
Oracle DBA
D. & E. Communications
Ephrata, PA USA
>>> [EMAIL PROTECTED] 01/22/02 09:20AM >>>
Hi All,
Trying my first attempt to clone a database using rman and ending up with
errors.
Situation:
TEST1 database = catalog Status=OPEN
TEST2 database= target database and to be cloned status= OPEN
TEST3 database= future clone of TEST2 status = NOMOUNT (as per docs)
I have all sorts of backups (full, incremental level0,1&2 and datafile copy
and controlfile copy) on disk.
I run the following script
*SCRIPT*
rman <
RMAN-06005: connected to target database: TEST2 (DBID=535250382)
RMAN>
RMAN-06008: connected to recovery catalog database
RMAN>
RMAN-06020: connected to auxiliary database
RMAN> 2> 3> 4> 5>
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: d1
RMAN-08500: channel d1: sid=11 devtype=DISK
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: d2
RMAN-08500: channel d2: sid=9 devtype=DISK
RMAN-03022: compiling command: Duplicate Db
RMAN-03027: printing stored script: Memory Script
{
set until scn 281474976710655;
set newname for datafile 1 to
"/data/oracle8/TEST3/systemTEST3.dbf";
set newname for datafile 2 to
"/data/oracle8/TEST3/rbsTEST3.ora";
set newname for datafile 3 to
"/data/oracle8/TEST3/tempTEST3.ora";
set newname for datafile 4 to
"/data/oracle8/TEST3/dataTEST3.ora";
restore
check readonly
clone database
;
}
RMAN-03021: executing script: Memory Script
RMAN-03022: compiling command: set
RMAN-03022: compiling command: set
RMAN-03022: compiling command: set
RMAN-03022: compiling command: set
RMAN-03022: compiling command: set
RMAN-03022: compiling command: restore
RMAN-03022: compiling command: IRESTORE
RMAN-03023: executing command: IRESTORE
RMAN-08019: channel d1: restoring datafile 1
RMAN-08507: input datafilecopy recid=34 stamp=451836451
filename=/data/oracle8/BACKUP/systemTEST2.dbf
RMAN-08509: destination for restore of datafile 1:
/data/oracle8/TEST3/systemTEST3.dbf
RMAN-03026: error recovery releasing channel resources
RMAN-08031: released channel: d1
RMAN-08031: released channel: d2
RMAN-00571: ===
RMAN-00569: === ERROR MESSAGE STACK FOLLOWS ===
RMAN-00571: ===
RMAN-03002: failure during compilation of command
RMAN-03013: command type: Duplicate Db
RMAN-03015: error occurred in stored script Memory Script
RMAN-03002: failure during compilation of command
RMAN-03013: command type: restore
RMAN-03006: non-retryable error occurred during execution of command:
IRESTORE
RMAN-07004: unhandled exception during command execution on channel d1
RMAN-10035: exception raised in RPC: ORA-01507: database not mounted
RMAN-10031: ORA-1507 occurred during call to
DBMS_BACKUP_RESTORE.COPYDATAFILECOPY
/OUTPUT***
I don't understand why I should be getting the message about not mounted,
since I can't even mount an non-existing database. and the documentation
states that database should be in nomount phase.
Can anybody explain???
TIA
Jack
===
De informatie verzonden met dit E-mail bericht is uitsluitend bestemd voor
de geadresseerde. Gebruik van deze informatie door anderen dan de
geadresseerde is verboden. Openbaarmaking, vermenigvuldiging, verspreiding
en/of verstrekking van deze informatie aan derden is niet toegestaan.
Ernst & Young staat niet in voor de juiste en volledige overbrenging van de
inhoud van een verzonden E-mail, noch voor tijdige ontvangst daarvan.
===
The information contained in this communication is confidential and may be
legally privileged. It is intended solely for the use of the individual or
entity to whom it is addressed and others authorised to receive it. If you
are not the intended recipient you are hereby notified that any disclosure,
copying, distribution or taking any action in reliance on the contents of
this information is strictly prohibited and may be unlawful. Ernst &
Young is neither liable for the proper and complete transmission of the
information contained in this communication nor for any delay in its
receipt.
===
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author:
INET: [EMAIL PROTECTED]
Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051
San Diego, California-- Public Internet access / Mailing Lists
