Oracle10g Logical DataGuard 详细搭建过程

2024-02-01 08:48

本文主要是介绍Oracle10g Logical DataGuard 详细搭建过程,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

logical standby是在physical standby基础上搭建

Oracle10g Physical DataGuard 详细搭建过程


--停止standby上的日志应用

SQL> alter database recover managed standby database  cancel;


Database altered.



--修改主库log_archive_dest_3参数,当切换为备库时在线日志归档路径

SQL> alter system set log_archive_dest_3='LOCATION=/u01/app/oracle/oradata/dbserver/arch valid_for=(standby_logfiles,standby_role) db_unique_name=dbserver';


System altered.


SQL> alter system set log_archive_dest_state_3=enable;


System altered.


--主库执行,alert.log显示Logminer Bld: Done

SQL> execute dbms_logstdby.build;


PL/SQL procedure successfully completed.



--修改备库log_archive_dest_3参数,备库在线日志归档路径

SQL> alter system set log_archive_dest_3='LOCATION=/u01/app/oracle/oradata/standby/arch valid_for=(standby_logfiles,standby_role) db_unique_name=standby';


System altered.


SQL> alter system set log_archive_dest_state_3=enable;


System altered.


--如果备库没有临时表空间需要创建

--在standby端将物理备库转为逻辑备库,最后一个standby是逻辑备库名称

SQL> select status from v$instance;


STATUS
------------
MOUNTED


SQL> select database_role from v$database;


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


SQL> startup mount force
ORACLE instance started.


Total System Global Area  612368384 bytes
Fixed Size                  2085872 bytes
Variable Size             167775248 bytes
Database Buffers          436207616 bytes
Redo Buffers                6299648 bytes
Database mounted.
SQL> alter database recover to logical standby standby;


Database altered.


SQL> select status from v$instance;


STATUS
------------
STARTED


SQL> startup mount force
ORACLE instance started.


Total System Global Area  612368384 bytes
Fixed Size                  2085872 bytes
Variable Size             167775248 bytes
Database Buffers          436207616 bytes
Redo Buffers                6299648 bytes
Database mounted.
SQL> select database_role from v$database;


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


SQL> alter database open resetlogs;


Database altered.


SQL> select name from v$database;


NAME
---------
STANDBY



--在主库switch logfile

SQL> alter system switch logfile;


System altered.


SQL> /


System altered.


SQL> /


System altered.


SQL> /


System altered.


SQL> /


System altered.


SQL> /


System altered.



--standby alert.log

RFS[3]: Assigned to RFS process 10806
RFS[3]: Identified database type as 'logical standby'
Mon Mar  3 13:10:28 2014
RFS LogMiner: Client enabled and ready for notification
RFS[3]: Successfully opened standby log 6: '/u01/app/oracle/oradata/standby/standby03.log'
Mon Mar  3 13:10:28 2014
RFS LogMiner: Client enabled and ready for notification
Mon Mar  3 13:11:21 2014
RFS LogMiner: Client enabled and ready for notification
Mon Mar  3 13:11:22 2014
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 5: '/u01/app/oracle/oradata/standby/standby02.log'
Mon Mar  3 13:11:33 2014
RFS LogMiner: Client enabled and ready for notification
Mon Mar  3 13:11:34 2014
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 5: '/u01/app/oracle/oradata/standby/standby02.log'


--在备库启用实时应用

SQL> alter database start logical standby apply immediate;


Database altered.



--接下来就是测试了,在主库插入数据在备库查看是否同步,以下是备库的alert.log

