Hey all, We've just changed our charactersets on our 8.1.7.2 (and 8.1.7.4) DBs from US7ASCII to WE8ISO8859P1 using the Oracle-approved "ALTER DATABASE CHARACTER SET WE8ISO8859P1" and accompanying commands. Everything works like a champ, but our Perl::DBI connections now all cause an invisibile "ORA-1017 invalid username/password" error. The error never appears in the client -- the only reason I know this happens is because I'm auditing for it.
Other than having our audit log tablespace fill up, this leaves me a little worried and I don't know how to track it down. Of course, since the apps all work without reporting the error we never caught it in our testing. The version of Perl is 5.005_03, the Oracle client is 8.0.5.0.0 on Solaris, and I don't know what version of DBI or DBD::Oracle. I've tested my much newer versions of Perl, Oracle client and DBI/DBD::Oracle under windows and no audit is generated. I've also connected using SQL*plus from the 8.0.5.0.0 client without audit. I'm going to try and debug this without affecting the production systems, but has anyone encountered this before? TIA! Rich Jesse System/Database Administrator [EMAIL PROTECTED] Quad/Tech International, Sussex, WI USA -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Jesse, Rich INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- 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).
