Oracle DataGuard中的一些坑

Oracle-Rman duplicate文件坏块问题处理ORA-19849 19612 最近,在使用rman duplicate进行备库环境搭建时,遇到了ORA-19849 19612坏块报错,最终分析是发现由于网络的配置导致。 阅读详情

Oracle DataGuard中的一些坑

知识0:SQL> 中alter set 设置变量值时注意用引号 '' , 否则会自动设置为大写。

知识1:Oracle数据库DB_NAME、SERVICE_NAME、SID、INSTANCE_NAME等区别

DB_NAME:

①是数据库名,长度不能超过8个字符,记录在datafile、redolog和control file中 
②在DataGuard环境中DB_NAME相同而DB_UNIQUE_NAME不同 
③在RAC环境中,各个节点的DB_NAME 都相同,但是INSTANCE_NAME不同 
④DB_NAME还在动态注册监听的时候起作用,无论是否定义了SERVICE_NAME,PMON进程都会使用DB_NAME动态注册监听

DB_UNIQUE_NAME:

①在DataGuard中,主备库拥有相同的DB_NAME,为了区别,就必须有不同的DB_UNIQUE_NAME 
②DB_UNIQUE_NAME在DG中会影响动态注册的SERVICE_NAME,即如果采用的是动态注册,则注册的SERVICE_NAME为DB_UNIQUE_NAME,但是实例还是INSTANCE_NAME,即SID

INSTANCE_NAME:

①数据库实例的名称,INSTANCE_NAME默认值是SID,一般情况下和数据库名称(DB_NAME)相同,也可不同 
②initSID.ora 和orapwSID 文件要与INSTANCE_NAME保持一致 
③INSTANCE_NAME会影响进程的名称

SID(SID_NAME)://待修正

①是操作系统中的环境变量,和ORACLE_HOME,ORACLE_BASE用法相同 
②在操作系统中要想得到实例名,就必须使用ORACLE_SID。且ORACLE_SID必须与INSTANCE_NAME的值一致

SID即INSTANCE_NAME是用来唯一标示实例的

SERVICE_NAME(s):

SERVICE_NAME参数直接对应数据库。

①数据库和客户端相连是使用的服务名 
②在DataGuard中,如果采用动态注册,建议在主备库使用相同的service_names 
③在DataGuard中,如果采用静态注册,建议在主备库上的listener中输入相同的服务名(service_name) 
④如果采监听采用了静态注册,那么SERVICE_NAME就等于Listener.ora文件中的GLOBAL_DATABASE_NAME的值

GLOBAL_DATABASE_NAME: 
①GLOBAL_DATABASE_NAME 是listener配置的对外网络连接名称,可以是任意值 
②在客户端配置监听的tnsnames.ora 文件中的service_name与这个GLOBAL_DBNAME 保持一致就可以了 
③配置静态监听注册时,需要输入SID和GLOBAL_NAME

 

 

 

 

建议1:

$ tnsping <target_db> 
$ tnsping <auxiliary_db>

多tnsping,验证两个数据库的连通性。

建议2:

SQL>shutdown 时,先退出RMAN连接。

 

 

bug1、lsnrctl reload 与 lsnrctl>stop    lsnrctl>start并不一样(待确认)。

bug2、ORACLE error from auxiliary database: ORA-17629: Cannot connect to the remote database server


RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/03/2019 10:16:24
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-17629: Cannot connect to the remote database server
ORA-17627: ORA-12533: TNS:illegal ADDRESS parameters
ORA-17629: Cannot connect to the remote database server

解决方:1:

如果用grid账户安装了GI,那grid目录下的sqlnet.ora、listen.ora和tnsname.ora是真正的配置文件。

方法是:将oracle用户下的tnsnames.ora的内容拷贝到grid用户下的tnsnames.ora文件中。

[root@ol73 admin]# cp tnsnames.ora /u01/12.1.0/grid/network/admin/ 

[root@ol73 admin]#  chown -R grid:oinstall tnsnames.ora  

 

解决方案2:可能是lsnrctl status的状态不对

lsnrctl reload / lsnrctl>start

 

 

bug3、“invalid username/password; logon denied”错误,也可能是数据库处于关闭状态。

