Forum Moderators: DixonJones
Symptoms:
I try to add an event to the scheduler, but it doesn't go in.
Can anyone provide some pointers as how to verify the DB is working correctly, or a reason why I can't add anything to the scheduler?
Also, I just noticed that WTRS.exe is not running, which I'm pretty sure it's supposed to be? When I try to run it manually, I get an error saying it can't locate the wtlicensemanager.dll file (I have the file, it's just not located in the directory it's looking in).
If you were using the InnoDb storage engine, tables undergo an automatic diagnostic/repair when mysql re-starts if using the innodb_force_recovery option in your config.
Regarding your license file -first try putting the file where WebTrends is looking. If that does not work try the webtrends knowledge base. Maybe you could crack open an ini file and alter the path...Also always remember to restart the webservices before you do anything.
cgrantski:
you could try a general mysql repair to your main db files: (these are lifted from WT KB articles)
mysqlcheck.exe -r --databases wt_sched -u Administrator -p
mysqlcheck.exe -r --databases wtmaster -u Administrator -p
where "Administrator" is your mysql username of course
also this:
mysql –u Administrator –p
use wtmaster
repair table wt_servicestatus:
exit
These are done from the mysql/bin folder
afterwards restart the mysql and scheduler services
mysql –u Administrator –p
use wtmaster
repair table wt_servicestatus:
exit
I'm not entirely sure what this is... is each line a different command via the command line interface?
mysql> use wtmaster
Database changed
mysql> repair table wt_servicestatus:
->
Excuse my ignorance, but how long does the repair take? As you can see, after I submitted the command, all I got was "->". Is this ok?
I've tried the mysqlcheck.exe tools as well, I got "OK" for everything. Things are still not working.
This is only two of all the possible tables to repair, but it's the two most common ones where things happen. If there's still a problem, you can try this:
mysql –u Administrator –p
(Press enter it prompts for password)
use wtmaster <enter>
repair table wt_servicestatus: <enter>
exit
What will work for you depends on what's wrong.
But in general for the problem you're having I reboot the server(s) and when they come back up the scheduler is working. I assume you checked Services in control panel to make sure scheduler is running?
There's also an issue with affinity tracking and pipelining that affects scheduler, but not usually all of a sudden like you are seeing.
Is there anything I can do/back up that will help me get back on the ground quicker?
i.e.
My analysis data?
My Profile settings?
Thank you,
M
C:\Program Files\WebTrends\modules\common\database\mysql\bin>
.... where, in the instructions a few responses above, it says "mysql\bin". Your own installation may have the folder pair \mysql\bin\ in a different path.
