11201 PHYSICAL STANDBY rolling upgrade 11203

最新推荐文章于 2022-08-31 14:28:54 发布
最新推荐文章于 2022-08-31 14:28:54 发布
阅读量1.1k 收藏
点赞数
分类专栏： oracle 文章标签： table database oracle server thread sql
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/aaaaaaaa2000/article/details/7520619
版权

测试使用11的新特性将数据库从11201升级到11203

1、备库上安装11203的软件，使用silent方式安装

2、将备库上的密码文件，参数文件，监听文件等，cp到新路径下
[oracle@oracle11g-std dbs]$ cp spfileora11.ora snapcf_ora11.f orapwora11 initora11.ora hc_ora11.dat /home/oracle/app/product/11.2.0.3/dbs/
[oracle@oracle11g-std admin]$ cp  listener.ora tnsnames.ora /home/oracle/app/product/11.2.0.3/network/admin/

3、主库打开flashback功能
做这一步的主要作用是：因为建立日志字典表的时候需要打开flashback功能
SQL> select DATABASE_ROLE from v$database;


DATABASE_ROLE
----------------
PRIMARY


SQL> select FLASHBACK_ON from v$database;


FLASHBACK_ON
------------------
NO


SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.


Total System Global Area  304807936 bytes
Fixed Size                  2212856 bytes
Variable Size             184552456 bytes
Database Buffers          113246208 bytes
Redo Buffers                4796416 bytes
Database mounted.
SQL> ALTER DATABASE FLASHBACK ON;

/* 同时创建保证还原点以保证升级失败时可以回退 */

SQL> create restore point pre_rolling_upgrd guarantee flashback database;

下面就是讲物理库转化为逻辑库：

取消物理库的日志应用
SQL> alter database recover managed  standby database cancel;


Database altered.
备库的日志输出
ORA-16037: user requested cancel of managed recovery operation
MRP0: Background Media Recovery process shutdown (ora11)
Waiting for MRP0 pid 1897 to terminate
Managed Standby Recovery Canceled (ora11)
Completed: alter database recover managed  standby database cancel

SQL> shut immediate
ORA-01109: database not open




Database dismounted.
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.


Total System Global Area  304807936 bytes
Fixed Size                  2212856 bytes
Variable Size             134220808 bytes
Database Buffers          163577856 bytes
Redo Buffers                4796416 bytes
Database mounted.

需要在Primary Database中创建Logminer dictionary日志挖掘字典：

SQL>  EXECUTE DBMS_LOGSTDBY.BUILD;


PL/SQL procedure successfully completed.


接下来就是讲物理库转化为逻辑库：
SQL> alter database recover managed standby database cancel;


Database altered.

SQL> ALTER DATABASE RECOVER TO LOGICAL STANDBY KEEP IDENTITY;


Database altered.


SQL> 
注意在进行转化的时候必须关闭日志应用，否则会报错



SQL> select database_role from v$database;


DATABASE_ROLE
----------------
LOGICAL STANDBY 

禁止在逻辑备库端删除外籍日志

SQL> EXECUTE DBMS_LOGSTDBY.APPLY_SET('LOG_AUTO_DELETE', 'FALSE');
BEGIN DBMS_LOGSTDBY.APPLY_SET('LOG_AUTO_DELETE', 'FALSE'); END;


      *
ERROR at line 1:
ORA-06550: line 1, column 7:
PLS-00201: identifier 'DBMS_LOGSTDBY.APPLY_SET' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored




SQL>  @?/rdbms/admin/dbmslsby.sql
CREATE OR REPLACE PACKAGE sys.dbms_logstdby AUTHID CURRENT_USER IS
*
ERROR at line 1:
ORA-01109: database not open

禁止删除日志的时候报：dbms包没有，创建的时候说数据库没有打开，接下来就打开数据库

SQL> alter database open;


Database altered.



SQL> @?/rdbms/admin/dbmslsby.sql


Package created.


No errors.


Synonym created.




PL/SQL procedure successfully completed.




Grant succeeded.


CREATE ROLE logstdby_administrator
            *
ERROR at line 1:
ORA-01921: role name 'LOGSTDBY_ADMINISTRATOR' conflicts with another user or
role name






Grant succeeded.




Grant succeeded.




Grant succeeded.




Library created.

