使用Rman恢复时出现ORA-01991
db:9.2.0.4
os:windows 2003 32bit
操作如下:
1 初始化文件都已经建好
2 password file是之前一个数据库使用过的
3 把另外一个数据库恢复到这台机器,在恢复完controlfile之后出现:
Starting restore at 10-DEC-12
channel ch0: restoring controlfile
channel ch0: restore complete
replicating controlfile
input filename=E:\ORADATA\CONTROL01.CTL
output filename=E:\ORADATA\CONTROL02.CTL
output filename=E:\ORADATA\CONTROL03.CTL
Finished restore at 10-DEC-12
released channel: ch0
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 12/10/2012 11:08:02
ORA-01991: invalid password file 'D:\oracle\ora92\DATABASE\PWDsfcdb.ORA'
使用password文件也是可以正常登陆的,不知为何会这样
但是为何别的数据库的password file 不能用呢,实例名都是一样的
Similar Messages
-
ORA-01991: invalid password file
I used producation backup file to restore in development side... but I get the following errors:
RMAN> restore controlfile from "E:\RMAN\C-922101420-20090628-01.BCK";
Starting restore at 29-JUN-09
using target database controlfile instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=14 devtype=DISK
channel ORA_DISK_1: restoring controlfile
channel ORA_DISK_1: restore complete
replicating controlfile
input filename=C:\ORACLE\ORADATA\HUBDB\CONTROL01.CTL
output filename=C:\ORACLE\ORADATA\HUBDB\CONTROL02.CTL
output filename=C:\ORACLE\ORADATA\HUBDB\CONTROL03.CTL
Finished restore at 29-JUN-09
RMAN> startup mount;
database is already started
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of startup command at 06/29/2009 15:57:11
ORA-01991: invalid password file 'C:\oracle\ora92\DATABASE\PWDhubdb.ORA'
I don't have any ideas?
AmyDear Amy!
Symptom:
When trying to open (or mount) a database the following error is generated:
ORA-01991: invalid password file '...PWDOrcl.ora'Where ‘Orcl’ is the SID of the database instance.
Cause:
Typically some corruption of the password file, or possibly the password file is for another database instance?
Possible Remedies:
If encountered when creating the database then it is because Oracle expects to create the password file but it already exists. In this instance database creation will have failed. Delete the password file and try again.
If it is suspected that the password file is corrupt then try deleting it and recreating it:
1. Delete the existing password file.
2.Create a new/replacement password file:
orapwd file=<path>\PWD<sid>.ora password=oracleUse the same path as given in the Oracle error. The password specified will be the new internal password.
Yours sincerely
Florian W. -
RMAN备份报错ORA-19501,DBV验证报错DBV-00102
存储发现有异常,厂商决定要重做raid
现在要进行数据备份,exp已备份无异常
rman备份时报错:
RMAN> backup validate datafile 53;
启动 backup 于 2012.11.05 14:41:26
分配的通道: ORA_DISK_1
通道 ORA_DISK_1: sid=524 devtype=DISK
通道 ORA_DISK_1: 启动全部数据文件备份集
通道 ORA_DISK_1: 正在指定备份集中的数据文件
输入数据文件 fno=00053 name=E:\TOEC01.DBF
RMAN-03009: backup 命令 (ORA_DISK_1 通道上, 在 11/05/2012 14:41:29 上) 失败
ORA-19501: 文件 "E:\TOEC01.DBF", 块编号 12545 读错误 (块大小 = 8192)
ORA-27070: 异步读取/写入失败
OSD-04016: 异步 I/O 请求排队时出错。
O/S-Error: (OS 1) 函数不正确。
关闭异步I/O同步
alter system set disk_asynch_io=FALSE scope=spfile;
重启实例
RMAN> backup validate datafile 53;
启动 backup 于 2012.11.05 15:24:53
使用通道 ORA_DISK_1
通道 ORA_DISK_1: 启动全部数据文件备份集
通道 ORA_DISK_1: 正在指定备份集中的数据文件
输入数据文件 fno=00053 name=E:\TOEC01.DBF
RMAN-03009: backup 命令 (ORA_DISK_1 通道上, 在 11/05/2012 15:24:57 上) 失败
ORA-19501: 文件 "E:\TOEC01.DBF", 块编号 11905 读错误 (块大小 = 8192)
ORA-27070: 异步读取/写入失败
OSD-04006: ReadFile() 失败, 无法读取文件
O/S-Error: (OS 1) 函数不正确。
E:\>dbv file=TOEC01.DBF blocksize=8192
DBVERIFY: Release 10.2.0.1.0 - Production on 星期一 11月 5 15:29:23 2012
Copyright (c) 1982, 2005, Oracle. All rights reserved.
DBVERIFY - 开始验证: FILE = TOEC01.DBF
DBV-00102: FILE (TOEC01.DBF) 在 verification read 操作 (-2) 期间出现文件 I/O 错误
os:Windows2003 x64
db:oracle10.2.0.1.0 x64
求解,怎样能使rman继续完成备份?ORA-19501: 文件 "E:\TOEC01.DBF", 块编号 11905 读错误 (块大小 = 8192)
ORA-27070: 异步读取/写入失败
OSD-04006: ReadFile() 失败, 无法读取文件
O/S-Error: (OS 1) 函数不正确。
DBV-00102: FILE (TOEC01.DBF) 在 verification read 操作 (-2) 期间出现文件 I/O 错误
说明该 数据文件的 11905 block存在 物理上的损坏,无法被读取
advise:
1. 尝试cp 该文件到其他位置 看是否能修复问题
2. 若步骤1 无效则在步骤1的基础上 对该数据块 做blockrecover,当然这需要该数据文件的全量备份和归档日志
3. 若没有备份考虑用 dbms_repair 包对该块标记为 corruption
建议你先查一下是否只有这样一个 物理坏块,这个块具体属于什么segment,就EXP看应当是TABLE,
那么可以考虑用 10231 event + CTAS 重建该表,并DROP 原表后再 exp
改造Oracle中文技术生态环境!
*<font color="red" size="2" face="courier">如果觉得本回复有意义,请点击本条回复右手边的Correct按钮,谢谢!</font>*
如何在OTN中文技术论坛提一个问题?
论坛礼仪需知及学习oracle的方法论
Maclean Liu
Oracle Database Administrator
Oracle Certified 10g/11g Master
www.askmaclean.com
请把需要上传的文件发给我
有问题请去OTN中文论坛开个帖子 我会回复 地址:http://www.otncn.org
如果需要发送附件,可以直接发邮件到 [email protected] -
RMAN ORA-19870: error reading backup piece 'location'
Hi All ,
I have run a restore from a RMAN backup and i got this error :
ORA-19870: error reading backup piece XX_df_23_11_2011_XXX_1_1.rman
ORA-19599: block number 616206 is corrupt in backup piece XX_df_23_11_2011_XXX_1_1.rmanThough the RMAN backup is still going on , it has not errored out, How can i find what all gets missing from the Source database , as in what all is present in the missing block ?
What is the use of MAXCORRUPT parameter ? can that be used here ? can this be prevented if i use maxcorrupt =1 and then run the restore ?
Also , Is there any way in which i can verify that all the backups are perfect before i drop my earlier database and run the restore. I think its the validate command but I am not sure, hence seek expert suggestion.
Please suggest
Thanks
Kk
Edited by: Kk on Dec 1, 2011 3:04 AMRMAN backup Fails with ORA-19599,ORA-19600 and ORA-19601 [ID 779386.1]
-
ORA-01991 invalid password file 'string'
Hi all
I am getting the message ORA-01991 invalid password file 'string' .
do i need to create a new password file.
If so what is the syntax and where to write the syntax.
can something be done which avoids creating the new password file.orapwd file=<filename> password=<password> entries=5
by default password file lcoations are
$Oracle_Home\database with the name of 'PWD' followed by ISD name.
eg.
PWDisd9i.ora -
Rman : ORA-19502: write error on file "
hi all,
I have a oracle 9.2.0.6, i am taking backup of primary database, my DB is on Sun box and all the datafile are the raw filesystems.......
but while taking backup i am getting an error.....
I have checked across the internet and i got to know that the error occured because of Disk space not sufficient as such the catalog is on win 2003 an oracle home of the catalog db is having 20 Gb of space whereas i am taking backup on H:\ there i am having more than 100gb of space...
please help me to resolve this problem....
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ch1 channel at 05/11/2009 13:00:19
ORA-19502: write error on file "H:\mainbackup\bk_inc0_65_1", blockno 269825 (blo
cksize=8192)
ORA-27063: skgfospo: number of bytes read/written is incorrect
Additional information: 131072
Additional information: 1048576we have more enough space on disks but still getting an error
pls suggest me...
channel ch1: starting piece 1 at 12-MAY-09
released channel: ch1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ch1 channel at 05/12/2009 12:46:07
ORA-19504: failed to create file "G:\mainbackup\bk_inc0_69_1"
ORA-27044: unable to write the header block of file
SVR4 Error: 28: No space left on device
Additional information: 1
{code} -
RMAN:ORA-12640 ERROR when perform BRBACKUP
I have scheduled the BRbackup job through DB13. But the job got the status: finished with error. And I checked the job as following(ECC 6/ABAP/):
Recovery Manager: Release 10.2.0.2.0 - Production on Wed May 7 16:09:39
2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
RMAN>
RMAN> connect target *
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-12640: Authentication adapter initialization failed
RMAN> *end-of-file*
RMAN>
host command complete
RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19>
20> 21> 22> 23> 24> 25> 26> 27> 28> 29> 30> 31> 32> 33> 34> 35> 36> 37>
38> 39> 40> 41> 42>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of catalog command at 05/07/2008 16:09:42
RMAN-06171: not connected to target database
BTW, I also find the error in topic:
Re: BRARCHIVE RMAN
But the status of that topic is : not answered.
So, I post the topic again.
What can I do to fix this problem?
Thanks in advance.Hi, Warren:
Many thanks for your reply.
1) I have added sapservice<SID> into adminstrator group and rerun the job, but I got the same error.
2) how can I checked the user environment of user: sapservice<SID> since I can not login the system by user: sapservice<SID>, and I just login the system by <sid>adm.
And the following is the detail job log of brbackup:
BR0051I BRBACKUP 7.00 (32)
BR0055I Start of database backup: bdxwdzzj.fnd 2008-05-07 14.45.35
BR0484I BRBACKUP log file: K:\oracle\DEV\sapbackup\bdxwdzzj.fnd
BR0477I Oracle pfile E:\oracle\DEV\102\database\initDEV.ora created from spfile E:\oracle\DEV\102\database\spfileDEV.ora
BR0101I Parameters
Name Value
oracle_sid DEV
oracle_home E:\oracle\DEV\102
oracle_profile E:\oracle\DEV\102\database\initDEV.ora
sapdata_home K:\oracle\DEV
sap_profile E:\oracle\DEV\102\database\initdev.sap
backup_mode FULL
backup_type online
backup_dev_type disk
backup_root_dir W:\backup\DB
compress no
disk_copy_cmd copy
cpio_disk_flags -pdcu
exec_parallel 0
system_info SAPServiceDEV CMPDEV01 Windows 5.2 Build 3790 Service Pack 2 AMD64
oracle_info DEV 10.2.0.2.0 8192 403 29170522 CMPDEV01 UTF8 UTF8
sap_info 700 SAPSR3 0002LK0003DEV0011I09091536040013NetWeaver_ORA
make_info NTAMD64 OCI_10201_SHARE Feb 11 2008
command_line brbackup -u / -jid FLLOG20080507144500 -c force -t online -m full -p initdev.sap -a -c force -p initdev.sap -cds
BR0116I ARCHIVE LOG LIST before backup for database instance DEV
Parameter Value
Database log mode Archive Mode
Automatic archival Enabled
Archive destination N:\oracle\DEV\oraarch\DEVarch
Archive format ARC%S_%R.%T
Oldest online log sequence 400
Next log sequence to archive 403
Current log sequence 403 SCN: 29170522
Database block size 8192 Thread: 1
Current system change number 29228679 ResetId: 649858176
BR0118I Tablespaces and data files
Tablespace TS-Status F-Status File Size Id. Device Link Type MaxSize IncrSize BlkSize
PSAPSR3 ONLINE* ONLINE+ J:\ORACLE\DEV\SAPDATA1\SR3_1\SR3.DATA1 2642419712 4 9 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ J:\ORACLE\DEV\SAPDATA1\SR3_2\SR3.DATA2 2663391232 5 9 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ J:\ORACLE\DEV\SAPDATA1\SR3_3\SR3.DATA3 2684362752 6 9 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ J:\ORACLE\DEV\SAPDATA1\SR3_4\SR3.DATA4 2663391232 7 9 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ J:\ORACLE\DEV\SAPDATA1\SR3_5\SR3.DATA5 2621448192 8 9 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ K:\ORACLE\DEV\SAPDATA3\SR3_11\SR3.DATA11 2894077952 14 10 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ K:\ORACLE\DEV\SAPDATA3\SR3_12\SR3.DATA12 2789220352 15 10 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ K:\ORACLE\DEV\SAPDATA3\SR3_13\SR3.DATA13 2873106432 16 10 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ K:\ORACLE\DEV\SAPDATA3\SR3_14\SR3.DATA14 2915049472 17 10 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ K:\ORACLE\DEV\SAPDATA3\SR3_15\SR3.DATA15 2873106432 18 10 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ K:\ORACLE\DEV\SAPDATA4\SR3_16\SR3.DATA16 2852134912 19 10 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ K:\ORACLE\DEV\SAPDATA4\SR3_17\SR3.DATA17 2936020992 20 10 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ K:\ORACLE\DEV\SAPDATA4\SR3_18\SR3.DATA18 3019907072 21 10 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ K:\ORACLE\DEV\SAPDATA4\SR3_19\SR3.DATA19 2852134912 22 10 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ K:\ORACLE\DEV\SAPDATA4\SR3_20\SR3.DATA20 2894077952 23 10 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ N:\ORACLE\DEV\SAPDATA2\SR3_10\SR3.DATA10 2705334272 13 13 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ N:\ORACLE\DEV\SAPDATA2\SR3_6\SR3.DATA6 2726305792 9 13 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ N:\ORACLE\DEV\SAPDATA2\SR3_7\SR3.DATA7 2768248832 10 13 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ N:\ORACLE\DEV\SAPDATA2\SR3_8\SR3.DATA8 2663391232 11 13 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ N:\ORACLE\DEV\SAPDATA2\SR3_9\SR3.DATA9 2705334272 12 13 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ J:\ORACLE\DEV\SAPDATA1\SR3700_1\SR3700.DATA1 4445970432 24 9 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ J:\ORACLE\DEV\SAPDATA1\SR3700_2\SR3700.DATA2 4404027392 25 9 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ J:\ORACLE\DEV\SAPDATA1\SR3700_3\SR3700.DATA3 4383055872 26 9 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ J:\ORACLE\DEV\SAPDATA1\SR3700_4\SR3700.DATA4 4257226752 27 9 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ K:\ORACLE\DEV\SAPDATA3\SR3700_10\SR3700.DATA10 4571799552 33 10 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ K:\ORACLE\DEV\SAPDATA3\SR3700_11\SR3700.DATA11 4550828032 34 10 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ K:\ORACLE\DEV\SAPDATA3\SR3700_12\SR3700.DATA12 4362084352 35 10 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ K:\ORACLE\DEV\SAPDATA3\SR3700_9\SR3700.DATA9 4613742592 32 10 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ K:\ORACLE\DEV\SAPDATA4\SR3700_13\SR3700.DATA13 4550828032 36 10 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ K:\ORACLE\DEV\SAPDATA4\SR3700_14\SR3700.DATA14 4676657152 37 10 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ K:\ORACLE\DEV\SAPDATA4\SR3700_15\SR3700.DATA15 4424998912 38 10 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ K:\ORACLE\DEV\SAPDATA4\SR3700_16\SR3700.DATA16 4424998912 39 10 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ N:\ORACLE\DEV\SAPDATA2\SR3700_5\SR3700.DATA5 4487913472 28 13 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ N:\ORACLE\DEV\SAPDATA2\SR3700_6\SR3700.DATA6 4257226752 29 13 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ N:\ORACLE\DEV\SAPDATA2\SR3700_7\SR3700.DATA7 3984596992 30 13 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ N:\ORACLE\DEV\SAPDATA2\SR3700_8\SR3700.DATA8 3858767872 31 13 NOLINK FILE 10485760000 20971520 8192
PSAPSR3USR ONLINE* ONLINE+ J:\ORACLE\DEV\SAPDATA1\SR3USR_1\SR3USR.DATA1 20979712 40 9 NOLINK FILE 10485760000 20971520 8192
PSAPTEMP ONLINE# ONLINE+ J:\ORACLE\DEV\SAPDATA2\TEMP_1\TEMP.DATA1 2097160192 -1 9 NOLINK FILE 10485760000 20971520 8192
PSAPUNDO ONLINE- ONLINE+ K:\ORACLE\DEV\SAPDATA3\UNDO_1\UNDO.DATA1 9248448512 2 10 NOLINK FILE 10485760000 20971520 8192
SYSAUX ONLINE* ONLINE+ J:\ORACLE\DEV\SAPDATA1\SYSAUX_1\SYSAUX.DATA1 230694912 3 9 NOLINK FILE 10485760000 20971520 8192
SYSTEM ONLINE* SYSTEM+ J:\ORACLE\DEV\SAPDATA1\SYSTEM_1\SYSTEM.DATA1 859840512 1 9 NOLINK FILE 10485760000 20971520 8192
BR0119I Redo log files
File Size Group Device Status Link Type
K:\ORACLE\DEV\MIRRLOGA\LOG_G11M2.DBF 524288512 1 10 INUSE NOLINK FILE
J:\ORACLE\DEV\ORIGLOGA\LOG_G11M1.DBF 524288512 1 9 INUSE NOLINK FILE
K:\ORACLE\DEV\MIRRLOGB\LOG_G12M2.DBF 524288512 2 10 INUSE NOLINK FILE
J:\ORACLE\DEV\ORIGLOGB\LOG_G12M1.DBF 524288512 2 9 INUSE NOLINK FILE
K:\ORACLE\DEV\MIRRLOGA\LOG_G13M2.DBF 524288512 3 10 INUSE NOLINK FILE
J:\ORACLE\DEV\ORIGLOGA\LOG_G13M1.DBF 524288512 3 9 INUSE NOLINK FILE
K:\ORACLE\DEV\MIRRLOGB\LOG_G14M2.DBF 524288512 4 10 INUSE NOLINK FILE
J:\ORACLE\DEV\ORIGLOGB\LOG_G14M1.DBF 524288512 4 9 INUSE NOLINK FILE
BR0120I Control files
File Size Id. Device Link Type
J:\ORACLE\DEV\ORIGLOGB\CNTRL\CNTRLDEV.DBF 12664832 0 9 NOLINK FILE
BR0280I BRBACKUP time stamp: 2008-05-07 14.45.41
BR0057I Backup of database: DEV
BR0058I BRBACKUP action ID: bdxwdzzj
BR0059I BRBACKUP function ID: fnd
BR0110I Backup mode: FULL
BR0077I Database file for backup: K:\oracle\DEV\sapbackup\CNTRLDEV.DBF
BR0061I 41 files found for backup, total size 130052.391 MB
BR0143I Backup type: online
BR0112I Files will not be compressed
BR0130I Backup device type: disk
BR0106I Files will be saved on disk in directory: W:\backup\DB\bdxwdzzj
BR0289I BRARCHIVE will be started at the end of processing
BR0134I Unattended mode with 'force' active - no operator confirmation allowed
BR0370I Directory W:\backup\DB\bdxwdzzj created
BR0202I Saving init_ora
BR0203I to W:\backup\DB\DEV ...
BR0202I Saving E:\oracle\DEV\102\database\initdev.sap
BR0203I to W:\backup\DB\DEV ...
BR0280I BRBACKUP time stamp: 2008-05-07 14.45.41
BR0198I Profiles saved successfully
BR0280I BRBACKUP time stamp: 2008-05-07 14.45.44
BR0315I 'Alter tablespace PSAPSR3 begin backup' successful
BR0202I Saving J:\ORACLE\DEV\SAPDATA1\SR3_1\SR3.DATA1
BR0203I to W:\backup\DB\bdxwdzzj\SR3.DATA1 ...
#FILE..... J:\ORACLE\DEV\SAPDATA1\SR3_1\SR3.DATA1
#SAVED.... W:\backup\DB\bdxwdzzj\SR3.DATA1 #1/1
BR0280I BRBACKUP time stamp: 2008-05-07 14.46.38
BR0063I 1 of 40 files processed - 2520.008 MB of 130040.313 MB done
BR0204I Percentage done: 1.94%, estimated end time: 15:34
BR0001I *_________________________________________________
BR0202I Saving J:\ORACLE\DEV\SAPDATA1\SR3_2\SR3.DATA2
BR0203I to W:\backup\DB\bdxwdzzj\SR3.DATA2 ...
#FILE..... J:\ORACLE\DEV\SAPDATA1\SR3_2\SR3.DATA2
#SAVED.... W:\backup\DB\bdxwdzzj\SR3.DATA2 #1/2
BR0280I BRBACKUP time stamp: 2008-05-07 14.48.51
BR0063I 2 of 40 files processed - 5060.016 MB of 130040.313 MB done
BR0204I Percentage done: 3.89%, estimated end time: 16:07
BR0001I **________________________________________________
BR0202I Saving J:\ORACLE\DEV\SAPDATA1\SR3_3\SR3.DATA3
BR0203I to W:\backup\DB\bdxwdzzj\SR3.DATA3 ...
#FILE..... J:\ORACLE\DEV\SAPDATA1\SR3_3\SR3.DATA3
#SAVED.... W:\backup\DB\bdxwdzzj\SR3.DATA3 #1/3
BR0280I BRBACKUP time stamp: 2008-05-07 14.49.46
BR0063I 3 of 40 files processed - 7620.023 MB of 130040.313 MB done
BR0204I Percentage done: 5.86%, estimated end time: 15:55
BR0001I ***_______________________________________________
BR0202I Saving J:\ORACLE\DEV\SAPDATA1\SR3_4\SR3.DATA4
BR0203I to W:\backup\DB\bdxwdzzj\SR3.DATA4 ...
#FILE..... J:\ORACLE\DEV\SAPDATA1\SR3_4\SR3.DATA4
#SAVED.... W:\backup\DB\bdxwdzzj\SR3.DATA4 #1/4
BR0280I BRBACKUP time stamp: 2008-05-07 14.52.04
BR0063I 4 of 40 files processed - 10160.031 MB of 130040.313 MB done
BR0204I Percentage done: 7.81%, estimated end time: 16:07
BR0001I ****______________________________________________
BR0202I Saving J:\ORACLE\DEV\SAPDATA1\SR3_5\SR3.DATA5
BR0203I to W:\backup\DB\bdxwdzzj\SR3.DATA5 ...
#FILE..... J:\ORACLE\DEV\SAPDATA1\SR3_5\SR3.DATA5
#SAVED.... W:\backup\DB\bdxwdzzj\SR3.DATA5 #1/5
BR0280I BRBACKUP time stamp: 2008-05-07 14.52.55
BR0063I 5 of 40 files processed - 12660.039 MB of 130040.313 MB done
BR0204I Percentage done: 9.74%, estimated end time: 15:59
BR0001I *****_____________________________________________
BR0202I Saving K:\ORACLE\DEV\SAPDATA3\SR3_11\SR3.DATA11
BR0203I to W:\backup\DB\bdxwdzzj\SR3.DATA11 ...
#FILE..... K:\ORACLE\DEV\SAPDATA3\SR3_11\SR3.DATA11
#SAVED.... W:\backup\DB\bdxwdzzj\SR3.DATA11 #1/6
BR0280I BRBACKUP time stamp: 2008-05-07 14.54.40
BR0063I 6 of 40 files processed - 15420.047 MB of 130040.313 MB done
BR0204I Percentage done: 11.86%, estimated end time: 16:01
BR0001I ******____________________________________________
BR0202I Saving K:\ORACLE\DEV\SAPDATA3\SR3_12\SR3.DATA12
BR0203I to W:\backup\DB\bdxwdzzj\SR3.DATA12 ...
#FILE..... K:\ORACLE\DEV\SAPDATA3\SR3_12\SR3.DATA12
#SAVED.... W:\backup\DB\bdxwdzzj\SR3.DATA12 #1/7
BR0280I BRBACKUP time stamp: 2008-05-07 14.56.16
BR0063I 7 of 40 files processed - 18080.055 MB of 130040.313 MB done
BR0204I Percentage done: 13.90%, estimated end time: 16:01
BR0001I *******___________________________________________
BR0202I Saving K:\ORACLE\DEV\SAPDATA3\SR3_13\SR3.DATA13
BR0203I to W:\backup\DB\bdxwdzzj\SR3.DATA13 ...
#FILE..... K:\ORACLE\DEV\SAPDATA3\SR3_13\SR3.DATA13
#SAVED.... W:\backup\DB\bdxwdzzj\SR3.DATA13 #1/8
BR0280I BRBACKUP time stamp: 2008-05-07 14.58.17
BR0063I 8 of 40 files processed - 20820.063 MB of 130040.313 MB done
BR0204I Percentage done: 16.01%, estimated end time: 16:04
BR0001I ********__________________________________________
BR0202I Saving K:\ORACLE\DEV\SAPDATA3\SR3_14\SR3.DATA14
BR0203I to W:\backup\DB\bdxwdzzj\SR3.DATA14 ...
#FILE..... K:\ORACLE\DEV\SAPDATA3\SR3_14\SR3.DATA14
#SAVED.... W:\backup\DB\bdxwdzzj\SR3.DATA14 #1/9
BR0280I BRBACKUP time stamp: 2008-05-07 15.00.17
BR0063I 9 of 40 files processed - 23600.070 MB of 130040.313 MB done
BR0204I Percentage done: 18.15%, estimated end time: 16:06
BR0001I *********_________________________________________
BR0202I Saving K:\ORACLE\DEV\SAPDATA3\SR3_15\SR3.DATA15
BR0203I to W:\backup\DB\bdxwdzzj\SR3.DATA15 ...
#FILE..... K:\ORACLE\DEV\SAPDATA3\SR3_15\SR3.DATA15
#SAVED.... W:\backup\DB\bdxwdzzj\SR3.DATA15 #1/10
BR0280I BRBACKUP time stamp: 2008-05-07 15.01.50
BR0063I 10 of 40 files processed - 26340.078 MB of 130040.313 MB done
BR0204I Percentage done: 20.26%, estimated end time: 16:05
BR0001I **********________________________________________
BR0202I Saving K:\ORACLE\DEV\SAPDATA4\SR3_16\SR3.DATA16
BR0203I to W:\backup\DB\bdxwdzzj\SR3.DATA16 ...
#FILE..... K:\ORACLE\DEV\SAPDATA4\SR3_16\SR3.DATA16
#SAVED.... W:\backup\DB\bdxwdzzj\SR3.DATA16 #1/11
BR0280I BRBACKUP time stamp: 2008-05-07 15.03.50
BR0063I 11 of 40 files processed - 29060.086 MB of 130040.313 MB done
BR0204I Percentage done: 22.35%, estimated end time: 16:06
BR0001I ***********_______________________________________
BR0202I Saving K:\ORACLE\DEV\SAPDATA4\SR3_17\SR3.DATA17
BR0203I to W:\backup\DB\bdxwdzzj\SR3.DATA17 ...
#FILE..... K:\ORACLE\DEV\SAPDATA4\SR3_17\SR3.DATA17
#SAVED.... W:\backup\DB\bdxwdzzj\SR3.DATA17 #1/12
BR0280I BRBACKUP time stamp: 2008-05-07 15.04.54
BR0063I 12 of 40 files processed - 31860.094 MB of 130040.313 MB done
BR0204I Percentage done: 24.50%, estimated end time: 16:04
BR0001I ************______________________________________
BR0202I Saving K:\ORACLE\DEV\SAPDATA4\SR3_18\SR3.DATA18
BR0203I to W:\backup\DB\bdxwdzzj\SR3.DATA18 ...
#FILE..... K:\ORACLE\DEV\SAPDATA4\SR3_18\SR3.DATA18
#SAVED.... W:\backup\DB\bdxwdzzj\SR3.DATA18 #1/13
BR0280I BRBACKUP time stamp: 2008-05-07 15.07.06
BR0063I 13 of 40 files processed - 34740.102 MB of 130040.313 MB done
BR0204I Percentage done: 26.71%, estimated end time: 16:05
BR0001I *************_____________________________________
BR0202I Saving K:\ORACLE\DEV\SAPDATA4\SR3_19\SR3.DATA19
BR0203I to W:\backup\DB\bdxwdzzj\SR3.DATA19 ...
#FILE..... K:\ORACLE\DEV\SAPDATA4\SR3_19\SR3.DATA19
#SAVED.... W:\backup\DB\bdxwdzzj\SR3.DATA19 #1/14
BR0280I BRBACKUP time stamp: 2008-05-07 15.08.44
BR0063I 14 of 40 files processed - 37460.109 MB of 130040.313 MB done
BR0204I Percentage done: 28.81%, estimated end time: 16:05
BR0001I **************____________________________________
BR0202I Saving K:\ORACLE\DEV\SAPDATA4\SR3_20\SR3.DATA20
BR0203I to W:\backup\DB\bdxwdzzj\SR3.DATA20 ...
#FILE..... K:\ORACLE\DEV\SAPDATA4\SR3_20\SR3.DATA20
#SAVED.... W:\backup\DB\bdxwdzzj\SR3.DATA20 #1/15
BR0280I BRBACKUP time stamp: 2008-05-07 15.10.47
BR0063I 15 of 40 files processed - 40220.117 MB of 130040.313 MB done
BR0204I Percentage done: 30.93%, estimated end time: 16:06
BR0001I ***************___________________________________
BR0202I Saving N:\ORACLE\DEV\SAPDATA2\SR3_10\SR3.DATA10
BR0203I to W:\backup\DB\bdxwdzzj\SR3.DATA10 ...
#FILE..... N:\ORACLE\DEV\SAPDATA2\SR3_10\SR3.DATA10
#SAVED.... W:\backup\DB\bdxwdzzj\SR3.DATA10 #1/16
BR0280I BRBACKUP time stamp: 2008-05-07 15.11.49
BR0063I 16 of 40 files processed - 42800.125 MB of 130040.313 MB done
BR0204I Percentage done: 32.91%, estimated end time: 16:05
BR0001I ****************__________________________________
BR0202I Saving N:\ORACLE\DEV\SAPDATA2\SR3_6\SR3.DATA6
BR0203I to W:\backup\DB\bdxwdzzj\SR3.DATA6 ...
#FILE..... N:\ORACLE\DEV\SAPDATA2\SR3_6\SR3.DATA6
#SAVED.... W:\backup\DB\bdxwdzzj\SR3.DATA6 #1/17
BR0280I BRBACKUP time stamp: 2008-05-07 15.13.43
BR0063I 17 of 40 files processed - 45400.133 MB of 130040.313 MB done
BR0204I Percentage done: 34.91%, estimated end time: 16:05
BR0001I *****************_________________________________
BR0202I Saving N:\ORACLE\DEV\SAPDATA2\SR3_7\SR3.DATA7
BR0203I to W:\backup\DB\bdxwdzzj\SR3.DATA7 ...
#FILE..... N:\ORACLE\DEV\SAPDATA2\SR3_7\SR3.DATA7
#SAVED.... W:\backup\DB\bdxwdzzj\SR3.DATA7 #1/18
BR0280I BRBACKUP time stamp: 2008-05-07 15.15.23
BR0063I 18 of 40 files processed - 48040.141 MB of 130040.313 MB done
BR0204I Percentage done: 36.94%, estimated end time: 16:06
BR0001I ******************________________________________
BR0202I Saving N:\ORACLE\DEV\SAPDATA2\SR3_8\SR3.DATA8
BR0203I to W:\backup\DB\bdxwdzzj\SR3.DATA8 ...
#FILE..... N:\ORACLE\DEV\SAPDATA2\SR3_8\SR3.DATA8
#SAVED.... W:\backup\DB\bdxwdzzj\SR3.DATA8 #1/19
BR0280I BRBACKUP time stamp: 2008-05-07 15.17.24
BR0063I 19 of 40 files processed - 50580.148 MB of 130040.313 MB done
BR0204I Percentage done: 38.90%, estimated end time: 16:07
BR0001I *******************_______________________________
BR0202I Saving N:\ORACLE\DEV\SAPDATA2\SR3_9\SR3.DATA9
BR0203I to W:\backup\DB\bdxwdzzj\SR3.DATA9 ...
#FILE..... N:\ORACLE\DEV\SAPDATA2\SR3_9\SR3.DATA9
#SAVED.... W:\backup\DB\bdxwdzzj\SR3.DATA9 #1/20
BR0280I BRBACKUP time stamp: 2008-05-07 15.19.01
BR0063I 20 of 40 files processed - 53160.156 MB of 130040.313 MB done
BR0204I Percentage done: 40.88%, estimated end time: 16:07
BR0001I ********************______________________________
BR0280I BRBACKUP time stamp: 2008-05-07 15.19.02
BR0317I 'Alter tablespace PSAPSR3 end backup' successful
BR0280I BRBACKUP time stamp: 2008-05-07 15.19.03
BR0315I 'Alter tablespace PSAPSR3700 begin backup' successful
BR0202I Saving J:\ORACLE\DEV\SAPDATA1\SR3700_1\SR3700.DATA1
BR0203I to W:\backup\DB\bdxwdzzj\SR3700.DATA1 ...
#FILE..... J:\ORACLE\DEV\SAPDATA1\SR3700_1\SR3700.DATA1
#SAVED.... W:\backup\DB\bdxwdzzj\SR3700.DATA1 #1/21
BR0280I BRBACKUP time stamp: 2008-05-07 15.21.55
BR0063I 21 of 40 files processed - 57400.164 MB of 130040.313 MB done
BR0204I Percentage done: 44.14%, estimated end time: 16:07
BR0001I **********************____________________________
BR0202I Saving J:\ORACLE\DEV\SAPDATA1\SR3700_2\SR3700.DATA2
BR0203I to W:\backup\DB\bdxwdzzj\SR3700.DATA2 ...
#FILE..... J:\ORACLE\DEV\SAPDATA1\SR3700_2\SR3700.DATA2
#SAVED.... W:\backup\DB\bdxwdzzj\SR3700.DATA2 #1/22
BR0280I BRBACKUP time stamp: 2008-05-07 15.24.44
BR0063I 22 of 40 files processed - 61600.172 MB of 130040.313 MB done
BR0204I Percentage done: 47.37%, estimated end time: 16:08
BR0001I ************************__________________________
BR0202I Saving J:\ORACLE\DEV\SAPDATA1\SR3700_3\SR3700.DATA3
BR0203I to W:\backup\DB\bdxwdzzj\SR3700.DATA3 ...
#FILE..... J:\ORACLE\DEV\SAPDATA1\SR3700_3\SR3700.DATA3
#SAVED.... W:\backup\DB\bdxwdzzj\SR3700.DATA3 #1/23
BR0280I BRBACKUP time stamp: 2008-05-07 15.27.24
BR0063I 23 of 40 files processed - 65780.180 MB of 130040.313 MB done
BR0204I Percentage done: 50.58%, estimated end time: 16:08
BR0001I *************************_________________________
BR0202I Saving J:\ORACLE\DEV\SAPDATA1\SR3700_4\SR3700.DATA4
BR0203I to W:\backup\DB\bdxwdzzj\SR3700.DATA4 ...
#FILE..... J:\ORACLE\DEV\SAPDATA1\SR3700_4\SR3700.DATA4
#SAVED.... W:\backup\DB\bdxwdzzj\SR3700.DATA4 #1/24
BR0280I BRBACKUP time stamp: 2008-05-07 15.29.43
BR0063I 24 of 40 files processed - 69840.188 MB of 130040.313 MB done
BR0204I Percentage done: 53.71%, estimated end time: 16:07
BR0001I ***************************_______________________
BR0202I Saving K:\ORACLE\DEV\SAPDATA3\SR3700_10\SR3700.DATA10
BR0203I to W:\backup\DB\bdxwdzzj\SR3700.DATA10 ...
#FILE..... K:\ORACLE\DEV\SAPDATA3\SR3700_10\SR3700.DATA10
#SAVED.... W:\backup\DB\bdxwdzzj\SR3700.DATA10 #1/25
BR0280I BRBACKUP time stamp: 2008-05-07 15.32.52
BR0063I 25 of 40 files processed - 74200.195 MB of 130040.313 MB done
BR0204I Percentage done: 57.06%, estimated end time: 16:08
BR0001I *****************************_____________________
BR0202I Saving K:\ORACLE\DEV\SAPDATA3\SR3700_11\SR3700.DATA11
BR0203I to W:\backup\DB\bdxwdzzj\SR3700.DATA11 ...
#FILE..... K:\ORACLE\DEV\SAPDATA3\SR3700_11\SR3700.DATA11
#SAVED.... W:\backup\DB\bdxwdzzj\SR3700.DATA11 #1/26
BR0280I BRBACKUP time stamp: 2008-05-07 15.35.56
BR0063I 26 of 40 files processed - 78540.203 MB of 130040.313 MB done
BR0204I Percentage done: 60.40%, estimated end time: 16:08
BR0001I ******************************____________________
BR0202I Saving K:\ORACLE\DEV\SAPDATA3\SR3700_12\SR3700.DATA12
BR0203I to W:\backup\DB\bdxwdzzj\SR3700.DATA12 ...
#FILE..... K:\ORACLE\DEV\SAPDATA3\SR3700_12\SR3700.DATA12
#SAVED.... W:\backup\DB\bdxwdzzj\SR3700.DATA12 #1/27
BR0280I BRBACKUP time stamp: 2008-05-07 15.38.39
BR0063I 27 of 40 files processed - 82700.211 MB of 130040.313 MB done
BR0204I Percentage done: 63.60%, estimated end time: 16:08
BR0001I ********************************__________________
BR0202I Saving K:\ORACLE\DEV\SAPDATA3\SR3700_9\SR3700.DATA9
BR0203I to W:\backup\DB\bdxwdzzj\SR3700.DATA9 ...
#FILE..... K:\ORACLE\DEV\SAPDATA3\SR3700_9\SR3700.DATA9
#SAVED.... W:\backup\DB\bdxwdzzj\SR3700.DATA9 #1/28
BR0280I BRBACKUP time stamp: 2008-05-07 15.41.21
BR0063I 28 of 40 files processed - 87100.219 MB of 130040.313 MB done
BR0204I Percentage done: 66.98%, estimated end time: 16:08
BR0001I *********************************_________________
BR0202I Saving K:\ORACLE\DEV\SAPDATA4\SR3700_13\SR3700.DATA13
BR0203I to W:\backup\DB\bdxwdzzj\SR3700.DATA13 ...
#FILE..... K:\ORACLE\DEV\SAPDATA4\SR3700_13\SR3700.DATA13
#SAVED.... W:\backup\DB\bdxwdzzj\SR3700.DATA13 #1/29
BR0280I BRBACKUP time stamp: 2008-05-07 15.43.46
BR0063I 29 of 40 files processed - 91440.227 MB of 130040.313 MB done
BR0204I Percentage done: 70.32%, estimated end time: 16:08
BR0001I ***********************************_______________
BR0202I Saving K:\ORACLE\DEV\SAPDATA4\SR3700_14\SR3700.DATA14
BR0203I to W:\backup\DB\bdxwdzzj\SR3700.DATA14 ...
#FILE..... K:\ORACLE\DEV\SAPDATA4\SR3700_14\SR3700.DATA14
#SAVED.... W:\backup\DB\bdxwdzzj\SR3700.DATA14 #1/30
BR0280I BRBACKUP time stamp: 2008-05-07 15.46.54
BR0063I 30 of 40 files processed - 95900.234 MB of 130040.313 MB done
BR0204I Percentage done: 73.75%, estimated end time: 16:08
BR0001I *************************************_____________
BR0202I Saving K:\ORACLE\DEV\SAPDATA4\SR3700_15\SR3700.DATA15
BR0203I to W:\backup\DB\bdxwdzzj\SR3700.DATA15 ...
#FILE..... K:\ORACLE\DEV\SAPDATA4\SR3700_15\SR3700.DATA15
#SAVED.... W:\backup\DB\bdxwdzzj\SR3700.DATA15 #1/31
BR0280I BRBACKUP time stamp: 2008-05-07 15.49.54
BR0063I 31 of 40 files processed - 100120.242 MB of 130040.313 MB done
BR0204I Percentage done: 76.99%, estimated end time: 16:09
BR0001I **************************************____________
BR0202I Saving K:\ORACLE\DEV\SAPDATA4\SR3700_16\SR3700.DATA16
BR0203I to W:\backup\DB\bdxwdzzj\SR3700.DATA16 ...
#FILE..... K:\ORACLE\DEV\SAPDATA4\SR3700_16\SR3700.DATA16
#SAVED.... W:\backup\DB\bdxwdzzj\SR3700.DATA16 #1/32
BR0280I BRBACKUP time stamp: 2008-05-07 15.52.23
BR0063I 32 of 40 files processed - 104340.250 MB of 130040.313 MB done
BR0204I Percentage done: 80.24%, estimated end time: 16:08
BR0001I ****************************************__________
BR0202I Saving N:\ORACLE\DEV\SAPDATA2\SR3700_5\SR3700.DATA5
BR0203I to W:\backup\DB\bdxwdzzj\SR3700.DATA5 ...
#FILE..... N:\ORACLE\DEV\SAPDATA2\SR3700_5\SR3700.DATA5
#SAVED.... W:\backup\DB\bdxwdzzj\SR3700.DATA5 #1/33
BR0280I BRBACKUP time stamp: 2008-05-07 15.54.58
BR0063I 33 of 40 files processed - 108620.258 MB of 130040.313 MB done
BR0204I Percentage done: 83.53%, estimated end time: 16:08
BR0001I ******************************************________
BR0348I Following file has been extended by database: N:\ORACLE\DEV\SAPDATA2\SR3700_5\SR3700.DATA5 4508884992
BR0202I Saving N:\ORACLE\DEV\SAPDATA2\SR3700_6\SR3700.DATA6
BR0203I to W:\backup\DB\bdxwdzzj\SR3700.DATA6 ...
#FILE..... N:\ORACLE\DEV\SAPDATA2\SR3700_6\SR3700.DATA6
#SAVED.... W:\backup\DB\bdxwdzzj\SR3700.DATA6 #1/34
BR0280I BRBACKUP time stamp: 2008-05-07 15.57.42
BR0063I 34 of 40 files processed - 112680.266 MB of 130040.313 MB done
BR0204I Percentage done: 86.65%, estimated end time: 16:08
BR0001I *******************************************_______
BR0202I Saving N:\ORACLE\DEV\SAPDATA2\SR3700_7\SR3700.DATA7
BR0203I to W:\backup\DB\bdxwdzzj\SR3700.DATA7 ...
#FILE..... N:\ORACLE\DEV\SAPDATA2\SR3700_7\SR3700.DATA7
#SAVED.... W:\backup\DB\bdxwdzzj\SR3700.DATA7 #1/35
BR0280I BRBACKUP time stamp: 2008-05-07 16.00.15
BR0063I 35 of 40 files processed - 116480.273 MB of 130040.313 MB done
BR0204I Percentage done: 89.57%, estimated end time: 16:08
BR0001I *********************************************_____
BR0202I Saving N:\ORACLE\DEV\SAPDATA2\SR3700_8\SR3700.DATA8
BR0203I to W:\backup\DB\bdxwdzzj\SR3700.DATA8 ...
#FILE..... N:\ORACLE\DEV\SAPDATA2\SR3700_8\SR3700.DATA8
#SAVED.... W:\backup\DB\bdxwdzzj\SR3700.DATA8 #1/36
BR0280I BRBACKUP time stamp: 2008-05-07 16.02.41
BR0063I 36 of 40 files processed - 120160.281 MB of 130040.313 MB done
BR0204I Percentage done: 92.40%, estimated end time: 16:09
BR0001I **********************************************____
BR0280I BRBACKUP time stamp: 2008-05-07 16.02.43
BR0317I 'Alter tablespace PSAPSR3700 end backup' successful
BR0280I BRBACKUP time stamp: 2008-05-07 16.02.43
BR0315I 'Alter tablespace PSAPSR3USR begin backup' successful
BR0202I Saving J:\ORACLE\DEV\SAPDATA1\SR3USR_1\SR3USR.DATA1
BR0203I to W:\backup\DB\bdxwdzzj\SR3USR.DATA1 ...
#FILE..... J:\ORACLE\DEV\SAPDATA1\SR3USR_1\SR3USR.DATA1
#SAVED.... W:\backup\DB\bdxwdzzj\SR3USR.DATA1 #1/37
BR0280I BRBACKUP time stamp: 2008-05-07 16.02.45
BR0063I 37 of 40 files processed - 120180.289 MB of 130040.313 MB done
BR0204I Percentage done: 92.42%, estimated end time: 16:09
BR0001I **********************************************____
BR0280I BRBACKUP time stamp: 2008-05-07 16.02.45
BR0317I 'Alter tablespace PSAPSR3USR end backup' successful
BR0280I BRBACKUP time stamp: 2008-05-07 16.02.46
BR0315I 'Alter tablespace PSAPUNDO begin backup' successful
BR0202I Saving K:\ORACLE\DEV\SAPDATA3\UNDO_1\UNDO.DATA1
BR0203I to W:\backup\DB\bdxwdzzj\UNDO.DATA1 ...
#FILE..... K:\ORACLE\DEV\SAPDATA3\UNDO_1\UNDO.DATA1
#SAVED.... W:\backup\DB\bdxwdzzj\UNDO.DATA1 #1/38
BR0280I BRBACKUP time stamp: 2008-05-07 16.08.35
BR0063I 38 of 40 files processed - 129000.297 MB of 130040.313 MB done
BR0204I Percentage done: 99.20%, estimated end time: 16:09
BR0001I **************************************************
BR0280I BRBACKUP time stamp: 2008-05-07 16.08.46
BR0317I 'Alter tablespace PSAPUNDO end backup' successful
BR0280I BRBACKUP time stamp: 2008-05-07 16.08.47
BR0315I 'Alter tablespace SYSAUX begin backup' successful
BR0202I Saving J:\ORACLE\DEV\SAPDATA1\SYSAUX_1\SYSAUX.DATA1
BR0203I to W:\backup\DB\bdxwdzzj\SYSAUX.DATA1 ...
#FILE..... J:\ORACLE\DEV\SAPDATA1\SYSAUX_1\SYSAUX.DATA1
#SAVED.... W:\backup\DB\bdxwdzzj\SYSAUX.DATA1 #1/39
BR0280I BRBACKUP time stamp: 2008-05-07 16.09.03
BR0063I 39 of 40 files processed - 129220.305 MB of 130040.313 MB done
BR0204I Percentage done: 99.37%, estimated end time: 16:09
BR0001I **************************************************
BR0280I BRBACKUP time stamp: 2008-05-07 16.09.04
BR0317I 'Alter tablespace SYSAUX end backup' successful
BR0280I BRBACKUP time stamp: 2008-05-07 16.09.11
BR0315I 'Alter tablespace SYSTEM begin backup' successful
BR0202I Saving J:\ORACLE\DEV\SAPDATA1\SYSTEM_1\SYSTEM.DATA1
BR0203I to W:\backup\DB\bdxwdzzj\SYSTEM.DATA1 ...
#FILE..... J:\ORACLE\DEV\SAPDATA1\SYSTEM_1\SYSTEM.DATA1
#SAVED.... W:\backup\DB\bdxwdzzj\SYSTEM.DATA1 #1/40
BR0280I BRBACKUP time stamp: 2008-05-07 16.09.29
BR0063I 40 of 40 files processed - 130040.313 MB of 130040.313 MB done
BR0204I Percentage done: 100.00%, estimated end time: 16:09
BR0001I **************************************************
BR0280I BRBACKUP time stamp: 2008-05-07 16.09.29
BR0317I 'Alter tablespace SYSTEM end backup' successful
BR0280I BRBACKUP time stamp: 2008-05-07 16.09.34
BR0530I Cataloging backups of all database files...
BR0278E Command output of 'E:\oracle\DEV\102\BIN\rman nocatalog':
Recovery Manager: Release 10.2.0.2.0 - Production on Wed May 7 16:09:39 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
RMAN>
RMAN> connect target *
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-12640: Authentication adapter initialization failed
RMAN> *end-of-file*
RMAN>
host command complete
RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21> 22> 23> 24> 25> 26> 27> 28> 29> 30> 31> 32> 33> 34> 35> 36> 37> 38> 39> 40> 41> 42>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of catalog command at 05/07/2008 16:09:42
RMAN-06171: not connected to target database
RMAN>
Recovery Manager complete.
BR0280I BRBACKUP time stamp: 2008-05-07 16.09.42
BR0279E Return code from 'E:\oracle\DEV\102\BIN\rman nocatalog': 1
BR0536E RMAN call for database instance DEV failed
BR0280I BRBACKUP time stamp: 2008-05-07 16.09.42
BR0532E Cataloging backups of all database files failed
BR0056I End of database backup: bdxwdzzj.fnd 2008-05-07 16.09.42
BR0280I BRBACKUP time stamp: 2008-05-07 16.09.48
BR0054I BRBACKUP terminated with errors
BR0280I BRBACKUP time stamp: 2008-05-07 16.09.48
BR0291I BRARCHIVE will be started with options '-U -jid FLLOG20080507144500 -d disk -c force -p initdev.sap -cds'
BR0280I BRBACKUP time stamp: 2008-05-07 16.10.26
BR0292I Execution of BRARCHIVE finished with return code 3 -
RMAN ORA-19625 (URGENT)
Hi all can anyone help me solve the problem asap, I am unable to fix it. While trying to do a backup I got this error what shall I do?
RMAN-06059: expected archived log not found, lost of archived log compromises re
coverability
ORA-19625: error identifying file C:\DEVIIST\ARCHIVE DEST\ARC00044.001
ORA-27041: unable to open file
OSD-04002: unable to open fileThis error message is quite clear, the mentioned archivelog cannot be found, although RMAN 'thinks' it has to be there. Here's the full description for RMAN-06059:
Error: RMAN-06059 (RMAN-6059)
Text: expected archived log not found, lost of archived log compromises
recoverability
Cause: The archived log was not found. The repository thinks it does
exist. If the archived log has in fact been lost and there is no
backup, then the database is no longer recoverable across the
point in time covered by the archived log. This may occur because
the archived log was removed by an outside utility without
updating the repository.
Action: If the archived log has been removed with an outside utility and
the archivelog has already been backed up, then you can
synchronize the repository by running CROSSCHECK ARCHIVELOG ALL.
If the archivelog has not been previously backed up, then you
should take a full backup of the database and archivelogs to
preserve recoverability. Previous backups are not fully
recoverable. -
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
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 '/u01/oracle/db_back/%F.ctl';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 2;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '/u01/oracle/db_back/%U' MAXPIECESIZE 20000000;
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE EXCLUDE FOR TABLESPACE 'EXAMPLE';
CONFIGURE EXCLUDE FOR TABLESPACE 'STAGING';
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/oracle/dbs/snapcf_wilson.f'; # default----备份数据文件8,4
RMAN> backup datafile 8,4;
Starting backup at 11-MAR-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=143 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=134 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00008 name=/u01/oradata/wilson/paulll01.dbf
channel ORA_DISK_1: starting piece 1 at 11-MAR-11
channel ORA_DISK_2: starting full datafile backupset
channel ORA_DISK_2: specifying datafile(s) in backupset
input datafile fno=00004 name=/u01/oradata/wilson/users01.dbf
channel ORA_DISK_2: starting piece 1 at 11-MAR-11
channel ORA_DISK_1: finished piece 1 at 11-MAR-11 with 2 copies and tag TAG20110311T145635
piece handle=/u01/oracle/db_back/12m6v813_1_1 comment=NONE
piece handle=/u01/oracle/db_back/12m6v813_1_2 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_2 channel at 03/11/2011 14:56:36
ORA-19806: cannot make duplex backups in recovery area提出问题:
从备份的输出内容来看,好像/u01/oracle/db_back/下面备份成功,但是怎么闪回恢复区备份失败?奇怪,我把数据备份设置到/u01/oracle/db_back/下面了,怎么还会备份到闪回恢复区啊,请教各位高手。
明明配置了CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '/u01/oracle/db_back/%U' MAXPIECESIZE 20000000,那备份怎么会即存在/u01/oracle/db_back又存在闪回恢复区?
问题发现:
如果将CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 2改为 CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;就可以成功备份。为什么写成2就不行呢?写成2又该如何配置呢?
Edited by: Lonion on 2012-8-30 上午1:53CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 2
备份数据文件到磁盘时保持2份
flashback area不支持 多份backup拷贝
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name G11R23 are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
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 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 2;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\APP\ML\PRODUCT\11.2.0\DBHOME_1\DATABASE\SNCFG11R23.ORA'; # default
RMAN> backup datafile 3 format 'D:\%U.bak';
Starting backup at 30-AUG-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00003 name=D:\APP\ML\ORADATA\G11R23\DATAFILE\O1_MF_UNDOTBS1_83C9K4YY_.DBF
channel ORA_DISK_1: starting piece 1 at 30-AUG-12
channel ORA_DISK_1: finished piece 1 at 30-AUG-12 with 2 copies and tag TAG20120830T171519
piece handle=D:\03NJV4T7_1_1.BAK comment=NONE
piece handle=D:\03NJV4T7_1_2.BAK comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 30-AUG-12CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1 ;
修改为仅保留一份数据文件备份
RMAN> backup datafile 3 format 'D:\%U.bak';
Starting backup at 30-AUG-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00003 name=D:\APP\ML\ORADATA\G11R23\DATAFILE\O1_MF_UNDOTBS1_83C9K4YY_.DBF
channel ORA_DISK_1: starting piece 1 at 30-AUG-12
channel ORA_DISK_1: finished piece 1 at 30-AUG-12
piece handle=D:\05NJV51I_1_1.BAK tag=TAG20120830T171738 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 30-AUG-12
对于flashback area 需要 CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1 ;
你的问题 "好像/u01/oracle/db_back/下面备份成功,但是怎么闪回恢复区备份失败?"
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
PARALLELISM 2
你的并行度是2 但是
CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '/u01/oracle/db_back/%U' MAXPIECESIZE 20000000;
你仅指定了一个channel 的 备份路径 , 另一个channel 没有!!
*<font color="red" size="2" face="courier">如果觉得本回复有意义,请点击本条回复右手边的Correct按钮,谢谢!</font>*
如何在OTN中文技术论坛提一个问题?
论坛礼仪需知及学习oracle的方法论
Maclean Liu
Oracle Database Administrator
Oracle Certified 10g/11g Master
www.askmaclean.com
Edited by: Liu Maclean on 2012-8-30 上午2:28 -
Oracle 10.1 + rman restore
Hi all,
I have restored a rman backup to another host with same directories.
I have stopped my database. When i restart it i have these error message :
ORA-01991: invalid password file '/oracle/product/10.1.0.4/dbs/orapwPREP'
When i try to recreate the password file, i have these error message :
OPW-00005: File with same name exists - please delete or rename
I have deleted this file before recreate it.
Do you have an idea ?
Thanks.user12064507 wrote:
Hi all,
I have restored a rman backup to another host with same directories.
I have stopped my database. When i restart it i have these error message :
ORA-01991: invalid password file '/oracle/product/10.1.0.4/dbs/orapwPREP'
When i try to recreate the password file, i have these error message :
OPW-00005: File with same name exists - please delete or rename
I have deleted this file before recreate it.
Do you have an idea ?
Thanks.
user12064507 wrote:
Hi all,
I have restored a rman backup to another host with same directories.
I have stopped my database. When i restart it i have these error message :
ORA-01991: invalid password file '/oracle/product/10.1.0.4/dbs/orapwPREP'
When i try to recreate the password file, i have these error message :
OPW-00005: File with same name exists - please delete or rename
I have deleted this file before recreate it.
Do you have an idea ?
Thanks.
Oracle is too dumb to lie.
Believe the error messages.
how can we reproduce what you report?
How do I ask a question on the forums?
https://forums.oracle.com/forums/thread.jspa?threadID=2174552#9360002 -
Duplicating a db to another host via rman
I found a few documents on this topic, but didn't resolve my issue.
I am trying to restore an RMAN backup to a different host
(with same instance name, different path) from where the backup was taken.
And while running it gives the following error:
ORA-19505: failed to identify file "D:\ORACLE\BACKUP\TRACKER_20050920_FULL.S148P1"
ORA-27041: unable to open file
ORA-04002 unable to open file
O/S-Error : (OS 21) device not ready
Here D: drive is where I backup via rman ervery day.
If any of you had come across this problem and had a solution to this, could you please share it with me.
Thanks
P.S. I'm able to connect to catalog, target and auxiliary.
Charlierun on host B:
step 1. create auxiliary instance and connect to auxiliary instance in nomount mode
SQL> connect sys/syspw@aux as sysdba
Connected to an idle instance.
SQL>startup nomount pfile='C:\oracle\admin\tracker\scripts\initauxdb.ora'
run on host A:
step 2. RMAN> connect catalog rman/rmanpw@rman
RMAN> connect target sys/syspw@target
RMAN> connect auxiliary sys/syspw@aux
step 3. RMAN> run
RMAN> {
RMAN> ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
RMAN> DUPLICATE TARGET DATABASE TO "auxdb"
RMAN> PFILE='D:\oracle\admin\tracker\scripts\initauxdb.ora';
RMAN> }
ORA-19505: failed to identify file "D:\ORACLE\BACKUP\TRACKER_20050920_FULL.S148P1"
ORA-27041: unable to open file
ORA-04002: unable to open file
O/S-Error: (OS 21) device not readyAfter made whole backup of primary db to drive C on host A,
and redo step 2 and step 3.
The error messages as the same as step 3.
There's my backup script:
RMAN>run
RMAN>{
RMAN> shutdown immediate;
RMAN> startup mount;
RMAN> ALLOCATE CHANNEL bck2disk1 DEVICE TYPE DISK;
RMAN> BACKUP DATABASE FORMAT 'C:\oracle\backup\%d_%T_Full.S%sP%p';
RMAN> sql "alter database open";
RMAN> Release Channel bck2disk1;
RMAN>}Thanks a lot
Charlie -
RMAN Script & RMAN Configuration
Dear All,
This is the first time i am using RMAN. i just wanted to execute the following RMAN script for a testing purpose, for this what are the RMAN configuration i must have to do before executing this script below:
RMAN> run {
shutdown immediate;
startup mount;
backup database;
alter database open;
}This is my current setup of RMAN
RMAN> show all;
RMAN configuration parameters for database with db_unique_name DP 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 'E:\RMAN\';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'E:\APP\10004\PRODUCT\11.2.0\DBHOME_1\DATABASE\SNCFDP.ORA'; # defaultKindly advice me and give me a very clear study for this above parameters
Regards
HAMEED
Once i execute that script i got this following error :
+RMAN> run {+
+2> shutdown immediate;+
+3> startup mount;+
+4> backup database;+
+5> alter database open;+
+6> };+
database closed
database dismounted
Oracle instance shut down
connected to target database (not started)
Oracle instance started
database mounted
Total System Global Area 770019328 bytes
Fixed Size 1374780 bytes
Variable Size 301991364 bytes
Database Buffers 461373440 bytes
Redo Buffers 5279744 bytes
Starting backup at 18-MAY-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=134 device type=DISK
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00006 name=E:\APP\10004\ORADATA\DP\HAMEED01.DBF
input datafile file number=00007 name=E:\APP\10004\ORADATA\DP\ABDUL01.DBF
input datafile file number=00008 name=E:\APP\10004\ORADATA\DP\TEST01.DBF
input datafile file number=00001 name=E:\APP\10004\ORADATA\DP\SYSTEM01.DBF
input datafile file number=00002 name=E:\APP\10004\ORADATA\DP\SYSAUX01.DBF
input datafile file number=00005 name=E:\APP\10004\ORADATA\DP\EXAMPLE01.DBF
input datafile file number=00003 name=E:\APP\10004\ORADATA\DP\UNDOTBS01.DBF
input datafile file number=00004 name=E:\APP\10004\ORADATA\DP\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 18-MAY-11
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 05/18/2011 17:22:30
ORA-19504: failed to create file "E:\RMAN\"
ORA-27038: created file already exists
OSD-04010: <create> option specified, file already exists
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
Edited by: Hameed on May 18, 2011 4:59 AMDear Chinar, can you please varify this below ,, is it correct,, after given your setup i ran this script,,,
Kindly advice me
Regards
HAMEED
RMAN> run
2> {
3> backup current controlfile;
4> }
Starting backup at 18-MAY-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=143 device type=DISK
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
channel ORA_DISK_1: starting piece 1 at 18-MAY-11
channel ORA_DISK_1: finished piece 1 at 18-MAY-11
piece handle=E:\RMAN\FULL_06MCLH66_1_1.BK tag=TAG20110518T180910 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 18-MAY-11
Starting Control File Autobackup at 18-MAY-11
piece handle=E:\RMAN\CFC-796596855-20110518-00 comment=NONE
Finished Control File Autobackup at 18-MAY-11Edited by: Hameed on May 18, 2011 5:55 AM -
Blockrecover but full datafile restore + ORA-01193
Hi,
We have a proplem, here is a short sescription:
We have corrupt blocks, how can we solve this problem? Blockrecover uses full datafile restore and finally fails with ORA-01193.
Here is a detailed description:
We have a 330GB datafile (bigfile tablespace) with 46 corrupt block.
DB version 10.2.0.4, Oracle linux, we use ASM.
We would repair these blocks.
V$DATABASE_BLOCK_CORRUPTION after "backup validate check logical datafile 7" :
FILE# BLOCK# BLOCKS CORRUPTION_CHANGE# CORRUPTION_TYPE
7 16872378 1 0 FRACTURED
7 16872408 40 0 CORRUPT
7 16872379 5 0 CORRUPT
The result is similar by dbv.
We have archivelog mode and backupset created by rman command:
backup as compressed backupset incremental level 0 database;
All of the corrupted blocks are in 1 LOB segment.
We copied the LOB segment, only 5 record cannot be read.
The corrupted LOB segment (and table) was exchanged by the copied (not corrupted) data, so users can work.
We remained the corrupted LOB segment in the database, but it is not in use.
I started blockrecovery by command:
BLOCKRECOVER DATAFILE 7 BLOCK 16872378,...,16872447;
The listed blocks are same as in the V$DATABASE_BLOCK_CORRUPTION, so the command could be:
BLOCKRECOVER CORRUPTION LIST;
The database was opened during blockrecocer and the datafile 7 was online.
A line appeared in the V$SESSION_LONGOPS with:
"RMAN: full datafile restore"
The restore was more than 4 hours, and finally it is failed with error:
Starting blockrecover at 29-AUG-12
starting media recovery
ORA-01193 file % is not the same file seen at start of recovery
Based on V$SESSTAT there were lot of physical read but only some physical write.
Maybe full datafile read, and only corrupted blocks was changed, but I didn't check it exactly.
We retried blockrecover with only one block, but the result was same: it failed after 4 hours with ORA-01193.
We retried the blockrecovery on a mounted but not opened database, and the datafile was offline:
SHUTDOWN IMMEDIATE;
STARTUP MOUNT;
ALTER DATABASE DATAFILE 7 offline
BLOCKRECOVER ...
The result was same: it failed after 4 hours with ORA-01193.
rman backup failed with error:
RMAN : ORA-19566: exceeded limit of 0 corrupt blocks for file %
After set maxcorrupt, rman backup ran successfuly
SET MAXCORRUPT FOR DATAFILE 7 TO 46;
Based on our current info, these workaround seems best for us:
- rman "set maxcorrupt"
- DB_BLOCK_CHECKING=FULL
- drop corrupted (but copied and not used segment)
- wait until corrupted blocks will be reallocated (checking it periodically by dbv)
- set maxcorrupt to 0
Our questions are:
*1. Why oracle uses "RMAN: full datafile restore" during blockrecover?*
Why needed to read the whole datafile?
One of the advantage of blockrecover should be the relative small IO, and fast restore.
I found only 2 results in google for "blockrecover" and "RMAN: full datafile restore".
(One of the findings was in this forum, but it was no answer for our problem)
*2. ORA-01193: file is not the same, but why?*
It is strange on opened database and online datafile, because other advantage of blockrecover should be the online recovery.
But it is more-more strange on closed(mounted) database and offline datafile. Only the rman blockrecover could change this file.
I found only 3 results in google for "blockrecover" "ORA-01193"
I found only the oerr output in google for "ORA-01193". But what does it mean? Only the rman blockrecover could change this file.
Cause: A different copy of the file was accessed the last time media recovery looked at the file header. A backup of the file was restored or the meaning of the file name changed during recovery.
Action: Ensure the correct file is available, then retry recovery.
*3. What else can be do to repair these corrupt blocks? What can we do for success blockrecover, or is there any other idea?*
Other infos:
- DB_BLOCK_CHECKING was false, but we changed it to FULL to avoid the subsequent corruptions
ALTER SYSTEM SET DB_BLOCK_CHECKING = FULL scope=both
- DBMS_REPAIR cannot detect the (out-of-line) LOB segment errors.
- rman SET MAXCORRUPT is not a "calming" solution
- When I read on internet, when we drop the corrupted LOB segments, the blocks will remains corrupt.
And the block will be repaired/formatted only when a new segment will allocate these blocks.
Based on metalink 336133.1, we can ensure the new allocation by fill the datafile with dummy data until the corrupted blocks will be allocated.
But this is a very IO intensive task.
- full recovery
very IO intensive, we try to avoid it.
Thx: lados.Hi,
other infos:
We use ASM, and one of the disk is dropped and added after the last full (incremental level 0) backup. Can this premise causes the slow restore (something physical storage info is changed), or the ORA-01193 error (file % is not the same file seen at start of recovery) ? I don't think that a full db backup is needed after ASM disk drop/add/rebalance. But we tried a full backup (this was when the corrupt block first appeared with ORA-19566).
I found only one finding in the metalink for ORA-01193. The oerr reference (cause,action). It would be strange, if nobady else had problem with this error.
Thx: lados. -
RMan Error message Please Help
Hi
I have been trying to register a database in RMAN . Here are the steps I took on OS linux Mandrake 8.1 using ORACLE version 9.2.0.1.0
SQL:
CONNECT sys/password@ora AS SYSDBA
CREATE TABLESPACE "RMAN"
DATAFILE 'C:\ORACLE\ORADATA\W2K1\RMAN01.DBF' SIZE 6208K REUSE
AUTOEXTEND ON NEXT 64K MAXSIZE 32767M
EXTENT MANAGEMENT LOCAL
SEGMENT SPACE MANAGEMENT AUTO;
CREATE USER rman IDENTIFIED BY rman
TEMPORARY TABLESPACE temp
DEFAULT TABLESPACE rman
QUOTA UNLIMITED ON rman;
GRANT connect, resource, recovery_catalog_owner TO rman;
rman catalog=rman/rman@ora
Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to recovery catalog database
recovery catalog is not installed
RMAN> create catalog tablespace "RMAN";
recovery catalog created
RMAN> exit
Recovery Manager complete.
rman catalog=rman/rman@ora target=sys/password@w2k2
Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: ora (DBID=1371963417)
connected to recovery catalog database
RMAN> register database;
This is returning the error message
RMAN-00571:
RMAN-00569:
RMAN-00571:
RMAN-03002:failure of register command at 07/16/03 12:56
RMAN-03014:implicit resyncof recovery catalog failed
RMAN-03009:failure of full resync command on default channel at 07/16/03
ORA01001- cursor not valideHi,
First of all I would not use RMAN as a tablespace name. It may be confusing oracle and besides it maybe a reserved term not available for use and a cause for some of those errors listed.
But here is what is in my notes that work.
After the database is created named RCAT you must create the user RMAN. It is then after he is created the program will run.
Create user RMAN
SQL> CREATE TABLESPACE CATTBS
'D/ORACLE/ORADATA/RECAT' SIZE 5M
AUTOEXTEND ON;
CREATE USER RMAN IDENTIFIED BY RMANTEMPORARY TABLESPACE TEMP
DEFAULT TABLESPACE CATTBS
QUOTA UNLIMITED ON CATTBS;
After the user has been created you need to grant some permissions for him to use.
GRANT RECOVERY_CATALOG_OWNER TO RMAN;
COMMIT;
GRANT CONNECT,RESOURCE TO RMAN;Now you need to create the RECOVERY CATALOG
Go to the host operating system oracle/ora81/bin/RMAN.EXE and execute this script the following prompt shows up.
RMAN>
You now need to create the CATALOG in tablespace CATTBS.
RMAN>CREATE CATALOG TABLESPACE CATTBS;
responds with
RMAN>RECOVERY CATALOG CREATED
Now you need to run these two scripts CATALOG.SQL AND CATPROC.SQL
RMAN>@D:\ORACLE\ORA81\RDBMS\ADMIN\CATALOG.SQL
\CATPROC.SQL
Running these two scripts now allows you to view the recovery catalog views.
This completes the setup of the recovery catalog database.
Now connect to your target
RMAN> connect target internal/oracle@ora
RMAN> connect RCVCAT rman/rman@rcat
Give the command to register database:
RMAN>register database
it responds with
RMAN>database registered in recovery catalog
You need to connect to the RCAT database with the following command:
RMAN>CONNECT CATALOG RMAN/RMAN@RCAT;
Hope this format helps.
Al -
Register Database error in Rman
Hi
I have been trying to register a database in RMAN . Here are the steps I took on OS linux Mandrake 8.1 using ORACLE version 9.2.0.1.0
SQL:
CONNECT sys/password@ora AS SYSDBA
CREATE TABLESPACE "RMAN"
DATAFILE 'C:\ORACLE\ORADATA\W2K1\RMAN01.DBF' SIZE 6208K REUSE
AUTOEXTEND ON NEXT 64K MAXSIZE 32767M
EXTENT MANAGEMENT LOCAL
SEGMENT SPACE MANAGEMENT AUTO;
CREATE USER rman IDENTIFIED BY rman
TEMPORARY TABLESPACE temp
DEFAULT TABLESPACE rman
QUOTA UNLIMITED ON rman;
GRANT connect, resource, recovery_catalog_owner TO rman;
rman catalog=rman/rman@ora
Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to recovery catalog database
recovery catalog is not installed
RMAN> create catalog tablespace "RMAN";
recovery catalog created
RMAN> exit
Recovery Manager complete.
rman catalog=rman/rman@ora target=sys/password@w2k2
Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: ora (DBID=1371963417)
connected to recovery catalog database
RMAN> register database;
This is returning the error message
RMAN-00571:
RMAN-00569:
RMAN-00571:
RMAN-03002:failure of register command at 07/16/03 12:56
RMAN-03014:implicit resyncof recovery catalog failed
RMAN-03009:failure of full resync command on default channel at 07/16/03
ORA01001- cursor not valideHi,
Change the name of your tablespace RMAN to CATTBS. I believe RMAN is a reserved word in oracle.
Maybe you are looking for
-
Error in local system;message is not complete--- in Solman 4.0
Hello Solman Gurus, After importing SP 13 in Solution Manager 4.0 , whenever i am trying from help--> create support message ; i am getting "ERROR IN LOCAL SYSTEM; MESSAGE <MSG NO> IS NOT COMPLETE " i have seen these threads ERROR when Tryin
-
... i seriousy can´t find the purchased songs on my Mac, and i live in a country where they´re not allowing me to download earlier purchased songs.
-
I'm using SQL Server Express 2014 and I need to test some queries prior to using them in a full version (I've not decided which to move over to yet). I have a table with an inventory of virtual machines and I need to list the count of them per cluste
-
How about a 'Text Layout Framwork' category on Adobe Labs Ideas in the Flex SDK section?
I like 'Adobe Labs Ideas', it's far more accessible/inviting then "Adobe Bugs and Issues" (JIRA). Therefor I would like to suggest a new category 'Text Layout Framework' under the Flex SDK section or even it's own section (after all TLF isn't Flex on
-
How to use GROUP BY in this Query
The below query has TRUNC funtion and I don't want the NMR field to put in group by, but it should be in select. Please help SELECT H.SAM_ATTUID AS ATTUID1, B.AGENT_ID, TRUNC (NVL (FORC_ANNREV_PAID, CALC_ANNREV_PAID) / 12, 2) AS NMR, PRODUCT_GROUP FR