There can be multiple reasons for this error.
1- Through a series of CREATE synonym statements, a synonym was defined that referred
to itself.
For example, the following definitions are circular:
CREATE SYNONYM s1 for s2
CREATE SYNONYM s2 for s3
CREATE SYNONYM s3 for s1
Change one synonym definition so that it applies to a base table or view and retry the operation.
2- We create a public synonym on a non-existing table. And when we try to access the public synonym we get the error. If the public synonym name and the table name are the same then we get ORA-01775. If they are different then we get ORA-00980. This is the behavior on a 10g database and above.
3- Some times querying the views like dba_blockers, dba_users etc gives this error. It can be due the view definition corruption. You shoueld recreate the view in this case.
eg;
SQL> @?/rdbms/admin/catblock.sql
1- Through a series of CREATE synonym statements, a synonym was defined that referred
to itself.
For example, the following definitions are circular:
CREATE SYNONYM s1 for s2
CREATE SYNONYM s2 for s3
CREATE SYNONYM s3 for s1
Change one synonym definition so that it applies to a base table or view and retry the operation.
2- We create a public synonym on a non-existing table. And when we try to access the public synonym we get the error. If the public synonym name and the table name are the same then we get ORA-01775. If they are different then we get ORA-00980. This is the behavior on a 10g database and above.
3- Some times querying the views like dba_blockers, dba_users etc gives this error. It can be due the view definition corruption. You shoueld recreate the view in this case.
eg;
SQL> @?/rdbms/admin/catblock.sql
No comments:
Post a Comment