Ora 00980: synonym translation no longer valid

building semantic layer
1

Hi,
i am getting an error ora 00980 while opening my universe. i have tried to drop that particular synonym and re created it but its of no use.
At database level this synonym is having data.
Please provide me with solution. :crazy_face:

shwetu_k85 (BOB member since 2008-05-14)

2

Hi,
Welcome to B:mrgreen:b,
This seems to be more of the database side. So please contact your dba first.

Please refrain from using words like Please provide me with solution,
This can be taken as a rude behaviour and is agaisnt the forum rule. This is not a paid forum and each and every bober is doing the work on the voluntary basis.

Omkar Paranjpe :us: (BOB member since 2006-02-13)

3

I have checked with that synonym by myself and i have recreated it that seems to be fine.

shwetu_k85 (BOB member since 2008-05-14)

4

I am able to resolve the problem…thanks…

shwetu_k85 (BOB member since 2008-05-14)

5

Hi,
Can you share us the way you got it solved. It may be useful for the future search.

Omkar Paranjpe :us: (BOB member since 2006-02-13)

6

I am now having this problem too, but it doesn’t tell me which synonym is not valid. I have changed a table name in the database from one universe to the other and a field was added, but I changed the Select statement of each object and all the CUIDs are still the same.

In a DESKI 3.0 Report, the universe can be changed fine, but when trying to change the universe in WEBI 3.0 Report, I get the “synonym translation no longer valid.” We are in the middle of migrating to WEBI only, so this is a problem.

The current universe is pointing to Production Database and the new universe is pointing to the test database. Our connections and synonyms are set up so that all i have to do is change the connection to switch to production from test. However the new table name is only in test, and will replace the old table when we put it in production.

Does anyone have any ideas?

Lots of thank yous for every report we don’t have to recreate or reconvert!

twatson (BOB member since 2008-10-07)

7

To fix my problem above, I had to create the alias used in production in the test environment. When I move to production, I will have to create the test alias in the production enivronment.
We basically just pointed both aliases to the same table.

Problem went away.
Thanks,
Trish

twatson (BOB member since 2008-10-07)