We help IT Professionals succeed at work.

Oracle DB Login Failure

alexcheng
alexcheng asked
on
Why does my oracle return this error when i try to login?
ORA-12638: Credential Retrieval failed

using SQL*PLUS, even Net8 when trying to login
What is wrong with my Database?
Comment
Watch Question

CERTIFIED EXPERT
Top Expert 2004

Commented:
TNS-12638 Credential retrieval failed
Cause: The authentication service failed to retrieve the credentials of a user.
Action: Enable tracing to determine the exact error.

Author

Commented:
A new error appeared after a reboot of the system....
ORA-12541: TNS:no listener
but my TNSListener service is runnning...
why?

Author

Commented:
The TNS Listener error is OK now.... but the Error "Credential retrieval failed" still exist...
how do i Enable tracing to determine the exact error?
by the way, i tried using all login accounts and came up with the same error.. even scott/tiger
Helena Markováprogrammer-analyst
CERTIFIED EXPERT

Commented:
Maybe this article will help you:

Solution Description:
=====================
 
1) The trace facility produces a detailed sequence of
   statements that describe network events as they are
   executed. "Tracing" an operation allows you to obtain
   more information on the internal operations of the
   components of Net8 than is provided in a log file.
   This information is output to files that can be
   evaluated to identify the events that led to an error.  
 
NOTE: The trace facility uses a large amount of disk space
      and may have a significant impact upon system
      performance. Therefore, you should enable tracing
      only when necessary.
 
Components that can be traced using the trace facility are:  
 * Network listener  
 * Net8 components on the client and server
 * Connection Manager  
 * Oracle Names Server
 * Oracle Names Control Utility
 * TNSPING utility
 
2) To enable tracing as well as to set specific trace
   parameters, choose one of the following methods and/or
   utilities:
 * Component Configuration Files
 * Component Control Utilities
 * Oracle Trace
 
To set tracing parameters using component configuration files:
 
   1.Execute or start the component to be traced.
 
   2.Set the following trace parameters in the component
     configuration file - SQLNET.ORA for client or server,
     LISTENER.ORA for listener:
 
TRACE_LEVEL_<CLIENT/LISTENER/SERVER>=(0/4/10/16)
          TRACE_DIRECTORY_<CLIENT/LISTENER/SERVER>=<directory name>
 
LOG_DIRECTORY_<CLIENT/LISTENER/SERVER>=<directory name>
 
   3.If you modified the configuration files while the
     component was running, start or restart the component
     to enable the changed parameters.
 
To set trace parameters using component control utilities:
 
   1.For the listener, use the LSNRCTL TRACE command from
     the Listener Control Utility, to set the trace level
     while the listener is running.  
 
   2.For Oracle Names, use the NAMES.TRACE_LEVEL
     command from the Names Control Utility, to set the
     trace level while the Names Server is running.  
 
Note: For Connection Manager, the trace level can only be
      set from the configuration file, CMAN.ORA.
 
Oracle Trace is a tool that will allow you to enable tracing, set trace parameters and format trace data through a graphical user interface (GUI). For more information about using Oracle Trace, refer to the Oracle Enterprise Manager's Oracle Trace User's Guide.
 
3) Use Trace Assistant to interpret your *.trc files
   (created with SQL*Net v2 style tracing) or *.txt
   (output from Orace Trace and TRCFMT - see below).  
 
This utility will help you diagnose and troubleshoot network problems by giving you a better understanding of:
 * the source and destination of trace files
 * the flow of packets between network nodes  
 * which component of Net8 is failing
 * pertinent error codes
 
Run the Trace Assistant by typing the following at the command line:
 
     trcasst [options] <filename>
 
Trace Assistant Text Formatting Options
---------------------------------------
 -o       Displays connectivity and Two Task Common (TTC)
          information.  
          After the -o the following options may be used:
 
               c (for summary connectivity information)
               d (for detailed connectivity information)
               u (for summary TTC information)
               t (for detailed TTC information)
               q (displays SQL commands enhancing summary
                  TTC information)
 
 -p       Oracle Internal Use Only
 
 -s       Displays statistical information  
 
 -e       Enables display of error information
          After the -e, zero or one error decoding level
          may follow:  
 
               0 or nothing (translates the NS error
                 numbers dumped from the nserror function
                 plus lists all other errors)
 
               1 (displays only the NS error translation
                  from the nserror function)
 
               2 (displays error numbers without
                  translation)
 
