000028808 - KB-1061 - Unable to authenticate error on log-in page

Document created by RSA Customer Support Employee on Jun 15, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000028808
Applies ToAffected Versions: All Versions
IssueAveksa Login screen says "no authentication source"
If on a cluster clustat shows the server bouncing between started/restarting
Resolution1. Check the startup log to see if we have the log file problem:
tail startup.log
The error is similar to:
ORA-16038: log 2 sequence# 2502 cannot be archived
ORA-19504: failed to create file ""
ORA-00312: online log 2 thread 1: '+DG01/avdb/onlinelog/group_2.265.643730255'
ORA-00312: online log 2 thread 1: '+DG01/avdb/onlinelog/group_2.266.643730295'
Note the log file number - in this case its "online log 2"
If there is a different message, this process is not required - contact Aveksa Customer Support
2A. Cluster
Shutdown the cluster software (database and Aveksa Services) using:
sudo AlterCluster.sh off
2B. Non clustered appliances
Shutdown the database from the command line using:
dbshut or sudo service dbora stop
3. Shutdown the AVDB instance through sqlplus:
sqlplus / as sysdba
SQL> shutdown;
4. Shutdown the +ASM instance
sqlplus / as sysdba
SQL> shutdown;
5. Run a ps-ef and ensure
No AVDB or +ASM processes are running
No scripts running "AVDB" or "ACM" start | stop | restart (kill the process if it's running)
6. From the command line start the database:
dbstart or sudo service dbora start
7. Clear the log file using the commands:
sqlplus / as sysdba
SQL> alter database clear unarchived logfile group 2;
** Your logfile group may be different ***
8. Reboot the machine
10. After the machine restarts, ensure the database and Aveksa services or clustering has started.
sudo AlterCluster.sh on
11. Verify you can access the dB correctly