000012218 - 'Users never logged in with token' report fails to successfully complete

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

Article Content

Article Number000012218
Applies ToAuthentication Manager 7.1 pre SP2
IssueIn imsTrace.log: com.rsa.common.UnexpectedDataStoreException: ORA-12899: value too large for column "RSA_NOREP"."AM_REPORT_NO_LOGINS"."TOKEN_PIN_TYPE" (actual: 14, maximum: 12)
"Users never logged in with token" report fails
CauseThe "Users never logged in with token" report fails to run on a AM 7.1 pre-SP2 system.
An exceptoin similar to the following would appear in imsTrace.log:
2009-11-23 09:54:41,152,  ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'], (PrincipalTokenReportBase.java:1043), trace.com.rsa.authmgr.internal.report.PrincipalNeverLoggedInWithTokenReport, ERROR, , , , , ORA-12899: value too large for column "RSA_NOREP"."AM_REPORT_NO_LOGINS"."TOKEN_PIN_TYPE" (actual: 14, maximum: 12)
2009-11-23 09:54:41,153, ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'], (BatchJobTXEngine.java:381), trace.com.rsa.ims.batchjob.impl.BatchJobTXEngine, ERROR, , , , , Error running job: BatchJob {id=1ebf69e34805520a02ac31809bf3c63a, name: UserNeverLog_mtlops_112309_0954AM_HKT, principal: 000000000000000000001000d0021000, principal UID: xxxxxxx, creation time: Mon Nov 23 09:54:38 HKT 2009, status: 1, category: REPORT, result location: null, description: , error message: null, error key: null, node ID: xxxxxxxxx_server, schedule ID: null, completion date: null, total number: 34, finished number: 35, progress message: null, result: null, job age: 2880}
com.rsa.common.UnexpectedDataStoreException: ORA-12899: value too large for column "RSA_NOREP"."AM_REPORT_NO_LOGINS"."TOKEN_PIN_TYPE" (actual: 14, maximum: 12)
at com.rsa.authmgr.internal.report.PrincipalTokenReportBase.generatePrincipalWithTokensReport(PrincipalTokenReportBase.java:1045)
at com.rsa.authmgr.internal.report.PrincipalNeverLoggedInWithTokenReport.generateReport(PrincipalNeverLoggedInWithTokenReport.java:81)
at com.rsa.ims.reportframework.ReportBase.startBatchJob(ReportBase.java:120)
at com.rsa.ims.batchjob.impl.BatchJobTXEngine$4.run(BatchJobTXEngine.java:370)
at com.rsa.ims.batchjob.impl.BatchJobTXEngine$4.run(BatchJobTXEngine.java:359)
at com.rsa.ims.security.spi.SimpleSecurityContextImpl.doAs(SimpleSecurityContextImpl.java:91)
at com.rsa.security.SecurityContext.doAs(SecurityContext.java:408)
at com.rsa.ims.batchjob.impl.BatchJobTXEngine.execute(BatchJobTXEngine.java:358)
at com.rsa.ims.batchjob.mdb.BatchJobMDBean.onMessage(BatchJobMDBean.java:108)
Resolution A bug that is fixed in AM 7.1 SP2 caused this issue to occur. The report tried to store in  SQL table column a too long value for users that have never logged on with a PINless token assigned to them.
Please install AM 7.1SP2 that can be downloaded from SecureCare online.
Legacy Article IDa48816

Attachments

    Outcomes