Invalid object name errors indicate that up.time is not able to find required objects in the database. This is typically caused by one of the following problems:
Example Stack Trace from an uptime.log file:
2008-03-05 16:11:39,847 INFO (UptimeInstance:75) - up.time 4.6.25 R G starting... 2008-03-05 16:11:39,863 INFO (UptimeInstance:78) - © 2006 uptime software inc. 2008-03-05 16:11:39,878 INFO (UptimeInstance:79) - Starting up.time... 2008-03-05 16:11:39,878 INFO (UptimeInstance:81) - Java heap size: 1065484288 bytes 2008-03-05 16:11:40,800 INFO (UptimeInstance:159) - Checking database version... 2008-03-05 16:12:02,082 WARN (JDBCExceptionReporter:71) - SQL Error: 208, SQLState: 42S02 2008-03-05 16:12:02,082 ERROR (JDBCExceptionReporter:72) - Invalid object name 'dbversion'. 2008-03-05 16:12:02,097 WARN (JDBCExceptionReporter:71) - SQL Error: 208, SQLState: 42S02 2008-03-05 16:12:02,097 ERROR (JDBCExceptionReporter:72) - Invalid object name 'dbversion'. 2008-03-05 16:12:02,097 INFO (Upgrader:36) - Upgrading database to version 4.6.25 R G 2008-03-05 16:12:06,754 WARN (JDBCExceptionReporter:71) - SQL Error: 208, SQLState: 42S02 2008-03-05 16:12:06,754 ERROR (JDBCExceptionReporter:72) - Invalid object name 'tip'. 2008-03-05 16:12:06,769 WARN (JDBCExceptionReporter:48) - SQL Warning: 208, SQLState: 42S02 2008-03-05 16:12:06,769 WARN (JDBCExceptionReporter:49) - Preparing the statement failed: Invalid object name 'tip'. 2008-03-05 16:12:06,769 ERROR (UptimeInstance:165) - Upgrade failed java.lang.RuntimeException: org.hibernate.exception.SQLGrammarException: could not execute update query at com.uptimesoftware.setup.install.InstallerSaver.save(InstallerSaver.java:16) at com.uptimesoftware.hibernate.HibernateManager.executeSave(HibernateManager.java:285) at com.uptimesoftware.hibernate.Saver.save(Saver.java:23) at com.uptimesoftware.setup.install.Installer.install(Installer.java:14) at com.uptimesoftware.setup.upgrade.Upgrader.doUpgrade(Upgrader.java:38) at com.uptimesoftware.uptime.base.UptimeInstance.checkForUpgrade(UptimeInstance.java:163) at com.uptimesoftware.uptime.base.UptimeInstance.runUptime(UptimeInstance.java:90) at com.uptimesoftware.uptime.base.Uptime.main(Uptime.java:275) at com.uptimesoftware.uptime.base.Uptime$1.run(Uptime.java:222) at java.lang.Thread.run(Unknown Source) Caused by: org.hibernate.exception.SQLGrammarException: could not execute update query at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:59) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.hql.ast.UpdateStatementExecutor.execute(UpdateStatementExecutor.java:99) at org.hibernate.hql.ast.QueryTranslatorImpl.executeUpdate(QueryTranslatorImpl.java:297) at org.hibernate.impl.SessionImpl.executeUpdate(SessionImpl.java:871) at org.hibernate.impl.QueryImpl.executeUpdate(QueryImpl.java:89) at com.uptimesoftware.setup.install.ToolTipDeleter.delete(ToolTipDeleter.java:13) at com.uptimesoftware.setup.install.ToolTipInstaller.clearCurrentToolTips(ToolTipInstaller.java:16) at com.uptimesoftware.setup.install.ToolTipInstaller.install(ToolTipInstaller.java:21) at com.uptimesoftware.setup.upgrade.Update.install(Update.java:22) at com.uptimesoftware.setup.install.InstallerSaver.save(InstallerSaver.java:14) ... 9 more Caused by: java.sql.SQLException: Invalid object name 'tip'. |
SQL Server error: Charset is not supported by the JVM | Rating | Views | |
---|---|---|---|
![]() |
When trying to use a SQL Server database as the up.time backend, you may receive the following error when initializing the database: > resetdb really Looking for resources in: C:\uptime4\.... By: uptime Support | Date Created: 10-1-2009 | Last Modified: 8-10-2011 | Index: 378 |
![]() ![]() ![]() ![]() ![]() |
2427 |
Running up.time with an MS SQL Server database | Rating | Views | |
---|---|---|---|
![]() |
The up.time DataStore can run on a MS SQL Server database to leverage existing SQL Server installations and take advantage of SQL Server's advanced replication, recovery and archiving options. By: uptime Support | Date Created: 7-10-2006 | Last Modified: 6-19-2014 | Index: 087 |
![]() ![]() ![]() ![]() ![]() |
10445 |
SAR error and SADC problems on AIX 5.3 | Rating | Views | |
---|---|---|---|
![]() |
By: uptime Support | Date Created: 9-23-2005 | Last Modified: 7-5-2011 | Index: 005 |
![]() ![]() ![]() ![]() ![]() |
8327 |
Configuring SQL Server Ports | Rating | Views | |
---|---|---|---|
![]() |
This article explains how to configure static and dynamic SQL Server ports. By: uptime Support | Date Created: 7-11-2007 | Last Modified: 6-28-2011 | Index: 193 |
![]() ![]() ![]() ![]() ![]() |
8816 |
Report Error Occurred During Processing | Rating | Views | |
---|---|---|---|
![]() |
This article explains how to resolve the root cause of a Report Error Occurred During Processing message. By: uptime Support | Date Created: 1-15-2007 | Last Modified: 7-5-2011 | Index: 116 |
![]() ![]() ![]() ![]() ![]() |
3022 |