Review Refresh fails with 'ORA-00607 Internal error while making a change to a data block' in RSA Identity Governance & Lifecycle
3 years ago
Originally Published: 2020-04-13
Article Number
000049759
Applies To
RSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.0.x, 7.1.x, 7.2.x
 
Issue
Review refresh in RSA Identity Governance & Lifecycle fails. The Run Details screen (Admin > Monitoring > Data Runs tab, {run id}) shows the status as having failed.
 
User-added image
 
The following error is logged to the aveksaServer.log file ($AVEKSA_HOME/wildfly/standalone/log/aveksaServer.log) when ...   
04/13/2020 14:25:00.036 INFO (ThreadPool-4) [com.aveksa.server.core.rule.RuleServiceProvider] 
Completed process of closing expired exceptional access
04/13/2020  15:09:16.389 INFO (Exec Task Consumer#0 - Sequence) [com.aveksa.server.db.persistence.PersistenceServiceProvider] 
executeCallableStatement giving up after hitting SQLException: 
ORA-00603: ORACLE server session terminated by fatal error
ORA-00607: Internal error occurred while making a change to a data block
ORA-00600: internal error code, arguments: [kdBlkCheckError], [201], [30848], [14508], [], [], [], [], [], [], [], []

04/13/2020  15:09:16.389 WARN (Exec Task Consumer#0 - Sequence) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] 
SQL Error: 603, SQLState: 08006
04/13/2020  15:09:16.390 ERROR (Exec Task Consumer#0 - Sequence) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] 
ORA-00603: ORACLE server session terminated by fatal error
ORA-00607: Internal error occurred while making a change to a data block
ORA-00600: internal error code, arguments: [kdBlkCheckError], [201], [30848], [14508], [], [], [], [], [], [], [], []

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. The aveksaServer.log may also be downloaded from the RSA Identity Governance & Lifecycle user interface (Admin > System > Server Nodes tab > under Logs.)
 
Cause
This is a known issue reported in engineering ticket ACM-103279 and is caused by the enablement of the TEMP_UNDO_ENABLED parameter. For more information on this parameter and its use with RSA Identity Governance & Lifecycle, see RSA Knowledge Base Article  000038718 -- Oracle 12c TEMP_UNDO_ENABLED parameter for managing GTT UNDO activity in RSA Identity Governance & Lifecycle.
 
Resolution
Disable the parameter TEMP_UNDO_ENABLED:
 
Login to SQL as SYS user
  
SQL> alter session set temp_undo_enabled=false scope=both;

By setting scope=both, this parameter will take effect immediately and will remain in effect after a system reboot.

 

Related Articles

Trending Articles

Don't see what you're looking for?