如:

Copyright (c) 1982, 2014, Oracle and/or its affiliates.  All rights reserved.

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database: 
ORA-01017: invalid username/password; logon denied

解决方法:

SQL>startup nomount(open)

 

bug4:  MEMORY_TARGET not supported on this system

SQL> startup open;
ORA-00845: MEMORY_TARGET not supported on this system

解决方案:原因是/dev/shm 必须大于 MEMORY_TARGET。

$ df -h
Filesystem           Size  Used Avail Use% Mounted on
devtmpfs             1.8G     0  1.8G   0% /dev
tmpfs                1.9G  635M  1.2G  35% /dev/shm
tmpfs                1.9G  9.2M  1.8G   1% /run
tmpfs                1.9G     0  1.9G   0% /sys/fs/cgroup
/dev/mapper/ol-root   10G  3.9G  6.2G  39% /
/dev/sda1            397M  199M  198M  51% /boot
/dev/mapper/ol-home  3.0G   58M  3.0G   2% /home
/dev/mapper/ol-u01    30G   18G   13G  58% /u01
/dev/mapper/ol-tmp   3.0G   59M  3.0G   2% /tmp
vmhgfs-fuse          159G  133G   27G  84% /mnt/hgfs
tmpfs                370M     0  370M   0% /run/user/54322
tmpfs                370M   16K  370M   1% /run/user/42
tmpfs                370M     0  370M   0% /run/user/54321
tmpfs                370M     0  370M   0% /run/user/0

$su

[root@ol73 dbs]# mount -o size=2560m /dev/shm

//*****************以下尚未测试**********

这个方案是临时方案,

#永久增加tempfs的大小,直接修改/etc/fstab
vi /etc/fstab
tmpfs /dev/shm tmpfs defaults,size=2048M 0 0
修改之后remount
mount -o remount /dev/shm

*************************************************//

bug5:   failed to create file "/u01/app/oracle/oradata/cdb1/pdbseed/system01.dbf"

channel ORA_AUX_DISK_1: using network backup set from service cdb1
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00004 to /u01/app/oracle/oradata/cdb1/undotbs01.dbf
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:03
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: using network backup set from service cdb1
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00005 to /u01/app/oracle/oradata/cdb1/pdbseed/system01.dbf
dbms_backup_restore.restoreCancel() failed
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/03/2019 10:43:37
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
ORA-19660: some files in the backup set could not be verified
ORA-19661: datafile 5 could not be verified
ORA-19849: error while reading backup piece from service cdb1
ORA-19504: failed to create file "/u01/app/oracle/oradata/cdb1/pdbseed/system01.dbf"
ORA-27040: file create error, unable to create file
Linux-x86_64 Error: 2: No such file or directory
Additional information: 1

解决方法:

在备机上创建目录 pdbseed。

 

 

 

------------以下是搞定的流程显示-----------------------------------------------------------------------------------------------------

[oracle@ol73 pdb1]$ rman target sys/Tian2018@cdb1 auxiliary sys/Tian2018@cdb2 nocatalog

Recovery Manager: Release 12.1.0.2.0 - Production on Fri May 3 11:36:14 2019

Copyright (c) 1982, 2014, Oracle and/or its affiliates.  All rights reserved.

connected to target database: CDB1 (DBID=980180079)
using target database control file instead of recovery catalog
connected to auxiliary database: CDB1 (not mounted)

RMAN> duplicate target database for standby nofilenamecheck from active database;

Starting Duplicate Db at 03-MAY-19
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=22 device type=DISK

contents of Memory Script:
{
   backup as copy reuse
   targetfile  '/u01/app/oracle/product/12.1.0/db_1/dbs/orapwcdb1' auxiliary format 
 '/u01/app/oracle/product/12.1.0/db_1/dbs/orapwcdb1'   ;
}
executing Memory Script

Starting backup at 03-MAY-19
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=21 device type=DISK
Finished backup at 03-MAY-19

