今天在做rman backup练习的时候,遇到了问题哦.
RMAN> run {
2> allocate channel dev1 type disk;
3> backup
4> format '/tmp/rmanbak/bak'
5> database;
6> release channel dev1;
7> }
因为对rman确实不熟,照着做,结果错误就出来了:
ORA-19504: 无法创建文件"C:\TMP\RMANBAK\BAK"
ORA-27038: 所创建的文件已存在
OSD-04010: 指定了<create>选项,但文件已经存在
google了很多, 总感觉没有能既知其然,又知其所以然的方案.
弄了好久终于解决, 分享如下:
确保几个因素:
1. 文件大小限制
RMAN> show all
列出了许多配置参数如下:
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 '%F'; # 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 'D:\ORACLE\ORA92\DATABASE\SNCFOSS.ORA'; # default
注意大小限制, 因为如果大小有限制, 其需要再创建第2,3...个备份文件,但名字却是和
第1个一样,而这个时候文件名不能唯一,肯定出错了。如果大小没有限制,应该不会有问题, 有限制则要注意名称唯一性问题了.
2. 名称唯一性, 如果名称不唯一, 要写多个文件的时候当然过不去.
下面的是metalink上的Doc ID: 1082911.6的描述:
Solution Description:
=====================
Insert a %U into the format portion of the backup script in order to ensure a unique backup file name.
Problem Explanation:
====================
These errors occur because a backup file name already exists by the name specified in you backup script. For instance, if you are using the line “allocate channel c1 type disk format
‘/oracle/database/rman/backup/df_%d_%p_%c’;”, df_%d_%p_%c formats the backupstring like so;
df_ is simply a name. This could be any set of characters. In this case it means
database full.
%d_ is the database sid.
%p_is the backup piece number within the backup set.
%c_ specifies the copy number of the backup piece within a set of duplexed backup pieces.
There needs to be a %U added to the format string.
%U_ specifies a convenient shorthand that guarantees uniqueness in generated backup filenames. So, if the string were “db_%d_%U_%p_%c a unique name would be generated and it would not be necessary to either rename or move the backup file name prior to the next backup.
If the format is changed to include the %U, for instance;
allocate channel c1 type disk format ‘/oracle/database/rman/backup/df_%d_%U_%p_%c’;
The backup file will automatically have a unique name generated like;
df_JTG_0eblfm65_1_1_1_1
The next one would look like;
df_JTG_0fblfm76_1_1_1_1
所以只要保证格式中有能唯一区别的格式符即可,像%U, %t,%p 当然组合使用更好.
3. 访问权限限制, 确保对写的文件夹,有写的权限.
分享到:
相关推荐
今天有朋友问到如下一则案例,ORA-01114,ORA-27067以及OSD-04026错误同时出现: *** ACTION NAME:() 2009-04-01 09:31:00.762*** MODULE NAME:(JDBC Thin Client) 2009-04-01 09:31:00.762*** SERVICE NAME:(SYS$...
ORA-27504: IPC error creating OSD context ORA-27300: OS system dependent operation:sskgxp_select failed with status: 3 ORA-27301: OS failure message: No such process ORA-27302: failure occurred at:...
- `OSD-04002`: 文件不存在或访问权限不足。 - `O/S-Error(OS2)`: 操作系统级别的错误。 - **解决方法**: - 需要确保指定的备份文件路径正确无误。 - 如果文件确实不存在,则需要检查备份是否完整。 - 确保有...
错误信息“OSD-160222236: Message 160222236 not found; product=RDBMS; facility=SOSDO/S-Error: (OS 1502) ??????????????????”表明系统日志已满,无法再接收新的日志条目。解决这个问题,你需要清理Windows事件...
OSD-04002: unable to open file O/S-Error: (OS2) 文件不存在 ``` 2. **确定受影响的数据文件**:根据错误信息,可以明确哪些数据文件被误删除。在本案例中,受影响的数据文件为 scsstz01.dbf, scsstz02.dbf 和...
需要注意的是,如果不正确地设置这些参数,可能会导致数据库启动失败或出现内存不足的错误,如 ORA-27102 out of memory 和 OSD-00034 Message 34 not found 等错误信息。 #### 四、总结 通过以上步骤,可以在 32 ...
- **OSD**(Operating System-Dependent):操作系统资源访问进程。 - **LMS** (Global Cache Service Process):全局缓存服务进程。 - **LMD** (Global Enqueue Service Daemon):全局查询服务守护进程。 - **...
3. **$ORA_CRS_HOME/crs/css目录权限发生改变**(未发生) 4. **/oracle文件系统满**(未满) 5. **/tmp目录下的.oracle目录被删除**(未删除) 6. **节点间认证信息网络包发生问题**(无证据) 尽管如此,尚无直接...
《Oracle Database Installation and Administration Guide 11g Release 2 (11.2) for Fujitsu BS2000/OSD》是Oracle公司为Fujitsu BS2000/OSD操作系统平台提供的数据库安装与管理指南,适用于版本11.2。该文档主要...