My Oracle Support Banner

Kerberos Connections Fail When Using Credential Cache Created by Kinit (Doc ID 360884.1)

Last updated on JULY 03, 2021

Applies to:

Advanced Networking Option - Version to [Release 9.2 to 10.2]
Information in this document applies to any platform.
This problem can occur on any platform.


Kerberos authenticated connections may fail when using the credential cache created using some versions of  MIT's Kerberos utility kinit.

Client sqlnet tracing reveals errors related to the credential cache (error messages vary by platform)


nauk5b1_fcc_open_file: Returning 144: Unsupported credentials cache format version number
nauk5b1_fcc_open_file: exit
nauk5bz_fcc_close_file: entry
snauk5t_close_file: entry
snauk5k_lock_file: entry
snauk5k_lock_file: Resetting lock.
snauk5k_lock_file: fcntl failed with 9: File I/O error
snauk5k_lock_file: Returning 202: OSD error
snauk5k_lock_file: exit
snauk5t_close_file: Could not unlock file.
snauk5t_close_file: Close file: Solaris Error: 9: Bad file number.
snauk5t_close_file: Returning 202: OSD error
snauk5t_close_file: Returning 202: OSD error
snauk5t_close_file: exit
nauk5bz_fcc_close_file: Returning 202: OSD error
nauk5bz_fcc_close_file: exit
nauk5ahgetcontext: entry
nauk5ahgetcontext: Using default context.
nauk5ahgetcontext: exit
NAUK5C_CC_GET_PRINCIPAL: NAUK5C_CC_GET_PRINCIPAL: Unsupported credentials cache format version number




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.