contents of Memory Script:
{
   sql clone "alter system set  control_files = 
  ''/u01/app/oracle/oradata/cdb1/controlfile/o1_mf_gdm6xmg4_.ctl'', ''/u01/app/oracle/fast_recovery_area/cdb1/controlfile/o1_mf_gdm6xmp1_.ctl'' comment=
 ''Set by RMAN'' scope=spfile";
   restore clone from service  'cdb1' standby controlfile;
}
executing Memory Script

sql statement: alter system set  control_files =   ''/u01/app/oracle/oradata/cdb1/controlfile/o1_mf_gdm6xmg4_.ctl'', ''/u01/app/oracle/fast_recovery_area/cdb1/controlfile/o1_mf_gdm6xmp1_.ctl'' comment= ''Set by RMAN'' scope=spfile

Starting restore at 03-MAY-19
using channel ORA_AUX_DISK_1

channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: using network backup set from service cdb1
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
output file name=/u01/app/oracle/oradata/cdb1/controlfile/o1_mf_gdm6xmg4_.ctl
output file name=/u01/app/oracle/fast_recovery_area/cdb1/controlfile/o1_mf_gdm6xmp1_.ctl
Finished restore at 03-MAY-19

contents of Memory Script:
{
   sql clone 'alter database mount standby database';
}
executing Memory Script

sql statement: alter database mount standby database
Using previous duplicated file /u01/app/oracle/oradata/cdb1/system01.dbf for datafile 1 with checkpoint SCN of 2716331
Using previous duplicated file /u01/app/oracle/oradata/cdb1/sysaux01.dbf for datafile 3 with checkpoint SCN of 2716354
Using previous duplicated file /u01/app/oracle/oradata/cdb1/undotbs01.dbf for datafile 4 with checkpoint SCN of 2716372
Using previous duplicated file /u01/app/oracle/oradata/cdb1/users01.dbf for datafile 6 with checkpoint SCN of 2724419

contents of Memory Script:
{
   set newname for tempfile  1 to 
 "/u01/app/oracle/oradata/cdb1/temp01.dbf";
   set newname for tempfile  2 to 
 "/u01/app/oracle/oradata/cdb1/pdbseed/pdbseed_temp012019-04-24_08-58-04-PM.dbf";
   set newname for tempfile  3 to 
 "/u01/app/oracle/oradata/cdb1/pdb1/pdb1_temp012019-04-24_09-08-24-PM.dbf";
   switch clone tempfile all;
   set newname for datafile  1 to 
 "/u01/app/oracle/oradata/cdb1/system01.dbf";
   set newname for datafile  3 to 
 "/u01/app/oracle/oradata/cdb1/sysaux01.dbf";
   set newname for datafile  4 to 
 "/u01/app/oracle/oradata/cdb1/undotbs01.dbf";
   set newname for datafile  5 to 
 "/u01/app/oracle/oradata/cdb1/pdbseed/system01.dbf";
   set newname for datafile  6 to 
 "/u01/app/oracle/oradata/cdb1/users01.dbf";
   set newname for datafile  7 to 
 "/u01/app/oracle/oradata/cdb1/pdbseed/sysaux01.dbf";
   set newname for datafile  8 to 
 "/u01/app/oracle/oradata/cdb1/pdb1/system01.dbf";
   set newname for datafile  9 to 
 "/u01/app/oracle/oradata/cdb1/pdb1/sysaux01.dbf";
   set newname for datafile  10 to 
 "/u01/app/oracle/oradata/cdb1/pdb1/SAMPLE_SCHEMA_users01.dbf";
   set newname for datafile  11 to 
 "/u01/app/oracle/oradata/cdb1/pdb1/example01.dbf";
   restore
   from service  'cdb1'   clone datafile
    5, 7, 8, 9, 10, 11   ;
   sql 'alter system archive log current';
}
executing Memory Script

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

renamed tempfile 1 to /u01/app/oracle/oradata/cdb1/temp01.dbf in control file
renamed tempfile 2 to /u01/app/oracle/oradata/cdb1/pdbseed/pdbseed_temp012019-04-24_08-58-04-PM.dbf in control file
renamed tempfile 3 to /u01/app/oracle/oradata/cdb1/pdb1/pdb1_temp012019-04-24_09-08-24-PM.dbf in control file

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

Starting restore at 03-MAY-19
using channel ORA_AUX_DISK_1

