java.sql.SQLException: Invalid object name 'jiraissue'.

Atlassian JIRA | Daryl Chuah | 7 months ago
  1. 0

    h3. Summary Based on this KB article [here|https://confluence.atlassian.com/jirakb/testing-database-access-speed-54362302.html], the testing database access tool only works on {{dbo}} schema which is the default schema in MSSQL. h3. Environment * Microsoft SQL Server 2012 h3. Steps to Reproduce # Try the steps in this KB article [here|https://confluence.atlassian.com/jirakb/testing-database-access-speed-54362302.html] using {{jiraschema}} in MSSQL database h3. Expected Results {code} Benchmark: JIRA SQL: jdbc:jtds:sqlserver://localhost:1433;instance=SQL;DatabaseName=jira7104 # retrieve-issue get-issue retrieve-workflow get-workflow retrieve-custom-field-value get-custom-field-value 0 2,707,052 4,403,985 30,680,352 111,190 307,911 91,090 1 360,084 198,859 266,857 47,897 224,519 54,312 2 283,963 402,851 233,927 65,432 227,939 89,380 3 5,632,636 277,976 413,114 113,329 274,126 86,813 4 290,805 91,090 232,216 47,898 177,049 45,759 5 274,981 185,175 222,380 54,740 174,056 41,055 6 260,869 98,361 202,708 53,029 182,609 57,733 7 237,348 174,483 254,455 61,155 239,486 61,582 8 325,872 147,540 220,670 40,199 173,628 39,772 9 232,644 83,820 164,647 41,911 354,953 45,331 10 458,446 556,378 593,157 61,154 238,631 91,518 11 360,512 215,965 294,226 61,155 211,262 57,306 12 441,340 199,715 248,895 43,621 201,425 65,431 13 300,641 119,743 239,914 54,739 183,036 41,482 14 254,882 115,467 183,464 39,344 159,943 41,482 TOTALS ---- ---- ---- ---- ---- stat mean median min max ---- ---- ---- ---- ---- retrieve-issue 828,138 300,641 232,644 5,632,636 get-issue 484,760 185,175 83,820 4,403,985 retrieve-workflow 2,296,732 239,914 164,647 30,680,352 get-workflow 59,786 54,739 39,344 113,329 retrieve-custom-field-value 222,038 211,262 159,943 354,953 get-custom-field-value 60,669 57,306 39,772 91,518 ---- ---- ---- ---- ---- All times are in nanoseconds. {code} h3. Actual Results The below exception is being thrown in: {noformat} Exception in thread "main" java.sql.SQLException: Invalid object name 'jiraissue'. at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:372) at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2988) at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2421) at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:671) at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQLQuery(JtdsStatement.java:505) at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeQuery(JtdsPreparedStatement.java:1029) at com.atlassian.util.benchmark.JIRASQLPerformance.getTests(JIRASQLPerformance.java:92) at com.atlassian.util.benchmark.JIRASQLPerformance.call(JIRASQLPerformance.java:80) at com.atlassian.util.benchmark.JIRASQLPerformance.main(JIRASQLPerformance.java:61) {noformat} h3.Workaround The only workaround is to switch it to {{dbo}} schema.

    Atlassian JIRA | 7 months ago | Daryl Chuah
    java.sql.SQLException: Invalid object name 'jiraissue'.
  2. 0

    h3. Summary Based on this KB article [here|https://confluence.atlassian.com/jirakb/testing-database-access-speed-54362302.html], the testing database access tool only works on {{dbo}} schema which is the default schema in MSSQL. h3. Environment * Microsoft SQL Server 2012 h3. Steps to Reproduce # Try the steps in this KB article [here|https://confluence.atlassian.com/jirakb/testing-database-access-speed-54362302.html] using {{jiraschema}} in MSSQL database h3. Expected Results {code} Benchmark: JIRA SQL: jdbc:jtds:sqlserver://localhost:1433;instance=SQL;DatabaseName=jira7104 # retrieve-issue get-issue retrieve-workflow get-workflow retrieve-custom-field-value get-custom-field-value 0 2,707,052 4,403,985 30,680,352 111,190 307,911 91,090 1 360,084 198,859 266,857 47,897 224,519 54,312 2 283,963 402,851 233,927 65,432 227,939 89,380 3 5,632,636 277,976 413,114 113,329 274,126 86,813 4 290,805 91,090 232,216 47,898 177,049 45,759 5 274,981 185,175 222,380 54,740 174,056 41,055 6 260,869 98,361 202,708 53,029 182,609 57,733 7 237,348 174,483 254,455 61,155 239,486 61,582 8 325,872 147,540 220,670 40,199 173,628 39,772 9 232,644 83,820 164,647 41,911 354,953 45,331 10 458,446 556,378 593,157 61,154 238,631 91,518 11 360,512 215,965 294,226 61,155 211,262 57,306 12 441,340 199,715 248,895 43,621 201,425 65,431 13 300,641 119,743 239,914 54,739 183,036 41,482 14 254,882 115,467 183,464 39,344 159,943 41,482 TOTALS ---- ---- ---- ---- ---- stat mean median min max ---- ---- ---- ---- ---- retrieve-issue 828,138 300,641 232,644 5,632,636 get-issue 484,760 185,175 83,820 4,403,985 retrieve-workflow 2,296,732 239,914 164,647 30,680,352 get-workflow 59,786 54,739 39,344 113,329 retrieve-custom-field-value 222,038 211,262 159,943 354,953 get-custom-field-value 60,669 57,306 39,772 91,518 ---- ---- ---- ---- ---- All times are in nanoseconds. {code} h3. Actual Results The below exception is being thrown in: {noformat} Exception in thread "main" java.sql.SQLException: Invalid object name 'jiraissue'. at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:372) at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2988) at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2421) at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:671) at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQLQuery(JtdsStatement.java:505) at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeQuery(JtdsPreparedStatement.java:1029) at com.atlassian.util.benchmark.JIRASQLPerformance.getTests(JIRASQLPerformance.java:92) at com.atlassian.util.benchmark.JIRASQLPerformance.call(JIRASQLPerformance.java:80) at com.atlassian.util.benchmark.JIRASQLPerformance.main(JIRASQLPerformance.java:61) {noformat} h3.Workaround The only workaround is to switch it to {{dbo}} schema.

    Atlassian JIRA | 7 months ago | Daryl Chuah
    java.sql.SQLException: Invalid object name 'jiraissue'.
  3. 0

    JasperReports JDBC TDS: internal error 2

    Stack Overflow | 3 years ago | user3489096
    net.sf.jasperreports.engine.JRException: Error executing SQL statement for : MSWST
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Using Hibernate and getting Server 'XXX' in 'sys.servers' not found

    Stack Overflow | 3 years ago | Artur Rem
    org.hibernate.exception.GenericJDBCException: could not extract ResultSet

  1. ruifung 1 times, last 3 months ago
12 unregistered visitors
Not finding the right solution?
Take a tour to get the most out of Samebug.

Tired of useless tips?

Automated exception search integrated into your IDE

Root Cause Analysis

  1. java.sql.SQLException

    Invalid object name 'jiraissue'.

    at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic()
  2. jTDS
    JtdsPreparedStatement.executeQuery
    1. net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:372)
    2. net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2988)
    3. net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2421)
    4. net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:671)
    5. net.sourceforge.jtds.jdbc.JtdsStatement.executeSQLQuery(JtdsStatement.java:505)
    6. net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeQuery(JtdsPreparedStatement.java:1029)
    6 frames
  3. com.atlassian.util
    JIRASQLPerformance.main
    1. com.atlassian.util.benchmark.JIRASQLPerformance.getTests(JIRASQLPerformance.java:92)
    2. com.atlassian.util.benchmark.JIRASQLPerformance.call(JIRASQLPerformance.java:80)
    3. com.atlassian.util.benchmark.JIRASQLPerformance.main(JIRASQLPerformance.java:61)
    3 frames