Oracle DG之--构建Physical Standby 系统环境: 操作系统: RedHat EL4 Oracle: Oracle 10.2.0.1.0 650) this.width=650;" src="http://www.68idc.cn/help/uploads/allimg/151111/121R54538-0.jpg" title="dg2.png" alt="wKioL1R28C2B7wXmAACOWpabg-4498.jpg
Oracle DG之--构建Physical Standby
系统环境:
操作系统: RedHat EL4
Oracle: Oracle 10.2.0.1.0
从以上图中所示:主库为bj(db_unique_name),备库为sh。
案例分析:
本案例采用RMAN Duplicate方式建立standby database。
一、配置主备库初始化参数
主库的初始化参数:initbj.ora
[oracle@ocmtest dbs]$ more initbj.ora *.audit_file_dest='/u01/app/oracle/admin/bj/adump' *.background_dump_dest='/u01/app/oracle/admin/bj/bdump' *.compatible='10.2.0.1.0' *.control_files='/u01/app/oracle/oradata/bj/control01.ctl','/u01/app/oracle/oradata/bj/control02.ctl','/u01/app/oracle/oradata/bj/control 03.ctl' *.core_dump_dest='/u01/app/oracle/admin/bj/cdump' *.db_block_size=8192 *.db_domain='' *.db_file_multiblock_read_count=16 *.db_name='bj' *.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area' *.db_recovery_file_dest_size=2147483648 *.dispatchers='(PROTOCOL=TCP) (SERVICE=bjXDB)' *.job_queue_processes=10 *.open_cursors=300 *.pga_aggregate_target=68157440 *.processes=150 *.remote_login_passwordfile='EXCLUSIVE' *.sga_target=205520896 *.undo_management='AUTO' *.undo_tablespace='UNDOTBS1' *.user_dump_dest='/u01/app/oracle/admin/bj/udump'
以下为DG配置参数:
DB_UNIQUE_NAME=bj LOG_ARCHIVE_CONFIG='DG_CONFIG=(bj,sh)' LOG_ARCHIVE_DEST_1='LOCATION=/u01/disk1/arch/bj/ VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=bj' LOG_ARCHIVE_DEST_2='SERVICE=sh LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=sh' LOG_ARCHIVE_DEST_STATE_1=ENABLE LOG_ARCHIVE_DEST_STATE_2=ENABLE REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE LOG_ARCHIVE_MAX_PROCESSES=3 FAL_SERVER=sh FAL_CLIENT=bj DB_FILE_NAME_CONVERT='/u01/app/oracle/oradata/sh/','/u01/app/oracle/oradata/bj/' LOG_FILE_NAME_CONVERT='/u01/app/oracle/oradata/sh/','/u01/app/oracle/oradata/bj/' STANDBY_FILE_MANAGEMENT=AUTO
备库的初始化参数:initsh.ora
[oracle@ocmtest1 dbs]$ more initsh.ora *.audit_file_dest='/u01/app/oracle/admin/sh/adump' *.background_dump_dest='/u01/app/oracle/admin/sh/bdump' *.compatible='10.2.0.1.0' *.control_file_record_keep_time=7 *.control_files='/u01/app/oracle/oradata/sh/control01.ctl','/u01/app/oracle/oradata/sh/control02.ctl','/u01/app/oracle/oradata/sh/control 03.ctl' *.core_dump_dest='/u01/app/oracle/admin/sh/cdump' *.db_block_size=8192 *.db_domain='' *.db_file_multiblock_read_count=16 *.DB_FILE_NAME_CONVERT='/u01/app/oracle/oradata/bj/','/u01/app/oracle/oradata/sh/' *.db_name='bj' *.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area' *.db_recovery_file_dest_size=2147483648 *.open_cursors=300 *.pga_aggregate_target=68157440 *.processes=150 *.REMOTE_LOGIN_PASSWORDFILE='EXCLUSIVE' *.sga_target=205520896 *.undo_management='AUTO' *.undo_tablespace='UNDOTBS1' *.user_dump_dest='/u01/app/oracle/admin/sh/udump'
以下为DG配置参数:
*.DB_UNIQUE_NAME='sh' *.FAL_CLIENT='sh' *.FAL_SERVER='bj' *.job_queue_processes=10 *.LOG_ARCHIVE_CONFIG='DG_CONFIG=(bj,sh)' *.LOG_ARCHIVE_DEST_1='LOCATION=/u01/disk1/arch/sh/ VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=sh' *.LOG_ARCHIVE_DEST_2='SERVICE=bj LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=bj' *.LOG_ARCHIVE_DEST_STATE_1='ENABLE' *.LOG_ARCHIVE_DEST_STATE_2='ENABLE' *.log_archive_format='arch_%t_%s_%r.log' *.LOG_ARCHIVE_MAX_PROCESSES=3 *.LOG_FILE_NAME_CONVERT='/u01/app/oracle/oradata/bj/','/u01/app/oracle/oradata/sh/' *.STANDBY_FILE_MANAGEMENT='AUTO'
二、在主库上建立standby 日志
对于默认的最大性能的保护方式,可以不用建立standby redo logfiles;但建立standby redo logfiles可以更好的保存redo log;standby redo日志组组数应等于或多于redo log,日志的大小应该一致。 SQL> alter database add standby logfile group 4 ('/u01/app/oracle/oradata/bj/redo04.log') size 50m; SQL> alter database add standby logfile group 5 ('/u01/app/oracle/oradata/bj/redo05.log.rdo') size 50m; SQL> alter database add standby logfile group 6 ('/u01/app/oracle/oradata/bj/redo06.log') size 50m;
三、在备库上建立相应目录:
[oracle@ocmtest1 dbs]$mkdir -p /u01/app/oracle/admin/sh/adump [oracle@ocmtest1 dbs]$mkdir -p /u01/app/oracle/admin/sh/udump [oracle@ocmtest1 dbs]$mkdir -p /u01/app/oracle/admin/sh/bdump [oracle@ocmtest1 dbs]$mkdir -p /u01/app/oracle/admin/sh/cdump [oracle@ocmtest1 dbs]$mkdir -p /u01/app/oracle/oradata/sh
四、在主库生成备库的controlfile和备份
1、数据库在mount 状态下 06:57:41 SQL> alter database create standby controlfile as '/home/oracle/std_control01.ctl'; 2、 将生成的控制文件,拷贝到备库相同的目录下 [oracle@ocmtest1 ~]$ scp /home/oracle/std_control01.ctl 192.168.8.86:/home/oracle 对主库进行备份 [oracle@ocmtest bj]$ rman target / Recovery Manager: Release 10.2.0.1.0 - Production on Wed Aug 31 10:55:55 2011 Copyright (c) 1982, 2005, Oracle. All rights reserved. connected to target database (not started) RMAN> run { 2> startup force mount; 3> backup database format='/u01/disk1/rman/bj/bj_%s.bak' plus archivelog; 4> alter database open; 5> }
五、在备库上Duplicate Database(备库启动到弄mount)
1)在备库上建立/u01/disk1/rman/bj目录 拷贝主库的备份到备库/u01/disk1/rman/bj目录(拷贝到相同的目录下) [oracle@ocmtest bj]$ scp /u01/disk1/rman/bj/bj_*.bak 192.168.8.86:/u01/disk1/rman/bj 2)配置Oracle network 因为,备库启动到no mount 状态,拒绝用户远程联机,所以采用静态注册,如下所示备库listenter [oracle@ocmtest1 admin]$ cat listener.ora # listener.ora Network Configuration File: /u01/app/oracle/product/10.2.0/db_1/network/admin/listener.ora # Generated by Oracle configuration tools. SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (SID_NAME = PLSExtProc) (ORACLE_HOME = /u01/app/oracle/product/10.2.0/db_1) (PROGRAM = extproc) ) (SID_DESC = (GLOBAL_DBNAME = bj) (ORACLE_HOME = /u01/app/oracle/product/10.2.0/db_1) (SID_NAME = bj) ) ) LISTENER = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = ocmtest1.51CTO提醒您,请勿滥发广告!)(PORT = 1521)) (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0)) ) ) 如下所示:主库的tnsnames文件: [oracle@ocmtest1 admin]$ [oracle@ocmtest admin]$ cat tnsnames.ora # tnsnames.ora Network Configuration File: /u01/app/oracle/product/10.2.0/db_1/network/admin/tnsnames.ora # Generated by Oracle configuration tools. BJ = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.8.84)(PORT = 1521)) ) (CONNECT_DATA = (SERVICE_NAME = bj) ) ) SH = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.8.86)(PORT = 1521)) ) (CONNECT_DATA = (SERVICE_NAME = sh) (UR=A) ;添加此项连接到静态注册的备库 ) ) 测试连接备库 [oracle@ocmtest bj]$ sqlplus sys/oracle@sh as sysdba SQL*Plus: Release 10.2.0.1.0 - Production on Wed Aug 31 11:19:32 2011 Copyright (c) 1982, 2005, Oracle. All rights reserved. Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production With the Partitioning, OLAP and Data Mining options SQL> exit Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production With the Partitioning, OLAP and Data Mining options 通过主库连接到备库,进行恢复(通过克隆方式建立备库) [oracle@ocmtest bj]$ rman target / Recovery Manager: Release 10.2.0.1.0 - Production on Wed Aug 31 11:19:36 2011 Copyright (c) 1982, 2005, Oracle. All rights reserved. connected to target database: BJ (DBID=1015723911) RMAN> connect auxiliary sys/oracle@sh; connected to auxiliary database: BJ (not mounted) RMAN> duplicate target database for standby; Starting Duplicate Db at 31-AUG-11 using target database control file instead of recovery catalog allocated channel: ORA_AUX_DISK_1 channel ORA_AUX_DISK_1: sid=155 devtype=DISK contents of Memory Script: { restore clone standby controlfile; sql clone 'alter database mount standby database'; } executing Memory Script Starting restore at 31-AUG-11 using channel ORA_AUX_DISK_1 channel ORA_AUX_DISK_1: restoring control file channel ORA_AUX_DISK_1: copied control file copy input filename=/home/oracle/stand.ctl output filename=/u01/app/oracle/oradata/sh/control01.ctl output filename=/u01/app/oracle/oradata/sh/control02.ctl output filename=/u01/app/oracle/oradata/sh/control03.ctl Finished restore at 31-AUG-11 sql statement: alter database mount standby database released channel: ORA_AUX_DISK_1 contents of Memory Script: { set newname for tempfile 1 to "/u01/app/oracle/oradata/sh/temp01.dbf"; switch clone tempfile all; set newname for datafile 1 to "/u01/app/oracle/oradata/sh/system01.dbf"; set newname for datafile 2 to "/u01/app/oracle/oradata/sh/undotbs01.dbf"; set newname for datafile 3 to "/u01/app/oracle/oradata/sh/sysaux01.dbf"; set newname for datafile 4 to "/u01/app/oracle/oradata/sh/users01.dbf"; set newname for datafile 5 to "/u01/app/oracle/oradata/sh/example01.dbf"; restore check readonly clone database ; } executing Memory Script executing command: SET NEWNAME renamed temporary file 1 to /u01/app/oracle/oradata/sh/temp01.dbf in control file executing command: SET NEWNAME executing command: SET NEWNAME executing command: SET NEWNAME executing command: SET NEWNAME executing command: SET NEWNAME Starting restore at 31-AUG-11 allocated channel: ORA_AUX_DISK_1 channel ORA_AUX_DISK_1: sid=155 devtype=DISK channel ORA_AUX_DISK_1: starting datafile backupset restore channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set restoring datafile 00001 to /u01/app/oracle/oradata/sh/system01.dbf restoring datafile 00002 to /u01/app/oracle/oradata/sh/undotbs01.dbf restoring datafile 00003 to /u01/app/oracle/oradata/sh/sysaux01.dbf restoring datafile 00004 to /u01/app/oracle/oradata/sh/users01.dbf restoring datafile 00005 to /u01/app/oracle/oradata/sh/example01.dbf channel ORA_AUX_DISK_1: reading from backup piece /u01/disk1/rman/bj/bj_2.bak channel ORA_AUX_DISK_1: restored backup piece 1 piece handle=/u01/disk1/rman/bj/bj_2.bak tag=TAG20110831T105953 channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:48 Finished restore at 31-AUG-11 contents of Memory Script: { switch clone datafile all; } executing Memory Script datafile 1 switched to datafile copy input datafile copy recid=10 stamp=760621486 filename=/u01/app/oracle/oradata/sh/system01.dbf datafile 2 switched to datafile copy input datafile copy recid=11 stamp=760621487 filename=/u01/app/oracle/oradata/sh/undotbs01.dbf datafile 3 switched to datafile copy input datafile copy recid=12 stamp=760621487 filename=/u01/app/oracle/oradata/sh/sysaux01.dbf datafile 4 switched to datafile copy input datafile copy recid=13 stamp=760621487 filename=/u01/app/oracle/oradata/sh/users01.dbf datafile 5 switched to datafile copy input datafile copy recid=14 stamp=760621487 filename=/u01/app/oracle/oradata/sh/example01.dbf Finished Duplicate Db at 31-AUG-11
---备库建立完毕,并启动到mount状态!
六、在备库上启动MRP进程
11:40:28 SQL> SELECT status from v$instance; STATUS ------------ MOUNTED 11:45:40 SQL> alter database recover managed standby database disconnect from session; Database altered. 告警日志: alter database recover managed standby database disconnect from session Wed Aug 31 11:46:00 2011 Attempt to start background Managed Standby Recovery process (sh) MRP0 started with pid=22, OS id=14159 Wed Aug 31 11:46:01 2011 MRP0: Background Managed Standby Recovery process started (sh) Managed Standby Recovery not using Real Time Apply Wed Aug 31 11:46:06 2011 Errors in file /u01/app/oracle/admin/sh/bdump/sh_mrp0_14159.trc: ORA-00313: open failed for members of log group 1 of thread 1 ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/sh/redo01.log' ORA-27037: unable to obtain file status Linux Error: 2: No such file or directory Additional information: 3 Wed Aug 31 11:46:06 2011 Errors in file /u01/app/oracle/admin/sh/bdump/sh_mrp0_14159.trc: ORA-00313: open failed for members of log group 1 of thread 1 ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/sh/redo01.log' ORA-27037: unable to obtain file status Linux Error: 2: No such file or directory Additional information: 3 Clearing online redo logfile 1 /u01/app/oracle/oradata/sh/redo01.log Clearing online log 1 of thread 1 sequence number 23 Wed Aug 31 11:46:06 2011 Errors in file /u01/app/oracle/admin/sh/bdump/sh_mrp0_14159.trc: ORA-00313: open failed for members of log group 1 of thread 1 ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/sh/redo01.log' ORA-27037: unable to obtain file status Linux Error: 2: No such file or directory Additional information: 3 Wed Aug 31 11:46:07 2011 Completed: alter database recover managed standby database disconnect from session Wed Aug 31 11:46:08 2011 Clearing online redo logfile 1 complete Wed Aug 31 11:46:08 2011 Errors in file /u01/app/oracle/admin/sh/bdump/sh_mrp0_14159.trc: ORA-00313: open failed for members of log group 2 of thread 1 ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/sh/redo02.log' ORA-27037: unable to obtain file status Linux Error: 2: No such file or directory Additional information: 3 Wed Aug 31 11:46:08 2011 Errors in file /u01/app/oracle/admin/sh/bdump/sh_mrp0_14159.trc: ORA-00313: open failed for members of log group 2 of thread 1 ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/sh/redo02.log' ORA-27037: unable to obtain file status Linux Error: 2: No such file or directory Additional information: 3 Clearing online redo logfile 2 /u01/app/oracle/oradata/sh/redo02.log Clearing online log 2 of thread 1 sequence number 21 Wed Aug 31 11:46:08 2011 Errors in file /u01/app/oracle/admin/sh/bdump/sh_mrp0_14159.trc: ORA-00313: open failed for members of log group 2 of thread 1 ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/sh/redo02.log' ORA-27037: unable to obtain file status Linux Error: 2: No such file or directory Additional information: 3 Clearing online redo logfile 2 complete Wed Aug 31 11:46:09 2011 Errors in file /u01/app/oracle/admin/sh/bdump/sh_mrp0_14159.trc: ORA-00313: open failed for members of log group 3 of thread 1 ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/sh/redo03.log' ORA-27037: unable to obtain file status Linux Error: 2: No such file or directory Additional information: 3 Wed Aug 31 11:46:09 2011 Errors in file /u01/app/oracle/admin/sh/bdump/sh_mrp0_14159.trc: ORA-00313: open failed for members of log group 3 of thread 1 ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/sh/redo03.log' ORA-27037: unable to obtain file status Linux Error: 2: No such file or directory Additional information: 3 Clearing online redo logfile 3 /u01/app/oracle/oradata/sh/redo03.log Clearing online log 3 of thread 1 sequence number 22 Wed Aug 31 11:46:09 2011 Errors in file /u01/app/oracle/admin/sh/bdump/sh_mrp0_14159.trc: ORA-00313: open failed for members of log group 3 of thread 1 ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/sh/redo03.log' ORA-27037: unable to obtain file status Linux Error: 2: No such file or directory Additional information: 3 Clearing online redo logfile 3 complete Media Recovery Waiting for thread 1 sequence 23 Wed Aug 31 11:47:00 2011 Using STANDBY_ARCHIVE_DEST parameter default value as /u01/disk1/arch/sh/ Redo Shipping Client Connected as PUBLIC -- Connected User is Valid RFS[1]: Assigned to RFS process 14219 RFS[1]: Identified database type as 'physical standby' Wed Aug 31 11:47:00 2011 RFS LogMiner: Client disabled from further notification Wed Aug 31 11:47:01 2011 Redo Shipping Client Connected as PUBLIC -- Connected User is Valid RFS[2]: Assigned to RFS process 14221 RFS[2]: Identified database type as 'physical standby' Wed Aug 31 11:47:01 2011 RFS[1]: Archived Log: '/u01/disk1/arch/sh/arch_1_7_760458507.log' RFS[1]: Archived Log: '/u01/disk1/arch/sh/arch_1_8_760458507.log' Wed Aug 31 11:47:01 2011 RFS[2]: Archived Log: '/u01/disk1/arch/sh/arch_1_6_760458507.log' RFS[2]: Archived Log: '/u01/disk1/arch/sh/arch_1_10_760458507.log' Wed Aug 31 11:47:01 2011 RFS[1]: Archived Log: '/u01/disk1/arch/sh/arch_1_9_760458507.log' Wed Aug 31 11:47:02 2011 RFS[2]: Archived Log: '/u01/disk1/arch/sh/arch_1_11_760458507.log' Wed Aug 31 11:47:02 2011 RFS[1]: Archived Log: '/u01/disk1/arch/sh/arch_1_12_760458507.log' Wed Aug 31 11:47:02 2011 RFS[2]: Archived Log: '/u01/disk1/arch/sh/arch_1_13_760458507.log' Wed Aug 31 11:47:02 2011 RFS[1]: Archived Log: '/u01/disk1/arch/sh/arch_1_14_760458507.log' Wed Aug 31 11:47:02 2011 RFS[2]: Archived Log: '/u01/disk1/arch/sh/arch_1_15_760458507.log' Wed Aug 31 11:47:02 2011 RFS[1]: Archived Log: '/u01/disk1/arch/sh/arch_1_16_760458507.log' Wed Aug 31 11:47:03 2011 RFS[2]: Archived Log: '/u01/disk1/arch/sh/arch_1_17_760458507.log' Wed Aug 31 11:47:03 2011 RFS[1]: Archived Log: '/u01/disk1/arch/sh/arch_1_18_760458507.log' RFS[1]: Archived Log: '/u01/disk1/arch/sh/arch_1_19_760458507.log' Wed Aug 31 11:47:03 2011 RFS[2]: Archived Log: '/u01/disk1/arch/sh/arch_1_20_760458507.log' RFS[2]: Archived Log: '/u01/disk1/arch/sh/arch_1_22_760458507.log' Wed Aug 31 11:47:04 2011 RFS[1]: Archived Log: '/u01/disk1/arch/sh/arch_1_21_760458507.log' Wed Aug 31 11:47:04 2011 RFS[2]: Archived Log: '/u01/disk1/arch/sh/arch_1_24_760458507.log' RFS[2]: Archived Log: '/u01/disk1/arch/sh/arch_1_25_760458507.log' Wed Aug 31 11:47:05 2011 RFS[1]: Archived Log: '/u01/disk1/arch/sh/arch_1_23_760458507.log' Wed Aug 31 11:47:05 2011 RFS[2]: Archived Log: '/u01/disk1/arch/sh/arch_1_26_760458507.log' RFS[2]: Archived Log: '/u01/disk1/arch/sh/arch_1_27_760458507.log' Wed Aug 31 11:47:05 2011 RFS[1]: Archived Log: '/u01/disk1/arch/sh/arch_1_28_760458507.log' Wed Aug 31 11:47:05 2011 RFS[2]: Archived Log: '/u01/disk1/arch/sh/arch_1_29_760458507.log' Wed Aug 31 11:47:05 2011 Media Recovery Log /u01/disk1/arch/sh/arch_1_23_760458507.log Media Recovery Log /u01/disk1/arch/sh/arch_1_24_760458507.log Media Recovery Log /u01/disk1/arch/sh/arch_1_25_760458507.log Media Recovery Log /u01/disk1/arch/sh/arch_1_26_760458507.log Media Recovery Log /u01/disk1/arch/sh/arch_1_27_760458507.log Media Recovery Log /u01/disk1/arch/sh/arch_1_28_760458507.log Media Recovery Log /u01/disk1/arch/sh/arch_1_29_760458507.log Media Recovery Waiting for thread 1 sequence 30
七、在主库上切换日志测试数据同步
RMAN> sql'alter system switch logfile'; sql statement: alter system switch logfile 备库告警日志: RFS[1]: No standby redo logfiles created RFS[1]: Archived Log: '/u01/disk1/arch/sh/arch_1_30_760458507.log' Wed Aug 31 11:48:06 2011 Redo Shipping Client Connected as PUBLIC -- Connected User is Valid RFS[3]: Assigned to RFS process 14234 RFS[3]: Identified database type as 'physical standby' Primary database is in MAXIMUM PERFORMANCE mode Primary database is in MAXIMUM PERFORMANCE mode RFS[3]: No standby redo logfiles created Wed Aug 31 11:48:08 2011 Media Recovery Log /u01/disk1/arch/sh/arch_1_30_760458507.log Media Recovery Waiting for thread 1 sequence 31 (in transit) ---备库接收到归档日志,并对其做Media Recover。
八、查看数据库信息:
18:02:08 SYS@ bj >select name,database_role,protection_mode from v$database; NAME DATABASE_ROLE PROTECTION_MODE --------- ---------------- -------------------- BJ PRIMARY MAXIMUM PERFORMANCE 18:02:50 SYS@ sh >select name,database_role,protection_mode from v$database; NAME DATABASE_ROLE PROTECTION_MODE --------- ---------------- -------------------- BJ PHYSICAL STANDBY MAXIMUM PERFORMANCE
----@此案例采用Oracle 10g的环境,对于备库在recover状态下,只能启动到mount状态,如果启动到open环境,则会停止recover,失去了数据保护的功能;对于Oracle 11g,Oracle启用了新的特性,“Active Standby”,可以将备库启动到open状态,并且可以继续recover,从而增强了备库的应用范围和备库的功能。

