Hi,
maybe an errorstack will help: alter system set events '1017 trace name
errorstack level 3; name library_cache level 10';
When the Ora-1017 happens it will log to the alert.log and give the trace file.
To end the situation: alter system set events '1017 trace name errorstack off;
name library_cache off' ;
Herald ten Dam
Superconsult
________________________________________
Van: oracle-l-bounce@xxxxxxxxxxxxx [oracle-l-bounce@xxxxxxxxxxxxx] namens Scott
Canaan [srcdco@xxxxxxx]
Verzonden: donderdag 14 januari 2016 14:34
Aan: oracle-l@xxxxxxxxxxxxx
Onderwerp: Capturing user / password For Failed Logins
We have an application that is getting an ORA-01017 when trying to connect to
the database. This is a new environment for this application. In the past,
the application was running on one server and the database on another. To
attempt to speed things up, we’ve co-located the application and database,
along with an upgrade to Oracle 12.1.0.2. In doing so, I installed both the
Oracle database software and Oracle client software in the same Oracle Home.
The idea is to use a bequeath connection and bypass the network to eliminate
the network traffic.
If the user uses SQL*Plus, they can connect to the database. Using the same
login, the application itself gets the ORA-01017. It is a COBOL application.
The vendor is insisting that they are passing the correct password. The SA is
insisting that I have to turn some tracing on to show the password being passed
in. As far as I know, the password is encrypted in the login process.
Is there any way to get this information? The vendor refuses to help us until
we can prove that the password being sent is wrong.
Scott Canaan ’88 (srcdco@xxxxxxx<mailto:srcdco@xxxxxxx>)
(585) 475-7886 – work (585) 339-8659 – cell
“Life is like a sewer, what you get out of it depends on what you put into it.”
– Tom Lehrer
--
//www.freelists.org/webpage/oracle-l
