Troubleshooting Data Synchronizations

You can enable additional logging to help you troubleshoot problems with data synchronizations.

Caution!

Enabling debug tracing results in extra debug files being created and accessed. This affects data synchronization performance and uses extra hard disk space. You should only enable these options when troubleshooting problems. Make sure to disable these options when in production.

  To enable additional logging:

  1. Navigate to: %EPM_ORACLE_INSTANCE%\config\EPMA\DataSync.

    For example, C:\Oracle\Middleware\user_projects\epmsystem1\config\EPMA\DataSync\.

  2. Using a text editor, open dme.properties.

  3. Uncomment the following debug lines by removing leading #.

    preTranslationProcessingClass=com.hyperion.awb.datasync.custom.FileBasedRowLogger preTranslationProcessingClass.outputFile=preTransOut.txt 

postTranslationProcessingClass=com.hyperion.awb.datasync.custom.FileBasedRowLogger postTranslationProcessingClass.outputFile=postTransOut.txt 

createDebugFiles=true 
debugSampleSize=1000

    Enabling preTranslationProcessingClass saves the data from the source before any mappings or transformations are applied in a temporary file. The file is named with a unique ID appended as a suffix: _preTransOut. This is useful to track what data is returned by the source.

    Enabling postTranslationProcessingClass saves the data from the source after all mappings and transformations are applied in a temporary file. The file is named with a unique ID appended as a suffix: _postTransOut. This is useful to track what data is sent to the source and how metadata is mapped and transformed.

    Enabling createDebugFiles generates these log files every time a data synchronization is executed or validated:

    • SynRequest.xml — traces each step in the data synchronization execution

    • ALEQuery.xml — the query in ALE format to be executed by the source

    The debugSampleSize setting ensures that file size will not exceed the number of bytes set.

  4. Save and close dme.properties.

  5. Restart the Hyperion EPM Architect Data Synchronizer – Web Application service.

  6. Execute the data synchronization.

The resulting log files are generated in the folder created for each data synchronization execution or validation job. If dme.log is located in the standard Web Logic server folder it should have path to the temporary folder. Typically, the temporary folder is: %EPM_ORACLE_INSTANCE%\tmp\Oracle\Temp.

For debug files that are created in a folder with a unique ID in the temporary folder, the files are created in the temporary folder with a unique ID appended as a suffix: _preTransOut and _postTransOut.

After you enable additional logging to resolve problems, you should disable the options when you return to your production environment.

  To disable additional logging:

  1. Using a text editor, open dme.properties.

  2. Comment the following debug lines by adding leading #.

    preTranslationProcessingClass=com.hyperion.awb.datasync.custom.
FileBasedRowLogger preTranslationProcessingClass.outputFile=preTransOut.txt 

postTranslationProcessingClass=com.hyperion.awb.datasync.custom.
FileBasedRowLogger postTranslationProcessingClass.outputFile=postTransOut.txt 

createDebugFiles=true 
debugSampleSize=1000

  3. Save and close dme.properties.

  4. Restart the Hyperion EPM Architect Data Synchronizer – Web Application service.