Hi,
I have a sequence and a table in a database that I am trying to access
via a WebSphere application, but I get an ORA-00980 error. I CAN
access these same objects with SQLDeveloper. I use the same database,
username and password for both the web application and for
SQLDeveloper, but I do not understand why I cannot access these
objects from the application. Any suggestions?
Thanks!

lord.zoltar@gmail.com wrote in news:1193238903.591802.91630
@y27g2000pre.googlegroups.com:

> Hi,
> I have a sequence and a table in a database that I am trying to access
> via a WebSphere application, but I get an ORA-00980 error. I CAN
> access these same objects with SQLDeveloper. I use the same database,
> username and password for both the web application and for
> SQLDeveloper, but I do not understand why I cannot access these
> objects from the application. Any suggestions?
> Thanks!
>
>

oerr ora 980
00980, 00000, "synonym translation is no longer valid"
// *Cause:
// *Action:

Ana C. Dent wrote:
>
> oerr ora 980
> 00980, 00000, "synonym translation is no longer valid"
> // *Cause:
> // *Action:

Thanks,
I've seen that description for the error before. The problem I am
encountering is that SQLDeveloper is able to access the objects in
question just fine, but the application CANNOT access them. I run the
application with the same user/password and database as I do for
SQLDeveloper.

lord.zoltar@gmail.com wrote in news:1193252125.964107.202420
@i13g2000prf.googlegroups.com:

>
> Ana C. Dent wrote:
>>
>> oerr ora 980
>> 00980, 00000, "synonym translation is no longer valid"
>> // *Cause:
>> // *Action:
>
> Thanks,
> I've seen that description for the error before. The problem I am
> encountering is that SQLDeveloper is able to access the objects in
> question just fine, but the application CANNOT access them. I run the
> application with the same user/password and database as I do for
> SQLDeveloper.
>
>

You provide only scant details of the error code.
Since I can't see "the application",
I have NO idea exactly what you are trying to do.
I have no idea if this is new code or something that has worked in the
past.
I have no idea how, what or why the synonym comes into play.
Since you decided to keep all these details to yourself,
I'll decide to not speculate what might be the problem or possible
solution.

Just a guess:

This could be due to privileges inherited from roles. If you don't
grant
privileges directly, stored procedures will not see referenced
objects
(roles are disabled for them unless they are authid current_user).

Make sure the owner of the program unit has directly-assigned
privileges (NOT via a role) on the synonym's target object.

On Oct 25, 9:56 am, epoko...@excite.com wrote:
> Just a guess:
>
> This could be due to privileges inherited from roles. If you don't
> grant
> privileges directly, stored procedures will not see referenced
> objects
> (roles are disabled for them unless they are authid current_user).
>
> Make sure the owner of the program unit has directly-assigned
> privileges (NOT via a role) on the synonym's target object.

Problem was resolved. You were close, I think it was something to do
with this as well as some sort of problem with some of the schemas
that some of the users were in. There was also an application config
problem that was certainly not making it easier to fix. I think in the
end the DBA recreated all the objects and I reconfigured the app. Now
things work. Not sure what the root cause was, but glad it's over.

On Oct 26, 9:40 am, lord.zol...@gmail.com wrote:
> On Oct 25, 9:56 am, epoko...@excite.com wrote:
>
> > Just a guess:
>
> > This could be due to privileges inherited from roles. If you don't
> > grant
> > privileges directly, stored procedures will not see referenced
> > objects
> > (roles are disabled for them unless they are authid current_user).
>
> > Make sure the owner of the program unit has directly-assigned
> > privileges (NOT via a role) on the synonym's target object.
>
> Problem was resolved. You were close, I think it was something to do
> with this as well as some sort of problem with some of the schemas
> that some of the users were in. There was also an application config
> problem that was certainly not making it easier to fix. I think in the
> end the DBA recreated all the objects and I reconfigured the app. Now
> things work. Not sure what the root cause was, but glad it's over.


Excellent explanation. So you don't know what the problem was .. but
state that "You were close".
And I love the "there was SOME sort of problem with SOME of the
schemas
that SOME of the users were in".

I need to use that wording more often to describe issues.



Anurag