OMD API error

Tools
Enthusiast

OMD API error

We recently upgraded our TTU client on a Windows Data Services server from 14.00 to 14.10.  The TPT programs are patched to 14.10.00.05. 

The server is Windows Server 2008 Enterprise SP1 64-bit

The first TPTLoad tests produced the following warning:

         TPT_INFRA: TPT04190: Warning: OMD API failed to initialize

The entire out file consists of:

C:\Program Files (x86)\Teradata\Client\14.10\Teradata Parallel Transporter\logs>

tlogview -l STAGE_CORP_OAS_T_OAS_MATL_BUS_IMPACT_S1-2.out

TPT_INFRA: TPT04101: Warning: Teradata PT cannot connect to Unity EcoSysetm Mana

ger.

The job will continue without event messages being sent to Unity EcoSystem Manag

er.

TPT_INFRA: TPT04190: Warning: OMD API failed to initialize

Teradata Parallel Transporter Coordinator Version 14.10.00.05

Teradata Parallel Transporter Executor Version 14.10.00.05

Teradata Parallel Transporter Executor Version 14.10.00.05

Teradata Parallel Transporter Load Operator Version 14.10.00.05

load_opt: private log specified: pl_OAS_MATL_BUS_IMPACT_S1

Teradata Parallel Transporter file_opt: TPT19006 Version 14.10.00.05

file_opt: TPT19206 Attribute 'TraceLevel' value reset to 'Statistics Only'.

file_opt Instance 1 directing private log report to 'dtacop-boetlqas-2708-1'.

file_opt: TPT19003 NotifyMethod: 'None (default)'

file_opt: TPT19008 DataConnector Producer operator Instances: 1

file_opt: TPT19003 ECI operator ID: 'file_opt-2708'

file_opt: TPT19222 Operator instance 1 processing file '\.\pipe\DS_TD_TGT_STAGE

_T_OAS_MATL_BUS_IMPACT_S1_0.dat'.

load_opt: connecting sessions

load_opt: The job will use its internal retryable error codes

load_opt: preparing target table

load_opt: entering Acquisition Phase

Task(SELECT_2[0001]): checkpoint completed, status = Success

Task(APPLY_1[0001]): checkpoint completed, status = Success

Task(SELECT_2[0001]) ready to checkpoint

Task(SELECT_2[0001]): checkpoint completed, status = Success

Task(APPLY_1[0001]): checkpoint completed, status = Success

Task(SELECT_2[0001]) ready to take the EOD checkpoint

Task(SELECT_2[0001]): checkpoint completed, status = Success

Task(APPLY_1[0001]): checkpoint completed, status = Success

load_opt: entering Application Phase

load_opt: Statistics for Target Table: '"STAGE_CORP_OAS_T"."OAS_MATL_BUS_IMPACT

_S1"'

load_opt: Total Rows Sent To RDBMS: 5

load_opt: Total Rows Applied: 5

load_opt: Total Rows in Error Table 1: 0

load_opt: Total Rows in Error Table 2: 0

load_opt: Total Duplicate Rows: 0

TPT_INFRA: TPT02255: Message Buffers Sent/Received = 1, Total Rows Received = 0,

Total Rows Sent = 5

file_opt: TPT19221 Total files processed: 1.

TPT_INFRA: TPT02255: Message Buffers Sent/Received = 1, Total Rows Received = 5,

Total Rows Sent = 0

load_opt: disconnecting sessions

load_opt: Total processor time used = '0.703125 Second(s)'

load_opt: Start : Fri Sep 05 15:20:23 2014

load_opt: End : Fri Sep 05 15:20:41 2014

Job step MAIN_STEP completed successfully

Job STAGE_CORP_OAS_T_OAS_MATL_BUS_IMPACT_S1 completed successfully

Job start: Fri Sep 05 15:20:19 2014

Job end: Fri Sep 05 15:20:41 2014

Total available memory: 20000000

Largest allocable area: 20000000

Memory use high water mark: 270264

Free map size: 1024

Free map use high water mark: 20

Free list use high water mark: 0