SQL>  EXECUTE DBMS_LOGSTDBY.APPLY_SET('LOG_AUTO_DELETE', 'FALSE');


PL/SQL procedure successfully completed. 



执行以下语句可以将逻辑备库不支持的而又在主库上运行过的事务记录到DBA_LOGSTDBY_EVENTS中

SQL> EXECUTE DBMS_LOGSTDBY.APPLY_SET('MAX_EVENTS_RECORDED',DBMS_LOGSTDBY.MAX_EVENTS);


PL/SQL procedure successfully completed. 

启动在逻辑备库上的SQL APPLY:

以下是输出日志
Thread 1 advanced to log sequence 4 (LGWR switch)
  Current log# 1 seq# 4 mem# 0: /home/oracle/app/oradata/ora11/redo01.log
Wed May 02 00:01:29 2012
Archived Log entry 25 added for thread 1 sequence 3 ID 0x2b47d37c dest 1:
Wed May 02 00:01:36 2012
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TAB$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TS$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_OBJ$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_IND$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_ICOL$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_COL$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_USER$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_CDEF$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_CCOL$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_LOB$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_PROPS$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_ENC$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_COLTYPE$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_SUBCOLTYPE$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_ATTRCOL$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TYPE$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_ATTRIBUTE$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_NTAB$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_REFCON$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_OPQTYPE$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_KOPM$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_PARTOBJ$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TABPART$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_INDPART$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TABSUBPART$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_INDSUBPART$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TABCOMPART$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_INDCOMPART$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_LOBFRAG$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_LOGMNR_BUILDLOG have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_SEED$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_DICTIONARY$ have been marked unusable
Indexes of table  SYSTEM.LOGMNR_ATTRCOL$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_ATTRIBUTE$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_CCOL$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_CDEF$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_COL$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_COLTYPE$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_DICTIONARY$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_ENC$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_ICOL$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_IND$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_INDCOMPART$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_INDPART$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_INDSUBPART$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_KOPM$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_LOB$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_LOBFRAG$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_LOGMNR_BUILDLOG have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_NTAB$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_OBJ$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_OPQTYPE$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_PARTOBJ$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_PROPS$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_REFCON$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_SEED$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_SUBCOLTYPE$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_TAB$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_TABCOMPART$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_TABPART$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_TABSUBPART$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_TS$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_TYPE$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_USER$ have been rebuilt and are now usable
Wed May 02 00:02:11 2012
Thread 1 advanced to log sequence 5 (LGWR switch)
  Current log# 2 seq# 5 mem# 0: /home/oracle/app/oradata/ora11/redo02.log
Wed May 02 00:02:13 2012
Archived Log entry 26 added for thread 1 sequence 4 ID 0x2b47d37c dest 1:
Wed May 02 00:02:42 2012
LOGMINER: End mining logfiles during dictionary load for session 1
Wed May 02 00:02:45 2012
LSP2 started with pid=38, OS id=2229 
Wed May 02 00:02:51 2012
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 91, /home/oracle/archivelog/1_91_781653794.dbf
Wed May 02 00:02:54 2012
LOGSTDBY Analyzer process AS00 started with server id=0 pid=39 OS id=2231
Wed May 02 00:02:55 2012
Wed May 02 00:02:55 2012
LOGSTDBY Apply process AS01 started with server id=1 pid=40 OS id=2233
Wed May 02 00:02:55 2012
LOGSTDBY Apply process AS02 started with server id=2 pid=41 OS id=2235
LOGSTDBY Apply process AS03 started with server id=3 pid=42 OS id=2237
Wed May 02 00:02:55 2012
LOGSTDBY Apply process AS05 started with server id=5 pid=44 OS id=2241
Wed May 02 00:02:55 2012
LOGSTDBY Apply process AS04 started with server id=4 pid=43 OS id=2239
Wed May 02 00:03:13 2012
LOGMINER: End   mining logfile for session 1 thread 1 sequence 91, /home/oracle/archivelog/1_91_781653794.dbf
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 92, /home/oracle/archivelog/1_92_781653794.dbf
LOGMINER: End   mining logfile for session 1 thread 1 sequence 92, /home/oracle/archivelog/1_92_781653794.dbf
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 93, /home/oracle/archivelog/1_93_781653794.dbf
LOGMINER: End   mining logfile for session 1 thread 1 sequence 93, /home/oracle/archivelog/1_93_781653794.dbf
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 94, /home/oracle/archivelog/1_94_781653794.dbf
LOGMINER: End   mining logfile for session 1 thread 1 sequence 94, /home/oracle/archivelog/1_94_781653794.dbf