If no options are provided, then the default is
 -odt -e -s,
providing detailed connectivity, detailed Two-Task
Common, error level 0, and statistics.  
 
4) Net8 tracing includes all the previous SQL*Net v2
   options, and adds Oracle Trace capability. This allows
   your trac information to be managed through an Oracle
   Enterprise Manager console in an Oracle Trace
   repository.
 
5) The *.cdf and *.dat files are created by Oracle Trace.
   To read these,you MUST use the trcfmt utility. It will
   extract and format the data inside binary files (.cdf
   and .dat extensions) into text files (.txt extension).
   To use this tool, type the following at any command
   line prompt:
 
     trcfmt collection.cdf
 
NOTE: "collection" is the name with the path included if
      not in the directory where the .cdf and .dat files
      exist. If you have collected several processes
      within a single .cdf and .dat files, they will be
      extracted to files with the name of process_id.txt.
 
Once you have formatted the data to text, you can view the data through any text editor.

TRACING PARAMETERS

Solution Description:
=====================
SQLNET.ORA Parameters
===========================================================
 DAEMON.TRACE_DIRECTORY
 
 Purpose:         Controls the destination directory of
                  the Oracle Enterprise Manager daemon
                  trace file
 
 Default Value:   $ORACLE_HOME/network/trace
 
 Description
 Available        Oracle Enterprise Manager Installation
                  Guide
 
 Example:         DAEMON.TRACE_DIRECTORY=/oracle/traces
 
-----------------------------------------------------------
 DAEMON.TRACE_LEVEL
 
 Purpose:         Turns tracing on/off to a certain
                  specified level for the Oracle
                  Enterprise Manager daemon.
 
 Default Value:      0 or OFF
 
                        * 0 or OFF - No trace output
 
                        * 4 or USER - User trace
                             information Available Values
                        * 10 or ADMIN - Administration
                                       trace information
                        * 16 or SUPPORT - WorldWide
                        Customer Support trace information
 
 Description
 Available           Oracle Enterprise Manager
                     Installation Guide
 
 Example:            DAEMON.TRACE_LEVEL=10
 
-----------------------------------------------------------
DAEMON.TRACE_MASK
 Purpose:          Specifies that only the Oracle
                   Enterprise Manager daemon trace entries
                   are logged into the trace file.
 
 Default Value:    $ORACLE_HOME/network/trace
 
 Description
 Available         Oracle Enterprise Manager Installation
                   Guide
 
 Example:          DAEMON.TRACE_MASK=(106)
 
 ----------------------------------------------------------
 LOG_DIRECTORY_CLIENT
 Purpose:        Controls the directory for where the log
                 file is written
 
 Default Value:  Current directory where executable is
                 started from.
 
 Example:        LOG_DIRECTORY_CLIENT=/oracle/network/trace
 
-----------------------------------------------------------
 LOG_DIRECTORY_SERVER
 Purpose:        Controls the directory for where the log
                 file is written
 
 Default Value:  Current directory where executable is
                 started from.
 
 Valid in File:  SQLNET.ORA
 
 Example:        LOG_DIRECTORY_SERVER=/oracle/network/trace
 
-----------------------------------------------------------
 LOG_FILE_CLIENT
 Purpose:        Controls the log output filename for an
                 Oracle client.
 
 Default Value:  SQLNET.LOG
 
 Example:        LOG_FILE_CLIENT=client
 
-----------------------------------------------------------
 LOG_FILE_SERVER
 Purpose:        Controls the log output filename for an
                 Oracle server.
 
 Default Value:  SQLNET.LOG
 
 Example:        LOG_FILE_SERVER=svr
 