Everything appears to have loaded correctly.  Do we need to be concerned with this warning message?

Thanks,

Joe

3 REPLIES

Re: OMD API error

Hi Joe,

Did you get this issue resolved?  We are getting the same error:

C:\Program Files\Teradata\Client\14.10\Teradata Parallel Transporter\logs>

tlogview -l NEXTGEN_AZ_DWS_DB_CLAIM_TRANS_ADJUSTMENTS_ACTIVE_RECS-69.out

TPT_INFRA: TPT04101: Warning: Teradata PT cannot connect to Unity EcoSysetm Mana

ger.

The job will continue without event messages being sent to Unity EcoSystem Manag

er.

TPT_INFRA: TPT04190: Warning: OMD API failed to initialize

Teradata Parallel Transporter Executor Version 14.10.00.05

Teradata Parallel Transporter Coordinator Version 14.10.00.05

Teradata Parallel Transporter Executor Version 14.10.00.05

Teradata Parallel Transporter Executor Version 14.10.00.05

Teradata Parallel Transporter Executor Version 14.10.00.05

Teradata Parallel Transporter Executor Version 14.10.00.05

Teradata Parallel Transporter file_opt: TPT19006 Version 14.10.00.05

file_opt: TPT19206 Attribute 'TraceLevel' value reset to 'Statistics Only'.

file_opt Instance 1 directing private log report to 'dtacop-svtasbiagentP-11196-

1'.

file_opt: TPT19003 NotifyMethod: 'None (default)'

file_opt: TPT19008 DataConnector Producer operator Instances: 1

Teradata Parallel Transporter Load Operator Version 14.10.00.05

load_opt: private log specified: pl_CLAIM_TRANS_ADJUSTMENTS_ACTIVE_RECS

Teradata Parallel Transporter file_opt: TPT19006 Version 14.10.00.05

file_opt: TPT19206 Attribute 'TraceLevel' value reset to 'Statistics Only'.

file_opt Instance 1 directing private log report to 'dtacop-svtasbiagentP-13972-

1'.

file_opt: TPT19003 ECI operator ID: 'file_opt-11196'

file_opt: TPT19003 NotifyMethod: 'None (default)'

file_opt: TPT19008 DataConnector Producer operator Instances: 1

Teradata Parallel Transporter file_opt: TPT19006 Version 14.10.00.05

file_opt: TPT19206 Attribute 'TraceLevel' value reset to 'Statistics Only'.

file_opt Instance 1 directing private log report to 'dtacop-svtasbiagentP-10668-

1'.

file_opt: TPT19003 NotifyMethod: 'None (default)'

file_opt: TPT19008 DataConnector Producer operator Instances: 1

file_opt: TPT19003 ECI operator ID: 'file_opt-13972'

file_opt: TPT19003 ECI operator ID: 'file_opt-10668'

load_opt: connecting sessions

load_opt: preparing target table

load_opt: entering Acquisition Phase

file_opt: TPT19222 Operator instance 1 processing file '\.\pipe\BH_STAGING_NEXT

GEN_AZ_DWS_DB_CLAIM_TRANS_ADJUSTMENTS_ACTIVE_RECS_0.dat'.

file_opt: TPT19222 Operator instance 1 processing file '\.\pipe\BH_STAGING_NEXT

GEN_AZ_DWS_DB_CLAIM_TRANS_ADJUSTMENTS_ACTIVE_RECS_1.dat'.

file_opt: TPT19222 Operator instance 1 processing file '\.\pipe\BH_STAGING_NEXT

GEN_AZ_DWS_DB_CLAIM_TRANS_ADJUSTMENTS_ACTIVE_RECS_2.dat'.

Task(SELECT_2[0001]): checkpoint completed, status = Success

Task(SELECT_3[0001]): checkpoint completed, status = Success

Task(APPLY_1[0001]): checkpoint completed, status = Success

Task(SELECT_4[0001]): checkpoint completed, status = Success

Task(APPLY_1[0002]): checkpoint completed, status = Success

Task(SELECT_2[0001]) ready to checkpoint

