Therefore, the original server's public key is now also stored in the replica server's cred table. Most of these locations will be updated automatically within a time ranging from a few minutes to 12 hours. This is because a corrupt credential provides no permissions at all, not even the permissions granted to the nobody class. Symptoms User or root cannot perform any namespace tasks or operations. The user or root cannot even perform a nisls operation.
Diagnosis Use iptrace to identify the bad credential.
For example, in most cases an object grants read authorization to the nobody class. Thus, the nisls object command should work for any principal listed in the cred table. Solution Ordinary user . The keyserv is unable to encrypt a session. The client has not keylogged in.