• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 998
  • Last Modified:

RMAN Backup error On Windows Vista !

Dear Experts
  HI !   I'm getting the following error when i take rman backup that say that backup file or piece already exist at the backup destination disk even though i didn't  when i started the backup !   I 'm pasting contents so that u can have a better idea !

   Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.


Recovery Manager: Release 10.2.0.3.0 - Production on Mon Apr 27 12:04:29 2009

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

connected to target database: ORA10G (DBID=4004087998)



RMAN> backup database;

Starting backup at 27-APR-09
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=F:\ORADATA\ORA10G\SYSTEM01.DBF
input datafile fno=00003 name=F:\ORADATA\ORA10G\SYSAUX01.DBF
input datafile fno=00005 name=F:\ORADATA\ORA10G\EXAMPLE01.DBF
input datafile fno=00002 name=F:\ORADATA\ORA10G\UNDOTBS01.DBF
input datafile fno=00004 name=F:\ORADATA\ORA10G\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 27-APR-09
channel ORA_DISK_1: finished piece 1 at 27-APR-09
piece handle=F:\ORACLE\ORA10GORA10G1 tag=TAG20090427T121030 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:55
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current control file in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 27-APR-09
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 04/27/2009 12:11:
30
ORA-19504: failed to create file "F:\ORACLE\ORA10GORA10G1"
ORA-27038: created file already exists
OSD-04010: <create> option specified, file already exists


RMAN> show all;

RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   'F:\oracle/%d%d%p';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'F:\ORACLE\DATABASE\SNCFORA10G.ORA'; # de
fault
RMAN>

RMAN> list backup;

using target database control file instead of recovery catalog

List of Backup Sets
===================

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
4       Full    654.25M    DISK        00:00:57     26-APR-09
        BP Key: 4   Status: AVAILABLE  Compressed: NO  Tag: TAG20090426T191157
        Piece Name: F:\ORACLE\ORA10GORA10G1
  List of Datafiles in backup set 4
  File LV Type Ckp SCN    Ckp Time  Name
  ---- -- ---- ---------- --------- ----
  1       Full 603300     26-APR-09 F:\ORADATA\ORA10G\SYSTEM01.DBF
  2       Full 603300     26-APR-09 F:\ORADATA\ORA10G\UNDOTBS01.DBF
  3       Full 603300     26-APR-09 F:\ORADATA\ORA10G\SYSAUX01.DBF
  4       Full 603300     26-APR-09 F:\ORADATA\ORA10G\USERS01.DBF
  5       Full 603300     26-APR-09 F:\ORADATA\ORA10G\EXAMPLE01.DBF

RMAN> crosscheck backup;

allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=158 devtype=DISK
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=F:\ORACLE\ORA10GORA10G1 recid=4 stamp=685221118
Crosschecked 1 objects




0
junaid_baig1
Asked:
junaid_baig1
  • 2
1 Solution
 
marperCommented:
Only Location of the backup is specified ,no output file name  .It should contain both location and file name.
As I see, you have listed only a directory name.
 
0
 
junaid_baig1Author Commented:
I 've also specified the file name !  Please check the output of backup database command  which give the error that it failed to create the  backup file alreday exist even though IT DID NOT EXIST INITAILLY WHEN I STARTED THE BACKUP ! even than i deleted that file try to take the backup again And IT GIVE THE SAME ERROR ! Please give some suggestions  that how could i overcome it !

 ORA-19504: failed to create file "F:\ORACLE\ORA10GORA10G1"
ORA-27038: created file already exists
OSD-04010: <create> option specified, file already exists

0
 
marperCommented:
Hmm...I am not sure, but as I said, I still think the file name is missing.
Look at this line again:
failed to create file "F:\ORACLE\ORA10GORA10G1" Is ORA10GORA10G1 your file name ?
It seems to me that's your directory name. If nothing try to add "\" at the and of ORA10GORA10G1
It should be something like "F:\ORACLE\ORA10GORA10G1\your_file_name.bak"
0
 
AndytwCommented:
The problem is with your RMAN configuration parameters, CHANNEL, which is defaulting the format string used to generate the filename of the resulting backupset ...
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   'F:\oracle/%d%d%p';

Since you specify format as  F:\oracle/%d%d%p', this will not be unique.  So, each time you run BACKUP DATABASE, RMAN is trying a file with the same name, hence your error.

Try:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'f:\oracle\%F';
which will generate a unique name, or check out the following for a list of substitution variables see:  

Oracle Database Backup and Recovery Reference
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta033.htm#i82206
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now