Exploring Oracle MFT 12c Database Tables

Oracle MFT Tables Useful For Gathering Daily Transactions

• Oracle MFT RCU utility creates multiple schemas for storing transfer configurations and runtime transaction data
• Below are some important schemas
• <Prefix>_MFT
• <Prefix>_MDS
• <Prefix>_ESS
• <Prefix>_OPSS
• <Prefix>_UMS
• Prefix can be like Dev, UAT or PROD. If we use MFT cloud service then prefix would be like SP<number>, number is randomly picked by oracle cloud orchestration logic which provisions MFT cloud service instance
• To gather daily statistics of transfers then we need to explore more on <Prefix>_MFT schema
• Below tables are useful under MFT schema

Table Name	Description
MFT_CALLOUT_INSTANCE	Contains data related to the actions or callouts performed during the transfers like Delete, Run Script PGP Encryption and so on
MFT_ERROR_INFO	Contains data related to the errors that occurs during mft transfers
MFT_SOURCE_MESSAGE	Contains data related to source details of the file transfer like source name, source endpoint and file name and so on
MFT_TARGET_INSTANCE	Contains data related to target details of the file transfer like transfer name, target name and status and so on
MFT_TARGET_MESSAGE	Contains data related to target details of the file transfer like target name, target endpoint and modified file name and so on
MFT_TRANSFER_INSTANCE	Contains data related to transfer name,status, creation and completed time and so on
MFT_TRIGGER_EVENT	Contains data when the source event is invoked for on demand file transfers and specifies the status of the event invoked
MFT_DATA_STORAGE	Contains information of payload file reference path, payload size and so on

• Query for source level details
• select source_name,source_endpoint_ref,file_name,status from mft_source_message
• Query for target level details
• select target_name,endpoint_reference,file_name,status from mft_target_message
• Composite query to fetch both source and target details of file transfers
• select distinct(MSG.FILE_NAME) Source_File_name,MTG.DELIVERED_FILE_NAME Target_File_name,MSG.source_name Source_name,MTG.target_name Target_name,MSG.source_endpoint_ref Source_Endpoint,MTG.endpoint_reference Target_Endpoint,TO_CHAR(MTG.transfer_completed_time, 'DD-MON-YY') Transfer_Completed_Time,MDS.PAYLOAD_SIZE,MTG.STATUS from MFT_SOURCE_MESSAGE MSG, MFT_TARGET_MESSAGE MTG,MFT_DATA_STORAGE MDS where trunc(MTG.transfer_start_time) = trunc(sysdate)and MTG.ecid = MSG.ecid and MSG.DATA_STORAGE_ID = MDS.ID order by transfer_completed_time desc    
• There are many other tables and views in *_MFT schema. Need to explore on these tables as per requirement  

Creation Of Oracle MFT Cloud Service Instance

Pre-requisites for creation of MFT Cloud Service:

1. Creation of SSH keypairs for use with oracle cloud service.
2. Creation of Storage Containers for back up storage.
3. Creation of Oracle Database Cloud Service for Oracle SOA Cloud Service.

Instance Creation Steps:

• Login to oracle.cloud.com with the credentials provided by oracle during subscription. You will be asked to select the cloud account type with below options and provide the identity domain name. Based on your subscription select accordingly click on My Services button.

Cloud Account with Identity Cloud Service	Users creation and management is based on “Oracle Identity Cloud Service”
Traditional Cloud Account	Users creation and management is based on “Traditional Identity and Access Management software”

• On the home page click on “Create Instance” and select “SOA” tab as below.

• You will be redirected to the SOA Cloud Service Console home page. Click on “Create Instance” as shown below.

• Instance creation form page appears. Please fill in the details and click on next.
• Service Name: Name of the MFT service instance
• Service Description: Description about MFT instance
• Notification Email: Recipient email for the provisioning status notifications
• Region: Name of the region where data centers are required
• Tags: You can include some tags like MFT Dev, MFT Test and so on
• SSH Public Key: Browse the SSH public key that was created during pre-requisite
• Software Release: Select the version of MFT required to be installed

• After filling the basic details, application navigates to Service Details page where we need to provide information regarding DB details, MFT configuration and load balancer configuration and click on next. Below are the few important details that needs to be considered.
• Service Type: Select MFT Cluster
• Compute Shape: Select the required compute shape 
• Provision Load Balancer: Check this option if the cluster size is > 2 and select the load balancer configuration
• Storage Container Name: Provide the container URL that is created during pre-requisites

• Now you can view all the provided configuration information review it once and click on submit and then click on create and after oracle cloud tooling completes the instance creation and it will be visible in SOA Console home page.