ADG级联备库环境PSU应用验证

adg,级联,环境,psu,应用,验证 · 浏览次数 : 104

小编点评

**内容生成时需要带简单的排版** **排版示例** ``` @dgNAME VALUE UNIT TIME_COMPUTED DATUM_TIME---------------------- ----------------------------- ------------------------------ ------------------------------ ------------------------------transport lag +00 00:00:00 day(2) to second(0) interval 05/22/2023 16:57:18 05/22/2023 16:57:11apply lag +00 00:00:00 day(2) to second(0) interval 05/22/2023 16:57:18 05/22/2023 16:57:11apply finish time day(2) to second(3) interval 05/22/2023 16:57:18estimated startup time 9 second 05/22/2023 16:58:16 05/22/2023 16:58:07apply lag +00 00:00:56 day(2) to second(0) interval 05/22/2023 16:58:16 05/22/2023 16:58:07apply finish time day(2) to second(3) interval 05/22/2023 16:58:16estimated startup time 9 second 05/22/2023 16:58:16都没问题了,整个过程也符合PSU补丁应用逻辑。。 ----------------------------- ------------------------------ ------------------------------ ------------------------------transport lag +00 00:00:56 day(2) to second(0) interval 05/22/2023 16:58:16 05/22/2023 16:58:07apply lag +00 00:00:56 day(2) to second(0) interval 05/22/2023 16:58:16 05/22/2023 16:58:07apply finish time day(2) to second(3) interval 05/22/2023 16:58:16estimated startup time 9 second 05/22/2023 16:58:16都没问题了,整个过程也符合PSU补丁应用逻辑。。 ----------------------------- ------------------------------ ------------------------------ ------------------------------transport lag +00 00:00:56 day(2) to second(0) interval 05/22/2023 16:58:16 05/22/2023 16:58:07apply lag +00 00:00:56 day(2) to second(0) interval 05/22/2023 16:58:16 05/22/2023 16:58:07apply finish time day(2) to second(3) interval 05/22/2023 16:58:16estimated startup time 9 second 05/22/2023 16:58:16都没问题了,整个过程也符合PSU补丁应用逻辑。。 ----------------------------- ------------------------------ ------------------------------ ------------------------------transport lag +00 00:00:56 day(2) to second(0) interval 05/22/2023 16:58:16 05/22/2023 16:58:07apply lag +00 00:00:56 day(2) to second(0) interval 05/22/2023 16:58:16 05/22/2023 16:58:07apply finish time day(2) to second(3) interval 05/22/2023 16:58:16estimated startup time 9 second 05/22/2023 16:58:16都没问题了,整个过程也符合PSU补丁应用逻辑。 ----------------------------- ------------------------------ ------------------------------ ------------------------------transport lag +00 00:00:56 day(2) to second(0) interval 05/22/2023 16:58:16 05/22/2023 16:58:07apply lag +00 00:00:56 day(2) to second(0) interval 05/22/2023 16:58:16 05/22/2023 16:58:07apply finish time day(2) to second(3) interval 05/22/2023 16:58:16estimated startup time 9 second 05/22/2023 16:58:16都没问题了,整个过程也符合PSU补丁应用逻辑。 ----------------------------- ------------------------------ ------------------------------ ------------------------------transport lag +00 00:00:56 day(2) to second(0) interval 05/22/2023 16:58:16 05/22/2023 16:58:07apply lag +00 00:00:56 day(2) to second(0) interval 05/22/2023 16:58:16 05/22/2023 16:58:07apply finish time day(2) to second(3) interval 05/22/2023 16:58:16estimated startup time 9 second 05/22/2023 16:58:16都没问题了,整个过程也符合PSU补丁应用逻辑。 ----------------------------- ------------------------------ ------------------------------ ------------------------------transport lag +00 00:00:56 day(2) to second(0) interval 05/22/2023 16:58:16 05/22/2023 16:58:07apply lag +00 00:00:56 day(2) to second(0) interval 05/22/2023 16:58:16 05/22/2023 16:58:07apply finish time day(2) to second(3) interval 05/22/2023 16:58:16estimated startup time 9 second 05/22/2023 16:58:16都没问题了,整个过程也符合PSU补丁应用逻辑。 ----------------------------- ------------------------------ ------------------------------ ------------------------------transport lag +00 00:00:56 day(2) to second(0) interval 05/22/2023 16:58:16 05/22/2023 16:58:07apply lag +00 00:00:56 day(2) to second(0) interval 05/22/2023 16:58:16 05/22/2023 16:58:07apply finish time day(2) to second(3) interval 05/22/2023 16:58:16estimated startup time 9 second 05/22/2023 16:58:16都没问题了,整个过程也符合PSU补丁应用逻辑。

正文

上篇文章

我只在中间备库环境应用了PSU,解决了级联备库从中间备库duplicate数据库的问题:

细心的朋友已经发现,因为是备库环境,并没有做数据库执行相关脚本部分,所以如果去DB查询补丁应用信息是没有的:

SQL> r
  1*  select * from dba_registry_history

ACTION_TIME                   ACTION         NAMESPACE        VERSION        ID BUNDLE_SERIES      COMMENTS
--------------------------------------------------------------------------- ------------------------------ ------------------------------ ------------------------------ ---------- ------------------------------ ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
17-SEP-11 10.21.11.595816 AM                APPLY        SERVER       11.2.0.3          0 PSU          Patchset 11.2.0.2.0
04-APR-23 04.37.58.780922 PM                APPLY        SERVER       11.2.0.3          0 PSU          Patchset 11.2.0.2.0

本篇文章就继续把级联备库以及主库的PSU软件补丁打上,步骤和上篇无区别,不再赘述。
最后要在主库按照readme执行对应脚本(只需在主库执行哦,通过ADG基理会将这些改变自动同步到备库):

cd $ORACLE_HOME/rdbms/admin
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
SQL> @catbundle.sql psu apply
SQL> QUIT

再次看状态:

set lines 1000
select * from dba_registry_history;

SQL> set lines 1000
select * from dba_registry_history;SQL>

ACTION_TIME                   ACTION         NAMESPACE        VERSION        ID BUNDLE_SERIES      COMMENTS
--------------------------------------------------------------------------- ------------------------------ ------------------------------ ------------------------------ ---------- ------------------------------ ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
17-SEP-11 10.21.11.595816 AM                APPLY        SERVER       11.2.0.3          0 PSU          Patchset 11.2.0.2.0
04-APR-23 04.37.58.780922 PM                APPLY        SERVER       11.2.0.3          0 PSU          Patchset 11.2.0.2.0
22-MAY-23 04.55.20.039373 PM                APPLY        SERVER       11.2.0.3         15 PSU          PSU 11.2.0.3.15

最后去备库,以及级联备库分别确认同步状态:

备库状态:已有11.2.0.3.15信息

[oracle@db11gadg ~]$ 

SQL> @dg

NAME           VALUE          UNIT           TIME_COMPUTED        DATUM_TIME
---------------------- ---------------------- ------------------------------ ------------------------------ ------------------------------
transport lag        +00 00:00:00       day(2) to second(0) interval   05/22/2023 16:56:04      05/22/2023 16:56:03
apply lag        +00 00:00:00       day(2) to second(0) interval   05/22/2023 16:56:04      05/22/2023 16:56:03
apply finish time      +00 00:00:00.000       day(2) to second(3) interval   05/22/2023 16:56:04
estimated startup time 9          second           05/22/2023 16:56:04

SQL> set lines 1000
select * from dba_registry_history;SQL>

ACTION_TIME                   ACTION         NAMESPACE        VERSION        ID BUNDLE_SERIES      COMMENTS
--------------------------------------------------------------------------- ------------------------------ ------------------------------ ------------------------------ ---------- ------------------------------ ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
17-SEP-11 10.21.11.595816 AM                APPLY        SERVER       11.2.0.3          0 PSU          Patchset 11.2.0.2.0
04-APR-23 04.37.58.780922 PM                APPLY        SERVER       11.2.0.3          0 PSU          Patchset 11.2.0.2.0
22-MAY-23 04.55.20.039373 PM                APPLY        SERVER       11.2.0.3         15 PSU          PSU 11.2.0.3.15

级联备库状态:在主库切日志后也会有11.2.0.3.15信息:

[oracle@db11gcas ~]$

SQL> @dg

NAME           VALUE          UNIT           TIME_COMPUTED        DATUM_TIME
---------------------- ---------------------- ------------------------------ ------------------------------ ------------------------------
transport lag        +00 00:00:48       day(2) to second(0) interval   05/22/2023 16:56:50      05/22/2023 16:56:06
apply lag        +00 00:00:48       day(2) to second(0) interval   05/22/2023 16:56:50      05/22/2023 16:56:06
apply finish time           day(2) to second(3) interval   05/22/2023 16:56:50
estimated startup time 9          second           05/22/2023 16:56:50

SQL> set lines 1000
select * from dba_registry_history;SQL>

ACTION_TIME                   ACTION         NAMESPACE        VERSION        ID BUNDLE_SERIES      COMMENTS
--------------------------------------------------------------------------- ------------------------------ ------------------------------ ------------------------------ ---------- ------------------------------ ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
17-SEP-11 10.21.11.595816 AM                APPLY        SERVER       11.2.0.3          0 PSU          Patchset 11.2.0.2.0
04-APR-23 04.37.58.780922 PM                APPLY        SERVER       11.2.0.3          0 PSU          Patchset 11.2.0.2.0

SQL> /

ACTION_TIME                   ACTION         NAMESPACE        VERSION        ID BUNDLE_SERIES      COMMENTS
--------------------------------------------------------------------------- ------------------------------ ------------------------------ ------------------------------ ---------- ------------------------------ ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
17-SEP-11 10.21.11.595816 AM                APPLY        SERVER       11.2.0.3          0 PSU          Patchset 11.2.0.2.0
04-APR-23 04.37.58.780922 PM                APPLY        SERVER       11.2.0.3          0 PSU          Patchset 11.2.0.2.0
22-MAY-23 04.55.20.039373 PM                APPLY        SERVER       11.2.0.3         15 PSU          PSU 11.2.0.3.15

SQL> @dg

NAME           VALUE          UNIT           TIME_COMPUTED        DATUM_TIME
---------------------- ---------------------- ------------------------------ ------------------------------ ------------------------------
transport lag        +00 00:00:00       day(2) to second(0) interval   05/22/2023 16:57:18      05/22/2023 16:57:11
apply lag        +00 00:00:00       day(2) to second(0) interval   05/22/2023 16:57:18      05/22/2023 16:57:11
apply finish time           day(2) to second(3) interval   05/22/2023 16:57:18
estimated startup time 9          second           05/22/2023 16:57:18


SQL> @dg

NAME           VALUE          UNIT           TIME_COMPUTED        DATUM_TIME
---------------------- ---------------------- ------------------------------ ------------------------------ ------------------------------
transport lag        +00 00:00:56       day(2) to second(0) interval   05/22/2023 16:58:16      05/22/2023 16:58:07
apply lag        +00 00:00:56       day(2) to second(0) interval   05/22/2023 16:58:16      05/22/2023 16:58:07
apply finish time           day(2) to second(3) interval   05/22/2023 16:58:16
estimated startup time 9          second           05/22/2023 16:58:16

都没问题了,整个过程也符合PSU补丁应用逻辑。

与ADG级联备库环境PSU应用验证相似的内容:

ADG级联备库环境PSU应用验证

上篇文章 - [源端为备库的场景下Duplicate失败问题](https://www.cnblogs.com/jyzhao/p/17420831.html) 我只在中间备库环境应用了PSU,解决了级联备库从中间备库duplicate数据库的问题: 细心的朋友已经发现,因为是备库环境,并没有做数据库

11g ADG级联备库基础测试环境准备

客户通过duplicate生产备库的方式创建cascade备库。 发现每次都会遇到两个文件报错,ORA-17628: Oracle error 19505错误,且每一次跑,报错文件不一样。 现在想帮客户验证,这属于是正常现象还是bug; 本文需要先模拟客户11.2.0.3环境,构建备库、级联备库环境

源端为备库的场景下Duplicate失败问题

**环境:** Oracle 11.2.0.3 + OEL 7.9 A -> B -> C 级联ADG环境:db11g -> db11gadg -> db11gcas 之前测试提到,从一级备库duplicate到二级备库会报错: ```shell RMAN-00571: RMAN-00569: ER

