Home > database >  Online help great god solve the problem of the OGG, person, can give points immediately
Online help great god solve the problem of the OGG, person, can give points immediately

Time:09-18

Ogg installed after deployment and running normally, after a period of time the source side inside the database in a few tables added two fields, the target side through DDL after field synchronization over the new value-added synchronous mapping error, again using the add trandata table after log or error, beg god to help solve!!!!!!!!!!! Be urgent! Be urgent! Be urgent!

CodePudding user response:

The source database is oracle 10 g

CodePudding user response:

Error log, OGG to have open synchronous DDL, provide nothing is difficult to judge what problems
1. Open synchronous DDL, OGG so if manual synchronization of table structure first, so will be submitted to the field name already exist, such as error
2. OGG no open synchronous DDL, need to manually synchronize table structure
3.,,,,,,,,,,,,,,,,,,,,,,,,,,,,, is synchronous table structure, the data is not synchronous, before,

CodePudding user response:

refer to the second floor u012355452 response:
error log, OGG ever open synchronous DDL, provide nothing is difficult to judge what problems
1. Open synchronous DDL, OGG so if manual synchronization of table structure first, so will be submitted to the field name already exist, such as error
2. OGG no open synchronous DDL, need to manually synchronize table structure
3.,,,,,,,,,,,,,,,,,,,,,,,,,,,,, is synchronous table structure, before the data is not synchronized,,
DDL has opened the

CodePudding user response:

After the structure change of the source table, is the need to reconfigure the OGG,

CodePudding user response:

The first solution, manually in case library the same table with the same field, try to start the copy process,
The second solution, a few tables to resynchronize, extraction process to cancel the change table attached log delete trandata USERA. TABLEA, then to add trandata USERA. TABLEA, original copy process table changes to the comments first, and then a new replication process, separate synchronous changes in a few tables, catch up later, to stop the progress of the new added, uncomment the original copy process starts, if no problem, delete the new process, (recommended)
The second solution, delete synchronization table changes to the repository, and then create to the main library dblink, create materialized views, (simple solution, real time table can not high)