Shulou(Shulou.com)06/03 Report--

Today, I encountered an error while backing up the customer's 11g database.

The backup script is as follows:

Run

{

Allocate channel C1 device type disk format'D:\ backup\ ora_primary.bak'

Backup incremental level 0 database

Backup current controlfile for standby format'D:\ backup\ ctl_stby.ctl'

Sql 'alter system archive log current'

Backup archivelog from time 'SYSDATE-1/24' format'D:\ backup\ ora_archive'

}

The error is the second sentence backup incremental level 0 database; error message is as follows

Replace the recovery directory with the target database control file

Assigned channel: C1

Channel C1: SID=33 device type = DISK

Launch backup in 08-April-15

Channel C1: starting incremental level 0 data file backup set

Channel C1: specifying data files in the backup set

Enter the data file: file number = 00001 name = D:\ APP\ ADMINISTRATOR\ ORADATA\ SJBZFW\ SYSTEM01.DBF

Enter the data file: file number = 00002 name = D:\ APP\ ADMINISTRATOR\ ORADATA\ SJBZFW\ SYSAUX01.DBF

Enter the data file: file number = 00003 name = D:\ APP\ ADMINISTRATOR\ ORADATA\ SJBZFW\ UNDOTBS01.DBF

Enter the data file: file number = 00004 name = D:\ APP\ ADMINISTRATOR\ ORADATA\ SJBZFW\ USERS01.DBF

Channel C1: starting segment 1 from 08 to April 15

Channel C1: completed segment 1 from 08 to April 15

Segment handle = D:\ BACKUP\ ORA_PRIMARY.BAK tag = TAG20150408T214419 comment = NONE

Channel C1: backup set completed, elapsed time: 00:01:15

Channel C1: starting incremental level 0 data file backup set

Channel C1: specifying data files in the backup set

The backup set includes the current control files

The backup set includes the current SPFILE

Channel C1: starting segment 1 from 08 to April 15

Released channel: C1

RMAN-00571:===

RMAN-00569: = ERROR MESSAGESTACK FOLLOWS =

RMAN-00571:===

RMAN-03009: the backup command (on C1 channel, on 04Universe 08Unix 201521) failed.

ORA-19504: unable to create the file "D:\ BACKUP\ ORA_PRIMARY.BAK"

ORA-27038: the file you created already exists

OSD-04010: options specified, but the file already exists

In the information, you can see that the data file has actually been backed up, but I don't know why, I am also backing up other things, because I have only one file name, and the file already exists, so I reported an error.

Modify it to the following script

Run

{

Allocate channel C1 device type disk format'D:\ backup\ ora_primary_df_%d_%

Ugg% paired% c.bak'

Backup incremental level 0 database

Backup current controlfile for standby format'D:\ backup\ ctl_stby.ctl'

Sql 'alter system archive log current'

Backup archivelog from time 'SYSDATE-1/24' format'D:\ backup\ ora_archive'

}

Backup was successful.

Channel C1: starting segment 1 from 08 to April 15

Channel C1: completed segment 1 from 08 to April 15

Segment handle = D:\ BACKUP\ ORA_PRIMARY_ DF_SJBZFW_03Q3T8L3_1_1_1_1.BAK tag = TAG20150408T21

4819 comment = NONE

Channel C1: backup set completed, elapsed time: 00:01:25

Channel C1: starting incremental level 0 data file backup set

Channel C1: specifying data files in the backup set

The backup set includes the current control files

The backup set includes the current SPFILE

Channel C1: starting segment 1 from 08 to April 15

Channel C1: completed segment 1 from 08 to April 15

Segment handle = D:\ BACKUP\ ORA_PRIMARY_ DF_SJBZFW_04Q3T8NO_1_1_1_1.BAK tag = TAG20150408T21

4819 comment = NONE

Channel C1: backup set completed, elapsed time: 00:00:01

Completion of backup in 08-April-15

If we look at the specific information, we can see that after a successful backup, RMAN will back up the control file and SPFILE file again, so if the file name does not have a variable identifier, it will report an error that already exists in the file.

When I was querying the data, I found another situation, the principle is actually the same, it is caused by the creation of multiple files.

File size limit

RMAN > show all

Many configuration parameters are listed as follows:

CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS

CONFIGURE BACKUP OPTIMIZATION OFF; # default

CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default

CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO'% favored; # default

CONFIGURE DEVICE TYPE DISK PARALLELISM 1; # 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 MAXPIECESIZE 100 M

CONFIGURE MAXSETSIZE TO UNLIMITED; # default

CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'DRAACLEORA92DATABASESNCFOSS.ORAN; # default

Pay attention to the size limit, because if there is a size limit, it needs to create 2, 3. A backup file, but the name is and

The first one is the same, but at this time the file name can not be unique, there must be an error. If there is no size limit, there should be no problem, if there is a limit, we should pay attention to the uniqueness of the name.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.