This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
Register Now
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

SecurID® Governance & Lifecycle Knowledge Base

Find answers to your questions and identify resolutions for known issues with knowledge base articles written by SecurID Governance & Lifecycle experts.

ASR fails to generate with an 'ORA-01422: exact fetch returns more than requested number of rows' error in RSA Identity Governance & Lifecycle

Article Number

000038411

Applies To

RSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.1.1
 

Issue

An Aveksa Statistics Report (ASR) cannot be generated in RSA Identity Governance & Lifecycle .

The RSA Identity Governance & Lifecycle user interface (Admin > Diagnostics) shows all Statistics Reports with a status of Generating.
 
Image descriptionImage description

The aveksaServer.log file ($AVEKSA_HOME/wildfly/standalone/log/aveksaServer.log) has the following errors: 
06/27/2019 11:59:59.492 INFO  (SystemReport) [com.aveksa.server.db.persistence.PersistenceServiceProvider] 
executeCallableStatement giving up after hitting SQLException: ORA-01422: exact fetch returns more than requested number of rows
ORA-06512: at "AVUSER.SRSECTION_SYSTEM", line 378
ORA-06512: at "AVUSER.SYSTEM_REPORT", line 193
ORA-06512: at "AVUSER.SYSTEM_REPORT", line 246
ORA-06512: at line 1

06/27/2019 11:59:59.492 WARN  (SystemReport) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] 
SQL Error: 1422, SQLState: 21000
06/27/2019 11:59:59.492 ERROR (SystemReport) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] 
ORA-01422: exact fetch returns more than requested number of rows
ORA-06512: at "AVUSER.SRSECTION_SYSTEM", line 378
ORA-06512: at "AVUSER.SYSTEM_REPORT", line 193
ORA-06512: at "AVUSER.SYSTEM_REPORT", line 246
ORA-06512: at line 1

06/27/2019 11:59:59.502 ERROR (SystemReport) [com.aveksa.server.system.SystemReport] ASR Params: 
[Lcom.aveksa.server.db.ProcedureParameter;@47989803
com.aveksa.server.db.PersistenceException: java.sql.SQLException: ORA-01422: exact fetch returns more than requested number of rows
ORA-06512: at "AVUSER.SRSECTION_SYSTEM", line 378
ORA-06512: at "AVUSER.SYSTEM_REPORT", line 193
ORA-06512: at "AVUSER.SYSTEM_REPORT", line 246
ORA-06512: at line 1

	at com.aveksa.server.db.persistence.PersistenceServiceProvider.runStoredProcedure(PersistenceServiceProvider.java:1548)
	at com.aveksa.server.db.persistence.PersistenceServiceProvider.runStoredProcedure(PersistenceServiceProvider.java:1480)
	at com.aveksa.server.db.PersistenceManager.runStoredProcedure(PersistenceManager.java:245)
	at com.aveksa.server.system.SystemReport.backgroundGenerateReport(SystemReport.java:129)
	at com.aveksa.server.system.SystemReport$1.run(SystemReport.java:71)
	at java.lang.Thread.run(Thread.java:812)
Caused by: 
java.sql.SQLException: ORA-01422: exact fetch returns more than requested number of rows
ORA-06512: at "AVUSER.SRSECTION_SYSTEM", line 378
ORA-06512: at "AVUSER.SYSTEM_REPORT", line 193
ORA-06512: at "AVUSER.SYSTEM_REPORT", line 246
ORA-06512: at line 1

	at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:494)
	at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:446)
	at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1054)
	at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:623)
	at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:252)
	at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:612)
	at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:223)
	at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:56)
	at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:907)
	at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1119)
	at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3780)
	at oracle.jdbc.driver.T4CCallableStatement.executeInternal(T4CCallableStatement.java:1300)
	at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3887)
	at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:4230)
	at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1079)
	at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecute(WSJdbcPreparedStatement.java:1066)
	at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.execute(WSJdbcPreparedStatement.java:637)
	at com.aveksa.server.db.persistence.work.PersistenceServiceBaseWork.executeCallableStatement(PersistenceServiceBaseWork.java:36)
	at com.aveksa.server.db.persistence.work.StoredProcedureCallWork.execute(StoredProcedureCallWork.java:80)
	at org.hibernate.jdbc.WorkExecutor.executeWork(WorkExecutor.java:37)
	at org.hibernate.internal.SessionImpl$3.accept(SessionImpl.java:2134)
	at org.hibernate.internal.SessionImpl$3.accept(SessionImpl.java:2131)
	at org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.coordinateWork(JdbcCoordinatorImpl.java:332)
	at org.hibernate.internal.SessionImpl.doWork(SessionImpl.java:2153)
	at org.hibernate.internal.SessionImpl.doWork(SessionImpl.java:2138)
	at com.aveksa.server.db.persistence.PersistenceServiceProvider.runStoredProcedure(PersistenceServiceProvider.java:1526)
	... 5 more
Caused by: 
Error : 1422, Position : 0, Sql = BEGIN System_Report.Run(:1 ,:2 ,:3 ,:4 ); END;, 
OriginalSql = {call System_Report.Run(?,?,?,?)}, Error Msg = ORA-01422: exact fetch returns more than requested number of rows
ORA-06512: at "AVUSER.SRSECTION_SYSTEM", line 378
ORA-06512: at "AVUSER.SYSTEM_REPORT", line 193
ORA-06512: at "AVUSER.SYSTEM_REPORT", line 246
ORA-06512: at line 1

	at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:498)
	... 30 more

Please refer to RSA Knowledge Base Article 000030327 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the aveksaServer.log file for your specific deployment if you are on a WildFly cluster or a non-WildFly platform.
 

Cause

This is a known issue reported in engineering ticket ACM-99240.
 

Resolution

This issue is resolved in the following RSA Identity Governance & Lifecycle versions and/or patch levels:
  • RSA Identity Governance & Lifecycle 7.1.1 P04
  • RSA Identity Governance & Lifecycle 7.2
Please contact RSA Identity Governance & Lifecycle Support to move the report(s) from Generating status to Completed status. The report(s) may then be deleted.

Please see related RSA Knowledge Base Articles:

Workaround

The ASR may be run from the Linux command line. Please see RSA Knowledge Base Article 000027912 -- How to create an Aveksa Statistics Report (ASR) from the Linux command line using SQL in RSA Identity Governance & Lifecycle for this workaround.
 
0 Likes
Was this article helpful? Yes No
No ratings

In this article

Version history
Last update:
‎2020-12-12 11:47 AM
Updated by:
Administrator Administrator

Related Content

© 2023 RSA Security LLC or its affiliates. All rights reserved.