000016886 - Intermittent failure of the RSA Authentication Manager Database service

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

Article Content

Article Number000016886
Applies ToRSA Authentication Manager 7.1 Service Pack 4
IssueUsers unable to authenticate  

Alert log shows the following types of error messages

Tue Dec 18 14:26:33 Pacific Standard Time 2012

Errors in file c:\progra~1\rsasec~1\rsaaut~1\db\admin\qcpoug03\udump\qcpoug03_ora_4772.trc:

ORA-00313: open failed for members of log group 1 of thread 1

ORA-00312: online log 1 thread 1: 'C:\PROGRA~1\RSASEC~1\RSAAUT~1\DB\ORADATA\QCPOUG03\REDO01.LOG'

ORA-27041: unable to open file

OSD-04002: unable to open file

O/S-Error: (OS 2) The system cannot find the file specified.

 

ARC1: All Archive destinations made inactive due to error 354

Committing creation of archivelog 'C:\PROGRA~1\RSASEC~1\RSAAUT~1\BACKUP\QCPOUG03\ARCHIVELOG\2014_02_12\O1_MF_1_223_9HRRLQHH_.ARC' (error 354)

Deleted Oracle managed file C:\PROGRA~1\RSASEC~1\RSAAUT~1\BACKUP\QCPOUG03\ARCHIVELOG\2014_02_12\O1_MF_1_223_9HRRLQHH_.ARC

ARCH: Archival stopped, error occurred. Will continue retrying

Wed Feb 12 22:12:41 Pacific Standard Time 2014

Errors in file c:\progra~1\rsasec~1\rsaaut~1\db\admin\qcpoug03\bdump\qcpoug03_arc1_1668.trc:

ORA-16038: log 1 sequence# 223 cannot be archived

ORA-00354: corrupt redo log block header

ORA-00312: online log 1 thread 1: 'C:\PROGRA~1\RSASEC~1\RSAAUT~1\DB\ORADATA\QCPOUG03\REDO01.LOG'

 

ARCH: Archival stopped, error occurred. Will continue retrying

Wed Feb 12 22:12:49 Pacific Standard Time 2014

Errors in file c:\progra~1\rsasec~1\rsaaut~1\db\admin\qcpoug03\bdump\qcpoug03_arc1_1668.trc:

ORA-16014: log 1 sequence# 223 not archived, no available destinations

ORA-00312: online log 1 thread 1: 'C:\PROGRA~1\RSASEC~1\RSAAUT~1\DB\ORADATA\QCPOUG03\REDO01.LOG'

 

 

 

 

Wed Feb 12 22:17:50 Pacific Standard Time 2014

ARC0: Log corruption near block 170192 change 55258067 time ?

Wed Feb 12 22:17:50 Pacific Standard Time 2014

Errors in file c:\progra~1\rsasec~1\rsaaut~1\db\admin\qcpoug03\bdump\qcpoug03_arc0_1652.trc:

ORA-00354: corrupt redo log block header

ORA-00353: log corruption near block 170192 change 55258067 time 02/10/2014 15:14:10

ORA-00312: online log 1 thread 1: 'C:\PROGRA~1\RSASEC~1\RSAAUT~1\DB\ORADATA\QCPOUG03\REDO01.LOG'

 

Tue Apr 01 18:07:11 Pacific Daylight Time 2014

Errors in file c:\progra~1\rsasec~1\rsaaut~1\db\admin\qcpoug03\udump\qcpoug03_ora_5172.trc:

ORA-19816: WARNING: Files may exist in db_recovery_file_dest that are not known to database.

*************************************************************

WARNING: Files created after time 04/01/2014 17:59:00 may exist in

db_recovery_file_dest that is not known to the database.

Use the RMAN command CATALOG RECOVERY AREA to re-catalog

any such files. This is most likely the result of a crash

during file creation.

*************************************************************


Server log shows the following type of error message

####<Mar 30, 2014 9:04:44 AM PDT> <Info> <JDBC> <RSA-DB> <rsa-db_server> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1396195484696> <BEA-001156> <Stack trace associated with message 001129 follows:  

java.sql.SQLException: ORA-00257: archiver error. Connect internal only, until freed. 

            at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)

            at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)

            at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:283)

            at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:278)

            at oracle.jdbc.driver.T4CTTIoauthenticate.receiveOsesskey(T4CTTIoauthenticate.java:293)

            at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:357)

            at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:427)

            at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:78)

            at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)

            at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:801)

            at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:299)

            at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:200)

            at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1073)

            at weblogic.common.resourcepool.ResourcePoolImpl$ResourcePoolMaintanenceTask.timerExpired(ResourcePoolImpl.java:2209)

            at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:271)

            at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)

            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)

            at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)

 

CauseThird party backup software has been installed on the server running the RSA Authentication Manager software which has caused inconsistencies in the database which cannot be recovered.
Resolution

Reinstallation of the RSA Authentication Manager Service Pack 4 Full Kit product

Customer will need the following:

Database backup (if possible)

License zip file

Refer to the RSA Authentication Manager 7.1 Installation and Configuration Guide - https://knowledge.rsasecurity.com/docs/rsa_securid/rsa_auth_mgr/71sp4p5/auth_manager_installation_guide.pdf

Legacy Article IDa64848

Attachments

    Outcomes