RFS LogMiner: Registered logfile [/u01/app/oracle/oradata/standby/arch/ARC0000000136_0839199018.0001] to LogMiner session id [1]
LOGMINER: session# = 1, reader process P000 started with pid=40 OS id=10844
LOGMINER: session# = 1, builder process P001 started with pid=41 OS id=10846
LOGMINER: session# = 1, preparer process P002 started with pid=42 OS id=10848
Mon Mar  3 13:17:08 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 136, /u01/app/oracle/oradata/standby/arch/ARC0000000136_0839199018.0001
Mon Mar  3 13:17:08 2014
LOGMINER: Turning ON Log Auto Delete
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000136_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 137, /u01/app/oracle/oradata/standby/arch/ARC0000000137_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000137_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 138, /u01/app/oracle/oradata/standby/arch/ARC0000000138_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000138_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 139, /u01/app/oracle/oradata/standby/arch/ARC0000000139_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000139_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 140, /u01/app/oracle/oradata/standby/arch/ARC0000000140_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000140_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 141, /u01/app/oracle/oradata/standby/arch/ARC0000000141_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000141_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 142, /u01/app/oracle/oradata/standby/arch/ARC0000000142_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000142_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 143, /u01/app/oracle/oradata/standby/arch/ARC0000000143_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000143_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 144, /u01/app/oracle/oradata/standby/arch/ARC0000000144_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000144_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 145, /u01/app/oracle/oradata/standby/arch/ARC0000000145_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000145_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 146, /u01/app/oracle/oradata/standby/arch/ARC0000000146_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000146_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 147, /u01/app/oracle/oradata/standby/arch/ARC0000000147_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000147_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 148, /u01/app/oracle/oradata/standby/arch/ARC0000000148_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000148_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 149, /u01/app/oracle/oradata/standby/arch/ARC0000000149_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000149_0839199018.0001
LNS1 started with pid=43, OS id=10850
Mon Mar  3 13:17:17 2014
Thread 1 advanced to log sequence 2 (LGWR switch)
  Current log# 2 seq# 2 mem# 0: /u01/app/oracle/oradata/standby/redo02.log
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_ATTRCOL$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_CCOL$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_CDEF$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_COL$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_COLTYPE$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_ICOL$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_IND$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_INDCOMPART$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_INDPART$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_INDSUBPART$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_LOB$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_LOBFRAG$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_OBJ$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TAB$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TABCOMPART$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TABPART$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TABSUBPART$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TS$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TYPE$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_USER$ 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_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_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_OBJ$ 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
LSP2 started with pid=44, OS id=10853
Mon Mar  3 13:17:26 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 136, /u01/app/oracle/oradata/standby/arch/ARC0000000136_0839199018.0001
Mon Mar  3 13:17:26 2014
LOGMINER: Turning ON Log Auto Delete
LOGSTDBY Analyzer process P003 started with pid=45 OS id=10855
LOGSTDBY Apply process P006 started with pid=48 OS id=10861
LOGSTDBY Apply process P008 started with pid=50 OS id=10865
LOGSTDBY Apply process P007 started with pid=49 OS id=10863
LOGSTDBY Apply process P004 started with pid=46 OS id=10857
LOGSTDBY Apply process P005 started with pid=47 OS id=10859
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000136_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 137, /u01/app/oracle/oradata/standby/arch/ARC0000000137_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000137_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 138, /u01/app/oracle/oradata/standby/arch/ARC0000000138_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000138_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 139, /u01/app/oracle/oradata/standby/arch/ARC0000000139_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000139_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 140, /u01/app/oracle/oradata/standby/arch/ARC0000000140_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000140_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 141, /u01/app/oracle/oradata/standby/arch/ARC0000000141_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000141_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 142, /u01/app/oracle/oradata/standby/arch/ARC0000000142_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000142_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 143, /u01/app/oracle/oradata/standby/arch/ARC0000000143_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000143_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 144, /u01/app/oracle/oradata/standby/arch/ARC0000000144_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000144_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 145, /u01/app/oracle/oradata/standby/arch/ARC0000000145_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000145_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 146, /u01/app/oracle/oradata/standby/arch/ARC0000000146_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000146_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 147, /u01/app/oracle/oradata/standby/arch/ARC0000000147_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000147_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 148, /u01/app/oracle/oradata/standby/arch/ARC0000000148_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000148_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 149, /u01/app/oracle/oradata/standby/arch/ARC0000000149_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000149_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 150, /u01/app/oracle/oradata/standby/standby03.log
Mon Mar  3 13:18:05 2014
RFS LogMiner: RFS id [10797] assigned as thread [1] PING handler

这篇关于Oracle10g Logical DataGuard 详细搭建过程的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/666725

相关文章

Nginx中配置HTTP/2协议的详细指南