InnoDB는 Redologs 및 Undologs를 사용하여 데이터 일관성과 신뢰성을 보장합니다. 1. Redologs는 사고 복구 및 거래 지속성을 보장하기 위해 데이터 페이지 수정을 기록합니다. 2. 결점은 원래 데이터 값을 기록하고 트랜잭션 롤백 및 MVCC를 지원합니다.

설명 명령에 대한 주요 메트릭에는 유형, 키, 행 및 추가가 포함됩니다. 1) 유형은 쿼리의 액세스 유형을 반영합니다. 값이 높을수록 Const와 같은 효율이 높아집니다. 2) 키는 사용 된 인덱스를 표시하고 NULL은 인덱스가 없음을 나타냅니다. 3) 행은 스캔 한 행의 수를 추정하여 쿼리 성능에 영향을 미칩니다. 4) Extra는 최적화해야한다는 Filesort 프롬프트 사용과 같은 추가 정보를 제공합니다.

Temporary를 사용하면 MySQL 쿼리에 임시 테이블을 생성해야 할 필요성이 있으며, 이는 별개의, 그룹 비 또는 비 인덱스 열을 사용하여 순서대로 발견됩니다. 인덱스 발생을 피하고 쿼리를 다시 작성하고 쿼리 성능을 향상시킬 수 있습니다. 구체적으로, 설명 출력에 사용되는 경우, MySQL은 쿼리를 처리하기 위해 임시 테이블을 만들어야 함을 의미합니다. 이것은 일반적으로 다음과 같은 경우에 발생합니다. 1) 별개 또는 그룹을 사용할 때 중복 제거 또는 그룹화; 2) OrderBy가 비 인덱스 열이 포함되어있을 때 정렬하십시오. 3) 복잡한 하위 쿼리 또는 조인 작업을 사용하십시오. 최적화 방법은 다음과 같습니다. 1) Orderby 및 GroupB

