Raju Boddupalli
Raju Boddupalli

Reputation: 1819

HSQL database user lacks privilege or object not found error

I am trying to use hsqldb-2.3.4 to connect from Spring applicastion.

I created data base using the following details

Type : HSQL Database Engine Standalone
Driver: org.hsqldb.jdbcDriver
URL: jdbc:hsqldb:file:mydb
UserName: SA
Password: SA

I created a table named ALBUM under "MYDB" schema

In spring configuration file:

<bean id="jdbcTemplate"
    class="org.springframework.jdbc.core.namedparam.NamedParameterJdbcTemplate">
    <constructor-arg ref="dbcpDataSource" />
</bean>

<bean id="dbcpDataSource" class="org.springframework.jdbc.datasource.DriverManagerDataSource">
    <property name="driverClassName" value="org.hsqldb.jdbcDriver" />
    <property name="url" value="jdbc:hsqldb:file:mydb" />
    <property name="username" value="SA" />
    <property name="password" value="SA" />
</bean>

And in my spring controller I am doing jdbcTemplate.query("SELECT * FROM MYDB.ALBUM", new AlbumRowMapper());

And It gives me exception:

org.springframework.web.util.NestedServletException: Request processing failed; nested exception is org.springframework.jdbc.BadSqlGrammarException: PreparedStatementCallback; bad SQL grammar [SELECT * FROM MYDB.ALBUM]; nested exception is java.sql.SQLSyntaxErrorException: user lacks privilege or object not found: ALBUM
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:982)
org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:861)
javax.servlet.http.HttpServlet.service(HttpServlet.java:622)
org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:846)
javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)

If I execute same query through SQL editor of hsqldb it executes fine. Can you please help me with this.

Upvotes: 47

Views: 143862

Answers (22)

Jaykishan
Jaykishan

Reputation: 1499

