Bruce_Wilkins
asked on
ORACLE 12638
ORA-12638 CREDENTIAL RETRIEVAL FAILED
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I'd have to assume that all 3 of us answered the question. Suggest 3-way split.
make sure that your oracle home is in the right place. mine wasn't. :-)
Here's some notes on how to do tracing.
Trace File Locations and Names
To enable tracing for the Net8 client, we need to set some parameters in the sqlnet.ora file. The default client trace filename is sqlnet.trc (cli.trc on some systems), and the default location is the $ORACLE_HOME /network /trace directory. To change those values, we can place entries such as the following in the sqlnet.ora file:
TRACE_FILE_CLIENT = host_problem.trc
TRACE_DIRECTORY_CLIENT = e:\oracle\ora81\network\tr
The sqlnet.ora file also supports TRACE_FILE_SERVER and TRACE_DIRECTORY_SERVER parameters. Those apply when you're tracing Net8's server functionality. For most client connectivity problems, you'll want to set the two client parameters shown here.
Never make your trace directory the root directory (C:\ for example) on a Windows system because, as a result, Net8 will not write the trace file that you are asking for.
Setting the trace file location and name does not enable tracing. For tracing to occur, you must enable it by choosing a trace level.
Trace Levels
A trace level is a setting that controls the amount of detail that gets written to a trace file. The default trace level for all Net8 facilities is OFF, which results in no trace data being generated. The other levels, in order of increasing levels of detail, are USER, ADMIN, and SUPPORT. There's no real semantic meaning to these keywords, at least not so far as we've ever been able to determine. Just realize that USER gets you some trace output, ADMIN gets you more, and SUPPORT will overwhelm you. When we enabled SUPPORT level tracing for the simple SQL*Plus connection attempt shown earlier, our resulting trace file was 820 lines long! That's a lot to read through. For this example, we'll use the ADMIN level, and we'll enable tracing at that level by placing the following line in our sqlnet.ora file:
TRACE_LEVEL_CLIENT = ADMIN
Now, with tracing enabled, all that's left to do is to generate the error by repeating our connection attempt. Then we can look in the trace file where we will find some clue as to what is going wrong.