My Oracle Support Banner

Replicat Abending With OGG-01163 Bad Column Length - Source Is MS SQL Server (Doc ID 2456923.1)

Last updated on JANUARY 09, 2020

Applies to:

Oracle GoldenGate - Version to [Release 12.2 to 12.3]
Microsoft Windows x64 (64-bit)


Problem Summary
replicat abending with OGG-01163 Bad column length - source is MS SQL Server

Problem Description

Even though source column can only accept 10 characters, i am seeing 11 and 12 characters in logdump output.

It is causing replicat to abend with
OGG-01163 Bad column length (11) specified for column EEEE in table XXXX.YYYY, maximum allowable length is 10

Logdump 13948 >pos 12264874
Reading forward from RBA 12264874
Logdump 13949 >n

2018/09/10 15:33:02.247.240 Insert Len 1403 RBA 12264874
Name: XXXX.YYYY (TDR Index: 5)
After Image:

Column 58 (x003a), Len 15 (x000f)
0000 000b 3138 3435 3739 3439 3433 30 | ....18457949430

same issue for another table replication as well, source can only create 10 characters
even in source side, in trail file, i am seeing this 12 digit value, not sure how or why extract is extracting data wrongly

trail file, logdump output that replicates to teradata
2018/09/10 15:24:30.086.592 Insert Len 1404 RBA 7384725
Name: XXXX.YYYY (TDR Index: 4)

Column 58 (x003a), Len 16 (x0010)
0000 000c 3031 3939 3734 3032 3234 3230 | ....019974022420

trail file logdump output that extracts from ms sql server




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.