MySQL/InnoDB는 4 개의 트랜잭션 격리 수준을 지원합니다. Readuncommitted, ReadCommitted, ReturableRead 및 Serializable. 1. READUCMITTED는 커밋되지 않은 데이터를 읽을 수 있으므로 더러운 판독 값을 유발할 수 있습니다. 2. ReadCommitted는 더러운 읽기를 피하지만 반복 할 수없는 독서가 발생할 수 있습니다. 3. RepeatableRead는 더러운 읽기와 반복 할 수없는 독서를 피하는 기본 레벨이지만 팬텀 독서가 발생할 수 있습니다. 4. 직렬화 가능한 것은 모든 동시성 문제를 피하지만 동시성을 줄입니다. 적절한 격리 수준을 선택하려면 균형 잡힌 데이터 일관성 및 성능 요구 사항이 필요합니다.

MySQL은 웹 응용 프로그램 및 컨텐츠 관리 시스템에 적합하며 오픈 소스, 고성능 및 사용 편의성에 인기가 있습니다. 1) PostgreSQL과 비교하여 MySQL은 간단한 쿼리 및 높은 동시 읽기 작업에서 더 잘 수행합니다. 2) Oracle과 비교할 때 MySQL은 오픈 소스와 저렴한 비용으로 인해 중소 기업에서 더 인기가 있습니다. 3) Microsoft SQL Server와 비교하여 MySQL은 크로스 플랫폼 응용 프로그램에 더 적합합니다. 4) MongoDB와 달리 MySQL은 구조화 된 데이터 및 트랜잭션 처리에 더 적합합니다.

