Hi List
Well, we figured it out. Here was the sequence of events
T1 - init ora parameter dblink_encrypt_login set to true in the target database
T2 - synonym created
T3 - init ora parameter dblink_encrypt_login set to false in the target database
The synonym created at T2 will never work again. Further if you reference that synonym you will cerate a connection to the target database that will not let you drop that synonym. Evil.
Another thing to know about dblink_encrypt_login is that the Oracle Gateway products will not work with that parameter set to true.
All of this just in case you ever have to deal with peach_fuzz_cheeked, checklist_toting, dumb_as_a_post auditors who want you to turn that parameter on.
Allan L. Nelson
Oracle DBA
M-I L.L.C.
(832) 295-2238 office
(832) 351-4180 fax
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
______________________________________________________________________________
This email is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. Copying, forwarding or distributing this message by persons or entities other than the addressee is prohibited. If you have received this email in error, please contact the sender immediately and delete the material from any computer. This email may have been monitored for policy compliance. [021216]
