Configuration Migration Assistant Part 6 - Migration Export

Now that the configuration steps have been completed the next step is to use the Configuration Migration Assistant to migrate data across environments. The first step is to export the data from the source environment.

The steps to perform to export data using the Configuration Migration Assistant are as follows:

  • Create a Migration Data Set Export record to register the intent to export.
  • Execute the Migration Data Set Monitor batch process to perform the export.
  • Optionally, check the exported file into a code repository for cross reference with any customized code.

 For example:

Export Process Overview

The first step in the process is to create a Migration Data Set Export record. To do this use the Administration --> M --> Migration Data Set Export menu item and provide the following information:

  • Migration Request - Name of the Migration Request to Migrate
  • Export Directory - The directory taken from the Master Configuration Record for this environment. You cannot override the directory.
  • File Name - Name of the export file. The name of the file must conform to operating system constraints. We advise you do not embed blanks in the file name. Also do not include the filename suffix.
  • Export Description - Short description to attach within the export file.
  • Source Environment Reference - Defaults to the URL of the source environment but can be changed to reference the source of the information.

For example:

Migration Data Set Export

You may of noticed that Migration Request is a free format field. The easiest way to populate that field automatically is initiating the Export from the Migration Request maintenance screen. This allows you to verify the criteria prior to registering the export request. For example:

Export function from Migration Request

After saving this Migration Data Set Export, the request is registered within the product. Remember this does not perform the actual export it just registers the intent. The F1-MGDPR batch process exports the file. As the Migration Data Set Export has been registered then the request can be cancelled anytime prior to the execution of the F1-MGDPR batch process using the Migration Data Set Export maintenance dialog. For example:

Migration Data Set Export display

Now, you can register any number of Migration Data Set Exports as necessary for migrations.

To export the data the Migration Data Set Monitor batch process (F1-MGDPR) must be executed. This can be executed using any method (online submission, command line, batch scheduler etc) available to the environment by an authorized user.

The generic F1-MGDPR job is used to execute exports, process imports as well as apply changes and requires only one parameter DIST-THD-POOL. This is the threadpool to use for the export. As the product is processing data that is potentially cached, the job must run with the L2 cache turned off. This can be done using the following command:

Linux/UNIX -l2 OFF -p <threadpoolname>=<number of threads> 


threadpoolworker  -l2 OFF -p <threadpoolname>=<number of threads> 


<threadpoolname> - Threadpool name to use in DIST-THD-POOL.

<number of threads> - Maximum limit for number of batch threads

Note: can be also used on Linux/UNIX.

Note: Running this process using a threadpool where L2 cache is enabled may cause unexpected results.

During the execution of the export batch process the Migration Data Set Export will transition to a number of states:

  • The Migration Data Set Export starts in a Pending Status. This indicates that the export should be initiated the next time the F1-MGDPR process is executed.
  • At anytime before the F1-MGDPR is executed the Migration Data Set Export can be Cancelled manually using the Migration Data Set Export maintenance function.
  • During the execution the data to be migrated is identified and Migration Data Set and Migration Objects are created. The Migration Data Set groups all the records for a particular export request. The Migration Data Set Export is transitioned to Set Up Data status to indicate this activity is being performed.
  • The Migration Objects in the Migration Data Set are reviewed for duplications and relationships to be combined into transactions. This allows them to be exported in the correct sequence. The Migration Data Set Export is transitioned to Combine Transactions to indicate this activity is being performed.
  • Once the objects are checked and combined they are ready to export, with the state transitioned to Ready To Export to indicate this activity is being performed.
  • If there is some sort of processing error during any of the above transitions the Migration Data Set Export is transitioned to Error state and the batch process terminated for that Migration Data Set Export.
  • Once all the objects in the Migration Data Set Export are written to the file indicated the Migration Data Set Export is set to an Exported state. The date and time are recorded for auditing purposes.
For example the state transition model for Migration Data Set Export objects: 

Export State Transition

The state transitions can be tracked on the Log tab for the Migration Data Set Export maintenance function. For example:

Log entries for state transition

After executing the F1-MGDPR process the Migration Data Set Export will be updated with the file name and the date/time exported. For example:

Updated Migration Data Set Export

Now the data has been exported to a file. The file is in an internal format and SHOULD NOT be altered manually except through this tool. Any attempt to edit the file may result in unexpected results and even data corruption. The file can be optionally checked into your site code repository if you wish to keep it with any additional customizations such as java code etc.

The file is now available for import which we will cover in the next blog entry.

For more information about this aspect of the Configuration Migration Assistant and other aspects refer to the Configuration Migration Assistant Overview (Doc Id: 1506830.1) whitepaper available from My Oracle Support.


Post a Comment:
  • HTML Syntax: NOT allowed

Anthony Shorten
Hi, I am Anthony Shorten, I am the Principal Product Manager for the Oracle Utilities Application Framework. I have been working for over 20+ years in the IT Business and am the author of many a technical whitepaper, manual and training material. I am one of the product managers working on strategy and designs for the next generation of the technology used for the Utilities and Tax markets. This blog is provided to announce new features, document tips and techniques and also outline features of the Oracle Utilities Application Framework based products. These products include Oracle Utilities Customer Care and Billing, Oracle Utilities Meter Data Management, Oracle Utilities Mobile Workforce Management and Oracle Public Service Revenue Management. I am the product manager for the Management Pack for these products.


« June 2016