Is it difficult to transition (migrate) from Single Instance to Oracle RAC?
must be installed and configured. The Oracle RAC option must be added using
the Oracle Universal Installer, which necessitates the existing DB instance
must be shut down. There are no changes necessary on the user data within
the database. However, a shortage of freelists and freelist groups can
causecontention with header blocks of tables and indexes as multiple
instances vie for the same block. This may cause a performance problem and
require data partitioning. However, the need for these changes should be
rare.
Recommendation: apply automatic space segment management to perform these
changes automatically. The free space management will replace the freelists
and freelist groups and is better. The database requires one Redo thread
and one Undo tablespace for each instance, which are easily added with SQL
commands or with Enterprise Manager tools. NOTE: With ORacle RAC 11g Release
2, you do not neet to pre-create redo threads or undo tablespaces if you are
using Oracle Managed Files (EG ASM).
Datafiles will need to be moved to either a clustered file system (CFS) so
that all nodes can access them. Oracle recommends the use of Automatic Storage
Management (ASM) Also, the MAXINSTANCES parameter in the control file must be
greater than or equal to number of instances you will start in the cluster.
For more detailed information, please see Migrating from single-instance to RAC
in the Oracle Documentation.
With Oracle Database 10g Release 2, $ORACLE_HOME/bin/rconfig tool can be used to
convert Single instance database to RAC. This tool takes in a xml input file
and convert the Single Instance database whose information is provided in the
xml. You can run this tool in "verify only" mode prior to performing actual
conversion. This is documented in the Oracle RAC Admin book and a sample xml
can be found $ORACLE_HOME/assistants/rconfig/sampleXMLs/ConvertToRAC.xml. This
tool only supports databases using a clustered file system or ASM. You cannot
use it with raw devices. Grid Control 10g Release 2 provides a easy to use
wizard to perform this function.
@ Note: Please be aware that you may hit bug: 4456047 (shutdown immediate hangs)
as you convert
@ the database. The bug is updated with workaround and the w/a should is release
noted as well.
Oracle Enterprise Manager includes workflows to assiste with migrations. (I.E.
Migrating to ASM, Creating Standby, Converting Standby to RAC etc) The migration
is automated in Enterprise Manager Grid Control 10.2.0.5.
将单实例数据库转换成rac困难么
RAC选项添加进来。用户数据中的数据没有必要做什么更改。然而,freelist和freelist
group的短缺会导致多个实例中的表或者索引通过块头访问相同块时的争用问题。这可能会产
生性能问题以及需要数据分区,不过这种需求应该是很少见的
建议:使用自动空间管理来管理这些改变。空闲空间管理能够替代free lists和freelist
group 并且更好。每个数据库实例需要一个redo线程和一个还原表空间,(在自动空间管理的
模式下)这些可以很容易的通过sql命令或者em来添加。在11gR2版本如果你使用omf管理数据文
件的话就不需要先创建一个undo线程和还原表空间
数据文件或者需要移动到集群文件系统(CFS),这样所有节点都能访问。Oracle建议使用ASM,
而且控制文件中最大实例数参数必须 不小于你要配置的节点数目。
更多信息参照移动单实例数据库到rac的文章
对于10gR2的版本,$ORACLE_HOME/bin/下的reconfig 工具可以用来转换单一数据库为RAC。这
个工具使用一个提供配置信息的xml作为输入文件来转换。你可以先运行这个工具使用verify
only模式来检测转换问题。这个工具只支持使用ASM或者CFS的数据库,不能使用裸设备。10gR2
版本的网格控制提供了更加易于使用的向导来实现这个功能。
Oracle em包含工作流来帮助迁移。像迁移到asm,创建备库,转换备库为rac这些迁移在
10.2.0.5的企业管理器网格控制是自动实现的。