接下来进行升级：

停止日志应用

SQL> ALTER DATABASE STOP LOGICAL STANDBY APPLY;


Database altered.

将原监听，密码文件、参数文件、spfile文件拷贝到相应的目录下，修改oracle用户的bash_profile文件
SQL> startup upgrade;
ORACLE instance started.


Total System Global Area  304807936 bytes
Fixed Size                  2227864 bytes
Variable Size             134218088 bytes
Database Buffers          163577856 bytes
Redo Buffers                4784128 bytes
Database mounted.
Database opened. 
@?/rdbms/admin/catupgrd

进行数据字典升级

升级完成之后脚本会自动down数据库
此时重启数据库
[oracle@oracle11g-std ~]$ sqlplus '/as sysdba'


SQL*Plus: Release 11.2.0.3.0 Production on Wed May 2 04:13:02 2012


Copyright (c) 1982, 2011, Oracle.  All rights reserved.


Connected to an idle instance.


SQL> startup
ORACLE instance started.


Total System Global Area  304807936 bytes
Fixed Size                  2227864 bytes
Variable Size             264241512 bytes
Database Buffers           33554432 bytes
Redo Buffers                4784128 bytes
Database mounted.
Database opened.
SQL> 

cd /home/oracle/app/product/11.2.0.3/rdbms/admin/

SQL>@utlu112s.sql

SQL>@catuppst.sql

编译各组件----耗时比较长，接近1个小时
SQL> @utlrp.sql


TIMESTAMP
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
COMP_TIMESTAMP UTLRP_BGN  2012-05-02 04:17:44


DOC>   The following PL/SQL block invokes UTL_RECOMP to recompile invalid
DOC>   objects in the database. Recompilation time is proportional to the
DOC>   number of invalid objects in the database, so this command may take
DOC>   a long time to execute on a database with a large number of invalid
DOC>   objects.
DOC>
DOC>   Use the following queries to track recompilation progress:
DOC>
DOC>   1. Query returning the number of invalid objects remaining. This
DOC>      number should decrease with time.
DOC>         SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
DOC>
DOC>   2. Query returning the number of objects compiled so far. This number
DOC>      should increase with time.
DOC>         SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;
DOC>
DOC>   This script automatically chooses serial or parallel recompilation
DOC>   based on the number of CPUs available (parameter cpu_count) multiplied
DOC>   by the number of threads per CPU (parameter parallel_threads_per_cpu).
DOC>   On RAC, this number is added across all RAC nodes.
DOC>
DOC>   UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel
DOC>   recompilation. Jobs are created without instance affinity so that they
DOC>   can migrate across RAC nodes. Use the following queries to verify
DOC>   whether UTL_RECOMP jobs are being created and run correctly:
DOC>
DOC>   1. Query showing jobs created by UTL_RECOMP
DOC>         SELECT job_name FROM dba_scheduler_jobs
DOC>            WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>
DOC>   2. Query showing UTL_RECOMP jobs that are running
DOC>         SELECT job_name FROM dba_scheduler_running_jobs
DOC>            WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>#


PL/SQL procedure successfully completed.




TIMESTAMP
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
COMP_TIMESTAMP UTLRP_END  2012-05-02 04:53:16


DOC> The following query reports the number of objects that have compiled
DOC> with errors (objects that compile with errors have status set to 3 in
DOC> obj$). If the number is higher than expected, please examine the error
DOC> messages reported with each object (using SHOW ERRORS) to see if they
DOC> point to system misconfiguration or resource constraints that must be
DOC> fixed before attempting to recompile these objects.
DOC>#


OBJECTS WITH ERRORS
-------------------
                  0


DOC> The following query reports the number of errors caught during
DOC> recompilation. If this number is non-zero, please query the error
DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors
DOC> are due to misconfiguration or resource constraints that must be
DOC> fixed before objects can compile successfully.
DOC>#


ERRORS DURING RECOMPILATION
---------------------------
                          0




Function created.




PL/SQL procedure successfully completed.




Function dropped.




PL/SQL procedure successfully completed.

