Subscribe to Posts by Email

Subscriber Count

    696

Disclaimer

All information is offered in good faith and in the hope that it may be of use for educational purpose and for Database community purpose, but is not guaranteed to be correct, up to date or suitable for any particular purpose. db.geeksinsight.com accepts no liability in respect of this information or its use. This site is independent of and does not represent Oracle Corporation in any way. Oracle does not officially sponsor, approve, or endorse this site or its content and if notify any such I am happy to remove. Product and company names mentioned in this website may be the trademarks of their respective owners and published here for informational purpose only. This is my personal blog. The views expressed on these pages are mine and learnt from other blogs and bloggers and to enhance and support the DBA community and this web blog does not represent the thoughts, intentions, plans or strategies of my current employer nor the Oracle and its affiliates or any other companies. And this website does not offer or take profit for providing these content and this is purely non-profit and for educational purpose only. If you see any issues with Content and copy write issues, I am happy to remove if you notify me. Contact Geek DBA Team, via geeksinsights@gmail.com

Pages

Example 8: Using Defgen Utility

It may be possible that some changes happen to table structure on target side, but this affects the replicat process.

For example, if a column name is changed in the replicat side itself and the primary column name is different then the replicat process will abended with error "invalid identifier"

In those cases, defgen utility will help to handle the column name changes.

Not only the above case, when you have structural changes between tables defgen utility can be used to create a COLMAP information.

First lets create a DDL information using defgen utility on source side.

## Create a Defgen Parameter file

EDIT PARAMS defgen

DEFSFILE I:\ggs_source\dirsql\def.sql

USERID ggs_owner, PASSWORD ggs_owner

TABLE test.myobj;

## Using Defgen utitlty create the sql file

./defgen paramfile I:\ggs_source\dirprm\defgen.prm

## Copy the generated SQL file to target location

scp I:\ggs_source\dirsql\def.sql 192.168.56.109:/u01/ggt_target/dirsql/def.sql

On target side, Edit the Replicat parameter file to colmap the differences in column names

./ggsci

EDIT params rep2

##Edit and Add the Bold part of following lines to parameter file

REPLICAT rep2

SOURCEDEFS /u01/ggt_target/dirsql/def.sql

USERID ggs_owner, PASSWORD ggs_owner

MAP test.myobj, TARGET test.myobj, COLMAP (usedefaults,object_name=objname);

## Start the replicat

start replicat rep2

## Replication will proceed with out error