{ "date": "2016-06-21T12:13:25", "slug": "ora-01775-looping-chain-of-synonyms", "link": "https://www.dbi-services.com/blog/ora-01775-looping-chain-of-synonyms/", "title": { "rendered": "ORA-01775: looping chain of synonyms" }, "content": { "rendered": "

By Franck Pachot

\n

.
\nThis error message is misleading. You may encounter it when you expect ORA-00942: table or view does not exist. Let’s explain
\n
\nI’m connected as SCOTT and create a PUBLIC SYNONYM for an object that do not exists:

\n
\nSQL> create public synonym MONEY for NOTHING;\nSynonym created.\n
\n

No error message.
\nOnly when I read it I have an error message telling me that there are no table or view behind it:

\n
\nSQL> select * from NOTHING;\nselect * from NOTHING\n              *\nERROR at line 1:\nORA-00942: table or view does not exist\n
\n

Let’s do the same but call it BONUS instead of MONEY:

\n
\nSQL> create public synonym BONUS for NOTHING;\nSynonym created.\n \nSQL> select * from BONUS;\nno rows selected\n
\n

No error here. Why? because I’ve a table that is called BONUS. So the name is resolved with the table and the synonym is not even tried.

\n

I’ll now drop that synonym and create it for the table BONUS. Same name for the public synonym and for the table.

\n
\nSQL> drop public synonym BONUS;\nSynonym dropped.\n \nSQL> create public synonym BONUS for BONUS;\nSynonym created.\n
\n

As user SCOTT, when I query BONUS the name is resolved as the table:

\n
\nSQL> show user\nUSER is \"SCOTT\"\nSQL> select * from BONUS;\nno rows selected\n
\n

As another user, when I query BONUS the name is resolved as the synonym, which finally reads SCOTT.BONUS:

\n
\nSQL> show user\nUSER is \"SCOTT\"\nSQL> select * from BONUS;\nno rows selected\n
\n

In 12c it is easy to see the final query:

\n
\nSQL> variable c clob\nSQL> exec dbms_utility.expand_sql_text('select * from BONUS',:c);\nPL/SQL procedure successfully completed.\n \nSQL> print c\n \nC\n----------------------------------------------------------------------------------------------------------\nSELECT \"A1\".\"ENAME\" \"ENAME\",\"A1\".\"JOB\" \"JOB\",\"A1\".\"SAL\" \"SAL\",\"A1\".\"COMM\" \"COMM\" FROM \"SCOTT\".\"BONUS\" \"A1\"\n
\n

But now, what happens when we drop the table?

\n
\nSQL> drop table SCOTT.BONUS;\nTable dropped.\n
\n

Do you expect a ORA-00942: table or view does not exist?

\n
\nSQL> select * from BONUS;\nselect * from BONUS\n              *\nERROR at line 1:\nORA-01775: looping chain of synonyms\n
\n

Here is the ‘looping chain of synonyms’. I ask for BONUS. The name resolution first check for an object in my schema, but there are none:

\n
\nSQL> select object_type from user_objects where object_name='BONUS';\nno rows selected\n
\n

Then it looks for public synonym and there is one:

\n
\nSQL> select object_type from all_objects where owner='PUBLIC' and object_name='BONUS';\n \nOBJECT_TYPE\n-----------------------\nSYNONYM\n
\n

So we check what it is a synonym for:

\n
\nSQL> select table_owner,table_name from all_synonyms where owner='PUBLIC' and synonym_name='BONUS';\n \nTABLE_OWNER  TABLE_NAME\n------------ ------------\nSCOTT        BONUS\n
\n

And there it is interesting. Besides the column names that includes ‘TABLE’ a synonym can reference any object. So it’s not just replacing the synonym with ‘SCOTT.BONUS’ which would raise an ORA-00942. It is doing name resolution of BONUS in the context of the user SCOTT. Something similar to:

\n
\nSQL> alter session set current_schema=SCOTT;\nSession altered.\nSQL> select * from BONUS;\n
\n

And then, what do you expect from that? There is no table named BONUS but there is a public synonym… and you’re back to the begining:

\n
\nselect * from BONUS\n              *\nERROR at line 1:\nORA-01775: looping chain of synonyms\n
\n

Most of the time, you don’t have synonyms that reference other synonyms, so you don’t really have a ‘chain’ of synonyms. Except when there is only synonym in the namespace and it’s a self-reference loop. So if you see ORA-01775, check if the referenced object is not missing.

\n", "protected": false } }