May 14, 2009, 07:02 AM
bcook278DM Schedule Logs Stuck in DFM_DIR
We have recently installed and started working with DM (7.6.8) and one thing that I started noticing when moving data flows to our production server was that the schedule logs are empty. I was able to see the target database files getting loaded daily so I knew the scheduled data flows were running. Looked around on the server and saw that the logs were sitting out in the DFM_DIR directory which I understand is a temp directory where these write to prior to being written to the log file. It seems that these are not performing that final step and get stuck in this directory. This is working correctly on our development/test server so I am leaning towards a setup issue but haven't come across any setting that may be responsible for this. Can anyone offer suggestions fpr things I may want to look at to resolve this? I did try deleting the files in DFM_DIR but the next scheduled run again just left the files here and never wrote to the log. The servers are running LINUX.
Thanks,
BobC
May 15, 2009, 11:32 AM
MarinaBob,
The files you are seeing inside of 'dfm_dir' directory (.rpf, .rqd, .rsp, etc.) are the deferred files that are being stored in this directory for further processing.
An actual ETL log and statistics files are located in /dm/catalog directory and are called: etllog.foc and etlstats.foc.
Please run the DataMigrator's Utility 'Create Log and Statistics' on that Linux server; the log and statistics files will appear in the /dm/catalog directory then.
Thanks,
Marina
May 19, 2009, 01:17 PM
bcook278I can see the log files in the /dm/catalog directory but nothing is getting written to these files. I can definately confirm that the process flows are running daily and these flows appear in the DM scheduled events but nothing appears when I view the Scheduler Log. Is there something within the flow itself that has to be set to log this information?
May 19, 2009, 01:28 PM
MarinaThere is nothing you should do within the flow(s) itself.
What is the size of etllog.foc that you see? If it's bigger than 1 GB, then perhaps you better change the format in the etllog.mas from SUFFIX=FOCUS to SUFFIX=XFOCUS and then run 'recreate log and statistics' utility. Please remember that if you do this, you need to assure nothing (requests) is running on the server at this time. The XFOCUS format allows an optimized processing and larger capacity than FOCUS.
May 20, 2009, 09:10 AM
bcook278Thanks. I made these changes and this morning can see all the scheduled flows appearing in the scheduler log report. I appreciate the help.