Veridata 12.1.3 Compare Job Fails OGGV-60038: Database Query Failed: 'Metric Value For End-To-End Tracing Is Too Long (Doc ID 1947518.1)

Last updated on MAY 27, 2023

Applies to:

Symptoms

Customer has got a veridata server:

Oracle GoldenGate Veridata
12.1.3.0.0 OGGVDT_12.1.3.0.0_PLATFORMS_140616.1904

The jagents for the 2 databases to compare are:

10g : OGGVDT_12.1.3.0.0_PLATFORMS_140616.1904 built on Mon, 16 Jun 2014 19:38:59 -0700
12g : OGGVDT_12.1.3.0.0_PLATFORMS_140616.1904 built on Mon, 16 Jun 2014 19:38:59 -0700

The error comes for the 10g database - veridata-agent_10g.log.gz :

[2014-10-31T17:29:51.675-07:00] [veridata] [ERROR] [OGGV-60038] [oracle.veridata.agent] [tid: 59]
[ecid: 84ad0fce-61eb-404a-b118-49c5b175efa9-000007ff,0:2994:2:14:1]

Database query failed: 'metric value for end-to-end tracing is too long: Table: HHXXX.XXX_ABC_XXX' SQL<select "XXX_PREF_XXX_ID", "XXX_XXX_ID", "XXX_GROUP_XXXX", "VALUE" from "HHXXX"."XXX_ABC_XXX" x order by "XXX_PREF_XXX_ID", "XXX_ABC_ID">

In the report files for the error:

rpt\CompareXXXX\00001007\HUQXXXX\CP_AXXX_ENT_XXX_CD=XXX_ENT_XXX_CD.rpt :

2014-11-01 13:29:31 OGGV-00119: Agent remote message (101): OGGV-60038: Database query failed: 'metric value for end-to-end tracing is too long: Table: HHXXX.ACNT_ENT_XXX_CD' SQL<select "AXXX_ID", "XXX_ENT_ROLE_CD", "XXX_ENT_XXX_CD", "XXX_ENT_XXX_NM", "XXX_ENT_SXXX_DESC" from "HHXXX"."XXX_ENT_XXX_CD" x order by "XXX_ID", "XXX_ENT_XXX_CD", "XXX_ENT_XXX_CD">

Cause

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