Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 
 Home
 E-mail Us
 Oracle Articles
New Oracle Articles


 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog


 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Analysis
 Design
 Implementation
 Oracle Support


 SQL Tuning
 Security

 Oracle UNIX
 Oracle Linux
 Monitoring
 Remote s
upport
 Remote plans
 Remote
services
 Application Server

 Applications
 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S
upport  
 Development  

 Implementation


 Consulting Staff
 Consulting Prices
 Help Wanted!

 


 Oracle Posters
 Oracle Books

 Oracle Scripts
 Ion
 Excel-DB  

Don Burleson Blog 


 

 

 


 

 

 
 

OGG-01296 Error mapping from tips

Oracle Database Tips by Donald BurlesonMarch 25, 2016

Question:  I started the GoldenGate replicat in target then I get the OGG-01296 error below:

OGG-01296 Error mapping from xxx to yyy

How do I fix the OGG-01296 error?

Answer:  The OGG-01296 error is caused my several things:

- Missing indexes:  We have created all the indexes on the target side (Replicat database) for the table.

- Non matching table columns:  The columns must match in both tables (source and target)

- Missing PK constraints:  All constraints must match on target and source.

 In sum, the OGG-01296 is when there is a mismatch between the structure of the tables in source and target, making the mapping fail.  The OGG-01296 is also fixed by adding TRANDATA for the table for the keycols. You can also fix the OGG-01296 by the source for primary key or unique columns and add the same to replicat param file and restart it

GoldenGate builds a pseudo key out of the entire row in the absence of a declared PK or UI, so for the source, the key is all the table columns.

For the target, the key becomes all of the target columns, including the ones that are only in the target and not in the source. So when an Update or Delete DML comes through GoldenGate from the source, there's no values for those last few columns in the target to satisfy the WHERE condition because those columns don't exist on the source.

If your source and target tables are different structures, you should use SOURCEDEFS instead of ASSUMETARGETDEFS, and you will need a DEFSFILE from the source and placed in the target

   
Oracle Training from Don Burleson 

The best on site "Oracle training classes" are just a phone call away! You can get personalized Oracle training by Donald Burleson, right at your shop!

Oracle training
 
 


 

 

Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


                    









Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


 

Copyright © 1996 -  2017

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.

Remote Emergency Support provided by Conversational

 

 

��  
 
 
Oracle Training at Sea
 
 
 
 
oracle dba poster
 

 
Follow us on Twitter 
 
Oracle performance tuning software 
 
Oracle Linux poster