-----------------------------------------------------------
 NAMESCTL.TRACE_LEVEL
 
 Purpose:        Indicates the level at which the NAMESCTL
                 program should be traced.
 
 Default Value:  OFF
 
 Values:         OFF, USER, or ADMIN
 
 Example:        NAMESCTL.TRACE_LEVEL=ADMIN
 
-----------------------------------------------------------
 NAMESCTL.TRACE_FILE
 
 Purpose:        Indicates the file in which the NAMESCTL
                 trace output is placed.
 
 Default Value:  namesctl_PID.cdf and namesctl_PID.dat
 
 Example:        NAMESCTL.TRACE_FILE=NMSCTL
 
-----------------------------------------------------------
 NAMESCTL.TRACE_DIRECTORY
 
 Purpose:     Indicates the directory where trace output
              from the NAMESCTL utility is placed.
 
 Default
 Value:       $ORACLE_HOME/network/trace
 
 Example:     NAMESCTL.TRACE_DIRECTORY=/ORACLE/TRACE
 
-----------------------------------------------------------
 NAMESCTL.TRACE_UNIQUE
               Indicates whether a process identifier is
               appended to the
 Purpose:      name of each trace file generated, so that
               several can coexist.
 
 Default
 Value:        OFF
 
 Values:       OFF or ON
 
 Example:      NAMESCTL.TRACE_UNIQUE = ON
 
-----------------------------------------------------------
 TNSPING.TRACE_DIRECTORY
 Purpose:        Control the destination directory of the
                 trace file
 
 Default Value:  $ORACLE_HOME/network/trace
 
 Example:        TNSPING.TRACE_DIRECTORY=/oracle/traces
 
-----------------------------------------------------------
 TNSPING.TRACE_LEVEL
 Purpose:         Turns tracing on/off to a certain
                  specified level
 
 Default Value:   0 or OFF
 
                     * 0 or OFF - No trace output
 
                     * 4 or USER - User trace information
                                   Available Values
                     * 10 or ADMIN - Administration trace
                                     information  
                     * 16 or SUPPORT - WorldWide Customer
                                 Support trace information
 
 Example:         TNSPING.TRACE_LEVEL=10
 
-----------------------------------------------------------
 TRACE_DIRECTORY_CLIENT
 Purpose:        Control the destination directory of the
                 trace file
 
 Default Value:  $ORACLE_HOME/network/trace
 
 Example:        TRACE_DIRECTORY_CLIENT=/oracle/traces
 
-----------------------------------------------------------
 TRACE_DIRECTORY_SERVER
 Purpose:        Control the destination directory of the
                 trace file
 
 Default Value:  $ORACLE_HOME/network/trace
 
 Example:        TRACE_DIRECTORY_SERVER=/oracle/traces
 
-----------------------------------------------------------
 TRACE_FILE_CLIENT
 Purpose:        Controls the name of the client trace
                 file
 
 Default Value:  SQLNET.CDF and SQLNET.DAT
 
 Example:        TRACE_FILE_CLIENT=cli
 
-----------------------------------------------------------
 TRACE_FILE_SERVER
 Purpose:        Controls the name of the server trace
                 file
 
 Default Value:  SVR_PID.CDF and SVR_PID.DAT
 
 Example:        TRACE_FILE_SERVER=svr
 
-----------------------------------------------------------
 TRACE_LEVEL_CLIENT
 Purpose:         Turns tracing on/off to a certain
                  specified level
 
 Default Value:   0 or OFF
 
                     * 0 or OFF - No trace output
 
                     * 4 or USER - User trace information
                                   Available Values
                     * 10 or ADMIN - Administration trace
                                     information  
                     * 16 or SUPPORT - WorldWide Customer
                                 Support trace information
 
 Example:         TRACE_LEVEL_CLIENT=10
 
-----------------------------------------------------------
 TRACE_LEVEL_SERVER
 Purpose:         Turns tracing on/off to a certain
                  specified level
 
 Default Value:   0 or OFF
 
                     * 0 or OFF - No trace output
 
                     * 4 or USER - User trace information
                                         Available Values
                     * 10 or ADMIN - Administration trace
                                     information  
                     * 16 or SUPPORT - WorldWide Customer
                                 Support trace information
 
 Example:         TRACE_LEVEL_SERVER=10
 
