Shulou(Shulou.com)05/31 Report--

This article mainly introduces "Oracle GoldenGate configuration parameter analysis". In daily operation, I believe many people have doubts about Oracle GoldenGate configuration parameter analysis. The editor consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful for you to answer the doubts of "Oracle GoldenGate configuration parameter analysis". Next, please follow the editor to study!

Initiated process

GGSCI 3 > info all

Program Status Group Lag at Chkpt Time Since Chkpt

MANAGER RUNNING

REPLICAT RUNNING REPSA 00:00:00 00:00:09

REPLICAT RUNNING REPSB 00:00:00 00:00:08

REPLICAT RUNNING REPSC 00:00:00 00:00:08

REPLICAT RUNNING REPSD 00:00:00 00:00:09

REPLICAT RUNNING REPSE 00:00:00 00:00:08

REPLICAT RUNNING REPSF 00:00:00 00:00:08

REPLICAT RUNNING REPSG 00:00:00 00:00:08

REPLICAT RUNNING REPSH 00:00:00 00:00:08

REPLICAT RUNNING REPSI 00:00:00 00:00:09

REPLICAT RUNNING REPSJ 00:00:00 00:00:09

REPLICAT RUNNING REPSK 00:00:00 00:00:08

REPLICAT RUNNING REPSL 00:00:00 00:00:09

REPLICAT RUNNING REPSM 00:00:00 00:00:09

REPLICAT RUNNING REPSN 00:00:00 00:00:08

REPLICAT RUNNING REPSO 00:01:24 00:00:01

REPLICAT RUNNING REPSP 00:00:00 00:00:08

REPLICAT RUNNING REPSQ 00:00:00 00:00:09

REPLICAT RUNNING REPSR 00:00:00 00:00:09

A total of 18 processes in REPSA-R are replication processes on the disaster recovery side. Starting multiple replication processes can relieve the pressure caused by too many tables on the production side.

Management process

GGSCI 4 > view params mgr

PORT 7839

USERID goldengate, PASSWORD AACAAAAAAAAAAAJAPJYATHVIMGMAOFHIUCUEPFYGGJBFJGIH, ENCRYPTKEY default

DYNAMICPORTLIST 7840-7914

AUTORESTART EXTRACT *, RETRIES 5 WAITMINUTES 3