查看各组件状态
SQL> col comp_name for a30;
SQL> col namespace for a20;
SQL> col version for a15;
SQL> col status for a10; 
SQL> SELECT COMP_NAME,namespace,VERSION, STATUS FROM SYS.DBA_REGISTRY;


COMP_NAME                      NAMESPACE            VERSION         STATUS
------------------------------ -------------------- --------------- ----------
OWB                            SERVER               11.2.0.1.0      VALID
Oracle Application Express     SERVER               3.2.1.00.10     VALID
Oracle Enterprise Manager      SERVER               11.2.0.3.0      VALID
OLAP Catalog                   SERVER               11.2.0.3.0      INVALID
Spatial                        SERVER               11.2.0.3.0      VALID
Oracle Multimedia              SERVER               11.2.0.3.0      VALID
Oracle XML Database            SERVER               11.2.0.3.0      VALID
Oracle Text                    SERVER               11.2.0.3.0      VALID
Oracle Expression Filter       SERVER               11.2.0.3.0      VALID
Oracle Rules Manager           SERVER               11.2.0.3.0      VALID
Oracle Workspace Manager       SERVER               11.2.0.3.0      VALID


COMP_NAME                      NAMESPACE            VERSION         STATUS
------------------------------ -------------------- --------------- ----------
Oracle Database Catalog Views  SERVER               11.2.0.3.0      VALID
Oracle Database Packages and T SERVER               11.2.0.3.0      VALID
总计一下升级步骤：
1、安装新的db
2、将物理库切换成逻辑库
3、修改用户的环境变量
4、startup upgrade
5、运行@$ORACLE_HOME/rdbms/admin/utlu112i.sql----显示各组件状态以及升级各组件大约消耗的时间
6、运行真正的升级脚本@$ORACLE_HOME/rdbms/admin/catupgrd.sql
7、运行数据库检查脚本:@$ORACLE_HOME/rdbms/admin/utlu112i.sql:改脚本是检查没有升级之前各组件的状态
8、运行@$ORACLE_HOME/rdbms/admin/utlrp.sql---为了保证数据字典的有效性和完整性，在运行完升级脚本后，建议运行该脚本，编译剩余存储的PL/SQL和JAVA代码
9、运行@$ORACLE_HOME/rdbms/admin/catuppst.sql---定位ORACLE_HOME/rdbms/admin目录用的，不需要进入upgrade模式了。所以直接运行。
/utlu112i.sql----脚本说明：
The Post-Upgrade Status Tool, which is the utlu112s.sql script, displays the status of the database components in the upgraded database and the time required to complete each component upgrade. Any errors that occur during the upgrade are listed with each component and must be addressed. The utlu112s.sql script can be run any time after you run catupgrd.sql, but not after running utlrp.sql.
以上就是原物理备库转化为逻辑库并且升级结束
后续就是进行贮备切换，以及原主机进行升级


主库：
SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY;


Database altered.


SQL> 



备库：
SQL> show user;
USER is "SYS"
SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY;


Database altered.


SQL> 

此时的主备库之间已经不能应用日志了，因为低版本的db应用不老高版本的log

接下来就升级原主库：
关闭数据库
SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> 
修改环境变量，加载最新的oracle_home路径

将原主库在新的环境变量的情况下mount起来
[oracle@oracle11 admin]$ sqlplus '/as sysdba'


SQL*Plus: Release 11.2.0.3.0 Production on Wed May 2 19:55:11 2012


Copyright (c) 1982, 2011, Oracle.  All rights reserved.


Connected to an idle instance.


SQL> startup mount;
ORACLE instance started.


Total System Global Area  304807936 bytes
Fixed Size                  2227864 bytes
Variable Size             184549736 bytes
Database Buffers          113246208 bytes
Redo Buffers                4784128 bytes
Database mounted.
SQL> select database_role from v$database;


DATABASE_ROLE
----------------
LOGICAL STANDBY
此时是逻辑库，将逻辑库转化为物理库

SQL> ALTER DATABASE CONVERT TO PHYSICAL STANDBY;


Database altered.

SQL> shut immediate
ORA-01507: database not mounted




ORACLE instance shut down.
SQL> 
SQL> Error 45 initializing SQL*Plus
Internal error
[oracle@oracle11 ~]$ 
启动redo应用
[oracle@oracle11 ~]$ sqlplus '/as sysdba'