MySQL Index Cardinality는 쿼리 성능에 중대한 영향을 미칩니다. 1. 높은 카디널리티 인덱스는 데이터 범위를보다 효과적으로 좁히고 쿼리 효율성을 향상시킬 수 있습니다. 2. 낮은 카디널리티 인덱스는 전체 테이블 스캔으로 이어질 수 있으며 쿼리 성능을 줄일 수 있습니다. 3. 관절 지수에서는 쿼리를 최적화하기 위해 높은 카디널리티 시퀀스를 앞에 놓아야합니다.

MySQL 학습 경로에는 기본 지식, 핵심 개념, 사용 예제 및 최적화 기술이 포함됩니다. 1) 테이블, 행, 열 및 SQL 쿼리와 같은 기본 개념을 이해합니다. 2) MySQL의 정의, 작업 원칙 및 장점을 배우십시오. 3) 인덱스 및 저장 절차와 같은 기본 CRUD 작업 및 고급 사용량을 마스터합니다. 4) 인덱스의 합리적 사용 및 최적화 쿼리와 같은 일반적인 오류 디버깅 및 성능 최적화 제안에 익숙합니다. 이 단계를 통해 MySQL의 사용 및 최적화를 완전히 파악할 수 있습니다.

MySQL의 실제 응용 프로그램에는 기본 데이터베이스 설계 및 복잡한 쿼리 최적화가 포함됩니다. 1) 기본 사용 : 사용자 정보 삽입, 쿼리, 업데이트 및 삭제와 같은 사용자 데이터를 저장하고 관리하는 데 사용됩니다. 2) 고급 사용 : 전자 상거래 플랫폼의 주문 및 재고 관리와 같은 복잡한 비즈니스 로직을 처리합니다. 3) 성능 최적화 : 인덱스, 파티션 테이블 및 쿼리 캐시를 사용하여 합리적으로 성능을 향상시킵니다.