PURGEOLDEXTRACTS. / dirdat/*,usecheckpoints, minkeepdays 5

-- PURGEDDLHISTORY MINKEEPDAYS 7, MAXKEEPDAYS 10

-- PURGEMARKERHISTORY MINKEEPDAYS 7, MAXKEEPDAYS 10

LAGREPORTHOURS 1

LAGINFOMINUTES 30

LAGCRITICALMINUTES 45

PORT 7839

Communication port 7839. The production side and the disaster recovery side need to be consistent.

DYNAMICPORTLIST 7840-7914

The dynamic port list ranges from 7840 to 7914. When the established port is occupied or a communication failure occurs, the management process will select the next port from the list to try to connect to avoid a single point of failure of the communication port.

AUTORESTART EXTRACT *, RETRIES 5 WAITMINUTES 3

Try to restart automatically after the extraction process is interrupted, try to start every 7 minutes, try 5 times. OGG operators usually comment out this configuration and prefer to restart it manually.

PURGEOLDEXTRACTS. / dirdat/*, USECHECKPOINTS, MINKEEPDAYS 5

Periodically clean up the remote queue (remote trail) under the dirdat path. The retention period is 5 days and will be deleted automatically when it expires. As a result, the directory that controls the queue files will not grow too large.

-- PURGEDDLHISTORY MINKEEPDAYS 7, MAXKEEPDAYS 10

Delete DDL history table, with a minimum of 7 days and a maximum of 10 days. This parameter is annotated because DDL is not enabled for this project.

-- PURGEMARKERHISTORY MINKEEPDAYS 7, MAXKEEPDAYS 10

Delete MARKER history table, with a minimum of 7 days and a maximum of 10 days. This parameter is not used in this project, so it is commented.

LAGREPORTHOURS 1

Check the transmission delay every other hour

LAGINFOMINUTES 30

A transfer delay of more than 30 minutes will be written to the error log

LAGCRITICALMINUTES 45

If the transmission delay exceeds 45 minutes, the warning log will be written.

Replication process

GGSCI 6 > view params repsa

REPLICAT repsa

SETENV (NLS_LANG = "American_America.UTF8")

SETENV (ORACLE_SID = "xxxx")

USERID goldengate, PASSWORD AACAAAAAAAAAAAJAPJYATHVIMGMAOFHIUCUEPFYGGJBFJGIH, ENCRYPTKEY default

-SQLEXEC "ALTER SESSION SET CONSTRAINTS=DEFERRED"

DBOPTIONS DEFERREFCONST6 >

GETTRUNCATES

REPORT AT 06:00

REPORTCOUNT EVERY 30 MINUTES, RATE

REPORTROLLOVER AT 02:00

REPERROR DEFAULT, ABEND

-- HANDLECOLLISIONS

ALLOWNOOPUPDATES

Assumetargetdefs

DISCARDFILE. / dirrpt/repsa.dsc, APPEND, MEGABYTES 1024M

DISCARDROLLOVER AT 02:00

-Schema name involves sensitive characters. Here, Schema is used instead of

-table name involves sensitive characters. Here, table is used instead of

Map Schema1.table1, target Schema1.table1

Map Schema1.table2, target Schema1.table2

Map Schema2.table1, target Schema2.table1

Map Schema2.table2, target Schema2.table2

SETENV (NLS_LANG= "AMERICAN_AMERICA.UTF8")

Set the character set environment variable to UTF8

If there are multiple databases in the system, ORACLE_HOME, ORACLE_SID, etc., are sometimes set with the parameter SETENV, for example:

SETENV (ORACLE_HOME = "/ home/oracle/product/10.2.0/db)

SETENV (ORACLE_SID = "PROD")

DBOPTIONS DEFERREFCONST

Constraint delay setting. Delay the checksum implementation of cascading deletions and cascading updates before the replication process is submitted.

GETTRUNCATES

The operation of the production-side truncate table is not captured.

REPORT AT 06:00

Report at 6 o'clock every morning

REPORTCOUNT EVERY 30 MINUTES, RATE

Report the number of transaction records from the beginning of the program to the present extraction process or replication process every 30 minutes, and report the statistical information of the process

REPORTROLLOVER AT 02:00

To prevent the report file from being full, set the file expiration at 2:00 every day.

REPERROR DEFAULT, ABEND

Except for specially specified REPERROR statements, all errors that occur during replication are reported, and things and processes that are not normally interrupted are rolled back.

-HANDLECOLLISIONS

When the data already exists at the disaster recovery end, resolve the conflicts in the replication process. If you want to reinitialize, you can delete the database on the drop disaster recovery side and then restore it with rman. If you do so, you don't need this parameter.

ALLOWNOOPUPDATES

When the production side has certain columns but the target table does not, or the COLSEXCEPT parameter is configured during the replication process, when the production side updates those columns, the target table will not change.

Assumetargetdefs

When using the ASSUMETARGETDEFS parameter, the production database source table specified in the map statement and the disaster recovery destination table have the same column structure. The Oracle GoldenGate it indicates does not look up the structure definition of the source table on the production side.

DISCARDFILE. / dirrpt/repsa.dsc, APPEND, MEGABYTES 1024M

Save the record of the failed execution in discard file, which is located in. / dirrpt/extya.dsc and the size is 1024MB. If a record is already included in the file, it will be appended later without deleting the previous record.

DISCARDROLLOVER AT 02:00

To prevent the discard file from being full, set the file expiration at 2:00 every day.

At this point, the study of "Oracle GoldenGate configuration parameter analysis" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.