We received the following question:
“I have a failover system that the db optimization ran on last night, both DMAs, but it doesn’t look like the BU DMA database was optimized. I checked the Windows Task Scheduler and it shows that it ran on both DMAs. How can I figure out what happened on the BU DMA and why the dbase was not optimized?”
We were thinking the SLDMS.txt log file set to logging level 5(debug) would provide the information requested, but this might only be for the online DMA and not the offline failover agent database optimization. I sent this suggestion and received the following feedback:
“I went into the Cube->System Center->Logging->netvue-> DMS log and changed the “Debug logging level” to “Log everything (5)”. Then I went to offline DMA Windows Task Scheduler and forced (Run) the optimization task to run. I do not see any indication of optimization events in either the Cube->System Center->Logging->netvue-> DMS log of the actual SLDMS log file on the Offline DMA. Nor do I see any info event related to Optimization.”
Is there any logging or debug methods to see why the offline DBOptimization might be failing here?
Hi Ryan,
Some pointers:
DB optimization gets triggered by the Windows Task Scheduler, which runs a script “c:\Skyline Dataminer\tools\OptimizeDB.js”.
This script will check whether SLDMS is running and then execute a DMS_OPTIMIZE_TABLES request on there.
Once in SLDMS, there will be logging on DBG|1 “MySQL base fir found at ‘xxxxx'”
From there, mysql processes will be launched to execute “optimize table xxxx” queries. You might be able to see these in the task manager / process explorer.
As for the OptimizeDB.js file, a known issue there was fixed with RN31877. If your version is from before 10.1 CU11 / 10.0 CU22 / 10.2.2. This might be related.
Wouter, thanks for the info. This is on a 9.6 Failover system that will soon be upgraded to 10.1. It works fine on the PRI online DMA but does not appear to work on the BU offline DMA. I tested it on both Online and Offline DMAs on a test system running 10.1 with the debug logging set to 5 and I do not see any logging info being generated on the offline DMA like I do on the Online DMA which leads me to believe that logging info is not generated on the offline DMA. With this being the case how can this be debugged?
Thanks