In case you're in following state than this solution is for you,

  • You've a field with text type

  • But you're creating DDL from separate file i.e. enter image description here

    if above is the case then remove columnDefinition which is just being used in DDL creation to defined inferred type. (Make sure you're not doing auto DDL in your project.)

This will fix your table creation and then following insert/other query would work.

Upvotes: 0

Rudolf
Rudolf

Reputation: 127

Had the same problem. In my case when setting up the database.

If I created the database via a SQL client the creation succeeded, but when I tried to create the same SQL DDL from Java I got this weird error, which is not really helpful.

I decided to split up the SQL DDL statements into separate CREATE statements and did this the trick. Now all tables and indices were created without any problems.

BTW it does not matter if I use executeUpdate(DDL) or execute(DDL). Both fail with the same error message, unless I split those statements up.

INSERTing multiple statements works without any problems. I do not understand this inconsistent behaviour.

Upvotes: 0

IKo
IKo

Reputation: 5816

In my case the table MY_TABLE was in the schema SOME_SCHEMA. So calling select/insert etc. directly didn't work. To fix:

  1. add file schema.sql to the resources folder
  2. in this file add the line CREATE SCHEMA YOUR_SCHEMA_NAME;

Upvotes: 0

soumitra chatterjee
soumitra chatterjee

Reputation: 2328

I faced the same issue and found there was more than one PersistenceUnit (ReadOnly and ReadWrite) , So the tables in HSQLDDB created using a schema from one persistence unit resulted in exception(HSQL database user lacks privilege or object not found error) being thrown when accessed from other persistence unit .It happens when tables are created from one session in JPA and accessed from another session

Upvotes: 0

Venkata Rahul S
Venkata Rahul S

Reputation: 324

Yet another reason could be a misspelt field name. If your actual table has an id column named albumid and you'd used album_id, then too this could occur.

As another anwer remarked, case differences in field names too need to be taken care of.

Upvotes: 0

johnbr
johnbr

Reputation: 589

For what it's worth - I had this same problem. I had a column named 'TYPE', which I renamed to 'XTYPE' and a column named ORDER which I renamed to 'XORDER' and the problem went away.

Upvotes: 0

Matteoo37
Matteoo37

Reputation: 1

In my case, one of the columns had the name 'key' with the missing @Column(name = "key") annotation so that in the logs you could see the query that created the table but in fact it was not there. So be careful with column names

Upvotes: 0

Anil Kumar
Anil Kumar

Reputation: 11

Add these two extra properties:

spring.jpa.hibernate.naming.implicit-strategy=
org.hibernate.boot.model.naming.ImplicitNamingStrategyLegacyJpaImpl

spring.jpa.hibernate.naming.physical-strategy=
org.hibernate.boot.model.naming.PhysicalNamingStrategyStandardImpl

Upvotes: 1

user1929905
user1929905

Reputation: 457

You have to run the Database in server mode and connect.Otherwise it wont connect from external application and give error similar to user lacks privilege. Also change the url of database in spring configuration file accordingly when running DB in server mode.

Sample command to run DB in server mode $java -cp lib/hsqldb.jar org.hsqldb.server.Server --database.0 file:data/mydb --dbname.0 Test

Format of URL in configuration file jdbc:hsqldb:hsql://localhost/Test

Upvotes: 0

Oleg Fedoruk
Oleg Fedoruk

Reputation: 1

I had this error while trying to run my application without specifying the "Path" field in Intellij IDEA data source (database) properties. Everything else was configured correctly.

I was able to run scripts in IDEA database console and they executed correctly, but without giving a path to the IDEA, it was unable to identify where to connect, which caused errors.

Upvotes: 0

sxc731
sxc731

Reputation: 2638

In my case the issue was caused by the absence (I'd commented it out by mistake) of the following line in persistence.xml:

<property name="hibernate.hbm2ddl.auto" value="update"/>

which prevented Hibernate from emitting the DDL to create the required schema elements...

(different Hibernate wrappers will have different mechanisms to specify properties; I'm using JPA here)

Upvotes: 0

Chidi
Chidi

Reputation: 991

had this issue with concatenating variables in insert statement. this worked

// var1, var3, var4 are String variables
// var2 and var5 are Integer variables
result = statement.executeUpdate("INSERT INTO newTable VALUES ('"+var1+"',"+var2+",'"+var3+"','"+var4+"',"+var5 +")");

Upvotes: 0

R.A
R.A

Reputation: 1871

In my case the error occured because i did NOT put the TABLE_NAME into double quotes "TABLE_NAME" and had the oracle schema prefix.

Not working:

SELECT * FROM FOOSCHEMA.BAR_TABLE

Working:

SELECT * FROM "BAR_TABLE"

Upvotes: 0

Damien MIRAS
Damien MIRAS

Reputation: 908

As said by a previous response there is many possible causes. One of them is that the table isn't created because of syntax incompatibility. If specific DB vendor syntax or specific capability is used, HSQLDB will not recognize it. Then while the creation code is executed you could see that the table is not created for this syntax reason. For exemple if the entity is annoted with @Column(columnDefinition = "TEXT") the creation of the table will fail.

There is a work around which tell to HSQLDB to be in a compatible mode for pgsl you should append your connection url with that

"spring.datasource.url=jdbc:hsqldb:mem:testdb;sql.syntax_pgs=true"

and for mysql with

"spring.datasource.url=jdbc:hsqldb:mem:testdb;sql.syntax_mys=true"

oracle

"spring.datasource.url=jdbc:hsqldb:mem:testdb;sql.syntax_ora=true" 

note there is variant depending on your configuration it could be hibernate.connection.url= or spring.datasource.url= for those who don't use the hibernate schema creation but a SQL script you should use this kind of syntax in your script

SET DATABASE SQL SYNTAX ORA TRUE;

It will also fix issues due to vendor specific syntax in SQL request such as array_agg for posgresql

Nota bene : The the problem occurs very early when the code parse the model to create the schema and then is hidden in many lines of logs, then the unitTested code crash with a confusing and obscure exception "user lacks privilege or object not found error" which does not point the real problem at all. So make sure to read all the trace from the beginning and fix all possible issues

Upvotes: 20

Eduardo Mior
Eduardo Mior

Reputation: 244

I was having the same mistake. In my case I was forgetting to put the apas in the strings.

I was doing String test = "inputTest";

The correct one is String test = "'inputTest'";

The error was occurring when I was trying to put something in the database

connection.createStatement.execute("INSERT INTO tableTest values(" + test +")";

In my case, just put the quotation marks ' to correct the error.

Upvotes: 0

batristio
batristio

Reputation: 160

I bumped into kind of the same problem recently. We are running a grails application and someone inserted a SQL script into the BootStrap file (that's the entry point for grails). That script was supposed to be run only in the production environment, however because of bad logic it was running in test as well. So the error I got was:

User lacks privilege or object not found:

without any more clarification...

I just had to make sure the script was not run in the test environment and it fixed the problem for me, though it took me 3 hours to figure it out. I know it is very, very specific issue but still if I can save someone a couple of hours of code digging that would be great.

Upvotes: 0

cammando
cammando

Reputation: 616

I was inserting the data in hsql db using following script

INSERT INTO Greeting (text) VALUES ("Hello World");

I was getting issue related to the Hello World object not found and HSQL database user lacks privilege or object not found error

which I changed into the below script

INSERT INTO Greeting (text) VALUES ('Hello World');

And now it is working fine.

Upvotes: 2

LCM
LCM

Reputation: 186

When running a HSWLDB server. for example your java config file has:

hsql.jdbc.url = jdbc:hsqldb:hsql://localhost:9005/YOURDB;sql.enforce_strict_size=true;hsqldb.tx=mvcc

check to make sure that your set a server.dbname.#. for example my server.properties file:

    server.database.0=eventsdb 
    server.dbname.0=eventsdb 
    server.port=9005

Upvotes: 1

Nirmal Mangal
Nirmal Mangal

Reputation: 812

I had similar issue with the error 'org.hsqldb.HsqlException: user lacks privilege or object not found: DAYS_BETWEEN' turned out DAYS_BETWEEN is not recognized by hsqldb as a function. use DATEDIFF instead.

DATEDIFF ( <datetime value expr 1>, <datetime value expr 2> )

Upvotes: 2

Abbas Gadhia
Abbas Gadhia

Reputation: 15128

If you've tried all the other answers on this question, then it is most likely that you are facing a case-sensitivity issue.

HSQLDB is case-sensitive by default. If you don't specify the double quotes around the name of a schema or column or table, then it will by default convert that to uppercase. If your object has been created in uppercase, then you are in luck. If it is in lowercase, then you will have to surround your object name with double quotes.

For example:

CREATE MEMORY TABLE "t1"("product_id" INTEGER NOT NULL)

To select from this table you will have to use the following query

select "product_id" from "t1"

Upvotes: 16

Arigion
Arigion

Reputation: 3558

I had the error user lacks privilege or object not found while trying to create a table in an empty in-memory database. I used spring.datasource.schema and the problem was that I missed a semicolon in my SQL file after the "CREATE TABLE"-Statement (which was followed by "CREATE INDEX").

Upvotes: 3

Arthur Noseda
Arthur Noseda

Reputation: 2664

user lacks privilege or object not found can have multiple causes, the most obvious being you're accessing a table that does not exist. A less evident reason is that, when you run your code, the connection to a file database URL actually can create a DB. The scenario you're experiencing might be you've set up a DB using HSQL Database Manager, added tables and rows, but it's not this specific instance your Java code is using. You may want to check that you don't have multiple copies of these files: mydb.log, mydb.lck, mydb.properties, etc in your workspace. In the case your Java code did create those files, the location depends on how you run your program. In a Maven project run inside Netbeans for example, the files are stored alongside the pom.xml.

Upvotes: 13

Related Questions