핫 AI 도구

Undresser.AI Undress
사실적인 누드 사진을 만들기 위한 AI 기반 앱

AI Clothes Remover
사진에서 옷을 제거하는 온라인 AI 도구입니다.

Undress AI Tool
무료로 이미지를 벗다

Clothoff.io
AI 옷 제거제

AI Hentai Generator
AI Hentai를 무료로 생성하십시오.

인기 기사

뜨거운 도구

SublimeText3 중국어 버전
중국어 버전, 사용하기 매우 쉽습니다.

Atom Editor Mac 버전 다운로드
가장 인기 있는 오픈 소스 편집기

VSCode Windows 64비트 다운로드
Microsoft에서 출시한 강력한 무료 IDE 편집기

스튜디오 13.0.1 보내기
강력한 PHP 통합 개발 환경

DVWA
DVWA(Damn Vulnerable Web App)는 매우 취약한 PHP/MySQL 웹 애플리케이션입니다. 주요 목표는 보안 전문가가 법적 환경에서 자신의 기술과 도구를 테스트하고, 웹 개발자가 웹 응용 프로그램 보안 프로세스를 더 잘 이해할 수 있도록 돕고, 교사/학생이 교실 환경 웹 응용 프로그램에서 가르치고 배울 수 있도록 돕는 것입니다. 보안. DVWA의 목표는 다양한 난이도의 간단하고 간단한 인터페이스를 통해 가장 일반적인 웹 취약점 중 일부를 연습하는 것입니다. 이 소프트웨어는