skipping datafile 5; already restored to SCN 1809309
skipping datafile 7; already restored to SCN 1809309
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: using network backup set from service cdb1
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00008 to /u01/app/oracle/oradata/cdb1/pdb1/system01.dbf
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:03
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: using network backup set from service cdb1
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00009 to /u01/app/oracle/oradata/cdb1/pdb1/sysaux01.dbf
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:07
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: using network backup set from service cdb1
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00010 to /u01/app/oracle/oradata/cdb1/pdb1/SAMPLE_SCHEMA_users01.dbf
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:02
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: using network backup set from service cdb1
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00011 to /u01/app/oracle/oradata/cdb1/pdb1/example01.dbf
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:07
Finished restore at 03-MAY-19

sql statement: alter system archive log current

contents of Memory Script:
{
   restore clone force from service  'cdb1' 
           archivelog from scn  2716331;
   catalog clone datafilecopy  "/u01/app/oracle/oradata/cdb1/system01.dbf", 
 "/u01/app/oracle/oradata/cdb1/sysaux01.dbf", 
 "/u01/app/oracle/oradata/cdb1/undotbs01.dbf", 
 "/u01/app/oracle/oradata/cdb1/users01.dbf";
   switch clone datafile  1 to datafilecopy 
 "/u01/app/oracle/oradata/cdb1/system01.dbf";
   switch clone datafile  3 to datafilecopy 
 "/u01/app/oracle/oradata/cdb1/sysaux01.dbf";
   switch clone datafile  4 to datafilecopy 
 "/u01/app/oracle/oradata/cdb1/undotbs01.dbf";
   switch clone datafile  6 to datafilecopy 
 "/u01/app/oracle/oradata/cdb1/users01.dbf";
   switch clone datafile all;
}
executing Memory Script

Starting restore at 03-MAY-19
using channel ORA_AUX_DISK_1

channel ORA_AUX_DISK_1: starting archived log restore to default destination
channel ORA_AUX_DISK_1: using network backup set from service cdb1
channel ORA_AUX_DISK_1: restoring archived log
archived log thread=1 sequence=45
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
channel ORA_AUX_DISK_1: starting archived log restore to default destination
channel ORA_AUX_DISK_1: using network backup set from service cdb1
channel ORA_AUX_DISK_1: restoring archived log
archived log thread=1 sequence=46
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
channel ORA_AUX_DISK_1: starting archived log restore to default destination
channel ORA_AUX_DISK_1: using network backup set from service cdb1
channel ORA_AUX_DISK_1: restoring archived log
archived log thread=1 sequence=47
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
channel ORA_AUX_DISK_1: starting archived log restore to default destination
channel ORA_AUX_DISK_1: using network backup set from service cdb1
channel ORA_AUX_DISK_1: restoring archived log
archived log thread=1 sequence=48
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
channel ORA_AUX_DISK_1: starting archived log restore to default destination
channel ORA_AUX_DISK_1: using network backup set from service cdb1
channel ORA_AUX_DISK_1: restoring archived log
archived log thread=1 sequence=49
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
channel ORA_AUX_DISK_1: starting archived log restore to default destination
channel ORA_AUX_DISK_1: using network backup set from service cdb1
channel ORA_AUX_DISK_1: restoring archived log
archived log thread=1 sequence=50
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
Finished restore at 03-MAY-19

cataloged datafile copy
datafile copy file name=/u01/app/oracle/oradata/cdb1/system01.dbf RECID=8 STAMP=1007293014
cataloged datafile copy
datafile copy file name=/u01/app/oracle/oradata/cdb1/sysaux01.dbf RECID=9 STAMP=1007293014
cataloged datafile copy
datafile copy file name=/u01/app/oracle/oradata/cdb1/undotbs01.dbf RECID=10 STAMP=1007293014
cataloged datafile copy
datafile copy file name=/u01/app/oracle/oradata/cdb1/users01.dbf RECID=11 STAMP=1007293014

datafile 1 switched to datafile copy
input datafile copy RECID=8 STAMP=1007293014 file name=/u01/app/oracle/oradata/cdb1/system01.dbf

datafile 3 switched to datafile copy
input datafile copy RECID=9 STAMP=1007293014 file name=/u01/app/oracle/oradata/cdb1/sysaux01.dbf

datafile 4 switched to datafile copy
input datafile copy RECID=10 STAMP=1007293014 file name=/u01/app/oracle/oradata/cdb1/undotbs01.dbf

datafile 6 switched to datafile copy
input datafile copy RECID=11 STAMP=1007293014 file name=/u01/app/oracle/oradata/cdb1/users01.dbf

datafile 5 switched to datafile copy
input datafile copy RECID=12 STAMP=1007293015 file name=/u01/app/oracle/oradata/cdb1/pdbseed/system01.dbf
datafile 7 switched to datafile copy
input datafile copy RECID=13 STAMP=1007293015 file name=/u01/app/oracle/oradata/cdb1/pdbseed/sysaux01.dbf
datafile 8 switched to datafile copy
input datafile copy RECID=14 STAMP=1007293015 file name=/u01/app/oracle/oradata/cdb1/pdb1/system01.dbf
datafile 9 switched to datafile copy
input datafile copy RECID=15 STAMP=1007293015 file name=/u01/app/oracle/oradata/cdb1/pdb1/sysaux01.dbf
datafile 10 switched to datafile copy
input datafile copy RECID=16 STAMP=1007293015 file name=/u01/app/oracle/oradata/cdb1/pdb1/SAMPLE_SCHEMA_users01.dbf
datafile 11 switched to datafile copy
input datafile copy RECID=17 STAMP=1007293015 file name=/u01/app/oracle/oradata/cdb1/pdb1/example01.dbf
Finished Duplicate Db at 03-MAY-19

[2022-04-07] 搭建dataguard报 dbms_backup_restore.restoreCancel() failed 1、备库搭建时报如下错误 [oracle@rac1-adg ~]$ rman target sys/tiger@primary auxiliary sys/tiger@standby Recovery Manager: Release 19.0.0.0.0 - Production on Thu Apr 7 12:44:24 2022 Version 19.7.0.0.0 Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rig 阅读详情

相关推荐

搭建Oracle DataGuard--记录自己搭建期间踩过的坑

近期公司要求搭建一个Oracle DG的主备库,因为之前只是看过相关的文档没仔细研究过,所以这次搭建的时候很多坑我都踩了,我觉得很有必要总结下来!!!   一、安装Data Guard的主要步骤。 在主库上安装Oracle软件以及创建实例,在备库上只安装软件不创建实例。 主库上创建pfile并修改参数、监听和TNS。 将主库上的pfile、监听文件、TNS文件拷贝到备库并修改相应的内容。...

Zacharl的博客 1700

12C ORA-错误汇总11 ORA-12500 to ORA-24279

ORA-19500: device block size string is invalid Cause: the device block size returned by sequential I/O OSD is invalid Action: If the block size was set by using the PARMS option of the Recovery Man

badman250的专栏 3万+

Oracle 19c DataGuard实战:从零到一搭建高可用数据库(含RMAN复制数据库避坑指南)

本文详细介绍了Oracle 19c DataGuard的实战搭建流程,涵盖环境规划、主库配置、RMAN复制数据库的关键操作及常见问题解决方案。通过具体命令和配置示例,帮助用户从零构建高可用数据库集群,确保业务连续性。特别针对RMAN复制过程中的典型问题提供了避坑指南,适用于企业级数据库架构的灾备需求。

【洪波@阿里云】 642

rac-rac搭建dg遇到错误 ora-19845 17628 19660 19662 19845 17628

发现此时参数文件,控制文件和数据文件均是正常的,故而此时可以直接open数据库,在open的过程中,数据库会自动创建redo文件

weixin_43475880的博客 855

避免踩坑:Oracle DataGuard解除过程中的常见错误及解决方案

本文详细解析了Oracle DataGuard解除过程中的常见错误及解决方案,涵盖了从参数配置到完整卸载的全流程。特别针对备库状态确认、主库归档日志处理、参数重置等关键环节提供专业指导,帮助DBA避免解除DataGuard时可能遇到的性能下降和数据不一致问题。

weixin_28318011的博客 390

