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.
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.)