ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Data Flow from CASAAS to DWH_INV_IDEA OData DWH_INV_IDEA Description: The remote server returned an error: (408) Request Timeout

book

Article ID: 223988

calendar_today

Updated On:

Products

Clarity PPM SaaS

Issue/Introduction

Having Issues with Odata and DWH see below errors

 

I have highlighted the error/issue when the job was trying to pull data from PROD DWH table/collections @ 2:40 & 3:40 PM PST scheduled runs. From 4:40 PM PST onwards jobs ran successfully.

 

Step ID

Step Name

Run Outcome

Last Run

Run Duration

Message

1

LoadCASAAS_To_ITGVCDWH_Prod

Failed

8/31/2021 16:01

0:05:02

Executed as user: domain\USER. Microsoft (R) SQL Server Execute Package Utility Version 13.0.5888.11 for 64-bit Copyright (C) 2016 Microsoft. All rights reserved. Started: 4:01:44 PM Error: 2021-08-31 16:06:46.41 Code: 0x00000000 Source: Data Flow from CASAAS to DWH_INV_IDEA OData DWH_INV_IDEA Description: The remote server returned an error: (408) Request Timeout. End Error Error: 2021-08-31 16:06:46.41 Code: 0xC004706B Source: Data Flow from CASAAS to DWH_INV_IDEA SSIS.Pipeline Description: "OData DWH_INV_IDEA" failed validation and returned validation status "VS_ISBROKEN". End Error Error: 2021-08-31 16:06:46.41 Code: 0xC004700C Source: Data Flow from CASAAS to DWH_INV_IDEA SSIS.Pipeline Description: One or more component failed validation. End Error Error: 2021-08-31 16:06:46.41 Code: 0xC0024107 Source: Data Flow from CASAAS to DWH_INV_IDEA Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 4:01:44 PM Finished: 4:06:46 PM Elapsed: 301.703 seconds. The package execution failed. NOTE: The step was retried the requested number of times (2) without succeeding. The step failed.

           
           
           
           
           

 

Cause

This is a timeout.

Environment

Release : 15.9.3

Component : ODATA

Resolution

Check network proxy timeouts, ask Broadcom support to check database performance / environment