RMAN error in date while coling new database. [message #74495] |
Mon, 20 December 2004 13:55 |
Natraj
Messages: 53 Registered: March 2003
|
Member |
|
|
Hi,
I am doing hot database clone, using RMAN,i get the following RMAN error, after almost 85% of db files have been copied.
printing stored script: Memory Script
{
set until time "20-DEC-2004 04:30:09";
recover
clone database
delete archivelog
;
}
executing script: Memory Script
executing command: SET until clause
released channel: ch1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 12/20/2004 17:27:49
RMAN-03015: error occurred in stored script Memory Script
ORA-01830: date format picture ends before converting entire input string
Recovery Manager complete.
Mon Dec 20 05:27:49 PM CST 2004 ----------------End of Script------------------
exit 1
the set until script i am runing is as below...
run {
set until time='20-DEC-2004 04:30:09';
allocate auxiliary channel ch1 type 'SBT_TAPE' parms
'ENV=(NB_ORA_CLIENT=xxxxx,NB_ORA_CLASS=Solaris_SSO_UNIX_Oracle,NB_ORA_SERV=yyyyyy)';
duplicate target database to fsuat1
logfile
group 1 ('/u03/oradata/rah/log01_1.rdo','/u22/oradata/rah/log01_2.rdo') size 100M reuse,
group 2 ('/u03/oradata/rah/log02_1.rdo','/u22/oradata/rah/log02_2.rdo') size 100M reuse,
group 3 ('/u03/oradata/rah/log03_1.rdo','/u22/oradata/rah/log03_2.rdo') size 100M reuse,
group 4 ('/u03/oradata/rah/log04_1.rdo','/u22/oradata/rah/log04_2.rdo') size 100M reuse;}
~
|
|
|
|
|
|
Re: RMAN error in date while coling new database. [message #74506 is a reply to message #74500] |
Tue, 21 December 2004 06:52 |
Natraj
Messages: 53 Registered: March 2003
|
Member |
|
|
the problem was i had archive log backups running at that time.:) ok coming to sp2-0640 error..could u pls check what i posted below... u said u dont go back and see t.. so i am pasting what i wanted to ask
Hi,
i havent reloaded the listener yet, however my server has 9.2.0.44 and 9.2.0.1, the 9.2.0.4 cold backup runs,whereas 9.2.0.1 fails. again in the env parameters, for 9.2.0 db, my tns_admin is configured to take 9.2.0.4, tnsping works correctly. do i need to look into any other parameter in the environmental settings of 9.2.0 database?why do you think the lisntener needs to be reloaded?
|
|
|