Task(SELECT_3[0001]) ready to take internal checkpoint

Task(SELECT_4[0001]) ready to take internal checkpoint

Task(SELECT_2[0001]): checkpoint completed, status = Success

Task(SELECT_4[0001]): checkpoint completed, status = Success

Task(SELECT_3[0001]): checkpoint completed, status = Success

Task(APPLY_1[0001]): checkpoint completed, status = Success

Task(APPLY_1[0002]): checkpoint completed, status = Success

Task(SELECT_3[0001]) ready to checkpoint

Task(SELECT_4[0001]) ready to checkpoint

Task(SELECT_3[0001]): checkpoint completed, status = Success

Task(SELECT_2[0001]): checkpoint completed, status = Success

Task(SELECT_4[0001]): checkpoint completed, status = Success

Task(APPLY_1[0002]): checkpoint completed, status = Success

Task(APPLY_1[0001]): checkpoint completed, status = Success

Task(SELECT_2[0001]) ready to take the EOD checkpoint

Task(SELECT_4[0001]) ready to take the EOD checkpoint

Task(SELECT_3[0001]) ready to take the EOD checkpoint

Task(SELECT_3[0001]): checkpoint completed, status = Success

Task(APPLY_1[0002]): checkpoint completed, status = Success

Task(SELECT_2[0001]): checkpoint completed, status = Success

Task(SELECT_4[0001]): checkpoint completed, status = Success

Task(APPLY_1[0001]): checkpoint completed, status = Success

load_opt: entering Application Phase

load_opt: Statistics for Target Table:  '"NEXTGEN_AZ_DWS_DB"."CLAIM_TRANS_ADJUST

MENTS_ACTIVE_RECS"'

load_opt: Total Rows Sent To RDBMS:      37157997

load_opt: Total Rows Applied:            37157997

load_opt: Total Rows in Error Table 1:   0

load_opt: Total Rows in Error Table 2:   0

load_opt: Total Duplicate Rows:          0

TPT_INFRA: TPT02255: Message Buffers Sent/Received = 53756, Total Rows Received

= 36960849, Total Rows Sent = 0

TPT_INFRA: TPT02255: Message Buffers Sent/Received = 289, Total Rows Received =

197148, Total Rows Sent = 0

TPT_INFRA: TPT02255: Message Buffers Sent/Received = 18009, Total Rows Received

= 0, Total Rows Sent = 12386000

TPT_INFRA: TPT02255: Message Buffers Sent/Received = 18024, Total Rows Received

= 0, Total Rows Sent = 12386000

TPT_INFRA: TPT02255: Message Buffers Sent/Received = 18012, Total Rows Received

= 0, Total Rows Sent = 12385997

file_opt: TPT19221 Total files processed: 1.

file_opt: TPT19221 Total files processed: 1.

file_opt: TPT19221 Total files processed: 1.

load_opt: disconnecting sessions

load_opt: Total processor time used = '3.625 Second(s)'

load_opt: Start : Thu Sep 24 16:36:06 2015

load_opt: End   : Thu Sep 24 16:41:51 2015

Job step MAIN_STEP completed successfully

Job NEXTGEN_AZ_DWS_DB_CLAIM_TRANS_ADJUSTMENTS_ACTIVE_RECS completed successfully

Job start: Thu Sep 24 16:36:05 2015

Job end:   Thu Sep 24 16:41:51 2015

Total available memory:          20000000

Largest allocable area:          20000000

Memory use high water mark:       1122952

Free map size:                       1024

Free map use high water mark:          25

Free list use high water mark:          0

C:\Program Files\Teradata\Client\14.10\Teradata Parallel Transporter\logs>

Thank you,

Stephanie

Teradata Employee

Re: OMD API error

You can ignore this warning, unless you have Unity EcoSystems Manager. The Operational MetaData API is the integration between ESM and Teradata Utilities.

Teradata Employee

Re: OMD API error

Fred is correct.

I just want to emphasize that the message is a WARNING and not an error.

(If it was an error, the job would have terminated.)

-- SteveF