Administration > Monitor Administration > SiteScope Data Collector Configuration > Managing SiteScope > SiteScope Preferences > Logging Preferences > Troubleshooting Database Connections
Troubleshooting Database Connections
When Database logging is active and working correctly, you should see a table called SiteScopeLog in your database and a record added to the table every time a monitor runs. The data is sent to the database as a single table in a flat-file format. For additional details, see section on "SiteScope Log File Columns" in the SiteScope Reference Guide.
If a table called SiteScopeLog is not created or is empty, check the SiteScope <SiteScope install path>/SiteScope/logs/RunMonitor.log and <SiteScope install path>/SiteScope/logs/Error.log files for log messages starting with "jdbc" or "odbc". When Database logging is working correctly, you should see a set of messages in RunMonitor.log that looks like this:
jdbc log, reconnect seconds=600
jdbc log, loading, driver=sun.jdbc.odbc.JdbcOdbcDriver
jdbc log, connecting, url=jdbc:odbc:SiteScopeLog,
jdbc log, logged in
jdbc log, checking log table
jdbc log, created log table
jdbc log, prepare insert, 19, INSERT INTO SiteScopeLog...
jdbc log, connectedIf these entries do not appear in the log file there is a problem with the database interface or configuration of the database connection. You should also carefully check the Database Connection URL you entered above. This parameter is case sensitive. It is also sensitive to leading or trailing white space which may be the reason the connection does not work properly. Check the spelling and letter case of the connection URL and be sure there are no leading or trailing spaces present in the text box.
You can also check the on-line Knowledge Base available via the Customer Support site for other information relating to database logging.
| Copyright 2006 Mercury Interactive Corporation |