Unable To Get File Name From Target Error Message

(Doc ID 2377223.1)

Last updated on APRIL 06, 2018

Applies to:

Oracle Managed File Transfer - Version 12.2.1.2.0 and later
Information in this document applies to any platform.

Symptoms

Unable to get file name from Target error message

Error at Target:

Runtime Error
  ID: 08e38a33-3e05-415c-80da-e38955899737
  Error Code: MFT-5253
  Error Description: Error in the connection for endpoint
  Target Message Details
  Transfer Name: DBCS_TO_ERPUCM
  Target Name: ERPUCM_TRG
  Protocol: RIDC
  Endpoint Reference: 
  Error Cause
  Cause: Error in the protocol layer.
  Action: Check the logs for the exception trace and try again. Contact Oracle Support Services if the problem persists.


Error at Source:

Runtime Error
  ID: d2b6e31f-a770-482f-94d6-e0de9ae92393
  Error Code: MFT-4401
  Error Description: Exception encountered during execution of callout Pre transfer Callback.
  Source Message Details
  Source Name: DBCS_OUT_SRC
  Endpoint Reference: 
  Source Type: EXTERNAL
  File: T15.zip
  Error Cause
  Cause: Error while executing custom callout.
  Action: Review the diagnostic log for the exact error.


Am able to get the file name for which instance is failed in case of source error message - but in the same case, am not getting file name if its failed at target stage.

EXPECTED BEHAVIOR
-----------------------
file name should also be in target message

Changes

 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms