ORA-12899: value too large for column "AVUSER"."STX_450689643"."OBJECT_TYPE" when importing a coverage file into an RSA Identity Governance & Lifecycle Review
Originally Published: 2019-08-06
Last Modified: 2023-11-30
Article Number
000041213
Applies To
RSA Product Set: Identity Governance & Lifecycle
RSA Version/Condition: All
   
Issue
Uploading a Coverage file to a User Access Review in RSA Identity Governance & Lifecycle fails with the following error in the user interface:
  
ORA-12899: value too large for column "AVUSER"."STX_450689643"."OBJECT_TYPE" (actual: 59, maximum: 50)

The following errors can be seen in the aveksaServer.log:
 
06/27/2019 14:35:43.103 ERROR (default task-24) [com.aveksa.gui.pages.review.definition.edit.coverage.UploadCoverageDataPageData] 
com.aveksa.server.review.ReviewServiceException: Error while processing coverage file <br><br>ORA-12899: value too large for column "AVUSER"."STX_450689643"."OBJECT_TYPE" (actual: 59, maximum: 50) 

at com.aveksa.server.review.ReviewServiceProvider.validateCoverageFile(ReviewServiceProvider.java:1695) 
at com.aveksa.server.review.ReviewServiceProvider.validateReviewerCoverageFile(ReviewServiceProvider.java:1658) 
Caused by: com.aveksa.server.db.PersistenceException: java.sql.BatchUpdateException: ORA-12899: value too large for column "AVUSER"."STX_450689643"."OBJECT_TYPE" (actual: 59, maximum: 50) 
at com.aveksa.server.review.ReviewUtils.loadCoverageIntoTmpTable(ReviewUtils.java:155) 
at com.aveksa.server.review.ReviewServiceProvider.validateCoverageFile(ReviewServiceProvider.java:1684) 
... 65 more 
Caused by: java.sql.BatchUpdateException: ORA-12899: value too large for column "AVUSER"."STX_450689643"."OBJECT_TYPE" (actual: 59, maximum: 50) 
at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:12296) 
at oracle.jdbc.driver.OracleStatementWrapper.executeBatch(OracleStatementWrapper.java:246) 
at org.jboss.jca.adapters.jdbc.WrappedStatement.executeBatch(WrappedStatement.java:1190) 
at com.aveksa.server.db.FileToTable.commitBatchToDB(FileToTable.java:397) 
at com.aveksa.server.db.FileToTable.process(FileToTable.java:372) 
at com.aveksa.server.review.ReviewUtils.loadCoverageIntoTmpTable(ReviewUtils.java:149) 

Please refer to RSA Knowledge Base Article 000030327 - Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the log files for your specific deployment.   
Cause
The separator character used to separate fields in the coverage file exists in the data itself.

 For example, the structure of a coverage file for a review is as follows:
 
<Reviewer/Monitor Filter>|<Subject Type>|<Subject Filter>|<Object Type>|<Object Filter>|<Privilege>

A legitimate sample entry could be as follows where the application name is Payroll.
  
user_id='009'|user|department='HR'|application|name='Payroll'|

What if the application name was 0025|Payroll as in:
  
user_id='009'|user|department='HR'|application|name='0025|Payroll'|

The use of the separator character (|) in the text field will cause this error.
 
Resolution
The separator character cannot be used in the data. One way to resolve this issue would be to change the coverage file entry
 
FROM:
user_id='009'|user|department='HR'|application|name='0025|Payroll'|
TO:
user_id='009'|user|department='HR'|application|name='0025%Payroll'|

 

Related Articles

Trending Articles

Don't see what you're looking for?