标签云
asm恢复 bbed bootstrap$ dul kcbzib_kcrsds_1 kccpb_sanity_check_2 kcratr_nab_less_than_odr MySQL恢复 obet ORA-00312 ORA-00704 ORA-00742 ORA-01110 ORA-01200 ORA-01555 ORA-01578 ORA-01595 ORA-600 2662 ORA-600 2663 ORA-600 3020 ORA-600 4000 ORA-600 4137 ORA-600 4193 ORA-600 4194 ORA-600 16703 ORA-600 kcbzib_kcrsds_1 ORA-600 KCLCHKBLK_4 ORA-600 kcratr_nab_less_than_odr ORA-15042 ORA-15196 ORACLE 12C oracle dul ORACLE PATCH Oracle Recovery Tools oracle加密恢复 oracle勒索 oracle勒索恢复 oracle异常恢复 ORACLE恢复 Oracle 恢复 ORACLE数据库恢复 oracle碎片 OSD-04016 YOUR FILES ARE ENCRYPTED 比特币加密文章分类
- MongoDB (1)
- MongoDB恢复 (1)
- Others (2)
- 中间件 (2)
- WebLogic (2)
- 操作系统 (112)
- 数据库 (1,884)
- DB2 (22)
- MySQL (82)
- Oracle (1,709)
- Data Guard (53)
- EXADATA (8)
- GoldenGate (24)
- ORA-xxxxx (168)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (15)
- ORACLE 21C (3)
- Oracle 23ai (8)
- Oracle ASM (73)
- Oracle Bug (8)
- Oracle RAC (56)
- Oracle 安全 (6)
- Oracle 开发 (28)
- Oracle 监听 (29)
- Oracle备份恢复 (662)
- Oracle安装升级 (108)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (91)
- PostgreSQL (37)
- pdu工具 (7)
- PostgreSQL恢复 (13)
- SQL Server (34)
- SQL Server恢复 (14)
- TimesTen (7)
- 达梦数据库 (5)
- 达梦恢复 (3)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (51)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (34)
- MongoDB (1)
-
最近发表
- 记录19c ASM磁盘掉线触发ORA-59048故障处理
- aix平台Oracle数据库由于断电无法启动故障处理
- 断电引起ORA-600 3005故障处理
- 记录一次云存储资源到期之后引起的数据库恢复
- Firebird 损坏数据库数据抢救工具—firebirdext
- Oracle 19c 202610补丁(RUs+OJVM)-19.33
- 由于con$.con#值达到极限,触发数据库增加约束报ORA-600 12807错误
- MongoDB 离线提取工具—mongoext
- .bres勒索病毒加密数据库dmp文件可恢复
- ORA-600 krsm_mrp_rebuild_lf_list.lno_mismatch
- 记录一次0丢失的ORA-00354: 损坏重做日志块标头故障恢复
- 不当数据库恢复操作导致一个月数据丢失
- obet快速修复oracle 位图损坏块
- 不太常见的10.2.0.1的oracle redo损坏恢复
- obet forcecopy功能抢救硬件故障中的数据文件
- kcratr_nab_less_than_odr和system坏块故障处理
- 通过obet 恢复system坏块,打开数据库
- obet dbv功能完整说明
- 分享一例运行在aix上的sap系统数据库恢复过程
- OBET-Oracle Block Editor Tool使用说明
分类目录归档:数据库
关于ORACLE 11G密码大小写敏感猜想(USER$.SPARE4)
从11.1开始密码大小写敏感了,同时可以设置sec_case_sensitive_logon参数可以忽略大小写敏感。
通过朋友咨询的不设置sec_case_sensitive_logon参数让密码大小写不敏感的实验这篇文章疑惑,同时也感谢朋友让我学习到了新知识,我通过测试证明了如下结论:
1.password_versions的优先级大于sec_case_sensitive_logon
2.通过修改USER$.SPARE4为空实现了屏蔽ORACLE 11g密码大小写敏感
10g创建用户导出数据
SQL> create user ora10g identified by xifenfei; User created. SQL> grant connect to ora10g; Grant succeeded. C:\Documents and Settings\Administrator>expdp \"/ as sysdba \" DIRECTORY=exp_dp DUMPFILE=chf.dmp schemas=ora10g Export: Release 10.2.0.1.0 - Production on 星期三, 15 5月, 2013 22:59:45 Copyright (c) 2003, 2005, Oracle. All rights reserved. 连接到: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production With the Partitioning, OLAP and Data Mining options 启动 "SYS"."SYS_EXPORT_SCHEMA_01": "/******** AS SYSDBA" DIRECTORY=exp_dp DUMPF ILE=chf.dmp schemas=ora10g 正在使用 BLOCKS 方法进行估计... 处理对象类型 SCHEMA_EXPORT/TABLE/TABLE_DATA 使用 BLOCKS 方法的总估计: 0 KB 处理对象类型 SCHEMA_EXPORT/USER 处理对象类型 SCHEMA_EXPORT/ROLE_GRANT 处理对象类型 SCHEMA_EXPORT/DEFAULT_ROLE 处理对象类型 SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA 已成功加载/卸载了主表 "SYS"."SYS_EXPORT_SCHEMA_01" ****************************************************************************** SYS.SYS_EXPORT_SCHEMA_01 的转储文件集为: C:\CHF.DMP 作业 "SYS"."SYS_EXPORT_SCHEMA_01" 已于 23:00:19 成功完成
11g创建用户
SQL> select * from v$version; BANNER -------------------------------------------------------------------------------- Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production PL/SQL Release 11.2.0.3.0 - Production CORE 11.2.0.3.0 Production TNS for Linux: Version 11.2.0.3.0 - Production NLSRTL Version 11.2.0.3.0 - Production SQL> show parameter logon NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ sec_case_sensitive_logon boolean TRUE SQL> create user ora11g identified by xifenfei; User created. SQL> grant connect to ora11g; Grant succeeded. SQL> conn ora11g/xifenfei Connected. SQL> conn ora11g/XIFENFEI ERROR: ORA-01017: invalid username/password; logon denied Warning: You are no longer connected to ORACLE.
这里证明,在sec_case_sensitive_logon=true的情况下,数据库密码是大小写敏感
导入10g创建用户dmp文件
[oracle@localhost ~]$ impdp '"/ as sysdba"' directory=exp_dp dumpfile=CHF.DMP Import: Release 11.2.0.3.0 - Production on Wed May 15 23:07:20 2013 Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options Master table "SYS"."SYS_IMPORT_FULL_01" successfully loaded/unloaded Starting "SYS"."SYS_IMPORT_FULL_01": "/******** AS SYSDBA" directory=exp_dp dumpfile=CHF.DMP Processing object type SCHEMA_EXPORT/USER Processing object type SCHEMA_EXPORT/ROLE_GRANT Processing object type SCHEMA_EXPORT/DEFAULT_ROLE Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA Job "SYS"."SYS_IMPORT_FULL_01" successfully completed at 23:07:21
查询ora10g和ora11g用户区别
SQL> conn ora10g/xifenfei
Connected.
SQL> conn ora10g/XIFENFEI
Connected.
SQL> conn / as sysdba
Connected.
SQL> select t.username,t.account_status,t.password_versions from dba_users t where t.username in ('ORA11G','ORA10G');
USERNAME ACCOUNT_STATUS PASSWORD
------------------------------ -------------------------------- --------
ORA11G OPEN 10G 11G
ORA10G OPEN 10G
SQL> select name,password,spare4 from SYS.USER$ t where name in ('ORA11G','ORA10G');
NAME PASSWORD SPARE4
------------------------------ ------------------------------ ----------------------------------------------------------------
ORA10G F3CF2F0CB35CB6CA
ORA11G 559D84354181EB8E S:BFE2625310D9382E9AEA6EE0AA2988E82C17B3EA23E3DAC23800490C2621
这里可以发现我们从低版本(10g)导入到11g中的用户登录是不区分大小写,而11g本身创建的用户是区分大小写,而他们的区别仅仅是在dba_users.password_versions中有不一样,跟踪到基表发现就是USER$.SPARE4列不一样(10g的该列为空).
猜想:password_versions的优先级大于sec_case_sensitive_logon这个参数
验证猜想
如果是password_versions的优先级大于sec_case_sensitive_logon那么,如果我修改了USER$.SPARE4,使得dba_users.password_versions变成和10g导入的库一样,是否就可以实现不区分密码大小写的问题,如果不缺乏证明:password_versions的优先级大于sec_case_sensitive_logon这个参数,反之失败.
SQL> update SYS.USER$ t set SPARE4='' where name='ORA11G'; 1 row updated. SQL> COMMIT; Commit complete. SQL> alter system flush shared_pool; System altered. SQL> conn ora11g/XIFENFEI Connected. SQL> conn ora11g/xifenfei Connected.
由此得出两个结论:
1.password_versions的优先级大于sec_case_sensitive_logon
2.通过修改USER$.SPARE4为空实现了屏蔽ORACLE 11g密码大小写敏感
windows Patch list
32-Bit Patches :
|
Patch |
Patch Location | Bug Fix List | Notes |
| 11.2.0.3.0 Patch 20 | Target date End May 2013 | ||
| 11.2.0.3.0 Patch 19 | Bug:16656150 Patch:16656150 | Note:1114533.1 | Requires 11.2.0.3.0 |
| 11.2.0.3.0 | Bug:10404530 Patch:10404530 | ReadMe | |
| 11.2.0.2.0 Patch 26 | Target date End May 2013 | ||
| 11.2.0.2.0 Patch 25 | Bug:16345845 Patch:16345845 | Note:1114533.1 | Requires 11.2.0.2.0 |
| 11.2.0.2.0 | Bug:10098816 Patch:10098816 | ReadMe | |
| 11.2.0.1.0 Patch 15 | Bug:13329696 Patch:13329696 | Note:1114533.1 | Requires 11.2.0.1.0 |
| 11.1.0.7.0 Patch 53 | Target date Mid July 2013 | ||
| 11.1.0.7.0 Patch 52 | Bug:16345861 Patch:16345861 | Note:560295.1 |
Requires 11.1.0.7.0 |
| 11.1.0.7.0 | Bug:6890831 Patch:6890831 | ReadMe | |
| 11.1.0.6.0 Patch 18 | Bug:8970709 Patch:8970709 | Note:560295.1 |
Requires 11.1.0.6.0 |
| 10.2.0.5.0 Patch 22 | Target date Mid July 2013 | ||
| 10.2.0.5.0 Patch 21 | Bug:16345855 Patch:16345855 | Note:342443.1 | Requires 10.2.0.5.0 |
| 10.2.0.5.0 | Bug:8202632 Patch:8202632 | ReadMe | |
| 10.2.0.4.0 Patch 50 | Bug:15834695 Patch:15834695 | Note:342443.1 |
Requires 10.2.0.4.0 |
| 10.2.0.4.0 Patch 49 | Bug:13928775 Patch:13928775 | Note:342443.1 |
Requires 10.2.0.4.0 |
| 10.2.0.4.0 | Bug:6810189 Patch:6810189 | ReadMe | |
| 10.2.0.3.0 Patch 31 | Bug:8288852 Patch:8288852 | Note:342443.1 |
Requires 10.2.0.3.0 |
| 10.2.0.3.0 | Bug:5337014 Patch:5337014 | ReadMe | |
| 10.2.0.2.0 Patch 18 | Bug:7213940 Patch:7213940 | Note:342443.1 |
Requires 10.2.0.2.0 |
| 10.2.0.2.0 | Bug:4547817 Patch:4547817 | ReadMe | |
| 10.2.0.1.0 Patch 9 | Bug:5695784 Patch:5695784 | Note:342443.1 | |
| 10.1.0.5.0 Patch 45 | Not planned |
Requires 10.1.0.5.0 Standalone Database Home |
|
| 10.1.0.5.0 Patch 44 | Bug:13413002 Patch:13413002 | Note:276548.1 |
Applicable to Standalone Database Oracle Homes. |
| 10.1.0.5.0 | Bug:4505133 Patch:4505133 | ReadMe | |
| 9.2.0.8.0 Patch 32 | Not planned | ||
| 9.2.0.8.0 Patch 31 | Bug:14666190 Patch:14666190 | Note:211268.1 |
Requires 9.2.0.8.0 |
| 9.2.0.8.0 CFS RAC | Bug:5388107 Patch:5388107 |
Cluster File System / RAC Clusterware bundle |
|
| 9.2.0.8.0 | Bug:4547809 Patch:4547809 | ReadMe |
64-Bit x64 Patches :
|
Patch |
Patch Location | Bug Fix List | Notes |
| 11.2.0.3.0 Patch 20 | Target date End May 2013 | ||
| 11.2.0.3.0 Patch 19 | Bug:16656151 Patch:16656151 | Note:1114533.1 | Requires 11.2.0.3.0 |
| 11.2.0.3.0 | Bug:10404530 Patch:10404530 | ReadMe | |
| 11.2.0.2.0 Patch 26 | Target date End May 2013 | ||
| 11.2.0.2.0 Patch 25 | Bug:16345846 Patch:16345846 | Note:1114533.1 | Requires 11.2.0.2.0 |
| 11.2.0.2.0 | Bug:10098816 Patch:10098816 | ReadMe | |
| 11.2.0.1.0 Patch 16 | Bug:13423278 Patch:13423278 | Note:1114533.1 | Requires 11.2.0.1.0. Patch 16 is only available on x64 Windows due a build issue. |
| 11.1.0.7.0 Patch 53 | Target date Mid July 2013 | ||
| 11.1.0.7.0 Patch 52 | Bug:16345862 Patch:16345862 | Note:560295.1 |
Requires 11.1.0.7.0 |
| 11.1.0.7.0 | Bug:6890831 Patch:6890831 | ReadMe | |
| 11.1.0.6.0 Patch 18 | Bug:8970710 Patch:8970710 | Note:560295.1 |
Requires 11.1.0.6.0 |
| 10.2.0.5.0 Patch 22 | Target date Mid July 2013 | ||
| 10.2.0.5.0 Patch 21 | Bug:16345857 Patch:16345857 | Note:342443.1 | Requires 10.2.0.5.0 |
| 10.2.0.5.0 | Bug:8202632 Patch:8202632 | ReadMe | |
| 10.2.0.4.0 Patch 49 | Bug:13928776 Patch:13928776 | Note:342443.1 |
Requires 10.2.0.4.0 |
| 10.2.0.4.0 | Bug:6810189 Patch:6810189 | ReadMe | |
| 10.2.0.3.0 Patch 31 | Bug:8288854 Patch:8288854 | Note:342443.1 |
Requires 10.2.0.3.0 |
| 10.2.0.3.0 | Bug:5337014 Patch:5337014 | ReadMe | |
| 10.2.0.2.0 Patch 18 | Bug:7213942 Patch:7213942 | Note:342443.1 |
Requires 10.2.0.2.0 |
| 10.2.0.2.0 | Bug:4547817 Patch:4547817 | ReadMe | |
| 10.2.0.1.0 Patch 9 | Bug:5695786 Patch:5695786 | Note:342443.1 |
64-Bit Itanium Patches :
|
Patch |
Patch Location | Bug Fix List | Notes |
| 10.2.0.5.0 Patch 22 | Target date Mid July 2013 | ||
| 10.2.0.5.0 Patch 21 | Bug:16345856 Patch:16345856 | Note:342443.1 | Requires 10.2.0.5.0 |
| 10.2.0.5.0 | Bug:8202632 Patch:8202632 | ReadMe | |
| 10.2.0.4.0 Patch 47 | Bug:12914909 Patch:12914909 | Note:342443.1 |
Requires 10.2.0.4.0 |
| 10.2.0.4.0 | Bug:6810189 Patch:6810189 | ReadMe | |
| 10.2.0.3.0 Patch 32 | Bug:8504486 Patch:8504486 | Note:342443.1 |
Requires 10.2.0.3.0 |
| 10.2.0.3.0 | Bug:5337014 Patch:5337014 | ReadMe | |
| 10.2.0.2.0 Patch 18 | Bug:7213941 Patch:7213941 | Note:342443.1 |
Requires 10.2.0.2.0 |
| 10.2.0.2.0 | Bug:4547817 Patch:4547817 | ReadMe | |
| 10.2.0.1.0 Patch 9 | Bug:5695785 Patch:5695785 | Note:342443.1 | |
| 10.1.0.5.0 Patch 45 | Not planned | ||
| 10.1.0.5.0 Patch 44 | Bug:13413003 Patch:13413003 | Note:276548.1 |
Applicable to Standalone Database Oracle Homes. |
| 10.1.0.5.0 | Bug:4505133 Patch:4505133 | ReadMe | |
| 9.2.0.8.0 Patch 31 | Not planned | ||
| 9.2.0.8.0 Patch 30 | Bug:9683645 Patch:9683645 | Note:211268.1 |
Requires 9.2.0.8 |
| 9.2.0.8.0 CFS RAC | Bug:5689499 Patch:5689499 | ||
| 9.2.0.8.0 | Bug:4547809 Patch:4547809 | ReadMe |
发表在 Oracle
评论关闭
修改dataguard主库redo组数和大小
在一个dg环境中,配置的是实时同步,需要增加主库的redo大小和组数,本来是一个很简单的问题,解决思路是:先备库增加standby redo删除老standby redo,然后主库增加redo删除老redo,备库增加新redo删除老redo,最后主库增加standby redo。但是在实施过程中,遇到了一些细节性的问题,主要是学习到了log_file_name_convert如果不配置,将导致备库redo 文件不能被删除
standby redo log管理
增加standby redo log
SQL> alter database add standby logfile group 8 ('/data/oradata/wasudb/st_redo08.log') size 200M;
alter database add standby logfile group 8 ('/data/oradata/wasudb/st_redo08.log') size 200M
*
ERROR at line 1:
ORA-01156: recovery in progress may need access to files
SQL> alter database recover managed standby database cancel;
Database altered.
SQL> alter database add standby logfile group 9 ('/data/oradata/wasudb/st_redo09.log') size 200M;
Database altered.
SQL> alter database add standby logfile group 10 ('/data/oradata/wasudb/st_redo10.log') size 200M;
Database altered.
SQL> alter database add standby logfile group 11 ('/data/oradata/wasudb/st_redo11.log') size 200M;
Database altered.
SQL> alter database add standby logfile group 12 ('/data/oradata/wasudb/st_redo12.log') size 200M;
Database altered.
删除standby redo log
SQL> alter database drop logfile group 4; alter database drop logfile group 4 * ERROR at line 1: ORA-00261: log 4 of thread 1 is being archived or modified ORA-00312: online log 4 thread 1: '/data/oradata/wasudb/st_redo04.log' SQL> alter database drop logfile group 5;; Database altered. SQL> alter database drop logfile group 6; Database altered. SQL> alter database drop logfile group 7; Database altered. --在主库多次执行switch logfile SQL> alter database drop logfile group 4; Database altered.
主库redo log 管理
增加redo log
SQL> alter database add logfile group 21 ('/data/oradata/wasudb/redo21.log') size 200m;
Database altered.
SQL> alter database add logfile group 22 ('/data/oradata/wasudb/redo22.log') size 200m;
Database altered.
SQL> alter database add logfile group 23 ('/data/oradata/wasudb/redo23.log') size 200m;
Database altered.
SQL> alter database add logfile group 24 ('/data/oradata/wasudb/redo24.log') size 200m;
Database altered.
删除redo log
SQL> alter database drop logfile group 1; Database altered. SQL> alter database drop logfile group 2; Database altered. SQL> alter database drop logfile group 3; Database altered. --这里涉及到多次switch logfile,需要确定redo是inactive才能够删除
备库redo log管理
增加redo log
SQL> alter database add logfile group 21 ('/data/oradata/wasudb/redo21.log') size 200m;
alter database add logfile group 21 ('/data/oradata/wasudb/redo21.log') size 200m
*
ERROR at line 1:
ORA-01275: Operation ADD LOGFILE is not allowed if standby file management is automatic.
SQL> alter system set standby_file_management=manual;
System altered.
SQL> alter database add logfile group 21 ('/data/oradata/wasudb/redo21.log') size 200m;
Database altered.
SQL> alter database add logfile group 22 ('/data/oradata/wasudb/redo22.log') size 200m;
Database altered.
SQL> alter database add logfile group 23 ('/data/oradata/wasudb/redo23.log') size 200m;
Database altered.
SQL> alter database add logfile group 24 ('/data/oradata/wasudb/redo24.log') size 200m;
Database altered.
删除redo log
SQL> alter database drop logfile group 1;
alter database drop logfile group 1
*
ERROR at line 1:
ORA-01624: log 1 needed for crash recovery of instance wasudb (thread 1)
ORA-00312: online log 1 thread 1: '/data/oradata/wasudb/redo01.log'
SQL> ALTER DATABASE CLEAR LOGFILE GROUP 1;
ALTER DATABASE CLEAR LOGFILE GROUP 1
*
ERROR at line 1:
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 1 thread 1: '/data/oradata/wasudb/redo01.log'
SQL> show parameter NAME_CONVERT
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_file_name_convert string
log_file_name_convert string
SQL> alter system set log_file_name_convert='/data/oradata/wasudb','/data/oradata/wasudb' scope=spfile;
System altered.
SQL> alter system set db_file_name_convert='/data/oradata/wasudb','/data/oradata/wasudb' scope=spfile;
System altered.
--重启数据库
SQL> show parameter file_name_convert;
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_file_name_convert string /data/oradata/wasudb, /data/or
adata/wasudb
log_file_name_convert string /data/oradata/wasudb, /data/or
adata/wasudb
SQL> alter database drop logfile group 1;
alter database drop logfile group 1
*
ERROR at line 1:
ORA-01624: log 1 needed for crash recovery of instance wasudb (thread 1)
ORA-00312: online log 1 thread 1: '/data/oradata/wasudb/redo01.log'
SQL> ALTER DATABASE CLEAR LOGFILE GROUP 1;
Database altered.
SQL> alter database drop logfile group 1;
Database altered.
SQL> ALTER DATABASE CLEAR LOGFILE GROUP 2;
Database altered.
SQL> alter database drop logfile group 2;
Database altered.
SQL> ALTER DATABASE CLEAR LOGFILE GROUP 3;
Database altered.
SQL> alter database drop logfile group 3;
Database altered.
主库standby redo log管理
增加standby redo
SQL> alter database add logfile group 21 ('/data/oradata/wasudb/redo21.log') size 200m;
Database altered.
SQL> alter database add logfile group 22 ('/data/oradata/wasudb/redo22.log') size 200m;
Database altered.
SQL> alter database add logfile group 23 ('/data/oradata/wasudb/redo23.log') size 200m;
Database altered.
SQL> alter database add logfile group 24 ('/data/oradata/wasudb/redo24.log') size 200m;
Database altered.
删除standby redo
SQL> alter database drop logfile group 4; Database altered. SQL> alter database drop logfile group 5; Database altered. SQL> alter database drop logfile group 6; Database altered. SQL> alter database drop logfile group 7; Database altered.
后续工作
SQL> alter system set standby_file_management=auto; System altered. SQL> alter database recover managed standby database using current logfile disconnect from session; Database altered.
至此修改dataguard环境中的redo大小和增加redo组数的操作基本完成.在这里主要修正了自己以前对log_file_name_convert的认识,我以前以为如果我的主备库redo对应的目录一致不用配置该参数,今天通过查询MOS发现从10.2开始数据库为了能实现dg的快速切换在mrp启动的时候会去尝试清理备库redo,如果备库没有redo,或者log_file_name_convert配置不正确导致不能正常执行这个清理工作,数据库就会报ORA-19527,特别是在mrp进程启动之时.对于本次出现执行CLEAR LOGFILE命令也出现该问题,确实有点过犹不及了.这里也就是提醒我们:就算redo file,datafile主备位置相同,也建议配置log_file_name_convert和db_file_name_convert参数,提高dg健壮性.
发表在 Data Guard
10 条评论

加我微信(17813235971)
加我QQ(107644445)

