ASR Report fails with ERROR ORA-06502: PL/SQL: numeric or value error: character string buffer too small in RSA Identity Governance and Lifecycle Version 7.x
Originally Published: 2019-09-20
Article Number
Applies To
RSA Product/Service Type: Enterprise Software
RSA Version/Condition: 7.1.0
Issue
Same behavior is observed when we try to run the report manually.
Below error is logged in aveksaServer.log
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
Complete ERROR
09/20/2019 15:23:17.815 ERROR (SystemReport) [com.aveksa.server.system.SystemReport] ASR Params: [Lcom.aveksa.server.db.ProcedureParameter;@61b2c4c4
com.aveksa.server.db.PersistenceException: java.sql.SQLException: ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at "AVUSER.SYSTEM_REPORT", line 224
ORA-06512: at line 1
at com.aveksa.server.db.persistence.PersistenceServiceProvider.runStoredProcedure(PersistenceServiceProvider.java:1534)
at com.aveksa.server.db.persistence.PersistenceServiceProvider.runStoredProcedure(PersistenceServiceProvider.java:1469)
at com.aveksa.server.db.PersistenceManager.runStoredProcedure(PersistenceManager.java:269)
at com.aveksa.server.system.SystemReport.backgroundGenerateReport(SystemReport.java:136)
at com.aveksa.server.system.SystemReport.access$000(SystemReport.java:53)
at com.aveksa.server.system.SystemReport$1.run(SystemReport.java:72)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.sql.SQLException: ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at "AVUSER.SYSTEM_REPORT", line 224
ORA-06512: at line 1
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:450)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1059)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:522)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:257)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:587)
at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:220)
at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:48)
at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:938)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1150)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:4798)
at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:4901)
at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:5631)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1385)
at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.execute(WrappedPreparedStatement.java:442)
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:1512)
... 6 more
Cause
For example:
If you have set your Environment Name in Admin --> System --> Settings as shown below, it will result into the ASR generation failure with the errors mentioned above.
PRODUCTION ENVIRONMENT SOFT APPLIANCE WITH LOCAL DATABASE AND WILDFLY
Resolution
