Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Database Performance Analyzer (DPA) > DPA - Knowledgebase Articles > Error logging into DPA; Invalid object name 'CONPRM'

Error logging into DPA; Invalid object name 'CONPRM'

Updated February 15, 2018

Overview

When logging in to DPA, you receive the following error:

DPA was stopped due to the following error. DPA is attempting to restart try again in 30 seconds.
org.springframework.jdbc.BadSqlGrammarException: PreparedStatementCallback; bad SQL grammar [select V from CONPRM where P = ?]; nested exception is java.sql.SQLException: Invalid object name 'CONPRM'

Environment

DPA, all versions

Cause 

The repository login was assigned to the sysadmin server role.

A login assigned to the sysadmin server role always defaults to the dbo schema, regardless of what is in the user mapping. The login will not see tables in the ignite schema, because it is looking at the dbo schema. Instead of looking for ignite.CONPRM, it looks for dbo.CONPRM

When you remove the repository login from the sysadmin server role, the repository login can default to the ignite schema.

Resolution

  1. Remove the repository login from the sysadmin server role.
    For more information see ALTER SERVER ROLE (© 2018 Microsoft, available at https://docs.microsoft.com, obtained on January 22, 2018).
  2. Add the repository login to the db_owner database role.
    For more information see ALTER ROLE (© 2018 Microsoft, available at https://docs.microsoft.com, obtained on January 22, 2018).
  3. Make sure the repository login defaults to the ignite schema.
    For more information see ALTER USER (© 2018 Microsoft, available at https://docs.microsoft.com, obtained on January 22, 2018).
  4. Restart DPA.

 

Last modified

Tags

Classifications

Public