使用dg迁移32位oracle到64位oracle

最新推荐文章于 2024-04-14 19:35:05 发布

久违的太阳

最新推荐文章于 2024-04-14 19:35:05 发布

阅读量938

点赞数

分类专栏： oracle dataguard

oracle dataguard 专栏收录该内容

17 篇文章 0 订阅

订阅专栏

跳至内容

可访问性首选项

面板

知识

服务请求

补丁程序和更新程序

社区

认证

系统

收集器

高级客户服务

设置

全局搜索

提供反馈...

Role Transitions for Data Guard Configurations Using Mixed Oracle Binaries (文档 ID 414043.1)

转到底部

APPLIES TO:

Oracle Database - Enterprise Edition - Version 9.0.1.0 to 12.1.0.2 [Release 9.0.1 to 12.1]
Information in this document applies to any platform.

PURPOSE

***Checked for relevance on 8-Jul-2015***

***Checked for relevance on 26-Oct-2016***?

Recompile packages in a database after a Data Guard role transition in a mixed Oracle Binaries Data Guard configuration.

DETAILS

Summary

Beginning with Oracle Database 10g, there are certain configurations where Data Guard Redo Apply (physical standby) can support different Oracle binaries between primary and standby databases as long as all systems in the Data Guard configuration are running the same OS family. For example, you may have a primary database with 32bit Oracle binaries on Red Hat 32bit, and a physical standby database with 64bit Oracle binaries on Red Hat 64bit.

Note: The Oracle RDBMS software version must be the same as per normal Data Guard requirements.

Such configurations must follow additional procedures during Data Guard role transitions (switchover and failover) as described in this note, below. If these procedures are not followed then errors will occur when trying to open the new primary database. One example error sequence would be:

ORA-00604: error occurred at recursive SQL level 1
 ORA-06553: PLS-801: internal error [56327]
<>
 \

For additional information on how Data Guard supports configurations in which the primary database/system may not be identical to its standby database(s)/system(s), please see Note 413484.1

Restrictions

SQL Apply (logical standby) always requires that the bit-ness of the Oracle Database is identical on all systems in a Data Guard configuration. Continuing with the example provided in the summary above of a Red Hat 32bit/64bit primary/standby, if you are using SQL Apply you must use 32 bit Oracle binaries on both primary and standby.The bit-ness of the Oracle database must be identical if you are using any Oracle release before Oracle Database 10g for both SQL Apply and Redo Apply. Continuing with the example provided in the summary above of a Red Hat 32bit/64bit primary/standby, if you are using Oracle9i you must use 32 bit Oracle binaries on both primary and standby (either physical or logical standby).

The Data Guard Broker does not support different binaries in the same Data Guard configuration in Oracle Database 10g. All such configurations must be managed from the SQL*Plus command line. Beginning with Data Guard 11g onward, this restriction is lifted and the Data Guard Broker does support Oracle 11g databases of mixed word-size in the same Data Guard configuration. Data Guard Fast-start Failover will failover in a mixed Oracle binary configuration but it will be unable to open the new primary database until the procedure below is followed.

Additional Role Transition Procedures when using mixed Oracle binaries

If you are running a physical standby configuration where the primary and standby have different Oracle binaries you will need to follow the instructions below on the new primary as part of any Data Guard role transition (switchover or failover) after a standby becomes a primary database (supported configurations are defined in MetaLink Note 413484.1). This procedure is necessary when transitioning roles in either direction.

Note: If you are using Oracle OLAP then you must also follow Note 352306.1 . Additionally, as a precaution for a failover, you may want to backup/export the user-created AW's ahead of time and periodically.

1. Shutdown the new primary database (If using RAC then set database to unclustered)

SQL> alter system set cluster_database=false scope=spfile;
 SQL> shutdown immediate

2. Startup the new primary in UPGRADE mode

                                             SQL> startup upgrade 
                                           

3. Invalidate existing PL/SQL modules in preparation to convert the format required by the new primary. Note that there should be no other DDL on the database while running the script. Not following this recommendation may lead to deadlocks.

                                             SQL> spool utlirp.log 
                                            
 SQL> @?/rdbms/admin/utlirp 
                                            
 SQL> spool off

4. Restart the database (If using RAC then set database back to clustered)

                                             SQL> alter system set cluster_database=true scope=spfile; 
                                            
 SQL> shutdown immediate 
                                            
 SQL> startup

5. Recompile all invalid PL/SQL modules to be in the format required by the new primary database.

                                             SQL> spool utlrp.log 
                                            
 SQL> @?/rdbms/admin/utlrp 
                                            
 SQL> spool off

6. Verify that all expected packages and classes are valid.

                                             SQL> SELECT count(*) FROM dba_objects WHERE status='INVALID'; 
                                            
 SQL> SELECT distinct object_name FROM dba_objects WHERE status='INVALID';