Hi, We're trying to prevent users from connecting to our production database via "illegal" connections (i.e. tools like TOAD, etc.).
Does anyone have any suggestions on how to block connections from query tools (i.e. Toad, SQL Nav, etc.) in such a way that an error message is reported back to the tool user that the connection is prohibited? We've tried designing a logon trigger with a PRAGMA definition but the error message is not getting relayed back to the client. As always, your feedback is appreciated! -w __________________________________________________ Do You Yahoo!? Check out Yahoo! Shopping and Yahoo! Auctions for all of your unique holiday gifts! Buy at http://shopping.yahoo.com or bid at http://auctions.yahoo.com -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Walter K INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
