GoldenGate colmap issue about calculation

Question

Hi guys,
     I did some replication from oracle to SQL server.
   Source DB:  Oracle table:
create table myemps(
id number,
first_name varchar2(100),
last_name varchar2(100),
salary number
  Target DB:  SQL Server DB:
CREATE TABLE [dbo].[myemps](
  [id] [numeric](18, 0) NOT NULL,
  [full_name] [varchar](300) NULL,
  [wages] [numeric](18, 0) NULL,
  [first_name] [varchar](200) NULL,
  [last_name] [varchar](200) NULL,
PRIMARY KEY CLUSTERED
  [id] ASC
)WITH (PAD_INDEX  = OFF, STATISTICS_NORECOMPUTE  = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS  = ON, ALLOW_PAGE_LOCKS  = ON) ON [PRIMARY]
) ON [PRIMARY]
The replicat params:
   REPLICAT MSREP1
  targetdb ggs_nc
  GETTRUNCATES
  APPLYNOOPUPDATES
  SOURCEDEFS dirdef/source.def
  MAP scott.customer, TARGET dbo.customer;
  map scott.myemps, target dbo.myemps,
  COLMAP (USEDEFAULTS,
  WAGES = @COMPUTE(SALARY * 12)
  FULL_NAME = @STRCAT(LAST_NAME,",",FIRST_NAME));
  The problem is the updates on only first _name on Oracle, the updates won't reflect to full_name on SQL Server;
  Sample:
     I issued some SQL from Oracle:
insert into myemps(id,first_name,last_name,salary) values(2, 'A', 'B', 100000);
commit;
update myemps set first_name = 'CCCC' where id = 2;
commit;
After updates, the full_name on SQL Server should be 'B,CCCC', but it remains B,A.
Can anyone explain this?
Thanks.

Answer 1

I am guessing that it has something to do with not having all of the source columns with which to do the @STRCAT. If you did an ADD TRANDATA on the source table, then all that is getting passed in your update record to the Replicat is the key and the first_name column. But if first_name is updated, you also need last_name so that you can format the target full_name column correctly, and vice versa, because it needs to overwrite the entire full_name string. One way to accomplish this is to always supplementally log both first_name and last_name. That is overkill, but I don't think there is a way to tie supplemental logging of one column to another (i.e., to log last_name only when first_name is updated).
Best regards,
Marie