Sometimes when the client fails to connect to a remote database, it will then try to connect to a local database on the machine (for reasons I've never understood truthfully), and when a local db doesnt exist, you get 12560. In that case, ignore the 12560 and troubleshoot the error that came before that. Usually there are two traces generated in that case; is the error in the other one?
What's the actual error you get reported to the oo4o app?
It only creates one .trc and one .log, the content of which are included above.
The vb app just displays the 12560 error.
Am I missing some logging options in my sqlnet.ora file, in order to get this second trace file?
Did you debug the app to CONFIRM that "BCDAT" is being passed? If you pass null, then a bequeath connection will be attempted, and you'll get 12560. The sqlnet trace snippet you've provided fairly clearly shows the app is trying to connect via bequeath.
Edited by: gdarling on Apr 6, 2012 10:24 AM
vb6 is not installed on the server so I have not
this is a production app, that does work on all of our client PCs and on our other server 2008 r2 server
I can make a temp release that will confirm what is sent in, but I'm very confident it is not sending a null
well I'll be a son of you know what
I did a test release and it appears you are correct on the null value, I will do some more digging and let you know the final results.
Thanks, I have a bit of hope now :-)