Few Important Pointers

  1. To reflect the migration changes, OFSAA services should be restarted.
  2. All metadata should have a Metadata Code of maximum length of 250 characters. Old XML based DMT definitions had only a name. So after migration, the existing name will be used as Code. If name exceeds 250 characters, migration of that metadata will be skipped.
  3. DMT_SRC is supported only for table based source in ONLY_DEFINITION mode.
  4. While migrating a Data Mapping metadata (T2T, T2F), the underlying table based source will also be migrated.
  5. While migrating a Data File Mapping metadata (F2T) there are some assumptions that we need to make, as the File based Sources have undergone a design change in the 8.0.6 version.
    1. Each existing data file mapping definition (F2T) has a unique file based source.
    2. The File based Source will be migrated implicitly by the utility when the F2T definition is being migrated.
    3. The source properties of the existing F2T definition will be set as the Properties of the File Based Source.
    4. If there are more than one F2T definition mapped to a single File Based source, then a new unique File Based Source will be created for each F2T. Name of the new source will be <Source Name>_ <Definition Name>. All references to the Source Name for this F2T in ICC and RRF tables will be updated by the migration utility.
  6. The new 806 table structure does not support a definition with the same name to be present in more than one source. For such definitions the 2nd occurrence of the definition will be made unique by appending the source name to the definition.
  7. Modified Definition Name : <Definition Name >_ <Source Name>
    1. All references of the definition name in ICC and RRF will be modified by the migration utility
  8. There have been a few modifications to properties names that are present in the ETLLoader.properties file, which are being migrated to the AAI_DMT_CONFIG Table. Following are the old property codes and the corresponding new ones.
    • T2TMode -> T2T_MODE
    • T2HMode -> T2H_MODE
    • H2TMode -> H2T_MODE
    • H2HMode -> H2H_MODE
    • F2HMode -> F2H_MODE
    • KEEP_WEBLOG_PROCESSED_FILES -> KEEP_WEBLOG_PROCESSED_FILE
    • ISHIVELOCAL -> IS_HIVE_LOCAL
    • SQOOPURL -> SQOOP_URL
  9. The following properties have been changed and will not be migrated from the ETLLoader.properties file into the AAI_DMT_DB_CLUSTER_PROPERTY table. The user must manually update the AAI_DMT_DB_CLUSTER_PROPERTY table with the new values, or use the DMT Configurations window to update these values. The values must go into source or target clusters as required.
    • SQOOPSERVER_NAME -> SSH_HOST_NAME
    • SQOOPSERVER_SSH_PORT -> SSH_PORT
    • SQOOPSERVER_SSH_USERID -> SSH_USERID
    • SQOOPSERVER_SSH_PASSWORD -> SSH_PASSWORD
  10. In case of PLC Migration, ensure the function defined for the Stored Procedure in the <Infodom name>_TFM.XML is same as the actual function in the Atomic Schema. In case of mismatch, in the Edit mode of the PLC definition, the actual function in the Atomic Schema is replaced by the function in the <Infodom name>_TFM.XML. If the SQL in Transformation has compilation errors, modification of PLC definition will fail.