2 Known Issues and Workarounds

Known issues and workarounds for Release 12c (12.2.1.x) of Oracle Managed File Transfer are:

2.1 Test Connection for OCI Storage Cloud Service Type Successful Despite Invalid Values

Beginning with 12c (12.2.1.4): In the Create Source or Create Target dialog, when the source or target type is OCI Storage Cloud Service, Test Connection returns a successful connection even if invalid values are specified for Endpoint URL or Compartment ID.

See OCI Storage Cloud Service Source Type and OCI Storage Cloud Service Target Type.

2.2 Supported Algorithms for MFT SFTP Embedded Server

The algorithms supported by MFT sFTP embedded server in Release 12c (12.2.1.3) are:

KeyExchange

Plain
  • diffie-hellman-group1-sha1
  • diffie-hellman-group-exchange-sha1
  • diffie-hellman-group14-sha1
  • diffie-hellman-group-exchange-sha256

FIPS

  • diffie-hellman-group14-sha1
  • diffie-hellman-group-exchange-sha256
  • ecdh-sha2-nistp256
  • ecdh-sha2-nistp384
  • ecdh-sha2-nistp521

MessageAuthentication

Plain
  • hmac-md5
  • hmac-sha1
  • hmac-md5-96
  • hmac-sha1-96
  • hmac-sha2-256
  • hmac-sha2-512
FIPS
  • hmac-sha1
  • hmac-sha2-256
  • hmac-sha2-512

Signature

Plain
  • ssh-dss
  • ssh-rsa
FIPS
  • ecdsa-sha2-nistp256
  • ecdsa-sha2-nistp384
  • ecdsa-sha2-nistp521

Ciphers

Plain
  • aes128-cbc
  • aes192-cbc
  • aes256-cbc
  • 3des-cbc
  • blowfish-cbc
  • aes128-ctr
  • aes192-ctr
  • aes256-ctr
  • arcfour128
  • arcfour256

FIPS

  • aes128-cbc
  • aes192-cbc
  • aes256-cbc
  • 3des-cbc

Compression

  • none
  • zlib
  • zlib@openssh.com

2.3 Supported Algorithms for Remote SFTP

To support the latest algorithms for remote SFTP server, first apply MLR 28258008 (Merge Request on top of 12.2.1.3.0 for Bugs 27446299, 28100096, 28182619, 28212991) and then apply bug 27787163 (Support for hmac-sha2-256 in MFT CS environment).

Latest Supported Remote SFTP Algorithms

KeyExchangeAlgorithm
  • diffie-hellman-group-exchange-sha1
  • diffie-hellman-group14-sha1
  • diffie-hellman-group-exchange-sha256
  • ecdh-sha2-nistp521
  • ecdh-sha2-nistp384
  • ecdh-sha2-nistp256
  • diffie-hellman-group1-sha1 <deprecated>
CompressionAlgorithm
  • none
  • zlib
  • zlib@openssh.com

DataIntegrityAlgorithm (MAC)

  • hmac-sha1
  • hmac-sha256
  • hmac-sha256@ssh.com
  • hmac-sha2-512
  • hmac-sha2-512-etm@openssh.com
  • hmac-sha2-512-96
  • hmac-sha2-256-96
  • hmac-sha2-256-etm@openssh.com
  • hmac-sha2-256
  • hmac-ripemd160
  • hmac-ripemd160-etm@openssh.com
  • hmac-sha1-96
  • hmac-sha1-etm@openssh.com
  • hmac-md5 <deprecated>

PKIAlgorithm

  • ssh-rsa
  • x509v3-sign-rsa
  • x509v3-sign-rsa-sha1
  • ecdsa-sha2-nistp521
  • ecdsa-sha2-nistp384
  • ecdsa-sha2-nistp256
  • ssh-dss <deprecated>

CipherSuite

  • aes128-cbc
  • aes128-ctr
  • 3des-cbc
  • 3des-ctr
  • aes256-cbc
  • aes256-ctr
  • aes192-cbc
  • aes192-ctr
  • twofish192-cbc <deprecated>
  • cast128-cbc <deprecated>
  • twofish256-cbc <deprecated>
  • twofish128-cbc <deprecated>

2.4 Scheduler Duration Created with 1 Minute Shows As 0 Minutes

Issue

Bug number: 26398242

Scheduler duration created with 1 minute shows as 0 minutes.

When you create a schedule with a Frequency of 10 minutes and Duration of 1 minute, the schedule frequency duration is wrongly displayed on the MFT console as 0. It should display as 1.

Workaround

No workaround.

2.5 WebCenter Designed with Invalid GUID Shows Completed Status When Executed

Issue

Bug Number: 26440747

WebCenter designed with invalid GUID shows completed status when executed.

When you create a WebCenter target, it is created with invalid GUID. The invalid GUID is not verified during runtime.

Workaround

No workaround.

2.6 sFTP Embedded Does Not Pick Up a 0 Byte File

Issue

Bug number : 26858988

When a 0 byte file is put on sFTP embedded source, the file does not get picked up for processing.

Workaround

There is no workaround for this issue.

2.7 Schedules Without Duration Process the Files Even After Expiry

Issue

Bug Number: 26798713

Files scheduled for transfer are picked up even after the Schedule time.

Workaround

Configure the schedules with duration and end date immediately after start date.

2.8 The installtime-stamp.out File Is Not Created in the MFT Installation Log Directory

Issue

In Oracle Managed File Transfer, the installtimestamp.out file is not created in the log inventory.

Workaround

None. This is not an error.