Oracle 19c DataGuard配置避坑指南:从归档模式到网络配置的10个常见错误

本文详细解析了Oracle 19c DataGuard配置中的10个常见错误及解决方案,涵盖归档模式设置、网络连接配置、密码文件同步等关键环节。通过实战案例和诊断命令,帮助DBA避免配置陷阱,确保主备库高效同步,特别适合需要优化DataGuard性能的Oracle数据库管理员。

weixin_34101914的博客 262

Oracle 19c ADG报错ORA-19660: some files in the backup set could not be verified ORA-19661: datafile 0

摘要: Oracle 19c主备库同步时出现“版本不兼容”错误(ORA-19690)的常见原因及解决方法: 备用库compatible参数错误:检查是否为19c版本(19.0.0.0),若为11g/12c值需修改spfile并重启实例。 主备库补丁版本不一致:对比v$version的补丁号(如19.18 vs 19.3),需升级备库至与主库一致。 环境变量污染:备库LD_LIBRARY_PATH或PATH混入11g路径,需清理并配置纯19c环境。 主库备份兼容性限制:检查RMAN备份是否强制兼容11g,需重

huanhuanzhou blog 512

避坑指南:Oracle 19c DataGuard配置中那些容易踩的“雷”(归档、网络、密码文件)

本文深入解析Oracle 19c DataGuard配置中的常见问题,包括归档模式、网络连接、密码文件同步等关键环节的避坑指南。特别针对19c版本的新特性,提供实战验证的解决方案和优化建议,帮助DBA团队高效搭建稳定的DataGuard环境。

weixin_33416697的博客 250

STM32第一个工程:启动流程、内存布局与AI协同调试全解析

