记一次oracle10g异机恢复故障

今天在做ngods数据库异机恢复时，执行restore database，报如下错误:

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 08/30/2018 16:27:47
ORA-01861: literal does not match format string

给原厂工程师提了SR，经过原厂分析:

1.是因为oracle数据库使用的裸设备，裸设备的头8个字节不为空，oracle数据库在恢复时需要检查裸设备前8个字节时报错，导致恢复失败。

通过dd命令，将oracle使用的所有裸设备的前8个字节设置为空。如下：

dd if=/dev/zero of='/dev/prmvg03/prmvg03_16_041'    bs=8k count=8 conv=notrunc

2.关于此次故障的oracle官方SR回复:

尊敬的客户：  因为raw device的文件头有些无意义的信息，导致oracle认为文件头有信息，但是格式错误，因此报错。  请参考以下bug的说明，注意，该bug最后关为not a bug  Bug 5873368 : RMAN RESTORE FAILED WITH ORA-1861 WHEN SET UNTIL TIME IS USED  When you use raw devices then it is always a good idea  to ensure that the content is zeroed out before using  the file/s with Oracle.   On a source DB:  when you CREATE a tablespace the file (raw device)  gets opened and a new header and content written  to it from scratch.   On another machine:  when restoring you have a controlfile telling you  the raw device/s are already part of the DB  but if these have never been zeroed they could  contain anything.  We should probably be able to handle nonsense in   a header like this better but it is good practice  to always zero out such devices if using them for  the first time then whatever the previous content  it cannot interfere with the new use.