RMAN backup of a small fault

The following error occurs when RMAN is used for full-Database Backup:

RMAN> backup database format = 'd:/orabak/20081008_fullbk.bak 'tag = 'seagal'; Start backup from March 10 to 08 using the channel ora_disk_1 ora_disk_1: start all data file backup set channels ora_disk_1: the data file in the backup set is being specified. The input data file fno = 00001 name = C: /Oracle/product/10.2.0/oradata/keymen/system01.dbf input data file fno = 00003 name = C: /Oracle/product/10.2.0/oradata/keymen/sysaux01.dbf input data file fno = 00005 name = C: /Oracle/product/10.2.0/oradata/keymen/example01.dbf input data file fno = 00002 name = C: /Oracle/product/10.2.0/oradata/keymen/undotbs01.dbf input data file fno = 00006 name = C: /Oracle/product/10.2.0/oradata/keymen/zhangsan_data.dat input data file fno = 00007 name = C: /Oracle/product/10.2.0/oradata/keymen/bigtbs_f1.dat input data file fno = 00004 name = C:/Oracle/product/10.2.0/oradata/keymen/users01.dbf channel ora_disk_1: starting segment 1 in March 10-08 ora_disk_1: Completed segment 1 in April 10-08 handle = D:/orabak/20081008_fullbk.bak mark = Seagal comment = none channel ora_disk_1: the backup set has been completed. After the time: 00: 01: 26 channel ora_disk_1: Start all data file backup set channels ora_disk_1: the data file backup set in the specified backup set is included in the current control file. The backup set contains the current spfile channel ora_disk_1: Starting segment 1 from April 10 to April 10.

A ORA-19504 error occurred: The file could not be created. Analysis: the backup statement used just now is:

RMAN> backup database format = 'd:/orabak/20081008_fullbk.bak 'tag = 'agal ';

Here is the problem: D:/orabak/20081008_fullbk.bakSolution:

RMAN> backup database format ='D:/orabak/keymen_fullbk _ % S _ % P. rmn ';

OK. The backup is complete.

RMAN> backup database format = 'd:/orabak/keymen_fullbk _ % S _ % P. rmn '; Start backup on March 10, 00001-08 Use channel ora_disk_1 ora_disk_1: Start all data file backup set channels ora_disk_1: data file input data file in the specified backup set fno = Name = C: /Oracle/product/10.2.0/oradata/keymen/system01.dbf input data file fno = 00003 name = C: /Oracle/product/10.2.0/oradata/keymen/sysaux01.dbf input data file fno = 00005 name = C: /Oracle/product/10.2.0/oradata/keymen/example01.dbf input data file fno = 00002 name = C: /Oracle/product/10.2.0/oradata/keymen/undotbs01.dbf input data file fno = 00006 name = C: /Oracle/product/10.2.0/oradata/keymen/zhangsan_data.dat input data file fno = 00007 name = C: /Oracle/product/10.2.0/oradata/keymen/bigtbs_f1.dat input data file fno = 00004 name = C:/Oracle/product/10.2.0/oradata/keymen/users01.dbf channel ora_disk_1: starting Section 1 in March 10-08 ora_disk_1: Completed Section 1 in April 10-08 handle = D:/orabak/keymen_fullbk_9_1.rmn mark = tag20081008t104639 comment = none channel ora_disk_1: the backup set has been completed. After the time: 00: 01: 25 channel ora_disk_1: starts all data file backup set channels ora_disk_1: the data file backup set in the specified backup set contains the current control file in the backup set contains the current spfile channel ora_disk_1: Starting segment 1 in March 10-08 channel ora_disk_1: completed segment 1 from month 08-10-08 segment handle = D:/orabak/keymen_fullbk_10_1.rmn mark = tag20081008t104639 comment = none channel ora_disk_1: Backup set completed, after time: 00: 00: 00: 03. Backup completed in month 08-10-month 08 RMAN>

When using RMAN for backup, it is best to add some parameter restrictions when creating the name of the backup file. The list of the most common parameters (case sensitive) is as follows:

Parameter Name	Parameter description
% U	This is the default file naming format. It provides a unique file name generated by the system for RMAN-related files. When processing image copies or backup slices, this replacement with strings has different meanings. When a backup set is used, % u stands for % u _ % P _ % C, and % u _ % P _ % C ensures that the generated backup file name is unique. When an image copy is used, the meaning is different, and the type of the image copy is different. When an image copy is used for a data file, the meaning is as follows: Data-D-% d_id-% I _ts-% n_fno-% F _ % u when the image copy is used for archiving the redo log, it indicates that arch-D-% d_id-% I _s-% e_t-% h_a-% A _ % u is used to control the image copy of a file, meaning: CF-D _ % d-ID-% I-% u
% P	Number of parts in the backup set. This value is initially set to 1 for each backup set. This value increases by 1 when each backup set is created.
% S	Indicates the number of backup sets. This quantity is the counter in the control file, and the counter value is added according to each backup set. The initial counter value is 1. This quantity will be unique in the lifecycle of the control file (therefore, this quantity is reset when resetlogs is executed or reset when the control file is restored or re-created)