Hi guys, I'm having serius problems with Hibernate3 and Oracle10g.

When my app is trying to SELECT from some table (ex. mytable), using the correct mapped object, I'm getting a "ORA-01031 Insufficient Privileges", although the current user has all the privileges needed for the app in order to access the superuser schema objects (I mean the owner for those tables). The more rare thing is that I can (using the app user) SELECT from that table without problems when using SQL*PLUS.

Also, I can SELECT from anothers tables in that schema using Hibernate mapping, but something odd is happing whit certain tables.

Can somebody give a hint about this situation?

Thanks in advance,

Are these system tables in a system schema? If so, witch tables are you having problems with?

Perhaps you can check you hibernate.cfg.xml to see if the correct user is configured.

Another thing you can try, is to create a synoniem in the schema from where you're working to the system table. That should work i guess

The table is owned by the ADM schema (it's the app owner or the superuser)....



Everything is Ok in hibernate.cfg.xml, and also we have correct access to other tables owned by ADM.



The user "appuser1" has access to the ADM schema objects through synonyms and it has granted all the privileges needed by a ROLE asigned to each user that will access the app.

The rare thing is that we can "select" from that table when using SQL*Plus.

HELP!!!!

Well, for all ppl that have Ora-01031 problems with no reason. We check inside Hibernate configuration in the current application and found that the ppl that made this app used a user and password in "hard code" into the hibernate and web context configurations. In this way the users who login to the application was not making severals access to the rdbms, but the "hard code" user was. this hard code user has not the ROLES needed in this new environment (a Oracle AS and a Oracle1g rdbms, both for development), and that user was generating the "ORA-01031 Insuffient Privileges" couse this user did the connection to the rdbms and not the user who loged in.

Now, we are trying to "remove" this aproach (and of course delete the "hard code" user in the hibernate config) and implement a login proccess where we can use a rdbms authentication and authorization.

Any hints at this moment will be apreciated.

Atte,