ADG无法同步:TT00进程报错 Error 12514

环境: Oracle 19.16 ADG (Single Instance -> RAC) 在配置ADG的场景,发现ADG不能同步。 1.查看报错信息 2.oerr查看该错误说明 3.尝试sqlplus连接到standby 4.尝试relocate监听 5.继续排查发现是参数问题 6.总结和延伸 1

ADG无法切换:报错 ORA-16467

现象: ADG无法切换:验证时就报错 ORA-16467 记录问题,顺便展现一次troubleshooting的心路历程。 具体查询: 在主库操作, @primary 切换验证: alter database switchover to demorac verify; 报错ORA-16467: SQ

ADG备库中某个PDB缺失temp文件

之前认为缺失的temp文件在开库时会自动创建,但其实也有不能自动创建的场景,alert会有类似如下提示: 2023-05-11T20:35:35.974983+08:00 AWR(6):*********************************************************

Oracle ADG环境下的RMAN备份策略

作为IT运维人员,尤其是数据库岗位,数据的备份重于一切。 现在很多用户会有一个普遍误区,认为现在类似ADG这类灾备已经很完善,且实时性也更佳,往往就忽略了传统的备份效用。 但实际上,我们千万不能因为有了容灾建设就盲目忽略备份的作用,二者其实有着本质区别。很多场景,灾备都是无法替代传统备份的,二者是缺

19c ADG Switchover 切换测试

背景: 环境未配置DG Broker,手工切换ADG,19c也要比11g时代的切换更简单。 使用自己的测试环境,具体可参见: 单实例Primary快速搭建Standby RAC参考手册(19.16 ADG) 1.主库demo切换到RAC环境demorac: 在主库demo执行命令: SQL> alt

验证ADG的坏块检测和自动修复

环境: Oracle 19c ADG(主库:单实例;备库:RAC) 1.主库新建测试文件 2.主库创建测试表 3.查询表对应数据文件信息 4.模拟数据文件物理坏块 5.查询对应测试表 6.进一步查询日志信息 7.确认当前参数设置 1.主库新建测试文件 主库在AWR的PDB中做测试,为了不影响其他测试

部署19c ADG过程中的问题处理

回忆起来也是有些年没亲自动手搭建ADG了,今天正好有个机会重温,客户环境是19.16,恍惚记得上一次搭ADG还是在11.2.0.4的时代,时光荏苒啊。 正好看下19c的ADG和11g的ADG在部署方面有啥不同? 主备库都是RAC架构,数据库是CDB架构,包含有4个PDB,整个搭建过程还是遇到很多小问