-----------------------------------------------------------
 TRACE_UNIQUE_CLIENT
             Used to make each client trace file have a
             unique name to
 Purpose:    prevent each trace file from being
             overwritten with the next occurrence of the
             client. The PID is attached to the end of
             the filename.
 
 Default
 Value:      OFF
 
 Example:    TRACE_UNIQUE_CLIENT=ON
 
 USE_CMAN
              If the session is in an Enhanced Discovery
              Network with a
 Purpose:     Names Server, this parameter forces all
              sessions to go through a Connection Manager
              to get to the server.
 
 Default
 Value:       FALSE
 
 Values:      TRUE or FALSE
 
 Example:     USE_CMAN=TRUE
 
===========================================================LISTENER.ORA Parameters
===========================================================
 LOG_DIRECTORY_listener_name
 Purpose:        Controls the directory for where the log
                 file is written
 
 Default Value:  Current directory where executable is
                 started from.
 
 Example:        LOG_DIRECTORY_LISTENER=/oracle/traces
 
-----------------------------------------------------------
 LOG_FILE_listener_name
 
 Purpose:        Specifies the filename where the log
                 information is written
 
 Default Value:  listener_name.log
 
 Example:        LOG_FILE_LISTENER=lsnr
 
-----------------------------------------------------------
 TRACE_DIRECTORY_listener_name
 Purpose:        Control the destination directory of the
                 trace file
 
 Default Value:  $ORACLE_HOME/network/trace
 
 Example:        TRACE_DIRECTORY_LISTENER=/oracle/traces
 
-----------------------------------------------------------
 TRACE_FILE_listener_name
 Purpose:        Controls the name of the listener trace
                 file
 
 Default Value:  LISTENER_NAME.CDF and LISTENER_NAME.DAT
 
 Example:        TRACE_FILE_LISTENER=lsnr
 
-----------------------------------------------------------
 TRACE_LEVEL_listener_name
 Purpose:         Turns tracing on/off to a certain
                  specified level
 
 Default Value:   0 or OFF
 
                     * 0 or OFF - No trace output
 
                     * 4 or USER - User trace information
                                   Available Values
                     * 10 or ADMIN - Administration trace
                                     information  
                     * 16 - WorldWide Customer Support
                                trace information
 
 Example:         TRACE_LEVEL_LISTENER=10
 
===========================================================NAMES.ORA Parameters
===========================================================  
 NAMES.TRACE_DIRECTORY
 
 Purpose:      Indicates the name of the directory to
               which trace files from a Names Server trace
               session are written.
 
 Default
 Value:        platform specific
 
 Example:      names.trace_directory = complete_directory_name
 
-----------------------------------------------------------
 NAMES.TRACE_FILE
 
 Purpose:      Indicates the name of the output file from
               a Names Server trace session. The filename
               extension is always.trc
 
 Default
 Value:        names
 
 Example:      names.trace_file = filename
 
-----------------------------------------------------------
 NAMES.TRACE_LEVEL
 
 Purpose:       Indicates the level at which the Names
                Server is to be traced.
 
 Default Value: OFF
 
 Example:       names.trace_level = [OFF|USER|ADMIN]
 
-----------------------------------------------------------
 NAMES.TRACE_UNIQUE
             indicates whether each trace file has a
             unique name, allowing
 Purpose:    multiple trace files to coexist. If the value
             is set to ON, a process identifier is
             appended to the name of each trace file
             generated.
 
 Default
 Value:      OFF
 
 Example:    names.trace_unique = ON
             names.trace_file = names_05.trc
===========================================================CMAN.ORA Parameters
===========================================================
 TRACING
 
 Default
 Value:      NO
 
 Example:    TRACING = [NO|YES]

Commented:

No comment has been added lately, so it's time to clean up this TA.
I will leave a recommendation in the Cleanup topic area that this question is:
 - PAQ'd and pts removed
Please leave any comments here within the
next seven days.

PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER !

Nic;o)
Commented:
Question has been closed as per recommendation

JGould-EE Moderator

Explore More ContentExplore courses, solutions, and other research materials related to this topic.