Oracle GoldenGate 11gR2 Configuration On Oracle Database 11g_MySQL
Jun 01, 2016 pm 01:28 PM
bitsCN.com
Oracle GoldenGate 11gR2 Configuration On Oracle Database 11gR2 RAC ACFS
?
OracleOracle RACOracle ASMoracle goldengatesourceOracle 11gR2 RAC#public IP192.168.1.51 vzwc1192.168.1.52 vzwc2#private IP172.168.1.51 vzwc1-priv172.168.1.52 vzwc2-priv#VIP192.168.1.151 vzwc1-vip192.168.1.152 vzwc2-vip#scanip192.168.1.159 vzwc-cluster vzwc-cluster-scanTargetOracle 11gR2 single instance192.168.1.233 ggoson sourceCreate ASM volumes [grid@vzwc1 ~]$ asmcmd lsdg State Type Rebal Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files Name MOUNTED HIGH N 512 4096 1048576 5120 4024 2048 658 0 N CRSDG/ MOUNTED NORMAL N 512 4096 1048576 30720 26374 0 13187 0 N DATADG/ MOUNTED NORMAL N 512 4096 1048576 30720 29724 0 14862 0 N FRADG/ MOUNTED NORMAL N 512 4096 1048576 20480 20290 0 10145 0 N OGGDG/ MOUNTED HIGH N 512 4096 1048576 5120 3867 2048 606 0 Y SYSDG/ [grid@vzwc1 ~]$ sqlplus / as sysasm SQL*Plus: Release 11.2.0.4.0 Production on Wed Oct 16 15:48:20 2013 Copyright (c) 1982, 2013, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production With the Real Application Clusters and Automatic Storage Management options SQL> alter diskgroup oggdg add volume ggs size 8G; Diskgroup altered. Create the ACFS filesystem[grid@vzwc1 ~]$ /sbin/mkfs -t acfs -b 4k /dev/asm/ggs-11 mkfs.acfs: version = 11.2.0.4.0 mkfs.acfs: on-disk version = 39.0 mkfs.acfs: volume = /dev/asm/ggs-11 mkfs.acfs: volume size = 8589934592 mkfs.acfs: Format complete. Register the ASM Volume (ADVM) & ACFS filesystem in the Oracle Registry[grid@vzwc1 ~]$ /sbin/acfsutil registry -f -a /dev/asm/ggs-11 /ggs acfsutil registry: mount point /ggs successfully added to Oracle Registry As root user, please mount the ACFS filesystem on the ASM Volume (ADVM)[root@vzwc1 ~]# mount -t acfs /dev/asm/ggs-11 /ggs [root@vzwc1 ~]# chown -R oracle.oinstall /ggs [root@vzwc1 ~]# df -TH Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/VolGroup00-LogVol00 ext3 47G 18G 27G 40% / /dev/sda1 ext3 104M 25M 75M 25% /boot tmpfs tmpfs 1.6G 964M 617M 61% /dev/shm /dev/asm/ggs-11 acfs 8.6G 98M 8.5G 2% /ggs configuration GoldenGateadd supplemental log[oracle@vzwc1 ora]$ sqlplus / as sysdba SQL*Plus: Release 11.2.0.4.0 Production on Wed Oct 16 17:05:11 2013 Copyright (c) 1982, 2013, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP, Data Mining and Real Application Testing options SQL> ALTER DATABASE ADD SUPPLEMENTAL LOG DATA; Database altered. SQL> ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY) COLUMNS; Database altered. SQL> ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (UNIQUE) COLUMNS; Database altered. SQL> ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (FOREIGN KEY) COLUMNS; Database altered. SQL> ALTER SYSTEM SWITCH LOGFILE; System altered. Create DDL objectsSQL> GRANT EXECUTE ON UTL_FILE TO goldengate; Grant succeeded. SQL> GRANT CONNECT,RESOURCE,DBA TO goldengate; Grant succeeded. SQL> @marker_setup Marker setup script You will be prompted for the name of a schema for the Oracle GoldenGate database objects. NOTE: The schema must be created prior to running this script. NOTE: Stop all DDL replication before starting this installation. Enter Oracle GoldenGate schema name:goldengate Marker setup table script complete, running verification script... Please enter the name of a schema for the GoldenGate database objects: Setting schema name to GOLDENGATE MARKER TABLE ------------------------------- OK MARKER SEQUENCE ------------------------------- OK Script complete. SQL> @ddl_setup Oracle GoldenGate DDL Replication setup script Verifying that current user has privileges to install DDL Replication... You will be prompted for the name of a schema for the Oracle GoldenGate database objects. NOTE: For an Oracle 10g source, the system recycle bin must be disabled. For Oracle 11g and later, it can be enabled. NOTE: The schema must be created prior to running this script. NOTE: Stop all DDL replication before starting this installation. Enter Oracle GoldenGate schema name:goldengate Working, please wait ... Spooling to file ddl_setup_spool.txt Checking for sessions that are holding locks on Oracle Golden Gate metadata tables ... Check complete. WARNING: Tablespace GOLDENGATE does not have AUTOEXTEND enabled. Using GOLDENGATE as a Oracle GoldenGate schema name. Working, please wait ... DDL replication setup script complete, running verification script... Please enter the name of a schema for the GoldenGate database objects: Setting schema name to GOLDENGATE CLEAR_TRACE STATUS: Line/pos Error -------------------- ----------------------------------------------------------------- No errors No errors CREATE_TRACE STATUS: Line/pos Error -------------------- ----------------------------------------------------------------- No errors No errors TRACE_PUT_LINE STATUS: Line/pos Error -------------------- ----------------------------------------------------------------- No errors No errors INITIAL_SETUP STATUS: Line/pos Error -------------------- ----------------------------------------------------------------- No errors No errors DDLVERSIONSPECIFIC PACKAGE STATUS: Line/pos Error -------------------- ----------------------------------------------------------------- No errors No errors DDLREPLICATION PACKAGE STATUS: Line/pos Error -------------------- ----------------------------------------------------------------- No errors No errors DDLREPLICATION PACKAGE BODY STATUS: Line/pos Error -------------------- ----------------------------------------------------------------- No errors No errors DDL IGNORE TABLE ----------------------------------- OK DDL IGNORE LOG TABLE ----------------------------------- OK DDLAUX PACKAGE STATUS: Line/pos Error -------------------- ----------------------------------------------------------------- No errors No errors DDLAUX PACKAGE BODY STATUS: Line/pos Error -------------------- ----------------------------------------------------------------- No errors No errors SYS.DDLCTXINFO PACKAGE STATUS: Line/pos Error -------------------- ----------------------------------------------------------------- No errors No errors SYS.DDLCTXINFO PACKAGE BODY STATUS: Line/pos Error -------------------- ----------------------------------------------------------------- No errors No errors DDL HISTORY TABLE ----------------------------------- OK DDL HISTORY TABLE(1) ----------------------------------- OK DDL DUMP TABLES ----------------------------------- OK DDL DUMP COLUMNS ----------------------------------- OK DDL DUMP LOG GROUPS ----------------------------------- OK DDL DUMP PARTITIONS ----------------------------------- OK DDL DUMP PRIMARY KEYS ----------------------------------- OK DDL SEQUENCE ----------------------------------- OK GGS_TEMP_COLS ----------------------------------- OK GGS_TEMP_UK ----------------------------------- OK DDL TRIGGER CODE STATUS: Line/pos Error -------------------- ----------------------------------------------------------------- No errors No errors DDL TRIGGER INSTALL STATUS ----------------------------------- OK DDL TRIGGER RUNNING STATUS ---------------------------------------------------------------------- ENABLED STAYMETADATA IN TRIGGER ---------------------------------------------------------------------- OFF DDL TRIGGER SQL TRACING ---------------------------------------------------------------------- 0 DDL TRIGGER TRACE LEVEL ---------------------------------------------------------------------- 0 LOCATION OF DDL TRACE FILE ------------------------------------------------------------------------------------------------------------------------ /u01/app/oracle/diag/rdbms/zwc/zwc1/trace/ggs_ddl_trace.log Analyzing installation status... STATUS OF DDL REPLICATION ------------------------------------------------------------------------------------------------------------------------ SUCCESSFUL installation of DDL Replication software components Script complete. SQL> @role_setup GGS Role setup script This script will drop and recreate the role GGS_GGSUSER_ROLE To use a different role name, quit this script and then edit the params.sql script to change the gg_role parameter to the preferred name. (Do not run the script.) You will be prompted for the name of a schema for the GoldenGate database objects. NOTE: The schema must be created prior to running this script. NOTE: Stop all DDL replication before starting this installation. Enter GoldenGate schema name:goldengate Wrote file role_setup_set.txt PL/SQL procedure successfully completed. Role setup script complete Grant this role to each user assigned to the Extract, GGSCI, and Manager processes, by using the following SQL command: GRANT GGS_GGSUSER_ROLE TO <loggedUser> where <loggedUser> is the user assigned to the GoldenGate processes. SQL> grant GGS_GGSUSER_ROLE to goldengate; Grant succeeded. SQL> @ddl_enable Trigger altered. SQL> @ddl_pin goldengate PL/SQL procedure successfully completed. PL/SQL procedure successfully completed. PL/SQL procedure successfully completed. SQL> @sequence Please enter the name of a schema for the GoldenGate database objects: Setting schema name to GOLDENGATE UPDATE_SEQUENCE STATUS: Line/pos -------------------- Error ----------------------------------------------------------------- No errors No errors GETSEQFLUSH Line/pos -------------------- Error ----------------------------------------------------------------- No errors No errors SEQTRACE Line/pos -------------------- Error ----------------------------------------------------------------- No errors No errors REPLICATE_SEQUENCE STATUS: Line/pos -------------------- Error ----------------------------------------------------------------- No errors No errors STATUS OF SEQUENCE SUPPORT -------------------------------------------------------------- SUCCESSFUL installation of Oracle Sequence Replication support [oracle@vzwc1 ora]$ ./ggsci Oracle GoldenGate Command Interpreter for Oracle Version 11.2.1.0.8 17044551 OGGCORE_11.2.1.0.0OGGBP_PLATFORMS_130718.0526_FBO Linux, x64, 64bit (optimized), Oracle 11g on Jul 18 2013 10:34:27 Copyright (C) 1995, 2013, Oracle and/or its affiliates. All rights reserved. GGSCI (vzwc1) 1> view params mgr PORT 7839 DYNAMICPORTLIST 7840-7914 USERID goldengate, PASSWORD goldengate --AUTOSTART EXTRACT * AUTORESTART EXTRACT *,RETRIES 3,WAITMINUTES 5,RESETMINUTES 10 PURGEOLDEXTRACTS ./dirdat/*,usecheckpoints, minkeepdays 1 PURGEDDLHISTORY MINKEEPDAYS 3, MAXKEEPDAYS 5 PURGEMARKERHISTORY MINKEEPDAYS 3, MAXKEEPDAYS 5 LAGREPORTHOURS 1 LAGINFOMINUTES 30 LAGCRITICALMINUTES 45 config source extract groupGGSCI (vzwc1) 2> dblogin userid goldengate, password goldengate Successfully logged into database. GGSCI (vzwc1) 3> info trandata zwc.* Logging of supplemental redo log data is disabled for table ZWC.TAB1. GGSCI (vzwc1) 4> add trandata zwc.tab1 Logging of supplemental redo data enabled for table ZWC.TAB1. GGSCI (vzwc1) 5> info trandata zwc.tab1 Logging of supplemental redo log data is enabled for table ZWC.TAB1. Columns supplementally logged for table ZWC.TAB1: OBJECT_ID. GGSCI (vzwc1) 6> info trandata zwc.* Logging of supplemental redo log data is enabled for table ZWC.TAB1. Columns supplementally logged for table ZWC.TAB1: OBJECT_ID. GGSCI (vzwc1) 7> list tables * GOLDENGATE.GGS_DDL_COLUMNS GOLDENGATE.GGS_DDL_HIST GOLDENGATE.GGS_DDL_HIST_ALT GOLDENGATE.GGS_DDL_LOG_GROUPS GOLDENGATE.GGS_DDL_OBJECTS GOLDENGATE.GGS_DDL_PARTITIONS GOLDENGATE.GGS_DDL_PRIMARY_KEYS GOLDENGATE.GGS_DDL_RULES GOLDENGATE.GGS_DDL_RULES_LOG GOLDENGATE.GGS_MARKER GOLDENGATE.GGS_SETUP GOLDENGATE.GGS_STICK GOLDENGATE.GGS_TEMP_COLS GOLDENGATE.GGS_TEMP_UK Found 14 tables matching list criteria. GGSCI (vzwc1) 8> capture tabledef zwc.tab1 Table definitions for ZWC.TAB1: OWNER VARCHAR (30) OBJECT_NAME VARCHAR (128) SUBOBJECT_NAME VARCHAR (30) OBJECT_ID NUMBER NOT NULL PK DATA_OBJECT_ID NUMBER OBJECT_TYPE VARCHAR (19) CREATED DATETIME LAST_DDL_TIME DATETIME TIMESTAMP VARCHAR (19) STATUS VARCHAR (7) TEMPORARY VARCHAR (1) GENERATED VARCHAR (1) SECONDARY VARCHAR (1) NAMESPACE NUMBER EDITION_NAME VARCHAR (30) GGSCI (vzwc1) 9> create a primary Extract group exta,and local trail file[oracle@vzwc1 ora]$ ./ggsci Oracle GoldenGate Command Interpreter for Oracle Version 11.2.1.0.8 17044551 OGGCORE_11.2.1.0.0OGGBP_PLATFORMS_130718.0526_FBO Linux, x64, 64bit (optimized), Oracle 11g on Jul 18 2013 10:34:27 Copyright (C) 1995, 2013, Oracle and/or its affiliates. All rights reserved. GGSCI (vzwc1) 1> dblogin userid goldengate, password goldengate Successfully logged into database. GGSCI (vzwc1) 2> add extract exta, tranlog, begin now, threads 2 EXTRACT added. GGSCI (vzwc1) 3> add exttrail ./dirdat/ea, extract exta EXTTRAIL added. GGSCI (vzwc1) 4> info all Program Status Group Lag at Chkpt Time Since Chkpt MANAGER RUNNING EXTRACT STOPPED EXTA 00:00:00 00:03:31 GGSCI (vzwc1) 13> view params exta EXTRACT exta setenv (NLS_LANG=AMERICAN_AMERICA.ZHS16GBK) setenv (ORACLE_HOME="/u01/app/oracle/product/11.2.0/dbhome_1") --setenv (ORACLE_SID="VRAC1") USERID goldengate@zwc, PASSWORD goldengate --cachemgr cachedirectory ./dirtmp 100MB, CacheDirectory /ggs --DDL Include Mapped DDL INCLUDE OBJNAME "ZWC.*" EXCLUDE INSTR 'CREATE TRIGGER' DDLOPTIONS ADDTRANDATA NOCROSSRENAME REPORT TRANLOGOPTIONS RAWDEVICEOFFSET 0 REPORTCOUNT EVERY 1 MINUTES, RATE DISCARDFILE ./dirrpt/exta.dsc,APPEND,MEGABYTES 1024 DBOPTIONS ALLOWUNUSEDCOLUMN WARNLONGTRANS 5h,CHECKINTERVAL 30m EXTTRAIL ./dirdat/ea FETCHOPTIONS NOUSESNAPSHOT --tranlogoptions altarchivelogdest instance zwc1 /ggs TranLogOptions ExcludeUser goldengate TRANLOGOPTIONS DBLOGREADER ThreadOptions MaxCommitPropagationDelay 10000 IOLatency 3000 TRANLOGOPTIONS _INFINITYTOZERO TranlogOptions ASMUser sys@asm , asmpassword oracle TRANLOGOPTIONS CONVERTUCS2CLOBS --exclude report-- TABLEEXCLUDE ZWC.TAB2; TABLE ZWC.*; Create data pump groupGGSCI (vzwc1) 14> add extract pumpa, exttrailsource ./dirdat/ea, begin now EXTRACT added. add remote trail fileGGSCI (vzwc1) 15> add rmttrail ./dirdat/ra, extract pumpa RMTTRAIL added. GGSCI (vzwc1) 4> view params pumpa EXTRACT pumpa RMTHOST 192.168.1.233, MGRPORT 7839 RMTTRAIL /ggs/ora/dirdat/ra PASSTHRU TABLEEXCLUDE ZWC.TAB2; TABLE ZWC.*; "oracle" user tnsnames.oraASM = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = vzwc1-vip)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = +ASM) (INSTANCE_NAME = +ASM1) (UR=A) ) ) --on node2 tnsnames.ora ASM = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = vzwc2-vip)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = +ASM) (INSTANCE_NAME = +ASM2) (UR=A) ) ) on targetSQL> @sequence.sql Please enter the name of a schema for the GoldenGate database objects: goldengate Setting schema name to GOLDENGATE UPDATE_SEQUENCE STATUS: Line/pos -------------------- Error ----------------------------------------------------------------- No errors No errors GETSEQFLUSH Line/pos -------------------- Error ----------------------------------------------------------------- No errors No errors SEQTRACE Line/pos -------------------- Error ----------------------------------------------------------------- No errors No errors REPLICATE_SEQUENCE STATUS: Line/pos -------------------- Error ----------------------------------------------------------------- No errors No errors STATUS OF SEQUENCE SUPPORT -------------------------------------------------------------- SUCCESSFUL installation of Oracle Sequence Replication support create mgrGGSCI (ggos) 6> view params mgr PORT 7839 DYNAMICPORTLIST 7840-7914 USERID goldengate, PASSWORD goldengate --AUTOSTART REPLICAT * AUTORESTART REPLICAT *, RETRIES 5, WAITMINUTES 3 PURGEOLDEXTRACTS ./dirdat/*,USECHECKPOINTS, MINKEEPDAYS 10 LAGREPORTHOURS 1 LAGINFOMINUTES 30 LAGCRITICALMINUTES 45 create replicat groupGGSCI (ggos) 8> add replicat repa, exttrail ./dirdat/ra, nodbcheckpoint REPLICAT added. GGSCI (ggos) 12> view params repa REPLICAT repa setenv (NLS_LANG=AMERICAN_AMERICA.ZHS16GBK) setenv (ORACLE_SID="oraprod") setenv (ORACLE_HOME="/u01/app/oracle/product/11.2.0/dbhome_1") USERID goldengate, PASSWORD goldengate --DDLOPTIONS MAPSESSIONSCHEMA ZWC TARGET ZHONGWC DDL include mapped ddloptions report ddlerror 30568, ignore ddlerror 942, ignore ddlerror 955, ignore ddlerror 1430, ignore ddlerror 54,ignore ddlerror 904,ignore ddlerror 4081,ignore ddlerror 1418,ignore REPORT AT 01:59 REPORTCOUNT EVERY 30 MINUTES, RATE REPERROR DEFAULT, ABEND HANDLECOLLISIONS assumetargetdefs DISCARDFILE ./dirrpt/repa.dsc, PURGE, MEGABYTES 1024 DISCARDROLLOVER AT 02:30 ALLOWNOOPUPDATES GROUPTRANSOPS 2000 BATCHSQL MAPEXCLUDE ZWC.TAB2; MAP ZWC.*, TARGET ZWC.*; --MAP ZWC.*, TARGET ZHONGWC.* ,filter (@range (1, 6)); check source/target statusGGSCI (vzwc1) 1> info all Program Status Group Lag at Chkpt Time Since Chkpt MANAGER RUNNING EXTRACT RUNNING EXTA 00:00:00 00:00:00 EXTRACT RUNNING PUMPA 00:00:00 00:00:06 GGSCI (ggos) 1> info all Program Status Group Lag at Chkpt Time Since Chkpt MANAGER RUNNING REPLICAT RUNNING REPA 00:00:00 00:00:01
?
bitsCN.com
Hot AI Tools
Undress AI Tool
Undress images for free
Undresser.AI Undress
AI-powered app for creating realistic nude photos
AI Clothes Remover
Online AI tool for removing clothes from photos.
Clothoff.io
AI clothes remover
Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!
Hot Article
Hot Tools
Notepad++7.3.1
Easy-to-use and free code editor
SublimeText3 Chinese version
Chinese version, very easy to use
Zend Studio 13.0.1
Powerful PHP integrated development environment
Dreamweaver CS6
Visual web development tools
SublimeText3 Mac version
God-level code editing software (SublimeText3)
Hot Topics
What is GTID (Global Transaction Identifier) and what are its advantages?
Jun 19, 2025 am 01:03 AM
GTID (Global Transaction Identifier) ??solves the complexity of replication and failover in MySQL databases by assigning a unique identity to each transaction. 1. It simplifies replication management, automatically handles log files and locations, allowing slave servers to request transactions based on the last executed GTID. 2. Ensure consistency across servers, ensure that each transaction is applied only once on each server, and avoid data inconsistency. 3. Improve troubleshooting efficiency. GTID includes server UUID and serial number, which is convenient for tracking transaction flow and accurately locate problems. These three core advantages make MySQL replication more robust and easy to manage, significantly improving system reliability and data integrity.
What is a typical process for MySQL master failover?
Jun 19, 2025 am 01:06 AM
MySQL main library failover mainly includes four steps. 1. Fault detection: Regularly check the main library process, connection status and simple query to determine whether it is downtime, set up a retry mechanism to avoid misjudgment, and can use tools such as MHA, Orchestrator or Keepalived to assist in detection; 2. Select the new main library: select the most suitable slave library to replace it according to the data synchronization progress (Seconds_Behind_Master), binlog data integrity, network delay and load conditions, and perform data compensation or manual intervention if necessary; 3. Switch topology: Point other slave libraries to the new master library, execute RESETMASTER or enable GTID, update the VIP, DNS or proxy configuration to
How to connect to a MySQL database using the command line?
Jun 19, 2025 am 01:05 AM
The steps to connect to the MySQL database are as follows: 1. Use the basic command format mysql-u username-p-h host address to connect, enter the username and password to log in; 2. If you need to directly enter the specified database, you can add the database name after the command, such as mysql-uroot-pmyproject; 3. If the port is not the default 3306, you need to add the -P parameter to specify the port number, such as mysql-uroot-p-h192.168.1.100-P3307; In addition, if you encounter a password error, you can re-enter it. If the connection fails, check the network, firewall or permission settings. If the client is missing, you can install mysql-client on Linux through the package manager. Master these commands
Why is InnoDB the recommended storage engine now?
Jun 17, 2025 am 09:18 AM
InnoDB is MySQL's default storage engine because it outperforms other engines such as MyISAM in terms of reliability, concurrency performance and crash recovery. 1. It supports transaction processing, follows ACID principles, ensures data integrity, and is suitable for key data scenarios such as financial records or user accounts; 2. It adopts row-level locks instead of table-level locks to improve performance and throughput in high concurrent write environments; 3. It has a crash recovery mechanism and automatic repair function, and supports foreign key constraints to ensure data consistency and reference integrity, and prevent isolated records and data inconsistencies.
Why do indexes improve MySQL query speed?
Jun 19, 2025 am 01:05 AM
IndexesinMySQLimprovequeryspeedbyenablingfasterdataretrieval.1.Theyreducedatascanned,allowingMySQLtoquicklylocaterelevantrowsinWHEREorORDERBYclauses,especiallyimportantforlargeorfrequentlyqueriedtables.2.Theyspeedupjoinsandsorting,makingJOINoperation
What are the transaction isolation levels in MySQL, and which is the default?
Jun 23, 2025 pm 03:05 PM
MySQL's default transaction isolation level is RepeatableRead, which prevents dirty reads and non-repeatable reads through MVCC and gap locks, and avoids phantom reading in most cases; other major levels include read uncommitted (ReadUncommitted), allowing dirty reads but the fastest performance, 1. Read Committed (ReadCommitted) ensures that the submitted data is read but may encounter non-repeatable reads and phantom readings, 2. RepeatableRead default level ensures that multiple reads within the transaction are consistent, 3. Serialization (Serializable) the highest level, prevents other transactions from modifying data through locks, ensuring data integrity but sacrificing performance;
What are the ACID properties of a MySQL transaction?
Jun 20, 2025 am 01:06 AM
MySQL transactions follow ACID characteristics to ensure the reliability and consistency of database transactions. First, atomicity ensures that transactions are executed as an indivisible whole, either all succeed or all fail to roll back. For example, withdrawals and deposits must be completed or not occur at the same time in the transfer operation; second, consistency ensures that transactions transition the database from one valid state to another, and maintains the correct data logic through mechanisms such as constraints and triggers; third, isolation controls the visibility of multiple transactions when concurrent execution, prevents dirty reading, non-repeatable reading and fantasy reading. MySQL supports ReadUncommitted and ReadCommi.
How to add the MySQL bin directory to the system PATH
Jul 01, 2025 am 01:39 AM
To add MySQL's bin directory to the system PATH, it needs to be configured according to the different operating systems. 1. Windows system: Find the bin folder in the MySQL installation directory (the default path is usually C:\ProgramFiles\MySQL\MySQLServerX.X\bin), right-click "This Computer" → "Properties" → "Advanced System Settings" → "Environment Variables", select Path in "System Variables" and edit it, add the MySQLbin path, save it and restart the command prompt and enter mysql--version verification; 2.macOS and Linux systems: Bash users edit ~/.bashrc or ~/.bash_