《Nginx中配置HTTP/2协议的详细指南》HTTP/2是HTTP协议的下一代版本,旨在提高性能、减少延迟并优化现代网络环境中的通信效率,本文将为大家介绍Nginx配置HTTP/2协议想详细步骤,需... 目录一、HTTP/2 协议概述1.HTTP/22. HTTP/2 的核心特性3. HTTP/2 的优

Java图片压缩三种高效压缩方案详细解析

《Java图片压缩三种高效压缩方案详细解析》图片压缩通常涉及减少图片的尺寸缩放、调整图片的质量(针对JPEG、PNG等)、使用特定的算法来减少图片的数据量等,:本文主要介绍Java图片压缩三种高效... 目录一、基于OpenCV的智能尺寸压缩技术亮点:适用场景:二、JPEG质量参数压缩关键技术:压缩效果对比

Java调用C++动态库超详细步骤讲解(附源码)

《Java调用C++动态库超详细步骤讲解(附源码)》C语言因其高效和接近硬件的特性,时常会被用在性能要求较高或者需要直接操作硬件的场合,:本文主要介绍Java调用C++动态库的相关资料,文中通过代... 目录一、直接调用C++库第一步:动态库生成(vs2017+qt5.12.10)第二步:Java调用C++

Python基础文件操作方法超详细讲解(详解版)

《Python基础文件操作方法超详细讲解(详解版)》文件就是操作系统为用户或应用程序提供的一个读写硬盘的虚拟单位,文件的核心操作就是读和写,:本文主要介绍Python基础文件操作方法超详细讲解的相... 目录一、文件操作1. 文件打开与关闭1.1 打开文件1.2 关闭文件2. 访问模式及说明二、文件读写1.

Ubuntu中远程连接Mysql数据库的详细图文教程

《Ubuntu中远程连接Mysql数据库的详细图文教程》Ubuntu是一个以桌面应用为主的Linux发行版操作系统,这篇文章主要为大家详细介绍了Ubuntu中远程连接Mysql数据库的详细图文教程,有... 目录1、版本2、检查有没有mysql2.1 查询是否安装了Mysql包2.2 查看Mysql版本2.

Oracle数据库常见字段类型大全以及超详细解析

《Oracle数据库常见字段类型大全以及超详细解析》在Oracle数据库中查询特定表的字段个数通常需要使用SQL语句来完成,:本文主要介绍Oracle数据库常见字段类型大全以及超详细解析,文中通过... 目录前言一、字符类型(Character)1、CHAR:定长字符数据类型2、VARCHAR2:变长字符数

Win11安装PostgreSQL数据库的两种方式详细步骤

《Win11安装PostgreSQL数据库的两种方式详细步骤》PostgreSQL是备受业界青睐的关系型数据库,尤其是在地理空间和移动领域,:本文主要介绍Win11安装PostgreSQL数据库的... 目录一、exe文件安装 (推荐)下载安装包1. 选择操作系统2. 跳转到EDB(PostgreSQL 的

Python3.6连接MySQL的详细步骤

《Python3.6连接MySQL的详细步骤》在现代Web开发和数据处理中,Python与数据库的交互是必不可少的一部分,MySQL作为最流行的开源关系型数据库管理系统之一,与Python的结合可以实... 目录环境准备安装python 3.6安装mysql安装pymysql库连接到MySQL建立连接执行S

将Mybatis升级为Mybatis-Plus的详细过程

《将Mybatis升级为Mybatis-Plus的详细过程》本文详细介绍了在若依管理系统(v3.8.8)中将MyBatis升级为MyBatis-Plus的过程,旨在提升开发效率,通过本文,开发者可实现... 目录说明流程增加依赖修改配置文件注释掉MyBATisConfig里面的Bean代码生成使用IDEA生

Linux系统配置NAT网络模式的详细步骤(附图文)

《Linux系统配置NAT网络模式的详细步骤(附图文)》本文详细指导如何在VMware环境下配置NAT网络模式,包括设置主机和虚拟机的IP地址、网关,以及针对Linux和Windows系统的具体步骤,... 目录一、配置NAT网络模式二、设置虚拟机交换机网关2.1 打开虚拟机2.2 管理员授权2.3 设置子