SQL*Plus: Release 11.2.0.3.0 Production on Wed May 2 21:52:50 2012


Copyright (c) 1982, 2011, Oracle.  All rights reserved.


Connected to an idle instance.


SQL> startup mount;
ORACLE instance started.


Total System Global Area  304807936 bytes
Fixed Size                  2227864 bytes
Variable Size             184549736 bytes
Database Buffers          113246208 bytes
Redo Buffers                4784128 bytes
Database mounted.
SQL> alter database recover managed standby database using current logfile disconnect from session;


Database altered.


SQL> select database_role from v$database;


DATABASE_ROLE
----------------
PHYSICAL STANDBY

然后进行主备库切换，将新备库再切换成原来的主库


aaaaaaaa2000
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
oracle升级110201-110204
07-17
server2008下oracle11g升级
linux 11201(11203) ASM RAC 安装
weixin_34015336的博客
08-03 109
注意：11G的RAC安装，如果升级，则会新建目录在放软件，原来的不删除，所以所需空间比较大。 1。安装系统，把所有的开发包全部安装上 关掉防火墙和SELinux yum -y install compat-libstdc++*yum -y install elfutils-libelf-devel*yum -y install elfutils-libelf-devel-static*...
oracle版本号升级,oracle版本升级：从11.2.0.1到11.2.0.3
weixin_31600439的博客
04-06 375
oracle版本升级：从11.2.0.1到11.2.0.3不过从11.2.0.2开始 都是全新install，并不升级原有的oracle_home目录，而是选择新的oracle_home进行安装，并升级。standalone升级asm：1、下载补丁包，2、安装grid 到新目录 选择第3项 upgrade (执行rootupgrade.sh 比较慢 半个小时多，还以为hung住了呢)升级 d...
oracle 202,Oracle11201升级到11202.doc
weixin_42560530的博客
04-11 121
Oracle11201升级到11202Oracle 11.2.0.1升级到11.2.0.2从11.2.0.1升级到11.2.0.2Oracle从11.2.0.2开始，Oracle database的补丁集合是完整的安装包，将不再需要安装11.2.0.1版本。所以升级的方式和以前的补丁包不同。11.2.0.2的软件需要安装在一个全新的目录，而不是在原有的11.2.0.1的目录下打补丁。可以选择使用d...
Oracle11201升级到11203示例
rede
03-27 1558
原 Oracle 11.2.0.1 升级到 11.2.0.3 示例https://blog.csdn.net/tianlesoftware/article/details/6833591版权声明： https://blog.csdn.net/tianlesoftware/article/details/6833591 Oracle 11.2.0.1 单实例升级到11.2.0.3。 Oracl...
oracle physical standby配置
03-19
Oracle物理备用库(Physical Standby)配置是在数据库高可用性架构中的一种常见实践，它确保在主数据库出现故障时，可以快速切换到备用数据库继续提供服务。以下是对配置过程的详细解释： 1. **启用Force Logging**：...
Linux 平台 Physical Standby 搭建ADG
01-23
本文档主要介绍如何在Linux平台上搭建ADG环境，以实现Physical Standby（物理备用）数据库。 一、注意事项： 1. 配置上注意：在搭建ADG时，需要确保主库和备库的系统配置一致，包括操作系统版本、Oracle版本、文件...
testzp05_standby_F2812_
09-29
标题“testzp05_standby_F2812_”暗示了这是一个关于F2812微控制器在STANDBY低功耗模式下利用看门狗中断唤醒CPU的测试项目。F2812是TI公司生产的C28x系列浮点数字信号处理器(DSP)，常用于实时控制应用。在这个场景中...
greenplum 集群Master 增加Standby 节点
05-14
"Greenplum 集群 Master 增加 Standby 节点" Greenplum 是一个基于 PostgreSQL 的开源关系数据库管理系统，支持大规模数据处理和分析。Greenplum 集群 Master 节点是整个集群的核心，负责管理和协调整个集群的操作...
DG standby-time 监控脚本
11-09
-- 同步正常 [oracle@standby ~]$ sh check_standbt_time.sh +00 00:00:00 -- 同步异常： [oracle@standby ~]$ sh check_standbt_time.sh 3mi43s
oracle upgrade 版本升级 解决办法
01-09
oracle 冷备到更高级的实例中 upgrade 方法
oracle rac10205升级到11204
11-25
redhat5.7下oracle rac 10.2.0.5.0升级到11.2.0.4.0
oracle版本升级：从11.2.0.1到11.2.0.3
cov98559的博客
02-10 199
oracle版本升级：从11.2.0.1到11.2.0.3不过从11.2.0.2开始 都是全新install，并不升级原有的oracle_home目录，而是选择新的oracle_home进行安装，并升级。standalone升级...
windows oracle升级 11.2.0.3,Oracle升级11.2.0.3-11.2.0.4（Windows）
weixin_35696092的博客
04-04 135
背景：解决11.2.0.3带来的ora-08103错误，将数据库seinescm升级到11.2.0.4版本方法：另辟路劲安装11.2.0.4版本数据库软件，再对现有的数据库进行升级步骤：1. 检查现有数据库并将要升级的数据库关闭 2.安装数据库软件(11.2.0.4) Notice:因为要对现有的数据库版本做升级，所以要选择升级现有的数据库选项 选择跟原版数据库相同的语言 在安装执行...
Oracle 11.2.0.1升级11.2.0.4（Linux 单机）
loveLAxin的博客
08-31 2444
Oracle Linux 单机11.2.0.1升级11.2.0.4，保姆级教程.........
oracle dbua 升级,33篇Oracle升级文档大全（收藏版）
weixin_30863465的博客
04-03 319
Oracle 11203->11204.6小版本物理升级方案https://www.modb.pro/doc/190OEM CC 12.1.0.2 -> 12.1.0.5 升级报告https://www.modb.pro/doc/197Oracle 11201 -> 11204.7 单实例升级步骤https://www.modb.pro/doc/205oracle 11g升级到O...
oracle-04063,ORA-04063 错误问题（package body "SYS.DBMS_LOGSTDBY" has errors）
weixin_30932183的博客
04-07 4567
SQL> @?/rdbms/admin/dbmslsby.sqlPackage created.No errors.Synonym created.PL/SQL procedure successfully completed.Grant succeeded.CREATE ROLE logstdby_administrator*ERROR at line 1:ORA-01921: role ...
ORACLE11.2.0.1升级到11.2.0.3
sunbocong的博客
06-11 2947
ORACLE11.2.0.1升级到11.2.0.3 转自：ORACLE11.2.0.1升级到11.2.0.3 说明 生产数据库一般情况下都是不建议使用11.2.0.1等类似的点1或R1的版本，11.2.0.1是基础版本，这个版本相对上一个版本有较多的特性的更新，而特性的更新也意味着出现BUG的可能性会比其他版本高很多。 原理 数据库的升级其实更像是数据库的迁移，如从11.2.0....
Oracle 10g 版本10.2.0.1.0升级到Oracle 10g 10.2.0.3.0过程
软体疯子专栏
02-27 2338
首先去http://metalink.oracle.com 下载 Oracle Database 10g Release 2 Patch Set 2  ，文件名：p5337014_10203_WINNT.zip，然后解压，运行SETUP安装，注意要先把数据库停掉并做好备份，运行完后，登陆SQLPLUS运行直接startup会报错，提示如下ORA-00704: bootstrap process f
ORA-16416: No viable Physical Standby switchover targets available
最新发布
06-09
这个错误是由于在进行物理 Standby switchover 操作时，没有可用的目标 Standby 数据库引起的。 以下是一些可能的解决方法： 1. 检查当前主数据库是否处于 Maximum Availability 模式下。如果不是，需要将其切换到 Maximum Availability 模式。 2. 确保已经在备库上启用了 Redo Apply 进程。如果没有，请启用 Redo Apply 进程。 3. 检查当前主数据库的 redo transport destination 是否已配置正确，并且备库的 redo transport destination 是否已启用。如果配置不正确，请进行修改。 4. 确保备库与主数据库之间的网络连接正常，并且没有防火墙等限制。 5. 如果您有多个备库，请确保每个备库都已启用，并且它们都处于 Maximum Availability 模式下。 6. 如果以上方法都无法解决问题，您可以尝试使用 DGMGRL 工具手动进行 switchover 操作，以便选择可用的目标 Standby 数据库。 希望这些解决方法能够帮助您解决问题。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值