嵌入式开发中,‘第一个STM32工程’远不止IDE建项目操作,本质是MCU启动流程、C运行时环境与硬件资源映射的系统性验证。其核心涉及向量表定位、栈/堆内存分配、链接脚本配置及启动文件(startup.s)定制等底层原理。掌握这些,才能理解Reset_Handler执行逻辑、SystemInit调用时机与NVIC异常响应机制。技术价值在于构建可信赖的软硬件信任链——确保复位后SP/PC正确加载、main函数可靠进入、中断可控响应。典型应用场景包括裸机驱动开发、RTOS移植、IAP升级及高实时性控制(如FOC

weixin_34323858的博客 342

Oracle 19c DataGuard实战:从主备库参数文件到网络配置,一个都不能少的避坑指南

本文深入解析Oracle 19c DataGuard实战配置中的关键参数与网络设置,提供主备库参数文件、归档日志配置及网络优化的详细指南,帮助DBA避开90%的常见陷阱,确保高可用性和数据同步效率。

java 学习 470

Oracle 19c DataGuard解除全流程:从参数备份到服务重启的避坑手册

本文详细介绍了Oracle 19c DataGuard解除的全流程,包括参数备份、主备库模式切换、参数重置、Standby日志清理及服务重启等关键步骤。特别针对金融级数据库环境,提供了避免数据丢失和性能波动的实用技巧,帮助DBA团队安全高效地将备库转为独立生产库。

weixin_29233333的博客 234

oracle DataGuard 主从 踩过坑的

一、主机描述 dbprimary: 192.168.1.57 主机名称db1 dbstandby: 192.168.1.58 主机名成db2 SID: orcl 二、配置tns,配置好的文件内容: dbprimary的listener.ora (/db/app/oracle/product/11.2.0/network/admi目录下): # Generated b...

weixin_33716941的博客 244

Oracle DataGuard实战:遇到ORA-00235错误怎么办?11g/12c避坑指南

本文深入解析了Oracle DataGuard环境中常见的ORA-00235错误。该错误通常由控制文件的并发更新引起,尤其在11g和12c版本中,其性质与官方建议有所不同。文章提供了详细的诊断流程与应急处理指南,帮助DBA快速判断其是否为可安全忽略的“良性噪音”,并给出优化监控告警的实用建议,确保数据安全体系稳定运行。

smartcontract5的博客 234

oracle 12C dataguard入坑笔记

12c DATAGUARD是在cdb级别的,其管理操作如应用日志等也是需要在cdb容器中执行。 在使用grid、asm、omf时可能会遇到的坑: 1、监听文件(listener.ora)中$ORACLE_HOME参数修改为oracle用户的$ORACLE_HOME值(例如/u01/app/oracle/product/12.2.0/dbhome_1),否则会一直报用户名密码错误。 2、避免om...

jxayxcj的专栏 249

Oracle 19c DataGuard配置避坑实录:从归档模式到网络配置,手把手解决‘ORA-28040’等常见报错

本文详细解析了Oracle 19c DataGuard配置过程中的常见问题与解决方案,包括归档模式设置、参数配置陷阱、ORA-28040错误处理等关键环节。通过实战案例和最佳实践,帮助DBA避开配置雷区,确保高可用架构的稳定运行。特别针对网络配置和性能优化提供了专业建议,助力企业构建可靠的数据库灾备体系。

java 学习 401

Oracle DataGuard自动切换实战:从配置到故障恢复

本文详细介绍了Oracle DataGuard实现自动切换的完整实战流程。通过配置DataGuard Broker和快速启动故障切换(FSFO),系统能在主库故障时自动将备库提升为新主库,将业务中断时间缩短至分钟级,极大保障了业务连续性。文章从环境检查、关键参数设置、监听配置到DGMGRL命令行操作,逐步解析了配置要点与常见错误排查方法。

weixin_29210759的博客 202

Oracle 19c DataGuard实战:从静默安装到主备同步,保姆级避坑指南

本文详细介绍了Oracle 19c DataGuard的实战部署,从静默安装到主备同步的全过程,特别针对配置中的常见问题提供了解决方案。通过环境准备、主备库配置、同步验证及高级调优技巧,帮助用户快速搭建高可用数据库架构,确保数据安全与业务连续性。

java 学习 482

[模型部署]-[LLM]昇腾部署Qwen3-Coder-30B-A3B-Instruct

摘要:本文介绍了在Ascend NPU上部署Qwen3-Coder-30B-A3B-Instruct大模型的实践过程。通过vLLM-Ascend框架,详细说明了环境准备(CANN 8.1、PyTorch-NPU 2.5.1等)、模型下载、容器启动及服务部署步骤,包括vLLM服务的启动参数配置和接口测试方法。测试结果显示在当前2卡910B3配置下性能表现仅为8token/s(1并发),并指出流式调用时存在无法输出usage信息的问题。该方案为Ascend平台私有化部署大模型推理服务提供了参考实现。

1671

Linux下oracle 11g高可用DataGuard搭建-优快云公开课-专题视频课程

嘉宾:黄杉,08年进入数据库领域,从SQL Server2000开发管理,到成为MySQL DBA后兼管MongoDB、Redis、Memcache等。从事过电信号百、社区业务以及互联网电商和游戏行业,现在专注于互联网电商数据管理开发分析。...

csdngkk的博客 250

从手机到单片机:聊聊ARM Cortex家族那些事,A、R、M系列到底有啥不同?

本文深入解析ARM Cortex家族的A、R、M三大系列处理器,揭示它们在性能、实时响应和能效方面的核心差异。从智能手机到汽车电子和物联网设备,Cortex-A、R、M各司其职,分别应对复杂运算、实时控制和超低功耗场景。通过技术指标对比和典型应用案例,帮助开发者理解如何根据DMIPS/MHz等关键参数选择适合的处理器架构。

weixin_31574149的博客 350

智能车‘大脑’的诞生:揭秘电磁循迹代码背后的控制论与系统思维

本文深入探讨智能车电磁循迹系统的核心架构与控制原理,揭示了其作为精密闭环系统如何通过模块化设计、信号处理、PID控制算法及电机驱动实现自主导航。重点分析了电磁信号采集与处理流程框架,为开发者提供从理论到实践的全面指南。

arduino9maker的博客 531
上一篇: Oracle Linux 7.1在Vmware中安装12CR1 RAC的流程及常见问题解决
下一篇: oracle 12.1 RAC 无法用OEM启动pdb或添加备用库,关闭再打开浏览器即可。
typ2004
博客等级 码龄17年 48粉丝 74原创
评论 1
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明:

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

余额充值