GoldenGate不使用数据泵完成Oracle-Oracle的双向复制
配置数据库环境、goldengate用户,安装goldengate等操作,不使用数据泵完成Oracle-Oracle的双向复制所需的配置:--我这里只配置同
配置数据库环境、goldengate用户,安装goldengate等操作,参考不使用数据泵完成Oracle-Oracle的双向复制所需的配置:--我这里只配置同步test用户的 test1表。
1.主库的配置:
#####配置Extract
按顺序执行以下操作:
add extract ext1,tranlog, begin now
add exttrail /u01/ogg/dirdat/lt, extract ext1
edit params ext1
在打开的编辑窗口写入以下:----这里使用为OGG创建的用户来登陆,同时要注意路径的对照。
extract ext1
userid ogg, password ogg
rmthost 192.168.1.213, mgrport 7809
rmttrail /u01/ogg/dirdat/lt
table test.*;
#####配置Replicat
edit params ./GLOBAL
在编辑窗口输入以下两行:
GGSCHEMA ogg
CHECKPOINTTABLE ogg.checkpoint
dblogin userid ogg,password ogg
add checkpointtable ogg.checkpoint
add replicat rep2,exttrail /u01/ogg/dirdat/at, checkpointtable ogg.checkpoint
edit params rep2
在弹出编辑窗口输入:---我这里只设置了同步test用户的test1表--这里的用户和表名在下一步的测试中再建立。
可以使用handlecollisions参数,避免主库与目标库所需要同步的表中数据不一致导致的接收进程挂起。
replicat rep2
handlecollisions
ASSUMETARGETDEFS
userid ogg,password ogg
discardfile /u01/ogg/dirdat/rep2_discard.txt,append, megabytes 10
map test.test1, target test.test1;
配置完成后的进程如下:--注意我这里的进程状态是启动后的。--建议主库及目标库都配置进程完成后再启动。
GGSCI (bys001.oel.com) 11> info all
Program Status Group Lag at Chkpt Time Since Chkpt
MANAGER RUNNING
EXTRACT RUNNING EXT1 00:00:00 00:00:00
REPLICAT RUNNING REP2 00:00:00 00:00:02
2.目标库的配置
#####配置Replicat
edit params ./GLOBAL
在编辑窗口输入以下两行:
GGSCHEMA ogg
CHECKPOINTTABLE ogg.checkpoint
逐次输入以下命令:
dblogin userid ogg,password ogg
add checkpointtable ogg.checkpoint
add replicat rep1,exttrail /u01/ogg/dirdat/lt, checkpointtable ogg.checkpoint
edit params rep1
在弹出编辑窗口输入以下:---我这里只设置了同步test用户的test1表--这里的用户和表名在下一步的测试中再建立。
replicat rep1
handlecollisions
ASSUMETARGETDEFS
userid ogg,password ogg
discardfile /u01/ogg/dirdat/rep1_discard.txt,append, megabytes 10
map test.test1, target test.test1;
#####配置Extract
按顺序执行以下命令:
add extract ext2,tranlog, begin now
add exttrail /u01/ogg/dirdat/at, extract ext2
edit params ext2
在打开的编辑窗口写入:
extract ext2
TRANLOGOPTIONS EXCLUDEUSER ogg
userid ogg, password ogg
rmthost 192.168.1.211, mgrport 7809
rmttrail /u01/ogg/dirdat/at
table test.*;
配置完成后的进程如下:--注意我这里的进程状态是启动后的。
GGSCI (bys2.oel.com) 32> info all
Program Status Group Lag at Chkpt Time Since Chkpt
MANAGER RUNNING
EXTRACT RUNNING EXT2 00:00:00 00:00:07
REPLICAT RUNNING REP1 00:00:00 00:00:01

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

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

Full table scanning may be faster in MySQL than using indexes. Specific cases include: 1) the data volume is small; 2) when the query returns a large amount of data; 3) when the index column is not highly selective; 4) when the complex query. By analyzing query plans, optimizing indexes, avoiding over-index and regularly maintaining tables, you can make the best choices in practical applications.

Yes, MySQL can be installed on Windows 7, and although Microsoft has stopped supporting Windows 7, MySQL is still compatible with it. However, the following points should be noted during the installation process: Download the MySQL installer for Windows. Select the appropriate version of MySQL (community or enterprise). Select the appropriate installation directory and character set during the installation process. Set the root user password and keep it properly. Connect to the database for testing. Note the compatibility and security issues on Windows 7, and it is recommended to upgrade to a supported operating system.

InnoDB's full-text search capabilities are very powerful, which can significantly improve database query efficiency and ability to process large amounts of text data. 1) InnoDB implements full-text search through inverted indexing, supporting basic and advanced search queries. 2) Use MATCH and AGAINST keywords to search, support Boolean mode and phrase search. 3) Optimization methods include using word segmentation technology, periodic rebuilding of indexes and adjusting cache size to improve performance and accuracy.

The difference between clustered index and non-clustered index is: 1. Clustered index stores data rows in the index structure, which is suitable for querying by primary key and range. 2. The non-clustered index stores index key values and pointers to data rows, and is suitable for non-primary key column queries.

MySQL is an open source relational database management system. 1) Create database and tables: Use the CREATEDATABASE and CREATETABLE commands. 2) Basic operations: INSERT, UPDATE, DELETE and SELECT. 3) Advanced operations: JOIN, subquery and transaction processing. 4) Debugging skills: Check syntax, data type and permissions. 5) Optimization suggestions: Use indexes, avoid SELECT* and use transactions.

MySQL supports four index types: B-Tree, Hash, Full-text, and Spatial. 1.B-Tree index is suitable for equal value search, range query and sorting. 2. Hash index is suitable for equal value searches, but does not support range query and sorting. 3. Full-text index is used for full-text search and is suitable for processing large amounts of text data. 4. Spatial index is used for geospatial data query and is suitable for GIS applications.

In MySQL database, the relationship between the user and the database is defined by permissions and tables. The user has a username and password to access the database. Permissions are granted through the GRANT command, while the table is created by the CREATE TABLE command. To establish a relationship between a user and a database, you need to create a database, create a user, and then grant permissions.

MySQL and MariaDB can coexist, but need to be configured with caution. The key is to allocate different port numbers and data directories to each database, and adjust parameters such as memory allocation and cache size. Connection pooling, application configuration, and version differences also need to be considered and need to be carefully tested and planned to avoid pitfalls. Running two databases simultaneously can cause performance problems in situations where resources are limited.
