When trying to do anything with the synonym, there is no response - no
error - no results - hangs for a very long time.
Attempted things done that all hang:
Select * from our_synonym;
drop public synonym our_synonym FORCE;
create or replace public synonym our_synonym for some_other_table;
Any ideas on why this is happening and what the remedy is?
Thanks
Bob
Maybe if you tell us the exact name of our_synonym.
IIRC, you can't db-link from 10g to 8i directly (not sure about that though)
Shakespeare
You can if the 8i is 8.1.7.4; nothing earlier than that, though.
David Fitzjarrell
1. You can link (we are using 8.1.7.4 - as correctly suggested by
Fitz).
2. How would my synonym name help you to respond?
3. Maybe I am cranky now (late afternoon) - but why did you bother
responding with no info?
1) I told you I was not sure, and Fitz corrected it correctly. If you had
bothered to state your version in your question, I might have looked it up
before answering.
2) You would be surprised how many people tried to drop a synonym which
appeared to be a reserved word or something alike... and put a question on a
forum
3) OK. I'll put you on my ignore list if you like
Shakespeare
It wasn't a suggestion, it was a statement of fact.
> 2. How would my synonym name help you to respond?
It may be that you've decided to choose a name for your synonym listed
in V$RESERVED_WORDS; not all of those entries throw an error when used
for other purposes.
I understand that this next request may appear strange, but does the
following query return in a timely manner:
select distinct owner
from v$access;
If not then the issue *may* revolve around fixed object statistics;
executing dbms_stats.gather_fixed_objects_stats(NULL) *may* fix your
situation. Then, again, it may not fix anything. Offering advice to
one who cannot, or will not, provide sufficient information about the
problem is difficult, at best.
> 3. Maybe I am cranky now (late afternoon) - but why did you bother
> responding with no info?
Possibly because you provided so little with which to work in your
original post and in this follow-up.
David Fitzjarrell
Okay - sorry for being cranky. Anyway - the problem is this - we have
circular links - a public synonym on both 8i and 10g pointing to each
other through reverse database links. Now, I just got on this project
and I did not set it up. However, a post on the internet from "Neil
Jarvis" indicates that in this situation, once the synonym is used
through the link, it will just hang every other DDL/DML statement
related to the public synonym and not return with an error or
anything. This is what we are seeing and he provides a solution which
I am going to try.
See link "Bugs, Quirks and Features" on the following link (it is a
word document).
http://www.go-faster.co.uk/bugs.htm
Apologies granted.
> Anyway - the problem is this - we have
> circular links - a public synonym on both 8i and 10g pointing to each
> other through reverse database links. Now, I just got on this project
> and I did not set it up. However, a post on the internet from "Neil
> Jarvis" indicates that in this situation, once the synonym is used
> through the link, it will just hang every other DDL/DML statement
> related to the public synonym and not return with an error or
> anything. This is what we are seeing and he provides a solution which
> I am going to try.
>
> See link "Bugs, Quirks and Features" on the following link (it is a
> word document).
> http://www.go-faster.co.uk/bugs.htm
Interesting link, thanks.
Shakespeare
After alerting developers to beware, I killed all sessions that were
coming through a DB_Link
select * from v$session where username='Our_Database_Link';
Then I was able to drop the public synonym that was causing all the
trouble and recreate the synonyms properly.
Everyone is happy and up and running.
Bob