主服务器系统 solaris 9 sparc
备份服务器系统 solaris 10 x86_64
oracle 10g 10.2.0.1
对主服务器rman备份后到备份服务器恢复
在对主服务器
alter database create standby controlfile as /data/standby.ctl;
然后复制standby.ctl 到备份服务器controlfile对应的位置,并且改名成control01.ctl ...
对备份服务器做
create spfile from pfile;
startup nomount;
当执行
alter database mount standby database;
时,数据库报错:
ORA-00205: error in identifying control file, check alert log for more info
查看日志:
alter database mount standby database
Tue Nov 20 10:57:36 2007
ORA-00202: control file: /data/oradata/grad/control01.ctl
ORA-27047: unable to read the header block of file
Additional information: 2
Tue Nov 20 10:57:39 2007
ORA-205 signalled during: alter database mount standby database...
SQL> select platform_name,endian_format from V$TRANSPORTABLE_PLATFORM
2where platform_name like 'Solaris%';
PLATFORM_NAME
--------------------------------------------------------------------------------
ENDIAN_FORMAT
--------------
Solaris[tm] OE (32-bit)
Big
Solaris[tm] OE (64-bit)
Big
Solaris Operating System (x86)
Little复制代码
应该是这个原因吧
The hardware and operating system architecture on the primary and standby
locations must be the same. For example, this means a Data Guard
configuration with a primary database on a 32-bit Sun system must have a
standby database that is configured on a 32-bit Sun system. Similarly, a primary
database on a 64-bit HP-UX system must be configured with a standby database
on a 64-bit HP-UX system, and a primary database on a 32-bit Linux on Intel
system must be configured with a standby database on a 32-bit Linux on Intel
system, and so forth.