Jay and Tom,
Thanks a million for your replies. I have now ran the script by creating it
and
then executing it from the RMAN prompt. It worked but I got the following
error :
rman target / catalog rman_sid1/rman_sid1@rman817 auxiliary /
Recovery Manager: Release 8.1.7.2.0 - Production
RMAN-06005: connected to target database: SID1 (DBID=647056675)
RMAN-06008: connected to recovery catalog database
RMAN-06020: connected to auxiliary database
RMAN> run {execute script dup_db;}
RMAN-03021: executing script: dup_db
RMAN-03022: compiling command: set
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: dupdb_d1
RMAN-08500: channel dupdb_d1: sid=43 devtype=SBT_TAPE
RMAN-08526: channel dupdb_d1: VERITAS NetBackup for Oracle8 - Release 3.4GA
(030800)
RMAN-03022: compiling command: set limit
RMAN-03023: executing command: set limit
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: Duplicate Db
RMAN-03026: error recovery releasing channel resources
RMAN-08031: released channel: dupdb_d1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03015: error occurred in stored script dup_db
RMAN-03002: failure during compilation of command
RMAN-03013: command type: Duplicate Db
RMAN-05500: the auxiliary database must be not mounted when issuing a
DUPLICATE command
Can you tell me if there is anything wrong with my Connect String ?? If so,
how do I
specify the connect string correctly ?? The auxiliary is DEFINITELY not
mounted here since
I have started it in NOMOUNT mode. The target db is the one I am trying to
duplicate and
the auxiliary db is the duplicate db I am attempting to create. The target
db is obviously
open. I am not using a password file since I am working directly on the
server.
Regards,
Samir
Samir Sarkar
Oracle DBA
SchlumbergerSema
Email : [EMAIL PROTECTED]
[EMAIL PROTECTED]
Phone : +44 (0) 115 - 957 6028
EPABX : +44 (0) 115 - 957 6418 Ext. 76028
Fax : +44 (0) 115 - 957 6018
-----Original Message-----
Sent: 08 April 2002 14:06
To: [EMAIL PROTECTED]; SARKAR, Samir
Your input to RMAN should be a script or "here" list. Scrap the shell
script, put your "run" script into a file, run RMAN from the command line
and call the rman "run" script that you just created.. Also, set
NLS_DATE_FORMAT and NLS_LANG. Depending on your database version the
"to_date" function will not work as you have it in "set until time".
Jay
>>> [EMAIL PROTECTED] 04/08/02 09:43AM >>>
Dear All,
I am totally out of my depth here and this is a production db which needs to
be restored urgently.
I shall explain my scenario first. Our application team had lost some data
after last Wednesday night's
backup. They have a tool to have a dump of the data from the database from
which they can extract the
data if needed. This dump was taken on Thursday morning. Due to some ***hole
they lost some more data
on Thursday during the day. They recovered this data from the database dump
which they had taken on
Thursday morning.
They now want the data which was lost on Wednesday. Since there was no
database dump available prior to
this, I suggested that we can create a duplicate database upto a point of
time (as on Wednesday night) to a
different location on the server. They could then take a database dump with
their tool and extract the lost records.
This is my script which I compiled with help from Metalink and an old
post from John Hallas (the backup of our target database is taken on tape
with Veritas Netbackup) :
#!/bin/ksh
rman target / catalog rman_sid1/rman_sid1@rman817 auxiliary /
run {
set until time "to_date('20-MAR-2002 20:00:00','DD-MON-YYYY HH24:MI:SS)";
allocate channel c_dlt1 type 'SBT_TAPE';
allocate auxiliary channel dupdb_d1 type disk;
setlimit channel c_dlt1 kbytes 67108864 maxopenfiles 128 readrate 256;
setlimit channel dupdb_d1 kbytes 67108864 maxopenfiles 128 readrate 256;
set newname for datafile
'/disk01/oradata/sid1/data/system01sid1.dbf'
to '/disk01/oradata/test/data/system01sid1.dbf';
set newname for datafile
'/disk01/oradata/sid1/data/rbs01sid1.dbf'
to '/disk01/oradata/test/data/rbs01sid1.dbf';
set newname for datafile
'/disk01/oradata/sid1/data/temp01sid1.dbf'
to '/disk01/oradata/test/data/temp01sid1.dbf';
set newname for datafile
'/disk01/oradata/sid1/data/tools01sid1.dbf'
to '/disk01/oradata/test/data/tools01sid1.dbf';
set newname for datafile
'/disk01/oradata/sid1/data/users01sid1.dbf'
to '/disk01/oradata/test/data/users01sid1.dbf';
duplicate target database to test
logfile
group 1 '/disk03/oradata/test/logs/log01a01sid1.dbf' size 180M,
group 2 '/disk03/oradata/test/logs/log02a01sid1.dbf' size 180M,
group 3 '/disk03/oradata/test/logs/log03a01sid1.dbf' size 180M;
}
What happens is that RMAN connects to the target, catalog and auxiliary
database and goes into the
RMAN prompt and just hangs there........after some time, when I type 'exit'
there out of frustration, I
get the following errors :
./create_dupdb.sh[5]: run: not found
./create_dupdb.sh[9]: allocate: not found
./create_dupdb.sh[11]: allocate: not found
./create_dupdb.sh[13]: setlimit: not found
./create_dupdb.sh[14]: setlimit: not found
./create_dupdb.sh[17]: /disk01/oradata/sid1/data/system01sid1.dbf: cannot
execute
./create_dupdb.sh[18]: to: not found
./create_dupdb.sh[21]: /disk01/oradata/sid1/data/rbs01sid1.dbf: cannot
execute
./create_dupdb.sh[22]: to: not found
./create_dupdb.sh[29]: /disk01/oradata/sid1/data/temp01sid1.dbf: cannot
execute
./create_dupdb.sh[30]: to: not found
./create_dupdb.sh[33]: /disk01/oradata/sid1/data/tools01sid1.dbf: cannot
execute
./create_dupdb.sh[34]: to: not found
./create_dupdb.sh[37]: /disk01/oradata/sid1/data/users01sid1.dbf: cannot
execute
./create_dupdb.sh[38]: to: not found
./create_dupdb.sh[77]: duplicate: not found
./create_dupdb.sh[79]: logfile: not found
./create_dupdb.sh[80]: group: cannot execute
./create_dupdb.sh[81]: group: cannot execute
./create_dupdb.sh[82]: group: cannot execute
./create_dupdb.sh[83]: syntax error at line 84 : `}' unexpected
Could anybody please help me in identifying what is the problem and why does
it say 'run:not found' and the
other subsequent lines ?? This is highly urgent for me !!
Thanks and Regards,
Samir
Samir Sarkar
Oracle DBA
SchlumbergerSema
Email : [EMAIL PROTECTED]
[EMAIL PROTECTED]
Phone : +44 (0) 115 - 957 6028
EPABX : +44 (0) 115 - 957 6418 Ext. 76028
Fax : +44 (0) 115 - 957 6018
___________________________________________________________________________
This email is confidential and intended solely for the use of the
individual to whom it is addressed. Any views or opinions presented are
solely those of the author and do not necessarily represent those of
SchlumbergerSema.
If you are not the intended recipient, be advised that you have received this
email in error and that any use, dissemination, forwarding, printing, or
copying of this email is strictly prohibited.
If you have received this email in error please notify the SchlumbergerSema Helpdesk
by telephone on +44 (0) 121 627 5600.
___________________________________________________________________________
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: SARKAR, Samir
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).
